wifi missing on core20 image with rpi

Bug #1878258 reported by Paul Larson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Fix Released
Critical
Unassigned
linux-firmware-raspi2 (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

With the rpi images for core20, no wifi interface is detected. I've tried this on rpi4 for certain, but I believe it is also happening on all other rpi devices with wifi.

This can be reproduced on both armhf and arm64 images, as well as others: http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200512.3/

Only lo and eth0 are detecte:
$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether dc:a6:32:59:ce:25 brd ff:ff:ff:ff:ff:ff

Tags: uc20
Pierre Equoy (pieq)
description: updated
Revision history for this message
Betty Lin (bettyl) wrote :

I got the same problem with ubuntu-core-20-arm64+raspi.img.xz on PI3B

$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enxb827eb9961ff: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether b8:27:eb:99:61:ff brd ff:ff:ff:ff:ff:ff

Revision history for this message
Nara Huang (narahuang) wrote :

I can see the same issue with Core 20 daily build 20200512.3 on Pi3 B+
$ uname -a
Linux ubuntu 5.4.0-1011-raspi #11-Ubuntu SMP Fri May 8 07:43:33 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux

$ snap list
Name Version Rev Tracking Publisher Notes
core20 20 635 latest/beta canonical✓ base
pi 20-1 58 20/beta canonical✓ gadget
pi-kernel 5.4.0-1011.11 154 20/beta canonical✓ kernel
snapd 2.45 7780 latest/beta canonical✓ snapd

$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enxb827eb570ac2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether b8:27:eb:57:0a:c2 brd ff:ff:ff:ff:ff:ff

Chris Wayne (cwayne)
tags: added: core20
Revision history for this message
Ian Johnson (anonymouse67) wrote :

I looked into the difference between a focal classic image (with kernel 5.4.0-1008-raspi) where I can see the wlan interface and the uc20 beta images where I cannot, and I see with the uc20 image, all of the broadcom related kernel modules that are loaded in the focal classic image are also loaded in the uc20 image, with a few additional ones. Additionally, as per Dave, I checked /lib/firmware/brcm, and this directory exists on uc20 and matches the contents of what's on classic images.

For reference, attaching lsmod of both the focal classic image and the uc20 image.
Focal classic lsmod: https://pastebin.ubuntu.com/p/4PxbFJRH82/
uc20 lsmod: https://pastebin.ubuntu.com/p/JRCVr4y76f/

So afaict this doesn't seem kernel module related, though one difference is that we don't have the full set of kernel modules available at the expected directory during the initramfs on uc20, while we might have that available on the focal classic image, but I don't see why this would affect anything.

Revision history for this message
Ian Johnson (anonymouse67) wrote :

also to be clear, my last comment was from arm64 rpi4 with kernel 5.4.0-1011-raspi

Changed in snapd:
importance: Undecided → High
status: New → Confirmed
Changed in linux-firmware-raspi2 (Ubuntu):
status: New → Confirmed
Changed in snapd:
importance: High → Critical
Changed in snapd:
assignee: nobody → Juerg Haefliger (juergh)
Paul Larson (pwlars)
tags: added: uc20
removed: core20
Juerg Haefliger (juergh)
Changed in snapd:
assignee: Juerg Haefliger (juergh) → nobody
Michael Vogt (mvo)
Changed in linux-firmware-raspi2 (Ubuntu):
importance: Undecided → Critical
Michael Vogt (mvo)
Changed in linux-firmware-raspi2 (Ubuntu):
status: Confirmed → In Progress
Changed in snapd:
status: Confirmed → In Progress
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

The device is there

Changed in snapd:
status: In Progress → Fix Released
Changed in linux-firmware-raspi2 (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.