BCM4312 Opensuse 11.1

English Network/Internet
1

Hey guys,

I seem to be having problems with my new latop with the wireless. I went thruogh the sticky and got as much info as possible. I also tried some of the things people were doing with their broadcom wireless devices but I have been unsuccesful. Below are the results from the command prompts.

05:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)

05:00.0 0280: 14e4:4315 (rev 01)

‘dmesg | less’ - Im guessing this is where my problem is I could find my wireless card and I have doubled checked so i put up anything that looked like it might have to do with my networking(looks like the ethernet port obviously but this is the best i found)

eth0: Tigon3 [partno(BCM95906) rev c002 PHY(5906)] (PCI Express) 10/100Base-TX Ethernet 00:1e:68:f0:95:64
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[0] TSOcap[0]
eth0: dma_rwctrl[76180000] dma_mask[64-bit]

ADDRCONF(NETDEV_UP): eth0: link is not ready
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.

eth0: no IPv6 routers present
[drm:i915_getparam] ERROR Unknown parameter 5

/usr/sbin/iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

sudo /usr/sbin/iwlist scan

lo Interface doesn’t support scanning.

eth0 Interface doesn’t support scanning.

2

ucfandrew wrote:
>
> 05:00.0 0280: 14e4:4315 (rev 01)

The 4315 device is not supported by the open-source b43 driver. You
need to use ndiswrapper with the Windows driver, or the Broadcom wl
hybrid driver. I think the latter is available through the packman repo.

Larry

3

If i revert to an older OpenSUSE version will it work, if not.

Can you please explain in more detail how to fix this.

Thanks,
Andrew

4

ucfandrew wrote:
> If i revert to an older OpenSUSE version will it work, if not.
>
> Can you please explain in more detail how to fix this.

An older/newer version will not help. The problem is that Broadcom
gives the open-source community zero help. The only reason that b43
exists at all is because a group of dedicated people
reverse-engineered one of the binary-only drivers that Broadcom wrote
for an AP that used Linux on a MIPS platform. The RE process consists
of decompiling the MIPS binary into C code, then writing a
“specification” for the device. It is more a prescription for
operating the device than a real spec; however, the code writers have
taken this prescription and written code that works for some Broadcom
devices. Your device has a new kind of PHY that is coded differently
than all others. The RE process is part way done, but we do not have a
driver yet. As a result, you need to use one of the two methods that I
mentioned in my previous post. Implementation of each of them is
extensively covered in many places, and I will not repeat that here.
As we used to say in academia, that is left as an exercise for the
student.

Larry

5

Hi,

I solved a similar problem with my bcm4318. Since bcm4312 is also supported by the exact same firmware provided by b43-linux wireless, I’m confident my instructions will help you:

wget http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
tar xjf broadcom-wl-4.80.53.0.tar.bz2
cd broadcom-wl-4.80.53.0/kmod/
sudo b43-fwcutter -w “/lib/firmware” wl_apsta.o

Now, restart and let me know if it works. This is the older version. I have found out, the older version works while the new version make the wireless behave erractic.

Andres

6

His model of BCM4312 with a PCI ID of 0x4315 is absolutely NOT
supported by the b43 driver. Using any version of firmware will not help.

There are 2 different 4312’s.

Larry

7

You can find the answer here. That information was helpful for me. I have BCM4312 card on HP dv4t C2D T5800, openSUSE 11.1 32-bit.

8

hi onestart; welcome to the opensuse forums;

would you care though to post to the forum the results,

from your computer, of

/sbin/lspci

or

/usr/bin/lsusb

depending on what type of card you have

as lwfinger says in post#6

His model of BCM4312 with a PCI ID of 0x4315 is absolutely NOT
supported by the b43 driver. Using any version of firmware will not help.

There are 2 different 4312’s.

9

Required Drivers

10

I have same wifi chips,I’ve got it work. Are u using default kernel? Just do this with super user mode in console,type su & enter yr password,then zypper in broadcom-wl broadcom-wl-kmp-default. After installation,just reboot,switch on yr wifi button,no more config needed. :wink:

11

hi to marcoslai and dmitry_serpokryl (and onestart);

I posted earlier what lwfinger said

There are 2 different 4312’s.

His model of BCM4312 with a PCI ID of 0x4315 is absolutely NOT supported by the b43 driver. Using any version of firmware will not help.

I am really curious: do you accept that statement as true?

12

They have to, because at the moment it is true.

If the device has the PCI-ID

14e4:4315

you have to use the proprietary drivers from broadcom (available from packman as stated before) or ndiswrapper and windows drivers.

13

Akoellh wrote:
> They have to, because at the moment it is true.
>
> If the device has the PCI-ID
>
> 14e4:4315
>
> you have to use the proprietary drivers from broadcom (available from
> packman as stated before) or ndiswrapper and windows drivers.

If you need further proof, look at the output from my system:

04:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11a/b/g
[14e4:4312] (rev 01)