- Joined
- Dec 17, 2012
- Messages
- 60
- Motherboard
- OS X 10.8.3. Windows 8 Pro
- CPU
- Core i7 3770K
- Graphics
- ASUS GTX680-DC2T-2GD5
- Mac
- Classic Mac
- Mobile Phone
Network Connection would collapse, then crash the system; on 10.9 [SOLVED]
Hey all,
Have any of you experience a network collapse under 10.9? As in, when you're streaming something from your local network, browsing, listening to Rdio; then all of a sudden lose connectivity to your local network and then eventually the entire computer would just grind to a halt?
I see this message on Console:
There's also a thread related to this:
http://www.tonymacx86.com/multibeast-bug-reports/111439-e1000-driver-hangs-multibeast-5-5-a.html
but no solution was found.
I've got an Asus Z77 Sabertooth Motherboard; worked like a charm under 10.8 with Multibeast 5.x.
Hey all,
Have any of you experience a network collapse under 10.9? As in, when you're streaming something from your local network, browsing, listening to Rdio; then all of a sudden lose connectivity to your local network and then eventually the entire computer would just grind to a halt?
I see this message on Console:
10/24/2013 12:52:26.000 AM kernel[0]: failed to getphysicalsegment in outputPacket.
There's also a thread related to this:
http://www.tonymacx86.com/multibeast-bug-reports/111439-e1000-driver-hangs-multibeast-5-5-a.html
but no solution was found.
I've got an Asus Z77 Sabertooth Motherboard; worked like a charm under 10.8 with Multibeast 5.x.
UPDATE:
Using an older hnak's Intel Ethernet .kext file from previous MultiBeast seems to have fixed the issue. 10.9's been running more than 36 hours without network issues.