First Last Prev Next    This bug is not in your last search results.
Bug 449243 - Logitech MX1000 USB Keyboard Not Working
Logitech MX1000 USB Keyboard Not Working
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
9
x86_64 Linux
low Severity urgent
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2008-05-31 16:58 EDT by Daniel Qarras
Modified: 2008-08-18 11:24 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-08-18 11:24:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Daniel Qarras 2008-05-31 16:58:13 EDT 
Description of problem:
When trying to install Fedora 9 on an x86_64 with Logitech MX1000 Wireless USB
keyboard, the keyboard works all ok under BIOS and F9 boot up menu but when the
kernel has booted and the installer asks whether to check installation media,
the keyboard is not working. As I have no other keyboard I can't provide any
additional information. I tested with boot parameters "acpi=off", "noapic", and
"acpi=off noapic" but they just hang the kernel in early boot.

Version-Release number of selected component (if applicable):
Fedora 9

How reproducible:
Always

Steps to Reproduce:
1. Try to install F9 on an x86_64 with Logitech MX1000
  
Actual results:
No keyboard

Expected results:
Keyboard working

Additional info:
Comment 1 Daniel Qarras 2008-08-18 11:23:27 EDT 
It seems that this might have been caused by a hardware problem, even Vista has some problems. I will close this as further investigation is not possible any more.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.