DragonFly kernel List (threaded) for 2003-09
Re: Prebinding for DragonFly/FreeBSD-4
Yeah... it was a response to a comment I made about not being able to
yet on my hardware... sorry for the lack of context but others had
asked me for this
information so I just cc'd the list.
Anyway SATA works on FBSD CURRENT at the moment pretty well and the
in question aren't SATA but just on the Nforce2 IDE controller. Does
experience similar problems with this motherboard chipset?
On Sep 23, 2003, at 11:22 AM, Matthew Dillon wrote:
Was this conversation started on the list in the middle? I seem to
have missed the context.
Could someone give a quick overview of the use of serial ATA in
FreeBSD/DragonFly? I know that the ATA driver has gone through
incarnations. We are using incarnation #2 in DragonFly (the same
4.8), while FreeBSD-5 is now on incarnation #3 (and having serious
with it). There was a lot of breakage between incarnation #1 (the
drivers) and #2, and between #2 and #3, which to me means that we
to stick with what we have now and try to fix it verses, say,
import the new infrastructure from FreeBSD-5.
The error below sounds like a DMA problem.
:Ok I got the 9/22 snapshot
:and it fails to boot beyond the following:
:ad0: 38166MB <WDC WD400BB-00DGA0> [77545/16/63] at ata0-master BIOSDMA
:WARNING: "ad" is usurping "ad"'s cdevsw
:ad1: READ command timeout tag=0 serv=0 - resetting
:ata0: resetting devices ..
:and then it hangs. I am sure its the SATA or something related to the
: NForce2 IDE controller causing this havoc.
:On Sep 20, 2003, at 8:25 PM, David Rhodus wrote:
:> On Thursday, September 18, 2003, at 08:32 AM, David Leimbach wrote:
:>> I bet those things are relatively easy to fix... I just need to
:>> some time
:>> this weekend and actually see if I can run DFBSD with one of the
:>> later snapshots.
:>> I still can't boot it here.
:> Dave, is there a specific point in the boot process were
:> your getting hung up at ? Or is it just sitting spinning the
:> cd ?
:> Also have you tried to boot a FreeBSD 4.8 cd ? Just to
:> check if something has gotten broken since we branched
:> off the cvs tree.