Github messages for voidlinux
 help / color / mirror / Atom feed
From: Sapein <Sapein@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: screen frozen linux6.6 and 6.7
Date: Fri, 09 Feb 2024 19:10:55 +0100	[thread overview]
Message-ID: <20240209181055.5DCC0240BD@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: 1059 bytes --]

New comment by Sapein on void-packages repository

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

Comment:
I'm having a similar -- if not the same -- issue on my install as well. 

This issue does _not_ occur on Kernels 6.5.5_2, 6.5.12_1, and 6.1.29_1. It does occur on the 6.6.8, 6.6.11, and 6.6.16. At least from my testing.

doing `nomodeset=1` does allow the system to boot, but it breaks anything graphical, treating my two monitors as one and not allowing me to actually set a resolution with X, and sway still refuses to start (where-as on the 6.5 kernels it does start. It also does not start on the 6.1.29 kernel but with a different error).

My system information is as follows:
- Void Linux x86_64 glibc
-  AMD Ryzen 7 5800X
-  Nvidia GeForce RTX 3060

I included the CPU as it does not include integrated graphics, IIRC.

Using the Proprietary Nvidia drivers does work, but I ran into the issue because sway won't start with them it seems, so I wanted to switch to the Nouveau ones to try out sway.

  parent reply	other threads:[~2024-02-09 18:10 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 [this message]
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=20240209181055.5DCC0240BD@inbox.vuxu.org \
    --to=sapein@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).