Jump to content

Intel 82562v LAN driver


iQQ
 Share

34 posts in this topic

Recommended Posts

I have a Dell Dimension E520, which comes with:

 

Intel G965 Motherboard

ICH8R storage controller, with SATA II hard drive + DVD RW

FSB=1066

CPU=Core 2 Duo, 2.4GH

2 GB memory

Onboard SigmaTel 9227 Audio

Onboard Intel 82562v 10/100 Lan

 

Take hard drive out and put it in a USB hard drive external box, plug into my IBM x40, install with JaS 10.4.8

Modify AppleAHCIPort.kext with AHCI ID 0x28228086 and AppleVIAATA.kext with SATA ID 0x28208086 0x28258086

Delete Entension cache and .mkext

Repair disk permission

Shutdown and put hard drive back to E520

 

Works fine except audio and Lan.

 

Thanks to prasys built audio driver for me, it works perfect now.

 

Only LAN can't work. I tried all methods I can find, none of them works.

 

Can any one help me work it out?

For reference, you may see solutions in Linux: http://www.centos.org/modules/newbb/viewto...p?topic_id=5865

Link to comment
Share on other sites

I have a Dell Dimension E520, which comes with:

 

Intel G965 Motherboard

ICH8R storage controller, with SATA II hard drive + DVD RW

FSB=1066

CPU=Core 2 Duo, 2.4GH

2 GB memory

Onboard SigmaTel 9227 Audio

Onboard Intel 82562v 10/100 Lan

 

Take hard drive out and put it in a USB hard drive external box, plug into my IBM x40, install with JaS 10.4.8

Modify AppleAHCIPort.kext with AHCI ID 0x28228086 and AppleVIAATA.kext with SATA ID 0x28208086 0x28258086

Delete Entension cache and .mkext

Repair disk permission

Shutdown and put hard drive back to E520

 

Works fine except audio and Lan.

 

Thanks to prasys built audio driver for me, it works perfect now.

 

Only LAN can't work. I tried all methods I can find, none of them works.

 

Can any one help me work it out?

For reference, you may see solutions in Linux: http://www.centos.org/modules/newbb/viewto...p?topic_id=5865

 

Can you tell me more about your Audio soluce with Sigmatel 9227

Sorry i 've got no issue with Lan

Tank's in advance

Link to comment
Share on other sites

I dump the code, and tried to use AppleHDA Patcher 1.15, but it cause OSX crash. So I move to IBM x40, It can patch the HDA file, but, no digital output.

 

Then in irc, prasys patched it for me. If you need, I can attach here.

 

What is your LAN, 82562v?

Link to comment
Share on other sites

  • 3 weeks later...
Take hard drive out and put it in a USB hard drive external box, plug into my IBM x40, install with JaS 10.4.8

Modify AppleAHCIPort.kext with AHCI ID 0x28228086 and AppleVIAATA.kext with SATA ID 0x28208086 0x28258086

Delete Entension cache and .mkext

Repair disk permission

Shutdown and put hard drive back to E520

Works fine except audio and Lan.

 

I have HP a1640n (ASUS P5BW-LA mobo) computer with the G965 Intel Chipset and can't boot & install from the DVD drive (SATA).

 

I want to modify the kext files. Where did you get your ID? Will those ID work with any computer or are they specific to your motherboard? I look into the files and can't find the same original ID.

 

Anyone else got luck with this G965 chipset?

 

Thanks

Link to comment
Share on other sites

  • 1 month later...
  • 3 weeks later...

dreadhead-

i, too, have an e520 running 10.4.10 flawlessly. (except sound and ethernet for which i use seperate PCI devices). to get os x to install, use a usb>sata cable and install the OS to the drive while it's connected via usb. then install the ICH8 drivers from uphucks dvd (or wherever else). then reconnect it to sata and it should be recognized by os x and you'll be good. no more "still waiting for root device". i think i had to use a USB dvd-rom as well. that's just how i did it. i'm not sure if there's a better way or not. if so, someone let me know!

Link to comment
Share on other sites

I also have a Dell E520 similar specs and I really need help :(

 

I put my hard drive onto a USB and borrowed a external DVD rom. I installed Uphuck's latest and the install webt just as advertised. But after the installation I get the feared error "... com.apple.boot.plist not found". I have searched and tried several things with no luck. Please tell me how you did it in detail. I would truley appreciate the help.

 

Thank you in advance

Link to comment
Share on other sites

  • 5 weeks later...

It's a long shot, but try this - this is for your LAN issue, by the way:

 

1a) Download and unpack AppleBCM5751Ethernet.kext.zip: http://www.mediafire.com/?8mzmtqmynjz

1b) Remove the Ethernet cable attached to your computer if it is attached.

2) Copy AppleBCM5751Ethernet.kext to your /System/Library/Extensions/ folder.

3) Open up Terminal and type the following commands in:

 

sudo -s

 

After pressing Enter/Return, proceed to type in your password.

After that, set permissions by typing the following. Remember, these are two separate commands here.

 

chown -R root:wheel /System/Library/Extensions/

chmod -R 755 /System/Library/Extensions/AppleBCM5751Ethernet.kext

 

7) Exit Terminal and any other programs you may have open.

8) Reboot normally.

9) After reboot, go to System Preferences, then Network.

10) Go to Show and select "Built-in Ethernet" from the click-menu.

11) Set up all of your settings. If you don't know what they are, just leave everything alone.

12) Click the "Ethernet" tab.

13) Go to Configure and select "Manually (Advanced)" from the click-menu.

14) Go to Speed and select "100baseTX" from the click-menu.

15) Go to Duplex and select "full-duplex, flow-control" from the click-menu.

16) Make sure the Maximum Packet Size (MTU) is set to it's default; Standard (1500), unless you're using DSL, in which case you know what changes to make, I hope.

17) Apply changes and exit Network.

18) Plug-in your Ethernet cable again. Go back into System Preferences and Network to make sure the light is green, not red. You may have to wait a few seconds for this to occur.

19) After you've confirmed you can connect to the Internet properly, I recommend another reboot to make sure everything is saved properly.

20) Enjoy! You're ready to go.

Link to comment
Share on other sites

  • 3 weeks later...

@WS2000

The boot error you are getting is because you did not create a MBP (Master boot partition), when you partitioned the hard drive, when os x tries to boot, it doesnt know what to look for because of no MBP, you can create this in the disk utility.

Link to comment
Share on other sites

  • 2 weeks later...

Well, I've done quite a bit of work on this today and I haven't come up with anything yet. I did find some things that were interesting. Intel says that the 82562v is in the same family as the 8255x, at least that's what they said on their website. So, that should give hope to using the AppleIntel8255x.kext plugin that is inside IONetworkingFamily.kext. My device ID is 104c and my vendor ID is 8086. I tried putting 0x104c8086 in and it didn't make a difference. But, maybe somebody else will get inspired.

 

One additional piece of info...

Here is the pdf from which I concluded that it is in the 8255x family. Inside you'll see that the 82562v is listed along side 8255x chipsets.

 

This document happens to be the manual for open source development. Apple has the source code for IONetworkingFamily on their site. Maybe some guru would be kind enough to fire up xcode and give some things a whirl. I would try myself, but I'm away from my xcode machine... not that I'm any stellar coder if I did have it.

 

Stevo

Link to comment
Share on other sites

Okey dokey. Here is what I figured out. Ironically, I think I may have got it now when I can't test it. Though, I'm the first to admit its not a revolutionary concept. So, here is the deal. I used Uphuck v1.4 r3 to install, which worked beautifully except there was no network and the network preference pane would crash whenever I would try to open it. Among my many times of try different things, obviously not enough, I decided to look at the System Profiler. Under the network section it listed a ethernet connection working with DHCP and happy as a clam. I thought, ah it must be some sort of a mistake, no matter. So I keep looking on the forums and I found one person who got the 82562 working! It was under the BCM570x thread. Solution? Simply using the 10.4.3 IONetworkingFamily. And then it hit me, the 10.4.3 IONetworkingFamily kext must be the one that Uphuck put in the mkext, therefore the installer program gets it and the installation doesn't. I never checked it because it said that it was needed for some Broadcom chipsets and therefore I didn't know any better. Should have been a logical thing to at least try.

 

Bottom Line: I think that checking 10.4.3 IONetworkingFamily in the installer will fix the problem!

 

As I said, I can't test it right now. Maybe not til tomorrow night at the earliest. Hopefully one of you could try it and see how it goes. I'm pretty sure it will work, or else the system profiler off the DVD shouldn't have showed anything. Good luck!

Link to comment
Share on other sites

  • 1 month later...

On the same boat!!! I had tons of problems with installing Mac.Dub 10.4.10...I had BOOTMRG missing, HFS+ Error, Apple logo with Stop sign, display not working....I overcomed those but I am hit again. I to have E520, same Network card and maybe same audio card tooo...Anyway, What's not working for me is that I haven't got any audio working, I have no internet working on the OSx86 system, My display is 1680x1050 and Mac sets it to 17" size while I have 22" even with the boot editor its like that! I have no dual boot menu as this chain0 {censored} dont work!! Please help!!! ASAP thank you all..

Link to comment
Share on other sites

  • 2 months later...

doing the whole mac thing to a compaq presario :blink: SR2029 spec: http://h10025.www1.hp.com/ewfrf/wc/prodinf...494&lang=en

and having the same difficulty with the charming chipset and its ethernet, this time on leopard.

The problem could never be fixed all through tiger use and still hasnt been fixed through any methods on the net, anywhere!

all help would be appreciated as before.

just thought i would join the collective misery!

Link to comment
Share on other sites

I dump the code, and tried to use AppleHDA Patcher 1.15, but it cause OSX crash. So I move to IBM x40, It can patch the HDA file, but, no digital output.

 

Then in irc, prasys patched it for me. If you need, I can attach here.

 

What is your LAN, 82562v?

 

 

I have a dell XPS210 With the Same Intel Lan and I believe audio as you. Would you be so kind as to either email me the driver prasys made for you. I'm XpS in the Hackintosh room and I have talked to prasys in the past quite a bit, I'd appreciate help getting this audio working.

I also would like to know if you got lan working, I'm going nuts using a targus port replicator for ethernet and soundblaster USB audio, however both work like a charm but just would be nice to have built on lan and sound.

THanks for your time

 

-XpS

Link to comment
Share on other sites

Ok well i found my sound solution from tarugas post so thanks for that.

I'm still stuck on the ethernet though which is really upsetting me. Everything else works mint now just that I'm stuck using a usb laptop port replicator and its really annoying. If anyone has a solution for this that works please post

it's for intel 82562v ethernet

 

Thanks

Link to comment
Share on other sites

  • 1 month later...

I FINALLY got my onboard Intel 82562v NIC working!!

 

Here's what I did:

1. cd to System/Library/Extensions/IONetworkingFamily.kext/Contents/Plugins/AppleIntel8255x.kext/Contents/

2. edit Info.plist. Add this to string below IOPCIMatch key: 0x27dc8086

3. cd back to System/Library/Extensions/IONetworkingFamily.kext/Contents/Plugins/

4. move or rename AppleIntel8254XEthernet.kext

5. clear cache, repair permissions, yada, yada...reboot

 

Enjoy!

Link to comment
Share on other sites

Great work! I had done everything but removing 8254X, never thought of that. I haven't had the opportunity to test it yet, so I can't confirm.

 

Time Ed is on an Asus board, can anybody confirm on a Dell, HP, etc. ? Shouldn't be any different, but I know that there are at least two different revisions of this PHY.

 

Good luck!

 

theStevo

Link to comment
Share on other sites

Intel released updated source for Pro100/Pro1000 drivers. AppleIntel8255x and AppleIntel8254xEth kext's conflict.

Here is list of device ID's + ICH that will work (from e100.c - attached):

INTEL_8255X_ETHERNET_DEVICE(0x1030, 0),

INTEL_8255X_ETHERNET_DEVICE(0x1031, 3),

INTEL_8255X_ETHERNET_DEVICE(0x1032, 3),

INTEL_8255X_ETHERNET_DEVICE(0x1033, 3),

INTEL_8255X_ETHERNET_DEVICE(0x1034, 3),

INTEL_8255X_ETHERNET_DEVICE(0x1038, 3),

INTEL_8255X_ETHERNET_DEVICE(0x1039, 4),

INTEL_8255X_ETHERNET_DEVICE(0x103A, 4),

INTEL_8255X_ETHERNET_DEVICE(0x103B, 4),

INTEL_8255X_ETHERNET_DEVICE(0x103C, 4),

INTEL_8255X_ETHERNET_DEVICE(0x103D, 4),

INTEL_8255X_ETHERNET_DEVICE(0x103E, 4),

INTEL_8255X_ETHERNET_DEVICE(0x1050, 5),

INTEL_8255X_ETHERNET_DEVICE(0x1051, 5),

INTEL_8255X_ETHERNET_DEVICE(0x1052, 5),

INTEL_8255X_ETHERNET_DEVICE(0x1053, 5),

INTEL_8255X_ETHERNET_DEVICE(0x1054, 5),

INTEL_8255X_ETHERNET_DEVICE(0x1055, 5),

INTEL_8255X_ETHERNET_DEVICE(0x1056, 5),

INTEL_8255X_ETHERNET_DEVICE(0x1057, 5),

INTEL_8255X_ETHERNET_DEVICE(0x1059, 0),

INTEL_8255X_ETHERNET_DEVICE(0x1064, 6),

INTEL_8255X_ETHERNET_DEVICE(0x1065, 6),

INTEL_8255X_ETHERNET_DEVICE(0x1066, 6),

INTEL_8255X_ETHERNET_DEVICE(0x1067, 6),

INTEL_8255X_ETHERNET_DEVICE(0x1068, 6),

INTEL_8255X_ETHERNET_DEVICE(0x1069, 6),

INTEL_8255X_ETHERNET_DEVICE(0x106A, 6),

INTEL_8255X_ETHERNET_DEVICE(0x106B, 6),

INTEL_8255X_ETHERNET_DEVICE(0x1091, 7),

INTEL_8255X_ETHERNET_DEVICE(0x1092, 7),

INTEL_8255X_ETHERNET_DEVICE(0x1093, 7),

INTEL_8255X_ETHERNET_DEVICE(0x1094, 7),

INTEL_8255X_ETHERNET_DEVICE(0x1095, 7),

INTEL_8255X_ETHERNET_DEVICE(0x1209, 0),

INTEL_8255X_ETHERNET_DEVICE(0x1229, 0),

INTEL_8255X_ETHERNET_DEVICE(0x2449, 2),

INTEL_8255X_ETHERNET_DEVICE(0x2459, 2),

INTEL_8255X_ETHERNET_DEVICE(0x245D, 2),

INTEL_8255X_ETHERNET_DEVICE(0x27DC, 7),

 

See e1000_main.zip (attached) for mobo's with ICH8 or better. Find line 'static struct pci_device_id e1000_pci_tbl[]'. If your device is there, you might be out of luck.

 

i.e.: 82566DC on Dell is supposed to have 82562v PHY, but only controller mentioned in architecture doc is 82577, so this fix won't work.

e100.c.zip

e1000_main.c.zip

Link to comment
Share on other sites

I FINALLY got my onboard Intel 82562v NIC working!!

 

Here's what to do:

1. cd to System/Library/Extensions/IONetworkingFamily.kext/Contents/Plugins/AppleIntel8255x.kext/Contents/

2. Add this to IOPCIMatch: 0x27dc8086

3. cd back to System/Library/Extensions/IONetworkingFamily.kext/Contents/Plugins/

4. move or rename AppleIntel8254XEthernet.kext

5. remove Extensions.mkext from System/Library/

6. rebuild kext cache (kextcache -k /System/Library/Extensions/)

7. repair permissions, yada, yada...reboot

 

Viola!! Enjoy!

 

I am making a new 10.5.2 install dvd and would like to add this solution in as a choice for users. Would it be alright with you if I add this in ?

Link to comment
Share on other sites

The second coming!!!

 

JaS, you have made my week. I'm back to my E520 now. That PCIMatch didn't work for me. I'll post back in a little bit, I think I might have a different ID. I'll get it and try it.

 

theStevo

Link to comment
Share on other sites

The second coming!!!

 

JaS, you have made my week. I'm back to my E520 now. That PCIMatch didn't work for me. I'll post back in a little bit, I think I might have a different ID. I'll get it and try it.

 

theStevo

 

Hey good to see your still around. I will keep an eye on this tread to see how the progress goes.

Link to comment
Share on other sites

Alrighty, here is the deal. This is to the best of my understanding. If I'm wrong feel free to say.

 

First, time ed, according to google and the forum you do not have a 82562v. I'm not calling you a liar, I'm sure it identified incorrectly. However, 0x27dc8086 has worked for a long time for many people on the forum and is considered an 100/VE. So, time ed's information does not apply to us. I am happy you have yours working though.

 

Now, for what I found out: The first place to start your endeavors is with the 10.4.3 IONetworking. You can't get anything later to even load for the 82562v. Even when I put 0x104c8086&0x00000000 it wouldn't load. (Which by the way, what follows the & is a mask where f means from what came previous and 0 means ignore. Therefore the mask I tried would have loaded anything with the IOPCIClass of 0x02000000) So, then the 10.4.3 kext. It will load, however it has problems with the eeprom. The reason for this is that the 82562v has a 1000/100 MAC paired with a 100/10 PHY. Therefore, OS X sees the controller, tries to load the controller. It finds that its DEV and Product IDs match for the 8255x kext, which wants to see an 100/10 eeprom. However, it actually tries to load the information from the eeprom and gets confused. It gets 1000/100 information. So, you say, lets work with 8254x. No. Then it might recognize the eeprom but never be able to negotiation with any hosts because the PHY wouldn't allow proper setting of the speed.

 

Therefore, I came to a conclusion I haven't had previously. And again, if I'm wrong just say. But, I think that this chipset won't ever work, even if we get AppleIntel8256x.kext. The reason why is that Intel drivers are not direct ports of e1000 from Linux. I was specifically told that by Small Tree. The guy I talked to said that they build all of their drivers from the bottom up. I'm sure they have better things to do with their time than build drivers from scratch for the fun of it, so most likely its necessary. When Apple is making their drivers, why would they ever put any code in pertaining to using a PHY that is set differently than the eeprom? Apple doesn't like using Intel for any integrated network solutions, much less working with their screwed up little disabled solutions for the cheap market. Granted, it probably wouldn't be difficult to add that code, but those who can won't and those who would won't have the source code. So, until I hear a couple people report that they have this integrated NIC working I'm not going to test any more of these solutions. I don't thing anybody was being deliberately misleading, not at all, but for now I just don't think its going to happen.

 

theStevo

Link to comment
Share on other sites

 Share

×
×
  • Create New...