Github messages for voidlinux
 help / color / mirror / Atom feed
From: mblouka <mblouka@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: screen frozen linux6.6 and 6.7
Date: Sat, 23 Mar 2024 20:24:30 +0100	[thread overview]
Message-ID: <20240323192430.5A149217CA@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: 1107 bytes --]

New comment by mblouka on void-packages repository

https://github.com/void-linux/void-packages/issues/48473#issuecomment-2016581720

Comment:
@thomasxg I no longer have it but when I faced this issue months ago it had a very similar trace to what you just posted. The issue is definitely GPU-related, and doesn't happen on proprietary drivers, only nouveau.

With the release of the new live image on March 14 however the problem has become worse and could impact adoption. With the previous live image, you could boot into live Void without any issues, install the OS to disk using local packages, reboot then blacklist nouveau right before performing an update. That's what I did to get Void working on my Nvidia machine (2080 Ti). However, the new live image rolls in the regression, meaning you cannot even reach a terminal after GRUB without explicitly blacklisting the nouveau driver and modeset through kernel flags. I had to do this recently when I reinstalled Void, which is practically simple but difficult to figure out when you don't even have logs or any output telling you what's erroring.

  parent reply	other threads:[~2024-03-23 19:24 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
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 [this message]
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=20240323192430.5A149217CA@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).