Re: [BUG] - Why anyone fix this problem?
Ok, Doron Cohen solved the problem in 5 seconds. There are 2 mode for DVB-T, we need to force mode 4 instead of mode 0. Thanks to Roberto for trying to solve the problem and to Olli for the e-mail of Doron Cohen. Regards Francesco 2015-02-03 11:57 GMT+01:00 Olli Salonen olli.salo...@iki.fi: Well, if you suspect that some other change broke the driver, then you can try an older kernel (the support was introduced in kernel 3.10) or an older media_tree to see if that's indeed the case. The firmware is just one small piece of the puzzle. Maybe you can just replace the firmware or maybe you need to write a lot of code or even both. All this is next to impossible to say without having a very strictly defined and pinpointed issue or alternatively the actual device to play around with. So far it seems you're the only one with that device here, so it would help a lot if you can narrow the scope down by saying: it worked fine in kernel xyz, but commit abc seems to break the support for the device or it seems it has never worked for DVB-T. Cheers, -olli On 3 February 2015 at 11:42, Francesco Other francesco.ot...@gmail.com wrote: Maybe when Doron Cohen wrote the patch the device worked fine but now, after that someone change the code for their own enjoyment, it doesn't. If you read my question you will find that the device has signal lock but no data stream. There isn't need to write a code from scratch because I have the working firmware that kernel asks for. I don't know what the problem is, I'm an aerospace engineer not a software engineer. Best Regards Francesco 2015-02-03 9:06 GMT+01:00 Olli Salonen olli.salo...@iki.fi: Hi Francesco, You need to understand that many people write code for their own enjoyment. In other words, they often write code to scratch an itch. Thus it can sometimes happen that there really is no-one here who could help you. The person who wrote the code originally might have stopped contributing and is more interested in gardening or kiteboarding these days. Maybe no-one here just has heard of the device you're talking about or owns one. Anyway, I did some digging for you. The support for your device was originally added based on this patch https://patchwork.linuxtv.org/patch/7881/ submitted by Doron Cohen dor...@siano-ms.com. It seems he's working for the Siano company itself. Have you tried contacting them already? Cheers, -olli On 2 February 2015 at 15:10, Francesco Other francesco.ot...@gmail.com wrote: Is it possible that the problem I explained here isn't interesting for anyone? The device is supported by kernel but obviously there is a bug with DVB-T. I have the working firmware (on Windows) for DVB-T if you need it. http://www.spinics.net/lists/linux-media/msg85505.html http://www.spinics.net/lists/linux-media/msg85478.html http://www.spinics.net/lists/linux-media/msg85432.html Regards Francesco -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [BUG] - Why anyone fix this problem?
Maybe when Doron Cohen wrote the patch the device worked fine but now, after that someone change the code for their own enjoyment, it doesn't. If you read my question you will find that the device has signal lock but no data stream. There isn't need to write a code from scratch because I have the working firmware that kernel asks for. I don't know what the problem is, I'm an aerospace engineer not a software engineer. Best Regards Francesco 2015-02-03 9:06 GMT+01:00 Olli Salonen olli.salo...@iki.fi: Hi Francesco, You need to understand that many people write code for their own enjoyment. In other words, they often write code to scratch an itch. Thus it can sometimes happen that there really is no-one here who could help you. The person who wrote the code originally might have stopped contributing and is more interested in gardening or kiteboarding these days. Maybe no-one here just has heard of the device you're talking about or owns one. Anyway, I did some digging for you. The support for your device was originally added based on this patch https://patchwork.linuxtv.org/patch/7881/ submitted by Doron Cohen dor...@siano-ms.com. It seems he's working for the Siano company itself. Have you tried contacting them already? Cheers, -olli On 2 February 2015 at 15:10, Francesco Other francesco.ot...@gmail.com wrote: Is it possible that the problem I explained here isn't interesting for anyone? The device is supported by kernel but obviously there is a bug with DVB-T. I have the working firmware (on Windows) for DVB-T if you need it. http://www.spinics.net/lists/linux-media/msg85505.html http://www.spinics.net/lists/linux-media/msg85478.html http://www.spinics.net/lists/linux-media/msg85432.html Regards Francesco -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[BUG] - Why anyone fix this problem?
Is it possible that the problem I explained here isn't interesting for anyone? The device is supported by kernel but obviously there is a bug with DVB-T. I have the working firmware (on Windows) for DVB-T if you need it. http://www.spinics.net/lists/linux-media/msg85505.html http://www.spinics.net/lists/linux-media/msg85478.html http://www.spinics.net/lists/linux-media/msg85432.html Regards Francesco -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: build failure on ubuntu 14.04.1 LTS
Hi Vincent, you may use this workaround, I have the same problem: https://github.com/ljalves/linux_media/issues/68 Reagrds Francesco 2015-01-19 13:32 GMT+01:00 Vincent McIntyre vincent.mcint...@gmail.com: Hi I am seeing build failures since 11 January. A build I did on 22 December worked fine. My build procedure and the error are shown below. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION=Ubuntu 14.04.1 LTS $ uname -a Linux ubuntu 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:30:01 UTC 2014 i686 i686 i686 GNU/Linux $ make distclean $ rm v4l/.config $ git pull $ git log |head commit de98549b53c938b44f578833fe8440b92f4a8c64 Author: Hans Verkuil hans.verk...@cisco.com Date: Mon Jan 12 10:53:27 2015 +0100 Update v3.11_dev_groups.patch Signed-off-by: Hans Verkuil hans.verk...@cisco.com commit 3886d538f89948d49b652465e0d52e6e9a7329ab Author: Hans Verkuil hans.verk...@cisco.com $ ./build --main-git ... CC [M] /home/me/git/clones/media_build/v4l/smiapp-core.o /home/me/git/clones/media_build/v4l/smiapp-core.c: In function 'smiapp_get_pdata': /home/me/git/clones/media_build/v4l/smiapp-core.c:3061:3: error: implicit declaration of function 'of_read_number' [-Werror=implicit-function-declaration] pdata-op_sys_clock[i] = of_read_number(val + i * 2, 2); ^ cc1: some warnings being treated as errors make[3]: *** [/home/me/git/clones/media_build/v4l/smiapp-core.o] Error 1 make[2]: *** [_module_/home/me/git/clones/media_build/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-3.13.0-37-generic' make[1]: *** [default] Error 2 make[1]: Leaving directory `/home/me/git/clones/media_build/v4l' make: *** [all] Error 2 build failed at ./build line 491, IN line 4. $ grep -ilr implicit-function-declaration . |grep -v o.cmd ./media/tools/thermal/tmon/Makefile ./media/arch/parisc/math-emu/Makefile ./media/Makefile It's not clear to me whether this a problem with the media_tree code or the media_build code. media/Makefile contains this definition KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \ -fno-strict-aliasing -fno-common \ -Werror-implicit-function-declaration \ -Wno-format-security \ -std=gnu89 Regards Vince -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Driver/module in kernel fault. Anyone expert to help me? Siano ID 187f:0600
Ok, many thanks.
I used this guide:
http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
and Ubuntu 14.04.1 LTS with kernel version 3.13.0-44.generic.
I'm not afraid using the terminal if you want to help me :-)
Regards
Francesco
2015-01-15 2:27 GMT+01:00 Roberto Alcântara robe...@eletronica.org:
Ok Francesco, just to confirm that buffer is empty.
Well I'm not expert but seems the driver has some bug on state
machine. I do not know details about Siano state machine for DVB but
MSG_SMS_DAB_CHANNEL seems not be the right message expected. I will
try to look deeply on this code.
Are you able to test driver last version from linux-media tree? What
kernel are you using?
As I can't test DVB system here I only can suppose some scenario (some
of them just a try) and do some blind patch for your tests.
Mauro Chehab surely know a lot more about this, but as he do not sent
message on this thread I suppose he is really busy.
Cheers,
- Roberto
- Roberto
On Wed, Jan 14, 2015 at 4:23 PM, Francesco Other
francesco.ot...@gmail.com wrote:
Hi Roberto,
It doesn't record anything, the file is blank (0 bytes) :-(
$ dd if=/dev/dvb/adapter0/dvr0 of=test.ts
0+0 records in
0+0 records out
0 bytes (0 B) copied, 13,4642 s, 0,0 kB/s
Francesco
2015-01-14 16:58 GMT+01:00 Roberto Alcântara robe...@eletronica.org:
Francesco,
Seems very strange not work once you have lock (1f) and ber 0. not a
real problem signal report.
After tzap -r open another console and:
dd if=/dev/dvb/adapter0/dvr0 of=test.ts
Wait 10 seconds and stop it. Please check file size (try to open on
vlc too if big enough...).
Cheers,
- Roberto
On Tue, Jan 13, 2015 at 6:56 PM, Francesco Other
francesco.ot...@gmail.com wrote:
So, this is the output for tzap with the NOT-working-device:
$ tzap -r -c ~/.tzap/channels.conf Italia1
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '/home/ionic/.tzap/channels.conf'
Version: 5.10 FE_CAN { DVB-T }
tuning to 69800 Hz
video pid 0x0654, audio pid 0x0655
status 00 | signal | snr | ber | unc |
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 010e | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 010e | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
- Roberto
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Driver/module in kernel fault. Anyone expert to help me? Siano ID 187f:0600
Hi Roberto,
It doesn't record anything, the file is blank (0 bytes) :-(
$ dd if=/dev/dvb/adapter0/dvr0 of=test.ts
0+0 records in
0+0 records out
0 bytes (0 B) copied, 13,4642 s, 0,0 kB/s
Francesco
2015-01-14 16:58 GMT+01:00 Roberto Alcântara robe...@eletronica.org:
Francesco,
Seems very strange not work once you have lock (1f) and ber 0. not a
real problem signal report.
After tzap -r open another console and:
dd if=/dev/dvb/adapter0/dvr0 of=test.ts
Wait 10 seconds and stop it. Please check file size (try to open on
vlc too if big enough...).
Cheers,
- Roberto
On Tue, Jan 13, 2015 at 6:56 PM, Francesco Other
francesco.ot...@gmail.com wrote:
So, this is the output for tzap with the NOT-working-device:
$ tzap -r -c ~/.tzap/channels.conf Italia1
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
reading channels from file '/home/ionic/.tzap/channels.conf'
Version: 5.10 FE_CAN { DVB-T }
tuning to 69800 Hz
video pid 0x0654, audio pid 0x0655
status 00 | signal | snr | ber | unc |
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 010e | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 010e | ber | unc |
FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc |
FE_HAS_LOCK
- Roberto
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
HELP: tzap, signal 1f, FE_HAS_LOCK, no demux on Ubuntu 14.04 LTS, Device Siano ID 187f:0600, DVB-T
Hi to all,
I have this output from tzap
Version: 5.10 FE_CAN { DVB-T }
tuning to 69800 Hz
video pid 0x0654, audio pid 0x0655
status 00 | signal | snr | ber | unc |
status 1f | signal | snr 0104 | ber | unc | FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc | FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc | FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc | FE_HAS_LOCK
status 1f | signal | snr 0104 | ber | unc | FE_HAS_LOCK
...
...
and I can't receive the channel (no video, no audio, no service from multiplex).
Maybe a demux problem?
Ubuntu 14.04 LTS, Device Siano ID 187f:0600, DVB-T
Thanks for any help
Francesco
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Driver/module in kernel fault. Anyone expert to help me? Siano ID 187f:0600
Is there a gentleman that can help me with my problem? On linuxtv.org they said that someone here sure will help me. I submitted the problem here: http://www.spinics.net/lists/linux-media/msg85432.html Regards Francesco -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Driver/module in kernel fault. Anyone expert to help me? Siano ID 187f:0600
Hi Roberto, thanks for your fast reply. I'm from Italy, a DVB-T region. With Windows the device works fine, it receives all the channels from multiplexes. I don't know if my device has the SMS2270 chip, I know the ID, 187f:0600, and the link on the Terratec site: http://www.terratec.net/details.php?artnr=145258#.VLU5Z2SG9LY In that site there are the software and the Windows driver, if you install those driver you can obtain the dvb_rio.inp driver from system32 folder. I forced the DVB-T mode because without it in dmesg output I see that system ask for isdbt_rio.inp, but with DVB-T forced mode the system ask for dvb_rio.inp. I can't understand why I can't receive any channels from multiplexes, the signal is ok, I can see this from many software (Kaffeine, w_scan, scan, TvHeadend). Can you help me please? Best Regards Francesco 2015-01-13 16:21 GMT+01:00 Roberto Alcântara robe...@eletronica.org: Hi Francesco, You are using Siano SMS2270, am I right? My guess you're using ISDB-T firmware to program your ic, but are you in ISDB-T region? I use same firmware name here and works fine (Brazil) and it seems loaded ok on your log. I never saw an DVB firmware available to sms2270. Your tuner is working fine under Windows with provided software ? Cheers, - Roberto - Roberto On Tue, Jan 13, 2015 at 11:50 AM, Francesco Other francesco.ot...@gmail.com wrote: Is there a gentleman that can help me with my problem? On linuxtv.org they said that someone here sure will help me. I submitted the problem here: http://www.spinics.net/lists/linux-media/msg85432.html Regards Francesco -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Driver/module in kernel fault. Anyone expert to help me? Siano ID 187f:0600
MSG_SMS_DAB_CHANNEL(607) size: 1324 Jan 13 22:25:16 Linux kernel: [ 2289.995258] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 196 Jan 13 22:25:16 Linux kernel: [ 2290.095263] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 572 Jan 13 22:25:16 Linux kernel: [ 2290.196141] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 760 Jan 13 22:25:17 Linux kernel: [ 2290.395886] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 196 Jan 13 22:25:17 Linux kernel: [ 2290.586763] smsusb_onresponse: received MSG_SMS_HO_PER_SLICES_IND(630) size: 108 Jan 13 22:25:17 Linux kernel: [ 2290.595756] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 1512 Jan 13 22:25:17 Linux kernel: [ 2290.695642] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 948 Jan 13 22:25:17 Linux kernel: [ 2290.766257] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 948 Jan 13 22:25:17 Linux kernel: [ 2290.866510] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 1324 Jan 13 22:25:17 Linux kernel: [ 2290.966384] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 196 Jan 13 22:25:17 Linux kernel: [ 2291.004024] smsusb_sendrequest: sending MSG_SMS_GET_STATISTICS_REQ(615) size: 8 Jan 13 22:25:17 Linux kernel: [ 2291.004136] smsusb_onresponse: received MSG_SMS_GET_STATISTICS_RES(616) size: 224 Jan 13 22:25:17 Linux kernel: [ 2291.067258] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 760 Jan 13 22:25:17 Linux kernel: [ 2291.161362] smsusb_sendrequest: sending MSG_SMS_REMOVE_PID_FILTER_REQ(603) size: 12 Jan 13 22:25:17 Linux kernel: [ 2291.161515] smsusb_onresponse: received MSG_SMS_REMOVE_PID_FILTER_RES(604) size: 12 Jan 13 22:25:17 Linux kernel: [ 2291.167134] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 384 Jan 13 22:25:17 Linux kernel: [ 2291.268142] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 2452 Jan 13 22:25:18 Linux kernel: [ 2291.368007] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 2076 Jan 13 22:25:18 Linux kernel: [ 2291.467890] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 2076 Jan 13 22:25:18 Linux kernel: [ 2291.568758] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 196 Jan 13 22:25:18 Linux kernel: [ 2291.769517] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 572 Jan 13 22:25:18 Linux kernel: [ 2291.785142] smsusb_onresponse: received MSG_SMS_HO_PER_SLICES_IND(630) size: 108 Jan 13 22:25:18 Linux kernel: [ 2291.869511] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 760 Jan 13 22:25:18 Linux kernel: [ 2291.969389] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 196 Jan 13 22:25:18 Linux kernel: [ 2292.070260] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 196 Jan 13 22:25:18 Linux kernel: [ 2292.149215] usb 1-1: USB disconnect, device number 9 Now, in which way can I tzap? Regards Francesco 2015-01-13 17:13 GMT+01:00 Roberto Alcântara robe...@eletronica.org: Good to know about DVB on this chip. This is sms2270 id :-) I think you can get more information from module debug messages. Try options smsusb debug=3 on /etc/modprobe.d. Then reload it and try to tzap one of channels found by scan to look for some lock. You will have more debug messages now. Cheers, - Roberto - Roberto On Tue, Jan 13, 2015 at 12:35 PM, Francesco Other francesco.ot...@gmail.com wrote: Hi Roberto, thanks for your fast reply. I'm from Italy, a DVB-T region. With Windows the device works fine, it receives all the channels from multiplexes. I don't know if my device has the SMS2270 chip, I know the ID, 187f:0600, and the link on the Terratec site: http://www.terratec.net/details.php?artnr=145258#.VLU5Z2SG9LY In that site there are the software and the Windows driver, if you install those driver you can obtain the dvb_rio.inp driver from system32 folder. I forced the DVB-T mode because without it in dmesg output I see that system ask for isdbt_rio.inp, but with DVB-T forced mode the system ask for dvb_rio.inp. I can't understand why I can't receive any channels from multiplexes, the signal is ok, I can see this from many software (Kaffeine, w_scan, scan, TvHeadend). Can you help me please? Best Regards Francesco 2015-01-13 16:21 GMT+01:00 Roberto Alcântara robe...@eletronica.org: Hi Francesco, You are using Siano SMS2270, am I right? My guess you're using ISDB-T firmware to program your ic, but are you in ISDB-T region? I use same firmware name here and works fine (Brazil) and it seems loaded ok on your log. I never saw an DVB firmware available to sms2270. Your tuner is working fine under Windows with provided software ? Cheers, - Roberto - Roberto On Tue, Jan 13, 2015 at 11:50 AM, Francesco Other francesco.ot...@gmail.com wrote: Is there a gentleman that can help me with my problem? On linuxtv.org they said that someone here
Re: Driver/module in kernel fault. Anyone expert to help me? Siano ID 187f:0600
kernel: [ 3969.720950] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 1888 Jan 13 22:53:16 Linux kernel: [ 3969.755826] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.756074] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.756200] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.756450] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.756699] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.786453] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.786702] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.786950] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.787200] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.818952] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.819200] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.819326] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.819576] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.852576] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.852701] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.852951] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.853200] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 1888 Jan 13 22:53:16 Linux kernel: [ 3969.853325] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.885829] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.886076] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.886325] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.886575] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.921452] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.921701] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.921950] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.922200] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.956204] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.956451] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.956574] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.956828] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.968468] smsusb_sendrequest: sending MSG_SMS_GET_STATISTICS_REQ(615) size: 8 Jan 13 22:53:16 Linux kernel: [ 3969.974578] smsusb_onresponse: received MSG_SMS_GET_STATISTICS_RES(616) size: 224 Jan 13 22:53:16 Linux kernel: [ 3969.991964] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 Jan 13 22:53:16 Linux kernel: [ 3969.992203] smsusb_onresponse: received MSG_SMS_DAB_CHANNEL(607) size: 3956 ... ... Regards Francesco 2015-01-13 17:13 GMT+01:00 Roberto Alcântara robe...@eletronica.org: Good to know about DVB on this chip. This is sms2270 id :-) I think you can get more information from module debug messages. Try options smsusb debug=3 on /etc/modprobe.d. Then reload it and try to tzap one of channels found by scan to look for some lock. You will have more debug messages now. Cheers, - Roberto - Roberto On Tue, Jan 13, 2015 at 12:35 PM, Francesco Other francesco.ot...@gmail.com wrote: Hi Roberto, thanks for your fast reply. I'm from Italy, a DVB-T region. With Windows the device works fine, it receives all the channels from multiplexes. I don't know if my device has the SMS2270 chip, I know the ID, 187f:0600, and the link on the Terratec site: http://www.terratec.net/details.php?artnr=145258#.VLU5Z2SG9LY In that site there are the software and the Windows driver, if you install those driver you can obtain the dvb_rio.inp driver from system32 folder. I forced the DVB-T mode because without it in dmesg output I see that system ask for isdbt_rio.inp, but with DVB-T forced mode the system ask for dvb_rio.inp. I can't
[no subject]
My USB dongle is recognized by the system but I have a problem with the channels. Please read all my post for any help ;-) At first, I used this guide: http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers After that dmesg showed that system was searching for isdbt_rio.inp firmware. If I use that firmware from linuxtv.org, w_scan shows me an error, it says that my dongle can't search for TERRESTRIAL. So, for using smsmdtv mode DVB-T as the default option, I forced the kernel module in this way: echo options smsmdtv default_mode=0 | sudo tee /etc/modprobe.d/smsmdtv.conf After that system searches for dvb_rio.inp, good ;-) dmesg: [ 1327.312795] usb 1-3: new high-speed USB device number 4 using ehci-pci [ 1327.446103] usb 1-3: New USB device found, idVendor=187f, idProduct=0600 [ 1327.446121] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1327.446130] usb 1-3: Product: MDTV Receiver [ 1327.446138] usb 1-3: Manufacturer: MDTV Receiver [ 1327.451833] usb 1-3: Direct firmware load failed with error -2 [ 1327.451849] usb 1-3: Falling back to user helper [ 1327.456026] smscore_load_firmware_from_file: line: 1168: failed to open firmware file dvb_rio.inp [ 1327.456535] DVB: registering new adapter (Siano Rio Digital Receiver) [ 1327.457351] usb 1-3: DVB: registering adapter 0 frontend 0 (Siano Mobile Digital MDTV Receiver)... I used dvb_rio.inp from my Windows installation (md5: 146156b55ce6fc586470f28194add5a7, sha1: 48907a4749ba5fd5b4b947195c0d484e55a4c169). Now I have this output form lsusb: Bus 002 Device 002: ID 0402:7675 ALi Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 003: ID 0489:e03c Foxconn / Hon Hai Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 187f:0600 Siano Mobile Silicon Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub dmesg: [ 1390.167433] usb 1-3: new high-speed USB device number 5 using ehci-pci [ 1390.300895] usb 1-3: New USB device found, idVendor=187f, idProduct=0600 [ 1390.300913] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1390.300922] usb 1-3: Product: MDTV Receiver [ 1390.300930] usb 1-3: Manufacturer: MDTV Receiver [ 1390.776240] DVB: registering new adapter (Siano Rio Digital Receiver) [ 1390.777275] usb 1-3: DVB: registering adapter 0 frontend 0 (Siano Mobile Digital MDTV Receiver)... lsmod | grep sms: smsdvb 27513 0 dvb_core 125880 1 smsdvb smsusb 17819 0 smsmdtv 53748 2 smsdvb,smsusb rc_core 27389 1 smsmdtv Finally I can scan and tune with a specific frequency but I can't obtain services from multiplexes. w_scan -c IT output: w_scan version 20130331 (compiled for DVB API 5.10) using settings for ITALY DVB aerial DVB-T Europe scan type TERRESTRIAL, channellist 4 output format vdr-2.0 WARNING: could not guess your codepage. Falling back to 'UTF-8' output charset 'UTF-8', use -C to override Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 - TERRESTRIAL Siano Mobile Digital MDTV Receiver: good :-) Using TERRESTRIAL frontend (adapter /dev/dvb/adapter0/frontend0) Getting frontend capabilities Using DVB API 5.a frontend 'Siano Mobile Digital MDTV Receiver' supports INVERSION_AUTO QAM_AUTO TRANSMISSION_MODE_AUTO GUARD_INTERVAL_AUTO HIERARCHY_AUTO FEC_AUTO FREQ (44.25MHz ... 867.25MHz) ---_ Scanning 7MHz frequencies... 177500: (time: 00:00) (time: 00:01) signal ok: QAM_AUTO f = 177500 kHz I999B7C999D999T999G999Y999 Info: no data from NIT(actual) 184500: (time: 00:15) 191500: (time: 00:18) (time: 00:19) signal ok: QAM_AUTO f = 191500 kHz I999B7C999D999T999G999Y999 Info: no data from NIT(actual) 198500: (time: 00:33) 205500: (time: 00:36) ... ... I created a file named frequency with this content for doing a test: # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 17750 7MHz 2/3 NONE QAM64 8k 1/8 NONE # MUX-B Rai T 69800 8MHz 2/3 NONE QAM64 8k 1/8 NONE # Mediaset 1 and when I launch dvbscan frequency I obtain: Unable to query frontend status. With the utility scan I obtain: scanning frequency using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 17750 1 2 9 3 1 2 0 initial transponder 69800 0 2 9 3 1 2 0 tune to: 17750:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 tune to: 69800:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 dumping lists (0 services) Done. WIth dvbv5-scan frequency: ERROR key/value without a channel group while parsing line 3 of frequency. I tried to insert
Terratec Cinergy DVB-T Stick, Siano ID 187f:0600, no data from NIT(actual)
My USB dongle is recognized by the system but I have a problem with the channels. Please read all my post for any help ;-) At first, I used this guide: http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers After that dmesg showed that system was searching for isdbt_rio.inp firmware. If I use that firmware from linuxtv.org, w_scan shows me an error, it says that my dongle can't search for TERRESTRIAL. So, for using smsmdtv mode DVB-T as the default option, I forced the kernel module in this way: echo options smsmdtv default_mode=0 | sudo tee /etc/modprobe.d/smsmdtv.conf After that system searches for dvb_rio.inp, good ;-) dmesg: [ 1327.312795] usb 1-3: new high-speed USB device number 4 using ehci-pci [ 1327.446103] usb 1-3: New USB device found, idVendor=187f, idProduct=0600 [ 1327.446121] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1327.446130] usb 1-3: Product: MDTV Receiver [ 1327.446138] usb 1-3: Manufacturer: MDTV Receiver [ 1327.451833] usb 1-3: Direct firmware load failed with error -2 [ 1327.451849] usb 1-3: Falling back to user helper [ 1327.456026] smscore_load_firmware_from_file: line: 1168: failed to open firmware file dvb_rio.inp [ 1327.456535] DVB: registering new adapter (Siano Rio Digital Receiver) [ 1327.457351] usb 1-3: DVB: registering adapter 0 frontend 0 (Siano Mobile Digital MDTV Receiver)... I used dvb_rio.inp from my Windows installation (md5: 146156b55ce6fc586470f28194add5a7, sha1: 48907a4749ba5fd5b4b947195c0d484e55a4c169). Now I have this output form lsusb: Bus 002 Device 002: ID 0402:7675 ALi Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 003: ID 0489:e03c Foxconn / Hon Hai Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 187f:0600 Siano Mobile Silicon Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub dmesg: [ 1390.167433] usb 1-3: new high-speed USB device number 5 using ehci-pci [ 1390.300895] usb 1-3: New USB device found, idVendor=187f, idProduct=0600 [ 1390.300913] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1390.300922] usb 1-3: Product: MDTV Receiver [ 1390.300930] usb 1-3: Manufacturer: MDTV Receiver [ 1390.776240] DVB: registering new adapter (Siano Rio Digital Receiver) [ 1390.777275] usb 1-3: DVB: registering adapter 0 frontend 0 (Siano Mobile Digital MDTV Receiver)... lsmod | grep sms: smsdvb 27513 0 dvb_core 125880 1 smsdvb smsusb 17819 0 smsmdtv 53748 2 smsdvb,smsusb rc_core 27389 1 smsmdtv Finally I can scan and tune with a specific frequency but I can't obtain services from multiplexes. w_scan -c IT output: w_scan version 20130331 (compiled for DVB API 5.10) using settings for ITALY DVB aerial DVB-T Europe scan type TERRESTRIAL, channellist 4 output format vdr-2.0 WARNING: could not guess your codepage. Falling back to 'UTF-8' output charset 'UTF-8', use -C to override Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 - TERRESTRIAL Siano Mobile Digital MDTV Receiver: good :-) Using TERRESTRIAL frontend (adapter /dev/dvb/adapter0/frontend0) Getting frontend capabilities Using DVB API 5.a frontend 'Siano Mobile Digital MDTV Receiver' supports INVERSION_AUTO QAM_AUTO TRANSMISSION_MODE_AUTO GUARD_INTERVAL_AUTO HIERARCHY_AUTO FEC_AUTO FREQ (44.25MHz ... 867.25MHz) ---_ Scanning 7MHz frequencies... 177500: (time: 00:00) (time: 00:01) signal ok: QAM_AUTO f = 177500 kHz I999B7C999D999T999G999Y999 Info: no data from NIT(actual) 184500: (time: 00:15) 191500: (time: 00:18) (time: 00:19) signal ok: QAM_AUTO f = 191500 kHz I999B7C999D999T999G999Y999 Info: no data from NIT(actual) 198500: (time: 00:33) 205500: (time: 00:36) ... ... I created a file named frequency with this content for doing a test: # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 17750 7MHz 2/3 NONE QAM64 8k 1/8 NONE # MUX-B Rai T 69800 8MHz 2/3 NONE QAM64 8k 1/8 NONE # Mediaset 1 and when I launch dvbscan frequency I obtain: Unable to query frontend status. With the utility scan I obtain: scanning frequency using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 17750 1 2 9 3 1 2 0 initial transponder 69800 0 2 9 3 1 2 0 tune to: 17750:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 tune to: 69800:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 dumping lists (0 services) Done. WIth dvbv5-scan frequency: ERROR key/value without a channel group while parsing line 3 of frequency. I tried to
