It seems Peter Wemm wrote:
> > Well, CAM & ATAPI is "fairly" easy, the only problem being all the
> > little details that are different enough to make it non-trivial to
> > maintain. I once sat down and tried to get all the details on how
> > the CCB's where different, and decided that I wouldn't
Soren Schmidt wrote:
> It seems Nick Hibma wrote:
> > > > I should have said "known bad configuration". I know Søren's ATA
> > > > driver supports UDMA on the Aladdin, but I don't have the luxury of
> > > > expendable file systems, so I don't use it. I also think it's the
> > > > wrong directi
It seems Nick Hibma wrote:
> > > I should have said "known bad configuration". I know Søren's ATA
> > > driver supports UDMA on the Aladdin, but I don't have the luxury of
> > > expendable file systems, so I don't use it. I also think it's the
> > > wrong direction to go off in; if we're going
> > I should have said "known bad configuration". I know Søren's ATA
> > driver supports UDMA on the Aladdin, but I don't have the luxury of
> > expendable file systems, so I don't use it. I also think it's the
> > wrong direction to go off in; if we're going to totally rewrite our
> > IDE dr
It seems Dag-Erling Smorgrav wrote:
> "Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> > On 4 Jul 1999, Dag-Erling Smorgrav wrote:
> > > Depends on your motherboard. Try to just disable UDMA66 first. If that
> > > doesn't help, or if you have a "known bad" chipset (e.g. AcerLabs
> > > Aladdin), di
"Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> On 4 Jul 1999, Dag-Erling Smorgrav wrote:
> > Depends on your motherboard. Try to just disable UDMA66 first. If that
> > doesn't help, or if you have a "known bad" chipset (e.g. AcerLabs
> > Aladdin), disable UDMA completely in the BIOS setup utilit
> Depends on your motherboard. Try to just disable UDMA66 first.
Thanks, that's what I did. It works fine (I'm using a SOYO 5EHM
motherboard with an AMD K6-2/200). Performance is excellent; bonnie
gives:
---Sequential Output ---Sequential Input-- --Random--
On 4 Jul 1999, Dag-Erling Smorgrav wrote:
> Richard Tobin <[EMAIL PROTECTED]> writes:
> > Is that relevant for 3.2 as well as current? And by "disabling ultra
> > DMA" did you mean "disabling UDMA66" or "disabling UDMA completely"?
> > (You can permanently disable UDMA66 with a DOS utility avail
It seems Dag-Erling Smorgrav wrote:
> Richard Tobin <[EMAIL PROTECTED]> writes:
> > Is that relevant for 3.2 as well as current? And by "disabling ultra
> > DMA" did you mean "disabling UDMA66" or "disabling UDMA completely"?
> > (You can permanently disable UDMA66 with a DOS utility available
>
Richard Tobin <[EMAIL PROTECTED]> writes:
> Is that relevant for 3.2 as well as current? And by "disabling ultra
> DMA" did you mean "disabling UDMA66" or "disabling UDMA completely"?
> (You can permanently disable UDMA66 with a DOS utility available
> from IBM, and it will then act as a plain UD
I'm about to install FreeBSD 3.2 on a machine with an IBM-DJNA-371350
(Deskstar 22GXP 13.5GB) drive. I see that on the -current mailing
list a few weeks ago you (phk) said:
>Try disabling "ultra DMA" in the BIOS, that seems to have worked for
>me on my IBM-DJNA-371800 drive.
Is that relevant fo
11 matches
Mail list logo
