wireless scan shows nothing

Hello all, It’s been a while since ive run any Linux OS, but after reading about Osuse, i decided to partition my drive and check it out. Just downloaded and installed OpenSUSE. I have access to internet via my hard wired lan port, but wireless has me confused. Any help on this will be greatly appreciated.

Dell D600.

I have allowed all updates to install, and added my wireless connection using KDE Control module. When i hit the scan button the scan box appears but nothing is picked up. My router is linksys, and its wide open (no encryption, nor hidden).

some other info that might help.
lspci
02:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02)

iwlist
Usage: iwlist [interface] scanning [essid NNN] [last]
[interface] frequency
[interface] channel
[interface] bitrate
[interface] rate
[interface] encryption
[interface] keys
[interface] power
[interface] txpower
[interface] retry
[interface] ap
[interface] accesspoints
[interface] peers
[interface] event
[interface] auth
[interface] wpakeys
[interface] genie
[interface] modulation

also, when i type
sudo /sbin/ifconfig wlan0 up
i get this msg:
SIOCSIFFLAGS: Unknown error 132

Thats about as far as i got with the diagnostics.

I mainly only use wireless on my laptop, so any help would really be appreciated…

On 03/16/2010 08:46 PM, apfing wrote:
>
> Hello all, It’s been a while since ive run any Linux OS, but after
> reading about Osuse, i decided to partition my drive and check it out.
> Just downloaded and installed OpenSUSE. I have access to internet via my
> hard wired lan port, but wireless has me confused. Any help on this will
> be greatly appreciated.
>
> Dell D600.
>
> I have allowed all updates to install, and added my wireless connection
> using KDE Control module. When i hit the scan button the scan box
> appears but nothing is picked up. My router is linksys, and its wide
> open (no encryption, nor hidden).
>
> some other info that might help.
> lspci
> 02:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
> Wireless LAN Controller (rev 02)
>
> iwlist
> Usage: iwlist [interface] scanning [essid NNN] [last]
> [interface] frequency
> [interface] channel
> [interface] bitrate
> [interface] rate
> [interface] encryption
> [interface] keys
> [interface] power
> [interface] txpower
> [interface] retry
> [interface] ap
> [interface] accesspoints
> [interface] peers
> [interface] event
> [interface] auth
> [interface] wpakeys
> [interface] genie
> [interface] modulation
>
> also, when i type
> sudo /sbin/ifconfig wlan0 up
> i get this msg:
> SIOCSIFFLAGS: Unknown error 132
>
> Thats about as far as i got with the diagnostics.
>
>
> I mainly only use wireless on my laptop, so any help would really be
> appreciated…

What does ‘dmesg | grep b43’ show? I expect that it will show that firmware
is not available. If that is the case, and you have an Internet connection,
issue the command:


sudo  /usr/sbin/install_bcm43xx_firmware

If you do not have Internet access from openSUSE, then read the 3rd stickie in
this forum. It contains a prescription for downloading with some other system.

Almost certain to be as explained above. Forgive me if this is not applicable, (or is obvious to you already), but make sure that your wireless device is physically switched on first. That can also cause this type of error.

Almost certain to be as explained above. Forgive me if this is not applicable, (or is obvious to you already), but make sure that your wireless device is physically switched on first. That can also cause this type of error.

Thank you for your reply. I do have wireless enabled… I wish It was that easy :wink:

thanks

What does ‘dmesg | grep b43’ show? I expect that it will show that firmware
is not available. If that is the case, and you have an Internet connection,
issue the command:

sudo /usr/sbin/install_bcm43xx_firmware

If you do not have Internet access from openSUSE, then read the 3rd stickie in
this forum. It contains a prescription for downloading with some other system.

Thank you for your reply. I do have connection via eth0, but not wireless. I made a cable to reach into my living room so i do currently have wired access to the net. I ran the commands and posted results below.


command : ‘dmesg | grep b43’
I get


    13.573361] b43-pci-bridge 0000:02:03.0: PCI INT A -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
   13.681132] b43legacy-phy0: Broadcom 4306 WLAN found
   33.552064] b43legacy ssb0:0: firmware: requesting b43legacy/ucode4.fw
   33.567126] b43legacy-phy0 ERROR: Firmware file "b43legacy/ucode4.fw" not found or load failed.
   33.567161] b43legacy-phy0 ERROR: You must go to [b43 - Linux Wireless](http://linuxwireless.org/en/users/Drivers/b43#devicefirmware) and download the correct firmware (version 3).
   33.772061] b43legacy ssb0:0: firmware: requesting b43legacy/ucode4.fw
   33.786930] b43legacy-phy0 ERROR: Firmware file "b43legacy/ucode4.fw" not found or load failed.
   33.786966] b43legacy-phy0 ERROR: You must go to [b43 - Linux Wireless](http://linuxwireless.org/en/users/Drivers/b43#devicefirmware) and download the correct firmware (version 3).


Ok, so i ran the command sudo /usr/sbin/install_bcm43xx_firmware
and i got



######################################################################## 100.0%                                 
Extracting b43 firmware                                                                                         
This file is recognised as:                                                                                     
  ID         :  FW13                                                                                            
  filename   :  wl_apsta_mimo.o                                                                                 
  version    :  410.2160                                                                                        
  MD5        :  cb8d70972b885b1f8883b943c0261a3c                                                                
Extracting b43/pcm5.fw                                                                                          
Extracting b43/ucode15.fw                                                                                       
Extracting b43/ucode14.fw                                                                                       
Extracting b43/ucode13.fw                                                                                       
Extracting b43/ucode11.fw                                                                                       
Extracting b43/ucode9.fw                                                                                        
Extracting b43/ucode5.fw                                                                                        
Extracting b43/lp0bsinitvals15.fw                                                                               
Extracting b43/lp0initvals15.fw                                                                                 
Extracting b43/lp0bsinitvals14.fw                                                                               
Extracting b43/lp0initvals14.fw                                                                                 
Extracting b43/a0g1bsinitvals13.fw                                                                              
Extracting b43/a0g1initvals13.fw                                                                                
Extracting b43/b0g0bsinitvals13.fw                                                                              
Extracting b43/b0g0initvals13.fw                                                                                
Extracting b43/lp0bsinitvals13.fw                                                                               
Extracting b43/lp0initvals13.fw                                                                                 
Extracting b43/n0absinitvals11.fw                                                                               
Extracting b43/n0bsinitvals11.fw                                                                                
Extracting b43/n0initvals11.fw                                                                                  
Extracting b43/a0g1bsinitvals9.fw                                                                               
Extracting b43/a0g0bsinitvals9.fw                                                                               
Extracting b43/a0g1initvals9.fw                                                                                 
Extracting b43/a0g0initvals9.fw                                                                                 
Extracting b43/b0g0bsinitvals9.fw                                                                               
Extracting b43/b0g0initvals9.fw
Extracting b43/a0g1bsinitvals5.fw
Extracting b43/a0g0bsinitvals5.fw
Extracting b43/a0g1initvals5.fw
Extracting b43/a0g0initvals5.fw
Extracting b43/b0g0bsinitvals5.fw
Extracting b43/b0g0initvals5.fw

Downloading b43legacy firmware
######################################################################## 100.0%
Extracting b43legacy firmware
This file is recognised as:
  ID         :  FW10
  filename   :  wl_apsta.o
  version    :  295.14
  MD5        :  e08665c5c5b66beb9c3b2dd54aa80cb3
Extracting b43legacy/ucode2.fw
Extracting b43legacy/ucode4.fw
Extracting b43legacy/ucode5.fw
Extracting b43legacy/ucode11.fw
Extracting b43legacy/pcm4.fw
Extracting b43legacy/pcm5.fw
Extracting b43legacy/a0g0bsinitvals2.fw
Extracting b43legacy/b0g0bsinitvals5.fw
Extracting b43legacy/a0g0initvals5.fw
Extracting b43legacy/a0g1bsinitvals5.fw
Extracting b43legacy/a0g0initvals2.fw
Extracting b43legacy/a0g1initvals5.fw
Extracting b43legacy/b0g0bsinitvals2.fw
Extracting b43legacy/b0g0initvals5.fw
Extracting b43legacy/b0g0initvals2.fw
Extracting b43legacy/a0g0bsinitvals5.fw

b43 firmware successfully installed.
b43legacy firmware successfully installed.
****************************

I removed the wireless connection and added a new one after this, and still nothing comes up on scan. I’m going to try a reboot and see if that makes any difference.

Thanks

yea, still nothing. But now when i run the command
dmesg | grep b43

I get


    9.634395] b43-pci-bridge 0000:02:03.0: PCI INT A -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
    9.790329] b43legacy-phy0: Broadcom 4306 WLAN found
   30.552056] b43legacy ssb0:0: firmware: requesting b43legacy/ucode4.fw
   30.655534] b43legacy ssb0:0: firmware: requesting b43legacy/pcm4.fw
   30.855416] b43legacy ssb0:0: firmware: requesting b43legacy/b0g0initvals2.fw
   31.132065] b43legacy-phy0: Loading firmware version 0x127, patch level 14 (2005-04-18 02:36:27)
   31.197410] Registered led device: b43legacy-phy0::tx
   31.197491] Registered led device: b43legacy-phy0::rx
   31.197561] Registered led device: b43legacy-phy0::radio

Which looks much better then the first time i ran it, but still nothing when i scan.
BAsed on what you see above, is there any other ideas or suggestions? Or did i miss something?

Thanks again

> I removed the wireless connection and added a new one after this, and
> still nothing comes up on scan. I’m going to try a reboot and see if
> that makes any difference.

It should. You could also have done the following:


sudo  /sbin/modprobe  -rv  b43
sudo  /sbin/modprobe  -v   b43

On 03/17/2010 05:46 PM, apfing wrote:
>
> yea, still nothing. But now when i run the command
> dmesg | grep b43
>
> I get
>
> Code:
> --------------------
>
> 9.634395] b43-pci-bridge 0000:02:03.0: PCI INT A → Link[LNKB] → GSI 5 (level, low) → IRQ 5
> 9.790329] b43legacy-phy0: Broadcom 4306 WLAN found
> 30.552056] b43legacy ssb0:0: firmware: requesting b43legacy/ucode4.fw
> 30.655534] b43legacy ssb0:0: firmware: requesting b43legacy/pcm4.fw
> 30.855416] b43legacy ssb0:0: firmware: requesting b43legacy/b0g0initvals2.fw
> 31.132065] b43legacy-phy0: Loading firmware version 0x127, patch level 14 (2005-04-18 02:36:27)
> 31.197410] Registered led device: b43legacy-phy0::tx
> 31.197491] Registered led device: b43legacy-phy0::rx
> 31.197561] Registered led device: b43legacy-phy0::radio
>
> --------------------
>
>
> Which looks much better then the first time i ran it, but still nothing
> when i scan.
> BAsed on what you see above, is there any other ideas or suggestions?
> Or did i miss something?

No, that should do it as long as you scan as root.


sudo  /usr/sbin/iwlist  scan

The above scan should work even if your SSID is hidden. Note: That is not
recommended.

yea, my ssid is broadcasted, network mode is mixed.
It shows up with many others (neighbors) when i boot to windows just not here in Osuse.

I ran the command ‘sudo /usr/sbin/iwlist scan’ under root, and got


lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

wmaster0  Interface doesn't support scanning.

wlan0     No scan results

anything else i should check?

Thanks

On 03/17/2010 06:16 PM, apfing wrote:
>
> yea, my ssid is broadcasted, network mode is mixed.
> It shows up with many others (neighbors) when i boot to windows just
> not here in Osuse.
>
> I ran the command ‘sudo /usr/sbin/iwlist scan’ under root, and got
>
> Code:
> --------------------
>
> lo Interface doesn’t support scanning.
>
> eth0 Interface doesn’t support scanning.
>
> wmaster0 Interface doesn’t support scanning.
>
> wlan0 No scan results
>
> --------------------
>
>
>
> anything else i should check?

Unless something else showed up in dmesg, I have no idea what is wrong. I have a
device just like yours - BCM4306/2 - that works. I have not tried it with the
standard kernel 2.6.31. I’m currently running 2.6.34-rc1 on all my machines.
From what I remember, there are no changes in b43legacy that should make a newer
kernel work and yours fail. The machine that uses the BCM4306/2 is running a
long-term test and is not available at the moment, but I did test b43legacy with
a BCM4303 that worked. You might try downloading

http://download.opensuse.org/factory/repo/oss/suse/i586/kernel-default-2.6.33-5.5.i586.rpm

(all on one line). I think you have a 32-bit system. If 64 bit, then change both
instances of i586 to x86_64.

After downloading is complete, then

sudo rpm -iv kernel-default-2.6.33-5.5.i586.rpm

This will install a 2.6.33 kernel as an additional option in the GRUB menu. It
should work.

Thanks i’ll give that a try. Ive read a lot about it, and nothing really points to anything other then turning the wireless on (FN-F2). So i’m at a loss, and glad to try anything.

yea, installed to 2.6.33, and still no worky :frowning: .

OSUSE has run with everything ive needed it to, from my phone, graphic apps, email, its almost perfect. I’m starting to wonder if im seeing the settings right, or maybe im completly missing something. Is there a difference between kde control module and yast? What is network services? So many questions lol.

Hate to bother folks, but i really want to get this wireless working. I’ll keep researching, if anyone thinks of anything else feel free.

Thanks

On 03/17/2010 09:16 PM, apfing wrote:
>
> yea, installed to 2.6.33, and still no worky :frowning: .
>
> OSUSE has run with everything ive needed it to, from my phone, graphic
> apps, email, its almost perfect. I’m starting to wonder if im seeing the
> settings right, or maybe im completly missing something. Is there a
> difference between kde control module and yast? What is network
> services? So many questions lol.
>
> Hate to bother folks, but i really want to get this wireless working.
> I’ll keep researching, if anyone thinks of anything else feel free.

Please post everything from the dmesg output after the loading of the firmware.
Note: I do not want the beginning.

To answer some of your questions, the KDE control module is used to control the
desktop, while YaST is used to control the system.

You will likely be using NetworkManager to control the connection, but the
device has to be able to scan before NM can do anything.

the only thing that refered to wlan0 in the output of dmesg, was

   33.860924] ADDRCONF(NETDEV_UP): wlan0: link is not ready

On 03/17/2010 10:56 PM, apfing wrote:
>
> lwfinger;2138508 Wrote:
>> On 03/17/2010 09:16 PM, apfing wrote:
>>>
>>> yea, installed to 2.6.33, and still no worky :frowning: .
>>>
>>> OSUSE has run with everything ive needed it to, from my phone,
>> graphic
>>> apps, email, its almost perfect. I’m starting to wonder if im seeing
>> the
>>> settings right, or maybe im completly missing something. Is there a
>>> difference between kde control module and yast? What is network
>>> services? So many questions lol.
>>>
>>> Hate to bother folks, but i really want to get this wireless
>> working.
>>> I’ll keep researching, if anyone thinks of anything else feel free.
>>
>> Please post everything from the dmesg output after the loading of the
>> firmware.
>> Note: I do not want the beginning.
>>
>> To answer some of your questions, the KDE control module is used to
>> control the
>> desktop, while YaST is used to control the system.
>>
>> You will likely be using NetworkManager to control the connection, but
>> the
>> device has to be able to scan before NM can do anything.
>
>
> the only thing that refered to wlan0 in the output of dmesg, was
>
>
> Code:
> --------------------
> 33.860924] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> --------------------

Are you controlling the network devices with ifup or NetworkManager? It looks as
if you are using ifup and have not configured the device, nor given the ifup
command. Incidentally, I suggest using NM.

yea, im using network manager. Ive tried both ifup and nm.

On 03/18/2010 08:56 AM, apfing wrote:
>
> yea, im using network manager. Ive tried both ifup and nm.

Then PLEASE submit the tail of dmesg that I asked for earlier.

Sorry, i wasnt sure what you wanted, i just posted the results that were relevant to wlan0. Here is as much of the tail end I can post from dmesg.

Thanks


           
   12.008065] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2                           
   12.010233] ACPI: Lid Switch [LID]                                                                                  
   12.010334] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3                         
   12.010407] ACPI: Power Button [PBTN]                                                                               
   12.010472] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4                         
   12.010512] ACPI: Sleep Button [SBTN]                                                                               
   12.019271] agpgart-intel 0000:00:00.0: Intel 855PM Chipset                                                         
   12.026211] agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xe0000000                                           
   12.030480] input: PC Speaker as /devices/platform/pcspkr/input/input5                                              
   12.046065] intel_rng: FWH not detected                                                                             
   12.229829] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)                                  
   12.240219] sr0: scsi3-mmc drive: 10x/24x cd/rw xa/form2 cdda tray                                                  
   12.240224] Uniform CD-ROM driver Revision: 3.20                                                                    
   12.240367] sr 1:0:0:0: Attached scsi CD-ROM sr0                                                                    
   12.261884] tg3.c:v3.106 (January 12, 2010)                                                                         
   12.261910] tg3 0000:02:00.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11                              
   12.301625] eth0: Tigon3 [partno(BCM95705A50) rev 3001] (PCI:33MHz:32-bit) MAC address 00:0f:1f:b6:b5:a1            
   12.301632] eth0: attached PHY is 5705 (10/100/1000Base-T Ethernet) (WireSpeed[1])                                  
   12.301636] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]                                                
   12.301639] eth0: dma_rwctrl[763f0000] dma_mask[64-bit]                                                             
   12.321530] ACPI: Battery Slot [BAT0] (battery present)                                                             
   12.326791] ACPI: Battery Slot [BAT1] (battery absent)                                                              
   12.409911] iTCO_vendor_support: vendor-support=0                                                                   
   12.453007] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05                                                         
   12.453106] iTCO_wdt: Found a ICH4-M TCO device (Version=1, TCOBASE=0x0860)                                         
   12.453207] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)                                                    
   12.478840] parport_pc 00:0b: reported by Plug and Play ACPI                                                        
   12.478888] parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA]                       
   12.643128] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:1d/LNXVIDEO:00/input/input6      
   12.643227] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)                                           
   12.727798] yenta_cardbus 0000:02:01.0: CardBus bridge found [1028:011d]                                            
   12.727820] yenta_cardbus 0000:02:01.0: O2: res at 0x94/0xD4: 00/ea                                                 
   12.727823] yenta_cardbus 0000:02:01.0: O2: enabling read prefetch/write burst                                      
   12.784519] ppdev: user-space parallel port driver                                                                  
   12.864723] yenta_cardbus 0000:02:01.0: ISA IRQ mask 0x0418, PCI irq 11                                             
   12.864730] yenta_cardbus 0000:02:01.0: Socket status: 30000006                                                     
   12.864736] pci_bus 0000:02: Raising subordinate bus# of parent bus (#02) from #02 to #06                           
   12.864748] yenta_cardbus 0000:02:01.0: pcmcia: parent PCI bridge I/O window: 0xd000 - 0xefff                       
   12.864754] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xd000-0xefff: clean.                                   
   12.865440] yenta_cardbus 0000:02:01.0: pcmcia: parent PCI bridge Memory window: 0xf6000000 - 0xfbffffff            
   12.865445] yenta_cardbus 0000:02:01.0: pcmcia: parent PCI bridge Memory window: 0x20000000 - 0x27ffffff            
   12.973299] Intel ICH 0000:00:1f.5: PCI INT B -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5                          
   12.973337] Intel ICH 0000:00:1f.5: setting latency timer to 64                                                     
   13.120249] b43-pci-bridge 0000:02:03.0: PCI INT A -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5                     
   13.120314] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x02, vendor 0x4243)                                       
   13.120322] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x04, vendor 0x4243)                                      
   13.120329] ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x01, vendor 0x4243)                                           
   13.120336] ssb: Core 3 found: V90 (cc 0x807, rev 0x01, vendor 0x4243)                                              
   13.120342] ssb: Core 4 found: PCI (cc 0x804, rev 0x07, vendor 0x4243)                                              
   13.120349] ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x04, vendor 0x4243)                                      
   13.123683] ssb: Sonics Silicon Backplane found on PCI device 0000:02:03.0                                          
   13.124147] yenta_cardbus 0000:02:01.1: CardBus bridge found [1028:011d]                                            
   13.271586] yenta_cardbus 0000:02:01.1: ISA IRQ mask 0x0418, PCI irq 11                                             
   13.271592] yenta_cardbus 0000:02:01.1: Socket status: 30000410                                                     
   13.271598] pci_bus 0000:02: Raising subordinate bus# of parent bus (#02) from #06 to #0a                           
   13.271610] yenta_cardbus 0000:02:01.1: pcmcia: parent PCI bridge I/O window: 0xd000 - 0xefff                       
   13.271616] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xd000-0xefff: clean.                                   
   13.272328] yenta_cardbus 0000:02:01.1: pcmcia: parent PCI bridge Memory window: 0xf6000000 - 0xfbffffff            
   13.272332] yenta_cardbus 0000:02:01.1: pcmcia: parent PCI bridge Memory window: 0x20000000 - 0x27ffffff            
   13.272548] cfg80211: Calling CRDA to update world regulatory domain                                                
   13.395276] b43legacy-phy0: Broadcom 4306 WLAN found                                                                
   13.534358] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean.                                     
   13.535388] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean.                                     
   13.537123] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.                                     
   13.537203] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.                                     
   13.537796] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.                                     
   13.540750] phy0: Selected rate control algorithm 'minstrel'                                                        
   13.541191] Broadcom 43xx-legacy driver loaded  Features: PLID, Firmware-ID: FW10 ]                                
   13.554029] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: clean.                                     
   13.555059] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff: clean.                                     
   13.555521] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x820-0x8ff: clean.                                     
   13.555597] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcf7: clean.                                     
   13.560470] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa00-0xaff: clean.                                     
   13.800037] intel8x0_measure_ac97_clock: measured 55361 usecs (2667 samples)                                        
   13.800042] intel8x0: clocking to 48000                                                                             
   13.800868] Intel ICH Modem 0000:00:1f.6: PCI INT B -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5                    
   13.800891] Intel ICH Modem 0000:00:1f.6: setting latency timer to 64                                               
   13.904071] ALSA ac97_codec.c:2173: MC'97 1 converters and GPIO not ready (0xff00)                                  
   14.164058] pcmcia_socket pcmcia_socket1: pccard: PCMCIA card inserted into slot 1                                  
   14.164069] pcmcia_socket pcmcia_socket1: cs: memory probe 0xf6000000-0xfbffffff: excluding 0xf6000000-0xf65fffff 0xf6c00000-0xf71fffff 0xf7e00000-0xf83fffff 0xf9c00000-0xfa1fffff 0xfae00000-0xfb3fffff                                  
   14.177383] pcmcia 1.0: pcmcia: registering new device pcmcia1.0                                                    
   14.809580] Adding 10482372k swap on /dev/sda5.  Priority:-1 extents:1 across:10482372k                             
   15.323528] device-mapper: uevent: version 1.0.3                                                                    
   15.324546] device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com                        
   15.603491] loop: module loaded
   15.761747] fuse init (API version 7.13)
   17.071901] type=1505 audit(1268928301.068:2): operation="profile_load" pid=1122 name=/bin/ping
   17.145508] type=1505 audit(1268928301.144:3): operation="profile_load" pid=1152 name=/sbin/klogd
   17.286591] type=1505 audit(1268928301.284:4): operation="profile_load" pid=1153 name=/sbin/syslog-ng
   17.442953] type=1505 audit(1268928301.440:5): operation="profile_load" pid=1154 name=/sbin/syslogd
   17.590704] type=1505 audit(1268928301.588:6): operation="profile_load" pid=1155 name=/usr/sbin/avahi-daemon
   17.730123] type=1505 audit(1268928301.728:7): operation="profile_load" pid=1156 name=/usr/sbin/identd
   17.863053] type=1505 audit(1268928301.860:8): operation="profile_load" pid=1157 name=/usr/sbin/mdnsd
   18.016318] type=1505 audit(1268928302.016:9): operation="profile_load" pid=1158 name=/usr/sbin/nscd
   18.228429] type=1505 audit(1268928302.228:10): operation="profile_load" pid=1159 name=/usr/sbin/ntpd
   18.359034] type=1505 audit(1268928302.356:11): operation="profile_load" pid=1160 name=/usr/sbin/traceroute
   24.292722] NET: Registered protocol family 10
   24.293385] lo: Disabled Privacy Extensions
   24.951778] pci 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
   25.127819] [drm] Initialized drm 1.1.0 20060810
   25.379967] [drm] radeon defaulting to userspace modesetting.
   25.380965] [drm] Initialized radeon 1.32.0 20080528 for 0000:01:00.0 on minor 0
   25.427950] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
   25.509488] agpgart-intel 0000:00:00.0: AGP 2.0 bridge
   25.509508] agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
   25.509546] pci 0000:01:00.0: putting AGP V2 device into 4x mode
   25.742050] [drm] Setting GART location based on new memory map
   25.742123] [drm] Loading R200 Microcode
   25.742129] platform radeon_cp.0: firmware: requesting radeon/R200_cp.bin
   25.860779] [drm] writeback test succeeded in 2 usecs
   25.924743] powernow: This module only works with AMD K7 CPUs
   29.721129] bootsplash: status on console 0 changed to on
   34.001978] tg3 0000:02:00.0: firmware: requesting tigon/tg3_tso5.bin
   34.352792] ADDRCONF(NETDEV_UP): eth0: link is not ready
   34.580068] b43legacy ssb0:0: firmware: requesting b43legacy/ucode4.fw
   34.593430] b43legacy ssb0:0: firmware: requesting b43legacy/pcm4.fw
   34.602250] b43legacy ssb0:0: firmware: requesting b43legacy/b0g0initvals2.fw
   34.720073] b43legacy-phy0: Loading firmware version 0x127, patch level 14 (2005-04-18 02:36:27)
   34.784847] Registered led device: b43legacy-phy0::tx
   34.784876] Registered led device: b43legacy-phy0::rx
   34.784900] Registered led device: b43legacy-phy0::radio
   34.785351] ADDRCONF(NETDEV_UP): wlan0: link is not ready
   34.842895] NET: Registered protocol family 17
   35.908034] tg3: eth0: Link is up at 100 Mbps, full duplex.
   35.908040] tg3: eth0: Flow control is on for TX and on for RX.
   35.908104] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   39.054740] RPC: Registered udp transport module.
   39.054745] RPC: Registered tcp transport module.
   39.054748] RPC: Registered tcp NFSv4.1 backchannel transport module.
   39.379590] Slow work thread pool: Starting up
   39.380989] Slow work thread pool: Ready
   39.381096] FS-Cache: Loaded
   39.664283] FS-Cache: Netfs 'nfs' registered for caching
   40.650718] CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold
   46.700039] eth0: no IPv6 routers present


Would ndiswrapper help? Ive been finding some hits on it and hearing that it might help me get this resolved. I’m reading good and bad things about it, not sure if i should try. From what im reading i would rather not go that route, but if it gets my wireless working and OS remains stable,. I wont have to use Windoz for wireless connections! :wink:

On 03/18/2010 06:56 PM, apfing wrote:
>
> Would ndiswrapper help? Ive been finding some hits on it and hearing
> that it might help me get this resolved. I’m reading good and bad things
> about it, not sure if i should try. From what im reading i would rather
> not go that route, but if it gets my wireless working and OS remains
> stable,. I wont have to use Windoz for wireless connections! :wink:

No, ndiswrapper will not help. From what I see in the dmesg output, you have the
Ethernet cable plugged in. NM is set to prefer wired to wireless, and will not
connect wireless whenever wired is connected.

Thx, but ive tried unplugging it and scanning countless times. Tried unplugging it and manually putting the ssid in and connecting.

The problem is, my scan turns up with nothing. I have a plethora of wireless routers in my neighborhood (including mine), and i pick them all up in windoz, yet logged into osuse i see nothing. Even tho everything appears to be installed and configured properly, I see nothing. Wireless is enabled, firmware installed.

Im at a loss.