trouble switching to generic kernel
i am following the guide on this page: http://docs.slackware.com/slackware:beginners_guide
first i ran this: Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh Code:
bash-4.2# /usr/share/mkinitrd/mkinitrd_command_generator.sh Quote:
Quote:
Code:
# LILO configuration file Code:
Warning: LBA32 addressing assumed |
edit: updated OP with exact details of all the changes i did
|
this is the error that i get on startup:
Quote:
a bunch of other stuff happens then keyboard starts blinking, cannot do anything... :D |
Note: I answered the wrong question, sorry.
|
Before you exit you should try to edit /etc/lilo.conf and remove the comments you put in front of the huge kernel, the ####'s. You can have more than one kernel to choose from at the lilo prompt and this will allow you to experiment and recover easily.
If you can get the file edited then run lilo, type exit, (maybe reboot) and you ought to be back up. Be sure to pick the huge kernel to boot from instead of the broken configuration. It also appears that you tried to set up the initrd.gz for a non-smp kernel. Unless you really, really want that and can modify the kernel sources to support it (in some cases), then you should really be using the smp kernel. Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh --longhelp | more basically, you should: Code:
root@tardis:~# /usr/share/mkinitrd/mkinitrd_command_generator.sh --lilo /boot/vmlinuz-generic-smp-3.2.29-smp >>/etc/lilo.conf |
Quote:
i do not understand why following the beginners guide, as perfectly as i have done, has resulted in a broken mess. don't get me wrong, i'm not mad I am learning and trying to have fun, but... ::violin |
Quote:
Code:
Note that it is recommended to add a new section instead of editing the existing kernel image section. Assign a unique label to your new section. After reboot, LILO will give you two options: to boot into your freshly added generic kernel, or to boot into the failsafe huge kernel (of which you are certain that it will work). |
Quote:
|
Quote:
Code:
bash-4.2# /usr/share/mkinitrd/mkinitrd_command_generator.sh --lilo /boot/vmlinuz-generic-smp-3.2.29-smp >>/etc/lilo.conf |
Quote:
can you post the results of ls -hal /boot here 's mine Code:
le@darkstar:~$ ls -hal /boot here's mine Code:
le@darkstar:~$ less /etc/lilo.conf |
here you go dude, am i all set to go now? :D
Quote:
Quote:
|
Quote:
Code:
#image = /boot/vmlinuz btw, can you now boot with the generic or you still have trouble? |
Quote:
The point of using a generic kernel is to optimize the pc, right? Is there another use to why I would want to use the huge kernel in the future? I originally had both the kernels listed in my lilo.conf file, but i couldn't figure out which one was being run by computer at bootup so thats why i commented it out. |
Quote:
i guess you have to label the huge to see it at boot time > eg. label = huge |
As others have said, if you instantly disable the huge kernel, you're just assuming the generic one will work. It's best to keep the huge kernel as a backup at least until you're sure the generic one boots.
Quote:
Quote:
This is how I build an initrd for the 3.2.29 generic kernel Code:
# mkinitrd -c -k 3.2.29-smp -m ext4 |
All times are GMT -5. The time now is 09:51 AM. |