> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Axalon Bloodstone
> Sent: Saturday, November 20, 1999 10:03 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] problem with ATA/66
>
>
> On Sat, 20 Nov 1999, Steve Philp wrote:
>
> > Axalon Bloodstone wrote:
> > >
> > > On Fri, 19 Nov 1999, Dan Swartzendruber wrote:
> > >
> > > > At 04:06 PM 11/19/99 +0100, Jean-Louis Debert wrote:
> > > > >Bartłomiej Muryn wrote:
> > > > >> Exactly! It is stupid and simple - I did it - but...
> > > > >> But do not work!!!!
> > > > >> Linux don`t want to boot (not install) from this
> disk!!!!! (when plugged to
> > > > >> ATA/66)
> > > > >> It`s hanged after recognition of IDE controlers.
> Kernel can see the HPT366
> > > > >> controler correctly, see the disks, but cannot see
> the partitions etc.
> > > > >>
> > > > >> Any idea?
> > > > >
> > > > >Well, maybe you have to activate something in the BIOS
> to let it boot
> > > > >on this controller ... or rather, to tell the BIOS
> that the _primary_
> > > > >IDE interface (ide0) should be the HPT366, not the Intel BX.
> > > > >Just guessing, I really don't know ...
> > > >
> > > > What motherboard? Some of them treat the HP366 as a
> SCSI controller (in
> > > > terms of boot order, etc...)
> > > >
> > >
> > > latest bios has the option to switch the EXT boot order
> from scsi to
> > > udma66. Read the howto, and the conversation between me
> and Steve from the
> > > archives, if you still have problems lets us know
> >
> > Even after all of that, I never did get my UDMA/66 drive
> booting. It
> > simply spits an 'LI' at me and that's it. Andre Hedrick's
> HPT366 notes
> > say that booting support isn't yet available for the
> chipset. I tend to
> > believe him.
> >
> > I've now got the UDMA/66 drive on the normal IDE controller and I'm
> > using it like that.
>
> I've done the same, my time is worth more than the speed
> improvements :)
>
> --
> MandrakeSoft http://www.mandrakesoft.com/
> --Axalon
>
Maybe, but:
It is simple to not use the ATA/66 but it is the same sollution as "if Your
computer is too new - don`t install linux"... And this question is not to
make the linux start, but to make linux use the newest hardware sollution.
So:
I switched off the BIOS support for ide0 and ide1. I`m booting the kernel by
loadlin.exe from dos prompt (in reality from especially prepared M$ Win98
start menu).
Results are:
1. Kernel is loaded to memory w/o problemz, then uncompressed.
2. I`v got: "PIIX4: device disabled (BIOS)" GREAT!!!
3. But when all disks and CDrom are correctly detected, kernel says:
"ide0 at 0xcc00-0xcc07,0xd002 on irq 15
ide1 at 0xd800-0xd807,0xdc02 on irq 15"
And system hangs up!
So it will be the "(...)booting support isn't yet available for the
chipset.(...)"
So,
4. I copied the "/" (root) filesystem to the second drive (not an ata/66, on
normal ide1, I enabled it in BIOS, I updated the mounts in /etc/fstab and
restarted again.
the reaction of kernel was the SAME!
But when I`m starting all linux from drive with ata/66 connected to normal
ide with second drive (which have only fat32 partition) connected to the
HPT366 controller all starts w/o problems and I can mount the second drive
correctly. (I have problem then with cdrom on HPT366 controller, but it is
not so important cause CDrom is not an UDMA66 device.)
Then I have second question:
Maybe mr. Andre Hedrick is wrong, and we can use this controller only to
mount non-system (I mean: no /home , /usr , /boot , / ,) filesystems???
Best Regards
Bartlomiej Muryn
