trabis wrote:
> Based on lwfinger instruction, here is the output in each step. What is
> missing? (I am using TRENDnet TEW-443PI PCI adapter)
>
> 1)# /sbin/lspci -n
> 00:0e.0 0200: 168c:0013 (rev 01) <===
>
> 2)# dmesg
> ath5k_pci 0000:00:0e.0: registered as ‘phy0’
> ath5k phy0: Atheros AR5213A chip found (MAC: 0x79, PHY: 0x45)
> ath5k phy0: RF2112A 2GHz radio found (0x56)
>
>
> 3)# /usr/sbin/iwconfig
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> wmaster0 no wireless extensions.
>
> *wlan0 IEEE 802.11g ESSID:"" *
> Mode:Managed Frequency:2.412 GHz Access Point:
> Not-Associated
> Tx-Power=27 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
>
> 4)# sudo /usr/sbin/iwlist scan
> root’s password:
> lo Interface doesn’t support scanning.
>
> eth0 Interface doesn’t support scanning.
>
> wmaster0 Interface doesn’t support scanning.
>
> wlan0 No scan results
Does the ath5k driver in openSUSE 11.0 work? Please search through the
postings on the forum to answer that. If not, you might try the
compat-wireless package. There has been considerable work on Atheros
drivers in the past month - the new code should be in compat.
trabis wrote:
> Larry,
>
> It’s hard to tell whether it is supported on opensuse 11 or not.
>
> # /usr/sbin/iwconfig wlan0 essid “manduk”
> Error for wireless request “Set ESSID” (8B1A) :
> SET failed on device wlan0 ; Operation not permitted.
That is not what I said. I know it is supported due to the interface
appearing in the iwconfig listing. The problem is that the driver can
be completely broken for your card, but it will load as long as it
recognizes your PCI ID. You need to check in the forum, and on the web
to see what kernel, if any, actually works with that device.
Larry, honestly, I could not really understand what you were saying.
Anyway, here is quick summary for the solution after too much trials and errors. Among so many different solutions on the web, I decided to go with ndiswrapper one.) In my opinion, this could be more general solution which could be applied to different Linux distros.
update /etc/modprobe.d/blacklist file with ‘blacklist ath5k’ at the end of the file in my case)
copied window driver files into temp directory and run ‘ndiswrapper -i net5211.inf’ in my case).
Luckily, openSuse has ndiswrapper packages and this was easy. But if you are using Ubuntu, this is another story. You have to install ndiswrapper first before using it in Ubuntu environment.
run ‘ndiswrapper -l’ just for validation
run ‘modprobe ndiswrapper’ and reboot
After reboot, I was getting another error message saying 'Enter password for default keyring to unlock".
In this case, remove default.keyring file. Run ‘rm /home/your_userid/.gnomes2/keyrings/default.keyring’ and you can assign new password.
Hew…,
it was really HARD long long journey to set up Linux wireless for new beginners like me. Hope Linux makes wireless setup more easier in the future.
well done trabis for getting through all this and getting the card working, and for documenting so beautifully all you did; hopefully, those coming after can find your post and be guided by it;
we remain as lurkers on the wireless channel;hoping to pick up grains of wisdom; I continue to praise our DynalinkRTA1335 with its big reliable wired cables that come out and plug into our two computers; and our small portable ASUS can hitch a ride too on the wired router when needed at hom