* DiBcom adapter problems
@ 2012-06-17 15:24 Rodolfo Timoteo da Silva
0 siblings, 0 replies; 10+ messages in thread
From: Rodolfo Timoteo da Silva @ 2012-06-17 15:24 UTC (permalink / raw)
To: linux-media
Hi, every time that i try to syntonize DVB-T channels i receive a
message in kernel like in log1.txt arch.
There are in log2.txt some usefull information about the device.
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: DiBcom adapter problems
@ 2012-06-26 18:41 Choi Wing Chan
0 siblings, 0 replies; 10+ messages in thread
From: Choi Wing Chan @ 2012-06-26 18:41 UTC (permalink / raw)
To: linux-media
no, it is not related to the dibcom, but i have similar problem about
the delivery system for my dmb-th card. i apply your patch and i can
go a small step further. now i have the xc5000 error. it is because in
the xc5000 driver, the set-params function is missing a switch-case
for SYS_DMBTH. after adding the case, i still got an error in the
driver. but that is another story.
--
http://chanchoiwing.blogspot.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: DiBcom adapter problems
2012-06-23 22:06 Choi Wing Chan
@ 2012-06-26 10:25 ` Olivier GRENIE
0 siblings, 0 replies; 10+ messages in thread
From: Olivier GRENIE @ 2012-06-26 10:25 UTC (permalink / raw)
To: linux-media
Hello,
the xc5000 seems not to support DMB-T/H: "[ 2458.525608] xc5000: delivery system is not supported!". Anyway, this is not related to the dibcom device.
regards,
Olivier
________________________________________
From: linux-media-owner@vger.kernel.org [linux-media-owner@vger.kernel.org] On Behalf Of Choi Wing Chan [chanchoiwing@gmail.com]
Sent: Sunday, June 24, 2012 12:06 AM
To: linux-media@vger.kernel.org
Subject: RE: DiBcom adapter problems
the patch correct the error about no support system, however, my card
still can not scan any channels.
[ 2458.524854] set_delivery_system() Using delivery system 13 emulated
as if it were a 3
[ 2458.524855] change delivery system on cache to 13
[ 2458.524857] dvbv3_type : delivery_system = 13
[ 2458.524858] dtv_property_cache_sync() Preparing OFDM req
[ 2458.524859] dvbv3_type : delivery_system = 13
[ 2458.524860] dtv_property_legacy_params_sync() Preparing OFDM req
[ 2458.524861] dvb_frontend_add_event
[ 2458.524896] dvb_frontend_swzigzag_autotune: drift:0 inversion:0
auto_step:0 auto_sub_step:0 started_auto_step:0
[ 2458.524899] lgs8gxx: lgs8gxx_set_fe
[ 2458.525608] xc5000: delivery system is not supported!
[ 2458.525610] lgs8gxx: lgs8gxx_auto_detect
[ 2458.527558] lgs8gxx: try GI 945
[ 2458.724898] dvb_frontend_ioctl (69)
[ 2460.670065] lgs8gxx: try GI 945
[ 2462.812594] lgs8gxx: try GI 420
[ 2464.955133] lgs8gxx: try GI 420
[ 2467.097660] lgs8gxx: try GI 595
[ 2469.240181] lgs8gxx: try GI 945
[ 2471.382719] lgs8gxx: try GI 945
[ 2473.525253] lgs8gxx: try GI 420
[ 2475.667781] lgs8gxx: try GI 420
[ 2477.810317] lgs8gxx: try GI 595
[ 2479.952853] lgs8gxx: lgs8gxx_auto_detect failed
[ 2480.067822] lgs8gxx: lgs8gxx_read_status
[ 2480.069688] lgs8gxx: AFC = 5469 kHz
[ 2480.070629] lgs8gxx: Reg 0x4B: 0x02
[ 2480.070630] lgs8gxx: lgs8gxx_read_status: fe_status=0x0
[ 2480.270678] dvb_frontend_ioctl (69)
[ 2480.270680] lgs8gxx: lgs8gxx_read_status
[ 2480.272562] lgs8gxx: AFC = 5649 kHz
[ 2480.273504] lgs8gxx: Reg 0x4B: 0x02
[ 2480.273505] lgs8gxx: lgs8gxx_read_status: fe_status=0x0
[ 2480.473548] dvb_frontend_ioctl (69)
[ 2480.473553] lgs8gxx: lgs8gxx_read_status
[ 2480.475438] lgs8gxx: AFC = 5579 kHz
[ 2480.476379] lgs8gxx: Reg 0x4B: 0x02
[ 2480.476380] lgs8gxx: lgs8gxx_read_status: fe_status=0x0
may be an error in the driver, or an error in the frontend.c. have to
compare both logs from 3.2 and 3.4.
--
http://chanchoiwing.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: DiBcom adapter problems
@ 2012-06-23 22:06 Choi Wing Chan
2012-06-26 10:25 ` Olivier GRENIE
0 siblings, 1 reply; 10+ messages in thread
From: Choi Wing Chan @ 2012-06-23 22:06 UTC (permalink / raw)
To: linux-media
the patch correct the error about no support system, however, my card
still can not scan any channels.
[ 2458.524854] set_delivery_system() Using delivery system 13 emulated
as if it were a 3
[ 2458.524855] change delivery system on cache to 13
[ 2458.524857] dvbv3_type : delivery_system = 13
[ 2458.524858] dtv_property_cache_sync() Preparing OFDM req
[ 2458.524859] dvbv3_type : delivery_system = 13
[ 2458.524860] dtv_property_legacy_params_sync() Preparing OFDM req
[ 2458.524861] dvb_frontend_add_event
[ 2458.524896] dvb_frontend_swzigzag_autotune: drift:0 inversion:0
auto_step:0 auto_sub_step:0 started_auto_step:0
[ 2458.524899] lgs8gxx: lgs8gxx_set_fe
[ 2458.525608] xc5000: delivery system is not supported!
[ 2458.525610] lgs8gxx: lgs8gxx_auto_detect
[ 2458.527558] lgs8gxx: try GI 945
[ 2458.724898] dvb_frontend_ioctl (69)
[ 2460.670065] lgs8gxx: try GI 945
[ 2462.812594] lgs8gxx: try GI 420
[ 2464.955133] lgs8gxx: try GI 420
[ 2467.097660] lgs8gxx: try GI 595
[ 2469.240181] lgs8gxx: try GI 945
[ 2471.382719] lgs8gxx: try GI 945
[ 2473.525253] lgs8gxx: try GI 420
[ 2475.667781] lgs8gxx: try GI 420
[ 2477.810317] lgs8gxx: try GI 595
[ 2479.952853] lgs8gxx: lgs8gxx_auto_detect failed
[ 2480.067822] lgs8gxx: lgs8gxx_read_status
[ 2480.069688] lgs8gxx: AFC = 5469 kHz
[ 2480.070629] lgs8gxx: Reg 0x4B: 0x02
[ 2480.070630] lgs8gxx: lgs8gxx_read_status: fe_status=0x0
[ 2480.270678] dvb_frontend_ioctl (69)
[ 2480.270680] lgs8gxx: lgs8gxx_read_status
[ 2480.272562] lgs8gxx: AFC = 5649 kHz
[ 2480.273504] lgs8gxx: Reg 0x4B: 0x02
[ 2480.273505] lgs8gxx: lgs8gxx_read_status: fe_status=0x0
[ 2480.473548] dvb_frontend_ioctl (69)
[ 2480.473553] lgs8gxx: lgs8gxx_read_status
[ 2480.475438] lgs8gxx: AFC = 5579 kHz
[ 2480.476379] lgs8gxx: Reg 0x4B: 0x02
[ 2480.476380] lgs8gxx: lgs8gxx_read_status: fe_status=0x0
may be an error in the driver, or an error in the frontend.c. have to
compare both logs from 3.2 and 3.4.
--
http://chanchoiwing.blogspot.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: DiBcom adapter problems
2012-06-22 12:15 ` Zhu Sha Zang
@ 2012-06-22 14:10 ` Olivier GRENIE
0 siblings, 0 replies; 10+ messages in thread
From: Olivier GRENIE @ 2012-06-22 14:10 UTC (permalink / raw)
To: Zhu Sha Zang, linux-media
You need to get the source code of your kernel, apply the path and recompile the kernel. There is another solution by compiling the module externally (http://git.linuxtv.org/media_build.git). You will also need to patch it.
regards,
Olivier
________________________________________
From: Zhu Sha Zang [zhushazang@gmail.com]
Sent: Friday, June 22, 2012 2:15 PM
To: linux-media@vger.kernel.org
Cc: Olivier GRENIE
Subject: Re: DiBcom adapter problems
Excuse me, dumb question, but where and how can i apply this patch?
Thanks again!
Em 21-06-2012 14:07, Olivier GRENIE escreveu:
> Hello,
> can you test the following patch.
>
> regards,
> Olivier
>
> From: Olivier Grenie <olivier.grenie@parrot.com>
> Date: Thu, 21 Jun 2012 18:57:14 +0200
> Subject: [PATCH] [media] dvb frontend core: tuning in ISDB-T using DVB API v3
> The intend of this patch is to be able to tune ISDB-T using
> the DVB API v3
>
> Signed-off-by: Olivier Grenie <olivier.grenie@parrot.com>
> ---
> drivers/media/dvb/dvb-core/dvb_frontend.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/media/dvb/dvb-core/dvb_frontend.c b/drivers/media/dvb/dvb-core/dvb_frontend.c
> index aebcdf2..ee1cc10 100644
> --- a/drivers/media/dvb/dvb-core/dvb_frontend.c
> +++ b/drivers/media/dvb/dvb-core/dvb_frontend.c
> @@ -1531,6 +1531,13 @@ static int set_delivery_system(struct dvb_frontend *fe, u32 desired_system)
> delsys = desired_system;
> break;
> }
> +
> + /* check if the fe delivery system corresponds
> + to the delivery system in cache */
> + if (fe->ops.delsys[ncaps] == c->delivery_system) {
> + delsys = c->delivery_system;
> + break;
> + }
> ncaps++;
> }
> if (delsys == SYS_UNDEFINED) {
>
--
---
Rodolfo Timóteo da Silva
Linux Counter: 359362
msn: zhushazang@gmail.com
skype: zhushazang
Ribeirão Preto - SP
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: DiBcom adapter problems
2012-06-21 17:07 ` Olivier GRENIE
@ 2012-06-22 12:15 ` Zhu Sha Zang
2012-06-22 14:10 ` Olivier GRENIE
0 siblings, 1 reply; 10+ messages in thread
From: Zhu Sha Zang @ 2012-06-22 12:15 UTC (permalink / raw)
To: linux-media; +Cc: Olivier GRENIE
Excuse me, dumb question, but where and how can i apply this patch?
Thanks again!
Em 21-06-2012 14:07, Olivier GRENIE escreveu:
> Hello,
> can you test the following patch.
>
> regards,
> Olivier
>
> From: Olivier Grenie <olivier.grenie@parrot.com>
> Date: Thu, 21 Jun 2012 18:57:14 +0200
> Subject: [PATCH] [media] dvb frontend core: tuning in ISDB-T using DVB API v3
> The intend of this patch is to be able to tune ISDB-T using
> the DVB API v3
>
> Signed-off-by: Olivier Grenie <olivier.grenie@parrot.com>
> ---
> drivers/media/dvb/dvb-core/dvb_frontend.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/media/dvb/dvb-core/dvb_frontend.c b/drivers/media/dvb/dvb-core/dvb_frontend.c
> index aebcdf2..ee1cc10 100644
> --- a/drivers/media/dvb/dvb-core/dvb_frontend.c
> +++ b/drivers/media/dvb/dvb-core/dvb_frontend.c
> @@ -1531,6 +1531,13 @@ static int set_delivery_system(struct dvb_frontend *fe, u32 desired_system)
> delsys = desired_system;
> break;
> }
> +
> + /* check if the fe delivery system corresponds
> + to the delivery system in cache */
> + if (fe->ops.delsys[ncaps] == c->delivery_system) {
> + delsys = c->delivery_system;
> + break;
> + }
> ncaps++;
> }
> if (delsys == SYS_UNDEFINED) {
>
--
---
Rodolfo Timóteo da Silva
Linux Counter: 359362
msn: zhushazang@gmail.com
skype: zhushazang
Ribeirão Preto - SP
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: DiBcom adapter problems
2012-06-21 12:59 ` Zhu Sha Zang
@ 2012-06-21 17:07 ` Olivier GRENIE
2012-06-22 12:15 ` Zhu Sha Zang
0 siblings, 1 reply; 10+ messages in thread
From: Olivier GRENIE @ 2012-06-21 17:07 UTC (permalink / raw)
To: Zhu Sha Zang, linux-media
Hello,
can you test the following patch.
regards,
Olivier
From: Olivier Grenie <olivier.grenie@parrot.com>
Date: Thu, 21 Jun 2012 18:57:14 +0200
Subject: [PATCH] [media] dvb frontend core: tuning in ISDB-T using DVB API v3
The intend of this patch is to be able to tune ISDB-T using
the DVB API v3
Signed-off-by: Olivier Grenie <olivier.grenie@parrot.com>
---
drivers/media/dvb/dvb-core/dvb_frontend.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/media/dvb/dvb-core/dvb_frontend.c b/drivers/media/dvb/dvb-core/dvb_frontend.c
index aebcdf2..ee1cc10 100644
--- a/drivers/media/dvb/dvb-core/dvb_frontend.c
+++ b/drivers/media/dvb/dvb-core/dvb_frontend.c
@@ -1531,6 +1531,13 @@ static int set_delivery_system(struct dvb_frontend *fe, u32 desired_system)
delsys = desired_system;
break;
}
+
+ /* check if the fe delivery system corresponds
+ to the delivery system in cache */
+ if (fe->ops.delsys[ncaps] == c->delivery_system) {
+ delsys = c->delivery_system;
+ break;
+ }
ncaps++;
}
if (delsys == SYS_UNDEFINED) {
--
1.7.9.5
________________________________________
From: Zhu Sha Zang [zhushazang@gmail.com]
Sent: Thursday, June 21, 2012 2:59 PM
To: linux-media@vger.kernel.org
Cc: Olivier GRENIE
Subject: Re: DiBcom adapter problems
Ok, my kernel versions are 3.4.2 and 3.4.3.
The apps used to tune are
media-tv/w_scan - http://wirbel.htpc-forum.de/w_scan/index2.html
media-tv/linuxtv-dvb-apps (dvbscan) - http://www.linuxtv.org/
media-video/vlc - http://www.videolan.org/vlc/
media-video/kaffeine - http://kaffeine.kde.org/
A six month later i've already created a channels.conf and still working
with vlc.
A question: How to set debug parameter using modprobe?
Something like, "modrobe dib8000 debug=1; modprobe dvb-core debug=1"?
Thanks for now.
Em 19-06-2012 12:43, Olivier GRENIE escreveu:
> Hello,
> can you provide more information:
> - kernel version
> - more log information (not only the error message but also the log from the beginning, when you plug the device) with:
> * the debug parameter of the dib8000 module set to 1
> * the frontend_debug parameter of the dvb-core module set to 1
> - which application do you use to tune the board
>
> regards,
> Olivier
> ________________________________________
> From: linux-media-owner@vger.kernel.org [linux-media-owner@vger.kernel.org] On Behalf Of Rodolfo Timoteo da Silva [zhushazang@gmail.com]
> Sent: Sunday, June 17, 2012 3:58 PM
> To: linux-media@vger.kernel.org
> Subject: DiBcom adapter problems
>
> Hi, every time that i try to syntonize DVB-T channels i receive a
> message in kernel like in log1.txt arch.
>
> There are in log2.txt some usefull information about the device.
>
> My kernel/system is:
>
>
> Linux version 3.4.2-gentoo-r1-asgard (root@asgard) (gcc version 4.6.3
> (Gentoo 4.6.3 p1.3, pie-0.5.2) ) #1 SMP PREEMPT Thu Jun 14 07:45:19 BRT 2012
>
> Best Regards
>
--
---
Rodolfo Timóteo da Silva
Linux Counter: 359362
msn: zhushazang@gmail.com
skype: zhushazang
Ribeirão Preto - SP
^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: DiBcom adapter problems
2012-06-19 15:43 ` Olivier GRENIE
@ 2012-06-21 12:59 ` Zhu Sha Zang
2012-06-21 17:07 ` Olivier GRENIE
0 siblings, 1 reply; 10+ messages in thread
From: Zhu Sha Zang @ 2012-06-21 12:59 UTC (permalink / raw)
To: linux-media; +Cc: Olivier GRENIE
[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]
Ok, my kernel versions are 3.4.2 and 3.4.3.
The apps used to tune are
media-tv/w_scan - http://wirbel.htpc-forum.de/w_scan/index2.html
media-tv/linuxtv-dvb-apps (dvbscan) - http://www.linuxtv.org/
media-video/vlc - http://www.videolan.org/vlc/
media-video/kaffeine - http://kaffeine.kde.org/
A six month later i've already created a channels.conf and still working
with vlc.
A question: How to set debug parameter using modprobe?
Something like, "modrobe dib8000 debug=1; modprobe dvb-core debug=1"?
Thanks for now.
Em 19-06-2012 12:43, Olivier GRENIE escreveu:
> Hello,
> can you provide more information:
> - kernel version
> - more log information (not only the error message but also the log from the beginning, when you plug the device) with:
> * the debug parameter of the dib8000 module set to 1
> * the frontend_debug parameter of the dvb-core module set to 1
> - which application do you use to tune the board
>
> regards,
> Olivier
> ________________________________________
> From: linux-media-owner@vger.kernel.org [linux-media-owner@vger.kernel.org] On Behalf Of Rodolfo Timoteo da Silva [zhushazang@gmail.com]
> Sent: Sunday, June 17, 2012 3:58 PM
> To: linux-media@vger.kernel.org
> Subject: DiBcom adapter problems
>
> Hi, every time that i try to syntonize DVB-T channels i receive a
> message in kernel like in log1.txt arch.
>
> There are in log2.txt some usefull information about the device.
>
> My kernel/system is:
>
>
> Linux version 3.4.2-gentoo-r1-asgard (root@asgard) (gcc version 4.6.3
> (Gentoo 4.6.3 p1.3, pie-0.5.2) ) #1 SMP PREEMPT Thu Jun 14 07:45:19 BRT 2012
>
> Best Regards
>
--
---
Rodolfo Timóteo da Silva
Linux Counter: 359362
msn: zhushazang@gmail.com
skype: zhushazang
Ribeirão Preto - SP
[-- Attachment #2: channel.conf --]
[-- Type: text/plain, Size: 595 bytes --]
TV CLUBE HD:485142857:INVERSION_AUTO:BANDWIDTH_6_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE:0:0:59776
TV CLUBE MOVEL:485142857:INVERSION_AUTO:BANDWIDTH_6_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE:0:0:59800
EP HD:641142857:INVERSION_AUTO:BANDWIDTH_6_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE:273:274:59520
EPTV1Seg:641142857:INVERSION_AUTO:BANDWIDTH_6_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE:529:530:59544
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: DiBcom adapter problems
2012-06-17 13:58 Rodolfo Timoteo da Silva
@ 2012-06-19 15:43 ` Olivier GRENIE
2012-06-21 12:59 ` Zhu Sha Zang
0 siblings, 1 reply; 10+ messages in thread
From: Olivier GRENIE @ 2012-06-19 15:43 UTC (permalink / raw)
To: Rodolfo Timoteo da Silva, linux-media
Hello,
can you provide more information:
- kernel version
- more log information (not only the error message but also the log from the beginning, when you plug the device) with:
* the debug parameter of the dib8000 module set to 1
* the frontend_debug parameter of the dvb-core module set to 1
- which application do you use to tune the board
regards,
Olivier
________________________________________
From: linux-media-owner@vger.kernel.org [linux-media-owner@vger.kernel.org] On Behalf Of Rodolfo Timoteo da Silva [zhushazang@gmail.com]
Sent: Sunday, June 17, 2012 3:58 PM
To: linux-media@vger.kernel.org
Subject: DiBcom adapter problems
Hi, every time that i try to syntonize DVB-T channels i receive a
message in kernel like in log1.txt arch.
There are in log2.txt some usefull information about the device.
My kernel/system is:
Linux version 3.4.2-gentoo-r1-asgard (root@asgard) (gcc version 4.6.3
(Gentoo 4.6.3 p1.3, pie-0.5.2) ) #1 SMP PREEMPT Thu Jun 14 07:45:19 BRT 2012
Best Regards
^ permalink raw reply [flat|nested] 10+ messages in thread
* DiBcom adapter problems
@ 2012-06-17 13:58 Rodolfo Timoteo da Silva
2012-06-19 15:43 ` Olivier GRENIE
0 siblings, 1 reply; 10+ messages in thread
From: Rodolfo Timoteo da Silva @ 2012-06-17 13:58 UTC (permalink / raw)
To: linux-media
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
Hi, every time that i try to syntonize DVB-T channels i receive a
message in kernel like in log1.txt arch.
There are in log2.txt some usefull information about the device.
My kernel/system is:
Linux version 3.4.2-gentoo-r1-asgard (root@asgard) (gcc version 4.6.3
(Gentoo 4.6.3 p1.3, pie-0.5.2) ) #1 SMP PREEMPT Thu Jun 14 07:45:19 BRT 2012
Best Regards
[-- Attachment #2: log1.txt --]
[-- Type: text/plain, Size: 20132 bytes --]
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0
dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0
dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
[-- Attachment #3: log2.txt --]
[-- Type: text/plain, Size: 4234 bytes --]
usb 2-1.2: new high-speed USB device number 4 using ehci_hcd
usb 2-1.2: New USB device found, idVendor=10b8, idProduct=1fa0
usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.2: Product: STK8096GP
usb 2-1.2: Manufacturer: DiBcom
usb 2-1.2: SerialNumber: 1
dvb-usb: found a 'DiBcom STK8096GP reference design' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
dib0700: firmware started successfully.
dvb-usb: found a 'DiBcom STK8096GP reference design' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (DiBcom STK8096GP reference design)
DVB: registering adapter 0 frontend 0 (DiBcom 8000 ISDB-T)...
DiB0090: successfully identified
Registered IR keymap rc-dib0700-rc5
input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/rc/rc0/input14
rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/rc/rc0
dvb-usb: schedule remote query interval to 50 msecs.
dvb-usb: DiBcom STK8096GP reference design successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_dib0700
Bus 002 Device 004: ID 10b8:1fa0 DiBcom
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x10b8 DiBcom
idProduct 0x1fa0
bcdDevice 1.00
iManufacturer 1 DiBcom
iProduct 2 STK8096GP
iSerial 3 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 46
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2012-06-26 18:41 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-06-17 15:24 DiBcom adapter problems Rodolfo Timoteo da Silva
-- strict thread matches above, loose matches on Subject: below --
2012-06-26 18:41 Choi Wing Chan
2012-06-23 22:06 Choi Wing Chan
2012-06-26 10:25 ` Olivier GRENIE
2012-06-17 13:58 Rodolfo Timoteo da Silva
2012-06-19 15:43 ` Olivier GRENIE
2012-06-21 12:59 ` Zhu Sha Zang
2012-06-21 17:07 ` Olivier GRENIE
2012-06-22 12:15 ` Zhu Sha Zang
2012-06-22 14:10 ` Olivier GRENIE
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.