Jump to content

SirNicky

Just Joined
  • Content count

    3
  • Joined

  • Last visited

About SirNicky

  • Rank
    InsanelyMac Protégé
  1. Could you please tell us the brand and build of your laptop. Also please tell us, whether the card was recognized with lspci as AR5006EG or AR5007EG and what specific chipset it has. By the way, it is like BuildSmart said. You cannot make a card nonaccessible by changing the registers "per se". Yet it can be the case that your card is blacklisted by the bios.... Then you need a special device for accessing it which you probably do not have.
  2. Hi, that is the info. In order to find the registers and the values we need the dump: ath_info -d (base address) You just have to insert the -d switch in between the ath_info and the base address, as for your current output. Sometimes you habe to be sudo to do it. What you should do is: Ubuntu 1. sudo ath_info -d (base address) then cut and paste this output 2. lspci -n => note vendor id and device id then sudo lspci -d [<vendor>]:[<device>] -xxxx then cut and paste this output Linpus 1. sudo ath_info -d (base address) then cut and paste this output 2. lspci -n => note vendor id and device id then sudo lspci -d [<vendor>]:[<device>] -xxxx then cut and paste this output
  3. The AR5007EG is a strange beast. I have only had experiences with this card on an Acer Aspire One. With the Linpus original-install it is recognized as a AR5006EG (!) in madwifi. On Ubuntu with the new madwifi it is recognized as a AR5007EG (!). Now there is the unique experience. The ath_info dump differs completely under Linpus and Ubuntu.... I think the ath_info output from Linpus is wrong, since in my opinion it only emulates a AR5006EG. Whereas the lspci output under Linpus is correct.... So, what is the solution. I would say, writing directly to the registers in Ubuntu should be the way to go. However, I have returned the Acer Aspire One. Therefore I cannot post the ath_info dumps. Yet there might be someone who still has one. If so, please post the two EEPROM-dumps. There ist actually still a second method. A czech-guy wrote a program that can change the ids an restore the configuration. This is a highly recommended feature. As you can read, what happens sometimes . I will try to find the link an post it.
×