[Bug 1186677] New: Leap 15.3 gold master - Ethernet controller added as wlan0
https://bugzilla.suse.com/show_bug.cgi?id=1186677 Bug ID: 1186677 Summary: Leap 15.3 gold master - Ethernet controller added as wlan0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs@suse.de Reporter: axel.braun@gmx.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I booted a Raspi4 from USB stick for installation of Leap 15.3 build 160 (gold master), and there was no network autodetected (ethernet cable plugged in!) On the Network settings page it offers ARM Ethernet controller as wlan0, and showing all WIFI options, but it does not find any wireless network. I could add manually an ethernet device eth0, which then enables to add online-repositories. See: https://lists.opensuse.org/archives/list/arm@lists.opensuse.org/thread/7JHAM... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
Guillaume GARDET
https://bugzilla.suse.com/show_bug.cgi?id=1186677
Guillaume GARDET
https://bugzilla.suse.com/show_bug.cgi?id=1186677
Dirk Mueller
https://bugzilla.suse.com/show_bug.cgi?id=1186677
Matthias Brugger
https://bugzilla.suse.com/show_bug.cgi?id=1186677
Ivan Ivanov
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c1
Ivan Ivanov
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c2
Axel Braun
Hi Axel, please, could you give me a link to image that you have used? I somehow can't find build 160 anywhere. Thanks!
http://download.opensuse.org/distribution/leap/15.3/iso/openSUSE-Leap-15.3-D... as of 26 May 2021 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c3
Ivan Ivanov
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c4
Matthias Brugger
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c6
Ivan Ivanov
So that means we are missing /lib/firmware/brcm/brcmfmac43455-sdio.clm_blob in the installation image.
Yes, sorry, that I haven't said this explicitly. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c7
Imobach Gonzalez Sosa
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c8
Steffen Winterfeldt
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c9
--- Comment #9 from Ivan Ivanov
First, openSUSE-Tumbleweed-ARM-XFCE-raspberrypi.aarch64.raw.xz is a kiwi built image and likely unconditionally contains all firmware blobs.
The installable images contain only firmware blobs needed for the modules to load. So comparing TW *raw.xz files with Leap *.iso won't reveal anything.
Well, if we ignore compressed vs. uncompressed it show which firmware file is missing.
vs. Leap-15.3: /mnt/lib/firmware/brcm> ls -l brcmfmac4345[56]* -rw-r--r-- 1 root root 638951 3. Mai 14:00 brcmfmac43455-sdio.bin -rw-r--r-- 1 root root 1884 3. Mai 14:00 brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lrwxrwxrwx 1 root root 47 3. Mai 14:00 brcmfmac43455-sdio.raspberrypi,4-compute-module.txt.xz -> brcmfmac43455-sdio.raspberrypi,4-model-b.txt.xz -rw-r--r-- 1 root root 1883 3. Mai 14:00 brcmfmac43455-sdio.raspberrypi,4-model-b.txt -rw-r--r-- 1 root root 495898 19. M�r 21:14 brcmfmac43456-sdio.bin -rw-r--r-- 1 root root 7163 19. M�r 21:14 brcmfmac43456-sdio.clm_blob lrwxrwxrwx 1 root root 22 3. Mai 14:00 brcmfmac43456-sdio.raspberrypi,4-compute-module.txt -> brcmfmac43456-sdio.txt lrwxrwxrwx 1 root root 22 3. Mai 14:00 brcmfmac43456-sdio.raspberrypi,400.txt -> brcmfmac43456-sdio.txt -rw-r--r-- 1 root root 2053 19. M�r 21:14 brcmfmac43456-sdio.txt
From here you can see that only brcmfmac43456-sdio.clm_blob file is present, while the driver is looking for brcmfmac43455-sdio.clm_blob. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
Ivan Ivanov
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c11
--- Comment #11 from Steffen Winterfeldt
From here you can see that only brcmfmac43456-sdio.clm_blob file is present, while the driver is looking for brcmfmac43455-sdio.clm_blob.
As said, please check your config. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c12
--- Comment #12 from Ivan Ivanov
From here you can see that only brcmfmac43456-sdio.clm_blob file is present, while the driver is looking for brcmfmac43455-sdio.clm_blob.
As said, please check your config.
Hm, not sure which config you are referring. This is about openSUSE-Leap-15.3-DVD-aarch64.iso -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c13
--- Comment #13 from Steffen Winterfeldt
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c14
--- Comment #14 from Ivan Ivanov
Both, TW and Leap.
:-) I am only user of these ISOs, which try to help resolving this issue, not their creator. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c15
--- Comment #15 from Steffen Winterfeldt
:-) I am only user of these ISOs, which try to help resolving this issue, not their creator.
Ah, sorry. I thought were involved in this aarch64 project. :-) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c16
--- Comment #16 from Ivan Ivanov
:-) I am only user of these ISOs, which try to help resolving this issue, not their creator.
Ah, sorry. I thought were involved in this aarch64 project. :-)
Well, I am somehow, but creating images is black art to me. :-) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c17
--- Comment #17 from Dirk Mueller
Current TW, for example has:
# modinfo -F firmware brcmfmac.ko.xz | head -2 brcm/brcm/brcmfmac*-pcie.*.txt brcm/brcm/brcmfmac*-sdio.*.txt
This looks entirely wrong to me.
this comes from:
commit 75729e110e680687668fd5b4bdd7b25c92e9c00d
Author: Matthias Brugger
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c18
--- Comment #18 from Dirk Mueller
That said, I'm actually not sure what drags in *clm_blob currently.
I think in installed systems simply all of kernel-firmware-brcm is available, so also the clm_blob files (which are not referenced as firmware). so this needs to be listed explicitly as firmware dependency on the module for installation-imagees to include those files? then thats a kernel patch.. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c19
--- Comment #19 from Steffen Winterfeldt
+MODULE_FIRMWARE(BRCMF_FW_DEFAULT_PATH "brcm/brcmfmac*-sdio.*.txt"); +MODULE_FIRMWARE(BRCMF_FW_DEFAULT_PATH "brcm/brcmfmac*-pcie.*.txt");
My point was the doubled 'brcm' directory, which is apparently not correct. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c20
--- Comment #20 from Steffen Winterfeldt
I think in installed systems simply all of kernel-firmware-brcm is available, so also the clm_blob files (which are not referenced as firmware).
At least one of them is also on the install ISO. But I'm puzzled as how it gets there. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c21
Steffen Winterfeldt
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c22
--- Comment #22 from Matthias Brugger
+MODULE_FIRMWARE(BRCMF_FW_DEFAULT_PATH "brcm/brcmfmac*-sdio.*.txt"); +MODULE_FIRMWARE(BRCMF_FW_DEFAULT_PATH "brcm/brcmfmac*-pcie.*.txt");
My point was the doubled 'brcm' directory, which is apparently not correct.
I'll fix that in the kernel, no problem. Regarding brcmfmac43455-sdio.clm_blob: although the driver does not mandate a clm_blob the in the case of the RPi4 we are not able to connect to a wlan. So we would need to add brcmfmac43455-sdio.clm_blob to the installer. Beware that in kernel-firmware(-brcm) this is a softlink to cypress/cyfmac43455-sdio.clm_blob -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c23
--- Comment #23 from Steffen Winterfeldt
So we would need to add brcmfmac43455-sdio.clm_blob to the installer.
Well, yes, that's obvious. The question was *how* without making things more messy. See comment 21. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c24
--- Comment #24 from Matthias Brugger
So we would need to add brcmfmac43455-sdio.clm_blob to the installer.
Well, yes, that's obvious. The question was *how* without making things more messy. See comment 21.
Well brcmfmac43456-sdio.clm_blob is used for RPi400 and it's not part of linux-firmware (yet). In comparison brcmfmac43455-sdio is part of linux-firmware. Anyway reading bsc#1169094 where we had a similar approach I think the easiet would be to add a the file to modinfo. I'm not sure if this will be accepted upstream, but as a stopgap I can add this out-of-tree patch to the kernel now and we can figure out how to fix this on tumbleweed if upstream does not like the clm_blob being added to modinfo. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
Matthias Brugger
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c25
--- Comment #25 from Steffen Winterfeldt
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c26
--- Comment #26 from Matthias Brugger
What's the status of bcm43xx-firmware? Should I continue to use it? Additionally to kernel-firmware-brcm?
Yes please. It holds firmware files that are not yet part of linux-firmware. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
Matthias Brugger
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c27
Matthias Brugger
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c35
--- Comment #35 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c36
--- Comment #36 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c37
--- Comment #37 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c38
--- Comment #38 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c39
Matthias Brugger
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c40
--- Comment #40 from Axel Braun
I suppose we are not planning to re-build the installer, as Leap is already released. I added Lubos to confirm.
The rebuild of installation media would grab all latest updates, improve user experience in terms of 'easy installation' and reduce the network load as not everybody needs to pull all updates. So from my PoV there are good reasons for a rebuild - we do this for TW every day :-) Shall we discuss this on factory@l.o.o? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c41
--- Comment #41 from Steffen Winterfeldt
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c43
Petr Tesa����k
Quarterly Updates for Leap? Why not, if it's supposed to be following SLES anyway.
@Lubos: Are there plans to make Leap Quarterly Updates? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c44
--- Comment #44 from Axel Braun
https://bugzilla.suse.com/show_bug.cgi?id=1186677
Matthias Brugger
https://bugzilla.suse.com/show_bug.cgi?id=1186677
Matthias Brugger
https://bugzilla.suse.com/show_bug.cgi?id=1186677
https://bugzilla.suse.com/show_bug.cgi?id=1186677#c49
Matthias Brugger
(In reply to Matthias Brugger from comment #47)
Axel did you verify Leap 15.3 updated installer image?
I just tried it at the moment (openSUSE-Leap-15.3-3-NET-aarch64-Build38.1-Media.iso), and, as far as I could get, it seems to run into the same error:
- despite connected to Ethernet, it asks for SSID and Wifi password - Then it complains that 'repository does not match selected boot image' and wants to download - 'Image does not fit' (on a 8GB stick...), which looks like https://bugzilla.opensuse.org/show_bug.cgi?id=1197662
-> looks to me that the bug is still not fixed
Axel, what I see in bsc#1199820 is, that the installer askes for ESSID for the wlan0 first, not that the ethernet device is shown as wlan0. You can check that by looking at the MAC address. Look out for line
if_to_mac: wlan0 = dc:a6:32:b1:07:7c
Can you please double check. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1186677
Matthias Brugger
https://bugzilla.suse.com/show_bug.cgi?id=1186677
Matthias Brugger
participants (1)
-
bugzilla_noreply@suse.com