Hi gang,
just received my Cinergy T2 saturday, and played with it on two
different systems, with very different results.
Both systems run Gentoo Linux, with kernel 2.6.11 and very
updated installations. The kernel configurations are different
as one system runs on a desktop PC, while the second is a
laptop. DVB kernel was pulled on May 15th, and was exactly the
same on the two systems.
Well, on the desktop system things seem to be working fine, the
T2 is recognized, tzap and femon report valid tuning data,
dvbscan finds the 1 only mux available here in Brussels, and I
have used the channels.conf data to successfully tune TV and
radio channels on the flemish VRT mux.
On the laptop unfortunately I get an oops when I attach the USB
cable to the laptop, there it is:
DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed
DVB-T Receiver).
Unable to handle kernel NULL pointer dereference at virtual
address 00000000
printing eip:
f8a2a365
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in: cinergyT2 dvb_core pcmcia aes_i586 airo
yenta_socket rsrc_nonstatic pcmcia_core ibm_acpi
CPU: 0
EIP: 0060:[<f8a2a365>] Not tainted VLI
EFLAGS: 00010246 (2.6.11-gentoo-r9)
EIP is at dvbdev_get_free_id+0x15/0x50 [dvb_core]
eax: f6ef2208 ebx: 00000004 ecx: f6ef2214 edx: 00000000
esi: 00000000 edi: 00000000 ebp: 00000004 esp: f6587e38
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 9821, threadinfo=f6586000 task=f6557a40)
Stack: f8a3c060 f6ef2234 f6ef2208 f8a2a3d6 f6ef2208 00000004
f6587e54 f644946c
f6ef2000 f6ef2234 00000000 f6ef2208 f8a3c060 f6ef2234
00000005 f8a3bfa0
f8a2c82c f6ef2208 f6ef2234 f8a3bfa0 f6ef2234 00000004
f6586000 00000100
Call Trace:
[<f8a2a3d6>] dvb_register_device+0x36/0x190 [dvb_core]
[<f8a2c82c>] dvb_dmxdev_init+0x19c/0x230 [dvb_core]
[<f8a2e7a8>] dvb_dmx_init+0x1d8/0x200 [dvb_core]
[<f8a191b1>] cinergyt2_probe+0x151/0x3f0 [cinergyT2]
[<c03261a0>] usb_probe_interface+0x70/0x90
[<c02c6d4f>] driver_probe_device+0x2f/0x80
[<c02c6e9c>] driver_attach+0x5c/0xa0
[<c02c73ed>] bus_add_driver+0x9d/0xd0
[<c02c7a0f>] driver_register+0x2f/0x40
[<c032629c>] usb_register+0x4c/0xb0
[<f887d013>] cinergyt2_init+0x13/0x5c [cinergyT2]
[<c0133927>] sys_init_module+0x187/0x240
[<c01031af>] syscall_call+0x7/0xb
Code: 18 89 04 24 e8 ed 03 00 00 83 c4 14 c3 89 f6 8d bc 27 00
00 00 00 57 56 31 f6 53 8b 44 24 10 8b 5c 24 14 8b 78 0c 8d 48
0c 89 fa <8b> 07 0f 18 00 90 39 cf 74 12 90 39 5a 10 74 12 89 c2
8b 00 0f
I have checked the thread about T2 oops I saw on this list a few
days ago, and I believe I have done things right as far as
modules and correct installation of the symlinks pointing to
dvb-kernel are concerned.
Thanks for letting me know what direction I should look to try
to fix this, as the performance of the Linux DVB driver is so
much better than what I get out on Windows, on the exact same
hardware but booted under Windows.
Thanks, Luca
