Page 1 of 1

IPFire 2.19 Core 105 Wireless Problem

Posted: October 12th, 2016, 3:22 pm
by stlawr
I recently updated my firewalls to v2.19 Core 105 from Core 103. After the upgrade, I had a problem with 4 of the firewalls. All are HP Mini 1000 laptops with a Red-Green-Blue configuration. IPFire recognizes the BCM43 wireless chipset during boot, but won't start HostAPD because it sees the wireless is turned off. The button to turn on wireless does nothing. When I boot the laptops, the wireless switch shows that it is on, but as soon as the IPFire kernel starts loading, the wlan turns off. Has anyone else seen this or have a suggestion?

I have already wiped one of the HP Minis and reloaded Core 103, but I'm still having the same problem.

Re: IPFire 2.19 Core 105 Wireless Problem

Posted: October 12th, 2016, 3:37 pm
by Arne.F
There should no changes on the wireless drivers in core104 and 105.
The kernel was updated from 3.14.65 to 3.14.79 but backports is still the same except
three patches
http://git.ipfire.org/?p=ipfire-2.x.git ... df100915c3

Nothing touch bcm43 drivers...

Re: IPFire 2.19 Core 105 Wireless Problem

Posted: October 12th, 2016, 3:41 pm
by stlawr
I don't think it did anything to the drivers. It seems to have turned the WLAN off on the computer itself. Like I said, this only happened to the 4 HP Mini 1000s in my environment, all the other firewalls were fine... The boot process states that RFKill is preventing HostAPD from loading.

Re: IPFire 2.19 Core 105 Wireless Problem

Posted: October 29th, 2016, 10:54 am
by AndyWas
I have exactly the same problem. I have just installed IPFire 2.19 Core 105 on a (very) old Acer TravelMate 4001LCi. I replaced the internal Intel Mini-PCI wireless card with a Atheros AR5212/5213/2414 based card as the original Intel one doesn't support AP mode. Although I can see the Atheros interface and assign it to blue0, when the laptop boots up it is unable to start blue0 due as "Operation not possible due to RF-kill". As with the OP the hardware wireless switch appears to be permanently "off" and doesn't respond or change state when pressed.

This same wireless card worked OK, including running hostapd in AP mode, when Fedora 24 was installed. If I plug in a RT5572 wireless adapter (TP-Link TL_WDN3200) I can use that as blue0 OK, including in hostapd. Obviously the hardware wireless switch doesn't control that.

I have seen some workarounds and fixes using the rfkill command, but IPFire doesn't seem to have a rfkill package in PakFire...

Regards,
Andrew

Re: IPFire 2.19 Core 105 Wireless Problem

Posted: February 19th, 2017, 7:31 pm
by trymes
We have bumped into this again, and I'm wondering if anyone has made any progress. We're taking these older devices out of service, but I'd like an answer in case it rears its head in the future on different hardware.

Having the RF-Kill utility would be helpful here because it could point to either the software switch or the hardware. I have found a few links that look promising, and I will see if just going into the BIOS and re-enabling will help, though I'm not certain how IPFire would have inadvertently changed BIOS settings?

Another thing I noticed is that, if I go into setup, remove the network card assignments, and then re-add them, there are two "ssd: b43" entries, with identical MAC addresses.

Re: IPFire 2.19 Core 105 Wireless Problem

Posted: February 19th, 2017, 7:51 pm
by trymes
I don't know why I hadn't seen this before, but I just saw this in the kernel log:

Code: Select all

Feb 19 11:47:02 myrouter kernel: <12>udevd[1380]: renamed network interface wlan0 to blue0
Feb 19 11:47:02 myrouter acpid: starting up with netlink and the input layer
Feb 19 11:47:02 myrouter acpid: 1 rule loaded
Feb 19 11:47:02 myrouter acpid: waiting for events: event logging is off
Feb 19 11:47:03 myrouter kernel: cfg80211: Regulatory domain changed to country: DE
Feb 19 11:47:03 myrouter kernel: cfg80211:  DFS Master region: ETSI
Feb 19 11:47:03 myrouter kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (5150000 KHz - 5250000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (5250000 KHz - 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (5470000 KHz - 5725000 KHz @ 160000 KHz), (N/A, 2698 mBm), (0 s)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
Feb 19 11:47:03 myrouter kernel: cfg80211: Invalid regulatory domain detected:
Feb 19 11:47:03 myrouter kernel: cfg80211: Regulatory domain: 00
Feb 19 11:47:03 myrouter kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Feb 19 11:47:03 myrouter kernel: cfg80211: World regulatory domain updated:
Feb 19 11:47:03 myrouter kernel: cfg80211:  DFS Master region: unset
Feb 19 11:47:03 myrouter kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Feb 19 11:47:03 myrouter kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Feb 19 11:47:04 myrouter kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Feb 19 11:47:04 myrouter kernel: cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Feb 19 11:47:04 myrouter kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Feb 19 11:47:04 myrouter kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Feb 19 11:47:04 myrouter kernel: cfg80211: Regulatory domain changed to country: US
Feb 19 11:47:04 myrouter kernel: cfg80211:  DFS Master region: FCC
Feb 19 11:47:04 myrouter kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Feb 19 11:47:04 myrouter kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Feb 19 11:47:04 myrouter kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A)
Feb 19 11:47:04 myrouter kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)
Feb 19 11:47:04 myrouter kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
Feb 19 11:47:04 myrouter kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
Feb 19 11:47:04 myrouter kernel: ------------[ cut here ]------------
Feb 19 11:47:04 myrouter kernel: WARNING: CPU: 0 PID: 1657 at /usr/src/backports-4.2.6-1/net/mac80211/driver-ops.h:12 ieee80211_bss_info_change_notify+0x1d5/0x1e0 [mac80211]()
Feb 19 11:47:04 myrouter kernel: blue0:  Failed check-sdata-in-driver check, flags: 0x0
Feb 19 11:47:04 myrouter kernel: Modules linked in: xt_ipp2p(O) compat_xtables(O) xt_mac xt_nat xt_mark xt_policy xt_TCPMSS nf_nat_irc nf_conntrack_irc nf_nat_pptp nf_nat_proto_
gre nf_conntrack_pptp nf_conntrack_proto_gre xt_CT xt_helper nf_nat_h323 nf_conntrack_h323 xt_conntrack xt_comment ipt_REJECT xt_LOG xt_limit iptable_raw iptable_mangle iptabl
e_nat nf_nat_ipv4 nf_nat iptable_filter arc4 sch_fq_codel b43(O) bcma(O) mac80211(O) cfg80211(O) iTCO_wdt iTCO_vendor_support hp_wmi sparse_keymap rfkill snd_hda_codec_idt snd
_hda_codec_generic uvcvideo(O) videobuf2_vmalloc(O) coretemp videobuf2_memops(O) videobuf2_core(O) microcode asix(O) lpc_ich mfd_core snd_hda_intel v4l2_common(O) usbnet(O) pc
spkr ssb(O) videodev(O) mii cdc_acm psmouse media(O) serio_raw snd_hda_codec i2c_i801 i2c_core snd_hwdep mmc_core snd_pcm compat(O) snd_timer pcmcia snd pcmcia_core soundcore 
sky2 wmi acpi_cpufreq lp parport_pc parport video ata_generic pata_acpi
Feb 19 11:47:04 myrouter kernel: CPU: 0 PID: 1657 Comm: iwconfig Tainted: G           O 3.14.79-ipfire-pae #1
Feb 19 11:47:04 myrouter kernel: Hardware name: Hewlett-Packard HP Mini/361A, BIOS 361A0 Ver. F.16 04/30/2010
Feb 19 11:47:04 myrouter kernel:  00000286 00000286 f6603c18 c09f9d71 f6603c5c 00000000 f6603c4c c045d112
Feb 19 11:47:04 myrouter kernel:  f8ab7504 f6603c78 00000679 f8ab74cc 0000000c f8a4fd45 0000000c f8a4fd45
Feb 19 11:47:04 myrouter kernel:  f70fb7b4 f70fb020 00040000 f6603c64 c045d163 00000009 f6603c5c f8ab7504
Feb 19 11:47:04 myrouter kernel: Call Trace:
Feb 19 11:47:04 myrouter kernel:  [<c09f9d71>] dump_stack+0x58/0x72
Feb 19 11:47:04 myrouter kernel:  [<c045d112>] warn_slowpath_common+0x82/0xa0
Feb 19 11:47:04 myrouter kernel:  [<f8ab7504>] ? __param_str_minstrel_vht_only+0x174/0x742a [mac80211]
Feb 19 11:47:04 myrouter kernel:  [<f8ab74cc>] ? __param_str_minstrel_vht_only+0x13c/0x742a [mac80211]
Feb 19 11:47:04 myrouter kernel:  [<f8a4fd45>] ? ieee80211_bss_info_change_notify+0x1d5/0x1e0 [mac80211]
Feb 19 11:47:04 myrouter kernel:  [<f8a4fd45>] ? ieee80211_bss_info_change_notify+0x1d5/0x1e0 [mac80211]
Feb 19 11:47:04 myrouter kernel:  [<c045d163>] warn_slowpath_fmt+0x33/0x40
Feb 19 11:47:04 myrouter kernel:  [<f8ab7504>] ? __param_str_minstrel_vht_only+0x174/0x742a [mac80211]
Feb 19 11:47:04 myrouter kernel:  [<f8a4fd45>] ieee80211_bss_info_change_notify+0x1d5/0x1e0 [mac80211]
Feb 19 11:47:04 myrouter kernel:  [<f8ab74cc>] ? __param_str_minstrel_vht_only+0x13c/0x742a [mac80211]
Feb 19 11:47:04 myrouter kernel:  [<f8ab7504>] ? __param_str_minstrel_vht_only+0x174/0x742a [mac80211]
Feb 19 11:47:04 myrouter kernel:  [<f8a64e54>] ieee80211_recalc_txpower+0x34/0x40 [mac80211]
Feb 19 11:47:04 myrouter kernel:  [<f8a6c368>] ieee80211_set_tx_power+0x48/0x1d0 [mac80211]
Feb 19 11:47:04 myrouter kernel:  [<f87db3d6>] ? rfkill_set_sw_state+0x66/0xc0 [rfkill]
Feb 19 11:47:04 myrouter kernel:  [<f8ab2f80>] ? tkip_sbox+0x2c0/0x2c0 [mac80211]
Feb 19 11:47:04 myrouter kernel:  [<f8911e42>] cfg80211_wext_siwtxpower+0x92/0x1d0 [cfg80211]
Feb 19 11:47:04 myrouter kernel:  [<f8911db0>] ? cfg80211_wext_siwpower+0x1d0/0x1d0 [cfg80211]
Feb 19 11:47:04 myrouter kernel:  [<c09f14ca>] ioctl_standard_call+0x6a/0x690
Feb 19 11:47:04 myrouter kernel:  [<c08e346d>] ? dev_get_by_name_rcu+0x5d/0x80
Feb 19 11:47:04 myrouter kernel:  [<c09f1e35>] wext_handle_ioctl+0x255/0x2d0
Feb 19 11:47:04 myrouter kernel:  [<f8911db0>] ? cfg80211_wext_siwpower+0x1d0/0x1d0 [cfg80211]
Feb 19 11:47:04 myrouter kernel:  [<c08fc42e>] dev_ioctl+0x3fe/0xa50
Feb 19 11:47:04 myrouter kernel:  [<c08cbf05>] sock_ioctl+0x135/0x250
Feb 19 11:47:04 myrouter kernel:  [<c08cbdd0>] ? sock_fasync+0x80/0x80
Feb 19 11:47:04 myrouter kernel:  [<c057f286>] do_vfs_ioctl+0x436/0x720
Feb 19 11:47:04 myrouter kernel:  [<c057f5d0>] SyS_ioctl+0x60/0x90
Feb 19 11:47:04 myrouter kernel:  [<c09ff6b4>] syscall_call+0x7/0x7
Feb 19 11:47:04 myrouter kernel:  [<c09f007b>] ? edsa_rcv+0x15b/0x240
Feb 19 11:47:04 myrouter kernel:  [<c044f440>] ? vmalloc_sync_all+0x1f0/0x1f0
Feb 19 11:47:04 myrouter kernel:  [<c09ff6da>] ? restore_all_pax+0xc/0xc
Feb 19 11:47:04 myrouter kernel:  [<c09f007b>] ? edsa_rcv+0x15b/0x240
Feb 19 11:47:04 myrouter kernel: ---[ end trace 5c79b046b8eec2fd ]---
Feb 19 11:47:07 myrouter codel: Codel AQM has been enabled on 'blue0'.

Re: IPFire 2.19 Core 105 Wireless Problem

Posted: December 14th, 2017, 7:26 pm
by trymes
This is driving me nuts. Most of the units have been migrated out of production, but it bothers me that the Broadcom wireless still doesn't work with IPFire when it used to work perfectly. Installing Arne_F's experimental 4.14.2 kernel on this machine did not help any.

Here is a link to a forum post at archlinux forums that looks to be identical:

https://bbs.archlinux.org/viewtopic.php?id=173808

The second to last post references this post, which I can't try on IPFire, because there is no rfkill utility installed.

https://bbs.archlinux.org/viewtopic.php ... 0#p1324810

This isn't a humongous deal for me, but I'm certain that others have run into it, and it really ought to work, especially when it used to.

Tom

Re: IPFire 2.19 Core 105 Wireless Problem

Posted: December 17th, 2019, 6:15 pm
by trymes
UPDATE: I was able to resolve this (years later) by downloading an RPM of a 32-bit (this is a 32-bit machine) rfkill binary for another linux distro. I then used 7-zip to extract the RPM file to a CPIO file, and then used 7-zip to extract the CPIO file. I then copied the files over to the system using WinSCP, moved them into the /usr/bin and /usr/sbin directories, and issued 'chmod a+x /usr/bin/rfkill' and 'chmod a+x /usr/sbin/rfkill' commands. From there, rfkill works and I was able to unblock the wireless card, and now it works as it should have all along.

I think that this has something to do with the introduction of the hp_wmi driver and perhaps other WMI bits?

Either way, it now works, which makes me happy.

Tom