Last Resort

[lwfinger]

****pixie wrote:
> Hey Larry,
>
> I typed in ls -l and recieved this: (only posting what is relevant to
> network)
>
> drwxr-xr-x 5 1102 1102 4096 2008-1-6 12:57 broadcom-wl-4.150.10.5

What do you get with

ls -lR broadcom-wl-4.150.10.5

Larry

[damnpixie]

Hey Larry,

I get a very long response when I type in that command. Since I'm having trouble sending info between my Windows and OpenSUSE, I wasn't able to copy everything (but can keep trying). Do you need to see everything, or is there a certain part I can write?

I hope this isn't contradictory to fixing this problem, but OpenSUSE with KDE 4 had programs that just kept crashing, so I re-installed it with KDE 3.5 (and then tried all the instructions all over again).

[lwfinger]

****pixie wrote:
> Hey Larry,
>
> I get a very long response when I type in that command. Since I'm
> having trouble sending info between my Windows and OpenSUSE, I wasn't
> able to copy everything (but can keep trying). Do you need to see
> everything, or is there a certain part I can write?

Try typing just

ls -l ~/broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o

> I hope this isn't contradictory to fixing this problem, but OpenSUSE
> with KDE 4 had programs that just kept crashing, so I re-installed it
> with KDE 3.5 (and then tried all the instructions all over again).

No, the desktop won't alter the driver result. BTW, you made a good move by
switching. KDE4 in 11.1 seems to be OK, but it certainly wasn't in 11.0.

Larry

[damnpixie]

The reply to that command was:

-rw-r--r-- 1 1102 1102 1194265 2008-01-06 12:57 /home/evetracy/broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o

-Eve

[lwfinger]

****pixie wrote:
> The reply to that command was:
>
> -rw-r--r-- 1 1102 1102 1194265 2008-01-06 12:57/home/evetracy/broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o

You should be able to use the command

sudo b43-fwcutter /home/evetracy/broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o

Larry

[damnpixie]

Hey Larry,

That worked! The driver was unpacked. How do I know if wireless is working, now? I have restarted it and entered a new wlan ssid connection, but did not see any indication that it was working.

Thank you for your help.

-Eve

[lwfinger]

****pixie wrote:
> Hey Larry,
>
> That worked! The driver was unpacked. How do I know if wireless is
> working, now? I have restarted it and entered a new wlan ssid
> connection, but did not see any indication that it was working.

Are you configuring from KNetworkManager (the applet in the corner)? If so,
clicking on the icon will show what connection you are using. If you have a wire
plugged in, it will take precedence.

First of all, look at 'dmesg | grep b43'. See if that indicates any errors.

The next step is to look at the output from 'sudo /usr/sbin/iwlist scan'.

We should also see the output of '/sbin/iwconfig'.

Larry

[damnpixie]

dmesg | grep b43

b43-phy0: Broadcom 4311 WLAN found
input: b43-phy0 as /devices/virtual/input/input9
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed
b43-phy0 ERROR: You must go to b43 - Linux Wireless and download the latest firmware (version 4).

sudo /usr/sbin/iwlist scan

l0 Interface doesn't support scanning
eth0 Interface doesn't support scanning
wmaster0 Interface doesn't support scanning
wlan0 Interface doesn't support scanning: Network is down

/sbin/iwconfig

bash: /sbin/iwconfig: No such file or directory.

[lwfinger]

****pixie wrote:
> -dmesg | grep b43-
>
> b43-phy0: Broadcom 4311 WLAN found
> input: b43-phy0 as /devices/virtual/input/input9
> b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed
> b43-phy0 ERROR: You must go to 'b43 - Linux Wireless'
> (http://linuxwireless.org/en/users/Dr...devicefirmware) and
> download the latest firmware (version 4).

Obviously unpacking the firmware did not work. It still is not available.

[damnpixie]

So this means that I won't be able to get wireless, correct?