No network connection after installation

User Support
1

Hi everybody,

I am a complete newbie when it comes to Qubes.
I currently have Qubes installed on my Macbook Pro 11.2 (Quad-Core Intel Core i7, 8GB memory) on separate partitions in parallel with other Linux operating systems and Big Sur on the same hardware (SSD). The installation went without any problems.
After booting the system, the network icon in the upper right corner of the taskbar is red. When I hover the mouse over it, the text “No network connection” appears.
The information from [Networking basics on qubes] seemed promising, but the problem is that without an internet connection I can’t download broadcom-sta-dkms and all the dependencies directly.
So I downloaded the package on another computer, but when I tried to install it, there were a lot of dependencies on other modules, which in turn depend on other modules. So in a few words, no success.

Here is a summary of the primarily relevant data from my point of view:

  • Macbook Pro 11.2 (Quad-Core Intel Core i7, 8GB memory)
  • Qubes OS release 4.1.1 (R4.1)
  • Default Template: debian-11

Output of lspci [dom0]:
00:00.0 Host bridge: Intel Corporation Crystal Well DRAM Controller (rev 08)
00:01.0 PCI bridge: Intel Corporation Crystal Well PCI Express x16 Controller (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Crystal Well Integrated Graphics Controller (rev 08)
00:03.0 Audio device: Intel Corporation Crystal Well HD Audio Controller (rev 08)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03)
03:00.0 Multimedia controller: Broadcom Inc. and subsidiaries 720p FaceTime HD Camera
04:00.0 Non-Volatile memory controller: Silicon Motion, Inc. SM2262/SM2262EN SSD Controller (rev 03)
05:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:03.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:04.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:05.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:06.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
07:00.0 System peripheral: Intel Corporation DSL5520 Thunderbolt 2 NHI [Falcon Ridge 4C 2013]

Output of lsusb [dom0]:
Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 05ac:8289 Apple, Inc. Bluetooth Host Controller
Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 003: ID 05ac:0263 Apple, Inc. Apple Internal Keyboard / Trackpad (MacBook Retina)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output of ifconfig [sys-firewall]:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.138.4.137 netmask 255.255.255.255 broadcast 10.255.255.255
inet6 fe80::216:3eff:fe5e:6c00 prefixlen 64 scopeid 0x20
ether 00:16:3e:5e:6c:00 txqueuelen 1000 (Ethernet)
RX packets 30 bytes 2202 (2.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 53 bytes 4006 (3.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 12 bytes 632 (632.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12 bytes 632 (632.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vif4.0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.138.4.137 netmask 255.255.255.255 broadcast 0.0.0.0
inet6 fe80::fcff:ffff:feff:ffff prefixlen 64 scopeid 0x20
ether fe:ff:ff:ff:ff:ff txqueuelen 32 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12 bytes 936 (936.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Output of ifconfig [sys-net]:
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 12 bytes 632 (632.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12 bytes 632 (632.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vif3.0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.138.27.206 netmask 255.255.255.255 broadcast 0.0.0.0
inet6 fe80::fcff:ffff:feff:ffff prefixlen 64 scopeid 0x20
ether fe:ff:ff:ff:ff:ff txqueuelen 32 (Ethernet)
RX packets 53 bytes 3264 (3.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 31 bytes 2692 (2.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I will provide all the information that could help to find a solution.

An Internet connection is important: Either wired or WiFi.

Can someone please, please help?
Thanks a lot!

2

Looks like sys-net is missing a/some interface[s] (IIRC)

Does lspci in sys-net list any network devices?

3

Yes, this is the output (lspci@sys-net):
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 Unassigned class [ff80]: XenSource, Inc. Xen Platform Device (rev 01)
00:04.0 VGA compatible controller: Device 1234:1111 (rev 02)
00:05.0 USB controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 10)
00:06.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03)

4

dang - it’s almost the same wireless card that I’m trying to get online (BMC4350) - I ended up plugging a USB Ethernet into the machine for now. :-/

1 Like
5

I could try out an external USB WiFi (ASUS USB-N13 802.11b/g/n).
Any suggestions how to achieve this?

6

If you have a sys-usb, you should just be able to plug it into the machine, see it pop up as a USB-device in the top bar, and assign it to the sys-net qube and available networks should pop u
p in the top bar. :crossed_fingers:

7

I already tried out a directly connected (wired) ethernet cable (ethernet to thunderbold and ethernet to usb as well) without any success.

8

No sys-usb present. Any information (reference, link etc.) how to create it?

9

Maybe this:

?

– I don’t know the difference between 11,1 and 11,2 … :-/

10

First of all thank you!!! I will report the result.

11

sys-usb created.
External USB WiFi recognized.
Now, trackpad & mouse are dead!

12

…and this https://github.com/QubesOS/qubes-issues/issues/6453 solution helped!

1 Like
13

External usb works fine, and I can establish WiFi connections to the Internet.
Any way, the suggested solution here ([Networking basics on qubes - #3 by unman]) doesn’t work. Maybe some details are still missing…(!?)
Another side effect using sys-usb is that the touchpad does not work, even after applying the solution indicated here ([Mouse and tablet can't click-and-drag using sys-usb · Issue #6453 · QubesOS/qubes-issues · GitHub]), it’s not possible resize or move any window, even if the mouse can be moved, and clicking works as well.

14

Well, I have followed this description https://forum.qubes-os.org/t/hcl-apple-macbook-pro-11-1/15944 and installed broadcom-wl without errors.
However, when I run lsmod | grep wl , I get no output at all.
The command modprobe wl gives me this error message:
modprobe: FATAL: Module wl not found in directory /lib/modules/5.15.81-1.fc32.qubes.x86_64
What am I doing wrong?
Any suggestions?

15

That’s where I’m lazy and just use a usb-ethernet dongle - I think it’s something about the running kernel version (5.15.81-1)vs. the kernel version that the broadcom-wl module is build for - try:

find /lib/modules | grep wl.ko
16

sudo find /lib/modules | grep wl.ko => No output at all.

17

Discrepancies between the kernel version and the module should logically prevent installation, right?

18

It looks like you didn’t follow that topic, because there it’s said:

set it’s kernel to empty value (use own kernel)

and from above it is obvious that you are using Qubes provided kernel

You can try to search my topics about building RTL88xxau drivers related to Qubes provided kernels and native kernels, as well as with dkms.

What worked for me and what I can suggest you is to create minimal template, to install native kernel there, to install pvgrub2-pvh and set that for its kernel, to assure to boot in such a template, to build the driver there, to create sys-net (!) in PVH (!) mode using pvgrub2-pvh as a kernel based on a dvm based on a said template.

Now, your Broadcom should be shown under sys-usb. Do not install any Broadcom drivers in your sys-usb’s template. If so, delete the template and recreate sys-usb without Broadcom drivers. After that, just attach it from sys-usb to sys-net-PVH and check there if it works. It should, at least it works for me. And I did it using dkms. I’m preparing to create a guide about building drivers with dkms in kernel>=6.x.

I couldn’t build the drivers under Qubes provided >=6.x kernel (with dkms).

19

This sounds like reliable and at the same time challenging information for someone like me with only a few days of experience with Qubes. But ok, I will take up the challenge, and of course I appreciate very much any additional information, hints, guiding or support.
Thank you!

20

OK, this seems to be the right doc.