Click to expand.But why I was able to change ID's 1st time by atheros_eeprom_tool.exe /w512? Now when I try to write original 512byte dump it says that is is written without problem, but after restart values are back. Maybe atheros_eeprom_tool now recognizes my card as 'AR9462' and that locks changes?
Online free web polls generator, Create Online Poll, create polls in easy steps, Use our easy tool,no charge for creating poll, Create-Analyse-Share Online Polls, Get. Restaurant Management Software In Vb Net Savefiledialog there.
Same happens with 'iwleeprom' on Linux - values with ID's are not written, but values with channel info are. On Linux I even forced 'iwleeprom' to recognize my card as 'AR9285' not 'AR9462' - by changing 'iwleeprom' source code but it still can't write to these areas. I really don't understand why it doesn't works! But why I was able to change ID's 1st time by atheros_eeprom_tool.exe /w512? Now when I try to write original 512byte dump it says that is is written without problem, but after restart values are back. Maybe atheros_eeprom_tool now recognizes my card as 'AR9462' and that locks changes?
Same happens with 'iwleeprom' on Linux - values with ID's are not written, but values with channel info are. On Linux I even forced 'iwleeprom' to recognize my card as 'AR9285' not 'AR9462' - by changing 'iwleeprom' source code but it still can't write to these areas.
I really don't understand why it doesn't works! Click to expand.The Atheros EEPROM Tool produces two kind of dumps: the first one is the dump you can make, starting the tool in GUI mode (which is full EEPROM dump), the second one is the 512b dump, taken from the command line. I've compared them both and it seems they are different, the data from the 512b dump can't be found anywhere inside the big dump. My presumption is that both are taken from different areas on the chip.
You know, I was able to make the Atheros EEPROM Tool to ignore the Vendor code by some changes in its source code (included in the archive), but that wasn't enough. It seems there are additional checks in the driver that's being used by the tool.
Its source code is included too, but it's totally unfamiliar to me. You said that your card works in Linux. How exactly did you do that? AFAIK, you should add the new IDs in the ath9k source code and then blacklist the kernel module that would be loaded with these IDs (in this case maybe ath10k). May I ask you about the changes you've made in that code (the tool code and maybe the ath9k code)?
The Atheros EEPROM Tool produces two kind of dumps: the first one is the dump you can make, starting the tool in GUI mode (which is full EEPROM dump), the second one is the 512b dump, taken from the command line. I've compared them both and it seems they are different, the data from the 512b dump can't be found anywhere inside the big dump. My presumption is that both are taken from different areas on the chip.
You know, I was able to make the Atheros EEPROM Tool to ignore the Vendor code by some changes in its source code (included in the archive), but that wasn't enough. It seems there are additional checks in the driver that's being used by the tool. Richie Havens Mixed Bag Rar there.
Its source code is included too, but it's totally unfamiliar to me. You said that your card works in Linux. How exactly did you do that? AFAIK, you should add the new IDs in the ath9k source code and then blacklist the kernel module that would be loaded with these IDs (in this case maybe ath10k). May I ask you about the changes you've made in that code (the tool code and maybe the ath9k code)? Click to expand.I checked the source code of Atheros EEPROM Tool, it seems like some C++ thing which I don't understand too. About two different dumps - I saw that, seems like big dump is incomplete, in Linux it was complete thing.
Needs some thinkering. Which is memory start address for your card?
In linux everything is simple - Linux loads ath9k module for all cards and doesn't asks which card is it. It works OOB. In 'iwleeprom' I changed ath9k driver IDs to detect my card correct as ath9k card, not ath9300. It loads different addresses for ath9k and ath9300.
One of my Atheros AR9280 minipcie cards had some odd undefined regulatory domain (0x6B) configured. This caused even latest Linux ath9k driver to break so I wanted to change it to valid regdom. Which ath9k developers think is sin and are trying to prevent people from doing, but luckily our old friend iwleeprom has Atheros support letting us to fix this. Hi thanks for your instructions, iwleeprom looks to show some promise. Unfortunately it could never get/set the checksums correctly (kernel complains with 'Bad EEPROM checksum').