Hiya,

After downloading and burning the 9.1 iso I installed Slackware 9.1 (which
went without any problems) but after reboot... kernel panic... init couldn't
be found... try passing blah blah...
So i did pass it to the kernel but problem wasn't solved.
Now i am wondering (because in a rather gray past i had some issues with
installing other distros on a secondary ide slave) whether Slackware doesn't
like being installed on the sec ide slave.
So obviously my question is: Does anyone know if Slackware 9.1 has trouble
with being installed on a secondary ide slave?

Thanx in advance,

Michel

On 2004-03-07, Michel <reply_in_group@here> wrote:
> Hiya,
>

> So obviously my question is: Does anyone know if Slackware 9.1 has trouble
> with being installed on a secondary ide slave?
>
Just installed Slack 9.1 on 2nd hd (slave on 2nd controller).
No problem at all


--
++++++++++++++++++++++++++++++++
Mike Slack 9.1
email: micr at zeelandnet dot nl
++++++++++++++++++++++++++++++++

"Mike" <Mike@forget.it> wrote in message
news:slrnc4ml20.15s.Mike@Linux.giel...
> On 2004-03-07, Michel <reply_in_group@here> wrote:
> > Hiya,
> >
>
> > So obviously my question is: Does anyone know if Slackware 9.1 has
trouble
> > with being installed on a secondary ide slave?
> >
> Just installed Slack 9.1 on 2nd hd (slave on 2nd controller).
> No problem at all
>
>
> --
> ++++++++++++++++++++++++++++++++
> Mike Slack 9.1
> email: micr at zeelandnet dot nl
> ++++++++++++++++++++++++++++++++

ok thanx, now i can rule this out as a possible problem

michel

On 2004-03-07, Michel <reply_in_group@here> wrote:
>
> "Mike" <Mike@forget.it> wrote in message
> news:slrnc4ml20.15s.Mike@Linux.giel...
>> On 2004-03-07, Michel <reply_in_group@here> wrote:
>> > Hiya,
>> >
>>
>> > So obviously my question is: Does anyone know if Slackware 9.1 has
> trouble
>> > with being installed on a secondary ide slave?
>> >
>> Just installed Slack 9.1 on 2nd hd (slave on 2nd controller).
>> No problem at all
>>

> ok thanx, now i can rule this out as a possible problem
>
BTW: I boot the 2nd disk box with the bootmanager on
the 1st disk (slave on primary controller)


--
++++++++++++++++++++++++++++++++
Mike Slack 9.1
email: micr at zeelandnet dot nl
++++++++++++++++++++++++++++++++

Michel wrote:

> Hiya,
>
> After downloading and burning the 9.1 iso I installed Slackware 9.1 (which
> went without any problems) but after reboot... kernel panic... init
> couldn't be found... try passing blah blah...
> So i did pass it to the kernel but problem wasn't solved.
> Now i am wondering (because in a rather gray past i had some issues with
> installing other distros on a secondary ide slave) whether Slackware
> doesn't like being installed on the sec ide slave.
> So obviously my question is: Does anyone know if Slackware 9.1 has trouble
> with being installed on a secondary ide slave?
>
> Thanx in advance,
>
> Michel

I think your problem is with lilo. lilo is a funny beast. It needs to be
able to see the kernel when you run lilo after you change /etc/lilo.conf.
If you are installing on the secondary drive but running lilo from the
primary there are a couple of things you need to do to get it to work.

My fist question is what's on the primary drive? If it's windows then we
need to approach it differently. But one thing for sure is you need to
have the root option set to /dev/hdbx. The x being the partition you have
set bootable. You did set your partition bootable didn't you? For
example:

image = /boot/vmlinuz
root = /dev/hdb1
label = Linux
read-only

Now when you run lilo to install the boot loader lilo needs to be able to
see /boot/vmlinuz. In other words you need to be able to do ls /boot and
see vmlinuz in the file list. If you can't lilo will not load the kernel.
And don't forget, if you have another version of linux on the primary there
will be a /boot/vmlinuz but it's not the one you want. So if you have
another version of linux on the primary you need to mount the secondary so
lilo will see the kernel you want loaded. Make sure that you set the image
option so lilo can find the kernel. Something like:
image = /slack/boot/vmlinuz

So if you have windows on your primary drive then you need a lilo.conf
something like this:


boot = /dev/hda

other = /dev/hda1
label = windows


image = /boot/vmlinuz
root = /dev/hdb1
label = Linux
read-only


You will need to use the boot disk you made when you installed slack. You
did make a boot disk right?? Or maybe you can use one of the install disks
to get into you system, I don't remember if you can do that right off hand.

This should get you pointed in the right direction.
JM