[SOLVED]Kernel 2.6.32 bootup problem

schen · 2009-12-30 23:59:05

After upgrading to kernel 2.6.32, I have a couple of problems, mainly dealing with the bootup. Sometimes when I boot up, it works without a problem. However, during other times, between bootup finishing and SLiM starting, a blank screen appears. It stays that way until I perform a hard shutdown, when on reboot, a fsck is required to fix the filesystem. I am using ext4 with no KMS and splashy, although the problem stayed when splashy was gone. It happens almost every 4 reboots. Also, I had none of these problems with 2.6.31.

Last edited by schen (2010-01-04 22:52:23)

Wintervenom · 2009-12-31 00:41:05

If you are using ath5k, by any chance, perhaps it could be one of these issues?
http://kerneltrap.org/mailarchive/linux … 21/6657963
http://bbs.archlinux.org/viewtopic.php?id=81930

Last edited by Wintervenom (2009-12-31 01:19:54)

schen · 2009-12-31 00:46:57

I didn't say I had a wireless problem, I said I had a bootup problem. I am also not using ath5k.

ulukai · 2009-12-31 08:41:18

What's the last daemon that loads before the blank screen appears?
Can you find anything related in your system logs or dmesg?
Would it be an option to try enabling KMS? Which video driver are you using?

schen · 2009-12-31 14:31:48

Most of my daemons are backgrounded, but here is the order.

DAEMONS=(syslog-ng @acpid @hal @cups @netfs @crond @alsa @wicd)

I can't really find anything interesting in my logs. But I just found out I WAS using ath5k, but with no wireless problems.

I am booting straight into X, but it makes no difference if I put slim as a daemon either.

Last edited by schen (2009-12-31 14:36:13)

schen · 2009-12-31 15:59:11

Just to clarify, I meant that the entire screen was off when I said "blank"

R00KIE · 2009-12-31 23:17:08

You should make sure hal starts before many other things, wicd is one of them, try not to background hal, maybe something like this:

DAEMONS=(syslog-ng hal @acpid @cups @netfs @crond @alsa @wicd)

Also, just to to test, add nomodeset to your kernel line, but make _one_ change at a time, otherwise if one of them works you will know which one worked.

schen · 2010-01-04 00:32:46

It seems that an error in rc.local started this problem. I removed plymouth and there was an extra line I forgot to take out.

tavianator · 2010-01-04 00:59:18

Glad you fixed it. Please mark this thread as [SOLVED].

Arch Linux

#1 2009-12-30 23:59:05

[SOLVED]Kernel 2.6.32 bootup problem

#2 2009-12-31 00:41:05

Re: [SOLVED]Kernel 2.6.32 bootup problem

#3 2009-12-31 00:46:57

Re: [SOLVED]Kernel 2.6.32 bootup problem

#4 2009-12-31 08:41:18

Re: [SOLVED]Kernel 2.6.32 bootup problem

#5 2009-12-31 14:31:48

Re: [SOLVED]Kernel 2.6.32 bootup problem

#6 2009-12-31 15:59:11

Re: [SOLVED]Kernel 2.6.32 bootup problem

#7 2009-12-31 23:17:08

Re: [SOLVED]Kernel 2.6.32 bootup problem

#8 2010-01-04 00:32:46

Re: [SOLVED]Kernel 2.6.32 bootup problem

#9 2010-01-04 00:59:18

Re: [SOLVED]Kernel 2.6.32 bootup problem

Board footer