Jump to content

planetbeing

planetbeing

Member Since 24 Feb 2006
Offline Last Active Feb 15 2010 09:18 PM
*****

Posts I've Made

In Topic: Discontinued

26 April 2008 - 07:06 AM

Hi, someone (selfdestruct) apparently successfully used one of the drivers here on their 0x0373. Unfortunately, after looking through the source in workaround.zip, I couldn't really find any significant changes from the version I posted years ago, other than switching to IOGatedOutputQueue and fixing that error with ReplaceOrCopyPacket failing and initializing nicTx. There are also some buffer size changes, but theoretically, our code should produce the same results. I had already made most of those changes myself, so I'm confused why forcedeth doesn't work for him whereas this driver does.

iNoob, would you mind taking me through some of the changes you made and what you had to fix to get it to work? I'm also confused on how you managed to use MikeNS's work if you have no source. Is that what enabled it to work for him?

Also, guys, on the GPL: The terms of the GPL license clearly states that with EVERY binary distribution of the work, the source code either must be included or a written offer to deliver the source code clearly stated. It doesn't matter if it's the "final release" or just a test, it only matters that something is being released. Unfortunately, MikeInNs has neither published the source code or a written offer to give the source code, so he technically is in violation of the GPL.

Now, I think it's clearly just an oversight! And if we got in touch with him, he'd probably be happy to give us the source... if we could get in touch with him. =P But I think it's important to publish the source code with every release (I have done that). With forcedeth based stuff, I even made it pretty easy. The XCode build script will automatically zip up everything as a last step, including the source code. The resulting distribution is less "neat" for end users, but I think it's worth it to keep stuff like this from happening.

iNoob and any other interested parties: I've setup a git repository here with the latest version of what I have: http://github.com/pl...osx/tree/master

It merges MeDevil's changes and a link change timer that hopefully will fix the issue for people being stuck on "network link down". The driver is quite stable on my machine with dual core and everything. The dual core issue was caused by the ReplaceOrCopyPacket bug. (Although I think yours and chuttenh's version of the fix is not quite ideal: on errors, you never reset the available bit on the packet so basically the NIC will think that packet is unavailable forever). I don't think there are any other stability related issues.

Anyway, PLEASE set up git and use this repository if you want to make changes to the code. Let's have one stable, good version of the driver for the entire family that always has all the bugfixes. :)

In Topic: Driver for nForce4 LAN

26 April 2008 - 06:14 AM

Would've been helpful to see the log. :/

In Topic: Ethernet adapter is recognized, but status = Cable Unplugged

25 April 2008 - 08:03 PM

Try:

sudo ifconfig en0 up

Where en0 is whatever the BSD name is of your ethernet interface. I had this issue when I was first testing my forcedeth driver for Leopard. Very weird and frustrating when you don't know what's going on.

Note: That command isn't a magic bullet or anything. It just will work in the unlikely event that OS X "forgot" to actually enable your ethernet interface.

In Topic: Driver for nForce4 LAN

25 April 2008 - 07:49 PM

Try this one. The version in dmesg should say 0.3c. I also fixed a stupid error in the one I gave you earlier and added diagnostic messages for the buffer size stuff that the other driver changed. The one that worked for you was what was in "workaroundsource.zip"?

Anyway, try this out and give me the dmesg. Thanks!

Opes: On the performance issue... That's really strange. On my computer, I can get both 2 MB/s upload and download sustained. That's through a university Internet connection and is unlikely to be matched by wi-fi. The gated I/O and indirect interrupts hurt performance somewhat, but theoretically the network would be the bottleneck, not the driver or NIC or the CPU. Hmmm. What kind of processor do you have? I guess it might be possible that the transmission rate is being limited by processor power.

In Topic: Driver for nForce4 LAN

25 April 2008 - 04:27 PM

wait, really? ok now im confused too... now im going to have to to some checking... :blink:

Ok this is the thread i got my driver from
http://forum.insanel...showtopic=89475

the 2nd one posted.

I was freezing on downloads, but after rebooting with cpus=1 im having no problems at all under Leo4Allv3

sorry for the confusion, and thanks for your help.


Thanks! After reading their code, it looks like there are only cosmetic changes from the current version of what I have, at least from what I can see. They use constants for the buffer sizes and so on. Except for one difference: In my program, I forget to initialize the nicTx variable to 0 and they did not. Looking at your log, that's why the driver fired off a packet before the link was even up. That might be the issue.

I'll fix the problem. Would you mind trying out the driver (I'll upload it later) to see if that was what the issue was?
© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy