Help - Search - Members - Calendar
Full Version: Driver for nForce4 LAN
InsanelyMac Forum > OSx86 Project > Hardware and Drivers > LAN and Wireless
Pages: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
meatloaf
Hello

I to have just installed OSX x86 edition and was going throug the 3rd party drivers section of OSx86 project and thought wouldn't it be cool if some one made a site dedicated to 3rd party driver development for OSx86 edition. I would say the site could do the following

-Link to 3rd Party drivers for x86 OSX
-Link for source code for that driver
-Instructions to install the driver (though i would encourage developers to use the OSX installer for ease for everyone)

The kinds of drivers I was thinking were soundcards, wireless network, wired network, soundcards, video cards, sata controllers

I would be happy setup a site like that, but how many people can we get on board for developing the drivers (im no programmer, thoug i can do some php etc and we app stuff)
dcm
WOW nice one !!! thanks alot, usin Safari now tongue.gif

good job wink.gif

i thought i had error, apparently though it's working biggrin.gif

pc info:
nforce 4 giga lan, same device id ..0507 or something
OSX 10.4.6 wink.gif


heres what's in my log from just now..

un 10 02:31:05 mark-davids-computer kernel[0]: forcedeth: Initializing.
Jun 10 02:31:05 mark-davids-computer kernel[0]: forcedeth: Probing.
Jun 10 02:31:05 mark-davids-computer kernel[0]: forcedeth: Starting.
Jun 10 02:31:05 mark-davids-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0057, subsystem 0x1462:0x7125 opened.
Jun 10 02:31:05 mark-davids-computer kernel[0]: forcedeth: Mapped from 0xFE029000 of length 4096.
Jun 10 02:31:05 mark-davids-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x23baa000, tx at 0x23baa400, wired at 0x1d47000.
Jun 10 02:31:05 mark-davids-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:13:D3:9E:7F:C2.
Jun 10 02:31:05 mark-davids-computer kernel[0]: forcedeth: Found PHY 0x5040:0x0003 at address 1.
Jun 10 02:31:05 mark-davids-computer kernel[0]: com_triton_forcedeth: Ethernet address 00:13:d3:9e:7f:c2
Jun 10 02:31:05 mark-davids-computer launchd: Server 0 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[82]: exited abnormally: Hangup
Jun 10 02:31:05 mark-davids-computer configd[52]: posting notification com.apple.system.config.network_change
Jun 10 02:36:20 mark-davids-computer lookupd[175]: lookupd (version 369.5) starting - Sat Jun 10 02:36:20 2006
Jun 10 02:37:05 mark-davids-computer kernel[0]: forcedeth: Enabling... 1 2 3 4 5 6 7
Jun 10 02:37:05 mark-davids-computer kernel[0]: forcedeth: Starting transmit/receive engines
Jun 10 02:37:05 mark-davids-computer kernel[0]: forcedeth: Link speed now 100Mbps, code 0x10064.
Jun 10 02:37:08 mark-davids-computer configd[52]: WirelessAirPortDeviceNameCopy(): no AirPort driver found
Jun 10 02:37:08 mark-davids-computer launchd: Server 432f in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[175]: exited abnormally: Hangup
Jun 10 02:37:08 mark-davids-computer configd[52]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-network
Jun 10 02:37:08 mark-davids-computer configd[52]: posting notification com.apple.system.config.network_change
Jun 10 02:37:08 mark-davids-computer lookupd[181]: lookupd (version 369.5) starting - Sat Jun 10 02:37:08 2006
Jun 10 02:37:08 mark-davids-computer configd[52]: posting notification com.apple.system.config.network_change
Jun 10 02:37:08 mark-davids-computer lookupd[182]: lookupd (version 369.5) starting - Sat Jun 10 02:37:08 2006
Jun 10 01:37:10 mark-davids-computer configd[52]: target=enable-network: disabled


OTHER TERMINAL:
mark-davids-computer:~ mark$ cd ~/Desktop//forcedeth//build/Release/
mark-davids-computer:~/Desktop/forcedeth/build/Release mark$ sudo chown -R root:wheel forcedeth.kext
Password:
mark-davids-computer:~/Desktop/forcedeth/build/Release mark$ sudo chmod -R 755 forcedeth.kext
mark-davids-computer:~/Desktop/forcedeth/build/Release mark$ sudo kextload -v forcedeth.kext
kextload: extension forcedeth.kext appears to be valid
kextload: loading extension forcedeth.kext
kextload: forcedeth.kext loaded successfully
kextload: loading personalities named:
kextload: nForce 4 LAN
kextload: sending 1 personality to the kernel
kextload: matching started for forcedeth.kext
mark-davids-computer:~/Desktop/forcedeth/build/Release mark$ sudo kextunload -v forcedeth.kext
Password:

I decided to test it out at that stage tongue.gif

lol it prob not work if i restart
G-Force
QUOTE(dhess83 @ May 15 2006, 03:59 AM) *
So, from what I gather from this thread, there is no nForce 3 network driver yet?

Tried this driver today on my K8N Neo2 Platinum with nForce3 LAN (Marvell 8E1111 PHY), works great.
sgmbest12321
When i try to install it it doesnt work
Here is the full contents of the debug terminal

any ideas or thoughts would be helpful

I am using deadmoo's 10.4.1 image

i have a A8N-SLI (regular not deluxe or premium)

thanks
SGM
DrXenon
sgm, I have the same motherboard but I am using the JaS 10.4.6 image. It works flawlessly for me. Maybe it's time to upgrade to 10.4.6?
tigrou235
Hi,
First thank you very much for your work !!
On my PC this patch works, but when i reboot or when i shut down the and i launch the pc, i've to do again the manipulation/patch.
What have i to do ?
Enough thank you, it's very plain to do and it works; my problem it's just a to get my mac more comfortable.
Sorry for my english and thank you for your help
Tigrou

edit: oh yes, i'm on a A8N-SLI Premium with a 4400+ X2 and two 7800GTX PoV
MorningWood
I'm not running NF4, but rather 3 and still works. This is the only driver that has worked for me so far. THANK YOU SO MUCH!
gwlalonde
Well it's working on my A8N-SLI Deluxe, nvidia phy.

I had to use the -nockd.kext version. What is that version vs the others?

Many thanks.
fiXXXer
Thank you very much planetbeing I have a working ethernet on ASUS K8N & nForce3 250 chipset..

But, after few hours of downloading something via aMule, ethernet just stops. There are no errors panics etc but I can't even open web pages after few hours.. What is that any ideas? Is there anyone suffering from similar problem??
pupdawg
Hello... I've been so excited to use OSX on my PC almost there... I have an nForce 410 chipset and I'm tring to get the forcedeth drivers to work.

Many people are having luck but not me, I installed the driver and there is basicaly zero output from the driver... please see attached screenshot.

Any ideas... I have X-Code loaded now and I'm going to start digging for a solution so if anyone can point me in the right direction, thanks.
jape
You have to look at the system log after kextload.
Issue the "sudo dmesg" command on the Terminal, or open the Console application and select the system.log file.
pupdawg
Thanks but the first terminal in that screen shot shows the output of system.log there is nothing.

QUOTE(jape @ Jul 24 2006, 02:05 AM) *
You have to look at the system log after kextload.
Issue the "sudo dmesg" command on the Terminal, or open the Console application and select the system.log file.
jape
Oops. Maybe the network card device id has changed on nForce 410?

You may check this in Windows: Open Device Manager, right click your card, properties, details tab, and read.

In my A8N-E "NVNET_DEV0057" appears on the string.
pupdawg
My MSI board has the ID NVNET_DEV0269

can I just edit the kext info.plist to make this work??

I'm going to try that now anyway.

Thanks


QUOTE(jape @ Jul 24 2006, 10:03 AM) *
Oops. Maybe the network card device id has changed on nForce 410?

You may check this in Windows: Open Device Manager, right click your card, properties, details tab, and read.

In my A8N-E "NVNET_DEV0057" appears on the string.
pupdawg
One step closer... ok I added my ID's to the forcedeth.kext info.plist and now I get the following output that looks promising...

The MAC address is correct but I get a 169 IP address and no connection.

Jul 24 09:06:54 robert-computer kernel[0]: NMAC: family specific matching fails
Jul 24 09:06:54 robert-computer kernel[0]: forcedeth: Initializing.
Jul 24 09:06:54 robert-computer kernel[0]: forcedeth: Probing.
Jul 24 09:06:54 robert-computer kernel[0]: forcedeth: WARNING - your nVidia device 0x10DE:0x0269 is not known to work, but it could be supported in the future. Please contact the coder. Continuing anyway...
Jul 24 09:06:54 robert-computer kernel[0]: forcedeth: Starting.
Jul 24 09:06:54 robert-computer kernel[0]: forcedeth: PCI system 0x10DE:0x0269, subsystem 0x1462:0x7207 opened.
Jul 24 09:06:54 robert-computer kernel[0]: forcedeth: Mapped from 0xF9FDC000 of length 4096.
Jul 24 09:06:54 robert-computer kernel[0]: forcedeth: Allocated 3072 bytes of contiguous memory for DMA: rx at 0x22bf9000, tx at 0x22bf9400, wired at 0x5405000.
Jul 24 09:06:54 robert-computer kernel[0]: forcedeth: Found nForce4 LAN with MAC: 00:13:D3:EC:0A:07.
Jul 24 09:06:54 robert-computer kernel[0]: forcedeth: Found PHY 0x0000:0x0020 at address 1.
Jul 24 09:06:54 robert-computer kernel[0]: com_triton_forcedeth: Ethernet address 00:13:d3:ec:0a:07
Jul 24 09:06:54 robert-computer kernel[0]: forcedeth: Enabling... 1 2 3 4 5 6 7
Jul 24 09:06:54 robert-computer kernel[0]: forcedeth: Starting transmit/receive engines
Jul 24 09:06:54 robert-computer kernel[0]: forcedeth: Network link down.
Jul 24 09:06:56 robert-computer kernel[0]: forcedeth: Link speed now 100Mbps, code 0x10064.
Jul 24 09:07:01 robert-computer launchd: Server 0 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[88]: exited abnormally: Hangup
Jul 24 09:07:01 robert-computer configd[50]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-network
Jul 24 09:07:01 robert-computer configd[50]: posting notification com.apple.system.config.network_change
Jul 24 09:07:01 robert-computer lookupd[175]: lookupd (version 369.5) starting - Mon Jul 24 09:07:01 2006
Jul 24 09:07:01 robert-computer ntpdate[187]: can't find host time.apple.com\n
Jul 24 09:07:01 robert-computer ntpdate[187]: no servers can be used, exiting
Jul 24 09:07:01 robert-computer configd[50]: target=enable-network: disabled

UPDATE: I've also ran the forcedeth-nockd.kext and have attched the output...


QUOTE(pupdawg @ Jul 24 2006, 05:04 PM) *
My MSI board has the ID NVNET_DEV0269

can I just edit the kext info.plist to make this work??

I'm going to try that now anyway.

Thanks
pupdawg
SUCCSESS!!

Ok... what I did to make this all work.

First make sure your using the newest drivers... there are two posts with driver attachments in this thread the second one suggests that it is more current but it is the one attached to the first post that is newer... I also had to use the forcedeth-nockd.kext and edit the info.plist file in that package to add my nforce 410 ID's.

The nforce ID I have is 0269 if anyone would like to add them into the driver for the future smile.gif

After doing this everything is working fine... but I get a lot of debug output to the logs and can't seem to use the forcedeth-nock.kext as it say's it is not a valid package. <--- anyone know how to fix this ?

Thanks.
Aien
I have the problem where it assigns 169 ip address to my nic. I have tried all the different files in the builds section. If I need to post my log file just let me know. I have my comp connected to a Dlink router.
Ignacio
QUOTE(pupdawg @ Jul 25 2006, 12:55 PM) *
SUCCSESS!!

Ok... what I did to make this all work.

First make sure your using the newest drivers... there are two posts with driver attachments in this thread the second one suggests that it is more current but it is the one attached to the first post that is newer... I also had to use the forcedeth-nockd.kext and edit the info.plist file in that package to add my nforce 410 ID's.

The nforce ID I have is 0269 if anyone would like to add them into the driver for the future smile.gif

After doing this everything is working fine... but I get a lot of debug output to the logs and can't seem to use the forcedeth-nock.kext as it say's it is not a valid package. <--- anyone know how to fix this ?

Thanks.


What model of MSI motherboard do you have? I own the K8NGM2-L and would be great If I can make the onboard lan to work. BTW, I'm not sure what driver to download, so, can you please attach the one you're using ?
Thanks in advance.
mb2
QUOTE(pupdawg @ Jul 25 2006, 04:55 PM) *
SUCCSESS!!

Ok... what I did to make this all work.

First make sure your using the newest drivers... there are two posts with driver attachments in this thread the second one suggests that it is more current but it is the one attached to the first post that is newer... I also had to use the forcedeth-nockd.kext and edit the info.plist file in that package to add my nforce 410 ID's.

The nforce ID I have is 0269 if anyone would like to add them into the driver for the future smile.gif

After doing this everything is working fine... but I get a lot of debug output to the logs and can't seem to use the forcedeth-nock.kext as it say's it is not a valid package. <--- anyone know how to fix this ?

Thanks.
this sounds very promising... but what do u edit (exactly) and into where?

what i did:
-followed steps 1-3 (using zip attached to 1st post),
-followed steps 6-9 (replacing all forcedeth.kext referances with forcedeth-nockd.kext, and replacing both instances of 0057 with 0269 in info.plist in \forcedeth\build\release\forcedeth-nockd.kext package)
..which didn't work..

FYI i have a 410 mobo (biostar 6100)
Aien
QUOTE(mb2 @ Jul 27 2006, 11:17 PM) *
this sounds very promising... but what do u edit (exactly) and into where?

what i did:
-followed steps 1-3 (using zip attached to 1st post),
-followed steps 6-9 (replacing all forcedeth.kext referances with forcedeth-nockd.kext, and replacing both instances of 0057 with 0269 in info.plist in \forcedeth\build\release\forcedeth-nockd.kext package)
..which didn't work..

FYI i have a 410 mobo (biostar 6100)


I have the same mobo. What happens when you do the install?
pupdawg
The MB I use is the K8NGM2-L also... the biostar may not use the same ID's... use Device Manager in Windows and look up the NVIDIA nForce Networking Controller Properties and then Details Tab you'll see a reference of NVNET_DEVXXXX <---XXXX is your ID.

If you get a 169 address power down your system and unplug it from the wall for 30 sec... I think the forcedeth driver being used may suffer from the same ACPI bugs that the older Linux forcedeth driver did and after booting into windows and then back to Linux the driver would not work untel you remove the power to the card for 30 sec... you do need to unplug the power from the wall because most cards have wake on lan power even when the system is powered off.

QUOTE(mb2 @ Jul 28 2006, 05:17 AM) *
this sounds very promising... but what do u edit (exactly) and into where?

what i did:
-followed steps 1-3 (using zip attached to 1st post),
-followed steps 6-9 (replacing all forcedeth.kext referances with forcedeth-nockd.kext, and replacing both instances of 0057 with 0269 in info.plist in \forcedeth\build\release\forcedeth-nockd.kext package)
..which didn't work..

FYI i have a 410 mobo (biostar 6100)
Aien
QUOTE(pupdawg @ Jul 29 2006, 07:16 AM) *
The MB I use is the K8NGM2-L also... the biostar may not use the same ID's... use Device Manager in Windows and look up the NVIDIA nForce Networking Controller Properties and then Details Tab you'll see a reference of NVNET_DEVXXXX <---XXXX is your ID.

If you get a 169 address power down your system and unplug it from the wall for 30 sec... I think the forcedeth driver being used may suffer from the same ACPI bugs that the older Linux forcedeth driver did and after booting into windows and then back to Linux the driver would not work untel you remove the power to the card for 30 sec... you do need to unplug the power from the wall because most cards have wake on lan power even when the system is powered off.



Well I will try that. I didn't even know about that bug. I has the same ID as all 410 boards. Thanks
Aien
QUOTE(Aien @ Jul 29 2006, 11:40 AM) *
Well I will try that. I didn't even know about that bug. I has the same ID as all 410 boards. Thanks



Well I tried that and I am typing this from my mac os. biggrin.gif Now I just need to get my Vid to work better. LOL
sotl
thumbsup_anim.gif robot.gif idea.gif

Thanks A TON Planetbeing/Pupdawg for helping me get my ethernet up and running on my NForce 4 mobo (nvidia ethernet dev 0269).

After shutting down and unplugging my power cord for 30 seconds because DHCP was not assigning properly it all worked. I now respond from Camino browser gathering.gif

1 down, 2 to go (sound/graphics)
mb2
Aien/pupdawg; are my actions outlined in 'what i did' exactly the same as u did? (i'm still not sure of my editing for the device ID; but i do know my device ID is 0269.)
and nothing more? (i'm think i've read u have to do something else to get it to work after a restart.. but maybe i'm wrong..)

i'm not sure how i can find out weather i'm getting a 169 or not.. i dont think i ever got (doing what i outlined^^^) an NIC found in the system properties..

please make it 100% idiot-proof if possible, as it can get a little confusing/fustrating tongue.gif

..i'd like to know if i'm doing the right thing before i try again (with the 30s off..)
~thanks
Aien
QUOTE(mb2 @ Jul 30 2006, 01:12 AM) *
Aien/pupdawg; are my actions outlined in 'what i did' exactly the same as u did? (i'm still not sure of my editing for the device ID; but i do know my device ID is 0269.)
and nothing more? (i'm think i've read u have to do something else to get it to work after a restart.. but maybe i'm wrong..)

i'm not sure how i can find out weather i'm getting a 169 or not.. i dont think i ever got (doing what i outlined^^^) an NIC found in the system properties..

please make it 100% idiot-proof if possible, as it can get a little confusing/fustrating tongue.gif

..i'd like to know if i'm doing the right thing before i try again (with the 30s off..)
~thanks


Okay start off by turning you comp off and remove the power cord for 30 seconds. Then boot into Mac OS. Use the archive that I have attached here. From there fallow the directions outlined in the first post here, but use the forcedeth-nockd.kext file. To check your ip address. Just go to network in the system pref. If it works then you should beable to load a webpage. If you need anymore help be sure to ask.
mb2
Thanks Aien!!, Pupdawg and of course Planetbeing!
works great.. i'm now posting from OSX (and already had my first safari crash!, eek!)
now i can start actually using OSX.. (and need to figure out how to configure my 2nd router to work like a wireless card so i dont have to run a wire accross the whole house tongue.gif )
Aien
QUOTE(mb2 @ Jul 30 2006, 03:56 PM) *
Thanks Aien!!, Pupdawg and of course Planetbeing!
works great.. i'm now posting from OSX (and already had my first safari crash!, eek!)
now i can start actually using OSX.. (and need to figure out how to configure my 2nd router to work like a wireless card so i dont have to run a wire accross the whole house tongue.gif )


No problem. I must agree Thank you very much Planetbeing and all the other people in this board that helped.
pupdawg
Glad I could help some of you out... what kind of issues are you having after using the driver for a few days ? How often does it drop the connection and how often do you have to power off your system to get the IP back ?

Oh yes and thanks Planetbeing for getting this driver started smile.gif
Aien
Well I haven't had any real crashes, or needs to restart yet with it. So heres hope that it is pretty stable on my machine.
1233666666
I've been using it for a week now and it's fine (nF4 Ultra chipset, btw)

I've done BitTorrent on it, downloaded Xcode tools (950mb) and both maxed out my connection!

Good work!!
sjoer
Ok, first off im a linux user dont do windows smile.gif

I have a Gigabite NF4-SLI motherboard and I get no link from this driver with my network.

There is no second ethernetport and the drivers output doesnt say that much sad.gif

(my network cable is fairly long but if I hook it up with a 1m cable it doesnt get up aswell)


Maybe becouse my cheapy network here is just 10MBit?


QUOTE
Well, more precisely, I decided to blatantly rip off of the GPL'ed forcedeth driver for Linux, which someone had mentioned earlier (but I had a really difficult time getting a copy of the source code on Google, I only managed to get several old versions so far). But I figured 2000 odd lines of code isn't too unreasonable and I could figure it out mostly, and also figure out enough of OS X's innards so I can port it.


You know you can get the kernel sources from http://kernel.org/? (its the upper most link wink.gif)

No google needed smile.gif
sotl
QUOTE(pupdawg @ Aug 1 2006, 11:34 PM) *
Glad I could help some of you out... what kind of issues are you having after using the driver for a few days ? How often does it drop the connection and how often do you have to power off your system to get the IP back ?

Oh yes and thanks Planetbeing for getting this driver started smile.gif



It's actually kinda funny. Windows recently started unplugging my network connection many minutes after bootup and I'm using the official nforce driver from nvidia's site. blink.gif Planetbeing's homebrew driver has worked flawlessly since the day I put my hardware ID in it.

It got to the point where I couldn't finish a download or bittorrent so I did a system restore and wouldn't you know it?... Windows wont boot anymore because of a missing/corrupt hal.dll file (which IS in the system32 folder which I THEN replaced with a dll from dlldump.com using the repair console). And because I bought a store display I don't have the winxp cd, so I'm screwed... hysterical.gif

o well, there is always happymac.GIF

btw, I only have to unplug the power cord if I go from Windows to OS X. Otherwise it's fine.
sotl
I see dozens, hundreds of these entries when I boot up, shutdown, or pull up the log in terminal, Is that normal? in log it keeps going... if it is normal is there a way to silence the beast?

Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:43 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:43 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:43 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aien
QUOTE(sotl @ Aug 5 2006, 10:29 AM) *
I see dozens, hundreds of these entries when I boot up, shutdown, or pull up the log in terminal, Is that normal? in log it keeps going... if it is normal is there a way to silence the beast?

Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:42 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:43 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:43 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e
Aug 5 12:25:43 carlos-computer kernel[0]: forcedeth: packet 80000000 - 8000062e


Thats normal, because you are using the forcedeth-nockd.kext. It dump a bunch of stuff in to your log file. The only real way is to edit forcedeth.kext and add your hardware ids, but I haven't been able to get that one to work with my nic.
letni
Guys,

For those who have a Nforce 410/430 board (with the Marvel PHY, not Vietese PHY) I have recompiled the forcedeath-nockd.kext to not output any debug system log output since the forcedeath-nock.kext isn't a valid kernel extension in this build.

So use this if you have forcedeath-nockd.kext working, but don't want your systemlog to fill up from all the debug crap...

This was compiled with Xcode 2.3

Letni...
Aien
QUOTE(letni @ Aug 6 2006, 12:51 PM) *
Guys,

For those who have a Nforce 410/430 board (with the Marvel PHY, not Vietese PHY) I have recompiled the forcedeath-nockd.kext to not output any debug system log output since the forcedeath-nock.kext isn't a valid kernel extension in this build.

So use this if you have forcedeath-nockd.kext working, but don't want your systemlog to fill up from all the debug crap...

This was compiled with Xcode 2.3

Letni...


Hey man, thanks very much. No more overloaded log files.
mb2
thanks letni.. (assuming it works, i haven't tried it but should if it works for aien)..

as to pupdawg, i've also not had any issues or dropouts using it.. the only issues were the log, and the power off requirement.

I don't use the lan in windows (use wireless).. so, is it possible to prevent the issue; iirc disabling it in device manager doesn't work, or does it? or is there some other way?
matriculated
Thanks guys! This edited version (along with powering down for 30 seconds) now works on my a8n-vm csm. The OPs drivers didn't work and I had lost hope. Out of all the things that don't work on this board (video, sound, network), this was the most important to me. I can live with using 1024x768 but having a computer with no internet is useless to me. Had I known about running OSX on x86 before I had to rebuild my system I would've bought the right components. smile.gif Next up, sound!
letni
Planetbeing - What kernel source tree did you build this driver off of? I would like to try to figure out the whole reboot from windows problem.. It's annoying smile.gif

Thanks

LetnI
sotl
Ooooo new nockd kext.. Nice LetnI! Can't wait to try it! Stupid Windows had a temper tantrum and wont boot or let me boot OS X either thumbsdown_anim.gif Once I set my OS X partition active in Acronis I'll take 'er for a whirl biggrin.gif
Trens
I've used the forcedeth6100.zip from Aien in combination with the fixed forcedeth from Letni, to get mij onboard networkchip functioning. When I Install it as discribed in the OP I see it is working. I get an IP adress, I can visit weppages, etc... But after a reboot the system seems it has forgot the whole thing. I think something is going wrong in the installation part (step 13 & 14 of the OP) but I can't see what. Any ideas?

I am using OSX 10.4.6 (the JaS one) by the way
letni
QUOTE(Trens @ Aug 10 2006, 01:46 AM) *
I've used the forcedeth6100.zip from Aien in combination with the fixed forcedeth from Letni, to get mij onboard networkchip functioning. When I Install it as discribed in the OP I see it is working. I get an IP adress, I can visit weppages, etc... But after a reboot the system seems it has forgot the whole thing. I think something is going wrong in the installation part (step 13 & 14 of the OP) but I can't see what. Any ideas?

I am using OSX 10.4.6 (the JaS one) by the way


Well, couple of things you need to remember..

1. After booting windows and back to MacOS X, these drivers will load but most likely won't work unless the PC has been completely powered off (power cable unplugged for a few seconds)

2. If the kext isn't loading after boot (sudo kextstat |grep -i "forcedeth") then you need to flush your kext cache by

sudo rm -R /System/Library/Extensions.mkext
sudo rm -R /System/Library/Extensions.kextcache
sudo kextcache -k /System/Library/Extensions

from a shell...

Hope this helps...
Trens
I've been working on my litle problem again, but not succesfull. The way I get it working now is:
  1. cd ~/Desktop/forcedeth/build/Release
  2. sudo chown -R root:wheel forcedth-nock.kext
  3. sudo chmod -R 755 forcedeth-nock.kext
  4. sudo kextload -v forcedeth-nock.kext
But after a reboot I have to type it in again. sudo cp -R forcedeth-nock.kext /system/library/extentions seems to do not a thing at all.
I don't use the tail -f /var/log/system.log anymore, because I could not reboot after using it.

Regarding your help, I have a dedicated disk (without windows) so no problem from that side. I had a unexpected IP number (something like 169?) but that has been solved earlier.
It seems that the kext isn't loading after a reboot, but I can't quite understand your help at number 2. How, instead of what and when do I use it?

QUOTE(letni @ Aug 10 2006, 05:53 AM) *
Well, couple of things you need to remember..

1. After booting windows and back to MacOS X, these drivers will load but most likely won't work unless the PC has been completely powered off (power cable unplugged for a few seconds)

2. If the kext isn't loading after boot (sudo kextstat |grep -i "forcedeth") then you need to flush your kext cache by

sudo rm -R /System/Library/Extensions.mkext
sudo rm -R /System/Library/Extensions.kextcache
sudo kextcache -k /System/Library/Extensions

from a shell...

Hope this helps...
Trens
I solved the problem on my own. I made a mistake in typing in the right command. Extentions instead of Extensions.

QUOTE
But after a reboot I have to type it in again. sudo cp -R forcedeth-nock.kext /system/library/extentions seems to do not a thing at all.


Next the soundcard issue...
AlienHrGig
cheers
i am in need of some assistance.
i realy have no idea what ele to try.

i tried the second posted drivers with my hardware id on the (the forcedeth_nockd.kext),and i tried out the letni "forcedeth_nock_fixed.zip" kext because it has already my hardware id in it
it loads without a problem, my ethernet adaptor can now be cheked as active.

i activated it and let it in default setings to fetch an ip trough DHCP where it says "configure IPv4"
it does not fetch an ip and the light on the ethernet port doesent light up

so i tried to force an ip adress on it
i forced it to an ip that matches my network server that is using XP (192.168.0.7) with the proper subnet mask and i tried giving my server adress in the router option, the DNS server and without any info on those fields.
when i trie to force the ip on the ethernet adapter if i go to the network status it says "The cable for built-in ethernet is not pluged in", wich makes sense since the light isnt on.

so i tried out the power down for 30sec disconecting from the plug.
it does exactly the same, cable disconected without any light.
i am completely lost, and dont know what to do.

my ethernet adapter is built in on the board, the board is the following "Asus M2NPV-MX GeForce 6150 SKAM2"
my ethernet is the following "NVIDIA nForceŽ 430 built-in Gigabit MAC with external Marvell PHY"

please help me out, if you need any more information about any of the hardware just say so. i just need some light on how to get it up and working. there are several people saying they have theyr Marvell PHY's working but mine just sais i have the network cable unpluged and it makes no sense.

thanks in advance
Aien
QUOTE(AlienHrGig @ Aug 11 2006, 01:21 PM) *
cheers
i am in need of some assistance.
i realy have no idea what ele to try.

i tried the second posted drivers with my hardware id on the (the forcedeth_nockd.kext),and i tried out the letni "forcedeth_nock_fixed.zip" kext because it has already my hardware id in it
it loads without a problem, my ethernet adaptor can now be cheked as active.

i activated it and let it in default setings to fetch an ip trough DHCP where it says "configure IPv4"
it does not fetch an ip and the light on the ethernet port doesent light up

so i tried to force an ip adress on it
i forced it to an ip that matches my network server that is using XP (192.168.0.7) with the proper subnet mask and i tried giving my server adress in the router option, the DNS server and without any info on those fields.
when i trie to force the ip on the ethernet adapter if i go to the network status it says "The cable for built-in ethernet is not pluged in", wich makes sense since the light isnt on.

so i tried out the power down for 30sec disconecting from the plug.
it does exactly the same, cable disconected without any light.
i am completely lost, and dont know what to do.

my ethernet adapter is built in on the board, the board is the following "Asus M2NPV-MX GeForce 6150 SKAM2"
my ethernet is the following "NVIDIA nForceŽ 430 built-in Gigabit MAC with external Marvell PHY"

please help me out, if you need any more information about any of the hardware just say so. i just need some light on how to get it up and working. there are several people saying they have theyr Marvell PHY's working but mine just sais i have the network cable unpluged and it makes no sense.

thanks in advance

What is your device id? Because my mod for the driver is for the NVIDIA nForce 410 Built-in 10/100 MAC. I believe the the external part is Realtek. So look in windows and check on your hardware id. If it is the same then I am not sure what your problem, if it is not the same and you need help changing it just ask.
AlienHrGig
my device id is {1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0269\4&2806F0ED&0&01

and my hardware id is{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0269

so i am guessing that the driver is ok, because it is DEV0269 right?
pupdawg
You should use lspci to find out your nForce device ID's then install with the instructions posted in past posts.


QUOTE(sjoer @ Aug 5 2006, 04:45 AM) *
Ok, first off im a linux user dont do windows smile.gif

I have a Gigabite NF4-SLI motherboard and I get no link from this driver with my network.

There is no second ethernetport and the drivers output doesnt say that much sad.gif

(my network cable is fairly long but if I hook it up with a 1m cable it doesnt get up aswell)
Maybe becouse my cheapy network here is just 10MBit?
You know you can get the kernel sources from http://kernel.org/? (its the upper most link wink.gif)

No google needed smile.gif
Aien
QUOTE(AlienHrGig @ Aug 11 2006, 03:21 PM) *
my device id is {1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0269\4&2806F0ED&0&01

and my hardware id is{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0269

so i am guessing that the driver is ok, because it is DEV0269 right?

Based on that I would say yes, but try what pupdawg asked you to do. Then see what your device ID is.
if its the same then again I don't know what to do. If not then we will add the new dev id to the drivers and then it should work. Did you try with just my mod first, or did you use mine and then Letni's? If you did the later then try mine first and if that works then try Letni's.

QUOTE(pupdawg @ Aug 11 2006, 04:35 PM)
You should use lspci to find out your nForce device ID's then install with the instructions posted in past posts.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.