HCL - Apple MacBook Pro (11,1)

User Support HCL Reports
15

I finally ended up with this solution:

System information:
xen_version: 4.14.5
Linux 5.15.81-1.fc32.qubes.x86_64
Qubes release 4.1.1 (R4.1)
Installed on a MacbookPro along to other operating systems in separate partition(s).

Assumption:
Some internet connection, either wired or wireless using a dongle (sys-usb)

Steps:

  1. Create a new qube based on the fedora-36 template

  • Open Qube Manager → New qube
    [Basic] Name and label: sys-wl
    [Basic] Type: StandaloneVM (fully persistent)
    [Basic] Template: fedora-36 (default)
    [Basic] Networking: sys-net (you need somebody to connect you)
    [Basic] Enable “Launch settings after creation”
    [Advanced] Enable "Provides network access to other qubes"
    [Advanced] Leave everything else as it is preconfigured

  • After Creation the [Dom0] Settings window for sys-wl pops up
    [Basic] Leave everything else as it is preconfigured
    [Advanced] Disable “Include in memory balancing”
    [Advanced] Kernel->Kernel: (provided by qube) → alternatively: (dom0): qvm-prefs sys-wl kernel ‘’
    [Advanced] Virtualization->Mode: HVM

  1. Install broadcom-wl
    Open a terminal
    sys-wl: Terminal
    Based on the information by balko here
    [user@sys-wl ~]$ sudo dnf config-manager --set-enabled rpmfusion-free
    [user@sys-wl ~]$ sudo dnf config-manager --set-enabled rpmfusion-free-updates
    [user@sys-wl ~]$ sudo dnf config-manager --set-enabled rpmfusion-nonfree
    [user@sys-wl ~]$ sudo dnf config-manager --set-enabled rpmfusion-nonfree-updates
    [user@sys-wl ~]$ sudo dnf upgrade --refresh
    [user@sys-wl ~]$ sudo dnf install broadcom-wl

  2. Blacklist unwanted modules
    [user@sys-wl ~]$ sudo vi /etc/modprobe.d/blacklist.conf
    blacklist b43
    blacklist bcma

  3. Prepare settings for sys-wl prior to restart
    Open Qube Manager
    sys-wl->Settings
    [Basic] Net qube: (none)(current)
    [Basic] Leave everything else as it is already configured

  4. Detach BCM4350 in case that it is attached to any VM (in my case it was attached per default to sys-net)
    a) Shutdown the VM (my case: sys-net) to which the bcm4360 card has been assigned.
    b) Open Qube Manager → sys-net → Settings → Devices → click in the right window frame on “Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter”, and move ( < ) it to the left one → OK

  5. Attach BCM4360 to the newly created sys-wl with the “magic” options

  • Shutdown the newly created sys-wl

  • Find out the BDF of your device
    (dom0) qvm-pci
    BACKEND:DEVID DESCRIPTION USED BY
    …
    dom0:02_00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter
    …

  • Now: The magic one step
    BEING WELL AWARE OF side channel attacks based on this description (How to use PCI devices | Qubes OS) attach the device to sys-wl:
    (dom0) sudo qvm-pci a sys-bcm4360 dom0:02_00.0 --persistent -o no-strict-reset=true -o permissive=true

  • Show the changes:
    (dom0) qvm-pci
    BACKEND:DEVID DESCRIPTION USED BY
    …
    dom0:02_00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter sys-bcm4360 (no-strict-reset=true, permissive=true)
    …

  1. Reboot the whole system
    After you got your system up and running again, the Network Manager icon will be shown on the right part of the taskbar, and available networks will be shown, and you will be able to establish a wireless connection.
1 Like