Jump to content

NForce4 Serial ATA (DEVELOPMENT)

hamlo

By hamlo,
in Hardware Components and Drivers

 Share
185 posts in this topic

Recommended Posts

jape
jape
Posted
Posted

Yeah.. it seems to unzip fine from any non OS X os.

You can look at my post how i built the kext succefully and it is non-working...

I could try replacing scanForDrives with Intel's (as Hamlo was about to do, If I understand this), but I dont think our problem is there. Better wait until he explains a bit more.

Link to comment
Share on other sites
Martin B
Martin B
Posted
Posted

Have people looked at http://darwinsource.opendarwin.org/10.4.3/...OnboardPCATA-2/ ? There is a driver there for the nForce, and also, at http://darwinsource.opendarwin.org/10.4.2/...leOnboardPCATA/ seems to most closely resemble hamlos driver... maybe there is something here which will supplement the missing parts of hamlos driver... sorry this has probably already been covered!

Link to comment
Share on other sites
westep23
westep23
Posted
Posted

:stretcher:-->

QUOTE(Martin B @ Nov 20 2006, 08:51 AM) <{POST_SNAPBACK}>

Have people looked at http://darwinsource.opendarwin.org/10.4.3/...OnboardPCATA-2/ ? There is a driver there for the nForce, and also, at http://darwinsource.opendarwin.org/10.4.2/...leOnboardPCATA/ seems to most closely resemble hamlos driver... maybe there is something here which will supplement the missing parts of hamlos driver... sorry this has probably already been covered!

 

 

I think these are the drivers we are using now. For Ide

Link to comment
Share on other sites
AlainTox714
AlainTox714
Posted
Posted

Just an another trail with possibly some useful info on piotiming & dmatiming

 

especially in file ata.chipset.c

 

here is the link :

 

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/

 

ATA(4) FreeBSD Kernel Interfaces Manual ATA(4)

 

NAME

ata, ar, acd, ad, afd, ast -- generic ATA/ATAPI disk controller driver

 

SYNOPSIS

For ISA based ATA/ATAPI support:

device isa

device ata

 

In /boot/device.hints:

hint.ata.0.at="isa"

hint.ata.0.port="0x1f0"

hint.ata.0.irq="14"

hint.ata.1.at="isa"

hint.ata.1.port="0x170"

hint.ata.1.irq="15"

 

For PC98 based ATA/ATAPI support:

device isa

device ata

 

In /boot/device.hints:

hint.atacbus.0.at="isa"

hint.atacbus.0.port="0x640"

hint.atacbus.0.irq="9"

 

For PCI based ATA/ATAPI support:

device pci

device ata

 

To support ATA compliant disk drives:

device atadisk

 

To support ATA software RAID's:

device ataraid

 

To support ATAPI CDROM, DVD and CD/DVD burner drives:

device atapicd

 

To support ATAPI floppy drives:

device atapifd

 

To support ATAPI tape drives:

device atapist

 

The following tunables are settable from the loader:

 

hw.ata.ata_dma

set to 1 for DMA access, 0 for PIO (default is DMA).

 

hw.ata.atapi_dma

set to 1 for DMA access, 0 for PIO (default is DMA).

 

hw.ata.wc

set to 1 to enable Write Caching, 0 to disable (default is enabled).

WARNING: can cause data loss on power failures and crashes.

 

DESCRIPTION

The ata driver provides access to ATA (IDE) and SerialATA disk drives,

ATAPI CDROM/DVD drives, ZIP/LS120 ATAPI drives and ATAPI tape drives con-

nected to controllers according to the ATA/ATAPI standards.

 

The currently supported ATA/SATA controller chips are:

 

Acard: ATP850P, ATP860A, ATP860R, ATP865A, ATP865R.

ALI: M5229, M5281, M5287, M5289.

AMD: AMD756, AMD766, AMD768, AMD8111.

ATI: IXP200, IXP300, IXP400.

CMD: CMD646, CMD646U2, CMD648, CMD649.

Cypress: Cypress 82C693.

Cyrix: Cyrix 5530.

HighPoint: HPT302, HPT366, HPT368, HPT370, HPT371, HPT372, HPT372N,

HPT374.

Intel: 6300ESB, 31244, PIIX, PIIX3, PIIX4, ICH, ICH0, ICH2,

ICH3, ICH4, ICH5, ICH6, ICH7.

ITE: IT8211F, IT8212F.

JMicron: JMB360, JMB361, JMB363, JMB365, JMB366.

Marvell 88SX5040, 88SX5041, 88SX5080, 88SX5081, 88SX6041,

88SX6081.

National: SC1100.

nVidia: nForce, nForce2, nForce2 MCP, nForce3, nForce3 MCP,

nForce3 Pro, nForce4.

Promise: PDC20246, PDC20262, PDC20263, PDC20265, PDC20267,

PDC20268, PDC20269, PDC20270, PDC20271, PDC20275,

PDC20276, PDC20277, PDC20318, PDC20319, PDC20371,

PDC20375, PDC20376, PDC20377, PDC20378, PDC20379,

PDC20571, PDC20575, PDC20579, PDC20580, PDC20617,

PDC20618, PDC20619, PDC20620, PDC20621, PDC20622,

PDC40518, PDC40519, PDC40718, PDC40719.

ServerWorks: ROSB4, CSB5, CSB6.

Silicon Image: SiI0680, SiI3112, SiI3114, SiI3512.

SiS: SIS180, SIS181, SIS182, SIS5513, SIS530, SIS540, SIS550,

SIS620, SIS630, SIS630S, SIS633, SIS635, SIS730, SIS733,

SIS735, SIS745, SIS961, SIS962, SIS963, SIS964, SIS965.

VIA: VT6410, VT6420, VT6421, VT82C586, VT82C586B, VT82C596,

VT82C596B, VT82C686, VT82C686A, VT82C686B, VT8231,

VT8233, VT8233A, VT8233C, VT8235, VT8237, VT8251.

 

Unknown ATA chipsets are supported in PIO modes, and if the standard bus-

master DMA registers are present and contain valid setup, DMA is also

enabled, although the max mode is limited to UDMA33, as it is not known

what the chipset can do and how to program it.

 

The ata driver can change the transfer mode and various other parameters

when the system is up and running. See atacontrol(8).

 

The ata driver sets the maximum transfer mode supported by the hardware

as default. However the ata driver sometimes warns: ``DMA limited to

UDMA33, non-ATA66 cable or device''. This means that the ata driver has

detected that the required 80 conductor cable is not present or could not

be detected properly, or that one of the devices on the channel only

accepts up to UDMA2/ATA33.

 

Unknown ATAPI devices are initialized to DMA mode if the hw.ata.atapi_dma

tunable is set to 1 and they support at least UDMA33 transfers. Other-

wise they are set to PIO mode because severe DMA problems are common even

if the device capabilities indicate support. You can always try to set

DMA mode on an ATAPI device using atacontrol(8), but be aware that your

hardware might not support it and can potentially hang the entire system

causing data loss.

 

FILES

/dev/ad* ATA disk device nodes

/dev/ar* ATA RAID device nodes

/dev/acd* ATAPI CD-ROM device nodes

/dev/afd* ATAPI floppy drive device nodes

/dev/ast* ATAPI tape drive device nodes

/sys/i386/conf/GENERIC sample generic kernel config file for ata based

systems

 

NOTES

Please remember that in order to use UDMA4/ATA66 and above modes you must

use 80 conductor cables. Please assure that ribbon cables are no longer

than 45cm. In case of rounded ATA cables, the length depends on the

quality of the cables. SATA cables can be up to 1m long according to the

specification.

 

Static device numbering (enabled with the ATA_STATIC_ID kernel option)

reserves a number for each possibly connected disk, even when not

present. This is useful in hotswap scenarios where disks should always

show up as the same numbered device, and not depend on attach order.

 

SEE ALSO

ataraid(4), atacontrol(8), burncd(8)

 

HISTORY

The ata driver first appeared in FreeBSD 4.0.

 

AUTHORS

Søren Schmidt <sos@FreeBSD.org>.

 

FreeBSD 4.11 March 16, 2006 FreeBSD 4.11

Link to comment
Share on other sites
AlainTox714
AlainTox714
Posted
Posted

I agree the thread is dead, and either with 10.4.8 it doesn't work.

Like has said myzar when it works it's "Pure luck i guess, the error shows up randomly, the msg ata device blocking bus is the first symptom"

Sorry but my knowledge is inadequate to make it working, I just can help.

Link to comment
Share on other sites
kitkit
kitkit
Posted
Posted

I have compaq presario v3112au notebook and nvidia go 430 chipset.

It can run in VMware, but it can't boot in normal. (still waiting root device error)

 

I hope have new nforce sate drive to slove my problem.

Or need to edit appleviaata.kext ? Thank you very much !

Link to comment
Share on other sites
sambo60
sambo60
Posted
Posted

No I havent checked system.log. What kind of messages should I look for? It's a DFI nf4 ultra-d (modded to sli, should make no difference). Lots of disk activity. I installed ilife 06 (about 7gb) and it went totally smooth. The ilife programs open fast and everything is snappy. I did shut off hard drive sleep because it caused problems with my old install. The hard drive is a 160gb model I bout about 6 months ago (maybe a bit more). The manufacturer of the disk is Hitachi. Oh and I forgot to mention that I initially had trouble getting past the registration thing on the sata drive (the ide one worked fine, the sata one would keep going back to the welcome video), so I ended up importing my registration from my ide install and it worked fine on the sata hard drive since then. @ruku: your motherboard chipset is and nforce410 which I think may be slightly different than the nforce4 chip. Sorry its not working for you :D

Link to comment
Share on other sites
westep23
westep23
Posted
Posted
Didn't hamlo state he was using a DFI board also? Why would DFI be different than others?

 

 

No Hamlo uses Biostar NF4UL-A9 which is a ultra. Sambo please check you system log and see ig you get IOATADevice Blocking Bus error. Maybe time for me to get a new mobo.

Link to comment
Share on other sites
sambo60
sambo60
Posted
Posted

I think I do get that error, but it doesn't seem to have any negative effect on the performance of my system. I have also tried playing dvds and cds and they all work great. It could be that its not really working right, but I just haven't seen the problem yet. But I sure hope thats not the case, because I just ordered a new wireless card so I can get the full Mac os experience with internet.

Link to comment
Share on other sites
westep23
westep23
Posted
Posted

Yea your probley get coruption after awhile. But maybe not 2 week's is along time, I couldn't get thru an install without it chocking up. I bet if you ran md5sum against some files and then against some files in another os or on a ide drive. They will be diffrent.

Link to comment
Share on other sites
sambo60
sambo60
Posted
Posted

I can do that if you want. Just give me instructions. (its late at night) :tomato:

How big of a file should it be? Well I decided on the AMD dvd iso file. I am copying it now to my ide mac install using winxp and macdrive, and I will then boot into mac and copy the whole file from the ide drive to my sata drive using mac. Then I will go back to win and compare the sha1 or md5s using hashcalc.

Link to comment
Share on other sites
westep23
westep23
Posted
Posted

You don't have to. I already know they will be diffrent. Everytime you copy something and you get the error part of the file isn't being written. Just do yourself a favor and don't do any valuable work in mac os x. To check your md5, from a command line run md5 filename.file. Easiest way would be to check the md5 of a file on cd, then copy to hard drive and check again. Again this is just for your knowledge. We all already know the results.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...