dvb-usb: bulk message failed: -90 (1/0)<br>dvb-usb: bulk message failed: -90 (1/0)<br>dvb-usb: bulk message failed: -90 (1/0)<br>dvb-usb: bulk message failed: -90 (1/0)<br>dvb-usb: bulk message failed: -90 (1/0)<br>dvb-usb: bulk message failed: -90 (1/0)
<br>dvb-usb: bulk message failed: -90 (1/0)<br>dvb-usb: bulk message failed: -90 (1/0)<br>dvb-usb: bulk message failed: -90 (1/0)<br>..<br>..<br><br>/var/log/messages reports the following:<br><br>Apr&nbsp; 3 15:54:25 magpie kernel: usb 3-1: new full speed USB device using uhci_hcd and address 3
<br>Apr&nbsp; 3 15:54:25 magpie kernel: dvb-usb: found a 'Artec T1 USB1.1 TVBOX with AN2235' in warm state.<br>Apr&nbsp; 3 15:54:25 magpie kernel: dvb-usb: will use the device's hardware PID filter (table count: 16).<br>Apr&nbsp; 3 15:54:25 magpie kernel: dibusb: this device has the Panasonic ENV77H11D5 onboard.
<br>Apr&nbsp; 3 15:54:25 magpie kernel: dvb-usb: schedule remote query interval to 150 msecs.<br>Apr&nbsp; 3 15:54:25 magpie kernel: dvb-usb: Artec T1 USB1.1 TVBOX with AN2235 successfully initialized and connected.<br><br>This
seems to suggest that everything should be working OK, and yet the LEDs
do not come on (indicating that the firmware has not been correctly
loaded), and no /dev/dvb.frontend0 device is created by udev
(/dev/dvb0.demux0, /dev/dvb0.dvr0 and /dev/dvb0/net0 are created at
this point) .
<br><br>I have tried many things including uncommenting the &quot;#define DVB_USB_DIBUSB_MB_FAULTY_USB_IDs&quot; line in dvb-kernel/linux/drivers/media/dvb/dvb-usb/dibusb-mb.c, as described in the Artec T1 howto, here -
<a style="border-bottom-style: groove;" href="http://linuxtv.org/wiki/index.php/Artec_T1_USB_TV_Box" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://linuxtv.org/wiki/index.php/Artec_T1_USB_TV_Box</a>, without any luck. <br><br>I
have also tried (just to make sure that the hardware actually works at
all) running it under windows, and frustratingly it fires up first time
without any problems :(. However, one thing that I did notice from this
is that the windows drivers report the product ID to be 8108 rather
than 8107 (as reported by lsusb under Linux). I'm not sure if this is
important, but thought I'd mention it, just in case.
<br><br>I would be very grateful for any suggestions that you have,
even if it is just to say that this type of T1 isn't currently
supported, as at least then I can move on, or buy some new hardware. <br><br>Many thanks<br></div><span class="sg">
<br>Richard </span>