On Wed, 2008-12-17 at 12:23 +0100, Jos Hoekstra wrote: > Jarod Wilson schreef op 17-12-2008 5:42: > > On Wed, 2008-12-17 at 11:27 +1100, Greg 'groggy' Lehey wrote: > >> I have a dual USB tuner from Aldi, which they call a Fission dual high > >> definition DVB-T receiver. > > [...] > >> dmesg output (complete version is attached) > >> says: > >> > >> [ 789.696018] usb 4-3: new high speed USB device using ehci_hcd and > >> address 2 > >> [ 789.846003] usb 4-3: configuration #1 chosen from 1 choice > >> [ 790.052259] usbcore: registered new interface driver hiddev > >> [ 790.056703] input: Afa Technologies Inc. AF9035A USB Device > >> as /devices/pci0000:00/0000:00:10.3/usb4/4-3/4-3:1.1/input/input8 > >> [ 790.057902] input,hidraw0: USB HID v1.01 Keyboard [Afa Technologies > >> Inc. AF9035A USB Device] on usb-0000:00:10.3-3 > >> [ 790.058287] usbcore: registered new interface driver usbhid > >> [ 790.058511] usbhid: v2.6:USB HID core driver > >> > >> I've been following the instructions on the wiki, and I've got hold of > >> the firmware files dvb-usb-af9015.fw and xc3028-v27.fw. The former > >> doesn't get loaded; the latter gets loaded even if the stick isn't > >> present > > > >> >From your dmesg output, it appears the usbhid driver has claimed the > > device, thus the dvb driver can't grab it. If I recall correctly, usbhid > > is a module on ubuntu, so you should be able to tell it not to load > > w/some modprobe options (which I don't remember off the top of my head). > > Which would be something like this: > options usbhid quirks=15a4:1001:0x0004 > in your case. Yeah, that'd be it. Can also slap an 0x in front of the device ID components too, seems that's not a requirement though. > Not totally sure about the 0x0004 though. The 0x0004 flag is HID_QUIRK_IGNORE, which tells the usbhid driver to ignore the device. -- Jarod Wilson jarod@xxxxxxxxxxxx _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
