Hi Friends,
I have a Vostro 1510 with suse 11.1 installed on it.The system lists the wireless card on ‘hardware information’ but in fact it doesnt recognize it.(the card is Wireless 1395 WLAN mini card)
I read some threads but I couldn’t find a simple way because I am new to linux.
Anyone can help me and explain me how to install it in a simple language?
Thanks alot
Wireless problems are handled in the wireless subforum of the networking forum.
With your DW1395, you need to install firmware. You would see this by opening a
console and entering the command
dmesg | grep b43
If you have Internet access while running Linux, you can fix this by entering
the command
sudo /usr/sbin/install_bcm43xx_firmware
If you do not have Internet access with Linux, then go to the wireless forum,
find the sticky entitled “Welcome”, go down about 2/3 of the way, and find the
prescription for using “sneakernet” to get the necessary file.
Larry
Thanks alot Larry,
I will look for the solution in that thread.
thanks
but the ‘welcome’ thread is closed,
/sbin/lspci -v gives these results(part of it)
06:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
Subsystem: Dell Wireless 1395 WLAN Mini-Card
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at f4000000 (64-bit, non-prefetchable) [size=16]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information <?>
Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+ Count=1/1 Enable-
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSVoil-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSVoil-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSVoil-
CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [13c] Virtual Channel <?>
Capabilities: [160] Device Serial Number 22-00-3b-ff-ff-5f-72-95
Capabilities: [16c] Power Budgeting <?>
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
Subsystem: Dell Device 0273
Flags: bus master, fast devsel, latency 0, IRQ 217
I/O ports at 6000 [size=256]
Memory at f8410000 (64-bit, prefetchable) [size=4]
Memory at f8400000 (64-bit, prefetchable) [size=64]
[virtual] Expansion ROM at f8420000 [disabled] [size=64]
Capabilities: [40] Power Management version 3
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Count=1/2 Enable+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable- Mask- TabSize=2
Capabilities: [d0] Vital Product Data <?>
Capabilities: [100] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSVoil-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSVoil-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSVoil-
CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout+ NonFatalErr+
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140] Virtual Channel <?>
Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
Kernel driver in use: r8169
Kernel modules: r8169
08:05.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02) (prog-if 10 [OHCI])
Subsystem: Dell Device 0273
Flags: bus master, medium devsel, latency 64, IRQ 22
Memory at f8000000 (32-bit, non-prefetchable) [size=4]
Memory at f8002000 (32-bit, non-prefetchable) [size=2]
Capabilities: [60] Power Management version 2
Kernel driver in use: ohci1394
Kernel modules: ohci1394[/size][/size][/size][/size][/size][/size][/size]
sa3lan wrote:
> but the ‘welcome’ thread is closed,
Yes, closed just means you cannot write to it. It is still readable!!!
The part I wanted you to see was
Using any method that you have to access the Internet, download this
http://tinyurl.com/3ammcm
Then copy it into your home directory. Once you have it there, you should enter
the following:
tar xjf broadcom-wl-4.150.10.5.tar.bz2
sudo mkdir -p /lib/firmware
sudo b43-fwcutter -w /lib/firmware \ broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o
These three commands will skip the download step and extract the firmware in the
same way that the /usr/sbin/install_bcm43xx_firmware would have.
Larry
after running the 3rd command I get this error:
“Cannot open input file broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o”
what can be the reason? (the file exists in that location but it cant be opened)
I tried those things in “welcome” too but it didnt work:
thanks again
PackMan :: Informationen zum Paket b43-firmware
But post output of
/sbin/lspci -nn |grep -i net
first.
the output is :
06:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
07:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 02)
06:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g **14e4:4315**] (rev 01)
As suspected, forget about b43 and install proprietary “broadcom-wl” driver (also available from packman-site/repo).
Please tell me how (with details and step-by-step if possible)
I tried those packages but they were unsuccessful,even those RPMs didnt work 
Thanks
Tell me which packages exactly you tried to install and cite error messages exactly how they appeared.
As I have no information on your installation (i586 or x86_64, kernel version etc.) I can’t tell you which packages you would need, even if I wanted to.
Hi,
The version of Kernel is -> 2.6.27.7-9-pae #1 SMP 2008-12-04 18:10:04 +0100 i686 i686 i386 GNU/Linux
As mentioned in a previous post during installing “broadcom-wl-4.150.10.5(2).tar.bz2” I got this error message :"“Cannot open input file broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o”"
During installing " broadcom-wl-kmp-debug-5.10.79.10_2.6.27.19_3.2-5.pm.8.i586.rpm" I get this error message :“nothing provides kernel(pae:mm) = 24aae03104bbf9ba needed by broadcom-wl-kmp-pae-5.10.79.10_2.6.27.19_3.2-5.pm.8.i586” so sth missing in/by kernel that should be added(compiled) but I couldnt do that.
I noticed in Yast->System->Kernel Settings there is a window for PCI ID Setup which you can add things there and the wireless card’s name is also in the list,but when you want to “add” it on the list it requires a “Driver” and a “SysFS Directory”…Is it related to installation of hardwares as wireless etc? if the answer is yes,how does it work?
Regards
sa3lan wrote:
> Hi,
> The version of Kernel is -> 2.6.27.7-9-pae #1 SMP 2008-12-04 18:10:04
> +0100 i686 i686 i386 GNU/Linux
> As mentioned in a previous post during installing
> “broadcom-wl-4.150.10.5(2).tar.bz2” I got this error message :"“Cannot
> open input file broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o”"
> During installing "
You don’t have the file in the right place. Please say exactly what you did,
your EXACT input and the error messages.
What I did Exactly:
I logged in by root and coppied broadcom-wl-4.150.10.5.tar.bz2 to /home/user/
then opened a Konsole terminal and ran these commands:
cd /home/user/
tar xjf broadcom-wl-4.150.10.5.tar.bz2 O.K
sudo mkdir -p /lib/firmware O.K
sudo b43-fwcutter -w /lib/firmware \ broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o
Error “Cannot open input file broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o”
Regards
sa3lan wrote:
> What I did Exactly:
> I logged in by root and coppied broadcom-wl-4.150.10.5.tar.bz2 to
> /home/user/
> then opened a Konsole terminal and ran these commands:
> cd /home/user/
> tar xjf broadcom-wl-4.150.10.5.tar.bz2 O.K
> sudo mkdir -p /lib/firmware O.K
> sudo b43-fwcutter -w /lib/firmware
> broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o
> Error “Cannot open input file
> broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o”
Those commands should have been OK. To check, open a terminal and enter the
following:
cd /home/user
ls -l broadcom-wl-4.150.10.5/driver/
Post the results.
Larry
No, the firmware is useless for this device it does not work with b43.
The Kernel is too old for those packages from packman, connect the machine via cable to the internet and run a complete online update.
After that reboot machine, kernel will be 2.6.27.19-3.2.
Add packman repository via YaST and install the packages.
Don not install the kmp-debug, only the kmp-pae!
Akoellh wrote:
> No, the firmware is useless for this device it does not work with
> b43.
Funny, but my DW1395, which is the OLDER version of the BCM4312, works
perfectly well with b43. The PHY is a 4311.
> The Kernel is too old for those packages from packman, connect the
> machine via cable to the internet and run a complete online update.
>
> After that reboot machine, kernel will be 2.6.27.19-3.2.
>
> Add packman repository via YaST and install the packages.
>
> Don not install the kmp-debug, only the kmp-pae!
To the OP: Please ignore the rest of this.
Look at the PCI-ID, its 14e4:4315, which is not supported by b43.
Akoellh wrote:
> Look at the PCI-ID, its 14e4:4315, which is not supported by b43.
>
> ‘Gmane – Mail To News And Back Again’
> (http://article.gmane.org/gmane.linux.kernel.wireless.general/29356)
Oh no. Even Dell is subscribing to the junk about reusing a name/number for two
very different devices.
Yes, you do need the Broadcom hybrid driver.
Larry
thanks lwfinger and Akoellh,
Akoellh wrote:
The Kernel is too old for those packages from packman, connect the machine via cable to the internet and run a complete online update.
the problem is that I can’t connect to internet with that laptop,I even couldnt install its USB modem(Conexant RD02-D400)(it seems it is installed(I can see its setting in yast->Network Devices->Modem),but when I create a connection with KPPP,it says there is no modem installed.
you see,my problem is not just that wireless:)
Isn’t there another way for updating kernel?
Regards