|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 lan does not show the proper kernel modules | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Stephan Hemeier <Sauerlandlinux> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | kanderssen, manfred.h, mfilka, snwint |
| Version: | Leap 15.5 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Stephan Hemeier
2023-11-29 11:17:47 UTC
I guess yast2-network uses an agent based on libhd. I am not sure if it's enough that the kernel modules are suddenly available; it might also need a rebuilt libd (hardware detection, the basis of the 'hwinfo' command; part of package 'hwinfo'). 'libhd', of course. Steffen, any input from your side? Michal, Knut? hwinfo just presents the kernel module info; it does not check any modprobe configuration files. So whether or not a module is blacklisted does not matter. What yast makes of this, I've no idea. > I am not sure if it's enough that the kernel modules are suddenly available;
> it might also need a rebuilt libd
To be clear: hwinfo parses modules.alias from the running kernel. An
explicit database update is not needed.
I think, hwinfo is not the problem as you can see in my first post.
It shows both modules and also shows the active ones.
> Driver Info #0:
> Driver Status: r8169 is not active
> Driver Activation Cmd: "modprobe r8169"
> Driver Info #1:
> Driver Status: r8168 is active
> Driver Activation Cmd: "modprobe r8168"
But yast2 lan (networksettings) shows only r81689 or automatic.
r8168 is missing.
Same if I install broadcom-wl, only bcma is available (but is not the proper one for my Card), wl is missing.
Stephan
I think, hwinfo is not the problem as you can see in my first post.
It shows both modules and also shows the active ones.
> Driver Info #0:
> Driver Status: r8169 is not active
> Driver Activation Cmd: "modprobe r8169"
> Driver Info #1:
> Driver Status: r8168 is active
> Driver Activation Cmd: "modprobe r8168"
But yast2 lan (networksettings) shows only r8169 or automatic.
r8168 is missing.
Same if I install broadcom-wl, only bcma is available (but is not the proper one for my Card), wl is missing.
Stephan
I narrowed it down to this code: https://github.com/yast/yast-network/blob/master/src/lib/y2network/hwinfo.rb#L232-L238 def drivers driver = @hwinfo.fetch("drivers", []).first return [] unless driver modules = driver.fetch("modules", []) modules.map { |m| Driver.new(*m) } end I am not sure if that '.first' is significant here. Knut, Michal? (In reply to Stefan Hundhammer from comment #9) > I narrowed it down to this code: > > https://github.com/yast/yast-network/blob/master/src/lib/y2network/hwinfo. > rb#L232-L238 > > > def drivers > driver = @hwinfo.fetch("drivers", []).first > return [] unless driver > > modules = driver.fetch("modules", []) > modules.map { |m| Driver.new(*m) } > end > > > I am not sure if that '.first' is significant here. I will take a look, it looks like a clear candidate to be fixed / checked as it should select the active one instead of the first one. (In reply to Stephan Hemeier from comment #8) > I think, hwinfo is not the problem as you can see in my first post. > > It shows both modules and also shows the active ones. > > > Driver Info #0: > > Driver Status: r8169 is not active > > Driver Activation Cmd: "modprobe r8169" > > Driver Info #1: > > Driver Status: r8168 is active > > Driver Activation Cmd: "modprobe r8168" > > But yast2 lan (networksettings) shows only r8169 or automatic. > r8168 is missing. > > Same if I install broadcom-wl, only bcma is available (but is not the proper > one for my Card), wl is missing. > > Stephan It should be fixed by: https://github.com/yast/yast-network/pull/1347 Thanks, Knut! The fix should arrive in Leap 15.5 / SLE-15 SP5 as yast2-network-4.5.22. Excuse for the late answer. Thanks for your fix, now I can see my drivers as before. Stephan SUSE-RU-2024:0040-1: An update that has one fix can now be installed. Category: recommended (moderate) Bug References: 1217652 Sources used: SUSE Linux Enterprise High Performance Computing 15 SP5 (src): yast2-network-4.5.22-150500.3.8.1 SUSE Linux Enterprise Server 15 SP5 (src): yast2-network-4.5.22-150500.3.8.1 SUSE Linux Enterprise Server for SAP Applications 15 SP5 (src): yast2-network-4.5.22-150500.3.8.1 SUSE Linux Enterprise Desktop 15 SP5 (src): yast2-network-4.5.22-150500.3.8.1 Basesystem Module 15-SP5 (src): yast2-network-4.5.22-150500.3.8.1 openSUSE Leap 15.5 (src): yast2-network-4.5.22-150500.3.8.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. |