boot stops before startx....

[François Patte]

Bonjour,

Yesterday I updated my fc40 installation. I have an nvidia GPU with 
nvidia driver from rpm-fusion.

I think that the akmod compilation of the driver went wrong and I could 
not boot until the graphical login screen: the screen remains black and 
nothing was possible to be done, even accessing to consol via 
ctrl-alt-F2-to-12.

So I booted in rescue mode and erased all nvidia stuff (except firmware) 
and modified the kernel line in grub (suppressing "blacklist nouveau")  
and rebooted.

Now, I can boot but not to graphical mode: at the end, I have to switch 
to consol (Ctrl-Alt F2), login and startx.

How can get a full boot upto graphical mode again?

Thank you.

[home user]

On 8/16/24 8:32 AM, François Patte wrote:
> Bonjour,
>
> Yesterday I updated my fc40 installation. I have an nvidia GPU with nvidia driver from rpm-fusion.
>
> I think that the akmod compilation of the driver went wrong and I could not boot until the graphical login screen: the screen remains black and nothing was possible to be done, even accessing to consol via ctrl-alt-F2-to-12.
>
> So I booted in rescue mode and erased all nvidia stuff (except firmware) and modified the kernel line in grub (suppressing "blacklist nouveau") and rebooted.
>
> Now, I can boot but not to graphical mode: at the end, I have to switch to consol (Ctrl-Alt F2), login and startx.
>
> How can get a full boot upto graphical mode again?
>
> Thank you.

I'm at f39 (workstation), and I use the rpm-fusion nvidia driver.  I did my weekly patches yesterday.  I noticed the kernel was updated, but there was no (a)kmod update.  The old driver does not compile with the new kernel.  On rebooting, the boot process fails back to the nouveau driver.  So I'm having to boot up with the older kernel.

I realize Francois and I are using different Fedora releases (39 vs. 40).  But I wonder if we both have the same problem: the kernel update got ahead of the rpm-fusion nvidia update.  This has happened to me several times in the past, and it has happened to other people as well.

Since I don't know what version of the rpm-fusion nvidia driver the new kernel wants, how can I know when the new driver is released?

Isn't dnf supposed to check dependencies before updating?  Why is dnf updating the kernel if the appropriate version of the rpm-fusion nvidia driver is not (yet?) available?

Bill.

[Patrick Dupre]

There are tools like
xrandr
which can help to query and setting the video 
After that, you need to check the video drivers fitting your hardware.

see also cvt

Good luck

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
===========================================================================
> Sent: Friday, August 16, 2024 at 4:32 PM
> From: "François Patte" 
> To: "Community support for Fedora users" 
> Subject: boot stops before startx....
>
> Bonjour,
>
> Yesterday I updated my fc40 installation. I have an nvidia GPU with 
> nvidia driver from rpm-fusion.
>
> I think that the akmod compilation of the driver went wrong and I could 
> not boot until the graphical login screen: the screen remains black and 
> nothing was possible to be done, even accessing to consol via 
> ctrl-alt-F2-to-12.
>
> So I booted in rescue mode and erased all nvidia stuff (except firmware) 
> and modified the kernel line in grub (suppressing "blacklist nouveau")  
> and rebooted.
>
> Now, I can boot but not to graphical mode: at the end, I have to switch 
> to consol (Ctrl-Alt F2), login and startx.
>
> How can get a full boot upto graphical mode again?
>
> Thank you.
>
> -- 
> François Patte
> UFR de mathématiques et informatique
> Laboratoire CNRS MAP5, UMR 8145
> Université Paris Descartes
> 45, rue des Saints Pères
> F-75270 Paris Cedex 06
> Tél. [phone]
> http://www.math-info.univ-paris5.fr/~patte
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Robert McBroom]

On 8/16/24 10:32 AM, François Patte wrote:
> Bonjour,
>
> Yesterday I updated my fc40 installation. I have an nvidia GPU with 
> nvidia driver from rpm-fusion.
>
> I think that the akmod compilation of the driver went wrong and I 
> could not boot until the graphical login screen: the screen remains 
> black and nothing was possible to be done, even accessing to consol 
> via ctrl-alt-F2-to-12.
>
> So I booted in rescue mode and erased all nvidia stuff (except 
> firmware) and modified the kernel line in grub (suppressing "blacklist 
> nouveau")  and rebooted.
>
> Now, I can boot but not to graphical mode: at the end, I have to 
> switch to consol (Ctrl-Alt F2), login and startx.

The 6.10.x kernels are not yet supported for nvidia. I keep three to 
four kernels on the system to be able to drop back to a working system. 
You are apparently now using the nouveau driver perhaps it is now 
agreeing with the display manager you are using.

systemctl status display-manager

will tell you what you have and if it is operating

[François Patte]

Le 2024-08-17 06:07, Robert McBroom via users a écrit :
> On 8/16/24 10:32 AM, François Patte wrote:
> > Bonjour,
> >
> > Yesterday I updated my fc40 installation. I have an nvidia GPU with 
> > nvidia driver from rpm-fusion.
> >
> > I think that the akmod compilation of the driver went wrong and I 
> > could not boot until the graphical login screen: the screen remains 
> > black and nothing was possible to be done, even accessing to consol 
> > via ctrl-alt-F2-to-12.
> >
> > So I booted in rescue mode and erased all nvidia stuff (except 
> > firmware) and modified the kernel line in grub (suppressing "blacklist 
> > nouveau")  and rebooted.
> >
> > Now, I can boot but not to graphical mode: at the end, I have to 
> > switch to consol (Ctrl-Alt F2), login and startx.
>
> The 6.10.x kernels are not yet supported for nvidia. I keep three to
> four kernels on the system to be able to drop back to a working
> system. You are apparently now using the nouveau driver perhaps it is
> now agreeing with the display manager you are using.
>
> systemctl status display-manager
>
> will tell you what you have and if it is operating

Ok! thank you. I could see that the display-manager  did not start, but 
the reason why is not obvious from the information given by 
systemctl....

Hi.

On Sun, 18 Aug 2024 14:59:09 +0200 François Patte wrote:
> Le 2024-08-17 06:07, Robert McBroom via users a écrit:
> > The 6.10.x kernels are not yet supported for nvidia.

I checked past friday with the 6.10.4-200.fc40 kernel and the 4
drivers provided by rpmfusion.

akmods succeded to compile:

kmod-nvidia-3:555.58.02-1.fc40.x86_64
    kmod-nvidia-340xx-1:340.108-32.fc40.x86_64

but failed on:

kmod-nvidia-470xx-3:470.256.02-1.fc40.x86_64
    kmod-nvidia-390xx-3:390.157-9.fc40.x86_64

A fix is coming for kmod-nvidia-470xx:

https://bugzilla.rpmfusion.org/show_bug.cgi?id=7020

nvidia-470xx-kmod-470.256.02-3.fc40
    https://koji.rpmfusion.org/koji/buildinfo?buildID=29683

currently in the rpmfusion-nonfree-updates-testing repo

kmod-nvidia-390xx is showing the same error than the 470xx one.
> > I keep three to four kernels on the system to be able to drop back to a
> > working system.

+1
> > You are apparently now using the nouveau driver perhaps it is
> > now agreeing with the display manager you are using.
> > systemctl status display-manager
> > will tell you what you have and if it is operating
> Ok! thank you. I could see that the display-manager  did not start, but 
> the reason why is not obvious from the information given by 
> systemctl....

Is it enabled ? Did it failed ?
Have you booted in graphical-target ? (runlevel 5)

You could try to reinstall the nvidia driver except if your card
needs the nvidia-390xx version, and enable the
rpmfusion-nonfree-updates-testing repo for the nvidia-470xx one

[François Patte]

Le 2024-08-18 16:05, [e-mail] a écrit :
> Hi.
>
> On Sun, 18 Aug 2024 14:59:09 +0200 François Patte wrote:
> > Le 2024-08-17 06:07, Robert McBroom via users a écrit:
> > > The 6.10.x kernels are not yet supported for nvidia.
>
> I checked past friday with the 6.10.4-200.fc40 kernel and the 4
> drivers provided by rpmfusion.
>
> akmods succeded to compile:
> kmod-nvidia-3:555.58.02-1.fc40.x86_64

This was the installed akmod-nvidia (for GeForce GTX 1050 Ti} and, for 
me, it failed to compile when upgrading the kernel to 
6.10.4-200.fc40.x86_64....

How can we be sure that a new kernel has the suitable stuff to compile 
kernel modules?
(before launching dnf upgrade, of course....)

Regards

[John Pilkington]

On 19/08/2024 09:51, François Patte wrote:
> Le 2024-08-18 16:05, [e-mail] a écrit :
> > Hi.
> >
> > On Sun, 18 Aug 2024 14:59:09 +0200 François Patte wrote:
> > > Le 2024-08-17 06:07, Robert McBroom via users a écrit:
> > > > The 6.10.x kernels are not yet supported for nvidia.
> >
> > I checked past friday with the 6.10.4-200.fc40 kernel and the 4
> > drivers provided by rpmfusion.
> >
> > akmods succeded to compile:
> >
> > kmod-nvidia-3:555.58.02-1.fc40.x86_64
>
> This was the installed akmod-nvidia (for GeForce GTX 1050 Ti} and, for 
> me, it failed to compile when upgrading the kernel to 
> 6.10.4-200.fc40.x86_64....
>
> How can we be sure that a new kernel has the suitable stuff to compile 
> kernel modules?
> (before launching dnf upgrade, of course....)
>
> Regards

I can't answer that, and I don't know how much our systems have in 
common.  But I have had no serious problems with almost daily 'dnf 
upgrade's since this post on 14 July, which named the packages being 
used.  That's on an old HP box, 470xx, KDE plasma-workspace-x11 and not 
using EFI.

https://lists.fedoraproject.org/archives/list/[e-mail]/th...

John P

[George N. White III]

On Mon, Aug 19, 2024 at 5:51 AM François Patte <
[e-mail]> wrote:
> How can we be sure that a new kernel has the suitable stuff to compile
> kernel modules?
> (before launching dnf upgrade, of course....)
>
> By watching the Fedora Forum and this list list.  I have an old iMac that

lacks an iGPU, so
when a new kernel appears I switch to nouveau so if dnf fails I don't get a
black screen.
The rpmfusion howto has a section on switching, which does require a
reboot.  You can
either edit the kernel command-line in the grub2 editor or edit
/etc/default/grub and then
run grub2-mkconfig -o /boot/grub2/grub.cfg.

PS: I avoid Nvidia as there are better ways to use my time, but the iMac
was discarded by
my wife when she moved to Apple silicon.

[François Patte]

Le 2024-08-19 14:54, George N. White III a écrit :
> On Mon, Aug 19, 2024 at 5:51 AM François Patte
>  wrote:
> > How can we be sure that a new kernel has the suitable stuff to
> > compile
> > kernel modules?
> > (before launching dnf upgrade, of course....)
>
> By watching the Fedora Forum and this list list.  I have an old iMac
> that lacks an iGPU, so
> when a new kernel appears I switch to nouveau so if dnf fails I don't
> get a black screen.
> The rpmfusion howto has a section on switching, which does require a
> reboot.  You can
>
> either edit the kernel command-line in the grub2 editor

and if you want to switch back to nvidia... it is not so easy...

moreover, if you have more than one monitor, what nvidia refers to as 
DVI-D-0 (for instance) is refered to DVI-D-1 by nouveau and if you have 
a script for, say, lightdm the graphical boot won't work...

F.P.

[Robert McBroom]

On 8/19/24 4:51 AM, François Patte wrote:
> Le 2024-08-18 16:05, [e-mail] a écrit :
> > Hi.
> >
> > On Sun, 18 Aug 2024 14:59:09 +0200 François Patte wrote:
> > > Le 2024-08-17 06:07, Robert McBroom via users a écrit:
> > > > The 6.10.x kernels are not yet supported for nvidia.
> >
> > I checked past friday with the 6.10.4-200.fc40 kernel and the 4
> > drivers provided by rpmfusion.
> >
> > akmods succeded to compile:
> >
> > kmod-nvidia-3:555.58.02-1.fc40.x86_64
>
> This was the installed akmod-nvidia (for GeForce GTX 1050 Ti} and, for 
> me, it failed to compile when upgrading the kernel to 
> 6.10.4-200.fc40.x86_64....
>
> How can we be sure that a new kernel has the suitable stuff to compile 
> kernel modules?
> (before launching dnf upgrade, of course....)

Assume a delay with NVIDIA drivers on kernel migration. The thing is to 
keep the working kernel and check https://bugzilla.rpmfusion.org until a 
report that a patch has been made.

[home user]

(general response)

I realize this isn't my thread, and the symptoms I experience are partially different from those that Francois is experiencing.  But there is overlap.

I thank everyone who tried to help.  The helpful posts were:
* Robert's: confirmed that the 6.10.x kernels are not yet supported for nvidia.  To keep this short, I'll just say I can only keep one old kernel and not go into the details.  But Robert's confirmation of my suspicion is appreciated.
* Francis's: I now know to watch for nvidia-470xx-kmod-470.256.02-3.fc39.  I hope I understood correctly.  Thank-you.

I agree with Francois's question:
"How can we be sure that a new kernel has the suitable stuff to compile kernel modules?
(before launching dnf upgrade, of course....)"
Once the "dnf upgrade" is done, it's too late; I'm stuck with a very difficult to use kernel+driver.

Robert's comment:
"Assume a delay with NVIDIA drivers on kernel migration. The thing is to keep the working kernel and check https://bugzilla.rpmfusion.org until a report that a patch has been made."
The first sentence makes sense.  The problem is I don't know that the kernel is going to update until it's too late: when I run the "dnf upgrade".

On 8/16/24 9:22 AM, home user via users wrote:
> On 8/16/24 8:32 AM, François Patte wrote:
> > Bonjour,
> >
> > Yesterday I updated my fc40 installation. I have an nvidia GPU with nvidia driver from rpm-fusion.
> >
> > I think that the akmod compilation of the driver went wrong and I could not boot until the graphical login screen: the screen remains black and nothing was possible to be done, even accessing to consol via ctrl-alt-F2-to-12.
> >
> > So I booted in rescue mode and erased all nvidia stuff (except firmware) and modified the kernel line in grub (suppressing "blacklist nouveau") and rebooted.
> >
> > Now, I can boot but not to graphical mode: at the end, I have to switch to consol (Ctrl-Alt F2), login and startx.
> >
> > How can get a full boot upto graphical mode again?
> >
> > Thank you.
>
> I'm at f39 (workstation), and I use the rpm-fusion nvidia driver.  I did my weekly patches yesterday.  I noticed the kernel was updated, but there was no (a)kmod update.  The old driver does not compile with the new kernel.  On rebooting, the boot process fails back to the nouveau driver.  So I'm having to boot up with the older kernel.
>
> I realize Francois and I are using different Fedora releases (39 vs. 40).  But I wonder if we both have the same problem: the kernel update got ahead of the rpm-fusion nvidia update.  This has happened to me several times in the past, and it has happened to other people as well.
>
> Since I don't know what version of the rpm-fusion nvidia driver the new kernel wants, how can I know when the new driver is released?
>
> Isn't dnf supposed to check dependencies before updating?  Why is dnf updating the kernel if the appropriate version of the rpm-fusion nvidia driver is not (yet?) available?
>
> Bill.

Hi.

On Wed, 21 Aug 2024 19:58:11 -0600 home user via users wrote:
> The problem is I don't know that the kernel is going to update until it's
> too late: when I run the "dnf upgrade".

I always do first a "dnf check-update", then if I agree:

nohup dnf -y update &

(a systemd-run will be even better/safer than nohup)

[Tim]

home user:
> > The problem is I don't know that the kernel is going to update until it's
> > too late: when I run the "dnf upgrade".

Francis:
> I always do first a "dnf check-update", then if I agree:
>
> nohup dnf -y update &
>
> (a systemd-run will be even better/safer than nohup)

I *never* do a dnf -y.  I always let it give me a list of things to do,
read it, then press y (for yes).  Firstly, I never develop the habit of
blindly doing dnf without checking.  And, secondly, I don't have to
worry that something may change between doing a check then an update.

I'm a bit surprised that an old nvidia package doesn't flag some sort
of warning about a too-new kernel for it.

[Barry Scott]

> On 22 Aug 2024, at 02:58, home user via users  wrote:
>
> I'll just say I can only keep one old kernel and not go into the details.

FYI: dnf update will never remove the kernel that you are currently running.

Barry

[home user]

On 8/22/24 3:53 AM, Barry Scott wrote:
> > On 22 Aug 2024, at 02:58, home user via users  wrote:
> >
> > I'll just say I can only keep one old kernel and not go into the details.
>
> FYI: dnf update will never remove the kernel that you are currently running.
>
> Barry

(not replying specifically to Barry)

I currently have two kernels on this f39 workstation:
* 6.9.12, and
* 6.10.4.
I do not have space for another.
If I understand things correctly, the rpmfusion nvidia package that I need for 6.10.xx is now available.
My lesser question: Am I correct?

If the answer to the lesser question is "yes", then here's my greater question:
Should I:
A. boot into 6.9.12, and then do the "dnf upgrade";
B. boot into 6.10.4, and then do the "dnf upgrade"; or
C. something else (what?)?

thanks,
Bill.

[John Pilkington]

On 22/08/2024 19:52, home user via users wrote:
> On 8/22/24 3:53 AM, Barry Scott wrote:
> > > On 22 Aug 2024, at 02:58, home user via users 
> > >  wrote:
> > >
> > > I'll just say I can only keep one old kernel and not go into the 
> > > details.
> >
> > FYI: dnf update will never remove the kernel that you are currently 
> > running.
> >
> > Barry
>
> (not replying specifically to Barry)
>
> I currently have two kernels on this f39 workstation:
> 6.9.12, and
> 6.10.4.
>
> I do not have space for another.
> If I understand things correctly, the rpmfusion nvidia package that I 
> need for 6.10.xx is now available.
> My lesser question: Am I correct?
>
> If the answer to the lesser question is "yes", then here's my greater 
> question:
> Should I:
> A. boot into 6.9.12, and then do the "dnf upgrade";
> B. boot into 6.10.4, and then do the "dnf upgrade"; or
> C. something else (what?)?
>
> thanks,
> Bill.

My f40 box is at present off, but runs 6.10.5 with 470xx.  That is from 
the rpmfusion-nonfree-updates testing repo.  So you need to enable that 
repo for f39.  If you can then boot and run dnf in an x11 desktop, 
either of your suggestions ought to work, leaving you with the running 
kernel and the installed update.

After that, ensure that the akmods build process has completed before 
rebooting.
  L

John P

[home user]

On 8/22/24 1:30 PM, John Pilkington wrote:
> On 22/08/2024 19:52, home user via users wrote:
> > On 8/22/24 3:53 AM, Barry Scott wrote:
> > > > On 22 Aug 2024, at 02:58, home user via users  wrote:
> > > >
> > > > I'll just say I can only keep one old kernel and not go into the details.
> > >
> > > FYI: dnf update will never remove the kernel that you are currently running.
> > >
> > > Barry
> >
> > (not replying specifically to Barry)
> >
> > I currently have two kernels on this f39 workstation:
> > 6.9.12, and
> > 6.10.4.
> >
> > I do not have space for another.
> > If I understand things correctly, the rpmfusion nvidia package that I need for 6.10.xx is now available.
> > My lesser question: Am I correct?
> >
> > If the answer to the lesser question is "yes", then here's my greater question:
> > Should I:
> > A. boot into 6.9.12, and then do the "dnf upgrade";
> > B. boot into 6.10.4, and then do the "dnf upgrade"; or
> > C. something else (what?)?
> >
> > thanks,
> > Bill.
>
> My f40 box is at present off, but runs 6.10.5 with 470xx.  That is from the rpmfusion-nonfree-updates testing repo.  So you need to enable that repo for f39.  If you can then boot and run dnf in an x11 desktop, either of your suggestions ought to work, leaving you with the running kernel and the installed update.
>
> After that, ensure that the akmods build process has completed before rebooting.
>   L

Barry's comment made me more comfortable doing the upgrade from the older kernel, so it would not be deleted.  The upgrade worked.  Thank-you John.  By the way, no need for the testing repo.

I can't speak for Francois, but for me the issue is solved.

Bill.

[George N. White III]

On Fri, Aug 23, 2024 at 12:09 AM home user via users <
[e-mail]> wrote:
> Barry's comment made me more comfortable doing the upgrade from the older
> kernel, so it would

not be deleted.  The upgrade worked.  Thank-you John.  By the way, no need
> for the testing repo.

I think the testing was succesful, so the fix is now provided in regular
updates.
> I can't speak for Francois, but for me the issue is solved.
>
> And you have gained some insight into the measures Fedora uses to avoid

breaking
systems when updates fail.