Bugzilla – Bug 307745
One NIC too much displayed in step 2
Last modified: 2007-09-13 14:19:45 UTC
During installation there will be one NIC too much be displayed.
Created attachment 162012 [details] hwinfo-network.txt
Created attachment 162013 [details] yast2-000.png
Created attachment 162014 [details] yast2-001.png
Created attachment 162015 [details] y2logs.tgz
This is by no means critical bug. By definition: "Critical - Crash, loss of data, corruption of data, severe memory leak", which this issue is not. It is maybe not even major ("Major - Major loss of function")... Application does not crash, no functionality is lost, just somehow confusing data are presented to the user.
Something in /devices/pci0000:00/0000:00:1e.0/0000:06:01.0 thinks (s)he ;-) is a network card, more specifically 'D-Link AR5211 802.11ab NIC'. From off-bugzilla talk with Holgi there is really 3rd wireless NIC present on this machine, but it seems to be misdetected. Hwinfo doesn't even show it to the user (see comment #1), otoh .probe.netcard YaST agent shows something, but dev_name key is empty (which is needed to retrieve 'name' key of the device). Kernel module did not get loaded? Steffen, can you have a look?
Btw, I did not notice at first - hwinfo from comment #1 is 'hwinfo --network'. 'hwinfo --netcard' would be of much greater use here ;-)
Holger, please attach the log of 'hwinfo --netcard --log=xxx'.
Created attachment 163451 [details] hwinfo.txt
The 3rd is an unsupported wireless card. As it's unsupported, hwinfo doesn't really know it's wifi. Joe, is that correct so far? Ort do we support it and the driver is just missing?
It's an Atheros card, we do not ship the driver at the moment. And without the driver, hwinfo does not know that it's a wireless card. If you install the drivers from http://madwifi.org/suse/ , it should be shown correctly. The situation is of course not perfect, as the user gets any WLAN card for which no driver is loaded presented as an ethernet device. Maybe YaST should check whether hwinfo reports an interface file and issue a warning that the system may lack a driver in case it's missing. Maybe it should even grey out the entry.
Katarina, maybe you can do something about it.
If the driver for a card does not get loaded (for whatever reason), the device summary i.e. the text you see under the table listing all network devices clearly states that "Unable to configure network card because kernel driver is not present". Of course, one must highlight that device item in the table first ;-) Moreover, 'Configure' button is disabled in such case I don't think there's anything more I can do here - we let the user know what is going on (no driver, no further info on NIC, no configuration possible). Invalid then?
I'd say so.
Hm, as this is atheros card, it's a duplicate *** This bug has been marked as a duplicate of bug 216530 ***