Hi,
I've been having a consistent failure of startx apparently due to the addition of "nomodeset" to the kernel boot parameters. I have been using "nomodeset" for several years. This has been happening for about 2 weeks. See startx log below.
Has anyone else seen this problem?
Best regards,
George...
xauth: file /root/.serverauth.136471 does not exist xauth: (stdin):2: unknown command "3cf149665e8d99e82510d31544f1a594"
X.Org X Server 1.21.1.13 X Protocol Version 11, Revision 0 Current Operating System: Linux fc42 6.12.0-0.rc0.20240927git075dbe9f6e3c.14.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Sep 27 17:02:57 U TC 2024 x86_64 Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-6.12.0-0.rc0.20240927git075dbe9f6e3c.14.fc42.x86_64 root=UUID=6ef3dfc3-32ed-4f01 -bebb-64f66a016d37 ro resume=UUID=e3537362-f3a8-48f3-94e7-f7b4de63fe42 nomodeset vga 791 net.ifnames=0 biosdevname=0 audit=0 selinux= 0 Build ID: xorg-x11-server 21.1.13-4.fc42 Current version of pixman: 0.43.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 2 10:37:28 2024 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) no screens found(EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error
George R Goffe composed on 2024-10-05 17:26 (UTC):
I've been having a consistent failure of startx apparently due to the addition of "nomodeset" to the kernel boot parameters.
Nomodeset is a troubleshooting parameter, designed to enable failsafe GUI operation so that logs can be accessed and reconfiguration can be performed in a crude fallback graphical environment. AIUI, Gnome and KDE/Plasma cannot run in either of these fallback GUI modes. Nomodeset blocks all kernel graphics modules that provide the KMS (Kernel Mode Setting) that all competent FOSS graphics drivers (amdgpu, intel, modesetting, nouveau, radeon) unconditionally depend on.
On Sat, 2024-10-05 at 17:26 +0000, George R Goffe via test wrote:
Hi,
I've been having a consistent failure of startx apparently due to the addition of "nomodeset" to the kernel boot parameters. I have been using "nomodeset" for several years. This has been happening for about 2 weeks. See startx log below.
Has anyone else seen this problem?
we drop int10 everywhere and obsolete vesa and fbdev X drivers [1]
if is related please try 21.1.13-3 https://koji.fedoraproject.org/koji/buildinfo?buildID=2556149
also need to check if you got vesa and fbdev installed
[1] * Mon Sep 30 2024 Simone Caronni negativo17@gmail.com - 21.1.13-5 - After removal of int10/vbe, obsolete vesa and fbdev X drivers: https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers
* Sat Sep 28 2024 Simone Caronni negativo17@gmail.com - 21.1.13-4 - Remove all conditionals. Drop int10 everywhere and enable libunwind/dri3 on ELN.
Best regards,
George...
xauth: file /root/.serverauth.136471 does not exist xauth: (stdin):2: unknown command "3cf149665e8d99e82510d31544f1a594"
X.Org X Server 1.21.1.13 X Protocol Version 11, Revision 0 Current Operating System: Linux fc42 6.12.0- 0.rc0.20240927git075dbe9f6e3c.14.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Sep 27 17:02:57 U TC 2024 x86_64 Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-6.12.0- 0.rc0.20240927git075dbe9f6e3c.14.fc42.x86_64 root=UUID=6ef3dfc3-32ed- 4f01 -bebb-64f66a016d37 ro resume=UUID=e3537362-f3a8-48f3-94e7- f7b4de63fe42 nomodeset vga 791 net.ifnames=0 biosdevname=0 audit=0 selinux= 0 Build ID: xorg-x11-server 21.1.13-4.fc42 Current version of pixman: 0.43.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 2 10:37:28 2024 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) no screens found(EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error
On Sat, 2024-10-05 at 19:32 +0100, Sérgio Basto wrote:
On Sat, 2024-10-05 at 17:26 +0000, George R Goffe via test wrote:
Hi,
I've been having a consistent failure of startx apparently due to the addition of "nomodeset" to the kernel boot parameters. I have been using "nomodeset" for several years. This has been happening for about 2 weeks. See startx log below.
Has anyone else seen this problem?
we drop int10 everywhere and obsolete vesa and fbdev X drivers [1]
if is related please try 21.1.13-3 https://koji.fedoraproject.org/koji/buildinfo?buildID=2556149
also need to check if you got vesa and fbdev installed
What xorg driver is expected to be used now with nomodeset, if not vesa or fbdev?
On Sat, 2024-10-05 at 13:52 -0700, Adam Williamson wrote:
On Sat, 2024-10-05 at 19:32 +0100, Sérgio Basto wrote:
On Sat, 2024-10-05 at 17:26 +0000, George R Goffe via test wrote:
Hi,
I've been having a consistent failure of startx apparently due to the addition of "nomodeset" to the kernel boot parameters. I have been using "nomodeset" for several years. This has been happening for about 2 weeks. See startx log below.
Has anyone else seen this problem?
we drop int10 everywhere and obsolete vesa and fbdev X drivers [1]
if is related please try 21.1.13-3 https://koji.fedoraproject.org/koji/buildinfo?buildID=2556149
also need to check if you got vesa and fbdev installed
What xorg driver is expected to be used now with nomodeset, if not vesa or fbdev?
I tried keep int10 etc , but the argument was that everything was replaced by modesetting and simpledrm and RHEL already removed int10
https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers#Detailed_Descript...
so I guess nomodeset option also should be remove from the kernel because now is useless , unless George or someone else show that still be useful , i.e. simpledrm doesn't replace it .
-- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net
On Sun, 2024-10-06 at 15:26 +0100, Sérgio Basto wrote:
On Sat, 2024-10-05 at 13:52 -0700, Adam Williamson wrote:
On Sat, 2024-10-05 at 19:32 +0100, Sérgio Basto wrote:
On Sat, 2024-10-05 at 17:26 +0000, George R Goffe via test wrote:
Hi,
I've been having a consistent failure of startx apparently due to the addition of "nomodeset" to the kernel boot parameters. I have been using "nomodeset" for several years. This has been happening for about 2 weeks. See startx log below.
Has anyone else seen this problem?
we drop int10 everywhere and obsolete vesa and fbdev X drivers [1]
if is related please try 21.1.13-3 https://koji.fedoraproject.org/koji/buildinfo?buildID=2556149
also need to check if you got vesa and fbdev installed
What xorg driver is expected to be used now with nomodeset, if not vesa or fbdev?
I tried keep int10 etc , but the argument was that everything was replaced by modesetting and simpledrm and RHEL already removed int10
https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers#Detailed_Descript...
I have to admit I didn't quite understand this justification, since that change is from several releases ago and the scope says nothing about removing X.org drivers....
so I guess nomodeset option also should be remove from the kernel because now is useless , unless George or someone else show that still be useful , i.e. simpledrm doesn't replace it .
Well, I know it's still sometimes used if e.g. you have a very new NVIDIA card that the nouveau driver is confused by. Is there a different option that should now be used in such a case to force the use of simpledrm instead of a native driver?
On Sun, 2024-10-06 at 18:55 -0700, Adam Williamson wrote:
On Sun, 2024-10-06 at 15:26 +0100, Sérgio Basto wrote:
On Sat, 2024-10-05 at 13:52 -0700, Adam Williamson wrote:
On Sat, 2024-10-05 at 19:32 +0100, Sérgio Basto wrote:
On Sat, 2024-10-05 at 17:26 +0000, George R Goffe via test wrote:
Hi,
I've been having a consistent failure of startx apparently due to the addition of "nomodeset" to the kernel boot parameters. I have been using "nomodeset" for several years. This has been happening for about 2 weeks. See startx log below.
Has anyone else seen this problem?
we drop int10 everywhere and obsolete vesa and fbdev X drivers [1]
if is related please try 21.1.13-3 https://koji.fedoraproject.org/koji/buildinfo?buildID=2556149
also need to check if you got vesa and fbdev installed
What xorg driver is expected to be used now with nomodeset, if not vesa or fbdev?
I tried keep int10 etc , but the argument was that everything was replaced by modesetting and simpledrm and RHEL already removed int10
https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers#Detailed_Descript...
I have to admit I didn't quite understand this justification, since that change is from several releases ago and the scope says nothing about removing X.org drivers....
so I guess nomodeset option also should be remove from the kernel because now is useless , unless George or someone else show that still be useful , i.e. simpledrm doesn't replace it .
Well, I know it's still sometimes used if e.g. you have a very new NVIDIA card that the nouveau driver is confused by. Is there a different option that should now be used in such a case to force the use of simpledrm instead of a native driver?
not loading the drive and using drive modesetting drive , I guess
Adam,
Thanks to you and Sergio for responding to my query... It's appreciated.
I have used nomodeset for so long I don't recall which driver I've been expecting to use.
My reason(s) for using nomodeset started several years ago... I think it was because of the turmoil related to driver updates. My main reason for using it now is that the font used by console output REALLY small and I have a hard time reading it.
I have tried using the ask boot parameter but it's a somewhat unwieldy interface to use and get the desired results.
From the Xorg.0.log file (below), it's not clear which driver is being selected.
What to do?
Best regards,
George...
On Sunday, October 6, 2024 at 06:55:58 PM PDT, Adam Williamson adamwill@fedoraproject.org wrote:
On Sun, 2024-10-06 at 15:26 +0100, Sérgio Basto wrote:
On Sat, 2024-10-05 at 13:52 -0700, Adam Williamson wrote:
On Sat, 2024-10-05 at 19:32 +0100, Sérgio Basto wrote:
On Sat, 2024-10-05 at 17:26 +0000, George R Goffe via test wrote:
Hi,
I've been having a consistent failure of startx apparently due to the addition of "nomodeset" to the kernel boot parameters. I have been using "nomodeset" for several years. This has been happening for about 2 weeks. See startx log below.
Has anyone else seen this problem?
we drop int10 everywhere and obsolete vesa and fbdev X drivers [1]
if is related please try 21.1.13-3 https://koji.fedoraproject.org/koji/buildinfo?buildID=2556149
also need to check if you got vesa and fbdev installed
What xorg driver is expected to be used now with nomodeset, if not vesa or fbdev?
I tried keep int10 etc , but the argument was that everything was replaced by modesetting and simpledrm and RHEL already removed int10
https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers#Detailed_Descript...
I have to admit I didn't quite understand this justification, since that change is from several releases ago and the scope says nothing about removing X.org drivers....
so I guess nomodeset option also should be remove from the kernel because now is useless , unless George or someone else show that still be useful , i.e. simpledrm doesn't replace it .
Well, I know it's still sometimes used if e.g. you have a very new NVIDIA card that the nouveau driver is confused by. Is there a different option that should now be used in such a case to force the use of simpledrm instead of a native driver?
On 10/13/24 4:33 PM, George R Goffe via test wrote:
Adam,
Thanks to you and Sergio for responding to my query... It's appreciated.
I have used nomodeset for so long I don't recall which driver I've been expecting to use.
My reason(s) for using nomodeset started several years ago... I think it was because of the turmoil related to driver updates. My main reason for using it now is that the font used by console output REALLY small and I have a hard time reading it.
https://wiki.archlinux.org/title/Linux_console section 3
I have tried using the ask boot parameter but it's a somewhat unwieldy interface to use and get the desired results.
From the Xorg.0.log file (below), it's not clear which driver is being selected.
It's using the generic modesetting driver. What graphics card do you have?
Samuel,
See this: link. https://discussion.fedoraproject.org/t/hwo-to-increase-the-size-of-tty-font/72945
I used this procedure when I could not find a way to get to a gui; it makes the console font legible even at very high monitor resolution.
Fred
On Sun, Oct 13, 2024 at 7:58 PM Samuel Sieb samuel@sieb.net wrote:
On 10/13/24 4:33 PM, George R Goffe via test wrote:
Adam,
Thanks to you and Sergio for responding to my query... It's appreciated.
I have used nomodeset for so long I don't recall which driver I've been
expecting to use.
My reason(s) for using nomodeset started several years ago... I think it
was because of the turmoil related to driver updates. My main reason for using it now is that the font used by console output REALLY small and I have a hard time reading it.
https://wiki.archlinux.org/title/Linux_console section 3
I have tried using the ask boot parameter but it's a somewhat unwieldy
interface to use and get the desired results.
From the Xorg.0.log file (below), it's not clear which driver is being
selected.
It's using the generic modesetting driver. What graphics card do you have?
-- _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Samuel Sieb composed on 2024-10-13 16:58 (UTC-0700):
George R Goffe wrote:
I have used nomodeset for so long I don't recall which driver I've been expecting to use.
My reason(s) for using nomodeset started several years ago... I think it was because of the turmoil related to driver updates. My main reason for using it now is that the font used by console output REALLY small and I have a hard time reading it.
I have tried using the ask boot parameter but it's a somewhat unwieldy interface to use and get the desired results.
From the Xorg.0.log file (below), it's not clear which driver is being selected.
It's using the generic modesetting driver. What graphics card do you have?
His log suggests to me Optimus: … [ 140.813] (II) modeset(0): using drv /dev/dri/card1 [ 140.813] (II) modeset(G0): using drv /dev/dri/card0 … [ 142.401] (II) modeset(0): [DRI2] DRI driver: crocus … [ 142.464] (II) modeset(G0): [DRI2] DRI driver: nouveau … IIRC, Crocus started with Haswell, ended with Skylake, so around 8-10 years old.
On 10/13/24 9:22 PM, Felix Miata wrote:
Samuel Sieb composed on 2024-10-13 16:58 (UTC-0700):
George R Goffe wrote:
I have used nomodeset for so long I don't recall which driver I've been expecting to use.
My reason(s) for using nomodeset started several years ago... I think it was because of the turmoil related to driver updates. My main reason for using it now is that the font used by console output REALLY small and I have a hard time reading it.
I have tried using the ask boot parameter but it's a somewhat unwieldy interface to use and get the desired results.
From the Xorg.0.log file (below), it's not clear which driver is being selected.
It's using the generic modesetting driver. What graphics card do you have?
His log suggests to me Optimus: … [ 140.813] (II) modeset(0): using drv /dev/dri/card1 [ 140.813] (II) modeset(G0): using drv /dev/dri/card0 … [ 142.401] (II) modeset(0): [DRI2] DRI driver: crocus … [ 142.464] (II) modeset(G0): [DRI2] DRI driver: nouveau … IIRC, Crocus started with Haswell, ended with Skylake, so around 8-10 years old.
Ah, I missed those lines. I also missed the earlier line: [ 141.854] (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) HD Graphics 3000 (SNB GT2)
George R Goffe composed on 2024-10-05 1:26 (UTC):
Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-6.12.0-0.rc0.20240927git075dbe9f6e3c.14.fc42.x86_64 root=UUID=6ef3dfc3-32ed-4f01 -bebb-64f66a016d37 ro resume=UUID=e3537362-f3a8-48f3-94e7-f7b4de63fe42 nomodeset vga 791 net.ifnames=0 biosdevname=0 audit=0 selinux=
Is space between vga and 791 instead of = something you've you're doing purposely? The result of its omission along with nomodeset I would expect to result in 80x25 on your vttys, or at least would have, before seeing Sérgio's thread reply.
-
Adam Williamson -
Felix Miata -
Frederick Bartlett -
George R Goffe -
Samuel Sieb -
Sérgio Basto