At 17:45 01/07/01 -0700, Ben Ford wrote:
>Fernando da Motta Hildebrand wrote:
>
>>At 23:21 30/06/01 -0700, Ben Ford wrote:
>>
>>>Fernando da Motta Hildebrand wrote:
>>>
>>>>At 16:22 30/06/01 -0700, Ben Ford wrote:
>>>>
>>>>>Fernando da Motta Hildebrand wrote:
>>>>>
>>>>>> Ive got 2 HDs, (hda,hdc), in hda Progeny with grub on MBR, in
>>>>>> hdc Slack. Ive managed to start Slack by adding the kernel
>>>>>> image(vmlinuz) into menu.list, but it doesnt load any modules when
>>>>>> it starts, also shows a 2.2.18 kernel instead of the 2.2.16 that
>>>>>> come along with slack7.1.
>>>>>> I guess ive should also indicate the initrd location for
>>>>>> slack(as the default for Progeny). The problem is:
>>>>>>-In progeny theres this /boot/initrd.gz, and it doesnt seem to have
>>>>>>any similar in Slack. so...
>>>>>>-How do I add the path to initrd�s in Slack(wheres the damn
>>>>>>thing??(read line above)) What to do?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>Slack doesn't use initrd. Just point it to the proper partition.
>>>>>(unless you've changed it, Slack's is /vmlinuz)
>>>>>
>>>>>Try this stanza, adjusting parameters to fit your setup. It is
>>>>>designed for a layout like this:
>>>>> /dev/hdc1 ---> swap
>>>>> /dev/hdc2 ---> / (root partition)
>>>>>
>>>>>title Slackware - Kernel 2.2.16
>>>>>root (hd2,1) <--------------- This is equiv. to /dev/hdc2
>>>>>kernel /vmlinuz root=/dev/hdc2 ro <---Adjust as needed.
>>>>>
>>>>>-b
>>>>>
>>>>>--
>>>>>: __o
>>>>>: -\<,
>>>>>: 0/ 0
>>>>>-----------
>>>>
>>>>
>>>>
>>>> Well... Ive tried that and didnt work. I also tried install
>>>> lilo from slack in MBR and the oppsite happened:
>>>>-When booting Progeny it wouldnt load its modules, as it tries to
>>>>search for the 2.2.16 modules.
>>>>Then Ive reinstalled grub and the same happened when trying to load
>>>>Slack: it wouldnt load its modules searching for the 2.2.18 modules.
>>>> So... Heres my guess: Whenever i try to use on or another
>>>> loader it (and i dont have a clue why!?!?!?) attempts to load the
>>>> modules relative to the system witch theyve been installed with(grub
>>>> for Progeny, Lilo for Slack), So there must be a way for telling
>>>> grub(or lilo) something like this: Hey you! There are 2 linux in this
>>>> box! each one with its own modules and kernels(one 2.2.16, other 2.2.18)!
>>>
>>>
>>>
>>>I have built boxes with up to 7 operatinng systems on them. Debian,
>>>Redhat, Mandrake, Slackware, BeOS, Windows98 and Windows2000 using both
>>>grub and lilo. Check out this page for help.
>>>
>>>http://www.ibiblio.org/pub/Linux/docs/HOWTO/mini/other-formats/html_single/Multiboot-with-GRUB.html
>
>>>
>>>
>>>-b
>>>
>>>--
>>>: __o
>>>: -\<,
>>>: 0/ 0
>>>-----------
>>
>>
>> Thanks, it was really good to read this How-to. Ive managed to
>> find something really stupid i was doing: Theres a link in progeny named
>> vmlinuz tha points to /boot/vmlinuz-2.2.18, so... I was loading the
>> wrong kernel in slack!!(no wonder i was not loading the rights modules,
>> dah!!someone kill me please!!!), than i did this with what ive found at
>> info-grub:
>>
>>title Slackware - Kernel 2.2.16
>>root (hd2,1)
>>kernel (hd2,1) /vmlinuz root=/dev/hdc2 ro
>>
>> But then ive got error 21: disk not recognized( or something
>> like that...).
>>
>>I cant get why grub isnt recognizing my hdc.
>>
>>So... any new ideas???
>
>
>This is the error message and the meaning.
>
>21 : Selected disk does not exist
> This error is returned if the device part of a device- or full
> filename refers to a disk or BIOS device that is not present or not
>recognized by the BIOS in the system.
>
>Try making both (hd2,1) into (hd1,1).
>
>Also, another trick is to press 'c' when you get to the boot menu. This
>will drop you into a command prompt so you can try the commands in real
>time instead of rebooting every time. You just type the commands in
>order, then when you are ready to boot, just type boot.
>
>In other words, when grub comes up, press 'c' then type the following:
>
>root (hd1,1)
>kernel (hd1,1) /vmlinuz root=/dev/hdc2 ro
>boot
>
>and you should be rolling. If you get any errors, make a note of them and
>let me know what the message was, and in response to what command. When
>you work out a sequence of commands, copy them into the
>/boot/grub/menut.1st (omitting the 'boot' command)
>
>-b
>
>
>--
>: __o
>: -\<,
>: 0/ 0
>-----------
THANK YOU MY TEACHER!!! I didnt understand why, but it worked!
Does grub only reads the devices names when it finds a HD? I cant get why a
hdc(HD2) would be read in the root command like a hdb (HD1)?
Could you teach me ( and everyone else in the list) what happened?
Once again: Thank you a lot for your help.
Fernando.
