/sbin/lspci -n
04:00.0 0280: 14e4:4315 (rev 01) ----**here it is said 4315 and it should be 4312**??!!
05:00.0 0200: 10ec:8168 (rev 03)
dmesg | less
9.553415] Bluetooth: Generic Bluetooth USB driver ver 0.6
9.554089] usbcore: registered new interface driver btusb
9.993957] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
/usr/sbin/iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
~> /usr/sbin/iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wlan0 Failed to read scan data : Network is down
So as far as I can see is that my card is there but in the network manager it said “device not ready, firmware missing”
> /sbin/lspci -n
> 04:00.0 0280: 14e4:4315 (rev 01) ----here it is said 4315 and it should be 4312??!!
No. A BCM4312 802.11 b/g device has IDs 14e4:4315. That is correct. Broadcom may
have screwed up, but that is the way it is.
Where is the appropriate output from dmesg? Your title says “Broadcom-wl” and
“firmware missing”. That is impossible as wl has the firmware built into the
driver. Only b43 needs external firmware. Which one are you using?
Hello and thanks for replying.
Well I did the dmesg and it showed that I had to download the b43-fwcutter and then I run the script: /usr/sbin/install_bcm43xx_firmware
that installed successfully. I rebooted and found that my wireless is up and I can see my network.
However I can’t login into my network after writing down my pass wep key. It keep trying with no success.
When I choose my wl-network a pop up message for the wireless network authentication show that wireless security is wep 40/128-bit key(Hexor ASCII) and I fill my key which is ‘36c73688a0’ then I click connect!
This: 36c73688a0
Is not what is required. It needs to be 128 charterers. You can find that in the router/access point (or ask your system admin)
Or switch the router to use WPA2 instead of WEP, because WEP is next to useless anyway.
If you are using b43, you should not install ‘wl’ - so make sure it’s not installed.
I did what you said and I didn’t install the wl.
For my wep key, it’s the only key that I have and always used for my wireless in Linux and windows.
I still can’t use it with Suse.
On 08/11/2011 03:46 PM, ehabareda wrote:
>
> Hello again,
>
> I did what you said and I didn’t install the wl.
> For my wep key, it’s the only key that I have and always used for my
> wireless in Linux and windows.
> I still can’t use it with Suse.
What does dmesg say?
KDE or Gnome?
NetworkManager or ifup? If NM, look in /var/log/NetworkManager.
On 08/11/2011 04:46 PM, ehabareda wrote:
>
> lwfinger;2374276 Wrote:
>> On 08/11/2011 03:46 PM, ehabareda wrote:
>>>
>>> Hello again,
>>>
>>> I did what you said and I didn’t install the wl.
>>> For my wep key, it’s the only key that I have and always used for my
>>> wireless in Linux and windows.
>>> I still can’t use it with Suse.
>>
>> What does dmesg say?
>>
>> KDE or Gnome?
>>
>> NetworkManager or ifup? If NM, look in /var/log/NetworkManager.
>
> dmesg
>
>
> Code:
> --------------------
> 78.445077] wlan0: authenticate with 08:76:ff:18:82:04 (try 1)
> 78.447421] wlan0: authenticated
> 78.447471] wlan0: associate with 08:76:ff:18:82:04 (try 1)
> 78.453423] wlan0: RX AssocResp from 08:76:ff:18:82:04 (capab=0x11 status=0 aid=4)
> 78.453429] wlan0: associated
> 78.455512] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> 83.217170] ieee80211 phy0: wlan0: No probe response from AP 08:76:ff:18:82:04 after 500ms, disconnecting.
> 83.224390] cfg80211: Calling CRDA to update world regulatory domain
> 83.231760] cfg80211: World regulatory domain updated:
> 83.231765] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> 83.231770] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> 83.231774] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> 83.231778] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> 83.231782] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> 83.231786] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> 84.629922] wlan0: authenticate with 08:76:ff:18:82:04 (try 1)
> 84.829129] wlan0: authenticate with 08:76:ff:18:82:04 (try 2)
> 85.029194] wlan0: authenticate with 08:76:ff:18:82:04 (try 3)
> 85.229190] wlan0: authentication with 08:76:ff:18:82:04 timed out
> 88.514186] wlan0: no IPv6 routers present
> 136.799636] CE: hpet increased min_delta_ns to 20113 nsec
As you can see from the messages at 78 seconds, you do have the correct key. The
NIC is authenticating and associating with the AP; however, the AP then stops
responding.
I did what you told me and installed the compact-wireless packages.
Restart, then try to login to the wl-network and keep on refusing my key. Do I have to uninstall something before that?
I have a request from you please not to give up with me.
I have tried linux from ubuntu, debian, mint, arch then suse.
Everything in suse is near perfect (It has changed dramatically since the 9 versions) so just a big help from you guys will keep me here.
Sorry for begging.
On 08/11/2011 05:46 PM, ehabareda wrote:
>
> I did what you told me and installed the compact-wireless packages.
> Restart, then try to login to the wl-network and keep on refusing my
> key. Do I have to uninstall something before that?
> I have a request from you please not to give up with me.
> I have tried linux from ubuntu, debian, mint, arch then suse.
> Everything in suse is near perfect (It has changed dramatically since
> the 9 versions) so just a big help from you guys will keep me here.
> Sorry for begging.
Once again, where is the dmesg output? If the driver from compat-wireless also
has the same problem, then there may be something flaky with your AP.
On 08/11/2011 06:06 PM, ehabareda wrote:
>
> dmesg…
>
>
> Code:
> --------------------
> 27.688268] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> 29.159577] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> 29.161279] b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
> 29.161288] b43-phy0 ERROR: This device does not support DMA on your system. It will now be switched to PIO.
This DMA problem should have been fixed in compat-wireless. To check that you
are using it, please post the output of
On 08/12/2011 11:36 AM, ehabareda wrote:
>
> Hello lwfinger,
>
> Out of no where. I unpluged my wired network and rebooted and bang…my
> wireless is perfectly working?
> I don’t know what exactley happened but it works.
>
> For the outputs if it will helps anybody:
>
> Code:
> --------------------
> rmmod /lib/modules/2.6.37.6-0.7-desktop/kernel/drivers/net/wireless/b43/b43.ko
Well, whenever the wired network is connected, it will be selected and wireless
will be deselected. FYI, you are using the standard b43 driver, not the one from
compat-wireless. Whenever you select a XX-kmp-YY (kernel module package), you
need to make sure that the YY matches the kernel you use. In your current
system, you are using the desktop kernel. I suspect that you installed the
-default version.