Bug 123399 - USB problem with kernel 2.4.22-1.2188
Summary: USB problem with kernel 2.4.22-1.2188
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 1
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-18 03:08 UTC by Jason
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-09-29 20:26:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jason 2004-05-18 03:08:56 UTC
Description of problem:

After updating to kernel-2.4.22-1.2188.nptl my usb printer
(samsing ML-1710) stopped working. CUPS error:

Unable to open USB device "usb:/dev/usb/lp0": No such device

Switching back to kernel-2.4.22-1.2179.nptl restores proper
operation.

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

kernel-2.4.22-1.2188.nptl

How reproducible:

Very reproducible

Steps to Reproduce:
1. Run kernel-2.4.22-1.2188.nptl
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Randy Rowe 2004-05-19 14:47:24 UTC
I also lost my USB devices with 2.4.22-1.2188.npt1, Lexmark Z-25 and
Palm Pilot. Rebooting to 2179 kernel brings them back. Output of grep
usb /var/log/messages is available at
http://www.rerowe.com/usbfedora.txt where the head of the log is
2188.npt1 and the bottom of the log (devices working) is after a
reboot to 2179.

Comment 2 David Lawrence 2004-09-29 20:26:38 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/



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