Broadcom 4352 wireless [14e4:43b1], anyone tested?

Hello.
Have anyone tested if Broadcom’s 4352 is working on Leap?
I haven’t installed Leap yet and wondering if it just install, and maybe connect with ethernet to install updates and then it working. On oS 13.2 I had to update with ethernet and then wifi worked as supposed.

linux-zsya:~ # uname -a
Linux linux-zsya.site 3.16.7-24-desktop #1 SMP PREEMPT Mon Aug 3 14:37:06 UTC 2015 (ec183cc) x86_64 x86_64 x86_64 GNU/Linux
linux-zsya:~ # lspci -knn | grep Net -A2
03:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03)
        Subsystem: AzureWave Device [1a3b:2123]
        Kernel driver in use: wl

Working very well lol!

**linux-7jgs:~ #** uname -a
Linux linux-7jgs 4.1.12-1-default #1 SMP PREEMPT Thu Oct 29 06:43:42 UTC 2015 (e24bad1) x86_64 x86_64 x86_64 GNU/Linux
**linux-7jgs:~ #** lspci -knn | grep Net -A2
03:00.0 **Net**work controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless **Net**work Adapter [14e4:43b1] (rev 03)
        Subsystem: AzureWave Device [1a3b:2123]
        Kernel driver in use: wl

quinness, how did you do? I mean, I just installed Leap 42.1 and the wireless is not working. I also have a Broadcom 4352. Some post talk about my computer in particular (Dell XPS 13) saying that certain combination enables the Network Device but didn’t work for me.

Certainly, that’s the problem. The network device is not enabled I don’t know if this is a problem of drivers or the solution is doing another thing.

Thanks in advance for any suggestion.

Start by showing us the device chipset and driver loaded

lspci -knn | grep Net -A2

or

lspci -knn | grep '\02' -A2

Wireless device node present?

ifconfig

Wireless device soft-blocked or hard-blocked?

rfkill list
lspci -knn | grep Net -A2
02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03)
        Subsystem: Dell Device [1028:0019]
        Kernel driver in use_ bcma-pci-bridge

Wireless device node present?

ifconfig
lo      Link encap:Local Loopback
        inet addr:127.0.0.1 Mask:255.0.0.0
        inet6 addr: ::1/128 Scope:Host
        UP LOOPBACK RUNNING MTU:65536 Metric:1
        RX packets:456 errors: 0 dropped:0 overruns:0 frame:0
        TX [FONT=monospace]packets:456 errors: 0 dropped:0 overruns:0 frame:0
        collision: 0 txqueulen:0
        RX bytes:34048 (33.2Kb) TX bytes:34048 (33.2Kb)

Wireless device soft-blocked or hard-blocked?

rfkill list
If 'rfkill' is not a typo you can...

[/FONT]
My computer did not recognize this command.

Okay, so a supporting driver is loaded.

ifconfig
lo      Link encap:Local Loopback
        inet addr:127.0.0.1 Mask:255.0.0.0
        inet6 addr: ::1/128 Scope:Host
        UP LOOPBACK RUNNING MTU:65536 Metric:1
        RX packets:456 errors: 0 dropped:0 overruns:0 frame:0
        TX [FONT=monospace]packets:456 errors: 0 dropped:0 overruns:0 frame:0
        collision: 0 txqueulen:0
        RX bytes:34048 (33.2Kb) TX bytes:34048 (33.2Kb)

It’s likely that the wireless device is simply disabled eg via switch or key combo. The following command (with -a switch) will report all available network device nodes.

ifconfig -a
rfkill list
If 'rfkill' is not a typo you can...

[/FONT]

My computer did not recognize this command.

You need to install the ‘rfkill’ package first. If you have wired internet connectivity available do

zypper in rfkill

I’m assuming that you’ll need to enable the wireless device first.

Yes, that’s seem to be the problem. The key combo which is intented to enable wireless device is Fn+PrtScr (http://www.businessnewsdaily.com/images/i/000/007/959/i02/Photo3.jpg?1422635095 next button to F12) But it enable/disable the bluetooth. That’s my problem, and I don’t know if this happens because of some driver of other thing.

This model have no wired option.

I’ve seen online references that suggest that the BCM4352 wireless may be supported by the closed source wl driver

https://wiki.archlinux.org/index.php/Dell_XPS_13_(2015)#WiFi

So, if you don’t get any joy with the current bcma driver (which does claim to support the 14e4:43b1 chipset), then that might be worth a shot too. Again, assuming working wired internet connectivity, subscribe to the packman repo and do

zypper broadcom-wl

That should install that and the applicable broadcom kernel package.

Okay, so you can install the package by downloading via another machine with internet access first, save to a USB memory stick, and transfer to this machine.

zypper in /path/to/package

Well, Dell XPS13 has no wired internet connectivity. I am trying to install rfkill. In a while I will post again (If I can install that without internet…)

Do you still have Windows installed? Can you enable the wireless there?

Now that I’ve had time to research further, I think you’re impacted by the same issue as reported in this thread
https://forums.opensuse.org/showthread.php/509327-Wifi-Fn-Key-on-Dell-Laptop-not-working
and associated bug report
https://bugzilla.opensuse.org/show_bug.cgi?id=942876

Yes, it’s dual boot, with W10 works perfect.

I will read such post. Also, I will try to install the package using a memory stick. I’ll come back in a while.

The OP found a workaround was to use a live Ubuntu distro to enable the wireless (since the wireless key combo worked there). Refer post #11 of that thread.

Make sure that the Windows wireless driver is configured to leave the card enabled at shutdown. I seem to remember encountering similar problematic behaviour with Windows and an HP laptop a few years back.

That’s a good point. But I don’t know how to verify that. How can I do that?

Check the networking settings, and consider disabling power management there eg

http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/windows-7-shuts-off-my-network-adapter-when-i-the/caf7e50c-9d04-4610-8517-01a962a7e1ba?auth=1

Review the advice given in the following as well(section 1.3.x)

Ok, Windows had activated the option of disable the network card when it shutdown, I disabled that option but didn’t work. I’m still trying to install rfkill using a USB stick, also looking for a live version of linux to try that option.

FWIW, here’s a discussion about patching dell-wmi for new hotkey support:
http://www.spinics.net/lists/platform-driver-x86/msg08242.html
I didn’t read it closely, but it may have been implemented in newer kernels 4.5.x+. You could try upgrading to a newer kernel. For that you’ll need to subscribe to the Kernel:stable repo and upgrade from there

http://kernel.opensuse.org/packages/stable

ArchLinux thread discussing similar
https://bbs.archlinux.org/viewtopic.php?id=210137

I just installed rfkill, it shows the following


rfkill list
2: hci0: Bluetooth
         Soft blocked: no
         Hard blocked: no