madmax Posted October 14, 2013 Share Posted October 14, 2013 Hi, normally I use WiFi. Yesterday I learned that the notebooks ethernet adapter is not detected. I notmaly did not load special drivers and last time ( some time ago) ethernet worked. I have checked the systems prefs and there is none detected. I have tried diffrent intel ones out of the edp package but non worked. Any suggesteions? Please assist. Madmax Link to comment Share on other sites More sharing options...
Administrators Hervé Posted October 14, 2013 Administrators Share Posted October 14, 2013 I believe some of the BCM57xx Ethernet kexts provided in the bootpack are 32bit only... Link to comment Share on other sites More sharing options...
madmax Posted October 15, 2013 Author Share Posted October 15, 2013 Hi, I tougth that the M4300 ( with sticker) is a centrino and therefore the network adapter would be all intel, or is it not? regards, madmax Link to comment Share on other sites More sharing options...
Administrators Hervé Posted October 15, 2013 Administrators Share Posted October 15, 2013 Centrino (in those days) meant Intel mobile CPU + Intel Chipset (Northbridge/Southbridge) + Intel Wireless card. That did not include wired Ethernet interface. Besides, that'll have nothing to do with Ethernet card being detected and/or operational or not. Only Intel wireless cards are unsupported in Mac OS X. Some Intel wired Ethernet interfaces are fully supported. If you can do an lspci -nn command in Terminal and confirm the very model of your card, we can look into it. Link to comment Share on other sites More sharing options...
madmax Posted October 16, 2013 Author Share Posted October 16, 2013 Hi Herve here is the info: pcilib: 0000:01:00.0 64-bit device address ignored. 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) 00:01.0 PCI bridge [0604]: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port [8086:2a01] (rev 0c) 00:1a.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 02) 00:1a.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 02) 00:1a.7 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 02) 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 02) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 02) 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 02) 00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 [8086:2845] (rev 02) 00:1c.5 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 [8086:2849] (rev 02) 00:1d.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830] (rev 02) 00:1d.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 [8086:2831] (rev 02) 00:1d.2 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 [8086:2832] (rev 02) 00:1d.7 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 [8086:2836] (rev 02) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev f2) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HM (ICH8M) LPC Interface Controller [8086:2815] (rev 02) 00:1f.1 IDE interface [0101]: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller [8086:2850] (rev 02) 00:1f.2 SATA controller [0106]: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02) 00:1f.3 SMBus [0c05]: Intel Corporation 82801H (ICH8 Family) SMBus Controller [8086:283e] (rev 02) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G86M [Quadro FX 360M] [10de:042d] (rev a1) 03:01.0 CardBus bridge [0607]: O2 Micro, Inc. Cardbus bridge [1217:7135] (rev 21) 03:01.4 FireWire (IEEE 1394) [0c00]: O2 Micro, Inc. Firewire (IEEE 1394) [1217:00f7] (rev 02) 09:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5755M Gigabit Ethernet PCI Express [14e4:1673] (rev 02) 0c:00.0 Network controller [0280]: Broadcom Corporation BCM4321 802.11a/b/g/n [14e4:4328] (rev 05) So its a Broadcom Corporation NetXtreme BCM5755M Gigabit Ethernet PCI Express [14e4:1673] (rev 02). Is there a kext that I should use? Thanks for your support. Madmax Link to comment Share on other sites More sharing options...
Administrators Hervé Posted October 16, 2013 Administrators Share Posted October 16, 2013 It's the same LAN hardware as fitted to the D630 (and D830 I think), so you can just download the D630 bootpack and grab the kext from there. But I would have thought it was already provided in the M4300 bootpack. Link to comment Share on other sites More sharing options...
madmax Posted October 16, 2013 Author Share Posted October 16, 2013 Hi, the bcm5722D is in the M4300 edp default. Its in Lat's 630 and 830 as well. Its unfortunately not working. Madmax Link to comment Share on other sites More sharing options...
Administrators Hervé Posted October 16, 2013 Administrators Share Posted October 16, 2013 In that case, it's probably as I thought: a 32bit kext only... I checked my D630 nVidia under ML and Mav, i.e. in 64bit mode. The kext is definitely 32/64bit and loads up Ok. I have the Ethernet board reported in Network Pref Pane. Try the attached, but I'm pretty sure you'd get the same file out of the boot pack. BCM5722D.kext.zipFetching info... Link to comment Share on other sites More sharing options...
madmax Posted October 27, 2013 Author Share Posted October 27, 2013 Hi, Ethernet seems to work on Mavericks. So I will not invest more time on ML and wait for Mavericks to work. Thanks for the help. Madmax Link to comment Share on other sites More sharing options...
rosmaniac Posted October 31, 2013 Share Posted October 31, 2013 On 10/27/2013 at 9:58 AM, madmax said: Hi, Ethernet seems to work on Mavericks. So I will not invest more time on ML and wait for Mavericks to work. Thanks for the help. Madmax I'm running ML 10.8.5 on my M4300 and the ethernet is working; after a lot of traffic, however, it drops out and requires a shutdown/boot up to fix. Note that I primarily use a D/Dock and its ethernet port (right now, in fact). But the D/Dock just extends the lines, to the best of my knowledge; lspci isn't working for me at the moment (gives a cannot find any working access method error). My /Extra shows that the EDP svn version I'm using is 701; that is actually from when I upgraded Lion to ML (with lots of issues of apps getting put in /Recovered Items, argh!) 10.8.3 and running EDP then. I've not been able to successfully update EDP since then; reinstalling and then re-running just produces the same blank window I've seen reported as with Mavericks (by you, in the thread https://osxlatitude.com/index.php?/topic/5568-mavericks-on-m4300/ ) I've also had other issues, mainly frequent kernel panics on boot (it'll KP twice, then boot up ok for a while). I've also seen booting from the USB installer stick bringing up a black screen, but the very next boot, without changing any boot parameters, it will work fine). i've seen this with two separate M4300's, so I don't think it's my hardware, but I reserve the right to be wrong. Since I dual-boot CentOS 6 (64-bit) and that works perfectly fine, I'm further convinced that the hardware is fine. CentOS is actually my primary OS on the laptop, but I do some audio production that requires OS X tools, and so that gets me in OS X at least once a week. My install started life as a 'leppy700m' boot disk install of 10.6.0 on an M65, upgraded to an EDP install (back early in the EDP 5.x cycle), changed to a D820 (motherboard/GPU failure), upgraded to Lion and through 10.7.5, then changed to the M4300 (by doing an EDP build for M4300 on the M65/D820 and swapping the HD to the M4300 and rebooting, which worked fine), then upgraded to ML 10.8.3, and finally a combo update to 10.8.5. Whew. Yes, I'm getting ready to do a scratch install on a new drive. I said that to say that it's quite possible my install has' issues' from the upgrade chain, and a fresh install may be very different. Link to comment Share on other sites More sharing options...
Recommended Posts