Dag-Erling Smorgrav wrote:
>
> Terry Lambert <[EMAIL PROTECTED]> writes:
> > So we removed it from the kernel config... and the damn
> > thing enabled it again.
>
> You're thinking of ATA_ENABLE_ATAPI_DMA, which is only for ATAPI
> devices (i.e. CD-ROMs), not for disks.
Yes, thank you; you save
Jonathan Smith <[EMAIL PROTECTED]> writes:
> I am thinking of what _was_ 'sysctl hw.atamodes' (or similar) in -STABLE.
You are not Terry.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
>, [EMAIL PROTECTED]
> Subject: Re: UDMA interfering with install
>
> Terry Lambert <[EMAIL PROTECTED]> writes:
> > So we removed it from the kernel config... and the damn
> > thing enabled it again.
>
> You're thinking of ATA_ENABLE_ATAPI_DMA, which is on
Terry Lambert <[EMAIL PROTECTED]> writes:
> So we removed it from the kernel config... and the damn
> thing enabled it again.
You're thinking of ATA_ENABLE_ATAPI_DMA, which is only for ATAPI
devices (i.e. CD-ROMs), not for disks.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: s
S?ren Schmidt wrote:
> > This was a 4.3 system -- things seem to have changed in
> > the source tree since then.
>
> Nope.
>
> > In 4.3, it's not possible to disable DMA, because it gets
> > reenabled in many places (atapi.c, etc.).
>
> there is no atapi.c...
>
> > This was off-topic for -curr
It seems Terry Lambert wrote:
> "Søren Schmidt" wrote:
> > > This won't work.
> > >
> > > Someone was having the same problem the other day, and
> > > I suggested the same soloution, but after probe, the
> > > damn driver enabled UDMA at attach time anyway.
> >
> > Just set hw.ata.ata_dma="0" in
"Søren Schmidt" wrote:
> > > Maybe _that_ will keep that ata code from over-riding
> > > the bios to disable dma (or maybe the bios just wasn't
> > > doing it's job right ;)
> >
> > This won't work.
> >
> > Someone was having the same problem the other day, and
> > I suggested the same soloution,
> >
> > That's good enough. :) Thanks
> >
> > Maybe _that_ will keep that ata code from over-riding
> > the bios to disable dma (or maybe the bios just wasn't
> > doing it's job right ;)
>
>
> This won't work.
What do you mean with this? The procedure that I described (barring
typos) do
It seems Terry Lambert wrote:
> Jonathan Smith wrote:
> >
> > That's good enough. :) Thanks
> >
> > Maybe _that_ will keep that ata code from over-riding
> > the bios to disable dma (or maybe the bios just wasn't
> > doing it's job right ;)
>
> This won't work.
>
> Someone was having the
Jonathan Smith wrote:
>
> That's good enough. :) Thanks
>
> Maybe _that_ will keep that ata code from over-riding
> the bios to disable dma (or maybe the bios just wasn't
> doing it's job right ;)
This won't work.
Someone was having the same problem the other day, and
I suggested the sam
Smith <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: UDMA interfering with install
>
> >
> > Unfortunately, the UDMA chipset on my ASUS P5A doesn't work well with
> > Western Vegetable drives So, I need to forcibly sysctl it into pio
> > mod
>
> Unfortunately, the UDMA chipset on my ASUS P5A doesn't work well with
> Western Vegetable drives So, I need to forcibly sysctl it into pio
> mode. Is there *any* way to do this from sysinstall on the
> 5.0-200105250-CURRENT (or later snap on current.freebsd.org) floppy
> bootup?
Well I
Unfortunately, the UDMA chipset on my ASUS P5A doesn't work well with
Western Vegetable drives So, I need to forcibly sysctl it into pio
mode. Is there *any* way to do this from sysinstall on the
5.0-200105250-CURRENT (or later snap on current.freebsd.org) floppy
bootup?
Thanks
j.
-
13 matches
Mail list logo
