Contribute
Register

Rebranding the Atheros 928x cards - The guide

Status
Not open for further replies.
Thanks a ton for this guide, just edited my unbranded ar9825 and it now passes whitelist \o/ Great guide!
 
Apart from getting rid of the boot message, is there any other advantage of a rebranded Atheros 9280 over a BCM94322HM8L ?
 
I'm trying to patch my Atheros Wifi. Because of that i downloaded the Atheros EEPROM tool from the first post. Is it on purpose that the dropbox link wont contain a binary but sourcecode from Visual C++?


EDIT: ups, i need glases! Found the binary in the Debug Folder. Sorry!
 
I successfully patched my AR9280. I had to use deviceID 0032/AR9485 due to BIOS whitelist. The Card is working fine with ubuntu but if I try to install the AR9280 drivers with windows I get a Code 10 - Device cannot start. I knew about the risk of bricking the card (I got it cheap so I had to try it :angel: ) and it would be okay for me if I had bricked it already - but as I said, the card is still working with Ubuntu so it's maybe just a windows issue? Any ideas or experiences?
 
elnino1 said:
I successfully patched my AR9280. I had to use deviceID 0032/AR9485 due to BIOS whitelist. The Card is working fine with ubuntu but if I try to install the AR9280 drivers with windows I get a Code 10 - Device cannot start. I knew about the risk of bricking the card (I got it cheap so I had to try it :angel: ) and it would be okay for me if I had bricked it already - but as I said, the card is still working with Ubuntu so it's maybe just a windows issue? Any ideas or experiences?
Click to expand...

You probably don't want to use AR9485, since it is a different (incompatible) device as compared to the AR9285/AR9280 family. Windows is probably loading the wrong drivers, since it is really an AR9280... What Windows sees, then, is a non-working AR9485.
 
RehabMan said:
You probably don't want to use AR9485, since it is a different (incompatible) device as compared to the AR9285/AR9280 family. Windows is probably loading the wrong drivers, since it is really an AR9280... What Windows sees, then, is a non-working AR9485.
Click to expand...

In fact I screwed the whole rebranding up a bit. Due to wrong research for my BIOS Whitelist I thought my 8560p accepts AR9285 & AR9485. As I noticed 9285 will be blocked too, i switched the ID to 9485... Now I know that the only working Atheros-Wifi for 8560p is HB112AGN (AR9380).

I think I have 2 options now:

1) recover AR9280 aka AR9485 and change DeviceID to AR9380 (if thats possible)

2) buy HB112AGN card and just change the SubVendorID to HP. Will be the same procedure than with 9280 I hope...
 
elnino1 said:
In fact I screwed the whole rebranding up a bit. Due to wrong research for my BIOS Whitelist I thought my 8560p accepts AR9285 & AR9485. As I noticed 9285 will be blocked too, i switched the ID to 9485... Now I know that the only working Atheros-Wifi for 8560p is HB112AGN (AR9380).

I think I have 2 options now:

1) recover AR9280 aka AR9485 and change DeviceID to AR9380 (if thats possible)

2) buy HB112AGN card and just change the SubVendorID to HP. Will be the same procedure than with 9280 I hope...
Click to expand...

AR9380 is not supported by OS X. Just to be clear to not buy one of those cards...

But branding AR9280 as AR9380 may work (then remapping via DSDT back to AR9280), but you might have the same issue with Windows...
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top