SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Originally posted by srinis hi,
i happen to do all tha req for copiling the 2.6 kernel , my present 2.4 kernel is fine. but when i try yo boot into he 2.6 kernel it stops saying
kernel panic give correct root=
something of that sort,
ut when i boo my 2. it's fine.
My boot device is /dev/hda6 so i my grub.conf i have
and others this is the same line in both the 2.6 part and 2.4 part of the grub.conf, but i don't get why it says unknown root device only while booting 2.6, can any sugges a solution.
Thanking You,
Satish
I don't know the solution, but I'm confused by your reference. I'm pretty sure hda6 should be referenced as hd0,5 in GRUB, not hd0,6.
Guys, this is strange. I am trying to re-install Mandrake 9.2 by using the same exact iso image/cd, but the difference is that this time around I am getting errors in different packages and it will not continue to install Mandrake rather it will put me back to the step where I select what I want to install. I tried it MANY many times.. but nothing worked. I just can't figure out why its doing this.
Distribution: RHEL, Ubuntu, Solaris 11, NetBSD, OpenBSD
Posts: 225
Rep:
Hi jsolanky,
The only time I've ever had anything like this, with packages failing to install from a previously used iso image is if it's a duff CD or the iso file has been corrupted.
With a cd that pas been previously used, I have the same problem when the cd has been scratched....
I got a 2.4.26 kernel to boot. I moved the old kernel back into /boot from /boot.old, and separated the kernels by giving them different names instead of having them in different directories (not really sure why that mattered, given that the stuff that was in /boot.old booted OK, but whatever). Interestingly, if I named the new kernel and system map just vmlinuz and System.map, it didn't work, but if I named them vmlinuz-2.4.261 and System.map-2.4.261, it did.
Now I am working on building a 2.6.9 kernel. Thanks very much for the help!
did you edit the Makefile?? I can't imagine that changing the names really solved the problem. Are you using LILO?
Make a directory, /boot/269, and the edit the Makefile in the 2.6.9 kernel tree so that INSTALL_PATH=/boot/269
Now when you compile and install the new kernel it will all go there. Edit lilo.config accordingly and you shouldn't have any problems.
Ok i must be doing somethign seriously wrong here.
It seems everything is hunky dory. i installed using the step by step advice of both posts on updating the kernel(ie the n00b one and this on). My kernel installs fine but when i try to boot to it i dont even get the linux.old at the lilo boot sector screen. Its as if nothing has been done to install. I am at a loss as to what to do. Im updating from 2.4.26 to 2.6.28. Is there a directory that this needs to be in? or something wrong with my lilo.conf? aany advice would be awesome.
wLancer,
Well, that's your problem, if you don't tell lilo about the changes you've made it's not going to work.
You need to seperate the two kernels within the lilo.conf file the update lilo via /sbin/lilo.
Only then will you have the option to choose what kernel you want to boot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.