Artec T1 AN2235 DVB USB is not detected by Jaunty Kernel

Bug #367217 reported by Obrouni on 2009-04-26
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-ports-meta (Ubuntu)
Undecided
Unassigned

Bug Description

It appears that my Artec T1 AN2235 DVB USB device is no longer detected by the Jaunty Kernel (2.6-28.11) . Plugging the device into a machine running Hardy, the device is detected.

lsusb:-
Bus 004 Device 005: ID 0547:2235 Anchor Chips, Inc. AN2235 EZUSB-FX Microcontroller

I believe this has something to do with the device having a faulty usb device id as the dmesg output from my Jaunty machine:-

[ 1913.364014] usb 4-2: new full speed USB device using uhci_hcd and address 4
[ 1913.510324] usb 4-2: configuration #1 chosen from 1 choice

Compares to my Hardy machine (Yes I know I am missing the firmware, but thats easily fixed):-

[ 241.999804] usb 1-2: new full speed USB device using ohci_hcd and address 2
[ 242.191982] usb 1-2: configuration #1 chosen from 1 choice
[ 243.390354] dvb-usb: found a 'Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)' in cold state, will try to load a firmware
[ 243.497369] dvb-usb: did not find the firmware file. (dvb-usb-dibusb-an2235-01.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2)
[ 243.497424] dvb_usb_dibusb_mb: probe of 1-2:1.0 failed with error -22
[ 243.497485] usbcore: registered new interface driver dvb_usb_dibusb_mb

The key point i think is this line:-

found a 'Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)

Has something changed in the kernel to not enable the faulty USB IDs config option, or is it something to do with this patch:-

http://patchwork.kernel.org/patch/3207/

Many Thanks

Alexis (alxju) wrote :

I'm also affected by this problem.

with hardy dvbt worked fine with dvb-usb-dibusb-an2235-01.fw

Now, just upgraded to jaunty, nothing happens, and lsusb give me:

Bus 002 Device 005: ID 0547:2235 Anchor Chips, Inc. AN2235 EZUSB-FX Microcontroller

Cedric (ubuntuone-xfou) wrote :

Also affected with this problem.

The problem is due to the linux building config file (/boot/config-2.6.28-15-generic) in which the line

# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set

Would it be possible to reenable this build option for the kernel as it was in hardy ?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers