Hello,
I currently just formatted my Dell Latitude D600 and did an install of openSUSE v11.0 on it. Now, no matter what I find to walk me through setting up my wireless connection, I get nowhere.
I have a PCMCIA card, 3Com OfficeConnect Wireless 108Mbps 11g XJACK PC card, 3C# 3CRXJK10075, and have yet to be able to figure it out.
Help?
I have gone through the “My Wireless doesn’t work” post by lwfinger and have done what it says there. When running iwconfig, I came back with this:
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
Then I ran the iwlist scan and it came back with this:
wlan0 No scan results.
I don’t know what your device is. Please run the command ‘/sbin/lspci
-nnv’ and post the first two lines that correspond to your wireless
device.
Larry
I’ll go ahead and post everything. This is the only thing in the /sbin/lspci -nnv that I saw that corresponded to my device, as it was the only 3Com device listed.
*Ethernet Controller [0200]: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor [168c:0013] (rev 01)
Subsystem: 3Com Corporation Device [a727:6801]
Flags: bus master, medium devsel, latency 168, IRQ 11
Memory at f8000000 (32-bit, non-prefetchable) [size=64]
Capabilities: <access denied>
Kernel driver in use: ath5k_pci
Kernel module: ath5k[/size]
I did go through and see what hardware compatibility it would need, and it said PCMCIA Wireless cards from 3Com required a downloaded firmware to work with openSUSE, so I did that. Not sure if I did it right … it downloaded as a .arm file, and it told me to rename it to isl3886, but I don’t know if I needed to keep it as a .arm extension or not.*
chroberts wrote:
> I’ll go ahead and post everything. This is the only thing in the
> -/sbin/lspci -nnv- that I saw that corresponded to my device, as it was
> the only 3Com device listed.
>
> -Ethernet Controller [0200]: Atheros Communications Inc. AR5212/AR5213
> Multiprotocol MAC/baseband processor [168c:0013] (rev 01)
> Subsystem: 3Com Corporation Device [a727:6801]
> Flags: bus master, medium devsel, latency 168, IRQ 11
> Memory at f8000000 (32-bit, non-prefetchable) [size=64]
> Capabilities: <access denied>
> Kernel driver in use: ath5k_pci
> Kernel module: ath5k-
>
> I did go through and see what hardware compatibility it would need, and
> it said PCMCIA Wireless cards from 3Com required a downloaded firmware
> to work with openSUSE, so I did that. Not sure if I did it right … it
> downloaded as a .arm file, and it told me to rename it to -isl3886-, but
> I don’t know if I needed to keep it as a .arm extension or not.
No, I don’t think it should have the .arm extension. When there is
doubt, check the output of dmesg to see what firmware files are trying
to be loaded.
Larry
[/size]
I tried that, and I literally got nothing back. No data at all, it just went back to the input screen chris@linux-gwez~>
I’m very much a newbie when it comes to Linux, if you couldn’t tell.
And when trying to edit any configuration already in YaST2, it ends up going through the ‘checklist’ of sorts, getting to the ‘Activate network services,’ and then tells me that it ‘Cannot access installation media (Medium 1).’
Is it trying to download something from the internet, even though with me trying to configure the connection, it doesn’t have access to it?
There is NO WAY you could enter the command dmesg and get nothing
back!!! That one is built in. Now, try it again.
Larry
wince Yeah, it was another command that I tried that gave me nothing back.
I took and renamed the extension for th isl3886 to .fw, because that seemed to be a pattern in the /lib/firmware directory, and the dmesg, as I could see, read like this, the only thing with ‘pcmcia,’ which is the format of the wireless device.
**<Line 383>**pcmcia: parent PCI bridge I/O window: 0xd000 - 0xefff
cs: IO port probe 0xd000-0xefff: clean.
pcmcia: parent PCI bridge Memory window: 0xf6000000 - 0xfbffffff
**<Line 386>**pcmcia: parent PCI bridge Memory window: 0x30000000 - 0x37ffffff
<…snip 7 lines…>
**<Line 394>*pcmcia: parent PCI bridge I/O window: 0xd000 - 0xefff
cs: IO port probe 0xd000-0xefff: clean.
pcmcia: parent PCI bridge Memory window: 0xf6000000 - 0xfbffffff
pcmcia: parent PCI bridge Memory window: 0x30000000 - 0x37ffffff
ACPI: PCI Interrupt 0000:00:1f.5 -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:1f.5 to 64
pccard: CardBus inserted into slot 0
pccard: **PCMCIA ****card inserted into slot 1
cs: memory probe 0xf6000000-0xfbffffff: excluding 0xf6000000-0xf65fffff 0xf6c00000-0xf71fffff 0xf7e00000-0xf83fffff 0xf9c00000-0xfa1fffff 0xfae00000-0xfb3fffff
**<Line 403>**pcmcia: registering new device pcmcia1.0
<… snip 50 lines to the end …>
That’s the only stuff with PCMCIA in it. Nothing with 3Com or anything that would refer strictly to the card.
I have no idea how to look for the specific firmware. I searched for isl3886 and got nothing.*
The thing you should be looking for in the dmesg output is ath5k,
which is the driver for your device. Incidentally, you have a Cardbus
interface which plugs into the PCMCIA slot, but is treated by the
system as a PCI device.
Two specific commands to enter:
lsmod | grep ath5k
If this one shows nothing, then try the following:
sudo /sbin/modprobe -v ath5k
and report what comes back. In addition, do the following:
dmesg | grep ath5k
Larry
lsmod | grep ath5k
ath5k 97156 0
mac80211 178196 1 ath5k
sudo /sbin/modprobe -v ath5k
This one, asked for the root password, and then did absolutely nothing. It went back to the command prompt.
dmesg | grep ath5k
ath5k_pci 0000:03:00.0: registered as ‘phy0’
ath5k phy0: Atheros AR5213A chip found (MAC: 0x79, PHY: 0x45)
ath5k phy0: RF2112A 2GHz radio found (0x56)
chroberts wrote:
> -lsmod|grep_ath5k-
>
> -ath5k 97156 0
> mac80211 178196 1 ath5k-
>
> -sudo/sbin/modprobe_-v_ath5k_-
>
> This one, asked for the root password, and then did absolute nothing.
> Went back to the command prompt.
You don’t read very well. I told you to do this one only if the first
one showed nothing. The driver was already loaded, which is why
loading it did nothing.
> -dmesg|grep_ath5k-
>
> -ath5k_pci 0000:03:00.0: registered as ‘phy0’
> ath5k phy0: Atheros AR5213A chip found (MAC: 0x79, PHY: 0x45)
> ath5k phy0: RF2112A 2GHz radio found (0x56)-
We don’t see any errors here. You should examine the entire dmesg
output to see if there are any complaints about missing firmware.
The other thing to do is to enter the following
sudo /usr/sbin/iwlist scan
If this one returns information about your AP, then all you have to do
is configure the interface.
Larry
Again, I must point out, I have only had about 2 days, including today, worth of experience with Linux. Pardon me if I don’t do everything, even if not necessary, while I learn the system and the terminal.
sudo /usr/sbin/iwlist scan
*lo Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning.
wmaster0 Interface doesn’t support scanning.
wlan0 No scan results*
I also searched the dmesg and found no message saying there was missing firmware.
Does your computer have a switch to kill wireless? Is it allowing the
radio to work?
Larry
Nope. The only thing I know of that would kill the wireless for this thing is actually pushing the spring-loaded antennae on the PCMCIA card itself in, and I’ve made sure that it was out and the LED light was on and active. However, it doesn’t seem to be getting any activity from the network, and I have no idea why.
I had an odd problem with a dual boot laptop. It has the little switch on the side that turns wifi on and off.
I was in Win XP and rebooted into opensuse 11. I could not get the wifi to work no matter what I tried. I tried for days to solve the problem, XP worked, suse did not. By accident, I discovered that suse had turned off the radio. I had to go through the whole enabling wifi again.
Well, this is a full install of Linux, no XP at all. And I went through and have tried everything I can think of … the Wifi is working, I can tell that much from it accessing the ath5k drivers and it coming up in the lspci, but I still cannot get it to talk to the card and find my network.