On Wednesday 22 September 2004 11:32, Gary Stainburn wrote: > On Friday 17 Sep 2004 11:59 pm, James Wilkinson wrote: > > Gary Stainburn wrote: > > > Running FC1 with USB keyboard and mouse with no problems. > > > > > > Just bought a new desk and re-arranged wiring so that my mouse goes > > > through a USB hub first to eliminate shore wire syndrome. > > > > > > Everything still works fine in WinXP, but the mouse won't work in > > > Linux. > > > > > > Anyone got any ideas why? > > > > What does lsusb show? > > > > James. > > Okay, > > so here's the story so far. > > If I cold boot into Linux it doesn't work. > If I cold boot into WinXP then reboot into Linux it doesn't work. > If I cold boot into WinXP, - USE XP for a while - then reboot it does > work. > > Below are the lsusb with the mouse working and without. Looks like thw > whole hub's missing in the first one as the Epson and joystick are also > missing. > > The mouse is a Genius Netscroll Traveller USB ballless mouse. When > booting into Linux (even when it ultimately doesn't work) it flashes > are suitable points, such as on initial turn-on, after kernel load, > during device init routines, during service start where it includes: > > Starting USB Keyboard [OK] > Starting USB Mouse [OK] > > [root@garyh root]# cat lsusb.nomouse > Bus 005 Device 001: ID 0000:0000 > Bus 004 Device 001: ID 0000:0000 > Bus 003 Device 001: ID 0000:0000 > Bus 002 Device 001: ID 0000:0000 > Bus 001 Device 001: ID 0000:0000 > Bus 001 Device 002: ID 046d:c309 Logitech, Inc. > [root@garyh root]# cat lsusb.mouse > Bus 005 Device 001: ID 0000:0000 > Bus 005 Device 003: ID 05e3:0660 Genesys Logic, Inc. > Bus 005 Device 005: ID 046d:c283 Logitech, Inc. WingMan Force 3D > Bus 005 Device 006: ID 04b8:0005 Seiko Epson Corp. Stylus Printer > Bus 005 Device 007: ID 0458:002e KYE Systems Corp. (Mouse Systems) > Bus 004 Device 001: ID 0000:0000 > Bus 003 Device 001: ID 0000:0000 > Bus 002 Device 001: ID 0000:0000 > Bus 001 Device 001: ID 0000:0000 > Bus 001 Device 002: ID 046d:c309 Logitech, Inc. > [root@garyh root]# > Gary buddy I would say you have faulty memory. Windows doesn't fill the modules the same way linux does. The fact that you can run windows first is proof. If there is a fracture in the circut of the memory, it will open when its cold and close when it hot , why? because when metals and other substances get hot they swell, and shrink when cold. The fact that you can actually boot into windows and work for a while with problems suggests that it isn't a fault on any other piece of hardware, Anyway hope this helps. Chad > > -- > Gary Stainburn > > This email does not contain private or confidential material as it > may be snooped on by interested government parties for unknown > and undisclosed purposes - Regulation of Investigatory Powers Act, 2000 -- -- Chadley Wilson Production Line Supervisor Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
