i think this is better
dvb-usb: found a 'ITEtech USB2.0 DVB-T Recevier' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-it9135.fw'
IT9135: This is IT9135 chip v1
IT9135: ~~~ .Fw file only include Omega1 firmware, Scripts1&2!!
IT9135: =========================================
IT9135: DRIVER_RELEASE_VERSION: v11.08.02.1
IT9135: FW_RELEASE_VERSION: V1_0_26_2
IT9135: API_RELEASE_VERSION: 203.20110426.0
IT9135: =========================================
IT9135: it9135_device_init success!!
dvb-usb: found a 'ITEtech USB2.0 DVB-T Recevier' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (ITEtech USB2.0 DVB-T Recevier)
DVB: registering adapter 1 frontend 0 (IT9135 USB DVB-T)...
dvb-usb: ITEtech USB2.0 DVB-T Recevier successfully initialized and connected.
usbcore: registered new driver dvb_usb_it9135
DVB: registering adapter 0 frontend 0 (IT9135 USB DVB-T)...
yes on the second dmesg i found the dvb-t
probably you forgot to tell me "switch off befoure create dmesg".
If i understand the dmesg is a buffer, and we need the initial message of startup. if you create a dmesg of a linux that stay on for a week (i never switch it off) the buffer overwrite the initial startup messages, is it corect ?
- For the "auto scan" and the manual "complete" scan witch is the difference ? the auto do not use terrestrial.xml ?
i use originalk terrestrial file, i will make other test.
- witch error do you have in the dmesg when the IT9135 not work ?
So Solo 1.6.6 has something different on compilation that's why testano dvb-t works?Yep. I forgot to tell you to reboot your box before do "dmesg" command
Both scan types uses the XML description file for their respective frontneds (satellite.xml, terrestrial.xml - the last common to DVB-C and DVB-T frontends). You can try to use a different terrestrial.xml and see if all it's ok or not.
About errors on device not corretly detected, the previous reports from other users don't show very big differences.
So Solo 1.6.6 has something different on compilation that's why testano dvb-t works?
So, its not a driver issue, neither is a firmware issue.
driver see it and use it, whats next?
Is there something that could be done to make it work?
Ok.VuDuo +
Ok, reflashed 1.6.6 then shutdown box, installed dvb-t and installed driver, reboot again and tried to search, Works
All ok,
Thanks angelofsky1980.
BUGS:
Just scale to 16:9 doesnt work on dvb-t channels, i tried auto resolution and same bug. So 4:3 content is on the middle of my 16:9 tv and sucks.
Recording on dvb-t channels is countable and i cannot record as much channels as before on Sattelite e.g 3 recordings on dvb-t at the same time then tried to record a dvb-s2 channel and it doesnt let me do it.
It should as it is on a different tunner right?
SNR 9% doesnt go higher dont know why! Maybe it needs the 5v thing that is not implemented?
Thanks again
ok, now we are 2 with this working
I have the same SNR 9% problem. maybe it is a little bug, i hope,
Angelo on your box in DTT the SNR work good ?
Other good think to know is that the official terrestrial.xml is not good for all.
In my area i found few channel with automatic scan, with a different file a found 122 channels.
I look inside the terrestrial and the setting is all "automatic", maybe some terrestrial transponder do not accept automatic
ok, attached terrestrial,
experiments are my work
For the 9% SNR, it is not fixed, example if you press OK more times, and look the SNR, often it work and go to 74%, but after 2 seconds it return to 9%.
I have a question, after automatic terrestrial channel search, it is normal that the channel do not go in Preferred Channel List ?
I must go in Satellites, Trasponders, and found them.
Under Preferred channel is there Terrestrial, but it is empty.
Hi, Angelofsky1980.
I found this for working driver for new kernels v3.xx
http://linuxtv.org/wiki/index.php/ITE_IT9135
I hope you can make use of it.
Thanks