Author Topic: Debian Direct Load of Non-free Firmware? Also boot problem - SOLVED  (Read 2611 times)

Re: Debian Direct Load of Non-free Firmware? Also boot problem
« Reply #25 on: 28 December, 2020, 10:44:28 pm »
Last post for tonight!

Thanks for all the help so far.

I managed to capture the tail end of /var/log/syslog, which is reproduced here.

Looks like 21:42:02 was the point where the boot/start sequence which was hanging got interrupted by my pressing ALT+CTRL+F2 to start a new session. 

Just confirming the install was with a netinst CD of Buster 10.7, specifically tailored for i386.

Kim

  • Timelord
    • Fediverse
Re: Debian Direct Load of Non-free Firmware? Also boot problem
« Reply #26 on: 28 December, 2020, 10:52:03 pm »
The dhpc6 stuff before that is mostly harmless (unless you've got an IPv6 DHPC server on the network, in which case it shouldn't be timing out like that), but could something be blocking waiting for the network to come up?

Re: Debian Direct Load of Non-free Firmware? Also boot problem
« Reply #27 on: 29 December, 2020, 12:18:09 am »
I would suggest the issue is probably with GDM rather than the kernel ( what you’re getting with dmesg)

You should be able to see gdm logs with ‘systemctl status gdm’ or journalctl -U gdm

I also think Debian may now use wayland by default instead of X which is prone to issues on older hardware. It could be worth checking and switching to X11 if it is. There are some instructions here https://wiki.debian.org/GDM#Disabling_Wayland

Finally, you could also install something like lightdm instead of gdm and see if that works


Sent from my iPhone using Tapatalk

Re: Debian Direct Load of Non-free Firmware? Also boot problem
« Reply #28 on: 29 December, 2020, 12:41:58 pm »
I would suggest the issue is probably with GDM rather than the kernel ( what you’re getting with dmesg)

I also think Debian may now use wayland by default instead of X which is prone to issues on older hardware. It could be worth checking and switching to X11 if it is. There are some instructions here https://wiki.debian.org/GDM#Disabling_Wayland

You seem to have hit the nail on the head, jds!

I followed your suggestion and the link provided to disable Wayland, and the machine is now booting properly, also with access to ethernet! 

Re: Debian Direct Load of Non-free Firmware? Also boot problem - SOLVED
« Reply #29 on: 29 December, 2020, 01:13:50 pm »
I also wonder how old your PC is if it needs 32 bit rather than 64 bit Linux.
I'm running full 64 bit everything on four Thinkpads that are up to ten years old and until a few week sago a PC that I bought in 2006. You can run 64 bit Linux on Intel CPUs back to Core2duo.
I think you'll find it's a bit more complicated than that.

Re: Debian Direct Load of Non-free Firmware? Also boot problem - SOLVED
« Reply #30 on: 29 December, 2020, 01:44:20 pm »
I also wonder how old your PC is if it needs 32 bit rather than 64 bit Linux.
I'm running full 64 bit everything on four Thinkpads that are up to ten years old and until a few week sago a PC that I bought in 2006. You can run 64 bit Linux on Intel CPUs back to Core2duo.

Wikipedia suggests it can't be newer than 2003!  Pentium M.

Re: Debian Direct Load of Non-free Firmware? Also boot problem
« Reply #31 on: 29 December, 2020, 01:51:45 pm »
My Intel Atom 2009/2010 netbook is 32 bit and there aren't many 32 bit versions of Linux now. Although slightly later ones from 2010-2012 are 64 bit.

I would suggest the issue is probably with GDM rather than the kernel ( what you’re getting with dmesg)

I also think Debian may now use wayland by default instead of X which is prone to issues on older hardware. It could be worth checking and switching to X11 if it is. There are some instructions here https://wiki.debian.org/GDM#Disabling_Wayland

You seem to have hit the nail on the head, jds!

I followed your suggestion and the link provided to disable Wayland, and the machine is now booting properly, also with access to ethernet!

You would think that would be done automatically or at least display a message and offering an option to disable it instead of making people waste hours/days trying to sort it out.