civileme wrote:
>
> > Sorry about this, but the 7.2 kernel just does not see IDE2 or IDE3,
> > which is where Promise lives.
> > This applies to both the installer and the installed runtime. I
> > don't know where your erroneous information might be coming from.
>
> It comes from actual, installed running systems.
>
> Now what is _different_ about yours?
The installaltion is from the 7.2 CDs made from the isos. VERSION is
"Linux-Mandrake Download Edition Odyssey-i586 20001027 15:47".
I also have another installation from the download tree. VERSION is
"Linux-Mandrake Odyssey-i586 20001027 15:20".
Neither of these can see IDE2 or 3, since they both use kernel
2.2.17-21mdk. kernel 2.2.17-28mdk in my experience was the first to
see IDE2 and 3.
> > Worse, neither lilo nor grub know about these IDE channels, so you
> > MUST at all times have a disk on one of your 2 mobo IDE channels,
> > otherwise there is no secondary boot loader (lilo gives no error
> > message from its failure to write it to a non-existent hda) and all
> > booting will stop at LI. Booting from floppy and re-executing
> > /sbin/lilo makes no difference - still stops at LI.
>
> OK, I'll try that. But if it works on my AZ11 with all drives on 2 and 3,
> under their Promise ATA/100 controller, does that mean it should work on your
> system too?
I tell you it does not work - but it takes some time, a few ups and
downs, to realise IDE0 and 1 are empty.
> > > lspci -vv | less
> > >
> > > and scroll through the output. The current advice on mandrakeuser.org is
> > > to do
> > >
> > > linux ide2=0xa000 0x9802
> >
> > This is totally unacceptable, because there is no way to automate it
> > that I am aware of since at that point there is no file system. To
> > have to type in such gobbledigook at every boot is plainly
> > unacceptable.
There is a solution: Have delay and timeout in lilo.conf set to 50
and 'lock' set in the global section, run lilo and reboot. At the
lilo boot prompt, enter 'linux ide3=0xd000,0xcc02' (or whatever
applies to you - NO append!) and enter. Once linux comes up it
will have the kernel mod, but any delay or timeout commands in
lilo.conf will now be ignored and future boots will no longer provide
any kernel intervention point. The previous kernel command is now
locked in and executed at every boot. To undo this you must remove
the lock command from lilo.conf and run lilo. Pretty good, eh?
> It is only for the boot--during bootloader installation we have to type the
> ide2=0xa000 0x9802 into the Append blank of each linux system booting
> (Usually linux linux-nonfb and failsafe)
That's no good, because the change needs to be global, and there is
no useable root or boot device for the global lilo. Lilo cannot
function.
> > But the reassignment is only for the duration of the install.
> >
> Now that is a very valid point! The reassignment will not work for boot
> because the append strings have to be loaded off the disk and it has to be a
> specific disk with the then existing assignments--instant freeze on partition
> check. With a flexible enough BIOS, this is not a problem. I have a
> motherboard which has a LS120 on /dev/hda and a Maxtor on /dev/hde and LILO
> boots from /hde with no problem, but if I tried to assign that to /dev/hda
> --Yeech-- That could be interesting to try....
I have described the solution above. Good luck with it!!!
--
Regards,
Ron. [au]
