grubconfig for grub 0.97 on hdd or usb: is there a patch for ext4?
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I still prefer to work with grub legacy than grub2. I use is on a regular basis but had some problem when I wanted to install vector linux and archbang on a usb key. Vector will boot but not archbang: http://bbs.archbang.org/viewtopic.php?id=2052
This grub package does not seem to be able to install a grub bootloader able to read ext4 file system on a sdb3 partition for a menu.lst installed on the sdb1 partition (sdb2 being the swapfile).
Is there some patch available for the abovementionned slackware package?
Last edited by francois.e; 01-27-2012 at 04:56 PM.
did you try changing
or did you try just removing the "root ( )" completely as with the Vector entry?
Are the Vector and/or Archbang just livecd's or are they full HDD installs?
did you try root=/dev/sdb3 in the kernel command line?
It seems you have a Archbang full install and a Vector livecd on usb?
that being said can you post the Archbang menu.lst and /etc/fstab?
when you installed archbang and it made the initrd/initramfs for sdb3?
did you see this?
If you are installing Archbang to a USB memory or USB HD, you have to add USB as a HOOK in /etc/mkinitcpio.conf, during the configuration. More information in the official Installing Arch Linux on a USB key.
"Note: When grub is installed on the USB key, the key will always be hd0,0"
"When editing the /etc/mkinitcpio.conf, add the usb hook to the hooks array right after udev. This is necessary for appropriate module loading in early userspace. "
"HOOKS="base udev usb autodetect pata scsi sata filesystems" https://wiki.archlinux.org/index.php...x_on_a_USB_key
and the grub error 15 is it can't find the kernel, so you have to start there
if it does boot the kernel/initrd but cant find it's root, check for the usb hook, and make sure the initramfs is looking for correct partition, etc
Your suggestions were finally part of the final solution. In addition, I realized that the grub version that I had was not patched for reading ext4 partitions.
I finally got around the grub legacy not patched for ext4 partition by using mepis 8.50 system assistant to repair grub. However, I would have like to be able to apply the ext4 patch provided by salix to slackware grub legacy and grubconfig package as proposed in:: http://www.salixos.org/forum/viewtopic.php?p=3127
Grubconfig is really a nice program to install grub and prepare a menu.lst.
I found this thread very useful wanting to play with grub. I installed grub-0.97-i486-9.txz
and ran grubconfig (didn't even know that script existed) Now about the patch I know about
sbopkg for getting patches ,upgrade for sbo packages, but had a mental block on actually applying the patch grub-0.97-i486-9.txz.asc played with slackpkg update,install-new etc
nothing seemed to happen but somehow eventually got grub installed.
But if you have downloaded the patch to the say the desktop whats the simple way of installing the patch from the command line.I mean installing the txz is
#installpkg grub-0.97-i486-9.txz ,so without using a network how do you install the patch?
While starting to play with grub ,I installed antiX based on mepis which boots itself using grub. First I tried to install grub on Slackware and boot Antix from slackware. Firstly I got a glitch over antix being ext2 and slackware being ext4,and crashed slackware.
Got slackware booted using install disk and then ran grubconfig. Bash terminal stated “done” and I assumed I put menu.lst into /boot/grub of slackware. Antix then wouldn’t boot but got into file system using trinity.
I found menu.lst that references slackware in /boot/grub/menu.lst of antiX
Now I read up about grub legacy and noted something about initrd files. I noted there were not any
in /boot of Slackware.
This begs the question although I installed grub-0.97-i486-9.txz it looks like i’m missing one or more packages (and or steps)to be able to be able to properly install grub legacy on slackware 13.37.
my partition are sda1 (swap)
sda2 antix (partly mashed but grub ok)
(when I ran grubconfig I entered /dev/sda2, thinking grub notation sda1 being hda0, or sda0)i.e I thought it was going to slackware (I was wrong)
What are the steps/ packages i’m missing ?
This is a bit of a dogs breakfast -sorry for that but
1) At least I can get slackware up booting
2) I’m starting to appreciate lilo very quickly
3) I can always run liloconfig and go back to lilo, and re-install another distro onto sda2
If you want to keep the grub bootloader installed with antiX, you have to update menu.lst from antiX, so you boot antiX and add slackware in antiX's /boot/grub/menu.lst
Now if you want to use grub from Slackware, you overwrite MBR and install slackware's grub with
grub-setup /dev/sda, then update grub menu in Slackware's /boot/grub/menu.lst
But again, I found using a separate /boot partition in ext2 format is the easier thing to deal with grub. This way you'll never have to mess with grub again, just update the /boot/grub/menu.lst even if you change distribution or upgrade system, update kernel etc...
I would like to go with using grub with slackware.
At the moment menu.lst is in boot/grub of partition sda2 which is antix.So at the moment grub is actually working but stage2 stuff(i.e menu.lst) is in boot/grub of antix, and I want it in slackware.
My understanding is that when you overwrite the mbr using grub-config ,it writes code on the mbr which points to config files such as menu.lst which is in /boot/grub of the partition you want to use in my case I would like slackware which is on sda3.
Now after booting into slackware from grub , I tried #grubconfig ,and choosing
simple install to /dev/sda3 output was "can not find stage1". Now I take it that the gubconfig script takes naming literally and does not use partition numbers starting from zero? Inside slackwares /boot/grub there are a load of mod files, kernel.img several other
So first I need to overwrite mbr to point to slackwares /boot/grub , I thought grubconfig would do that, and other scripts as you say grub-setup and or grub-install to put a menu.lst (which I then edit) into sda3 /boot/grub