Hi,
I am on a fresh install of Debian 12 with kernel 6.5 from Debian backports. Sometimes when I boot the machine, the graphical login prompt does not appear. The screen goes black and the monitor goes into sleep because of no signal. My gfx card is a Radeon RX6600. I need kernel 6.5 for my USB WIFI stick to work. So now I can chose between a system without Internet (Kernel 6.1) and one that sometimes does not boot up properly (kernel 6.5).![;)]( "Wink")
The CPU has integrated gfx and I tried disabling that in the BIOS but it does not solve the problem.
How can I debug this further. So far what I have is following logs:
I am on a fresh install of Debian 12 with kernel 6.5 from Debian backports. Sometimes when I boot the machine, the graphical login prompt does not appear. The screen goes black and the monitor goes into sleep because of no signal. My gfx card is a Radeon RX6600. I need kernel 6.5 for my USB WIFI stick to work. So now I can chose between a system without Internet (Kernel 6.1) and one that sometimes does not boot up properly (kernel 6.5).
The CPU has integrated gfx and I tried disabling that in the BIOS but it does not solve the problem.
How can I debug this further. So far what I have is following logs:
Code:
journalctl -u gdm --since "1 hour ago"First a failed boot, then a good one:-- Boot bc941149a87b456c9bb01bd2a3957bf2 --Mar 02 16:30:24 debian systemd[1]: Starting gdm.service - GNOME Display Manager...Mar 02 16:30:24 debian systemd[1]: Started gdm.service - GNOME Display Manager.Mar 02 16:30:24 debian gdm-launch-environment][981]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=112) by (uid=0)Mar 02 16:30:24 debian gdm-launch-environment][981]: pam_unix(gdm-launch-environment:session): session closed for user Debian-gdmMar 02 16:30:24 debian gdm-launch-environment][981]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failedMar 02 16:30:24 debian gdm3[964]: Gdm: GdmDisplay: Session never registered, failingMar 02 16:30:24 debian gdm3[964]: Gdm: Child process -1069 was already dead.Mar 02 16:30:24 debian gdm3[964]: Gdm: GdmDisplay: Session never registered, failingMar 02 16:30:24 debian gdm3[964]: Gdm: Child process -1069 was already dead.Mar 02 16:30:24 debian gdm-launch-environment][1446]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=112) by (uid=0)-- Boot 55f4a77fe6ec43c6bbdedfa0c431d993 --Mar 02 16:31:22 debian systemd[1]: Starting gdm.service - GNOME Display Manager...Mar 02 16:31:22 debian systemd[1]: Started gdm.service - GNOME Display Manager.Mar 02 16:31:22 debian gdm-launch-environment][1023]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=112) by (uid=0)Mar 02 16:31:30 debian gdm-password][2776]: gkr-pam: unable to locate daemon control fileMar 02 16:31:30 debian gdm-password][2776]: gkr-pam: stashed password to try later in open sessionMar 02 16:31:30 debian gdm-password][2776]: pam_unix(gdm-password:session): session opened for user puck(uid=1000) by (uid=0)Mar 02 16:31:30 debian gdm-password][2776]: gkr-pam: unlocked login keyringMar 02 16:31:33 debian gdm3[1004]: Gdm: Child process -1120 was already dead.Statistics: Posted by mrspuck — 2024-03-05 18:59 — Replies 0 — Views 59