Arch Linux

kolombo

Member

From: Ukraine

Registered: 2011-12-14

Posts: 31

[SOLVED] Not able to boot after upgrade to linux-3.5.3-1-i686

HI After recent upgrade my system was not able to boot.
It hungs on `Waiting for udev events`.

I have downgraded linux kernel to  3.4.7 and it works now, also doing that I removed virtualbox and virtualbox-modules.
Does anybody know what it could be ?

Last edited by kolombo (2012-09-27 18:05:59)

miko

Member

From: Poland

Registered: 2006-04-16

Posts: 49

Re: [SOLVED] Not able to boot after upgrade to linux-3.5.3-1-i686

Happened to me once today. I just rebooted and it passed that without problem. Is your problem persistent?

kolombo

Member

From: Ukraine

Registered: 2011-12-14

Posts: 31

Re: [SOLVED] Not able to boot after upgrade to linux-3.5.3-1-i686

Yes it is persistent

kolombo

Member

From: Ukraine

Registered: 2011-12-14

Posts: 31

Re: [SOLVED] Not able to boot after upgrade to linux-3.5.3-1-i686

Note: I'm using sysV and not systemd boot system.

I have found that my system is missing some files from sysvinit-tools package

 pacman -Qk sysvinit-tools
warning: sysvinit-tools: /bin/pidof (No such file or directory)
warning: sysvinit-tools: /sbin/bootlogd (No such file or directory)
warning: sysvinit-tools: /sbin/fstab-decode (No such file or directory)
warning: sysvinit-tools: /sbin/killall5 (No such file or directory)
warning: sysvinit-tools: /sbin/sulogin (No such file or directory)
warning: sysvinit-tools: /usr/bin/last (No such file or directory)
warning: sysvinit-tools: /usr/bin/lastb (No such file or directory)
warning: sysvinit-tools: /usr/bin/mesg (No such file or directory)
warning: sysvinit-tools: /usr/bin/utmpdump (No such file or directory)
warning: sysvinit-tools: /usr/bin/wall (No such file or directory)
warning: sysvinit-tools: /usr/include/initreq.h (No such file or directory)
warning: sysvinit-tools: /usr/share/man/man1/last.1.gz (No such file or directory)
warning: sysvinit-tools: /usr/share/man/man1/lastb.1.gz (No such file or directory)
warning: sysvinit-tools: /usr/share/man/man1/mesg.1.gz (No such file or directory)
warning: sysvinit-tools: /usr/share/man/man1/utmpdump.1.gz (No such file or directory)
warning: sysvinit-tools: /usr/share/man/man1/wall.1.gz (No such file or directory)
warning: sysvinit-tools: /usr/share/man/man8/bootlogd.8.gz (No such file or directory)
warning: sysvinit-tools: /usr/share/man/man8/fstab-decode.8.gz (No such file or directory)
warning: sysvinit-tools: /usr/share/man/man8/killall5.8.gz (No such file or directory)
warning: sysvinit-tools: /usr/share/man/man8/pidof.8.gz (No such file or directory)
warning: sysvinit-tools: /usr/share/man/man8/sulogin.8.gz (No such file or directory)
sysvinit-tools: 30 total files, 21 missing files

I fixed this and verified all installed packages for integrity.

I have next version of packages installed and everything works well.

 pacman -Q systemd sysvinit initscripts filesystem linux
systemd 189-4
sysvinit 2.88-7
initscripts 2012.08.3-2
filesystem 2012.8-1
linux 3.4.7-1

But right after linux update to 3.5.3-1 it stops to boot. No errors in logs, no logs at all.

So the question: What should I do next ? How to debug this ? Shoudl I file a bug ?

Last edited by kolombo (2012-09-05 18:49:25)

thujone

Member

From: Prague, Czech Republic

Registered: 2007-01-01

Posts: 18

Re: [SOLVED] Not able to boot after upgrade to linux-3.5.3-1-i686

Having the same problem still in 3.5.4, I managed to boot my system after disabling KMS (which is on by default).
Ex-post it was easy to find that 3.5 breaks KMS on Radeon.
If it's a different bug that's affecting you, though, I couldn't tell how to investigate, except for blindly shoot down modules one by one.

Last edited by thujone (2012-09-19 12:21:15)

kolombo

Member

From: Ukraine

Registered: 2011-12-14

Posts: 31

Re: [SOLVED] Not able to boot after upgrade to linux-3.5.3-1-i686

You were absolutely right
Thanks, I would never find that issue with my radeon card and KMS

Last edited by kolombo (2012-09-27 18:06:26)