You are not logged in.
Hallo everyone,
Today I did solve one problem and here is just another one :-)
I updated my Arch/Linux kernel to 2.6.39.1 yesterday and ended up with [FAIL] status on [MODULES] during boot process.
So I checked rc.conf MODULES section and found nothing unusual.
I also rebuilded my mkinitcpio with SUCCESS status message, but I am still getting MODULES - FAIL status on boot, (but the boot process continues normally after a couple of seconds).
According to other posts here on Arch forums it may be some sort of bug or so.
Any fix/workaround to this?
Thanks for any help,
MTL,
Last edited by MatejLach (2011-06-23 17:03:48)
Offline
There has been an update which changes the way modules get loaded / blacklisted in rc.conf. Have you seen / tried the following?
Offline
According to other posts here on Arch forums it may be some sort of bug or so.
According to which posts? Show us the links so we can understand what the problem is. Also post your MODULES array.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
There has been an update which changes the way modules get loaded / blacklisted in rc.conf. Have you seen / tried the following?
Thanks!
I did not blacklisted modules in modprobe config.
But now I cannot see any MODULES section loading dunning boot.
Is this ok?
MatejLach wrote:According to other posts here on Arch forums it may be some sort of bug or so.
According to which posts? Show us the links so we can understand what the problem is. Also post your MODULES array.
I was unable to find the exact link again, that's why I did not included it in my first post.
(Sorry)
But it was something similar to this bug report.
Last edited by MatejLach (2011-06-23 15:06:36)
Offline
Do you use virtualbox? Because that has a module that needs to be handled seperately. I always forget to do it.
Offline
Inxsible wrote:MatejLach wrote:According to other posts here on Arch forums it may be some sort of bug or so.
According to which posts? Show us the links so we can understand what the problem is. Also post your MODULES array.
I was unable to find the exact link again, that's why I did not included it in my first post.
(Sorry)
But it was something similar to this bug report.
I don't see any similarities with what you are describing and that bug report. Are you using an EFI system? Are you using Grub2?
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Try this:
$ su -
# depmod -a
# shutdown -r now
You probably updated without having the full root argument, and that often seems to create problems with kernel (and other crucial) upgrades.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
MatejLach wrote:Inxsible wrote:According to which posts? Show us the links so we can understand what the problem is. Also post your MODULES array.
I was unable to find the exact link again, that's why I did not included it in my first post.
(Sorry)
But it was something similar to this bug report.I don't see any similarities with what you are describing and that bug report. Are you using an EFI system? Are you using Grub2?
Apologies,
My bad,
You're right, I provided wrong link, the correct one is this one, but my laptop will continue to boot normally after couple of seconds.
Here are my modules from rc.conf:
MODULES=(mii r8169 brcm80211 pcspkr snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-codec snd-hda-intel soundcore fuse)
I installed Arch just a couple of days ago and so I am sure that this is problem on my side.
I just don't know what I am doing wrong. :-)
Offline
Offline
brcm80211 no longer exists -- it's been renamed brcmsmac as of 2.6.39. Most of those modules will be found automatically.
That did the trick for me!
Thanks so much!
Next time I should just read Kernel Release Notes and I will be fine :-)
Offline