From: mblouka <mblouka@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: screen frozen linux6.6 and 6.7
Date: Tue, 06 Feb 2024 18:25:18 +0100 [thread overview]
Message-ID: <20240206172518.4DDAA2586A@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48473@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
New comment by mblouka on void-packages repository
https://github.com/void-linux/void-packages/issues/48473#issuecomment-1930417009
Comment:
I had this problem a month-ish ago and it was due to `nouveau`. Blacklisting the module correctly prior to a system upgrade completely fixes the problem, but you will have to use proprietary drivers as a replacement until this is fixed. You can see the relevant discussion here: https://old.reddit.com/r/voidlinux/comments/18w0mq9/upgrade_to_kernel_668_hangs_the_os_at_boot/
I was able to solve this by booting from the latest ISO, installing the system from local packages, blacklisting `nouveau` through dracut and the other initramfs mechanism (you can find instructions for both from the handbook), then performing a full system upgrade. The upgrade automatically rebuilds the ramfs configuration, so there's no need to do anything manually. That worked across multiple installations as well. As for why blacklisting didn't work for you earlier, make sure to blacklist _before_ installing the new kernel and doing a system upgrade, or otherwise you will have to reconfigure ramfs manually.
next prev parent reply other threads:[~2024-02-06 17:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 3:57 [ISSUE] " levdopa
2024-02-01 15:47 ` abenson
2024-02-01 20:19 ` levdopa
2024-02-01 20:27 ` classabbyamp
2024-02-01 22:09 ` levdopa
2024-02-06 1:57 ` nau5ea
2024-02-06 17:24 ` mblouka
2024-02-06 17:25 ` mblouka [this message]
2024-02-06 17:26 ` mblouka
2024-02-09 18:10 ` Sapein
2024-03-09 12:17 ` Brixy
2024-03-23 17:20 ` thomasxg
2024-03-23 19:24 ` mblouka
2024-03-23 19:24 ` mblouka
2024-04-16 20:14 ` nezos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240206172518.4DDAA2586A@inbox.vuxu.org \
--to=mblouka@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).