On Sat, 2 Jun 2007, Jimbo123 wrote: > Hi, > > Apologies for the length of the post,..
Never mind the length of the post; the length of the lines is more annoying. Could you please have your email client fold lines after about 72 columns? > I´m going down the MythTV path and purchased an ASUS M2NPV-VM board. > I already had a DVICO Dual Digital card, (PCI with 2nd tuner being > USB2). > > My initial testing was using a different motherboard and was quite > successful but am getting nowhere with this new board. > > It looks as though the USB2 drivers don´t want to have a bar of the > USB devie of this card. "have a bar of"? Is that an Australian idiom? > Here´s some details,... > At this time, with USB2 support and module ehci_hcd loaded, lsusb shows: > [==========] > Bus 001 Device 001: ID 0000:0000 > Bus 002 Device 007: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard > Receiver > Bus 002 Device 001: ID 0000:0000 > [==========] > > Now, if I disconnect my external USB cable between the DVICO and board and > then re-connect it, (with USB2 module in play), I get the following logged: > [==========] > Jun 1 00:26:24 couch kernel: [ 1328.428000] usb 1-2: new high speed USB > device using ehci_hcd and address 11 > Jun 1 00:26:24 couch kernel: [ 1328.972000] usb 1-2: new high speed USB > device using ehci_hcd and address 12 > Jun 1 00:26:25 couch kernel: [ 1329.516000] usb 1-2: new high speed USB > device using ehci_hcd and address 13 > Jun 1 00:26:25 couch kernel: [ 1330.036000] usb 1-2: new high speed USB > device using ehci_hcd and address 14 > [==========] > > Those numbers, i.e. 11 thru to 14 just go higher with every time I > disconnect/reconnect. With the re-connect I´d have expected one of > the cx88 modules to have kicked in the firmware load, which it hasn´t > done :-( Without any debugging messages it's impossible to say what's wrong. But it's clear that your device isn't enumerating properly at high speed. > Now if I disconnect the external USB cable between my DVICO card and USB > port, remove the ehci_hcd module and then re-connect it, I get the following: > [==========] > Jun 1 00:36:15 couch kernel: [ 1919.692000] usb 2-2: new full speed USB > device using ohci_hcd and address 9 > Jun 1 00:36:15 couch kernel: [ 1919.900000] usb 2-2: configuration #1 chosen > from 1 choice > Jun 1 00:36:15 couch kernel: [ 1920.036000] dvb-usb: found a 'DViCO > FusionHDTV DVB-T Dual USB' in warm state. > Jun 1 00:36:15 couch kernel: [ 1920.040000] dvb-usb: DViCO FusionHDTV DVB-T > Dual USB error while loading driver (-19) > Jun 1 00:36:15 couch kernel: [ 1920.040000] dvb_usb_cxusb: probe of 2-2:1.0 > failed with error -22 > Jun 1 00:36:15 couch kernel: [ 1920.040000] usbcore: registered new > interface driver dvb_usb_cxusb > [==========] > > The errors (-19) & (-22) I believe are due to USB being at 1.1 and not USB2 - > the following is what got logged on my initial Fedora attempt for the same > type of scenario: > [==========] > May 25 20:50:13 localhost kernel: usb 1-5: new full speed USB device using > ohci_hcd and address 3 > May 25 20:50:14 localhost kernel: usb 1-5: configuration #1 chosen from 1 > choice > May 25 20:50:14 localhost kernel: dvb-usb: found a 'DViCO FusionHDTV DVB-T > Dual USB' in cold state, will try to load a firmware > May 25 20:50:14 localhost kernel: dvb-usb: downloading firmware from file > dvb-usb-bluebird-01.fw' > May 25 20:50:16 localhost kernel: usbcore: registered new interface driver > dvb_usb_cxusb > May 25 20:50:16 localhost kernel: usb 1-5: USB disconnect, address 3 > May 25 20:50:16 localhost kernel: dvb-usb: generic DVB-USB module > successfully deinitialized and disconnected. > May 25 20:50:18 localhost kernel: usb 1-5: new full speed USB device using > ohci_hcd and address 4 > May 25 20:50:18 localhost kernel: usb 1-5: configuration #1 chosen from 1 > choice > May 25 20:50:18 localhost kernel: dvb-usb: found a 'DViCO FusionHDTV DVB-T > Dual USB' in warm state. > May 25 20:50:18 localhost kernel: **WARNING** I2C adapter driver [DViCO > FusionHDTV DVB-T Dual USB] forgot to specify physical device; fix it! > May 25 20:50:18 localhost kernel: dvb-usb: This USB2.0 device cannot be run > on a USB1.1 port. (it lacks a hardware PID filter) > May 25 20:50:18 localhost kernel: dvb-usb: DViCO FusionHDTV DVB-T Dual USB > error while loading driver (-19) > May 25 20:50:18 localhost kernel: dvb_usb_cxusb: probe of 1-5:1.0 failed with > error -22 > May 25 20:50:18 localhost kernel: usb 1-5: device_add(1-5:1.0) --> -22 > [==========] More specifically, the driver doesn't want to run at full speed. Turn on CONFIG_USB_DEBUG in your kernel and then see what shows up in the dmesg log when you load ehci-hcd. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
