InsanelyMac Forum > Realtek 8168/8111 solution

junior

Dec 29 2007, 12:25 PM

Hi

Im realy new and i installed mac and everything (exept my sound because its a SB Live!

wish it worked) is supported...

But..

I downloaded the folder "RealtekR1000" with al files in...
Now this is what i read and what i do step by step to install...

>sudo -s
>my password
>sudo mv /users/koen/desktop/RealtekR1000.kext /System/Library/Extensions
>sudo chmod -R 775 /system/Library/Extensions/RealtekR1000.kext
>sudo chown -R root:wheel /system/library/Extensions/RealtekR1000.kext

Then i go to /System/library/ and there i remove 'Extensions.cachekext' and 'Extensions.mkext'.
Then i reboot and it works..

Problem is.. I Have to do this every time i reboot my Computer...

Can anyone say me what i have to do to get this working forever....?

In my map i found files like installrelease.exec and so on and so on.. I think this is like .exe in windows,
but how i use the file... ?
Sorry for noob-questions;)

Gtrz, and thanx!

Koen

overloade

Dec 30 2007, 11:22 AM

QUOTE(Me123 @ Nov 9 2007, 01:49 AM)

Realtek R8111/8168 works for me in Leopard (Mainboard: Gigabyte P35-DS3P).
If you are a windows user, make sure to enable "Wake on lan after shutdown" in the advanced tab of your network card driver settings dialog (at least for WinXP, no idea if this also applies to Vista)

This trick really works, I tried this with my XP, then reboot to Leopard, the ethernet works like magic.
Thanks Me123.

STRESSY

Dec 31 2007, 06:08 AM

hi, i have this ethernet card and everythin works great in leopard with RTG 1.1.6 but when i start torrenting in azureus or transmission i lose my internet connection.. i still have lan connection but no signal of internet.. if i quit the bittorrent client internet starts working again

any ideas?

fellow

Jan 7 2008, 02:01 PM

Hi everybody !

Thanks for everything !

I juste have a problem with my system. I installed a 10.4.8 JaS intel version of Mac OS and my gigabit network card doesn't want to work properly. Let me explain the problem. I had a D-Link DGE528T with a DLink chipset. This card never came up, so a friend gave me a Realtek with a 8169S chipset and miraculously, this card seems to work. But there is a major problem, it does not detect that i connect the cable to the gigabit switch.

I don't understad what i am supposed to install...

Can someone help me?

Thank you very much !

Andr3s

Jan 14 2008, 10:15 PM

Hey people!

I need some help, please! I have a Realtek 8168/8111 and i cant connect to ethernet! I just cant, how can i do? what can i do? i already downloaded the two zip files, one from daemones "RTLxxx_1.02" and the other one "RealtekR1000_1.04" but i dont really know how to run it... i need some good help on this one! I'm lost because im new on this stuff!I'd be really thanked if someone could tell me what to do!

Rwild

Jan 18 2008, 01:46 PM

Wow!!! Thanks so much for the release and the installer!

It works great on my MSI K8T NEO FIS2R board with the 8110S Ethernet.

mtotho

Jan 19 2008, 08:32 PM

I ran "sh installrelease" and it appeared work.. but i go into network settings and i see that it gave itself a home ip instead of LAN. How do i fix this?

Also Neo, your site isnt working.

Nullius

Jan 31 2008, 01:08 AM

I'm having trouble with the drivers.
The kext loads perfectly, but I can't seem to get a connection. The status led on my motherboard isn't flashing either.

Any idea's ?

Tnx a lot

Gantlett

Feb 5 2008, 07:32 PM

I have a GA-P35C-DS3R Rev. 2.0 motherboard with a Realtek 8168B/8111B built-in PCI-E Ethernet adapter.

I installed Kalyway's 10.5.1 a week ago. Ethernet worked out of the box, until yesterday when Ethernet just stopped working all of a sudden. It kept saying "Cable Unplugged" in Network prefs.

So I tried installing the R1000 v1.04 package, but after restarting I got a message upon logging in saying that the R1000 kext cannot be used and therefor it will be unloaded by the system.

I uninstalled it (just dumped the kext) and installed Realtek's own "RTGMac_v1.1.6" driver.

This driver works, but when I go into "Advanced" in Network prefs the computer completely crashes - colored wheel starts spinning and nothing works. I have to press the power button to shut the computer down.

Any help will be greatly appreciated. Thanks.

dacho

Feb 8 2008, 09:35 AM

QUOTE(overloade @ Dec 30 2007, 11:22 AM)

This trick really works, I tried this with my XP, then reboot to Leopard, the ethernet works like magic.
Thanks Me123.

Same here. What I have done is I installed leopard 10.5.1 then windows and after windows installation nic stopped working and the above mentioned fix actually fixed. Now it is back to normal.

Thanks for the info

dali

ovof

Feb 10 2008, 02:47 PM

Hi great daemonES, i try to add magic wake on lan, so i add within configlock, in initHw,

WriteMMIO8(Config1, ReadMMIO8(Config1) | PMEnable);
WriteMMIO8(Config3, ReadMMIO8(Config3) & LinkUp | MagicPacket);
WriteMMIO8(Config5, ReadMMIO8(Config5) | PMEStatus | LanWake | BWF | MWF | UWF);

So when i first kextload, no wakeonlan, so i kextunload, then load again, and tada it works

But why out of hell, do i need to load/unload kext once, before it works ???? any idea Help

inedible

Feb 11 2008, 04:43 AM

I'm having a bit of a problem with this driver... Seems it interferes with ps2 devices somehow.

for some reason when I install it, my mouse will behave erratically... In the middle of using it, it will shoot off in a random direction and start clicking.... Or, I'll be in the middle of typing something and it will get stuck on a letter and just keep repeating, at which point my mouse no longer works and the only thing that's responsive is the power button - but of course I can't click shutdown or even hit enter since one of my keys is stuck, it just keeps beeping at me. I've also had it freeze where it's not apparent that a key is stuck, it just acts frozen.

Oddly enough, it starts doing this as soon as the kext is in the extensions folder, even before I have a chance to chown, chmod, and delete my caches... and it continues to have this problem even after I've kextunload'ed it. The only solution is to delete the kext in single user mode and everything goes back to normal.

I've tried the release, as well as the debug... the debug one only started doing it after I'd typed loaddebug, but kept doing it after restart. I've also tried recompiling it using xcode since I'm using leopard and I thought that might be the problem. (made absolutely no difference)

No errors to speak of.. save for dependencies on com.apple.something and kpi.apple.something, use only one style. (or something)... but I've had that come up with working drivers too, and I think it's irrelevant.

I'm using a toshiba satellite u300 laptop, with a Realtek 8101, apparently on the pci-e bus of my laptop.
After installing I get an "ethernet" in network configuration and an "en0" in ifconfig, though my mac address is 00:00:00... and it always says the cable is unplugged.

Windows says it's an 8101 family, but I'm inclined to believe it's an 8169. here's what windows says: Realtek RTL8101 Family PCI-E Fast Ethernet NIC; ven 10ec dev 8136

Help!

inedible

Feb 11 2008, 09:32 AM

Ok, so I've found the relevant section in system.log...

This starts just after the installdebug script finishes.. and cuts off at the end where I had to hold down the power button.

CODE

Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::init(OSDictionary *properties)
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::start(IOService *provider)
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::createWorkLoop()
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::getWorkLoop()
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::createOutputQueue()
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::getWorkLoop()
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::getPacketBufferConstraints(IOPacketBufferConstraints *constraints) const
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] mmio/pio base 0x0000
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] Couldn't setup memory io
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] Forcing to port IO
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] mcfg 1, pcfg 3
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] Chip RTL8169 detected
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] MAC address: 00 00 00 00 00 00 
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] PHY config
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] Set MAC Reg C+CR Offset 0x82h = 0x01h
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: [RealtekR1000] Set PCI Latency=0x40
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: ApplePS2Keyboard: Unexpected resend request from PS/2 controller.
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: ApplePS2Keyboard: Unexpected acknowledge from PS/2 controller.
 Feb 10 12:16:00 ryans-mac-pro kernel[0]: ApplePS2Keyboard: Unexpected resend request from PS/2 controller.
 Feb 10 12:16:01: --- last message repeated 1 time ---
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] Link Status: Not Linked
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: ApplePS2Keyboard: Unexpected resend request from PS/2 controller.
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::R1000InitEventSources()
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::getWorkLoop()
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::newVendorString() const
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::newModelString() const
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::getHardwareAddress(IOEthernetAddress *addr)
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::registerWithPolicyMaker(IOService *policyMaker)
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::configureInterface(IONetworkInterface *interface)
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::setPowerState(unsigned long powerStateOrdinal, IOService *policyMaker)
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: rtl_r1000_nic_ext: Ethernet address 00:00:00:00:00:00
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::enable(IONetworkInterface *netif)
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] setActivationLevel 2
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] Selected medium is NULL, forcing to autonegotiation
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::selectMedium(const IONetworkMedium *medium)
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: [RealtekR1000] index 6
 Feb 10 12:16:01 ryans-mac-pro kernel[0]: ApplePS2Keyboard: Unexpected resend request from PS/2 controller.
 Feb 10 12:16:02: --- last message repeated 3 times ---
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: [RealtekR1000] bool RealtekR1000::R1000OpenAdapter()
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: ApplePS2Keyboard: Unexpected resend request from PS/2 controller.
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: [RealtekR1000] Set MAC Reg C+CR Offset 0xE0: bit-3.
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::setMulticastMode(bool enabled)
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::setMulticastList(IOEthernetAddress *addrs, UInt32 count)
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::setMulticastMode(bool enabled)
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: [RealtekR1000] mbuf_len 342, packet_len 342
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: [RealtekR1000] cur_tx 1, dirty_tx 0, buf_len 342
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::selectMedium(const IONetworkMedium *medium)
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: [RealtekR1000] index 0
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: ApplePS2Keyboard: Unexpected resend request from PS/2 controller.
 Feb 10 12:16:02: --- last message repeated 3 times ---
 Feb 10 12:16:02 ryans-mac-pro configd[40]: PMSettingsPSChange() AC Power
 Feb 10 12:16:02 ryans-mac-pro kernel[0]: ApplePS2Keyboard: Unexpected resend request from PS/2 controller.
 Feb 10 12:16:12: --- last message repeated 1 time ---
 Feb 10 12:16:12 ryans-mac-pro kernel[0]: [RealtekR1000] RealtekR1000::R1000TxTimeout(OSObject *owner, IOTimerEventSource * timer)
 Feb 10 12:16:12 ryans-mac-pro kernel[0]: [RealtekR1000] Set MAC Reg C+CR Offset 0xE0: bit-3.

those "unexpected request from ps2 controller" are what's killing me... anyone know what might cause that?

let me know if there's any other logs I should post.

inedible

Feb 13 2008, 11:27 PM

bump...

is this what people refer to as "mouse tearing"?

LTL

Feb 14 2008, 12:45 PM

QUOTE(DaemonES @ Oct 5 2006, 09:41 PM)

Hi guys.
More than one weak ago I\'ve started writing driver for Realtek controllers. At this time I have some results, I've not tested all features, cause I have no such opportunity, but MacOS successfully communicate with WinXP system through my driver.
It works on RTL8169, RTL8168, RTL8110, RTL8111, RTL8100, RTL8101 chips and their modifications.

I have some driver programming skills under WinXP, but MacOS and IOKit are new things for me, so be careful when using my driver. You can freely load it and unload, but only once at one system boot (cause more loads may cause system crash, I\'m planning to fix it). Use sh scenarios for loading/unloading driver.

Now I\'m planing to add such features:
- Manual MTU control (now it fixed at 1500).
- Jumbo frame support.
- Wake on magic packet.

Thanks to the:
- author of Linux R1000 driver.
- NeoPheus for installer. Great job, thanks.

Share your knowledge so much as you can.

Compiled with XCode 2.4 on OSX 10.4.6 JaS Install DVD.
Visit to project page for the latest driver and installer.
https://sourceforge.net/projects/realtekr1000/

Great work... installed today and things seem to be running much better, but toward the end of the day I started to see errors like this in my log (same errors i was getting before sadly):

PS- I am using dot mac, back to my mac

Any suggestions?

2/14/08 7:19:12 PM mDNSResponder[15] Permission denied (NOAUTH): HEATER._ssh._tcp.drezd.members.mac.com.
2/14/08 7:19:12 PM mDNSResponder[15] Error -65537 for refresh of service HEATER._ssh._tcp.drezd.members.mac.com.
2/14/08 7:19:50 PM mDNSResponder[15] Permission denied (NOAUTH): HEATER._rfb._tcp.drezd.members.mac.com.
2/14/08 7:19:50 PM mDNSResponder[15] Error -65537 for refresh of service HEATER._rfb._tcp.drezd.members.mac.com.
2/14/08 7:22:21 PM mDNSResponder[15] Permission denied (NOAUTH): _autotunnel._udp. HEATER.drezd.members.mac.com.
2/14/08 7:22:21 PM mDNSResponder[15] hndlRecordUpdateReply: Registration of record _autotunnel._udp. HEATER.drezd.members.mac.com. type 33 failed with error -65537
2/14/08 7:26:44 PM mDNSResponder[15] Unable to refresh LLQ _afpovertcp._tcp.drezd.members.mac.com. (PTR) - will retry in 250 minutes
2/14/08 7:26:44 PM mDNSResponder[15] Unable to refresh LLQ _rfb._tcp.drezd.members.mac.com. (PTR) - will retry in 250 minutes
2/14/08 7:26:44 PM mDNSResponder[15] Unable to refresh LLQ _dm-notification._udp.drezd.members.mac.com. (TXT) - will retry in 250 minutes
2/14/08 7:29:45 PM mDNSResponder[15] Permission denied (NOAUTH): AutoTunnel-02-1A-4D-FF-FE-5F-06-08.drezd.members.mac.com.
2/14/08 7:29:45 PM mDNSResponder[15] hndlRecordUpdateReply: Registration of record AutoTunnel-02-1A-4D-FF-FE-5F-06-08.drezd.members.mac.com. type 1 failed with error -65537
2/14/08 7:29:47 PM mDNSResponder[15] Permission denied (NOAUTH): HEATER._device-info._tcp.drezd.members.mac.com.
2/14/08 7:29:47 PM mDNSResponder[15] hndlRecordUpdateReply: Registration of record HEAT._device-info._tcp.drezd.members.mac.com. type 16 failed with error -65537
2/14/08 7:30:45 PM com.apple.RemoteDesktop.PrivilegeProxy[135] mach_msg_server: (ipc/send) invalid memory
2/14/08 7:31:11 PM mDNSResponder[15] Permission denied (NOAUTH): HEATER._sftp-ssh._tcp.drezd.members.mac.com.
2/14/08 7:31:11 PM mDNSResponder[15] Error -65537 for refresh of service HEATER._sftp-ssh._tcp.drezd.members.mac.com.
2/14/08 7:31:41 PM mDNSResponder[15] Permission denied (NOAUTH): HEATER._afpovertcp._tcp.drezd.members.mac.com.
2/14/08 7:31:41 PM mDNSResponder[15] Error -65537 for refresh of service HEATER._afpovertcp._tcp.drezd.members.mac.com.
2/14/08 7:32:11 PM FileSyncAgent[174] MKCOL /.FileSync (FAILED), httpStatusCode:405, errorType:100, transactionState:5, txnId:28CCC64A-323F-4913-829B-99BA16297B40, auto-retries=0, manual-retries=0
2/14/08 7:33:50 PM mDNSResponder[15] Permission denied (NOAUTH): _kerberos. HEATER.drezd.members.mac.com.
2/14/08 7:33:50 PM mDNSResponder[15] hndlRecordUpdateReply: Registration of record _kerberos. HEATER.drezd.members.mac.com. type 16 failed with error -65537

LTL

Feb 17 2008, 03:04 PM

QUOTE(DaemonES @ Oct 5 2006, 09:41 PM)

Hi guys.
More than one weak ago I\'ve started writing driver for Realtek controllers. At this time I have some results, I've not tested all features, cause I have no such opportunity, but MacOS successfully communicate with WinXP system through my driver.
It works on RTL8169, RTL8168, RTL8110, RTL8111, RTL8100, RTL8101 chips and their modifications.

I have some driver programming skills under WinXP, but MacOS and IOKit are new things for me, so be careful when using my driver. You can freely load it and unload, but only once at one system boot (cause more loads may cause system crash, I\'m planning to fix it). Use sh scenarios for loading/unloading driver.

Now I\'m planing to add such features:
- Manual MTU control (now it fixed at 1500).
- Jumbo frame support.
- Wake on magic packet.

Thanks to the:
- author of Linux R1000 driver.
- NeoPheus for installer. Great job, thanks.

Share your knowledge so much as you can.

Compiled with XCode 2.4 on OSX 10.4.6 JaS Install DVD.
Visit to project page for the latest driver and installer.
https://sourceforge.net/projects/realtekr1000/

Hello and thank you for your work

I have been using your driver with my 8111 built into my Mobo... about to change to PCI 8169 Trendnet

Wondering if you have had any luck getting Bonjour to work... I am still getting major errors via mDNSResponder

thanks!

LTL

Feb 19 2008, 12:06 PM

QUOTE(DaemonES @ Oct 5 2006, 09:41 PM)

Hi guys.
More than one weak ago I\'ve started writing driver for Realtek controllers. At this time I have some results, I've not tested all features, cause I have no such opportunity, but MacOS successfully communicate with WinXP system through my driver.
It works on RTL8169, RTL8168, RTL8110, RTL8111, RTL8100, RTL8101 chips and their modifications.

I have some driver programming skills under WinXP, but MacOS and IOKit are new things for me, so be careful when using my driver. You can freely load it and unload, but only once at one system boot (cause more loads may cause system crash, I\'m planning to fix it). Use sh scenarios for loading/unloading driver.

Now I\'m planing to add such features:
- Manual MTU control (now it fixed at 1500).
- Jumbo frame support.
- Wake on magic packet.

Thanks to the:
- author of Linux R1000 driver.
- NeoPheus for installer. Great job, thanks.

Share your knowledge so much as you can.

Compiled with XCode 2.4 on OSX 10.4.6 JaS Install DVD.
Visit to project page for the latest driver and installer.
https://sourceforge.net/projects/realtekr1000/

Thanks for your work

But still no AFP and Bonjour... only SMB

any ideas?

I even got a new NIC 8169 based, same issues. Only works when I do a vanilla Kalyway ... untouched

Hope you guys have an answer... i have exhausted myself with this...and need to reach out for help now

GERGÖ

Feb 26 2008, 09:13 AM

Hi guys!
I have a big problem: I installed this stuff on my pc, but it says there is no cable connected. My motherboard is Gigabyte P35-DS3L.
I applied manually, dhcp etc., but no success.

GERGÖ

Feb 27 2008, 08:45 AM

OK! I SOLVED THE PROBLEM!
Please write it on the first page: The Mac OS can't "power up" the network card. If it's not powered on, than Mac will say: No cable is plugged in and can't use. But if the lan boot rom is enabled the bios switches it on and everything works fine.
The boot is a bit longer because of the rom, but after than it's surely on.

sporty-vibe

Mar 4 2008, 08:56 PM

Anyone got this working on an intel DG31PR motherboard.

Specs say something like Realtek 8111-gr nic,
When i put lan as first in bootsequence is says 8111b??

I did the install, without errors, after a reboot the kext shows up in system profiler.

however Ethernet says cable unplugged

no lights on the nic either.

I haven't got a dual boot, so i cant do the wake on lan trick.

any help would be appreciated.

markpenn

Mar 12 2008, 04:25 AM

do you guys know how to get

Integrated Realtek RTL8211B

Integrated Realtek RT8201CL

works?
thanks

OnePlane

Mar 12 2008, 11:53 PM

This is the perfect driver I needed! Thanks alot

However, I have a small problem when sending/receiving large files / lots of data. The network card simply stops responding, nothing the the logs, no errors, nothing. Just a halt of everything networking related and after some time a load of timeout messages. I need to kextunload/kextload before I can use it again...

Is there a way to fix this? Can I do something? I have a Sweex RTL8169-based network card which standard operates at 100Mbps and needs to be set manually to 1Gbps for it to work correctly. (Doesn't matter if I do this or not, because even in 100 mode it's going to crash)

Why is this happening anyway? I tried 4 different drivers, and only this one could get it to work... Now if that impractical reload could be ironed out..

gkrangers

Mar 13 2008, 09:43 PM

My RTL8111B was working out of the box on my GA-P35-DS3L (with 10.5.2), but adding your driver enabled some sharing capabilities. I can share iTunes libraries now.

I'm able to share files between my Hac Pro (desktop) and Hac Book (notebook), with AFP enabled. However, after a quick start to the transfer, it hit about 12MB and has now slowed to a crawl. Transferring at like 500KB every 20-30 seconds.

Is this a known issue with sharing? I'm transferring 4.5GB of files.

Edit: I just transfered a 800MB file, and that went fine. However, I just tried a 3.68GB file and that slowed way down. Tried some other files of varying size, hit or miss. Some go fine, some start fine and slow down, and some crawl from the start.

OnePlane

Mar 15 2008, 08:23 PM

I had that too, but worse: it just stops

KahNv2

Mar 17 2008, 10:16 AM

QUOTE(GERGÖ @ Feb 27 2008, 09:45 AM)

OK! I SOLVED THE PROBLEM!
Please write it on the first page: The Mac OS can't "power up" the network card. If it's not powered on, than Mac will say: No cable is plugged in and can't use. But if the lan boot rom is enabled the bios switches it on and everything works fine.
The boot is a bit longer because of the rom, but after than it's surely on.

Ok, i have the same problem. I keeps saying that there is no cable attached. But... I dont have a WOL option in my bios. Does someone have any idea how to solve this?

superigeek

Mar 18 2008, 03:57 PM

QUOTE

I have a GA-P35C-DS3R Rev. 2.0 motherboard with a Realtek 8168B/8111B built-in PCI-E Ethernet adapter.

I installed Kalyway's 10.5.1 a week ago. Ethernet worked out of the box, until yesterday when Ethernet just stopped working all of a sudden. It kept saying "Cable Unplugged" in Network prefs.

So I tried installing the R1000 v1.04 package, but after restarting I got a message upon logging in saying that the R1000 kext cannot be used and therefor it will be unloaded by the system.

I uninstalled it (just dumped the kext) and installed Realtek's own "RTGMac_v1.1.6" driver.

This driver works, but when I go into "Advanced" in Network prefs the computer completely crashes - colored wheel starts spinning and nothing works. I have to press the power button to shut the computer down.

Any help will be greatly appreciated. Thanks.

Like Gantlett, I get the same issue.
Do we need to put R1000 kext into /System/library/Extentions or in /System/Library/Extentions/IONetworkFamily/.../Plugins.
Also 'd like to know if others Realtek kext should be deleted to make R1000 work. See my signature for my configuration. Help would be very much appreciated.

pjay1182

Mar 18 2008, 08:42 PM

DaemonES,

I managed to get my soundchip working, butt the LAN is still not working at all. I did already try those tips that you gave to sunriis.

I don't know if if this helps, butt here is the output of the command "sh installrelease"

./installrelease
file attribute adjusting for RealtekR1000.kext
kernel extension RealtekR1000.kext has problems:
Authentication failures:
{
"File owner/permissions are incorrect (must be root:wheel, nonwritable by group/other)" = (
"/RealtekR1000/build/Release/RealtekR1000.kext"
"/RealtekR1000/build/Release/RealtekR1000.kext/Contents/Info.plist"
"/RealtekR1000/build/Release/RealtekR1000.kext/Contents"
"/RealtekR1000/build/Release/RealtekR1000.kext/Contents/MacOS/RealtekR1000"
"/RealtekR1000/build/Release/RealtekR1000.kext/Contents/MacOS"
)
}
Warnings:
{
"Kext has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style" = true

Please help

Tnx in advance!

My setup is :
E8400
Gigabyte P35-DS4 Ahci Enable with Guid table
Raptor 74GiB GD
2GB of RAM

OnePlane

Mar 18 2008, 08:51 PM

As you may notice, this tells you that:

-kernel extension RealtekR1000.kext has problems
-kind of problem: Authentication failures
-what's wrong with authentication: File owner/permissions are incorrect (must be root:wheel, nonwritable by group/other)
-Warnings, which you don't need to worry about since they're only warnings.

Use the noob installer that came with kalyway

pjay1182

Mar 18 2008, 10:17 PM

Which installer should I use than?
I did found the realtek universal installer? Butt it stills remains not connected. I tried auto nogotition, manual @ 10baseT half en full duplex and 100MB half and full duplex.

I will try it agian with this

sudo -s
cp -R /System/Library/Extensions/AppleRealtek8139.kext /Users
rm - R /System/Library/Extensions/AppleRealtek8139.kext
rm -R /System/Library/Extensions/RealtekR1000.kext
diskutil repairpermissions /

What should I do next? Any tips?

OnePlane

Mar 18 2008, 10:25 PM

Next, you should place the extension you want in the directory where it belongs and then make it owned by user root group wheel (root:wheel) by using chown -R on the .kext. then repair diskpermissions and reboot and rise and shine. try the network utility too (shows what driver is used, and so does console.app). I'm kinda lazy, but with the right questions i'll give you all the answers you need.

pjay1182

Mar 18 2008, 11:24 PM

QUOTE(OnePlane @ Mar 18 2008, 11:25 PM)

Next, you should place the extension you want in the directory where it belongs and then make it owned by user root group wheel (root:wheel) by using chown -R on the .kext. then repair diskpermissions and reboot and rise and shine. try the network utility too (shows what driver is used, and so does console.app). I'm kinda lazy, but with the right questions i'll give you all the answers you need.

Well you don't need to anymore!
It works now! Hopefully it wil last!
I did enable wake up on lan in the device manger of windows. And now it works!

OnePlane

Mar 18 2008, 11:30 PM

Lucky you

Have fun, and enjoy your H4xxint0sh

Draner86

Mar 23 2008, 11:14 PM

hy i'm working with MSI K9AG Mobo an got a Realtek 8111b ethernet card inside
i am able to transfer data over my network as long as i do this from my hack directly without any problems, but when i connect from any other pc/mac to my hack an getting from him data (copy) the hack crashes after some traffic (mostly between 1.9 and 2,5 GB)

here is a systemlog with the debug kext until crash happens:

CODE

23.03.08 23:52:48    kernel    1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:48    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:48    kernel    [RealtekR1000] cur_tx 1882010, dirty_tx 1882002, buf_len 1514
23.03.08 23:52:48    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:48    kernel    [RealtekR1000] mbuf_len 66, packpt, packet sended to the network, packet size 66, phys addr 3601a000
23.03.08 23:52:48    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1882019, dirty_tx 1882019, tx_left 0
23.03.08 23:52:48    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1882019, dirty_tx 1882019, tx_left 0
23.03.08 23:52:48    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1882019, dirty_tx 1882019, tx_left 0
23.03.08 23:52:49    kernel    R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35dda000
23.03.08 23:52:49    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:49    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:49    kernel    [RealtekR1000] cur_tx 1883771, dirty_tx 1883770, buf_len 1514
23.03.08 23:52:49    kernel    [RealtekR1000] RedaltekR1000::outputPackelen 66, mised packets 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883781, dirty_tx 1883781, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] Receive: packet len 66, mised packets 0
23.03.08 23:52:49    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:49    kernel    [RealtekR1000] cur_1000TxInterrupt cur_tx 1883807, dirty_tx 1883807, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883807, dirty_tx 1883807, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883807, dirty_tx 1883807, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883807, dirty_tx 1883807, tx_left 0
23.03.08 23:52:49    kernel    ] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35e3a000
23.03.08 23:52:49    kernel    [Real830, dirty_tx 1883830, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] Recei000TxInterrupt, packet sended to the network, packet size 66, phys addr 3612a000
23.03.08 23:52:49    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 3628c000
23.03.08 23:52:49    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 3610e000
23.03.08 23:52:49    kernel    [RealtekR1000] Se1000TxInterrupt, packet sended to the network, packet size 66, phys addr 36368000
23.03.08 23:52:49    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 3614a000
23.03.08 23:52:49    kernel    [RealtekR1000] Receive: packet len 66, mised packets 0
23.03.08 23:52:49    kernel    [RealtekR10001514
23.03.08 23:52:49    kernel    [RealtekR1000] RedaltekR10_tx 1883880, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883880, dirty_tx 1883880, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883880, dirty_tx 1883880, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883880, dirty_tx 1883880, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883880, dirty_tx 1883880, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883880, dirty_tx 1883880, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883880, dirty_tx 1883880, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883880, dirty_tx 1883880, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883880, dirty_tx 1883880, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] Receive: packet len 66, mised packets 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883880, dirty_tx 1883880, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:49    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:49    kernel    [RealtekR1000] cur_tx 1883881, dirty_tx 1883880, buf_len 1514
23.03.08 23:52:49    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:49    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:49    kernel    [RealtekR1000] cur_tx 1883882, dirty_tx 1883880, buf_len 1514
23.03.08 23:52:49    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:49    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:49    kernel    [RealtekR1000] cur_tx 1883883, dirty_tx 1883880, buf_len 1514
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883883, dirty_tx 1883880, tx_left 3
23.03.08 23:52:49    kernel    [RealtekR1000] Send: R1000TxInterruekR1000] mbuf_len 66, packtx 1883908, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883908, dirty_tx 1883908, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883908, dirty_tx 1883908, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883908, dirty_tx 1883908, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883908, dirty_tx 1883908, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883908, dirty_tx 1883908, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883908, dirty_tx 1883908, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883908, dirty_tx 1883908, tx_left 0
23.03.08 23:52:49    kernel    tekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35602000
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:49    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] Receive: packet len 66, mised packets 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883933, dirty_tx 1883933, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883934, dirty_tx 1883933, buf_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] Receive: packet len 66, mised packets 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883934, dirty_tx 1883933, tx_left 1
23.03.08 23:52:50    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 328a4000
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883935, dirty_tx 1883934, buf_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883936, dirty_tx 1883934, buf_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883936, dirty_tx 1883934, tx_left 2
23.03.08 23:52:50    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 34906000
23.03.08 23:52:50    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 33708000
23.03.08 23:52:50    kernel    [RealtekR1000] Receive: packet len 66, mised packets 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883936, dirty_tx 1883936, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883937, dirty_tx 1883936, buf_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883938, dirty_tx 1883936, buf_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883939, dirty_tx 1883936, buf_len 1514
23.03.08 23:52:50    kernel    14
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883951, dirty_tx 1883949, buf_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883952, dirty_tx 1883949, buf_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883952, dirty_tx 1883949, tx_left 3
23.03.08 23:52:50    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 31f64000
23.03.08 23:52:50    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 34926000
23.03.08 23:52:50    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 32128000
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883952, dirty_tx 1883952, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] Receive: packet len 66, mised packets 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883952, dirty_tx 1883952, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883953, dirty_tx 1883952, buf_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883954, dirty_tx 1883952, buf_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883955, dirty_tx 1883952, buf_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [kR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:50    kernel    en 1514
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883981, dirty_tx 1883978, buf_len 1514
23.03.08 23:52:50    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:50    kernel    [RealtekR1000] mbuf_len 66, packet_len 642
23.03.08 23:52:50    kernel    [RealtekR1000] cur_tx 1883982, dirty_tx 1883978, buf_len 642
23.03.08 23:52:50    kernel    [RealtekR1000] Receive: packet len 66, mised packets 0
23.03.08 23:52:50    kernel    [RealtekR1000] Receive: packet len 66, mised packets 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883982, dirty_tx 1883978, tx_left 4
23.03.08 23:52:50    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 31f60000
23.03.08 23:52:50    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 320e2000
23.03.08 23:52:50    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 363c4000
23.03.08 23:52:50    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 31dc6000
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883982, dirty_tx 1883982, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883982, dirty_tx 1883982, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883982, dirty_tx 1883982, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883982, dirty_tx 1883982, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883982, dirty_tx 1883982, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883982, dirty_tx 1883982, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883982, dirty_tx 1883982, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1883982, dirty_tx 1883982, tx_left 0
23.03.08 23:52:50    kernel    nd: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35e9e000
23.03.08 23:52:50    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the networ44, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1885644, dirty_tx 1885644, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1885644, dirty_tx 1885644, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1885644, dirty_tx 1885644, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1885644, dirty_tx 1885644, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1885644, dirty_tx 1885644, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1885644, dirty_tx 1885644, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1885644, dirty_tx 1885644, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1885644, dirty_tx 1885644, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1885644, dirty_tx 1885644, tx_left 0
23.03.08 23:52:50    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1885644, dirty_tx 1885644, tx_left 0
23.03.08 23:52:51    kernel    00TxInterrupt, packet sended to the network, packet size 66, phys addr 35eec000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35a6e000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35d90000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35c72000
23.03.08 23:52:51    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1887491, dirty_tx 1887491, tx_left 0
23.03.08 23:52:51    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1887491, dirty_tx 1887491, tx_left 0
23.03.08 23:52:51    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1887491, dirty_tx 1887491, tx_left 0
23.03.08 23:52:51    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1887491, dirty_tx 1887491, tx_left 0
23.03.08 23:52:51    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1887491, dirty_tx 1887491, tx_left 0
23.03.08 23:52:51    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1887491, dirty_tx 1887491, tx_left 0
23.03.08 23:52:51    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1887491, dirty_tx 1887491, tx_left 0
23.03.08 23:52:51    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1887491, dirty_tdirty_tx 10] cur_tx 1887520ed to the network, packet size 66, phys addr 35fa4000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the putPacket(mbuf_t m, void *param)
23.03.08 23:52:51    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:51    kernel    [RealtekR1000] cur_tx 1887535, dirty_tx 1887532, buf_len 1514
23.03.08 23:52:51    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:51    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:51    kernel    [RealtekR1000] cur_tx 1887536, dirty_tx 1887532, buf_len 1514
23.03.08 23:52:51    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:51    kernel    [RealtekR1000] mbuf_len 66, packet_len 1514
23.03.08 23:52:51    kernel    [RealtekR1000] cur_tx 1887537, dirty_tx 1887532, buf_len 1514
23.03.08 23:52:51    kernel    ] Receive: packet len 66, mised packets 0
23.03.08 23:52:51    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1887548, dirty_tx 1887542, tx_left 6
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35d9e000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35ea0000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the nealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35dd4000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35e36000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35c79000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35ltekR1000] Receive: packet len 66, mised packets 0
23.03.08 23:52:51    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1887572, dirty_tx 1887570, tx_left 2
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys a00] cur_tx 1887585, dirty_tx 1887577, buf_len 1514
23.03.08 23:52:51    kernel    [RealtekR1000] RedaltekR1000::outputPacket(mbuf_t m, buf_len 66, packet_lehys addr 35c1c000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35e1e000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35f20000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 36202000
23.03.08 23:52:51    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 36064000
23.03.08 23:52:52    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35de6000
23.03.08 23:52:52    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1887612, dirty_tx 1887609, tx_left 3
23.03.08 23:52:52    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 360a8000
23.03.08 23:52:52    kernel    ended to the network, packet size 66, phys addr 35e7d000
23.03.08 23:52:52    kernel    [RealtekR1000] Send: R1000TxInterrupt cur_tx 1887639, dirty_tx 1887623, tx_left 16
23.03.08 23:52:52    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 360a5000
23.03.08 23:52:52    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 36067000
23.03.08 23:52:52    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35d89000
23.03.08 23:52:52    kernel    [ReaRedaltekR1000::outputPacket(mbuf_t m, void *param)
23.03.08 23:52:52    kernel    [RealtekR1000] mbuf_len 66, packet_len 978
23.03.08 23:52:52    kernel    [RealtekR1000] cur_tx 188735ebd000
23.03.08 23:52:52    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 35e3f000
23.03.08 23:52:52    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 36181000
23.03.08 23:52:52    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 36003000
23.03.08 23:52:52    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the network, packet size 66, phys addr 360e5000
23.03.08 23:52:52    kernel    [RealtekR1000] Send: R1000TxInterrupt, packet sended to the n
23.03.08 23:52:52    kernel    202, packet_len 202
23.03.08 23:52:52    kernel    RealtekR1000] R1000TxInterrupt cur_tx 1887682, dirty_tx 1887682, tx_left 0
23.03.08 23:52:52    kernel    [RealtekR1000] R1000TxInterrupt cur_tx 1887682, dirty_tx 1887682, tx_left 0
23.03.08 23:52:52    kernel    cket(mbuf_t m, void *param)

the only thing i found in google is this:
link

but i'm not an programme and do not realy understood what it means.

P.S.: sorry for my english

NIrving

Mar 24 2008, 06:17 AM

QUOTE(overloade @ Dec 30 2007, 11:22 AM)

This trick really works, I tried this with my XP, then reboot to Leopard, the ethernet works like magic.
Thanks Me123.

This worked for me too, How could it be that I need windows to activate my Network Card?????? Just grateful it is working for me now. Just need to get the Audio and Video to work and I will be a happy man

pignion

Mar 25 2008, 03:07 AM

Hi all,

I'm having trouble getting my 8169\8111 Realtek onboard LAN to work.

I've tried installing the RealtekR1000 1.04 driver, and although my device is recognized and even detected as 'connected' I cannot negotiate DHCP with my router and always get a self-assigned IP.

The Network Utility says it knows what my card is, and I've tried different combinations of Ethernet settings (half-duplex, 100 MB/s, etc), but still nothing.

Here are my specs:

ECS PX1 mobo with Intel P965 & ICH8DH, Core 2 Duo 2.19 gHZ, 3 SATA II drives.
KALYWAY 10.5.1 Vanilla Kernel, most things working correctly (no audio, no onboard Intel 82566DC LAN), dual-booted with XP.

incidentally, the Realtek was actually detected and correctly identified before I even installed the RealtekR1000 driver, but had the same DHCP issues.

Any advice is appreciated.

morkus

Apr 1 2008, 12:00 AM

Thanks Daemon for this. Problem though...

I, at first, didn't appear to have any problems at first on my build (LEO4ALLv2 on an Intel 6850 3.0 GhZ CPU + GA-G31M-S2L mobo + 2 x fresh 500mb SATAs + 4 gig mem + ATi 1900XT card). Smooth install, Leopard on a GUID partition, Windows XP on a mbr, no problems, Kext the ALC662 audio with HDAPatcher 1.20 + alc662.txt, no problems, I noticed the LAN RTL8111C chip worked at first out of the box and then on a reboot would sporadically fail (ie was not connecting and Network > Not Connected, 'Cable Unplugged' error (no IP, DNS, etc...), also, noticed I couldn't see my Windows 'shares' folder on other PC so installed sharefix.zip (eddie1c mentioned this prob somewhere about a missing "/" in his prog so this fixed it...

However, I thought it was strange that sometimes the LAN would 'pickup' and then other times it would not... I found your link here and decided to take the plunge and see if your Realtek1000 answer would solve the issue of random fails.

Alas, although the Network works with your fix, it still doesn't stop the Network from dropping out or 'losing itself'.

Either this is one of 3 things,

1. A LEO4ALLv2 LAN install problem or incompatability.
2. A problem at BIOS level? because, if I go to BIOS and to my SMART LAN diagnostic which detects if a cable is attached and is functioning normally I wait till I get the green light ie 'Link Detected' and then start up Leopard boot - voila! all is working again.
or,
3. I found that after using Windows XP and then restarting in Leopard (with BIOS f12 HD selector boot) the LAN would disappear again too. Though I must admit after a hard reset (switch off) I still sometimes get LAN failure under Leopard under first boot.

Any ideas why I keep losing connection? I think other people have experienced this as well on other boards....

Best to you mate,

Mork

morkus

Apr 1 2008, 04:46 AM

oh, I just tested what the other guys were saying about using wake up on lan in the device manager of windows and checked it - that now works, and if I am cold booting I now have LAN Boot ROM Enabled too - now it works all the time.... so far!

Cheers all

mork

DaemonES

Apr 1 2008, 10:04 PM

Some fixes with kernel' panic on Leopard.

neverfollow

Apr 4 2008, 07:12 PM

I built the 'hack yesterday (see specs below) and got most everything up and running (many many thanks to PCWiz and Kalyway!!!), but after 6 hours I still couldn't get the ethernet to work. I read through as many posts as I could, tried installing DaemonES's fix, tried the Realtek site's drivers, tried running the install script from PCWiz selecting only the ethernet drivers, tried PCWiz's previous "manual" install method, but when the clock struck 4am, I gave up. This morning I tried uninstalling drivers, and re-installing the realtek dmg, but still no luck. I had an old LAN card that I stuck in, which worked. Any ideas on fixes for the realtek on-board LAN?

Thanks!
-Bryan

MDW2

Apr 5 2008, 09:42 AM

Hi!

LAN doesn't work in my Hackintosh because I have Attansic L1 Gigabit Ethernet on my board. So I have to buy a card. What card should I buy? Which cards (with Realtek chipset) work? RTL8139, RTL8169, and... Could someone tell me?

MDW

Firechild

Apr 7 2008, 01:18 PM

QUOTE(DaemonES @ Apr 1 2008, 10:04 PM)

Some fixes with kernel' panic on Leopard.

Hi Daemon, thanks for the link. Can you just tell us how to use it?

Firechild

Apr 8 2008, 08:28 AM

I bought the Netgear GA 311 Gbit ethernet PCI card which worked out of the box with leo4all V2.

bedub

Apr 10 2008, 03:38 AM

I think you have to build the kext with xcode.... just install xcode and open RealtekR1000.xcodeproj, RealtekR1000.kext should appear in the build folder.

Hope this helps... took me a minute to figure it out too

Oh, and not to change the subject but I recently switched to GA311 too and it works great!

MisterJack

Apr 11 2008, 07:21 PM

i have an usb dongle with rtl8187 chipset. now i'm using the official driver and it works very well.

the driver posted here works with this chipset? if so, macos will recognise my card as an airport card or not?

thanks in advance

MJ

PGreen07

Apr 14 2008, 02:48 PM

can someone tell me if> Realtek RTL8139/810x works for anyone ? if so does anyone have an installer or kext for it ???

karaakeha1

Apr 16 2008, 02:37 PM

QUOTE(MisterJack @ Apr 11 2008, 03:21 PM)

i have an usb dongle with rtl8187 chipset. now i'm using the official driver and it works very well.

the driver posted here works with this chipset? if so, macos will recognise my card as an airport card or not?

thanks in advance

MJ

Which USB Dongle (I mean what Brand) you are using

MisterJack

Apr 17 2008, 02:46 PM

QUOTE(karaakeha1 @ Apr 16 2008, 02:37 PM)

Which USB Dongle (I mean what Brand) you are using

http://cgi.ebay.it/ws/eBayISAPI.dll?ViewIt...em=190208914841

the dongle is this.

i don't know the brand, but it works with the official realtek drivers.

if i use this driver, i will see the dongle recognised as an airport card?

MJ

DaemonES

Apr 17 2008, 03:44 PM

MisterJack {censored} no!!! Read first post. Do you see you RTL chip here? Do you see any WiFi note?

Tha_Messiah

Apr 24 2008, 09:46 PM

Hi...

Now i have been reading through this topic, and trying out all of the solutions, reinstalling OSX like 50 times, and i still can't use my ethernet :/

I have the MSI P35 Neo-F mainboard, with the bios update, that makes OSX possible, i set up the settings as they should be, according to what i have read about all over the forums.

My complete setup:

Pentium 4 3.2GHz Prescott 640 (LGA775)
MSI P35Neo-F with modded bios // Realtek 8168B/8111B Ethernet card (according to OSX (Kalyway Leopard 10.5.2) and Windows)
4GB Adata Viesta 667MHz RAM
Samsung 160GB SATA-II HDD for OSX + WindowsXP
Samsung 250GB SATA-II HDD for storage
Samsung 500GB SATA-II HDD not partitioned yet (planning to use this drive for OSX stuff)
Samsung SATA DVD-RW Drive
MSI NX8800GTS/512

I get the File Ownership/Permission error, when trying to use the 'kextload -t RealtekR1000.kext' command, and yes, i remembered to use sudo -s

I get no error, and the card is found in the network settings, but it does not find that the cable is inserted. When i look at the router, it does not light op in the port where the computer is connected. I have used all the ports, and a few different cables, to make sure that was not the problem.

Can anyone help me out here ?

Thanks in advance.

//Tha_Messiah

bazz38

Apr 28 2008, 09:58 PM

Hello,

I've installed the driver today, and it's working like a charm, thanks a lot

. There's only one thing that doesn't work like it should, and that's the DHCP-lease. When woken from sleep, there's no DHCP adress configured. The driver loads perfectly, no errors in console whatsoever, only there's no DHCP configured. If I choose to renew the DHCP adress manually, it's working again... I guess the power management for this driver isn't stable yet. Any way to fix this?

Thanks in advance and thanks again for the great driver so far!

Btw: I'm using a GA-P35DS3R, with the Realtek 811B...

@ Tha_Messiah; did you try using Kexthelper, and you should try repairing permissions with Diskutil