Bug 387104

Summary:	Beta2 DVD Installation : automatic configuration is missing network 88E8056
Product:	[openSUSE] openSUSE 11.0	Reporter:	Gilles Sabourin <sabourin.gilles>
Component:	Installation	Assignee:	Michal Zugec <mzugec>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None
Version:	Beta 2
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.0
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	yast2 logs hwinfo on P5K-E Wifi/AP dmesg output from kernel - opensuse 1st start ifconfig -a output

Description Gilles Sabourin 2008-05-06 09:38:23 UTC

I have a P5K-E Wifi/AP asustek motherboard which offers :

- one ethernet gigabit controller Marvell Yukon 88E8056
- one wireless device rtl8187 802.11b/g.

After automatic configuration is done and openSUSE have restarted, only wireless rtl8187 is configured, not ethernet gigabit 88E8056

This gigabit ethernet device is recognized cand an be configured in yast.

Comment 1 Stephan Kulow 2008-05-08 12:46:22 UTC

please provide your yast log files

Comment 2 Gilles Sabourin 2008-05-08 18:41:25 UTC

Created attachment 213682 [details]
yast2 logs

Comment 3 Gilles Sabourin 2008-05-08 18:42:30 UTC

Created attachment 213683 [details]
hwinfo on P5K-E Wifi/AP

Comment 4 Gilles Sabourin 2008-05-08 18:43:37 UTC

Created attachment 213684 [details]
dmesg output from kernel - opensuse 1st start

Comment 5 Gilles Sabourin 2008-05-08 18:44:26 UTC

Created attachment 213685 [details]
ifconfig -a output

Comment 6 Gilles Sabourin 2008-05-08 19:32:51 UTC

I have a look myself at yast logs. 88E8056 device is detected and well supported by sky2 module (eth0). rtl8187 is also supported and seen as a wireless device (wlan0), but this device is configured with no cyphering.

As my wireless router is only offering WPA TKIP/AES, the authentication fails.

yast2 lan configuration proposal returns both devices (from line 1060)
- RTL8187_Wireless already configured with DHCP [preformatted proposal]
- 88E8056 PCI-E Gigabit Ethernet Controller not yet used

At the end of this process, only "lo" and "wlan0" interfaces are listed, and eth0 is not in the list and is disabled.

Comment 7 Michal Zugec 2008-05-09 13:39:16 UTC

Sure, but this is only proposal.
Maybe it should be better documented:
- when "laptop" is detected, prefered method is NetworkManager, otherwise NetControl
- for NetworkManager propose to configure all devices
- for NetControl propose to configure first available (with regular device name) device 

Did you offer anything else?

Comment 8 Gilles Sabourin 2008-05-09 14:18:48 UTC

According to this strategy, the results returned by yast are corrects. But, in the case where the PC is not a laptop, application of this strategy leads to no connectivity.

The simplest way could be for NetControl to propose to configure in first ethernet devices with regular device name.

I guess the cost of this enhancement is lower than providing a guy to allow the user to give all wireless parameters.

In my case, my prefered method to connect my destop is by ethernet device, and my prefered way to connect my laptop is by wireless device, even if I have an ethernet port.

Comment 9 Michal Zugec 2008-06-02 07:57:25 UTC

already fixed for you - yast now configure first _plugged_ device which is in your case Gigabit netcard

*** This bug has been marked as a duplicate of bug 389131 ***