glitch77 Posted February 17, 2008 Share Posted February 17, 2008 I am using iAtkos R3, with a Q6600, 4gb of ram, and an IN9 ABIT nforce 680i mobo. After Leo boots, networking works fine. I can use Safari, etc, but after about a minute, it just stops. If I go into networking properties, it shows that it has assigned its own IP and if I click "dhcp renew" the settings go away, then reset back to its own made up IP. The same card works in Vista64 (I am posting this message though it), so its not a bad card. What else could it be? Any suggestions on wha to try? Thanks! EDIT: I have tried setting the IP and DNS / router IPs manually, but it still won't connect. Link to comment Share on other sites More sharing options...
blackbird_n1 Posted March 16, 2008 Share Posted March 16, 2008 yeh I got the same problem Link to comment Share on other sites More sharing options...
kn3pp Posted March 18, 2008 Share Posted March 18, 2008 me too "leo4all" -distro tho .. Link to comment Share on other sites More sharing options...
pupdawg Posted March 19, 2008 Share Posted March 19, 2008 Well I have the same problems... I am now on the 5th card and starting to realize it has nothing to do with the card or the drivers. I've tried the a RTL8139 based card, a D-link GFE-530TX, D-lInk GDE-530T, Nforce Networking all have different drivers and work... I can connect to the internet but all will quit after a few min until I reboot. This has nothing to do with the card or drivers. Any one have any ideas? Link to comment Share on other sites More sharing options...
bushd Posted March 19, 2008 Share Posted March 19, 2008 Same here. When i use my Network intensivly (after about 50-70mb data transfer) the connection wents down, and thats it - no way to bring the network up again, except of rebooting. I tried four different network cards (Realtek, 3Com) and two complete different network settings - nothing. I tried to change the PCI Latency in the BIOS as suggested somewhere else, i used DHCP, manually... no effect at all. I also tried 2 different LeoOS86-Distris (Zeph 10.5.2 Rev.1 and eddie11c's Leo4all). I don't know what to do now, I need the network, and I need it for more than 50mb and a handfull of minutes. Anybody an idea? Link to comment Share on other sites More sharing options...
pupdawg Posted March 20, 2008 Share Posted March 20, 2008 After doing some tests I have discovered that by booting with cpus=1 fixes the network drop issue but disables 3 cores to do it. I'm going to swap out my AppleSMBIOS.kext and try a few combinations. Can anyone else verify that booting cpus=1 makes a difference for you? My system is 99% just need to get the issues worked out. Link to comment Share on other sites More sharing options...
blackbird_n1 Posted March 20, 2008 Share Posted March 20, 2008 yeh botting with cpus=1 solves that unstable network connection... but that isn't a good solution. I've already bought another card but that didn't helped out ether.. My system is perfect exept this problem Link to comment Share on other sites More sharing options...
pupdawg Posted March 20, 2008 Share Posted March 20, 2008 Yea I agree cpus=1 is no solution... I have a quad core and Leopard runs great with all 4 cores enabled. I'm not sure what the solution is but I think it have something to do with AppleSMBIOS.kext Please post here if anyone figures this one out... as will I. Link to comment Share on other sites More sharing options...
blackbird_n1 Posted March 22, 2008 Share Posted March 22, 2008 well I can't fix it, I've tried different ionetworking...kexts from my probook 10.5.2, and other dvds like kalyways or tohs .. but no fix at all Link to comment Share on other sites More sharing options...
Macshiba Posted March 22, 2008 Share Posted March 22, 2008 So what does cpus=1 do? Does that boot with only 1 core? Because I have a dual core, and if that's the only fix, then that's a really poor fix. Link to comment Share on other sites More sharing options...
demigod Posted March 22, 2008 Share Posted March 22, 2008 Guys mine works well.i have RTL8139 on Zep's AMD 10.5.2 rev 1 release.if you guys need any file. i can post it here and my Onboard LAN RTL8201 also works too Link to comment Share on other sites More sharing options...
Mysticus C* Posted March 22, 2008 Share Posted March 22, 2008 all these problems in my opinion are related to drivers... with the latest findings... why? bcoz all these card I myself, and many others were trying had drivers taht are written for 10.4.8 or earlier versions.... i dont think any of them are official either... most importantly, if you know the cpu=1 problem, it started after 10.4.8! which is parallel to the network problem... However these two cards lately... being tried under heavy usage and for long enough, are working good so far... Both cards have official OS X drivers and latest to support leopard... + Linksys WUSB54GC + Netgear WG111V3 wireless card Both these cards are wireless, I recommend Netgear if you can find, as I asked one person to stress test it, and seen it on action, and it worked perfectly and didnt have any more drops or freezes related to various programs anymore...... Good luck... Link to comment Share on other sites More sharing options...
chevy2410 Posted March 22, 2008 Share Posted March 22, 2008 I'm using a Realtek 8139 card and I don't have any issues at all. Interesting?? Chevy Link to comment Share on other sites More sharing options...
demigod Posted March 23, 2008 Share Posted March 23, 2008 actually i didn't installed any driver for RTL8139. just plugged in and started the pc.all set, internet was working.. Link to comment Share on other sites More sharing options...
KellyKelly Posted April 19, 2008 Share Posted April 19, 2008 guys, this issues only happens on nForce motherboard. Especially the 6 series. From what I heard, this is due to OS X compatibility with the nForce chipset. Link to comment Share on other sites More sharing options...
bushd Posted April 20, 2008 Share Posted April 20, 2008 i do not have a nForce motherboard and I have these problems. I cant remeber having these probs with Zeph 10.5.1 but i dont want do switch back due other problems vith 10.5.1 nobody any ideas? Link to comment Share on other sites More sharing options...
KellyKelly Posted April 26, 2008 Share Posted April 26, 2008 I just set the network toStatic IP instead of DHCP and I don't experience drop anymore. Link to comment Share on other sites More sharing options...
Denicio Posted June 24, 2008 Share Posted June 24, 2008 My case is very similar to the rest of you. I can confirm that the problem is on nForce610i in my case with a Realtek 8139 (Belkin). This connection loss never happened in 10.4.x but repeatedly occurs in 10.5.2 Leopard using Leo4All v3. I also searched the net and many "genuine" Mac users report that Leopard has networking issues (connection loss). I will try the cpus=1 fix and report here as well. UPDATE: Ok disabled second Core on the CPU, LAN works flawessly. QUESTION: Was any of you able to run Leopard with Vanilla Kernel? I can't do that with my processor and it might be one of the causes for the LAN problem. Link to comment Share on other sites More sharing options...
LTL Posted June 25, 2008 Share Posted June 25, 2008 I am using iAtkos R3, with a Q6600, 4gb of ram, and an IN9 ABIT nforce 680i mobo. After Leo boots, networking works fine. I can use Safari, etc, but after about a minute, it just stops. If I go into networking properties, it shows that it has assigned its own IP and if I click "dhcp renew" the settings go away, then reset back to its own made up IP. The same card works in Vista64 (I am posting this message though it), so its not a bad card. What else could it be? Any suggestions on wha to try? Thanks! EDIT: I have tried setting the IP and DNS / router IPs manually, but it still won't connect. Buy my network card for 15 bucks and disable your 8139 card. 8169 works natively Link to comment Share on other sites More sharing options...
gmind Posted July 2, 2008 Share Posted July 2, 2008 i have the same problem. now i am using the tulip driver and when the connection goes down, i do a kextunload tulip.kext and then a kextload tulip.kext and then i have connection for another 10 minutes. i also tried an older RTL LAN card but the same result. I have a also a nforce mobo. With an intergrated LAN card (nvidia gigabit ethernet). What i think is wierd, is that even thought i have the onboard lan disabled it was listed in the network preferences. can it be that we have these problem from having multiply lan boards? i really hope this get solved.. Link to comment Share on other sites More sharing options...
gmind Posted July 2, 2008 Share Posted July 2, 2008 UPDATE: cpus=1 really solves this problem. But do you really wanna live with it? Link to comment Share on other sites More sharing options...
Recommended Posts