|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Wireless Questions about wireless networking setup, use, and wireless specific applications |
![]() |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Hi,
I have installed SuSE 11.1 on my system and tried to activate my W-LAN device BCM4312 802.11b/g Wireless LAN Controller. However, an automatic configuration could not be done in YaSt -> Network devices -> Network settings. The UDI line of the devices is as follows: UDI: /org/freedesktop/Hal/devices/pci_14e4_4315 In /var/log/boot.msg no specification containing the term "firmware" can be found. Is there anyone who could help me in this case? Thanks in advance and best regards, Roland |
|
|||
|
rollandhommedor wrote:
> Hi, > > I have installed SuSE 11.1 on my system and tried to activate my W-LAN > device BCM4312 802.11b/g Wireless LAN Controller. However, an automatic > configuration could not be done in YaSt -> Network devices -> Network > settings. > > The UDI line of the devices is as follows: > UDI: /org/freedesktop/Hal/devices/pci_14e4_4315 As has been stated many times in this forum, driver b43 does not work with any built-in driver. |
|
|||
|
Thanks for your hint. It finally made my WLAN device work
![]() Roland |
|
|||
|
Quote:
hi this is my kernel: uname -a Linux linux-6avb 2.6.27.19-3.2-default #1 SMP 2009-02-25 15:40:44 +0100 x86_64 x86_64 x86_64 GNU/Linux in Yast, when i search for BROADCOM i have this: b43-fwcutter-011-2.49 - Tool for extracting firmware from newer Broadcom WLAN drivers /usr/bin/b43-fwcutter /usr/sbin/install_bcm43xx_firmware /usr/share/doc/packages/b43-fwcutter /usr/share/doc/packages/b43-fwcutter/README /usr/share/man/man1/b43-fwcutter.1.gz what else i'm missing? sorry for my nubbiness with suse |
|
|||
|
mrtyler81 wrote:
> > what else i'm missing? > > sorry for my nubbiness with suse You need to enable the Packman repository. Larry |
|
|||
|
go to the link below and click one click install
PackMan :: Package details for broadcom-wl hope that works |
|
|||
|
I tried to boot into the Debug kernel, but my x server will not start when doing so. The only kernel I can boot into is the default kernel and after installing broadcom-wl I still do not have the wireless device showing up for configuration. When I had Ubuntu installed, everything was much easier. this should be as easy in opensuse as Ubuntu. After all, I am in the same equipment (and opensuse is, for the most part, better, isn't it?)
|
|
|||
|
flabbergasted wrote:
> I tried to boot into the Debug kernel, but my x server will not start > when doing so. The only kernel I can boot into is the default kernel and > after installing broadcom-wl I still do not have the wireless device > showing up for configuration. When I had Ubuntu installed, everything > was much easier. this should be as easy in opensuse as Ubuntu. After > all, I am in the same equipment (and opensuse is, for the most part, > better, isn't it?) ![]() As always, the down side of using an out-of-kernel driver is that any module must match your kernel _EXACTLY_. This situation cannot be altered. It is the same in Ubuntu as in openSUSE. Look at the output of the 'lsmod' command. If you see the module 'ssb' mentioned, that is part of the reason. Larry |
![]() |
|
| Bookmarks |
| Tags |
| bcm4312 |
| Thread Tools | |
| Display Modes | |
|
|