404 replies to this topic

[stiffy]

tonyl, on Apr 27 2006, 11:16 AM, said:

Thanks a lot, works great in my P4P800-SE.

Thanks a lot, works great in my P4P800!

[link93300]

bonjour,

Moi je n'y arrive pas du tout help meeee pliz

[cyclonefr]

putain ta pas vu ? le guide d'install c débile tu copie le fichier ds
System/Bibliotheque/Extensions
ensuite répare les permissions et vire ds Bibliotheque les 2 fichiers extensions.mkext et .cache

[schrepfler]

Works with the 3COM 3C940 found on the ASUS P4P800 Deluxe. The Id of the device should be 0x170010B7 if anyone cares. Great job musashi, I can't say I've noticed anything strange but I don't really push the network stack on the MacOS.
PS. What is your assesment of the skge driver (the linux version)? Is it buggy or missing features that the hardware can do? If you do changes to it will you submit patches for the linux version?
Thanks and keep up the great work!
PS. Why not go with source code and project repository?

[m.musashi]

schrepfler, on Apr 28 2006, 05:44 PM, said:

Works with the 3COM 3C940 found on the ASUS P4P800 Deluxe. The Id of the device should be 0x170010B7 if anyone cares.

great thanks

dunno if linux skge has bugs; I just used the bits of code that interface with the hardware - everything else (descriptor and ring management, queues, interrupt handling, etc. are different and some are OSX specific)
for example, the UDP stalling bug I believe is actually an issue with the OSX stack
to be able to add new features I'd need the marvell yukon chip manual, but I don't have it (and even if I had it I'm not sure I'd have the time to try and test it)

as for the source, it will follow, but first I want to clean up a couple of more things

[rlepage]

A8V from Asus

THANKS!

[cyclonefr]

musashi r u working on other drivers?

[schrepfler]

Wouldn't it be usefull if we could create a list of device id's for the various versions of the chip so that they can all be supported without changeing the Plist. One driver that supports several devices like the ATIX1000 driver?
My deviceid is stated above, musashi could start adding them to the main comments and slowly adding them to the driver itself.
So if you guys have a id different that the shipped one or the ones mentions on the thread post your own (if musashi aproves).

[m.musashi]

guys, all of a sudden I'm having problems with v0.2b downloading large files from the net - basically it stops after few seconds, the network connection doesn't work anymore (although it still appears as linked and no error message) and I have to restart the driver
now, this started happening after I played around with some other drivers and I wonder if I screwed up something with my system or the driver is actually bugged (note that v1 works fine and downloads huge files at full speed without freezing)
any1 encountered the same error?

cyclonefr: nope, don't have other unsupported hardware to work on

[autoy]

I'm perfectly downloading big files no problem with 0.2b musashi. I fact I haven't had a single crash or freeze with this version, already tested for a couple of days non-stop.

[macprodan]

Same for me here,
when connection is under heavy use network freezes and then no longer works, until a reboot. !

[autoy]

itmandan, on Apr 30 2006, 08:34 PM, said:

Same for me here,
when connection is under heavy use network freezes and then no longer works, until a reboot. !

Are you using 0.2b? I got freezes with the previous kext but not with this one.

[macprodan]

yeah 0.2b

[autoy]

itmandan, on Apr 30 2006, 10:48 PM, said:

yeah 0.2b

Try to reproduce the network loss stressing the net traffic. After you get this error, open up a terminal and write: sudo dmesg

Paste the output of the networking errors here so musashi can take note.

Thanx

[najt]

I woke up today and my network was not working... it's working again after ifconfig down & ifconfig up. This is the only thing I found in the logs

May  1 00:40:52 orion kernel[0]: skgeosx ERR: kIOReturnOutputStall, txActiveCount = 124, txHead = 84, txTail = 88

[najt]

I just found out that my brother was copying a lot of large files over the LAN from my computer when this happened.

[m.musashi]

guys,
I'm working on fixing this bug(s)
I'm currently testing a new build, but it's a bit difficult to replicate the error at will

[m.musashi]

ok, one more bug fixed and this one was HUGE.
amazing it actually worked at all!!
now you can download ver 0.2d
if you guys can stress test it and report any issue, that would be great

I'm actually quite surprised that so few of you reported issues (out of hundreds of downloads). Go figure.

[oldschool]

m.musashi, on May 1 2006, 09:55 PM, said:

I'm actually quite surprised that so few of you reported issues (out of hundreds of downloads). Go figure.

Hi!

I had to install a new system. Your first release runs well.
I tried the first 0.2 and got probs. I´ll try 0.2d and be back...

Thanks for your work!

[autoy]

oldschool, on May 1 2006, 11:01 PM, said:

I had to install a new system. Your first release runs well.
I tried the first 0.2 and got probs. I´ll try 0.2d and be back...

It was the other way round for me... The first release was the worst and 0.2 was better. So far 0.2b was the best (not a single crash for almost a week) and now I expect 0.2d performing even better.