according to opensuse startup document Available visible wireless networks are listed in the GNOME NetworkManager applet menu under Wireless Networks. The signal strength of each network is also shown in the menu. Encrypted wireless networks are marked with a shield icon.
i can’t find any entry in the applet icon that express wireless connection
i can only find wired connection
The revision level read by ssb will not make any difference as ssb/b43 work only
on devices with an SSB interconnect on the wireless chip. The BCM4313 does not
have this hardware. The driver you need is brcm80211, which is found in
compat-wireless, or in the 2.6.37 kernel used in 11.4…
On 12/08/2010 08:06 PM, mostafaxxx wrote:
>
> does any one can help me getting the driver from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6.git
>
> i have no idea about git
> and i really don’t think that “git” is a sort of a protocol???
The instructions for building your own kernel are in several places on the Forums.
Another option is that you could install openSUSE 11.4 M4. It is beta software,
but most things work for most people. It contains the 2.6.37 kernel that your
device needs. Check the most annoying bugs page to see if there are any killers
for you.
Not ignoring what has already been suggested in the previous answers, especially #2 and #5.
But if you really want to install a whole new OS or kernel or even compile your own kernel just to have one (sic!) new driver, go ahead, makes as much sense as transplanting kidney/liver/etc. because one has a bladder infection.
I suspected that the user mostafaxxx has not understood what the other solutions meant - especially the one with:
And searching for “compat-wireless” gave me Download - Linux Wireless with brcm80211 - Linux Wireless is in my opinion (being not so skilled in Linux based systems or informatics myself) not very easy to understand and presumingly not easy to follow.
This package contains firmware files for broadcom BCM4313, BCM43224, BCM43225 chipsets with open source driver “brcm80211.ko”.
The firmware files were taken from “linux-firmware” git-repository and will be copied to /lib/firmware/brcm.
(I am assuming that firmware is needed to my knowledge together with the driver itself and probably also together with a kernel module if you are not running a actual testing candidate of the kernel.)
maybe someone (with more knowledge than me) could try to explain the meant issue a bit more?
pistazienfresser - maybe someone (with more knowledge than me) could try to explain the meant issue a bit more?
I am not more qualified than any of the contributors to this post, that’s for certain, but I can offer that I had the same problem with the same chip in a very similar PC and solved the problem by following advice offered by those same contributors who are certainly very, very knowledgeable in this area. I only had to follow the very simple tip offered in Post #2 above and I was up and running in no time.
If/as I understood something in Install Broadcom Drivers from Packman and following -
the right driver packages from packman (=“wl driver”?) should work for a device with a ID “… 4727” .
But it might also be comprehensible
that a user may be at least a bit puzzled
because of all the different drivers, different names for the same driver, different software (e.g.: kernel-modules, driver and firmware just for one possibility/way) and different possibilities/ways.
I think we should be really grateful to the ones how are merging the Broadcom driver(s) with the new 2.6.37 kernel - hopefully it will be easier in the future for many Broadcom wireless devices.
On 12/12/2010 06:06 PM, pistazienfresser wrote:
>
> caprus;2264410 Wrote:
>> I am not more qualified than any of the contributors to this post,
>> that’s for certain, but I can offer that I had the same problem with the
>> same chip in a very similar PC and solved the problem by following
>> advice offered by those same contributors who are certainly very, very
>> knowledgeable in this area. I only had to follow the very simple tip
>> offered in Post #2 above and I was up and running in no time.
>
> mostafaxxx;2263251 Wrote:
>>
>> …]
>> /SBIN/LSPCI -N:
>>>
> Code:
> --------------------
> > > 03:00.0 0280: 14e4:4727 (rev 01)
> --------------------
>>>
>> …]
>
> If/as I understood something in
> ‘Install Broadcom Drivers from Packman’ (http://tinyurl.com/2c72nor)
> and following -
> the right driver packages from packman (=“wl driver”?) should work for
> a device with a ID “… 4727” .
>
> But it might also be comprehensible
> that a user may be at least a bit puzzled
> because of all the different drivers, different names for the same
> driver, different software (e.g.: kernel-modules, driver and firmware
> just for one possibility/way) and different possibilities/ways.
>
> I think we should be really grateful to the ones how are merging the
> Broadcom driver(s) with the new 2.6.37 kernel - hopefully it will be
> easier in the future for many Broadcom wireless devices.
Unfortunately, we will not be able to fix everything. The current implementation
of b43 only supports devices that use the Sonics Silicon Backplane (SSB) as an
interconnect between the various parts of the chip. The BCM4313 (14e4:4727) does
not contain this feature; however, it will be supported by the brcm80211 driver
that is in the kernel starting with 2.6.37. Once b43 supports all the 802.11n
devices, no one will have to use an out-of-kernel driver such as wl. That will
certainly be an improvement.