[feisty] DVB-T USB LiteOn Problems with recognize the frontend

Thanks for taking the time to report this bug and helping to make Ubuntu better. Which version of the kernel are you currently running? Thanks in advance.

My system is an Ubuntu Feisty Beta for x86. The kernel is updated on a v2.6.20.13. for i386.
Thanks for helping me.

Could you please also add the output of 'sudo lspci -vv' and 'sudo lspci -vvn'? Thanks again.

Here is the result of the comand, when the system does not recognize the USB key :

sudo lspci -vv
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
        Subsystem: ASUSTeK Computer Inc. Unknown device 81bf
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Capabilities: [44] HyperTransport: Slave or Primary Interface
                Command: BaseUnitID=0 UnitCnt=15 MastHost- DefDir- DUL-
                Link Control 0: CFlE+ CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 IsocEn- LSEn- ExtCTL- 64b-
                Link Config 0: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=16bit DwFcInEn- LWO=16bit DwFcOutEn-
                Link Control 1: CFlE+ CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 IsocEn+ LSEn+ ExtCTL- 64b-
                Link Config 1: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=8bit DwFcInEn- LWO=8bit DwFcOutEn-
                Revision ID: 1.03
                Link Frequency 0: 1.0GHz
                Link Error 0: <Prot- <Ovfl- <EOC- CTLTm-
                Link Frequency Capability 0: 200MHz+ 300MHz+ 400MHz+ 500MHz+ 600MHz+ 800MHz+ 1.0GHz+ 1.2GHz- 1.4GHz- 1.6GHz- Vend-
                Feature Capability: IsocFC+ LDTSTOP+ CRCTM- ECTLT- 64bA- UIDRD-
                Link Frequency 1: 800MHz
                Link Error 1: <Prot- <Ovfl- <EOC- CTLTm-
                Link Frequency Capability 1: 200MHz+ 300MHz+ 400MHz+ 500MHz+ 600MHz+ 800MHz+ 1.0GHz+ 1.2GHz- 1.4GHz- 1.6GHz- Vend-
                Error Handling: PFlE+ OFlE+ PFE- OFE- EOCFE- RFE- CRCFE- SERRFE- CF- RE- PNFE- ONFE- EOCNFE- RNFE- CRCNFE- SERRNFE-
                Prefetchable memory behind bridge Upper: 00-00
                Bus Number: 00
        Capabilities: [e0] HyperTransport: MSI Mapping

00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
        Subsystem: ASUSTeK Computer Inc. Unknown device 81bf
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
        Subsystem: ASUSTeK Computer Inc. Unknown device 81bf
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
        Subsystem: ASUSTeK Computer Inc. Unknown device 81bf
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
        Subsystem: ASUSTeK Computer Inc. Unknown device 81bf
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort...

Here is the result of the command, when the system DOES recognize the USB key :

sudo lspci -vv :

00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
 Subsystem: ASUSTeK Computer Inc. Unknown device 81bf
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0
 Capabilities: [44] HyperTransport: Slave or Primary Interface
  Command: BaseUnitID=0 UnitCnt=15 MastHost- DefDir- DUL-
  Link Control 0: CFlE+ CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 IsocEn- LSEn- ExtCTL- 64b-
  Link Config 0: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=16bit DwFcInEn- LWO=16bit DwFcOutEn-
  Link Control 1: CFlE+ CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 IsocEn+ LSEn+ ExtCTL- 64b-
  Link Config 1: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=8bit DwFcInEn- LWO=8bit DwFcOutEn-
  Revision ID: 1.03
  Link Frequency 0: 1.0GHz
  Link Error 0: <Prot- <Ovfl- <EOC- CTLTm-
  Link Frequency Capability 0: 200MHz+ 300MHz+ 400MHz+ 500MHz+ 600MHz+ 800MHz+ 1.0GHz+ 1.2GHz- 1.4GHz- 1.6GHz- Vend-
  Feature Capability: IsocFC+ LDTSTOP+ CRCTM- ECTLT- 64bA- UIDRD-
  Link Frequency 1: 800MHz
  Link Error 1: <Prot- <Ovfl- <EOC- CTLTm-
  Link Frequency Capability 1: 200MHz+ 300MHz+ 400MHz+ 500MHz+ 600MHz+ 800MHz+ 1.0GHz+ 1.2GHz- 1.4GHz- 1.6GHz- Vend-
  Error Handling: PFlE+ OFlE+ PFE- OFE- EOCFE- RFE- CRCFE- SERRFE- CF- RE- PNFE- ONFE- EOCNFE- RNFE- CRCNFE- SERRNFE-
  Prefetchable memory behind bridge Upper: 00-00
  Bus Number: 00
 Capabilities: [e0] HyperTransport: MSI Mapping

00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
 Subsystem: ASUSTeK Computer Inc. Unknown device 81bf
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
 Subsystem: ASUSTeK Computer Inc. Unknown device 81bf
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
 Subsystem: ASUSTeK Computer Inc. Unknown device 81bf
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
 Subsystem: ASUSTeK Computer Inc. Unknown device 81bf
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0

00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
 Subsystem: ASUSTeK Computer Inc. Unknown device 81bf
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <P...

The mt2060 was not loaded on a edgy with V4L modules until the (ugly) line "msleep(1000) was added in dvb-usb-dvb.c before reassign sleep and wake up fonctions.
maybe this bug is related to this

I Have the exact same problem on Ubuntu 7.04 x86.

sudo lspci -vv:

00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
        Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
        Latency: 0
        Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [e4] Vendor Specific Information
        Capabilities: [a0] AGP version 3.0
                Status: RQ=32 Iso- ArqSz=2 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
                Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>

00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02) (prog-if 00 [Normal decode])
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
        Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
        BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-

00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin A routed to IRQ 16
        Region 4: I/O ports at ef00 [size=32]

00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin B routed to IRQ 17
        Region 4: I/O ports at ef20 [size=32]

00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin C routed to IRQ 18
        Region 4: I/O ports at ef40 [size=32]

00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- ...

Hi,

At the moment you can download V4l, make a modification on dvb_usb_dvb.c
(the ugly msleep(1000)) and compile it for you kernel.

Tell me if you want more details ...

rgds,

On Wed, 2007-07-04 at 09:01 +0000, busta wrote:
> I Have the exact same problem on Ubuntu 7.04 x86.
>
> sudo lspci -vv:
>
> 00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
> Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
> Latency: 0
> Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
> Capabilities: [e4] Vendor Specific Information
> Capabilities: [a0] AGP version 3.0
> Status: RQ=32 Iso- ArqSz=2 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
> Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
>
> 00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02) (prog-if 00 [Normal decode])
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
> Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64
> Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
> Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
> BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
>
> 00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
> Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
> Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0
> Interrupt: pin A routed to IRQ 16
> Region 4: I/O ports at ef00 [size=32]
>
> 00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
> Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
> Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0
> Interrupt: pin B routed to IRQ 17
> Region 4: I/O ports at ef20 [size=32]
>
> 00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
> Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
> Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0
> Interrupt: pin C routed to IRQ 18
> Region 4: I/O ports at ef40 [size=32]
>
> 00:1d...

What do you mean by "download v4l". Do you mean that i should download the kernel source? i thought that v4l was integrated into the kernel.

First you have to install mercurial (versionning tool)

sudo apt-get install mercurial

You have to install the kernel source and headers corresponding to your
current kernel (tell me if you want more details)

.. then

hg clone http://linuxtv.org/hg/v4l-dvb

.. take some time

then edit

./v4l/dvb-usb-dvb.c to insert an msleep(1000) (approx line 177) :

int dvb_usb_adapter_frontend_init(struct dvb_usb_adapter *adap)
{
        if (adap->props.frontend_attach == NULL) {
                err("strange: '%s' #%d doesn't want to attach a
frontend.",adap->dev->desc->name, adap->id);
                return 0;
        }
        msleep(1000); <-------------------------------------HERE !!!!!
        /* re-assign sleep and wakeup functions */
        if (adap->props.frontend_attach(adap) == 0 && adap->fe != NULL)
{
                adap->fe_init =

save, make, sudo make install (and reboot)

It should work, it works fine for me.

On Fri, 2007-07-06 at 08:21 +0000, busta wrote:
> What do you mean by "download v4l". Do you mean that i should download
> the kernel source? i thought that v4l was integrated into the kernel.
>

I may work too by modifying the dvb-usb-dvb.c of the v4l integrated into
the kernel. It didn't work for me (i didn't search why) .. However it
may work for you.

On Fri, 2007-07-06 at 08:21 +0000, busta wrote:
> What do you mean by "download v4l". Do you mean that i should download
> the kernel source? i thought that v4l was integrated into the kernel.
>

I have a similar problem with 7.04 (2.6.20-16-generic) and an Intuix S-810 Lite-On based (ID 04ca:f001 Lite-On Technology Corp.) dvb-t stick, as the frontend never gets loaded:

[ 24.080000] dvb-usb: found a 'LITE-ON USB2.0 DVB-T Tuner' in cold state, will try to load a firmware
[ 24.412000] dvb-usb: downloading firmware from file 'dvb-usb-dibusb-6.0.0.8.fw'
[ 24.500000] usbcore: registered new interface driver dvb_usb_dibusb_mc
[ 24.620000] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
[ 26.512000] dvb-usb: found a 'LITE-ON USB2.0 DVB-T Tuner' in warm state.
[ 26.512000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 26.516000] dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner'
[ 26.516000] dvb-usb: schedule remote query interval to 150 msecs.
[ 26.516000] dvb-usb: LITE-ON USB2.0 DVB-T Tuner successfully initialized and connected.

Here are two others:
http://www.linuxtv.org/pipermail/linux-dvb/2007-February/015719.html
http://www.linuxtv.org/pipermail/linux-dvb/2007-July/018883.html

However, the 'solution' referred to, on
http://linuxtv.org/hg/~mkrufky/megasky/
has been integrated into the drivers.

So I tried Crevany's suggestions, which can be found on
http://www.linuxtv.org/wiki/index.php/How_to_install_DVB_device_drivers
but compiling failed:

CC [M] /home/user/v4l-dvb/v4l/radio-gemtek.o
  CC [M] /home/user/v4l-dvb/v4l/radio-gemtek-pci.o
/home/user/v4l-dvb/v4l/radio-gemtek-pci.c: In function 'gemtek_pci_probe':
/home/user/v4l-dvb/v4l/radio-gemtek-pci.c:437: error: 'struct pci_dev' has no member named 'revision'
make[3]: *** [/home/user/v4l-dvb/v4l/radio-gemtek-pci.o] Error 1
make[2]: *** [_module_/home/user/v4l-dvb/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.20-16-generic'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/user/v4l-dvb/v4l'
make: *** [all] Error 2

Might this be a hardware issue? How to find out?

The solution?

"it's neccessary (even in current sources) to modify frontends/dib3000mc.c
remove
...
insert
...

http://www.linuxforen.de/forums/showthread.php?p=1553857

Okay, after commenting out a line with /radio in one of the Makefiles in v4l-dvb/v4l it compiled successfully with the above changes on my Ubuntu 7.04 system. The change to the Makefile was necessary because of some missing method in one of the radio adapter's code. Advanced users probably will figure things like this out by themselves, but as a beginner, it took me a day to get to this point.

Thanks.

Hi,

I've got the same kernel version as you. Try with other v4l version.

Here is the command line to get it :

 hg clone http://mcentral.de/hg/~mrec/v4l-dvb-experimental

On Thu, 2007-07-19 at 20:52 +0000, isayhelloyousaygoodbye wrote:
> I have a similar problem with 7.04 (2.6.20-16-generic) and an Intuix
> S-810 Lite-On based (ID 04ca:f001 Lite-On Technology Corp.) dvb-t stick,
> as the frontend never gets loaded:
>
> [ 24.080000] dvb-usb: found a 'LITE-ON USB2.0 DVB-T Tuner' in cold state, will try to load a firmware
> [ 24.412000] dvb-usb: downloading firmware from file 'dvb-usb-dibusb-6.0.0.8.fw'
> [ 24.500000] usbcore: registered new interface driver dvb_usb_dibusb_mc
> [ 24.620000] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
> [ 26.512000] dvb-usb: found a 'LITE-ON USB2.0 DVB-T Tuner' in warm state.
> [ 26.512000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
> [ 26.516000] dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner'
> [ 26.516000] dvb-usb: schedule remote query interval to 150 msecs.
> [ 26.516000] dvb-usb: LITE-ON USB2.0 DVB-T Tuner successfully initialized and connected.
>
> Here are two others:
> http://www.linuxtv.org/pipermail/linux-dvb/2007-February/015719.html
> http://www.linuxtv.org/pipermail/linux-dvb/2007-July/018883.html
>
> However, the 'solution' referred to, on
> http://linuxtv.org/hg/~mkrufky/megasky/
> has been integrated into the drivers.
>
> So I tried Crevany's suggestions, which can be found on
> http://www.linuxtv.org/wiki/index.php/How_to_install_DVB_device_drivers
> but compiling failed:
>
> CC [M] /home/user/v4l-dvb/v4l/radio-gemtek.o
> CC [M] /home/user/v4l-dvb/v4l/radio-gemtek-pci.o
> /home/user/v4l-dvb/v4l/radio-gemtek-pci.c: In function 'gemtek_pci_probe':
> /home/user/v4l-dvb/v4l/radio-gemtek-pci.c:437: error: 'struct pci_dev' has no member named 'revision'
> make[3]: *** [/home/user/v4l-dvb/v4l/radio-gemtek-pci.o] Error 1
> make[2]: *** [_module_/home/user/v4l-dvb/v4l] Error 2
> make[2]: Leaving directory `/usr/src/linux-headers-2.6.20-16-generic'
> make[1]: *** [default] Error 2
> make[1]: Leaving directory `/home/user/v4l-dvb/v4l'
> make: *** [all] Error 2
>
> Might this be a hardware issue? How to find out?
>

Same problem in gutsy:

Linux 2.6.22-10-generic:

[ 9641.260114] usb 5-1.4: new high speed USB device using ehci_hcd and address 6
[ 9641.352227] usb 5-1.4: configuration #1 chosen from 1 choice
[ 9641.472894] dvb-usb: found a 'LITE-ON USB2.0 DVB-T Tuner' in cold state, will try to load a firmware
[ 9641.505369] dvb-usb: downloading firmware from file 'dvb-usb-dibusb-6.0.0.8.fw'
[ 9641.558190] usbcore: registered new interface driver dvb_usb_dibusb_mc
[ 9641.573235] usb 5-1.4: USB disconnect, address 6
[ 9641.573298] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
[ 9643.302636] usb 5-1.4: new high speed USB device using ehci_hcd and address 7
[ 9643.418809] usb 5-1.4: configuration #1 chosen from 1 choice
[ 9643.419275] dvb-usb: found a 'LITE-ON USB2.0 DVB-T Tuner' in warm state.
[ 9643.419476] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 9643.423449] DVB: registering new adapter (LITE-ON USB2.0 DVB-T Tuner).
[ 9643.424460] dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner'
[ 9643.425265] input: IR-receiver inside an USB DVB receiver as /class/input/input11
[ 9643.425305] dvb-usb: schedule remote query interval to 150 msecs.
[ 9643.425312] dvb-usb: LITE-ON USB2.0 DVB-T Tuner successfully initialized and connected.

I actually think this problem is an USB-problem.

My Liteon-stick had the same problems when used with my notebook (Fujitsu Siemens Amilo Si 1520). The trick with plugging in the stick and then do a restart worked for me so I did it this way (recompiling V4L broke my webcam).

But on my older desktop the stick works just fine and stable without any restart.

I tried the "solution" to change the V4L-source as well on my notebook. When looking at the device and vendor IDs I recognized that they always changed. So it didn't worked for me to replace them in the source I just de-activated the "exception".

Since changing the device and vendor ID doesn't seem to be a normal behavior for me (and it doesn't happen on my desktop) I think that there is a problem somewhere in the "USB-driver" (or whatever it is called).

Does anyone have an idea why this could happen?

I forget to mention that the IDs changed after I unplugged and replugged the stick.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

On my new notebook and with Ubuntu 8.10 this seems to be fixed.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Thanks, will mark this Fix Released for Intrepid. @zebulon25000, since you are the original bug reporter, if this is not resolved for you with the Intrepid Ibex 8.10 release feel free to reopen by setting the status back to "New". Thanks.