Bug 115504 - wireless usb keyboard and mouse (Logitech) not working
Summary: wireless usb keyboard and mouse (Logitech) not working
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-13 03:00 UTC by Ryan Betts
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-02-17 04:44:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ryan Betts 2004-02-13 03:00:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115

Description of problem:
When boot the 2.6 kernel in Fedora Core Test 2 the wireless keyboard
and mouse are not being loaded and therefore will not work. The
keyboard DOES work however in GRUB, but as soon as the kernel boots
the keyboard stops working and the mouse is never found. Halfway
through the booting process kudzu loads as though it has found the
keyboard and mouse but since the keyboard is dead the process times
out and the kernel continues to load without any problems.

Version-Release number of selected component (if applicable):
kernel-2.6.1-1.65

How reproducible:
Always

Steps to Reproduce:
1.boot kernel-2.6.1-1.65
2.
3.
    

Actual Results:  Logitech wireless keyboard and mouse do not work

Expected Results:  Initialization of keyboard and mouse

Additional info:

Comment 1 Ryan Betts 2004-02-13 03:02:12 UTC
Line 1 should read:

When boot the 2.6 kernel in "Fedora Core 2 Test 1" the wireless keyboard

Comment 2 Bill Nottingham 2004-02-16 06:21:50 UTC
Do you have a USB controller alias in /etc/modprobe.conf?

Comment 3 Ryan Betts 2004-02-17 04:12:41 UTC
just added it and it works great initializes just fine...don't know
why I didnt think of that...

Comment 4 Bill Nottingham 2004-02-17 04:44:53 UTC
OK, fixed with configuration. Please reopen if this still fails with
test2.


Note You need to log in before you can comment on or make changes to this bug.