Bug 114028

Summary:	booting with mouse plugged in messes up usb and network
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	jo de baer <jo.debaer>
Component:	Installation	Assignee:	E-mail List <yast2-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Major
Priority:	P5 - None
Version:	Beta 3
Target Milestone:	---
Hardware:	i386
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description jo de baer 2005-08-30 07:21:31 UTC

Hi, when I boot with my mouse connected in the usb port, I cannot use the mouse,
only the touchpad. The mouse does not even get power. lsusb yields this output :
Duplicate product spec at line 2453 product 0846:4240 WG111 WiFi

As a side effect eth0 is nog present when running ifconfig -a. I have no
network. Just running YaST-> network devices -> next -> finish repairs this.

None of these problems exist when booting without the mouse connected.

Hardware : Dell D800 with Logitech USB optical mouse.

I am novell staff so if you want you can log on to my laptop when I have the
problem. Obviously I will have repaired the network then - but the usb problem
will still persist and this is the root cause after all. Just send me a mail to
jdebaer@novell.com

PS during installation I noticed that by default the mouse was set to something
like "no mouse regardless if one is plugged in". I thought this was strange -
but I didn't change it because it was set to that by default.

Comment 1 jo de baer 2005-08-30 08:26:33 UTC

Ok - now even when booting without the mouse connected the usb system does not
come up.

Could it have something to do with bug
https://bugzilla.novell.com/show_bug.cgi?id=112820 ?

Comment 2 Ludwig Nussel 2005-08-30 08:42:39 UTC

yes 

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

Comment 3 jo de baer 2005-08-30 08:51:17 UTC

Now I reconfigured my mouse manually i.e. set it to USB optical mouse, rebooted,
and now I have mouse and network. But that shouldn't be necessary. I see you
marked it as a duplicate of 112820... Iguess it's likely that that is the
underlying cause - don't understand our device model anymore, too much changes :-)