LinuxQuestions.org
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   GRUB configuration (https://www.linuxquestions.org/questions/linux-newbie-8/grub-configuration-369181/)

JSLayton 10-02-2005 08:27 PM
GRUB configuration
 
I am trying to configure GRUB for booting Windows XP, Fedora, and Slackware. All are working fine except for Slackware. Seems I have the wrong path for the vmlinuz file. Can someone tell me what the path is for that file in a default install of Slackware??

bulliver 10-02-2005 08:46 PM
/boot/vmlinuz I suppose.

If you post your grub.conf and a partition table I could help you a lot better...

JSLayton 10-02-2005 08:50 PM
/boot/vmlinuz isn't working. Let me try it again and I'll post the error message.

b0nd 10-02-2005 08:50 PM
hello,
post yr grub.conf.

anyways...default entry slackware is

image = /boot/vmlinuz
root = /dev/hda8
label = Slackware
read-only

but since u r dealing with grub.conf, so entries will be a little different

Note: slackware has lilo.conf

regards

bulliver 10-02-2005 09:00 PM
Please post grub.conf and a partition table, at least for your slack partitions. If slack has a separate /boot partition then configuration will be different.

Are you even sure the slack kernel is called vmlinuz?

JSLayton 10-02-2005 09:09 PM
Error is
13 : Invalid or unsupported executable format

grub.conf is

Code:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd1,1)
#          kernel /boot/vmlinuz-version ro root=/dev/hdb2
#          initrd /boot/initrd-version.img
#boot=/dev/hda
default=1
timeout=7
splashimage=(hd1,1)/boot/grub/splash.xpm.gz
hiddenmenu
title Redhat Fedora Core (2.6.11-1.1369_FC4)
        root (hd1,1)
        kernel /boot/vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=REDHAT rhgb quiet
        initrd /boot/initrd-2.6.11-1.1369_FC4.img
title Windows XP
        rootnoverify (hd0,0)
        chainloader +1
title Slackware Linux
        root (hd0,4)
        kernel /boot/vmlinuz root=/dev/hda5

bulliver 10-02-2005 09:21 PM
OK, I don't think your kernel is called vmlinuz.

Try:
Code:
title Slackware Linux
        root (hd0,4)
        kernel /boot/bzImage root=/dev/hda5
If that doesn't work then I can walk you through some grub command line magic to find out what your kernel really is called...

JSLayton 10-02-2005 09:25 PM
Now I'm getting file not found. What commands do I need to do to find out the kernel name?

bulliver 10-02-2005 09:38 PM
Ok. When your in the grub menu press 'c'. This will give you a command line:
grub>

Now you want to set the root to your slack install:
Code:
grub> root (hd0,4)
Filesystem is ext2fs, partition type 0x83
Now lets see what is in /boot:
Code:
grub> kernel /boot/[Tab] # press 'tab' key here
Possible files are: foo bar baz
Now this will list all files in /boot. One must be your kernel
At this point you can:
Code:
grub> kernel /boot/fooKernel root=/dev/hda5
grub> boot
And slack should boot. Now edit grub.conf to reflect what your kernel is called.

syg00 10-02-2005 09:57 PM
conf looks o.k. for a default Slack install.
You sure it's on hda5 ??? - same disk as Winders, whilst FC4 is on the other disk.
Is this correct ???.

JSLayton 10-02-2005 10:37 PM
Yes, same disk as Windows.

I tried and there were only two files that appeared to be kernels, vmlinuz and vmlinuz-ide-2.4.29. Neither one worked. Both gave me the same error.

bulliver 10-02-2005 10:46 PM
Ok, so this kernel, did you make it yourself or is it the default slack kernel?
On my system I have this:
title slackware
root (hd0,8)
kernel /boot/vmlinuz root=/dev/hda9

And it works fine. So if it is not working for you, even though the file clearly exists, I can only assume that the kernel itself is borked, and not grub.

Looks like you may have to boot slack with a rescue cd and redo your kernel.

Another idea is that sometimes automated kernel tools place the kernel in the '/' directory, so have a look using the method I showed before and see if there is a kernel like: '/vmlinuz'

syg00 10-02-2005 10:52 PM
Whoops - didn't notice it was error 13.
Only time I've ever seen that is if the wrong file was copied from ..arch/i386/boot/ after a compile.
Copy .config as vmlinuz - that sort of thing.

If this is Pats shipped system, I guess that's unlikely.

JSLayton 10-02-2005 11:09 PM
OK, well it appears I might have to reinstall Slackware to get it to work, so I might go with another distribution all together. Any recommendations?? I want something that is actively being developed and isn't a no-name version.

syg00 10-02-2005 11:14 PM
Maybe before doing that, try booting your HD Slack from the Slack bootCD - it's in the doco somewhere.
I had to do it once, worked fine. Will at least prove the install itself is o.k.


All times are GMT -5. The time now is 06:23 PM.
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page