old it9135 works good with my usb dvbt stick. after replace with it913x from update, dvbt is not recognised. I'm using latest pli and et9000. is there any chance to compile old it9135 driver in new update?
I so this here
2) dvb-usb-it913x-patch-collection.patch again is a collection of recent updates from the media_build tree; in fact, the old it9135 driver we had in the previous kernels supported more devices than the it913x driver included in kernel 3.2.2, so I updated this driver to the latest version which supports even more devices and seems to be a "final" version;
I have new firmware for this chipset but still not working
new it913x drivers not working in new kernel with et9000
Started by halflife, 13 Feb 2012 14:53
101 replies to this topic
Re: new it913x drivers not working in new kernel with et9000 #2
-
- Senior Member
- 296 posts
+31
Good
Posted 13 February 2012 - 15:23
Start posting a dmesg log and a lsusb log.
Re: new it913x drivers not working in new kernel with et9000 #3
-
- Senior Member
- 296 posts
+31
Good
Posted 13 February 2012 - 15:50
Probably I found the problem; try with this:
Pieterg, in file openembedded/conf/machine/etxx00 you should replace the line:
with the new line:
Also, you can now create a meta-package for it913x devices including the 3 firmwares in attachment.
echo dvb-usb-it913x > /etc/modutils/dvb-usb-it913x update-modules reboot
Pieterg, in file openembedded/conf/machine/etxx00 you should replace the line:
module_autoload_dvb-usb-it9135 = "dvb-usb-it9135"
with the new line:
module_autoload_dvb-usb-it913x = "dvb-usb-it913x"
Also, you can now create a meta-package for it913x devices including the 3 firmwares in attachment.
Attached Files
-
it913x-firmwares.tar.gz 17.63KB
150 downloads
Re: new it913x drivers not working in new kernel with et9000 #4
-
- PLi® Core member
- 32,766 posts
+245
Excellent
Posted 13 February 2012 - 16:27
the firmwares are waiting to be pulled, I'd rather not put data files in the oe repository.
I'll fix the autoload entry.
I'll fix the autoload entry.
Re: new it913x drivers not working in new kernel with et9000 #5
-
- Senior Member
- 296 posts
+31
Good
Posted 13 February 2012 - 16:40
Thanks.
Re: new it913x drivers not working in new kernel with et9000 #6
-
- Senior Member
- 59 posts
0
Neutral
Posted 13 February 2012 - 20:18
after this,
echo dvb-usb-it913x > /etc/modutils/dvb-usb-it913x
update-modules
reboot
everything works fine, thx!
here is the log before that:
pli log.rar 5.26KB
14 downloads
and here is after
pli log ok.rar 5.2KB
13 downloads
echo dvb-usb-it913x > /etc/modutils/dvb-usb-it913x
update-modules
reboot
everything works fine, thx!
here is the log before that:
pli log.rar 5.26KB
14 downloadsand here is after
pli log ok.rar 5.2KB
13 downloads
Re: new it913x drivers not working in new kernel with et9000 #7
-
- Senior Member
- 59 posts
0
Neutral
Posted 13 February 2012 - 20:56
and btw, snr/agc now looks good on dvbt usb!
Re: new it913x drivers not working in new kernel with et9000 #8
-
- Senior Member
- 296 posts
+31
Good
Posted 13 February 2012 - 21:17
Nice to know, thanks for the report.
BTW, I see from your log that the PID filter of the it9135 chipset is enabled by default.
I don't know if this can be a limit (for example, in case you want to record and watch 2 channel from the same multiplex at the same time).
If you notice this kind of problems, run:
to disable the hardware PID filter.
BTW, I see from your log that the PID filter of the it9135 chipset is enabled by default.
I don't know if this can be a limit (for example, in case you want to record and watch 2 channel from the same multiplex at the same time).
If you notice this kind of problems, run:
echo dvb-usb-it913x pid=1 > /etc/modutils/dvb-usb-it913x update-modules reboot
to disable the hardware PID filter.
Edited by Gennar1, 13 February 2012 - 21:17.
Re: new it913x drivers not working in new kernel with et9000 #9
-
- Senior Member
- 59 posts
0
Neutral
Posted 13 February 2012 - 21:46
just testing one ch rec, 2nd watching, seems good without disabling hw pid filter
Re: new it913x drivers not working in new kernel with et9000 #10
-
- Senior Member
- 59 posts
0
Neutral
Posted 6 March 2012 - 11:38
something is realy wrong with new drivers. it just stop working after hour, maybe two. only reboot helps. I dont do anything, just watching, and ops, black screen!
here is the dmesg:
here is the dmesg:
Attached Files
-
dvbt crash.txt 13.81KB
11 downloads
Re: new it913x drivers not working in new kernel with et9000 #11
-
- Senior Member
- 296 posts
+31
Good
Posted 6 March 2012 - 16:24
Looks like a USB issue:
I recently updated the IT913x patch with a few changes from the official driver mantainer.
If you had no problem with the previous version of the driver, we can revert the latest changes and wait for a fix from the mantainer.
ehci-brcm ehci-brcm.0: force halt; handshake b0480314 00004000 00000000 -> -145 ehci-brcm ehci-brcm.0: HC died; cleaning up usb 1-2: USB disconnect, device number 3 dvb-usb: error while stopping stream.
I recently updated the IT913x patch with a few changes from the official driver mantainer.
If you had no problem with the previous version of the driver, we can revert the latest changes and wait for a fix from the mantainer.
Re: new it913x drivers not working in new kernel with et9000 #12
-
- Senior Member
- 296 posts
+31
Good
Posted 7 March 2012 - 12:31
Looking at the description of the new patches, I found this comment from the driver maintainer:
This description fits perfectly your problem, so probably you are experiencing the same issue.
The fix is already included in the current OpenPli kernel, but if you still experience the problem you can disable the PID filtering completely following this instructions:
In the next kernel update I will disable the hardware PID filter by default, as we don't need it in Enigma2.
Some virtual I2C commands are missed along some PID filtering
commands resulting complete stall of driver.
This description fits perfectly your problem, so probably you are experiencing the same issue.
The fix is already included in the current OpenPli kernel, but if you still experience the problem you can disable the PID filtering completely following this instructions:
echo dvb-usb-it913x pid=1 > /etc/modutils/dvb-usb-it913x update-modules reboot
In the next kernel update I will disable the hardware PID filter by default, as we don't need it in Enigma2.
Re: new it913x drivers not working in new kernel with et9000 #13
-
- Senior Member
- 59 posts
0
Neutral
Posted 10 March 2012 - 10:57
just to confirm after few days of testing, drivers works well, thx @gennar1
Re: new it913x drivers not working in new kernel with et9000 #14
-
- Member
- 32 posts
0
Neutral
Posted 26 April 2012 - 19:48
These works on the new kernel 3.3?
For me the 3.3 detects the tuner, but is not visible in E2.
I have to remove the usb tuner and start again e2 / init 3 / and re-insert the USB tuner
A friend wrote that he had the same problem on kernel 3.3
For me the 3.3 detects the tuner, but is not visible in E2.
dmesg ... DVB: registering new adapter (dvb0) DVB: registering adapter 0 frontend 0 (DVB-S2)... DVB: registering adapter 0 frontend 1 (DVB-S2)... input: front panel as /devices/virtual/input/input2 usbcore: registered new interface driver ath9k_htc usbcore: registered new interface driver carl9170 it913x: Chip Version=02 Chip Type=9135 it913x: Dual mode=0 Tuner Type=38 it913x: Unknown tuner ID applying default 0x60 dvb-usb: found a 'ITE 9135 Generic' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-it9135-02.fw' it913x: FRM Starting Firmware Download it913x: FRM Firmware Download Completed - Resetting Device it913x: Chip Version=02 Chip Type=9135 it913x: Firmware Version 52887808 dvb-usb: found a 'ITE 9135 Generic' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (ITE 9135 Generic) it913x-fe: ADF table value :00 it913x-fe: Crystal Frequency :12000000 Adc Frequency :20250000 ADC X2: 01 it913x-fe: Tuner LNA type :60 DVB: registering adapter 1 frontend 0 (ITE 9135 Generic_1)... Registered IR keymap rc-it913x-v1 input: IR-receiver inside an USB DVB receiver as /devices/platform/ehci-brcm.1/usb2/2-1/2-1.1/rc/rc0/input3 rc0: IR-receiver inside an USB DVB receiver as /devices/platform/ehci-brcm.1/usb2/2-1/2-1.1/rc/rc0 dvb-usb: schedule remote query interval to 250 msecs. dvb-usb: ITE 9135 Generic successfully initialized and connected. it913x: DEV registering device driver usbcore: registered new interface driver it913x NET: Registered protocol family 10 rtw driver version=v3.3.0_2971.20111128 usbcore: registered new interface driver rtl8192cu r8712u: module is from the staging directory, the quality is unknown, you have been warned. usbcore: registered new interface driver r8712u usbcore: registered new interface driver rt2500usb usbcore: registered new interface driver rt2800usb usbcore: registered new interface driver rt73usb usbcore: registered new interface driver rtl8187 usbcore: registered new interface driver usbserial USB Serial support registered for generic usbcore: registered new interface driver usbserial_generic usbserial: USB Serial Driver core usbcore: registered new interface driver zd1211rw Console: switching to colour dummy device 80x25 DVB: registering adapter 0 frontend 2 (vtuner)... eth0: no IPv6 routers present DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)...and decoder crashes, the e2 will not start ...
I have to remove the usb tuner and start again e2 / init 3 / and re-insert the USB tuner
DVB: registering adapter 0 frontend 2 (vtuner)... dvb-usb: error -71 while querying for an remote control event. usb 2-1.1: USB disconnect, device number 3 dvb-usb: ITE 9135 Generic successfully deinitialized and disconnected. usb 2-1.1: new high-speed USB device number 5 using ehci-brcm it913x: Chip Version=02 Chip Type=9135 it913x: Dual mode=0 Tuner Type=38 it913x: Unknown tuner ID applying default 0x60 dvb-usb: found a 'ITE 9135 Generic' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-it9135-02.fw' it913x: FRM Starting Firmware Download it913x: FRM Firmware Download Completed - Resetting Device it913x: Chip Version=02 Chip Type=9135 it913x: Firmware Version 52887808 dvb-usb: found a 'ITE 9135 Generic' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (ITE 9135 Generic) it913x-fe: ADF table value :00 it913x-fe: Crystal Frequency :12000000 Adc Frequency :20250000 ADC X2: 01 it913x-fe: Tuner LNA type :60 DVB: registering adapter 1 frontend 0 (ITE 9135 Generic_1)... Registered IR keymap rc-it913x-v1 input: IR-receiver inside an USB DVB receiver as /devices/platform/ehci-brcm.1/usb2/2-1/2-1.1/rc/rc1/input4 rc1: IR-receiver inside an USB DVB receiver as /devices/platform/ehci-brcm.1/usb2/2-1/2-1.1/rc/rc1 dvb-usb: schedule remote query interval to 250 msecs. dvb-usb: ITE 9135 Generic successfully initialized and connected. it913x: DEV registering device driverusb tuner but you can not see the options of heads in e2.
A friend wrote that he had the same problem on kernel 3.3
Confirm for me the kernel version 3.2 CABLETECH URZ0085 tuner on a chip 9135 worked without a problem, after updating to 3.3 crashes on boot
Re: new it913x drivers not working in new kernel with et9000 #15
-
- Senior Member
- 296 posts
+31
Good
Posted 27 April 2012 - 11:48
Looks like the device is detected multiple times and connected multiple times to the vtuner:
Maybe it's a bug in the new Enigma2 code replacing the old USBtunerhelper?
But it's weird, because it works perfeclty with a lot of devices.
DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)... DVB: registering adapter 0 frontend 2 (vtuner)...
Maybe it's a bug in the new Enigma2 code replacing the old USBtunerhelper?
But it's weird, because it works perfeclty with a lot of devices.
Re: new it913x drivers not working in new kernel with et9000 #16
-
- Member
- 32 posts
0
Neutral
Posted 27 April 2012 - 17:17
At startup, the enigma spinner appears several times and then hangs the tuner remains a communication from the console.
Re: new it913x drivers not working in new kernel with et9000 #17
-
- Senior Member
- 59 posts
0
Neutral
Posted 27 April 2012 - 18:14
yes, kernel 3.3 has a problem with it913x. here is mine case: everything works fine few hours, then I get error: check tuner configuration, and of course, black screen on dvbt channels. only reboot helps.
OpenEmbedded Linux et9x00
openpli 2.1 et9x00
et9x00 login: root
root@et9x00:~# dmesg
ng disabled
serial8250.0: ttyS0 at MMIO 0x10400b00 (irq = 22) is a 16550A
serial8250.0: ttyS1 at MMIO 0x10400b40 (irq = 66) is a 16550A
serial8250.0: ttyS2 at MMIO 0x10400b80 (irq = 67) is a 16550A
loop: module loaded
sata_brcmstb 0000:01:00.0: version 4.0
brcm-pm: enabling sata clocks
PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
sata_brcmstb 0000:01:00.0: setting latency timer to 64
scsi0 : sata_brcmstb
scsi1 : sata_brcmstb
ata1: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510000 irq 42
ata2: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510100 irq 42
Broadcom STB NAND controller (BrcmNand Controller)
bcmemac: Broadcom STB 10/100 EMAC driver v3.0
bcmemac: registered interface #0 at 0x10080000 as 'eth0' (00:16:b4:02:fb:8b)
bcmemac: not registering interface #1 at 0x10090000 (no PHY detected)
usbcore: registered new interface driver zd1201
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
brcm-pm: enabling usb clocks
ehci-brcm ehci-brcm.0: Broadcom STB EHCI
ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
ehci-brcm ehci-brcm.0: irq 62, io mem 0x10480300
ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ehci-brcm ehci-brcm.1: Broadcom STB EHCI
ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
ehci-brcm ehci-brcm.1: irq 57, io mem 0x10480500
ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-brcm ohci-brcm.0: Broadcom STB OHCI
ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 3
ohci-brcm ohci-brcm.0: irq 63, io mem 0x10480400
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ohci-brcm ohci-brcm.1: Broadcom STB OHCI
ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 4
ohci-brcm ohci-brcm.1: irq 64, io mem 0x10480600
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
lirc_dev: IR Remote Control driver registered, major 254
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR RC5 (streamzap) protocol handler initialized
IR SANYO protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR LIRC bridge handler initialized
usbcore: registered new interface driver btusb
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
EBI CS1: setting up NAND flash (primary)
mtd->oobsize=0, mtd->eccOobSize=0
NAND_CS_NAND_XOR=00000000
B4: NandSelect=50000200, nandConfig=15142200, chipSelect=1
brcmnand_read_id: CS1: dev_id=ecf10095
After: NandSelect=50000200, nandConfig=15142200
Block size=00020000, erase shift=17
NAND Config: Reg=15142200, chipSize=128 MB, blockSize=128K, erase_shift=11
busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
timing1 not adjusted: 5363444f
timing2 not adjusted: 00000fc6
eccLevel=15, 1Ksector=0, oob=16
nbrBitsPerCell=2, cellinfo=0, chip->cellinfo=00000000
<--brcmnand_set_acccontrol: acc b4: d7ff1010, after: d7ff1010
BrcmNAND mfg ec f1 Samsung K9F1G08U0A 128MB on CS1
Found NAND on CS1: ACC=d7ff1010, cfg=15142200, flashId=ecf10095, tim1=5363444f, tim2=00000fc6
BrcmNAND version = 0x0302 128MB @00000000
B4: NandSelect=50000200, nandConfig=15142200, chipSelect=1
brcmnand_read_id: CS1: dev_id=ecf10095
After: NandSelect=50000200, nandConfig=15142200
Found NAND flash on Chip Select 1, chipSize=128MB, usable size=128MB, base=0
brcmnand_scan: B4 nand_select = 50000200
brcmnand_scan: After nand_select = 50000200
page_shift=11, bbt_erase_shift=17, chip_shift=27, phys_erase_shift=17
Brcm NAND controller version = 3.2 NAND flash size 128MB @18000000
ECC layout=brcmnand_oob_bch4_4k
brcmnand_scan: mtd->oobsize=64
brcmnand_scan: oobavail=50, eccsize=512, writesize=2048
brcmnand_scan, eccsize=512, writesize=2048, eccsteps=4, ecclevel=15, eccbytes=3
-->brcmnand_default_bbt
brcmnand_default_bbt: bbt_td = bbt_main_descr
Bad block table Bbt0 found at page 0000ffc0, version 0x01 for chip on CS1
Bad block table 1tbB found at page 0000ff80, version 0x01 for chip on CS1
nand_read_bbt: Bad block at 0x05a80000
Adjust partition complete size from entire device to 7f00000 to avoid overlap with BBT reserved space
Adjust partition rootfs size from entire device to 7900000 to avoid overlap with BBT reserved space
Creating 3 MTD partitions on "brcmnand.0":
0x000000000000-0x000007f00000 : "complete"
0x000000000000-0x000000600000 : "kernel"
0x000000600000-0x000007f00000 : "rootfs"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-8: SAMSUNG HD155UI, 1AQ10001, max UDMA/133
ata1.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 0/32)
usb 1-1: new high-speed USB device number 2 using ehci-brcm
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD155UI 1AQ1 PQ: 0 ANSI: 5
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
input: ITE Technologies, Inc. DVB-T TV Stick as /devices/platform/ehci-brcm.0/usb1/1-1/1-1:1.1/input/input0
generic-usb 0003:048D:9006.0001: input,hidraw0: USB HID v1.01 Keyboard [ITE Technologies, Inc. DVB-T TV Stick] on usb-ehci_hcd-1/input1
ata2: SATA link down (SStatus 4 SControl 300)
usb 3-2: new full-speed USB device number 2 using ohci-brcm
hub 3-2:1.0: USB hub found
hub 3-2:1.0: 4 ports detected
usb 2-1: new high-speed USB device number 2 using ehci-brcm
UBI: max. sequence number: 4
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
UBI: attached mtd2 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 121 MiB
UBI: number of good PEBs: 967
UBI: number of bad PEBs: 1
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 967
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 1/0
UBI: image sequence number: 1395567592
UBI: background thread "ubi_bgt0d" started, PID 40
Warning: unable to open an initial console.
UBIFS: recovery needed
usb 3-2.1: new low-speed USB device number 3 using ohci-brcm
input: Riitek Micro Keyboard as /devices/platform/ohci-brcm.0/usb3/3-2/3-2.1/3-2.1:1.0/input/input1
generic-usb 0003:1997:0409.0002: input,hidraw1: USB HID v1.11 Keyboard [Riitek Micro Keyboard] on usb-ohci_hcd-2.1/input0
input: Riitek Micro Keyboard as /devices/platform/ohci-brcm.0/usb3/3-2/3-2.1/3-2.1:1.1/input/input2
generic-usb 0003:1997:0409.0003: input,hidraw2: USB HID v1.11 Mouse [Riitek Micro Keyboard] on usb-ohci_hcd-2.1/input1
usb 3-2.4: new full-speed USB device number 4 using ohci-brcm
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 119738368 bytes (116932 KiB, 114 MiB, 943 LEBs)
UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:12.
Freeing unused kernel memory: 256k freed
usb 3-2.4: not running at top speed; connect to a high speed hub
scsi2 : usb-storage 3-2.4:1.0
usb 2-1.2: new full-speed USB device number 3 using ehci-brcm
scsi 2:0:0:0: Direct-Access Corsair Voyager 1100 PQ: 0 ANSI: 0 CCS
sd 2:0:0:0: [sdb] 7831552 512-byte logical blocks: (4.00 GB/3.73 GiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Attached SCSI removable disk
EXT4-fs (sda1): recovery complete
EXT4-fs (sda1): mounted filesystem with writeback data mode. Opts: (null)
usbcore: registered new interface driver tpm
modloader: module license 'PROPRIETARY' taints kernel.
Disabling lock debugging due to kernel taint
dvb: module_layout: kernel tainted.
Console: switching to colour dummy device 80x25
Console: switching to colour frame buffer device 160x45
input: dreambox remote control (native) as /devices/virtual/input/input3
input: dreambox advanced remote control (native) as /devices/virtual/input/input4
DVB: registering new adapter (dvb0)
DVB: registering adapter 0 frontend 0 (DVB-S2)...
DVB: registering adapter 0 frontend 1 (DVB-S2)...
input: front panel as /devices/virtual/input/input5
usbcore: registered new interface driver ath9k_htc
usbcore: registered new interface driver carl9170
it913x: Chip Version=01 Chip Type=9135
it913x: Remote HID mode NOT SUPPORTED
it913x: Dual mode=0 Tuner Type=0
dvb-usb: found a 'ITE 9135(9006) Generic' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-it9135-01.fw'
it913x: FRM Starting Firmware Download
it913x: FRM Firmware Download Completed - Resetting Device
it913x: Chip Version=01 Chip Type=9135
it913x: Firmware Version 204869120
dvb-usb: found a 'ITE 9135(9006) Generic' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (ITE 9135(9006) Generic)
it913x-fe: ADF table value :00
it913x-fe: Crystal Frequency :12000000 Adc Frequency :20250000 ADC X2: 01
it913x-fe: Tuner LNA type :38
DVB: registering adapter 1 frontend 0 (ITE 9135(9006) Generic_1)...
dvb-usb: ITE 9135(9006) Generic successfully initialized and connected.
it913x: DEV registering device driver
usbcore: registered new interface driver it913x
NET: Registered protocol family 10
rtw driver version=v3.3.0_2971.20111128
usbcore: registered new interface driver rtl8192cu
r8712u: module is from the staging directory, the quality is unknown, you have been warned.
usbcore: registered new interface driver r8712u
usbcore: registered new interface driver rt2500usb
usbcore: registered new interface driver rt2800usb
usbcore: registered new interface driver rt73usb
usbcore: registered new interface driver rtl8187
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
usbcore: registered new interface driver zd1211rw
Console: switching to colour dummy device 80x25
DVB: registering adapter 0 frontend 2 (vtuner)...
ehci-brcm ehci-brcm.0: force halt; handshake b0480314 00004000 00000000 -> -145
ehci-brcm ehci-brcm.0: HC died; cleaning up
usb 1-1: USB disconnect, device number 2
out of order segment: rcv_next 2D591876 seq 2D592252 - 2D59229D
ofo requeuing : rcv_next 2D592252 seq 2D592252 - 2D59229D
out of order segment: rcv_next EF210FC7 seq EF211283 - EF2112BD
ofo requeuing : rcv_next EF211283 seq EF211283 - EF2112BD
out of order segment: rcv_next 7FE86447 seq 7FE868BD - 7FE86E5D
out of order segment: rcv_next 7FE86447 seq 7FE86E5D - 7FE873FD
out of order segment: rcv_next 7FE86447 seq 7FE873FD - 7FE8799D
ofo requeuing : rcv_next 7FE868BD seq 7FE868BD - 7FE86E5D
ofo requeuing : rcv_next 7FE86E5D seq 7FE86E5D - 7FE873FD
ofo requeuing : rcv_next 7FE873FD seq 7FE873FD - 7FE8799D
out of order segment: rcv_next 7FE89B1A seq 7FE8A0BA - 7FE8A130
ofo requeuing : rcv_next 7FE8A0BA seq 7FE8A0BA - 7FE8A130
out of order segment: rcv_next 7FE8EA68 seq 7FE8F008 - 7FE8F105
ofo requeuing : rcv_next 7FE8F008 seq 7FE8F008 - 7FE8F105
out of order segment: rcv_next 7FE9293A seq 7FE92F5B - 7FE934FB
out of order segment: rcv_next 7FE9293A seq 7FE934FB - 7FE93A9B
ofo requeuing : rcv_next 7FE92F5B seq 7FE92F5B - 7FE934FB
ofo requeuing : rcv_next 7FE934FB seq 7FE934FB - 7FE93A9B
out of order segment: rcv_next BD40710C seq BD4076AC - BD407C24
ofo requeuing : rcv_next BD4076AC seq BD4076AC - BD407C24
out of order segment: rcv_next BD412FE0 seq BD4134EB - BD413A8B
out of order segment: rcv_next BD412FE0 seq BD413A8B - BD41402B
out of order segment: rcv_next BD412FE0 seq BD41402B - BD4145CB
out of order segment: rcv_next 1886849F seq 18868A3F - 18868B92
ofo requeuing : rcv_next 18868A3F seq 18868A3F - 18868B92
out of order segment: rcv_next 84907368 seq 84907DB3 - 84908353
out of order segment: rcv_next 84907368 seq 84908353 - 849088F3
out of order segment: rcv_next 84907368 seq 849088F3 - 84908E93
ofo requeuing : rcv_next 84907DB3 seq 84907DB3 - 84908353
ofo requeuing : rcv_next 84908353 seq 84908353 - 849088F3
ofo requeuing : rcv_next 849088F3 seq 849088F3 - 84908E93
out of order segment: rcv_next 8493139B seq 84931824 - 84931BB5
ofo requeuing : rcv_next 84931824 seq 84931824 - 84931BB5
out of order segment: rcv_next 849395B4 seq 84939B54 - 84939C31
out of order segment: rcv_next 849395B4 seq 84939C31 - 8493A1D1
out of order segment: rcv_next 849395B4 seq 8493A1D1 - 8493A771
ofo requeuing : rcv_next 84939B54 seq 84939B54 - 84939C31
ofo requeuing : rcv_next 84939C31 seq 84939C31 - 8493A1D1
ofo requeuing : rcv_next 8493A1D1 seq 8493A1D1 - 8493A771
out of order segment: rcv_next 84955086 seq 84955626 - 84955A8A
ofo requeuing : rcv_next 84955626 seq 84955626 - 84955A8A
out of order segment: rcv_next 84966A37 seq 84966FD7 - 84967400
ofo requeuing : rcv_next 84966FD7 seq 84966FD7 - 84967400
out of order segment: rcv_next 84987EEE seq 84988FCE - 8498956E
out of order segment: rcv_next 84987EEE seq 84989B0E - 8498A0AE
out of order segment: rcv_next 84987EEE seq 8498A0AE - 8498A406
ofo requeuing : rcv_next 84988FCE seq 84988FCE - 8498956E
ofo requeuing : rcv_next 84989B0E seq 84989B0E - 8498A0AE
ofo requeuing : rcv_next 8498A0AE seq 8498A0AE - 8498A406
out of order segment: rcv_next 84991C2B seq 849921CB - 8499264E
ofo requeuing : rcv_next 849921CB seq 849921CB - 8499264E
out of order segment: rcv_next 84994D23 seq 84995863 - 84995E03
out of order segment: rcv_next 84994D23 seq 84995E03 - 84995E64
out of order segment: rcv_next 849952C3 seq 84995E64 - 84996404
ofo requeuing : rcv_next 84995863 seq 84995863 - 84995E03
ofo requeuing : rcv_next 84995E03 seq 84995E03 - 84995E64
ofo requeuing : rcv_next 84995E64 seq 84995E64 - 84996404
out of order segment: rcv_next 356A36C1 seq 356A4201 - 356A43D2
ofo requeuing : rcv_next 356A4201 seq 356A4201 - 356A43D2
dvb-usb: ITE 9135(9006) Generic successfully deinitialized and disconnected.
root@et9x00:~#
Re: new it913x drivers not working in new kernel with et9000 #18
-
- Member
- 32 posts
0
Neutral
Posted 27 April 2012 - 19:59
@ Halflife, you have a version of the chip 01, version 02 does not work at all 
Re: new it913x drivers not working in new kernel with et9000 #19
-
- Senior Member
- 59 posts
0
Neutral
Posted 5 May 2012 - 14:57
any news about this problem? I was update image and see some new version for it913x drivers. but still usb stick just disconnect after few minutes, sometimes a little bit longer. so I have to go back on some vix image with kernel 3.1 where everything works fine
Re: new it913x drivers not working in new kernel with et9000 #20
-
- Member
- 32 posts
0
Neutral
Posted 7 May 2012 - 09:00
Do you expect to solve the problem?
3 user(s) are reading this topic
0 members, 3 guests, 0 anonymous users
