On Mon, Nov 3, 2025 at 4:20 PM Stephen Morris <[email protected]>
wrote:

> On Mon, Nov 3, 2025 at 8:53 AM Neal Becker <[email protected]> wrote:
>
>> I ran the usual dnf update today, but this time it brought problems.  I
>> rebooted (since it had some big updates to kde), but on reboot the
>> graphical mode showed the Fedora logo and the spinner, but then just
>> froze.  I was able to get to a tty.  At this point I'm just going to run
>> the F43 update which I hope will restore it.  This is the first time I've
>> seen an update cause such an issue.  I tried a quick look at journalctl in
>> tty mode, but didn't see anything interesting.
>>
>> Update to F43 worked and graphical mode is working again.  I had put off
> the update because I need xpra > 6, which is currently in updates-testing.
> I went ahead with the F43 update, which downgraded xpra, and then I removed
> xpra* and installed it from updates-testing.
>
> Hi Neal, I've just posted another thread where I'm reporting the same
> issue you have after I updated yesterday which also installed kernel
> 6.17.5, but using nvidia drivers I checked journalctl for nvidia messages
> and found a message that the nvidia module failed to load and it was
> falling back to nouveau. I don't understand what the issue is because
> booting into kernel 6.17.4, which was working, also gets the same issue.
> Under 6.17.4 I was able to issue ctrl+alt+F2 to get a console to login with
> where is issued startx which successfully loaded a Gnome desktop (I
> normally use KDE), hence the journalctl results. I'm going to try an akmods
> build of the nvidia driver again hoping it is that the module hasn't built
> properly rather than the module has lost its Secure Boot signature.
>
> The journalctl nvidia message was:
>
> Nov 04 07:17:20 fedora systemd[1]: nvidia-fallback.service - Fallback to
> nouveau as nvidia did not load was skipped because of an unmet condition
> check (ConditionPathExists=!/sys/module/nvidia)
>
> Without knowing exactly what the message means it looks to me like maybe a
> KDE module has been changed by mistake to verify that path doesn't exist
> rather than check that the path does exist (I would expect it to exist).
>
> regards,
>

Possibly related, but I'm using plain old intel graphics here.
-- 
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to