Bugzilla – Bug 1199820
[rpi] - Ethernet controller added as wlan0
Last modified: 2022-09-22 15:37:01 UTC
+++ This bug was initially created as a clone of Bug #1186677 +++
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
I can confirm that I get asked about SSID and password. After connecting to the WLAN I don't see any progress in the installer.
Tested with openSUSE-Leap-15.4-NET-aarch64-Build230.2-Media.iso
My experience is:
I get asked for ESSID name:
> 00:02:03 <2>: ifcfg_write: device = wlan0, ifcfg = (null)
> 00:02:03 <4>: win on
> ESSID (Network Name). (Enter '+++' to abort).
> WLAN Authentication
> 0) <-- Back <--
> 1) No Authentication
> 2) WPA-PSK
> 3) WPA-PEAP
> > 0
After that I get fallback to eth0 which get's an IP.
Steffen, any idea why the installer does not try to get an IP from eth0 first before asking for ESSID?
Created attachment 859144 [details]
Leap 15.4 NET installer askes for ESSID first
The full debug log
The order network interfaces are presented is a bit tricky. Basically, because
people complained a lot in that area.
Technically, it's done here:
and you can watch the result in the log by searching for 'hd list (before)',
which is followed by 'hd list (after)'.
TL;DR: proper wired interfaces with an active link are considered first,
followed by wlan, followed by 'weird' interfaces (weird = interfaces without
proper matching card entry, which normally indicates some strange kernel
interface or an unsupported hardware).
I see in your case a network interface without a name ("(null)") - which is
really strange and looks a bit like some missing sysfs data.
Could you attach the log of "hwinfo --netcard --network --log=foo.log" to have
a better look at what's happening?
Created attachment 859149 [details]
> hwinfo --netcard --network --log=foo.log
It actually looks the very same on my rpi4. :-/
Anyway, as I see it, there are two different issues:
(a) hwinfo does not properly report the hardware: the wifi card ends up
in two different items and the ethernet card is missing entirely (only the
interface shows up)
(b) the wifi connection does not work
I can look into (a) but (b) seems to be more of a driver issue and in that
case is probably better tracked separately.
(In reply to Steffen Winterfeldt from comment #6)
> Ok, thanks.
> It actually looks the very same on my rpi4. :-/
> Anyway, as I see it, there are two different issues:
> (a) hwinfo does not properly report the hardware: the wifi card ends up
> in two different items and the ethernet card is missing entirely (only the
> interface shows up)
> (b) the wifi connection does not work
> I can look into (a) but (b) seems to be more of a driver issue and in that
> case is probably better tracked separately.
Yes please look into (a). My experience is that (b) isn't an issue, I can connect to my wifi when passing essid=xxx wpapsk=xxx
Adding to YaST Kanban board.
This is still an issue on TW 20220729
hwinfo is now maintained outside the YaST team by email@example.com. Reassigning.