LinuxQuestions.org - [SOLVED] Debian 10 behaving very glitchy

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Debian 10 behaving very glitchy (https://www.linuxquestions.org/questions/linux-newbie-8/debian-10-behaving-very-glitchy-4175718348/)

Debian 10 behaving very glitchy

I am running Debian 11 Bullseye with xfce4 desktop.
After booting when I press 'restart' the OS will restart but won't show the uefi motherboard screen or the grub screen.
There's simply a blank screen and eventually the OS will open the Debian 11 login page which will be displayed on the screen.

Secondly, if I press 'suspend' the OS will suspend but then immediately come back on again.
But if I suspend with the internet still active - then the OS will suspend correctly.

I've never had this problem before but I do have a new build.
Is it my motherboard or SSD or is it a Debian issue?

If the motherboard screen isn't shown on a restart is that a display screen issue? Or motherboard issue?

What do the logs show?

Code:

journalctl -b-1

should show detailed messages about your previous boot.

It could be the BIOS doesn't like to play nice with your display. Is there a motherboard BIOS upgrade available? Is fast boot enabled in BIOS? How old is your display? Older ones well may have electrolytic capacitors fading out of specification prematurely. Which type video cable are you using? Do you have a different type available to try?

Quote:

Originally Posted by JeremyBoden (Post 6389858)

What do the logs show?

Code:

journalctl -b-1

should show detailed messages about your previous boot.

There are over 2000 lines of code.
They are color coded.
These are the lines in red which seem to be error messages:

Code:

root@deb11:~# journalctl -b-1

deb11 kernel: kvm: disabled by bios

deb11 kernel: kvm: disabled by bios

deb11 kernel: kvm: disabled by bios

deb11 pipewire[759]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedes

deb11 kernel: kvm: disabled by bios

deb11 gsd-sharing[1024]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedeskt>

deb11 gsd-media-keys[1057]: Failed to grab accelerator for keybinding settings:rfkill

deb11 gdm-password][1269]: gkr-pam: unable to locate daemon control file

deb11 pipewire[1288]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freede>

deb11 light-locker[1722]: Environment variable XDG_SESSION_PATH not set. Is LightDM running?

deb11 pulseaudio[1289]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': tim>

deb11 gdm3[719]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing act>

deb11 kernel: watchdog: watchdog0: watchdog did not stop!

It says 'XDG_SESSION_PATH not set. Is LightDM running?'.
On installation I had to choose a display manager. I think it was between X Windows and Lightdm. I think I chose the first option: X Windows.

Quote:

Originally Posted by mrmazda (Post 6389920)

It could be the BIOS doesn't like to play nice with your display. Is there a motherboard BIOS upgrade available?

On completing this new build - the motherboard was upgraded by using a Ryzen 3000 so the mobo would initially come on. And then installing an upgrade via usb. After that the mobo would come on when the new Ryzen 5000 was installed.

Quote:

Is fast boot enabled in BIOS?

I haven't checked that yet.

Quote:

How old is your display? Older ones well may have electrolytic capacitors fading out of specification prematurely.

I think this might be the problem.
I'm using my 32" TV as the monitor. It's about 10 years old.

When I press 'restart' the OS shutsdown but the TV display is still running. So the motherboard and grub flashscreens can't be seen.
But if I switch off the plug socket which shutsdown the display (whilst the OS is already off) - then the motherboard and grub screens can be seen on boot.
I tested this further by pressing 'restart' when the OS was on and then turned the TV off and on again via the remote. It was slower to do this than the OS - so I was only able to see the grub screen.

So this means it's a hardware issue. My TV software needs upgrading. But the last software upgrade for my model was in 2012. So I'm not sure that helps.

Incidentally the 'suspend' button now works fine. It may have been the fact that I inadvertently moved the keyboard or mouse which would restart the OS.

I have an older Panasonic plasma TV (10+ years). It does not play well with some of my machines, others it works fine. Over the years I've tried using it on laptops and desktops using Linux (Mint, Ubuntu, Pop OS), Windows 10, Mac OS 11 and Chrome OS. I've found that regardless of the operating system used it just plays better with some hardware than it does with other. With an older TV I think the best advice is to accept that it might be quirky, but as long as it works for you, it's good enough for older equipment.

I would also like to ask if you have quiet boot enabled or disabled? I'm not as great with the specifics as quite a few of the members here are, but I know I've seen different options in the BIOS of computers for what information they show during initial boot.

Hope this helps.