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)!
HELP!!!!!
Thanks!!!
