Description of problem: I tried to use a Hauppauge WinTV-soloHD usb device, which didn't work although support has been present in the kernel for over a year: https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-soloHD As it turns out the usb-id isn't even present in mageia's kernel, 0x264 is missing from /usr/src/kernel-4.4.39-desktop-1.mga5/drivers/media/dvb-core/dvb-usb-ids.h If I compile kernel 4.9 from kernel.org using the original .config the usb device is working. Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. Plug in a Hauppauge WinTV soloHD 2. 3.
CC: (none) => marja11Assignee: bugsquad => kernel
(In reply to Stephan Mueller from comment #0) > Description of problem: > > I tried to use a Hauppauge WinTV-soloHD usb device, which didn't work > although support has been present in the kernel for over a year: > https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-soloHD > Yeah, but upstream media maintainer has not tagged them for stable@ so it does not get automatically backported to older maintained kernels. > As it turns out the usb-id isn't even present in mageia's kernel, 0x264 is > missing from > /usr/src/kernel-4.4.39-desktop-1.mga5/drivers/media/dvb-core/dvb-usb-ids.h > If I compile kernel 4.9 from kernel.org using the original .config the usb > device is working. I've queued the needed commit for next mageia 5 update kernel
CC: (none) => tmb
(In reply to Thomas Backlund from comment #1) > (In reply to Stephan Mueller from comment #0) > > > I've queued the needed commit for next mageia 5 update kernel This update got pushed with kernel-4.4.44, so a very long time ago :-)
Status: NEW => RESOLVEDResolution: (none) => FIXED