Jump to content

Attansic L1 Driver Project


DaemonES
 Share

597 posts in this topic

Recommended Posts

i was thinking about this cause that was the only reason i didnt get a asus P5l-VM 1394. no driver support for the Gb LAN.

i may just pick one up so i can help you out.

I will let you know when that happens but it should be soon, a week or two.

Link to comment
Share on other sites

OK guys, I've attached current snapshot of the driver. It's not fully functional yet (it receives, but not transmits packets). All that I may know now how it communicates and setups hardware. Attansic L1 is very hard to program. To test driver you need 2 terminals:

1. In the first terminal type: tail -f /var/log/system.log

2. In the second enter to the driver directory and type sh loaddebug.sh

 

After some time you will see in the first screen messages from the driver. Post it here please.

AttansicL1Ethernet.zip

Link to comment
Share on other sites

Feb  4 18:49:46 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::start
Feb  4 18:49:46 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::createOutputQueue
Feb  4 18:49:46 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::getPacketBufferConstraints
Feb  4 18:49:46 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::atl1AllocateDescriptors
Feb  4 18:49:46 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::getHardwareAddress
Feb  4 18:49:48 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::atl1GetPermanentAddress
Feb  4 18:49:48 icys-computer kernel[0]: [AttansicL1Ethernet] Couldn't get device mac address
Feb  4 18:49:48 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::registerWithPolicyMaker
Feb  4 18:49:48 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::setPowerState
Feb  4 18:49:48 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::configureInterface
Feb  4 18:49:48 icys-computer kernel[0]: AttansicL1Ethernet: Ethernet address 00:00:d8:bc:ca:01

 

and then system hangs

Link to comment
Share on other sites

OK guys, I've attached current snapshot of the driver. It's not fully functional yet (it receives, but not transmits packets). All that I may know now how it communicates and setups hardware. Attansic L1 is very hard to program. To test driver you need 2 terminals:

1. In the first terminal type: tail -f /var/log/system.log

2. In the second enter to the driver directory and type sh loaddebug.sh

 

After some time you will see in the first screen messages from the driver. Post it here please.

 

Maybe I'm too stupid, after extract the zip file, it's not a kext and I don't really know how to deal with the files inside the folder...... Is ther any instruction I can follow? Thanks~~

Link to comment
Share on other sites

I have a pair of Corsair Twin2X modules, 2GB summary and Gigabyte GF7600GT video + titan driver.

I used this guide to get AD1988 sound working: http://forum.insanelymac.com/index.php?showtopic=32426

There are some strange sound appearance in movies and system clock running too fast, but this problems gone after I have added "fsb=266" to the kernel flags string.

Later I can try to boot with mikfi kernel.

Link to comment
Share on other sites

Hi!

 

I tested the driver on a friend's Asus M2N4-SLI board which has an Athlon 64 x2 and a newer nForce 4 chipset with an Attensic PHY which isn't detected by the forcedeth driver. With the original version of the AttansicL1Ethernet.kext I got no result, so I added the network adapter's id (0x005710de) to the plist inside the kext.

 

Result: the adapter was detected at the next reboot :) The kext seems to be really have fun detecting my adapter, at every reboot I got a new one :D But they all weren't working :poster_oops:

Another effect is that SATA wasn't working with the Attensic driver installed, after removing it I had my SATA back again.

 

Was a great begin, get on with it. My system was 10.4.7 myzar.

 

GreetinX from the Other Side!

Link to comment
Share on other sites

Good point about SATA controller. It seems, that it shares the same interrupt line with Attansic controller. Like here http://www.archivesat.com/Technical_discus...read2382776.htm

 

I've attached a new version of kext. Now I'm using MSI interrupts from PCI-E attansic controller. So those people who had problems with SATA driver please try.

 

Sooner or later I'll write this driver, I need only feedback and time.

AttansicL1Ethernet.zip

Link to comment
Share on other sites

Feb  5 00:09:51 icys-computer sudo:	  icy : TTY=ttyp2; PWD=/Users/icy/Desktop/AttansicL1Ethernet/build/Debug; USER=root; COMMAND=/bin/rm -rf /System/Library/Extensions.mkext
Feb  5 00:09:51 icys-computer sudo:	  icy : TTY=ttyp2; PWD=/Users/icy/Desktop/AttansicL1Ethernet/build/Debug; USER=root; COMMAND=/bin/rm -rf /System/Library/Extensions.kextcache
Feb  5 00:09:51 icys-computer sudo:	  icy : TTY=ttyp2; PWD=/Users/icy/Desktop/AttansicL1Ethernet/build/Debug; USER=root; COMMAND=/usr/sbin/chown -R root:wheel AttansicL1Ethernet.kext
Feb  5 00:09:51 icys-computer sudo:	  icy : TTY=ttyp2; PWD=/Users/icy/Desktop/AttansicL1Ethernet/build/Debug; USER=root; COMMAND=/usr/bin/find AttansicL1Ethernet.kext -type d -exec chmod 0755 {};
Feb  5 00:09:51 icys-computer sudo:	  icy : TTY=ttyp2; PWD=/Users/icy/Desktop/AttansicL1Ethernet/build/Debug; USER=root; COMMAND=/usr/bin/find AttansicL1Ethernet.kext -type f -exec chmod 0644 {};
Feb  5 00:09:51 icys-computer sudo:	  icy : TTY=ttyp2; PWD=/Users/icy/Desktop/AttansicL1Ethernet/build/Debug; USER=root; COMMAND=/sbin/kextload -t AttansicL1Ethernet.kext
Feb  5 00:09:56 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::init
Feb  5 00:09:56 icys-computer sudo:	  icy : TTY=ttyp2; PWD=/Users/icy/Desktop/AttansicL1Ethernet/build/Debug; USER=root; COMMAND=/usr/sbin/kextcache -k /System/Library/Extensions
Feb  5 00:09:56 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::start
Feb  5 00:09:56 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::createOutputQueue
Feb  5 00:09:56 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::getPacketBufferConstraints
Feb  5 00:09:56 icys-computer kernel[0]: [AttansicL1Ethernet] icr = ffffffff
Feb  5 00:09:56 icys-computer kernel[0]: [AttansicL1Ethernet] Error:Couldn't reset hardware
Feb  5 00:09:56 icys-computer kernel[0]: [AttansicL1Ethernet] Error:Couldn't init hardware
Feb  5 00:09:56 icys-computer kernel[0]: [AttansicL1Ethernet] MSI interrupt index 1
Feb  5 00:09:56 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::atl1AllocateDescriptors
Feb  5 00:09:56 icys-computer kernel[0]: [AttansicL1Ethernet] Allocated memory for ring header 18684
Feb  5 00:09:56 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::getHardwareAddress
Feb  5 00:09:58 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::atl1GetPermanentAddress
Feb  5 00:09:58 icys-computer kernel[0]: [AttansicL1Ethernet] Error:Mac address through SPI is invalid
Feb  5 00:09:58 icys-computer kernel[0]: [AttansicL1Ethernet] Couldn't get device mac address
Feb  5 00:09:58 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::registerWithPolicyMaker
Feb  5 00:09:58 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::setPowerState
Feb  5 00:09:58 icys-computer kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::configureInterface
Feb  5 00:09:58 icys-computer kernel[0]: AttansicL1Ethernet: Ethernet address 00:00:44:b4:4a:01

Edited by icy
Link to comment
Share on other sites

Here's my output from the new version (post 16):

 

Feb  5 07:50:16 comp1 kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::init
Feb  5 07:50:16 comp1 sudo:      : TTY=ttyp2 ; PWD=/AttansicL1Ethernet/build/Debug ; USER=root ; COMMAND=/usr/sbin/kextcache -k /System/Library/Extensions
Feb  5 07:50:16 comp1 kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::start
Feb  5 07:50:16 comp1 kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::createOutputQueue
Feb  5 07:50:16 comp1 kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::getPacketBufferConstraints
Feb  5 07:50:16 comp1 kernel[0]: [AttansicL1Ethernet] icr = ffffffff
Feb  5 07:50:16 comp1 kernel[0]: [AttansicL1Ethernet] Error:Couldn't reset hardware
Feb  5 07:50:16 comp1 kernel[0]: [AttansicL1Ethernet] Error:Couldn't init hardware
Feb  5 07:50:16 comp1 kernel[0]: [AttansicL1Ethernet] MSI interrupt index 1
Feb  5 07:50:16 comp1 kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::atl1AllocateDescriptors
Feb  5 07:50:16 comp1 kernel[0]: [AttansicL1Ethernet] Allocated memory for ring header 18684
Feb  5 07:50:16 comp1 kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::getHardwareAddress
Feb  5 07:50:17 comp1 kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::atl1GetPermanentAddress
Feb  5 07:50:17 comp1 kernel[0]: [AttansicL1Ethernet] Error:Mac address through SPI is invalid
Feb  5 07:50:17 comp1 kernel[0]: [AttansicL1Ethernet] Couldn't get device mac address
Feb  5 07:50:17 comp1 kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::registerWithPolicyMaker
Feb  5 07:50:17 comp1 kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::setPowerState
Feb  5 07:50:17 comp1 kernel[0]: [AttansicL1Ethernet] AttansicL1Ethernet::configureInterface
Feb  5 07:50:17 comp1 kernel[0]: AttansicL1Ethernet: Ethernet address 00:00:a8:3c:79:01

Link to comment
Share on other sites

I'll throw myself in as a tester. I have a P5L-VM 1394 and will test over this coming week.

 

Thanks for volunteering to do the work on this. The above board is great! I have 3 different boards and it is my favorite as far as stability, ease to mildly OC, speed (much faster than other 945G boards I've tried), has built in FW, and has a sound chip that one can easily get sound from.

 

If you can make the Ethernet port work, I would say this board would regain 1st place over ASrock 945G-DVI as the best board...it is certainly faster at identical speeds than the ASrock board.

 

Thanks again, and let's get the Ethernet working :thumbsup_anim:

Link to comment
Share on other sites

jester1o1 unfortunately I don't know how to make from Linux, maybe anybody can helps.

I think we can do several probs to know, what kind of registry mapping used by Attansic (I/O mapped or memory mapped).

I've attached a new kext. Please try.

 

icy thanks. It seems that this MSI interrupts may solve some problems with forcedeth driver and nForce4 USB.

 

Please try this version too.

AttansicL1Ethernet.zip

AttansicL1Ethernet.zip

Link to comment
Share on other sites

 Share

×
×
  • Create New...