Bug 387110

Summary:	Beta2 DVD Installation : rtl8187 automatically configured as ethernet device
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:	Normal
Priority:	P5 - None	CC:	ma
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

Description Gilles Sabourin 2008-05-06 09:53:07 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.

This wireless device is configured as an ethernet device by automatic configuration.

No wireless configuration guy is proposed to allow the user to configure its wireless settings at installation time.

Comment 1 Stephan Kulow 2008-05-08 12:48:21 UTC

I'm not sure what's the bug here. Can you please be more specific? And please provide your yast log files

Comment 2 Stephan Kulow 2008-05-08 12:49:49 UTC

*** Bug 387118 has been marked as a duplicate of this bug. ***

Comment 3 Gilles Sabourin 2008-05-08 19:53:29 UTC

I haven't exactly reported the problem : rtl8187 is supported and well detected as a wireless device (RTL8187_Wireless, wlan0), but this device is configured with no ciphering.

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

I think that 88E8056 should have been proposed for automatic configuration rather than RTL8187_Wireless.

A wireless device can't be automatically configured since, at least, SSID, working mode (managed, ad-hoc...), ciphering type (WEP, WPA, ...), passphrase or key are wireless parameters which can only be provided by the user.

An other solution could be to provide the guy which allow the user to provide its wireless configuration. This is nice for laptop with wireless

Comment 4 Gilles Sabourin 2008-05-08 19:54:29 UTC

I haven't exactly reported the problem : rtl8187 is supported and well detected as a wireless device (RTL8187_Wireless, wlan0), but this device is configured with no ciphering.

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

I think that 88E8056 should have been proposed for automatic configuration rather than RTL8187_Wireless.

A wireless device can't be automatically configured since, at least, SSID, working mode (managed, ad-hoc...), ciphering type (WEP, WPA, ...), passphrase or key are wireless parameters which can only be provided by the user.

An other solution could be to provide the guy which allow the user to provide its wireless configuration. This is nice for laptop with only wireless network available.

Comment 5 Gilles Sabourin 2008-05-08 19:56:45 UTC

Created attachment 213705 [details]
yast2 logs

Comment 6 Gilles Sabourin 2008-05-08 20:13:21 UTC

bug 387118 is NOT a duplicate from this bug. This is an old problem : whenever you configure a device (again), dhcp client daemon fails to acquire new ip address.

The workaround is to stop all network devices which also stops dhcp client daemon, and only then, to restart it.

Comment 7 Michal Zugec 2008-05-13 13:58:31 UTC

already fixed

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