Live w/ red errors to set can_be_ap ('failed_when: False' was too strong) + WiFi firmware questions w/ Linux Mint (Broadcom or Realtek) #3329
Conversation
|
Looks like a crutch to me, the red warning remains yet there is a goal to avoid that kind of behavior, seem like a regression to me. |
|
Ansible sometimes makes the simplest possible action complex, it's true. However in this case, a visually strong warning (with actual concrete details not papered over, and why not in red) serve a valuable purpose — notifying people that IIAB's main purpose (setting up a WiFi learning hotspot) will fail — as a result of their WiFi chipset being incapable of AP Mode. |
|
I'll call BS, The next stanza set the variable that is recorded in iiab.ini, affecting the actions performed and the resulting reminder in iiab-hotspot-on is what is important. Nobody is looking at the long running install when 'iiab' is used but we have a general avoid the red warning motto that you wanted, stick to that motto and use the recorded value in iiab.ini as the diagnostic go to. |
|
You are free to disagree. As I'm free to disagree with you. In the end, most people (not all, for sure, but the vast majority) want a functioning WiFi learning hotspot as the central purpose of their IIAB — and as such red details highlighting the impossibility of that goal are a perfect early warning — when this is unfortunately a No Go. |
|
You will be free to debug alone if you keep that attitude up, final warning. |
|
Hello ,I have tried with usb wifi dongle.It allows me to set laptop as hotspot and iiab ssid appears.This happens exactly same when using internal chipset as hotspot.Nothing comes up if I connect to iaab wifi with either internal chip or wifi dongle .I have tried all types of phones and laptop.Looks like we may have to go the router way.Good effort all.Am sending screenshots.,
|
|
There is an option for creating a bridge or vlan on the menu but not sure if i am setting it properly. |
|
iiab-diagnostics and the url please. |
PLAY RECAP ******************************************************************************************************************************************************************************************* 127.0.0.1 : ok=97 changed=24 unreachable=0 failed=0 skipped=81 rescued=0 ignored=1 DEVICE TYPE STATE CONNECTION enp9s0 ethernet connected Wired connection 1 br0 bridge connected br0 tun0 tun connected tun0 bridge0 bridge connecting (getting IP configuration) Bridge connection 1 wlp12s0 wifi disconnected -- bridge0.0 vlan unavailable -- lo loopback unmanaged -- NAME UUID TYPE DEVICE Bridge connection 1 125c8479-c23e-4f0d-90c0-9cbe0024416b bridge bridge0 Wired connection 1 7eae1869-7276-3359-9890-c92fd208ec28 ethernet enp9s0 br0 856021bb-27a4-4cfe-bdf6-089f7e4f480a bridge br0 tun0 9ee47742-cedd-4b68-bddd-93364230f2d6 tun tun0 bridge0 slave 1 074f9ceb-448d-464c-8718-552ff6d5c4e9 vlan -- Hotspot 72fd16c4-9951-438f-be46-df0af786f507 wifi -- default via 192.168.0.1 dev enp9s0 proto dhcp metric 100 10.8.0.0/18 via 10.8.0.29 dev tun0 10.8.0.1 via 10.8.0.29 dev tun0 10.8.0.29 dev tun0 proto kernel scope link src 10.8.0.30 10.10.10.0/24 dev br0 proto kernel scope link src 10.10.10.10 169.254.0.0/16 dev tun0 scope link metric 1000 192.168.0.0/24 dev enp9s0 proto kernel scope link src 192.168.0.31 metric 100 5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 br0 15: bridge0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master bridge0 iiab-network run start: Mon 1 Aug 14:36:51 CAT 2022 iiab-network run end: Mon 1 Aug 14:39:14 CAT 2022 Please REBOOT to fully verify your network -- graphical desktops MUST reboot! |
|
I came across this feature for enabling hotspot in last 30mins and tried it without luck then tried creating a bridge .. but still no luck |
root@iiab-mint01:/home/ed01# iiab - diagnostics IIAB INSTALLATION (/usr/sbin/iiab) IS ALREADY COMPLETE -- per existence of: /etc/iiab/install-flags/iiab-complete -- nothing to do. root@iiab-mint01:/home/ed01# |
root@iiab-mint01:/home/ed01# iw list Wiphy phy0 max # scan SSIDs: 1 max scan IEs length: 0 bytes max # sched scan SSIDs: 0 max # match sets: 0 max # scan plans: 1 max scan plan interval: -1 max scan plan iterations: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP-128 (00-0f-ac:4) * CMAC (00-0f-ac:6) Available Antennas: TX 0 RX 0 Supported interface modes: * IBSS * managed Band 1: Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps (short preamble supported) * 5.5 Mbps (short preamble supported) * 11.0 Mbps (short preamble supported) * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (20.0 dBm) (no IR) * 2472 MHz [13] (20.0 dBm) (no IR) * 2484 MHz [14] (20.0 dBm) (no IR) Band 2: Bitrates (non-HT): * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 5170 MHz [34] (disabled) * 5180 MHz [36] (20.0 dBm) (no IR) * 5190 MHz [38] (20.0 dBm) (no IR) * 5200 MHz [40] (20.0 dBm) (no IR) * 5210 MHz [42] (20.0 dBm) (no IR) * 5220 MHz [44] (20.0 dBm) (no IR) * 5230 MHz [46] (20.0 dBm) (no IR) * 5240 MHz [48] (20.0 dBm) (no IR) * 5260 MHz [52] (20.0 dBm) (no IR, radar detection) * 5280 MHz [56] (20.0 dBm) (no IR, radar detection) * 5300 MHz [60] (20.0 dBm) (no IR, radar detection) * 5320 MHz [64] (20.0 dBm) (no IR, radar detection) * 5500 MHz [100] (20.0 dBm) (no IR, radar detection) * 5520 MHz [104] (20.0 dBm) (no IR, radar detection) * 5540 MHz [108] (20.0 dBm) (no IR, radar detection) * 5560 MHz [112] (20.0 dBm) (no IR, radar detection) * 5580 MHz [116] (20.0 dBm) (no IR, radar detection) * 5600 MHz [120] (20.0 dBm) (no IR, radar detection) * 5620 MHz [124] (20.0 dBm) (no IR, radar detection) * 5640 MHz [128] (20.0 dBm) (no IR, radar detection) * 5660 MHz [132] (20.0 dBm) (no IR, radar detection) * 5680 MHz [136] (20.0 dBm) (no IR, radar detection) * 5700 MHz [140] (20.0 dBm) (no IR, radar detection) * 5745 MHz [149] (20.0 dBm) (no IR) * 5765 MHz [153] (20.0 dBm) (no IR) * 5785 MHz [157] (20.0 dBm) (no IR) * 5805 MHz [161] (20.0 dBm) (no IR) * 5825 MHz [165] (20.0 dBm) (no IR) * 5920 MHz [184] (disabled) * 5940 MHz [188] (disabled) * 5960 MHz [192] (disabled) * 5980 MHz [196] (disabled) * 6000 MHz [200] (disabled) * 6020 MHz [204] (disabled) * 6040 MHz [208] (disabled) * 6060 MHz [212] (disabled) * 6080 MHz [216] (disabled) Supported commands: * set_interface * new_key * join_ibss * set_pmksa * del_pmksa * flush_pmksa * connect * disconnect software interface modes (can always be added): interface combinations are not supported Device supports scan flush. Supported extended features: root@iiab-mint01:/home/ed01# |
s/b |
|
sorry |
|
Did you see the loud red message that the chipset doesn't support AP mode? |
|
I cant see a red message in diagnostics,please help |
|
Just FYI Ansible's yellow warnings were sometimes workable in the past, for those with an aversion to the color red, as part of notifications, e.g. those preferring a gentler color like yellow or orange. But FYI Ansible warnings are being completely removed from Ansible 2.14, whose Beta is expected next month, and whose final release ETA is 2022-11-07:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html#id71 |
Sorry I meant within iiab-network when you ran iiab-network at Mon 1 Aug 15:06:12 CAT 2022 |
|
yes it was there |
|
Then why do you continue trying to enable hotspot support on a chipset that does not support AP mode as noted below? |
TASK [network : Run 'iw list' to check for Access Point capability -- if discovered_wireless_iface != "none"] ****************************************************************************************
fatal: [127.0.0.1]: FAILED! => {"changed": true, "cmd": "iw list | grep '^[[:space:]]*\\* AP$'", "delta": "0:00:00.024203", "end": "2022-08-01 15:31:20.228186", "msg": "non-zero return code", "rc": 1, "start": "2022-08-01 15:31:20.203983", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}
|
|
Sorry i missed that final decision that the chipset does not support hotspot,sincere apologies.I guess i can close the ticket now. |
|
that was the line in red |
|
Thanks very much Jerry and Adam for your help,very much appreciated.Please let me know if you need to add something otherwise we can close the ticket. |
|
Many Thanks @EMG70 for pushing forward, skill-building for Zimbabwe. Despite some "vintage" (less than ideal!) hardware you're currently stuck with, through no fault of your own. Please test Linux Mint 21 if/when you later have time — in coming days or after the return from your trip — preferably on better hardware (that's more supportive of WiFi AP Mode) if possible 😄 |
|
Definitely need better hardware next time .Meantime i will make sure I have all content i need before traveling.I will try mint 21 on my return.Thanks once again Gents. |
|
Last attempt with external wifi dongle |
root@iiab-mint01:/home/ed01# iw list Wiphy phy0 max # scan SSIDs: 1 max scan IEs length: 0 bytes max # sched scan SSIDs: 0 max # match sets: 0 max # scan plans: 1 max scan plan interval: -1 max scan plan iterations: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP-128 (00-0f-ac:4) * CMAC (00-0f-ac:6) Available Antennas: TX 0 RX 0 Supported interface modes: * IBSS * managed Band 1: Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps (short preamble supported) * 5.5 Mbps (short preamble supported) * 11.0 Mbps (short preamble supported) * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (20.0 dBm) (no IR) * 2472 MHz [13] (20.0 dBm) (no IR) * 2484 MHz [14] (20.0 dBm) (no IR) Band 2: Bitrates (non-HT): * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 5170 MHz [34] (disabled) * 5180 MHz [36] (20.0 dBm) (no IR) * 5190 MHz [38] (20.0 dBm) (no IR) * 5200 MHz [40] (20.0 dBm) (no IR) * 5210 MHz [42] (20.0 dBm) (no IR) * 5220 MHz [44] (20.0 dBm) (no IR) * 5230 MHz [46] (20.0 dBm) (no IR) * 5240 MHz [48] (20.0 dBm) (no IR) * 5260 MHz [52] (20.0 dBm) (no IR, radar detection) * 5280 MHz [56] (20.0 dBm) (no IR, radar detection) * 5300 MHz [60] (20.0 dBm) (no IR, radar detection) * 5320 MHz [64] (20.0 dBm) (no IR, radar detection) * 5500 MHz [100] (20.0 dBm) (no IR, radar detection) * 5520 MHz [104] (20.0 dBm) (no IR, radar detection) * 5540 MHz [108] (20.0 dBm) (no IR, radar detection) * 5560 MHz [112] (20.0 dBm) (no IR, radar detection) * 5580 MHz [116] (20.0 dBm) (no IR, radar detection) * 5600 MHz [120] (20.0 dBm) (no IR, radar detection) * 5620 MHz [124] (20.0 dBm) (no IR, radar detection) * 5640 MHz [128] (20.0 dBm) (no IR, radar detection) * 5660 MHz [132] (20.0 dBm) (no IR, radar detection) * 5680 MHz [136] (20.0 dBm) (no IR, radar detection) * 5700 MHz [140] (20.0 dBm) (no IR, radar detection) * 5745 MHz [149] (20.0 dBm) (no IR) * 5765 MHz [153] (20.0 dBm) (no IR) * 5785 MHz [157] (20.0 dBm) (no IR) * 5805 MHz [161] (20.0 dBm) (no IR) * 5825 MHz [165] (20.0 dBm) (no IR) * 5920 MHz [184] (disabled) * 5940 MHz [188] (disabled) * 5960 MHz [192] (disabled) * 5980 MHz [196] (disabled) * 6000 MHz [200] (disabled) * 6020 MHz [204] (disabled) * 6040 MHz [208] (disabled) * 6060 MHz [212] (disabled) * 6080 MHz [216] (disabled) Supported commands: * set_interface * new_key * join_ibss * set_pmksa * del_pmksa * flush_pmksa * connect * disconnect software interface modes (can always be added): interface combinations are not supported Device supports scan flush. Supported extended features: |
root@iiab-mint01:/home/ed01# ls /sys/class/net br0 enp9s0 lo tun0 wlp12s0 wlx1ca7705e063c root@iiab-mint01:/home/ed01# |
root@iiab-mint01:/home/ed01# ls /sys/class/net br0 enp9s0 lo tun0 wlp12s0 wlx1ca7705e063c root@iiab-mint01:/home/ed01# lsusb Bus 002 Device 003: ID 0bda:0179 Realtek Semiconductor Corp. RTL8188ETV Wireless LAN 802.11n Network Adapter Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 0c45:6400 Microdia Integrated_Webcam_1.3M Bus 001 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub root@iiab-mint01:/home/ed01# |
|
Think you might be missing the firmware for that device, try that Driver Manager screen that you were at before. |
|
comes up as working with alternative drivers |
|
image taking long to load but no issues on drive manager |
|
|
|
[ 3640.831230] usb 2-3: new high-speed USB device number 2 using ehci-pci |
|
Looks to be using the same firmware as the on board chip, Edit: onboard is using Broadcom BCM4315 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) @shanti-bhardwa From your notes Is there an alternate firmware that does AP mode for this device: 0bda:0179 Realtek Semiconductor Corp. RTL8188ETV Wireless LAN 802.11n Network Adapter uses the r8188eu kernel driver? |
|
I have just seen some Tplink USB dongles that support AP.I will buy one and try,will let you know soonest and also check with Shanty which ones are best. |
|
Thanks Jerry,will update in a day or two |
|
Think you need to custom compile the driver to get AP mode |
holta
changed the title
I see,I will refer to these documents and try .Thanks. |
In short, this PR was overkill:
As confirmed by @EMG70's:
This Ansible stanza regrettably introduces many different code paths for what should really be a dead simple
grep -qexistence test.In any case, they're now fixed and tested, and we live with Ansible's artificially-added complexity in this case.