You are not logged in.
After upgrading to default x86_64 kernel 2.6.31-ARCH with no error messages, I get this during reboot:
"Could not load /lib/modules/2.6.30-ARCH/modules.dep"
Well, no wonder, as there is no 2.6.30-ARCH directory, only 2.6.31-ARCH. I have tried "mkinitcpio -p kernel26", but it didn't help any (naturally).
Is there an easy fix for this?
Last edited by whaler (2009-10-18 22:15:46)
Offline
sudo depmod -a
They say that if you play a Win cd backward you hear satanic messages. That's nothing! 'cause if you play it forwards, it installs windows.
Offline
Thanks, but the system thinks it is still at 2.6.30-ARCH (uname -r), so that command cannot find directory 2.6.31-ARCH either. I tried specifying the new directory with depmod's -C option, but after a while depmod exited with a "FATAL".
Strange that the new kernel does not look for itself...
Could I uninstall and then reinstall the kernel within itself (no Internet connection)? If so, what would the commands be?
Offline
OK, I used 'pacman -U' and rolled back to v2.6.30 and everything seems fine again.
BTW, I first tried to reinstall v2.6.31, but with the same unworkable result as before. I am using the 'radeonhd' video driver and notice it is not mentioned in the ATI wiki with regard to the new KMS functionality in the 31 kernel. Anyway - the latest kernel is broken on my system.
CPU - Intel Core i7
M/B - ASUS P6T Deluxe V2
Videocard - MSI Radeon HD4850 / RV770
Offline
You need to reboot after updating the kernel.
Offline
I always reboot after a kernel upgrade, and did mention the reboot in my first message...
However, I did not try a _cold restart. Is it probable that would make a difference?
Offline
What dates are vmlinuz and kernel26.img?
I'm also wondering how complex your setup is e.g. is your /boot separate, is it full, is it the same one grub/lilo is using, have you renamed the 2.6.30 vmlinuz to something like vmlinuz-2.6.30?
Offline
whaler - apologies. I should make sure I'm fully awake before posting.
Offline
I've got the same error after kernel upgrade to the latest 2.6.31.3. I have a separate /boot partition with a plenty of spare space. So I had to boot with my arch livecd in order to downgrade to 2.6.30.
Offline
What dates are vmlinuz and kernel26.img?
I'm also wondering how complex your setup is e.g. is your /boot separate, is it full, is it the same one grub/lilo is using, have you renamed the 2.6.30 vmlinuz to something like vmlinuz-2.6.30?
My set up is rather 'vanilla'...
I have a separate boot partition with GRUB, with plenty of extra room.
I have not renamed the 2.6.30 vmlinuz or any other file/directory on the root partition.
*After* the borked install I placed an extra parameter after the kernel append sentence in GRUB, as per the ATI wiki, even though I use 'radeonhd', not 'radeon'. I then ran 'mkinitcpio -p kernel26' a second time and rebooted. No change.
I then rolled back to 2.6.30 and everything is running as normal. There are a few issues, with an external harddisk, the pcspeaker etc., but I consider them minor and they have not caused problems with previous kernel installations. Since I have never even compiled a kernel, I can't begin to guess what is wrong...
Offline
whaler - apologies. I should make sure I'm fully awake before posting.
(Almost) any attention is better than none
Offline
A few days have passed and I noticed a new build of the default kernel - kernel26-2.6.31.4-1.
As before, it appeared to install without any errors, but upon reboot I get the same (console) error messages as with build 3:
quote
FATAL: Could not load /lib/modules/2.6.30-ARCH/modules.dep: No such file or
directory
::Mounting Local Filesystems
mount: unknown filesystem type "jfs"
::Configuring System Clock
Cannot access the Hardware Clock via any known method. Use the --debug option
to see the details of our search for an access method
::Starting Network
eth1: unknown interface: No such device
dhcpcd: eth1: interface not found or invalid
::Restoring ALSA levels
/usr/sbin/alsactl: load_state: 1608: No soundcards found
unquote
Rolling back to kernel 2.6.30 fixes usability of the system for now, but some day one or more vital dependency will break.
This is a relatively fresh install of the August Arch x86_64. The installation went smoothly, upgrading to the latest 2.6.30 kernel went smoothly, but the 2 latest 2.6.31 kernels bork the system almost completely. I really hope the devs are reading this forum.
Last edited by whaler (2009-10-17 23:05:48)
Offline
*After* the borked install I placed an extra parameter after the kernel append sentence in GRUB, as per the ATI wiki, even though I use 'radeonhd', not 'radeon'. I then ran 'mkinitcpio -p kernel26' a second time and rebooted. No change.
What do you mean "in GRUB". Did you edit your grub configuration and/or edit the command line during boot? Are these the same?
Offline
I had the same problem. As it turned out, /boot was not mounted during kernel installation.
The fix, for me, was:
- boot in the broken system
- uncomment /boot in fstab (mount /boot didn't work. it didn't recognize ext3 and mounting as ext2 didn't work)
- reinstall the 2.6.30 kernel with `pacman -U /var/pacman/cache..`, this made sure early and late userspace used the 'boot' directory on '/'
- reboot : gives a working system with 2.6.30
- uncomment /boot in fstab, mount it and install 2.6.31
- reboot: all was fine again
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
What do you mean "in GRUB". Did you edit your grub configuration and/or edit the command line during boot? Are these the same?
I am referring to editing GRUB, as in its menu.lst, as per the ATI.wiki. I did not issue anything (extra) from the command line.
Offline
I had the same problem. As it turned out, /boot was not mounted during kernel installation.
The fix, for me, was: ( ... )
Thanks a lot, Dieter!
I had 2.6.30 running and tried first to go directly to 2.6.31...
However, following your instructions precisely, everything went as smooth as can be. I guess I should leave the /boot partition uncommented in fstab in the future? Or should I comment it again and just remember your fix procedure?
There is one downside to the new KMS functionality in the 2.6.31 kernel: graphic rendering is *CONSIDERABLY* slower. Also, MPlayer/SMplayer no longer works - at least not for wma-files. It's 1996 all over again... I am using "radeonhd", which may be part of the reason, and will experiment a little with the settings suggested in the ATI.wiki (which does not mention "radeonhd" at all...)
Guess I should make a separate thread for this.
Last edited by whaler (2009-10-18 21:13:10)
Offline
Dieter@be wrote:I had the same problem. As it turned out, /boot was not mounted during kernel installation.
The fix, for me, was: ( ... )Thanks a lot, Dieter!
I had 2.6.30 running and tried first to go directly to 2.6.31...
However, following your instructions precisely, everything went as smooth as can be. I guess I should leave the /boot partition uncommented in fstab in the future? Or should I comment it again and just remember your fix procedure?
Yes, if you have a separate filesystem for /boot, you should leave it uncommented in fstab and mounted when you install a new kernel (watch out with the 'noauto' mount option). during package installation it will show a warning if you have /boot not mounted but I guess we both overlooked it.
It is remarkable however, I don't remember ever having an issue like this, do you? It looks to me like something changed, I looked at the sources for kernel26 but couldn't find anything special.
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
Yes, if you have a separate filesystem for /boot, you should leave it uncommented in fstab and mounted when you install a new kernel (watch out with the 'noauto' mount option). during package installation it will show a warning if you have /boot not mounted but I guess we both overlooked it.
It is not so surprising if I overlooked it... However, I cannot recall seeing such a warning? I am in the habit of copying both pacman's package install msgs and boot console msgs, but I don't think I have ever seen a warning about the /boot partition not being mounted.
It is remarkable however, I don't remember ever having an issue like this, do you? It looks to me like something changed, I looked at the sources for kernel26 but couldn't find anything special.
During the 18 months I have used Arch I have received a faulty kernel twice. On both occasions the problem was another than this /boot partition issue. I have never had the /boot partition uncommented in fstab while using Arch, so something must have changed, or there is a new bug in the kernel code somewhere. It is significant that this only appears with the 2.6.31 kernel.
I have EXT3 on my boot partition, and I use this ending in fstab "defaults 0 1". Is it safe?
BTW - with "vga=773 nomodeset" in GRUB, graphics, incl. MPlayer etc., seem to be back to normal - in fact better than before, as I am now getting full repaints in OOo Calc! Of course, since I am not into gaming, I don't know if there is some other functionality missing...
Thanks again, Dieter - I will mark this thread solved!
Offline
I have the same problem.
Fresh install; pacman -Syu and now kernel 2.6.31 cannot find "modules.dep"
Solution didn't work, because I have everything on one partition.
Offline