Login loop problem - possibly a graphics problem

Support and Help
,
21

Leave GRUB alone - your bootloader is completely fine, and you already have a working shell.

Also do not look for logs in /var/logs. Ubuntu uses systemd journal, which stores binary logs in /var/log/journal.

To see the exact crash that kicked you back to the login screen, run:

journalctl -b -p 3 --no-pager

Test disabling Wayland: open /etc/gdm3/custom.conf, uncomment WaylandEnable=false, and reboot.

If Xorg lets you log in, that confirms the crash is specifically between Wayland and amdgpu.

1 Like
22

The OP is using Ubuntu 26.04 - Xorg packages are probably not present

2 Likes
23

My Bad, you’re right! :slight_smile:

That does not change the main point though: the journalctl command will show the exact crash reason without guessing.

1 Like
24

Since you are using the built-in graphics of your CPU and since the hardware side of this is managed by the BIOS, I’d definitely go for a BIOS upgrade… You seem to be pretty behind in versions…

1 Like
25

That really did do something!

The report was:

Sep 29 12:48:35 frank-B650-AORUS-ELITE-AX-V2 kernel: Bluetooth: hci1: No support for _PRR ACPI method
Sep 29 12:48:37 frank-B650-AORUS-ELITE-AX-V2 kernel: amdgpu 0000:10:00.0: probe with driver amdgpu failed with error -22
Sep 29 12:48:43 frank-B650-AORUS-ELITE-AX-V2 kernel: Bluetooth: hci0: Opcode 0x0c03 failed: -110
Sep 29 12:48:43 frank-B650-AORUS-ELITE-AX-V2 kernel: Bluetooth: hci2: Opcode 0x0c03 failed: -110
Sep 29 12:48:47 frank-B650-AORUS-ELITE-AX-V2 (generato[1717]: /usr/lib/systemd/system-generators/friendly-recovery failed with exit status 1.
Sep 29 12:48:59 frank-B650-AORUS-ELITE-AX-V2 gdm-autologin][2308]: gkr-pam: couldn’t unlock the login keyring.
Sep 29 12:57:22 frank-B650-AORUS-ELITE-AX-V2 (generato[6384]: /usr/lib/systemd/system-generators/friendly-recovery failed with exit status 1.
Sep 29 13:49:19 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled.

What I particularly noticed was the “Keyring” comment. That might be a sign of something, although the other warnings are also concerning to my unpracticed eye.

I am assuming this means that the problem is between Wayland and amdgpu.

1 Like
26

This is your actual error, the graphics driver can not properly be initialized (again, update your BIOS, that will likely help)…

The keyring message just means you would normally see a popup asking for your keyring password, it is not fatal.

1 Like
27

I bought the motherboard in November and that was the Bios it came with. I know that the Bios versions are often well behind the times. I have always been torn between the “Do/Don’t” brigades that are so active so often. I have had Internet denizens applying the frighteners.

Cheers for that. I believe that the latest is F42c, I trust that the ‘c’ is of no importance. One post I read claimed that the letter suffix was an indication of it being a pre-release candidate. Of course there is another army that says that is all a fairytale.

1 Like
28

The AMD AGESA microcode is what drives the hardware side of your graphics card in the BIOS so you might want to look for the BIOS with the latest version of that …

3 Likes
29

Error -22 is -EINVAL - amdgpu could not parse the VBIOS tables from the old firmware, so the driver never loaded.

Just checked Gigabyte’s BIOS naming: trailing lowercase letters (like F42c) are indeed beta builds. If you prefer a final stable release, pick the latest version without a letter. Either one will update AGESA and fix that -22 probe failure.

1 Like
30

Right! I am now downloading F42c to load in. The process seems quite straightforward, so I shouldn’t be breaking anything in the process.

1 Like
31

That is intersting. I see that the F41 Bios version includes:

  1. Update AMD AGESA 1.3.0.1

  2. AMD EXPO™ Technology: Featuring Ultra Low Latency support

However, Bios 42b has:

  1. Checksum: 25D0

  2. Updated AM5 AGESA 1.3.0.1b Patch A

  3. Optimized performance for AMD EXPO™ Technology: Featuring Ultra Low Latency

  4. Support for TSME (Transparent Secure Memory Encryption) on Ryzen 9000 Series processors

  5. Improve system security and stability

And Bios F42c has:

  1. Update AMD AGESA 1.3.0.1c

  2. Enhance CXSH (CXMT) chip-based memory compatibility

My problem is that the letter code indicates a beta version. Is it advisable that I install the latest (F42c), or the one with the patch (F42b) or the stable release (F41.)

I like the idea of having the new patch, but is a beta worth the risk? Then again, why not F42c, save for the fact it is the latest beta?

Sorry to take up so much of your time, but I am falling prey to lots of internet opinions that do not agree with anything anybody else posts.

32

Cheers! That helps quite a lot. I am suspicious of betas, but F42b seems to promise a new patch. is it worth the risk?

1 Like
33

41 is still far ahead of your current F31 so I’d first go with that one and see if it fixes the issue …

as you said yourself, the process of upgrading is straightforward, you can always move to the b version if the F41 one doesn’t fix it …

2 Likes
34

Agree with @ogra on F41.

That Patch A in 42b is specifically for Ryzen 9000 processors. Your CPU is Ryzen 7000 (Raphael), which is already fully supported by AGESA 1.3.0.1 in F41.

You are not missing out on anything by sticking with the stable F41 release.

35

Due to quite stormy weather at the moment I am hesitating to create another new user in stormy weather. Bad experiences with past computers makes me cautious. Hopefully later today, or tomorrow will clear up and I can test the user profiles again.

36

F41 it is then. I would rather not try a beta without compelling reasons

37

Right! I am going with the F41 Bios. Stormy weather here at the moment means I am delaying the upgrade. I might be cautious but there is a list of disasters with electronics in the past to justify it.

2 Likes
38

I think your log output has proven that it is a system level issue, so I don’t think the test user would help here anyway, just go with the BIOS update once you can, if there are still issues we can still come back to that approach later.

2 Likes
39

Sorry to be delayed, this is the first day I have seen sunlight since. There are still storm warnings, but I believe the worst is over. I admit that it is amusing to see unattended cars going on unscheduled cruises down main streets on the news. Many drivers complaining about the infrastructure when they have parked their cars on streets clearly marked “riera,” meaning “a small river.” We were all warned of heavy storms, but some of us thought that applied to everybody else.

In any case, I have changed the bios from F31 to F41 and it is still in a login loop, but it now asks me to sign in and then gives ma a black screen. When I first rebooted with the Bios, I had a “Secure Boot Violation,” which concerned me but I found a solution from Gigabyte.

I have added another user identity, and it works, in that it gives me a login page, but then reverts to a black screen as well.

I ran:

journalctl -u gdm -n 100 ls -la ~/.cache

and my result was this:

bash: /home/linuxbrew/.linuxbrew/bin/brew: No such file or directory

bash: /home/linuxbrew/.linuxbrew/bin/brew: No such file or directory

frank@frank-B650-AORUS-ELITE-AX-V2:~$ journalctl -u gdm -n 100

Oct 04 15:04:31 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -31724 was already dead.

Oct 04 15:04:31 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][32937]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:04:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -33157 was already dead.

Oct 04 15:04:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -33157 was already dead.

Oct 04 15:04:41 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][35636]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:04:53 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -35857 was already dead.

Oct 04 15:04:53 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -35857 was already dead.

Oct 04 15:04:31 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -31724 was already dead.

Oct 04 15:04:31 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][32937]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:04:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -33157 was already dead.

Oct 04 15:04:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -33157 was already dead.

Oct 04 15:04:41 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][35636]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:04:53 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -35857 was already dead.

Oct 04 15:04:53 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -35857 was already dead.

Oct 04 15:04:53 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][37721]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:03 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -37937 was already dead.

Oct 04 15:05:03 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -37937 was already dead.

Oct 04 15:05:03 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][39153]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:14 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -39384 was already dead.

Oct 04 15:05:14 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -39384 was already dead.

Oct 04 15:05:14 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][40762]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:25 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -40981 was already dead.

Oct 04 15:05:25 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -40981 was already dead.

Oct 04 15:05:25 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][43428]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:35 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -43671 was already dead.

Oct 04 15:05:35 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -43671 was already dead.

Oct 04 15:05:35 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][46137]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:37 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:37 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -46355 was already dead.

Oct 04 15:05:37 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:37 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -46355 was already dead.

Oct 04 15:05:37 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][46638]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:39 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:39 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -46831 was already dead.

Oct 04 15:05:39 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:39 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -46831 was already dead.

Oct 04 15:05:39 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][47110]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -47302 was already dead.

Oct 04 15:05:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -47302 was already dead.

Oct 04 15:05:41 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][47583]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:43 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:43 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -47776 was already dead.

Oct 04 15:05:43 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:43 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -47776 was already dead.

Oct 04 15:05:43 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][48051]: pam_unix(gdm-launch-environment:session)>

lines 5-40

Oct 04 15:04:31 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -31724 was already dead.

Oct 04 15:04:31 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][32937]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:04:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -33157 was already dead.

Oct 04 15:04:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -33157 was already dead.

Oct 04 15:04:41 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][35636]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:04:53 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -35857 was already dead.

Oct 04 15:04:53 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -35857 was already dead.

Oct 04 15:04:31 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -31724 was already dead.

Oct 04 15:04:31 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][32937]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:04:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -33157 was already dead.

Oct 04 15:04:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -33157 was already dead.

Oct 04 15:04:41 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][35636]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:04:53 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -35857 was already dead.

Oct 04 15:04:53 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -35857 was already dead.

Oct 04 15:04:53 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][37721]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:03 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -37937 was already dead.

Oct 04 15:05:03 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -37937 was already dead.

Oct 04 15:05:03 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][39153]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:14 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -39384 was already dead.

Oct 04 15:05:14 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -39384 was already dead.

Oct 04 15:05:14 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][40762]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:25 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -40981 was already dead.

Oct 04 15:05:25 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -40981 was already dead.

Oct 04 15:05:25 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][43428]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:35 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -43671 was already dead.

Oct 04 15:05:35 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -43671 was already dead.

Oct 04 15:05:35 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][46137]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:37 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:37 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -46355 was already dead.

Oct 04 15:05:37 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:37 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -46355 was already dead.

Oct 04 15:05:37 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][46638]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:39 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:39 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -46831 was already dead.

Oct 04 15:05:39 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:39 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -46831 was already dead.

Oct 04 15:05:39 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][47110]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -47302 was already dead.

Oct 04 15:05:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:41 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -47302 was already dead.

Oct 04 15:05:41 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][47583]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:43 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:43 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -47776 was already dead.

Oct 04 15:05:43 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:43 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -47776 was already dead.

Oct 04 15:05:43 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][48051]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:45 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:45 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -48250 was already dead.

Oct 04 15:05:45 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:45 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -48250 was already dead.

Oct 04 15:05:45 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][48548]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:05:47 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmDisplay: Session never registered, failing

Oct 04 15:05:47 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: GdmLocalDisplayFactory: maximum number of display failu>

Oct 04 15:05:47 frank-B650-AORUS-ELITE-AX-V2 gdm3[2021]: Gdm: Child process -48741 was already dead.

-- Boot ae458e91b4cf4d77a98db4de983bbf9b –

Oct 04 15:08:38 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: Starting gdm.service - GNOME Display Manager…

Oct 04 15:08:38 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: Started gdm.service - GNOME Display Manager.

Oct 04 15:08:48 frank-B650-AORUS-ELITE-AX-V2 gdm3[2980]: Gdm: It appears that your system does not have a primary GPU>

Oct 04 15:08:48 frank-B650-AORUS-ELITE-AX-V2 gdm-autologin][3155]: gkr-pam: no password is available for user

Oct 04 15:08:48 frank-B650-AORUS-ELITE-AX-V2 gdm-autologin][3155]: pam_unix(gdm-autologin:session): session opened fo>

Oct 04 15:08:49 frank-B650-AORUS-ELITE-AX-V2 gdm-autologin][3155]: gkr-pam: couldn’t unlock the login keyring.

Oct 04 15:27:55 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: Stopping gdm.service - GNOME Display Manager…

Oct 04 15:27:55 frank-B650-AORUS-ELITE-AX-V2 gdm3[2980]: Gdm: Failed to list cached users: GDBus.Error:org.freedeskto>

Oct 04 15:27:55 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAIL>

Oct 04 15:27:55 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: gdm.service: Failed with result ‘exit-code’.

Oct 04 15:27:55 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: Stopped gdm.service - GNOME Display Manager.

Oct 04 15:27:55 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: gdm.service: Triggering OnFailure= dependencies.

Oct 04 15:27:55 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: gdm.service: Failed to enqueue OnFailure=plymouth-quit.servi>

-- Boot 96e4eaee8e954dc58a5fc8b4369760a6 –

Oct 04 15:28:27 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: Starting gdm.service - GNOME Display Manager…

Oct 04 15:28:27 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: Started gdm.service - GNOME Display Manager.

Oct 04 15:28:27 frank-B650-AORUS-ELITE-AX-V2 gdm-autologin][2050]: gkr-pam: no password is available for user

Oct 04 15:28:27 frank-B650-AORUS-ELITE-AX-V2 gdm-autologin][2050]: pam_unix(gdm-autologin:session): session opened fo>

Oct 04 15:28:27 frank-B650-AORUS-ELITE-AX-V2 gdm-autologin][2050]: gkr-pam: couldn’t unlock the login keyring.

Oct 04 15:28:34 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][3776]: pam_unix(gdm-launch-environment:session):>

Oct 04 15:28:40 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -4027 was already dead.

Oct 04 15:28:40 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -4027 was already dead.

Oct 04 15:28:40 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][6275]: pam_unix(gdm-launch-environment:session):>

Oct 04 15:28:48 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -6473 was already dead.

Oct 04 15:28:48 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -6473 was already dead.

Oct 04 15:28:48 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][7797]: pam_unix(gdm-launch-environment:session):>

Oct 04 15:28:56 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -8013 was already dead.

Oct 04 15:28:56 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -8013 was already dead.

Oct 04 15:28:56 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][9325]: pam_unix(gdm-launch-environment:session):>

Oct 04 15:29:03 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -9522 was already dead.

Oct 04 15:29:03 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -9522 was already dead.

Oct 04 15:29:03 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][10738]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:29:09 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -10936 was already dead.

Oct 04 15:29:09 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -10936 was already dead.

Oct 04 15:29:09 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][12142]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:29:18 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -12358 was already dead.

Oct 04 15:29:18 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -12358 was already dead.

Oct 04 15:29:18 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][13839]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:29:26 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -14054 was already dead.

Oct 04 15:29:26 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -14054 was already dead.

Oct 04 15:29:26 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][15373]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:29:34 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -15589 was already dead.

Oct 04 15:29:34 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -15589 was already dead.

Oct 04 15:29:34 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][16914]: pam_unix(gdm-launch-environment:session)>

Oct 04 15:29:42 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -17129 was already dead.

Oct 04 15:29:42 frank-B650-AORUS-ELITE-AX-V2 gdm3[2042]: Gdm: Child process -17129 was already dead.

Oct 04 15:29:42 frank-B650-AORUS-ELITE-AX-V2 gdm-launch-environment][18455]: pam_unix(gdm-launch-environment:session)>

-- Boot 026137ce9b8a4eb1a791c6a0eb4912d3 –

Oct 04 15:34:39 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: Starting gdm.service - GNOME Display Manager…

Oct 04 15:34:39 frank-B650-AORUS-ELITE-AX-V2 systemd[1]: Started gdm.service - GNOME Display Manager.

Oct 04 15:34:49 frank-B650-AORUS-ELITE-AX-V2 gdm3[2180]: Gdm: It appears that your system does not have a primary GPU>

Oct 04 15:34:49 frank-B650-AORUS-ELITE-AX-V2 gdm-autologin][2351]: gkr-pam: no password is available for user

Oct 04 15:34:49 frank-B650-AORUS-ELITE-AX-V2 gdm-autologin][2351]: pam_unix(gdm-autologin:session): session opened fo>

Oct 04 15:34:50 frank-B650-AORUS-ELITE-AX-V2 gdm-autologin][2351]: gkr-pam: couldn’t unlock the login keyring.

lines 68-103/103 (END)

Which is a lot of information that has very little meaning for me, but at least it is a record of my boot attempts.

I also ran: journalctl -b -p 3 --no-pager again.

The result was:

frank@frank-B650-AORUS-ELITE-AX-V2:~$ journalctl -b -p 3 --no-pager
Oct 04 15:34:20 frank-B650-AORUS-ELITE-AX-V2 kernel: integrity: Problem loading X.509 certificate -22
Oct 04 15:34:20 frank-B650-AORUS-ELITE-AX-V2 kernel: integrity: Problem loading X.509 certificate -22
Oct 04 15:34:24 frank-B650-AORUS-ELITE-AX-V2 kernel: Bluetooth: hci0: No support for _PRR ACPI method
Oct 04 15:34:26 frank-B650-AORUS-ELITE-AX-V2 kernel: amdgpu 0000:10:00.0: probe with driver amdgpu failed with error -22
Oct 04 15:34:32 frank-B650-AORUS-ELITE-AX-V2 kernel: Bluetooth: hci1: Opcode 0x0c03 failed: -110
Oct 04 15:34:38 frank-B650-AORUS-ELITE-AX-V2 (generato[1765]: /usr/lib/systemd/system-generators/friendly-recovery failed with exit status 1.
Oct 04 15:34:50 frank-B650-AORUS-ELITE-AX-V2 gdm-autologin][2351]: gkr-pam: couldn’t unlock the login keyring.

Which is much shorter but with all red comments afterwards. Hopefully I have advanced a little closer to the solution

I did think that since I was able to get a working version to load after a “dpkg” run, that I would try it after it was loaded. I used https://www.progressiverobot.com/2026/08/01/ubuntu-26-04-lts-dpkg-interrupted-state-blocks-package-installs-fix-prevention/ to do what I could with “Dpkg.” It did load all of the previous packages that failed to update, but I saw no other changes in the system.

Again, many thanks for all of your help. It is very much appreciated and I am taking notes to avoid help with future problems.

40

EDITED:
My bad, missed the top line of your post! The F41 flash actually made progress.

Your Ryzen iGPU still choked on that same error -22.

The -p 3 flag in journalctl only shows the final fatal line, not the reason. Run this so we can see what actually tripped the driver:

sudo dmesg | grep -i -E "amdgpu|drm" | head -n 40

Also, check one quick thing in the BIOS:
under Settings - IO Ports - Integrated Graphics, if UMA Frame Buffer Size is set to Auto, bump it to 2G.

AFAIK Ryzen iGPUs hate when the motherboard feeds them dynamic memory crumbs.

1 Like