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?