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.
Yes I know there are loads of Q&As on GRUB...........
ok so i want to use GRUB for a change (on a fresh install).
Install Grub pkg.
grub-install (hd0,0) //which is sda WinXP. sdb is slack.
ok thats all fine, it find the 2 hds and a floppy.
reboot Slack. Grub shell pops up. check if i can boot WinXP, yup works fine.
reboot win, and check if slack boots.
Code:
root (hd 1,1)
kernel /boot/vmlinuz root=/dev/sdb2 ro vga=791
boot
which fine it boots Slackware until;
VFS:Cannot open root device @sdb@ or unkown block (0,0)
Please append a correct @root=@ boot option
Kernel Panic - not syncing: VFS:Unable to mount root fs on unknown-block (0,0)
ok i reboot and boot again to make sure i havent done anything stupid. same thing.
so my next guess is check the config, probably sdb is pointing to (0,0) than (1,1)...hm
but their is no /boot/grub/gub.conf, or under /etc/ or anywhere! bah. their is only a generic menu.lst.sample, not a properly created menu.lst
If the kernel is panicking it's not grub's fault, unless you've given the kernel the wrong arguments. Have you made an initrd? It looks like the kernel gets lost as it doesn't have the disk driver or filesystem module and can't read the disk.
Did you give up?
For the record, the MBR is the first 512 bytes of a whole hard drive (sda in your case), not part of any partition. Grub calls the whole hard drive (hd0). So if you want to install grub to the MBR then it is right to setup (hd0).
If WinXP is installed on the first partition, then grub will see that as (hd0,0). If slackware is installed on the second partition of the second drive then it is (hd1,1).
But, something tells me that you have only one hard drive -is that correct?
Do have one or two hard drives -physical disks I mean? sdb means a second whole hard drive.
grub-install (hd0,0) installs grub to the first *partition* of the first drive. This is what's called the 'superblock' of the partition -the first 512 bytes of the *partition* -not the same as the MBR.
What commands did you use to start WinXP? Or did you run them from a menu.lst file which you have configured? Please post the exact commands you used or the contents of your menu.lst If you have a menu.lst file, did you create it manually?
Have you tried using the grubconfig utility that comes with the slackware grub package?
Distribution: Slackware 12 Kernel 2.6.24 - probably upgraded by now
Posts: 1,054
Rep:
if you have sda and sdb, then you have 2 HDDs. Why mess with the WinXP loader?
Install grub to sdb. In BIOS you can easily select to boot to whichever HDD you want. Each HDD has a MBR.
Slack 12 by default asks to use the generic kernel, which requires a initrd. The huge kernel doesn't . I would always recommend to run your own kernel, without an initrd.
Slack 12 by default asks to use the generic kernel, which requires a initrd. The huge kernel doesn't
Ok thanks for the correction. I do not remember specifying a kernel during install and my /boot/vmlinuz points to the huge kernel so I just made the assumption.
Quote:
if you have sda and sdb, then you have 2 HDDs. Why mess with the WinXP loader?
Install grub to sdb. In BIOS you can easily select to boot to whichever HDD you want. Each HDD has a MBR.
Interesting option. As a matter of personal preference I like to choose which system to boot from grub, rather than from the BIOS. Once grub is set up, all I need to do is press the down arrow and hit enter. This is quicker for because I use both OS's fairly often.
Distribution: Slackware 12 Kernel 2.6.24 - probably upgraded by now
Posts: 1,054
Rep:
Quote:
Hmmm ... I thought the default kernel for Slack 12.0 was huge-smp, wasn't it ? And it doesn't require any initrd.
The readme file in Slack clearly states, you shouldn't use HUGE SMPS for anything at all, ever. Only to find out what is the stuff you need etc. etc. Using huge smps anytime for actual use is just wrong.
I didn't install slack12, I upgraded so I don't know what exactly happens on an install, I used my own kernel throughout .
Well, I'm pretty sure the default is huge-smp. I mean, it's not a bad option for an install kernel, because it has many things built-in. After that, however, it is recommended that if you have a bit of patience, that you compile your own kernel. I recommend using the generic '.config' file, and going from there. It saves time for me, doing it this way.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.