Rebranding Atheros AR5006EG to a Vanilla Card

[Kykc]

kizwan OK, my full story.

0) I've dumped original EEPROM

1) I've tried to rebrand my card after ath_info documentation. So I've used commands like that: ath_info -g 1:0 -w fa9f0000 pci_dev_id 1014

In that way I've changed dev id, device class, subvendor and subdevice ids. After reboot card's device id is ff1b. Then I've dumped current EEPROM and compared it to original.

2) I've manage to get back to original EEPROM. It was difficult, because addressing in file and EEPROM is different. (In EEPROM each 16bits have address, in file each 8 bits have adress). I've used commands like ath_info -g 1:0 -w fa9f0000 0x01 0x169c (0x01 is address or offset, 0x169c value) After reboot all gone OK, card is now recognized like it always was.

3) Manually analyze the EEPROM dump and try to guess where my numbers are. I've successfully changed device id, subdevice and subvendor ids. In windows xp card was recognized as a/b/g Wireless Adapter and in device manager I can see the values I've just changed. Macos don't recognize card at all.

4) Try to change device class id. Manually, as before. I've changed one pair which was 0x0200 to 0x0280 and gard has gone

PS Be careful with manual flashing. Addresses in dump file are not equal to addresses in EEPROM, also pairs are in reversed order. The value 0x168c in EEPROM is equal to two bytes in dump file: 0x8c 0x16

PPS Sorry, I'll be able to write full-sized and clear tutorial about my experience, if only I knew English better.

[kizwan]

kizwan OK, my full story.

0) I've dumped original EEPROM

1) I've tried to rebrand my card after ath_info documentation. So I've used commands like that: ath_info -g 1:0 -w fa9f0000 pci_dev_id 1014

In that way I've changed dev id, device class, subvendor and subdevice ids. After reboot card's device id is ff1b. Then I've dumped current EEPROM and compared it to original.

2) I've manage to get back to original EEPROM. It was difficult, because addressing in file and EEPROM is different. (In EEPROM each 16bits have address, in file each 8 bits have adress). I've used commands like ath_info -g 1:0 -w fa9f0000 0x01 0x169c (0x01 is address or offset, 0x169c value) After reboot all gone OK, card is now recognized like it always was.

3) Manually analyze the EEPROM dump and try to guess where my numbers are. I've successfully changed device id, subdevice and subvendor ids. In windows xp card was recognized as a/b/g Wireless Adapter and in device manager I can see the values I've just changed. Macos don't recognize card at all.

4) Try to change device class id. Manually, as before. I've changed one pair which was 0x0200 to 0x0280 and gard has gone

PS Be careful with manual flashing. Addresses in dump file are not equal to addresses in EEPROM, also pairs are in reversed order. The value 0x168c in EEPROM is equal to two bytes in dump file: 0x8c 0x16

PPS Sorry, I'll be able to write full-sized and clear tutorial about my experience, if only I knew English better.

 

Hi Kykc,

Thank you very much for the info. I really appreciate it. I have downloaded your original EEPROM dump file. Look like we have same value at the beginning & end of EEPROM space. Do the false device id ff1b viewable by naked eye if you execute (for example) "./ath_info -d 0x80200000"? Can you post your broken EEPROM dump (the one that you get device id ff1b)? I want try to compare with your original EEPROM dump. Thank you.

 

I think you can get back your card to working condition. If somehow you can get bios image for your paticular notebook, you can flash back that image to your bios. This just my theory because EEPROM just a chipset, the content of the EEPROM will be loaded by BIOS. But....emmmm....on second thought....that may not work. Don't try this at home.

 

kizwan

[Kykc]

kizwan I don't have this dump :\ But I remember that I've restored two first strings from original dump file. (from 0x00 to 0x1F) But you can get the addresses of these constants pci_dev_id of ath_info. Just try ath_info -w 80200000 pci_dev_id 0x0000 (without -g) this value will not be written, but you can get an address in ath_info output =)

PS I'm happy to be somehow helpful

[iHack13]

ok if you endure it another few days I'll do a tutorial about this.

[kizwan]

Hi,

This is another successful rebranding story:-

Shocky's Lab

 

In that article, the author did change mapping for pc_dev_id, pc_vendor_id & pc_class in ath_info.c. No wonder when I try to change my pc_dev_id, ath_info try to change at different address.

 

kizwan

 

ok if you endure it another few days I'll do a tutorial about this.

 

That great!! Thank you.

[kizwan]

Hi guys,

I have lost my card in the process to rebrand it. Now I want to try to recover my card if it is possible. It is very wonderful experience even though it is complete failure to me. Is there any device that I need to recover my card? Maybe I can find it at any D.I.Y shop. There is an aluminium that cover the entire board. So, any attempt tu connect directly to the chipset may be difficult.

 

kizwan

[Kykc]

Hi guys,

I have lost my card in the process to rebrand it. Now I want to try to recover my card if it is possible. It is very wonderful experience even though it is complete failure to me. Is there any device that I need to recover my card? Maybe I can find it at any D.I.Y shop. There is an aluminium that cover the entire board. So, any attempt tu connect directly to the chipset may be difficult.

 

kizwan

You have same story like mine? Card didn't appear in lspci listing and so on?

[kizwan]

You have same story like mine? Card didn't appear in lspci listing and so on?

 

Hi Kykc,

Yes, same story. First I got device ID ff1b but I don't lost it after I change device class 0200 to 0280 yet. I don't know what cause it but I lost is after a lot of attempt. Do you know any software that can execute low level task to communicate/access to the eeprom chipset? I think I can access the card using the base address (0x8c100000) but any attempt to access the chipset using ath_info will failed with "0xffff is not supported!".

 

kizwan

[iHack13]

Ok. It's done. Enjoy it!

[althon]

Thanks for the guide, but did not work for me.

 

My card is Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01)

Subsystem: Hewlett-Packard Company Unknown device [103c:137a]

 

I make everything steb by steb, but when execute the command "lspci -vvnn" the info is the same. No change.

 

In the EEPROM Dump is OK - have succses

Before:

 

0000: a55a 0000 0020 0001 0000 5001 0000 137a

0008: 103c 1c0a 0100 0000 0002 0002 c606 0001

0010: 0000 0000 0000 0000 0000 0000 0000 0000

0018: 0000 0000 0000 0000 0000 0f38 3a68 001f

0020: 0000 0000 0000 0000 0000 0000 0000 0000

0028: 0000 0000 0000 0000 0000 0000 0000 0000

0030: 0000 0000 0000 0000 0000 0000 0000 0000

0038: 0000 0000 0000 0000 0000 0000 0000 0000

0040: 1400 168c 001c 1402 0001 0200 140a 5001

0048: 0000 140b 103c 137a 140f 0100 1c0a 1410

0050: 5001 01c2 101a 050a 0000 1419 0cc0 0504

 

After:

 

0000: a55a 0000 0020 0001 0000 5001 0000 004e

0008: 106b 1c0a 0100 0000 0002 0002 c606 0001

0010: 0000 0000 0000 0000 0000 0000 0000 0000

0018: 0000 0000 0000 0000 0000 0f38 3a68 001f

0020: 0000 0000 0000 0000 0000 0000 0000 0000

0028: 0000 0000 0000 0000 0000 0000 0000 0000

0030: 0000 0000 0000 0000 0000 0000 0000 0000

0038: 0000 0000 0000 0000 0000 0000 0000 0000

0040: 1400 168c 001c 1402 0001 0280 140a 5001

0048: 0000 140b 106b 004e 140f 0100 1c0a 1410

0050: 5001 01c2 101a 050a 0000 1419 0cc0 0504

 

 

Sorry for my English

[iHack13]

Thanks for the guide, but did not work for me.

 

My card is Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01)

Subsystem: Hewlett-Packard Company Unknown device [103c:137a]

 

I make everything steb by steb, but when execute the command "lspci -vvnn" the info is the same. No change.

 

In the EEPROM Dump is OK - have succses

Before:

[...]

 

ok. as I see you have got an HP lappy. Those are famous for their whitelisted Hardware. I think you will have to mod your BIOS. Look for it on the forums , there should be smthn about it in this topic too.

[althon]

Ok, a make it rebranded, but still have error

"unable to attach hardware: HAL status 13

IO80211Controller : : stop called!

start [sourceCache/AirportDriverAtheros....loaded unsuccessfully" ( I try it on another Notebook, because of my Notebook BIOS ).

I do a rebrand of another Atheros WiFi card and got the same error.

After login in MAC OS X and type in terminal "lspci" it shows me that I have Network Controler Atheros ...blabla.... AR5006EG b/g [168c:001c], Apple ......blablabla.... [106b:004e] and other info.

I dont know what to do.

[iHack13]

do you use the latest airport kexts from apple?

and whats your OS X version

[althon]

I don't know what version of kext I have.

I use the iDeneb v 1.0 10.5.4 MAC OS X.

You mean that I must update first, right?

If so, I'll check this way today.

[diogan]

I have the following card:

 

> 168c:001c:1468:0428 "Atheros AR5007EG Wireless Network Adapter"

 

According to ath_info only G is supported by my card, so I'm curious what IDs I should use since neither the a/b/g nor b/g IDs would be accurate for this card.

[trangir]

Ok, a make it rebranded, but still have error

"unable to attach hardware: HAL status 13

IO80211Controller : : stop called!

start [sourceCache/AirportDriverAtheros....loaded unsuccessfully" ( I try it on another Notebook, because of my Notebook BIOS ).

I do a rebrand of another Atheros WiFi card and got the same error.

After login in MAC OS X and type in terminal "lspci" it shows me that I have Network Controler Atheros ...blabla.... AR5006EG b/g [168c:001c], Apple ......blablabla.... [106b:004e] and other info.

I dont know what to do.

 

How did you do that? I have the same HP {censored}, and I'm unsuccessful with the rebranding, by the same reason you wrote above.

[althon]

I did it following the guide from the first post, but whit already installed Linux-Ubuntu and working WiFi Card ( I skip the steps of installing drivers ).

After that got Error form the BIOS. Here was the beginning of the Game , because I can't use the card with the HP notebook.

By following of another guide, I back it to the original ID's on the same notebook.

After that I try with other notebook ( MSI ) with Atheros card. Got the same same error after rebrand and loading MAC OS X.

I must say that with rebranded and no rebranded card I get the same error.

Today I make a update to 10.5.5 from SoftwareUpdate and after restart I got another error ( with no rebranded card on HP ).

There was something like:

"ath0: 0x2..."

"ath0: unable to attach the device"

and after that the other error like before.

That is for now.

Will try more this night.

 

See ya!!!

[diogan]

I have a couple easier questions that I hope someone can clear up for me.

 

1. When entering the locations in the EEPROM for the various IDs, what is the proper format? For example, if the location is 008a, should you put it into the command exactly like that, or 0x8a?

 

2. When entering in the class ID like in the guide:

 

ath_info -g 3:0 -w 0x<memory_loc> <class_id_loc> 280

 

Should it just be "280" or should it be "0280"?

 

3. How do you determine which number to use when changing IDs (the 3 after the -g flag in the example)?

 

4. Which subvendor and subdevice ID should I use if my card only supports wireless g? I left info about my specific card in a previous comment.

 

Sorry if these are stupid questions, I just like to nail down any unknowns before I start messing around so I don't brick my card.

[diogan]

Ok... just ignore my last comment; naturally I figured out the answers to my own questions right after posting.

 

I changed all the IDs successfully and I can see the updated values in the EEPROM, however lspci still shows the old card information.

 

Any ideas?

 

Thanks.

[althon]

Did you make a reboot after rebranding the card?

I was able to see the new info only after reboot.

[diogan]

Did you make a reboot after rebranding the card?

I was able to see the new info only after reboot.

 

Yes; that was the first thing I thought to try but it didn't make any difference. I'm re-installing OSX at the moment so I have a fresh installation to work with.

[diogan]

Did you make a reboot after rebranding the card?

I was able to see the new info only after reboot.

 

Well slap me silly. After I installed Leopard, I booted back into Ubuntu and checked again and now it is rebranded. Go figure. Wonder why it didn't show up the last time I rebooted.

 

Hmm... Leopard still acts like there is no wireless card in the laptop. Odd.

[althon]

I try many things last night. No success anyway

Still the same f.....g ERROR.

I think that this is not from the driver, but from the kernel or something.

I did a research in Google and find something for FreeBSD with the same error.

The peoples there was talking about kernel extensions and HAL........ I didn't understand nothing.

[redratfish]

i have an hp with whitelist. i edit my atheros card eprom chip via external willem programmer. and change the ven-id and all with broadcom id . the laptop now boots with out the 104 whitelist error.

its a atherous card . now showing as broadcom card in leopard . i need to know what i should edit in leo for the card to work.

[kc8jdc]

I have followed the instructions for rebranding. Now lspci shows like the last step of your instructions.

Network controller [0280]: Atheros Communications, Inc. AR5006EG ...................... [168c:001c] (rev 01)

Subsystem: Apple Computer Inc. Device [106b:004e]

 

I have rebooted, checked System Configuration, apple airport utility and my card still does not show up. I do get an error from console that shows:

 

ath_attach: devid 0x1c

unable to attach hardware; HAL status 13

 

I have also checked the AirportAtheros.kext and made sure that both the 168c:1c and the 106b:4e were in there. I have also tried it with only one of these. I have deleted the cache and the mkext and have repaired permissions in disk utility.

 

I am using an Acer Aspire One with Kalyway 10.5.2 (with updates to 10.5.5 vanilla kernel).

What is the next step?