I’ve been trying to get wireless working on a dell laptop. I’ve enabled the packman repo and supposedly installed the driver, rebooted, but no wireless networks show up
Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
Subsystem: Dell Wireless 1397 WLAN Mini-Card
Flags: bus master, fast devsel, latency 0, IRQ 4
Memory at f69fc000 (64-bit, non-prefetchable) [size=16]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number cb-b6-a1-ff-ff-d5-70-f1
Capabilities: [16c] Power Budgeting <?>
Kernel modules: ssb
Thanks Deano, I installed that, then was able to run the aforementioned command, rebooted, still haven’t got any wireless networks available though
Anything else I’m missing out on? I’m new to OpenSuse btw, so not much is obvious to me at the moment.
Can you show us more more info about your wireless hardware?
/sbin/lspci -nnk |grep Net -A2
or
/usr/sbin/hwinfo --wlan
Is wlan0 listed in the output from the following?
/sbin/ifconfig
If so, proceed to configuring via YaST >> Network Devices >> Network Settings. Under ‘Global Options’ make sure ‘User controlled with NetworkManager’ is selected.
Then set about configuring your wireless connection from the Network Manager.
and I could see and connect to wireless (yay) but I rebooted and now it’s the same again. Wireless not showing
btw, thanks for your help with this Deano, much appreciated!
On 11/20/2013 04:06 PM, deano ferrari wrote:
>
> ge0ffery_pancake;2599459 Wrote:
>> no output there either unfortunately.
> Can you try
>
> Code:
> --------------------
> modprobe b43
> --------------------
>
> then
>
> Code:
> --------------------
> ifconfig
> --------------------
One comment on the advice given here. Blockage of wireless with rfkill does not
prevent the formation of a wl** device - it only causes a failure to connect. If
the device is not created, failure to load firmware, or the blacklisting of a
driver should be suspected.
To the OP, have you ever fooled around with wl? You mentioned the Packman repo
earlier, and that makes me think you did. When you do that, its installation
process blacklists b43 (among other drivers), which leads to exactly what you
are seeing. In directory /dev/modprobe.d/, use grep to find all the files that
mention b43 or ssb, and delete all the lines that do.
One comment on the advice given here. Blockage of wireless with rfkill does not
prevent the formation of a wl** device - it only causes a failure to connect.
Not necessarily true (at least for my HP hardware). When I issue ‘rfkill block wlan’, the wlan0 device also disappears. I’ve just tested the behaviour again to verify.
To the OP, have you ever fooled around with wl? You mentioned the Packman repo
earlier, and that makes me think you did. When you do that, its installation
process blacklists b43 (among other drivers), which leads to exactly what you
are seeing. In directory /dev/modprobe.d/, use grep to find all the files that
mention b43 or ssb, and delete all the lines that do.
To the OP, have you ever fooled around with wl? You mentioned the Packman repo
earlier, and that makes me think you did. When you do that, its installation
process blacklists b43 (among other drivers), which leads to exactly what you
are seeing. In directory /dev/modprobe.d/, use grep to find all the files that
mention b43 or ssb, and delete all the lines that do.
Not /dev/modprobe.d/, but /etc/modprobe.d/ is the relevant directory to check for blacklisted modules.
