No kernel modules found for Linux 2.6.27.7-smp.
I try to configure Slackware 12.2 with original kernel 2.6.27.7-smp but for some reason I can't boot the system using generic kernel and initrd.
First I build in /boot directory initrd with the command: Code:
mkinitrd -c -k vmlinuz-generic-smp-2.6.27.7-smp -m reiserfs Code:
image = /boot/vmlinuz-generic-smp-2.6.27.7-smp Everything seems to be good. I did full installation of Slackware 12.2 including kernel sources and modules. New system is on /dev/sda1 device and uses ReiserFS. I prepared appropriate intrd and LILO configuration. After reboot I select linux.generic kernel and boot procedures stop at the message: Code:
Freeing unused kernel memory: 328k freed Any help will be appreciated. *** Just in case I attach a few additional information... $ ls -l /boot/ Code:
total 19333 Code:
boot = /dev/sda1 Code:
/dev/sda8 swap swap defaults 0 0 Code:
2.6.27.7 2.6.27.7-smp Code:
total 1 |
The only thing I can think of is that mkinitrd command, you only need 2.6.27.7-smp, without the vmlinuz-generic-smp part.
Code:
mkinitrd -c -k 2.6.27.7-smp -m reiserfs -r /dev/sda1 |
The 12.1 README.mkinitrd file was much better than the current one regarding the initrd examples.
The example given on the 12.2 one never worked for me. |
w1k0,
I fiddled a bit with the same issue, and what I think fixed it was editing the file "/boot/initrd-tree/rootdev", changing the text to (in my case) "/dev/hda1", then run the command "mkinitrd" (without anything else) and finally re-run lilo. There is also an upgraded package of mkinitrd available since some days back. You might want to upgrade and try all over again. |
I started from the beginning and I shortened mkinitrd command:
Code:
mkinitrd -c -k 2.6.27.7-smp -m reiserfs Code:
Freeing unused kernel memory: 328k freed I suppose jannekrille has right. In rootdev file there is inscription: Code:
/dev/root Code:
/dev/sda1 I write now from Slackware 12.1. I can't chroot to /mnt/sda1 directory. # chroot /mnt/sda1 Code:
chroot: cannot run command `/bin/bash': Permission denied Other commands produce similar messages: # chroot /mnt/sda1 /bin/pwd Code:
chroot: cannot run command `/bin/pwd': Permission denied And now I go to Slackware 12.2 to check jannekrille's hint... |
Thank you, jannekrille. Handshake if you're boy or kiss if you're girl. Your choice...
*** So I ask once again my second question: why the command chroot /mnt/sda1 produces message: Code:
chroot: cannot run command `/bin/bash': Permission denied (I'm trying to chroot from Slackware 12.1 to Slackware 12.2.) |
FYI, problems with mkinitrd initially shipped with 12.2 release are now fixed, see:
http://slackware.com/changelog/stable.php?cpu=i386 so install the new version and you'll be happy. |
When I install and configure new system I don't establish Internet connections from it. At the end of the configuration I backup the system and then connect to Internet for the first time to check if there are some new patches. I want to be completely sure that my backup isn't compromised. It's my paranoid method of installing and configuring the system.
It's nice that mkinitrd was patched so fast but it's nice also to know that hack with rootdev invented by jannekrille. |
Quote:
That /dev/root- stuff was just a lucky shot I got when I had the same problem as you. You know, every dog has it's day... About your /bin/bash-issue, did you set up a login shell for your user? It's easy to forget, but easy to fix in "KUser". Jan-C |
Quote:
Code:
mkinitrd -c -k 2.6.27.7-smp -m reiserfs -r /dev/hda1 This fixed the problem for me, once you are up and running you will be able to update your system. samac |
Quote:
Merry X-mas, by the way. Jan-C |
This script by Eric is useful for finding the right command to enter to create an initrd:
http://www.slackware.com/~alien/tool...d_generator.sh Yeah, Merry Christmas to Slackers everywhere. |
All times are GMT -5. The time now is 10:57 PM. |