Bug 457875 - WinTV USB2 stick does not working
Summary: WinTV USB2 stick does not working
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 9
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-05 05:32 UTC by Azwan b. Amit
Modified: 2009-07-14 14:20 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-14 14:20:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Azwan b. Amit 2008-08-05 05:32:42 UTC
Description of problem:
When I plugged in the WinTV USB2 stick to the USB port, the system could only recognize the device but does not load the approriate driver for it. I was informed that this device (WinTV USB2 stick) is working with em28xx driver, but when I load the driver using modprobe, nothing happened. I also informed that em28xx driver is bundled together with the current kernel of fedora 9, but it doesn't automatically loaded when I plug in the wintv device.

Version-Release number of selected component (if applicable):
kernel-2.6.25.11-97.fc9.i686

How reproducible:
Everytime I plug in the device to the USB port.
  
Actual results:
Device's driver was not loaded and cannot be assigned as /dev/video0

Additional info:
Here's the dmesg output when plugging the wintv device:
usb 2-6: new high speed USB device using ehci_hcd and address 3
usb 2-6: configuration #1 chosen from 1 choice
usb 2-6: New USB device found, idVendor=2040, idProduct=650a
usb 2-6: New USB device strings: Mfr=0, Product=1, SerialNumber=2
usb 2-6: Product: WinTV USB2stk
usb 2-6: SerialNumber: 4028708785

output of dmesg when em28xx is loaded:
Linux video capture interface: v2.00
em28xx v4l2 driver version 0.1.0 loaded
usbcore: registered new interface driver em28xx

Comment 1 Chuck Ebbert 2008-08-12 00:21:17 UTC
There is no support for that exact device yet, not even in 2.6.27-rc2.

Comment 2 Bug Zapper 2009-06-10 02:22:42 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2009-07-14 14:20:12 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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