Last Resort

[damnpixie]

Hey everyone,

I am a Linux newb but I LOVE OpenSUSE and am determined to learn it. Biggest problem is that I haven't been able to get wireless to work on my OpenSUSE 11.0 (haven't tried earlier versions). I have tried many, many different fixits via research: installing Intel pro/100 VE's Linux driver, installing its Vista driver, installing Ndiswrapper, installing progs that come with OpenSUSE, etc. I may install a fresh copy of OpenSUSE 11.0 after I figure out how to do internet, as my OpenSUSE has redundancies now.

Anyway, I have done research and couldn't find a solution. For anyone who would be kind enough to help me, I have followed the sticky requirements for what I need to post.

1) Entered "/sbin/lspci" in terminal.
Response: (ignoring non-network responses)

00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 family) PCI Express Port 1 (rev 02)

00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 family) PCI Express Port 2 (rev 02)

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)

03:00.0 Network Controller: Broadcom Corporation BCM 94311BCG wlan mini-PCI (rev 01)

04:08.0 Ethernet Controller: Intel Corporation PRO/100 VE Network Connection (rev 02)

2)Entered "/sbin/lspci -n"
Responses: (matching above)

00:1c.0 0604: 8086:27d0 (rev 02)
00:1c.1 0604: 8086:27d2 (rev 02)
00:1e.0 0604: 8086:2448 (rev e2)
03:00.0 0280: 14e4:4311 (rev 01)
04:08.0 0200: 8086:1092 (rev 02)

3)Entered "dmesg | less"
Response: (related to network)

b43-phy0: Broadcom 4311 wlan found
(haven't found any lines indicating that I am missing firmware)

4)Entered "/usr/sbin/iwconfig"
Response:

wlan0 -
IEEE 802.11g ESSID= " "
mode: managed channel:0
Access point: Not-Associated
Tx-Power - 0 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 infalid frag: 0
TX recessive retries: 0
Invalid misc: 0
Missed beacon: 0

5)Entered "sudo /usr/sbin/iwlist scan"
Response:

e100: Intel(R) PRO/100 Network drivers 3.5.23-k4-NAPI
e100: Copyright (c) 1999-2006 Intel Corp
ACPI: PCI Interrupt 0000:04:08.0 [A] -> GSI 20 (level, low) -> IRQ 20
PCI: setting latency timer of device 0000:04:08.0 to 64
rtc_cmos 00:06: rtc core:registered rtc_cmos as rtc0
e100: eth0: e100_probe:addr 0x8004000, irq 20, MAC addr 00:e0:b8:bf:82:c2

_________________________________

I also got a response that says "wlan0: Interface doesn't support scanning: Network is down." (don't remember the command I typed in to get that...)
_________________________________

I am running with KDE 4.0 and am not sure what I'm doing wrong. Please let me know if I need to provide more information. I'm not even sure if it's Intel or Broadcom that I need to focus on. I would be SO happy if anyone could help me get my wireless working with OpenSUSE 11.0.

THANK YOU!!
-Eve

[lwfinger]

Your wired interface is the Intel one - the wireless is a Broadcom BCM4311,
which works well - I'm using one now.

First, what does the output of 'dmesg | grep b43' show? If it shows missing
firmware, go to the stickies and see how to install the firmware.

If the firmware has been loaded, then post the output of 'sudo /usr/sbin/iwlist
wlan0 scan'.

Larry

[damnpixie]

Hey Larry,

Thank you for your help. I typed in the first command and DID get a response that my Broadcom 4311 firmware was "not found or lead failed." I was given a web address for the firmware fix (but wasn't sure which one to download). The address was b43 - Linux Wireless.

I wanted to follow your instructions on the broadcom fix first so I followed your direction in the sticky, but the very first command's response was "git: command not found." I am sure that I didn't mistype, as I copied and pasted.

What do you think I should do next?

Larry, I really appreciate your help.
-Eve

[lwfinger]

****pixie wrote:
> Hey Larry,
>
> Thank you for your help. I typed in the first command and DID get a
> response that my Broadcom 4311 firmware was "not found or lead failed."
> I was given a web address for the firmware fix (but wasn't sure which
> one to download). The address was 'b43 - Linux Wireless'
> (http://linuxwireless.org/en/users/Dr...devicefirmware).
>
> I wanted to follow your instructions on the broadcom fix first so I
> followed your direction in the sticky, but the very first command's
> response was "git: command not found." I am sure that I didn't mistype,
> as I copied and pasted.

That means you don't have the git package installed, but you shouldn't need it.

> What do you think I should do next?

Do you have Internet access in Linux? If so, then enter the command

sudo /usr/sbin/install_bcm43xx_firmware

If you don't have Internet access in Linux, then one of the stickies has the
instructions on downloading the firmware files in some other OS, sneaker netting
them to Linux, and then extracting the firmware. This process does not require
compiling any programs.

Larry


That will

[pdc_2]

sounds like you need to install git:

"git
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals.
This package itself only provides the README of git but with the packages it requires, it brings you a complete Git environment including GTK and email interfaces and tools for importing source code repositories from other revision control systems such as subversion, CVS, and GNU arch."

It would seem to be in the main update repository: do you know how to download such things?

on my system; if I open a terminal, and type in man git I get a version of the above: what I has pasted above comes from opening YaST; and in the "available" window, typing git

[damnpixie]

Hey there,

Thanks so much for helping me. I took Larry's advice and found the part of the sticky that has instructions for installing the firmware through another method. I typed in:

"
1.tar xjf broadcom-wl-4.150.10.5.tar.bz2
2.sudo mkdir -p /lib/firmware
3.sudo b43-fwcutter -w /lib/firmware \ broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o"

And the response was "Cannot open input file broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o"

So I followed pdc_2's advice and installed git in order to follow the first set of instructions. Everything was going well until I typed in "./ssb-sprom -i sprom.old -P." The results were "bash: ./ssb-sprom: no such file or directory." So I was unable to get the results I needed.

Am I doing something wrong?

THANKS!!
-Eve

[lwfinger]

****pixie wrote:
> Hey there,
>
> Thanks so much for helping me. I took Larry's advice and found the part
> of the sticky that has instructions for installing the firmware through
> another method. I typed in:
>
> "
> 1.tar xjf broadcom-wl-4.150.10.5.tar.bz2
> 2.sudo mkdir -p /lib/firmware
> 3.sudo b43-fwcutter -w /lib/firmware \
> broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o"
>
> And the response was "Cannot open input file
> broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o"

Your command looks correct except for the final " in the file name. You need to
get rid of that and rerun that single command.

Larry

[damnpixie]

Hey Larry,

I didn't put the " (quotation mark) in the command line when I input the commands; I just put it in the post because I have some kind of anal retentive punctuation thing going on. Sorry for the misunderstanding.

-Eve

[lwfinger]

****pixie wrote:
> Hey Larry,
>
> I didn't put the " (quotation mark) in the command line when I input
> the commands; I just put it in the post because I have some kind of anal
> retentive punctuation thing going on. Sorry for the misunderstanding.

Find the file that the command calls for. In addition, check its permissions
(use 'ls -l'). Report back what you find.

Larry

[damnpixie]

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

-rw-r--r-- 1 evetracy root 3888794 2008-12-03 16:44 broadcom-wl-4.150.10.5.tar.tar

-rw-r--r-- 1 root root 258 2008-12-03 17:13 sprom.old

-rw-r--r-- 1 evetracy root 652766 2008-11-29 19:57 wl_apsta-3.130.20.0

Did I do this right? FYI, I think I did try an earlier Broadcom fix before coming to the forums. Thank you for your help.

-Eve