Hi have a severe problem with the latest patches (sent to me by Abraham) for the Twinhan DVB cards. (Note for Manu: I compiled the tree named "17 Feb 05 Twinhan FE") With a stock 2.6.10 kernel the drivers successfully registers the frontend, but then some applications don't work due to FE_DISEQC_SEND_BURST. With the patches I get: bttv0: Bt878 (rev 17) at 0000:01:09.0, irq: 5, latency: 32, mmio: 0xd4000000 bttv0: detected: Twinhan VisionPlus DVB-T [card=113], PCI subsystem ID is 1822:0001 bttv0: using: Twinhan DST + clones [card=113,autodetected] bttv0: gpio: en=00000000, out=00000000 in=00f500ff [init] bttv0: using tuner=4 bttv0: add subdevice "dvb0" bt878: AUDIO driver version 0.0.0 loaded bt878: Bt878 AUDIO function found (0). DVB: registering new adapter (bttv0). DVB: registering frontend 0 (<NULL>)... newdeal:~# lsmod Module Size Used by dvb_bt8xx 11844 0 dst_ca 16464 1 dvb_bt8xx dvb_core 83176 2 dvb_bt8xx,dst_ca nxt6000 7236 1 dvb_bt8xx sp887x 8196 1 dvb_bt8xx cx24110 8260 1 dvb_bt8xx mt352 6980 1 dvb_bt8xx dst 18896 2 dvb_bt8xx,dst_ca bt878 10488 2 dvb_bt8xx,dst vmnet 30448 6 vmmon 49560 0 tuner 21796 0 bttv 153680 2 dvb_bt8xx,bt878 video_buf 22020 1 bttv v4l2_common 5760 1 bttv btcx_risc 4808 1 bttv videodev 9728 1 bttv lirc_serial 13344 1 lirc_dev 13836 1 lirc_serial 8139too 24832 0 forcedeth 17536 0 rtc 12664 0 And if I try to access to frontend0: scan Hotbird-13.0E scanning Hotbird-13.0E using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' Segmentation fault And on dmesg: Unable to handle kernel NULL pointer dereference at virtual address 000001ac printing eip: f8e2d40f *pde = 00000000 Oops: 0000 [#1] PREEMPT Modules linked in: dvb_bt8xx dst_ca dvb_core nxt6000 sp887x cx24110 mt352 dst bt878 vmnet vmmon tuner bttv video_buf v4l2_common btcx_risc videodev lirc_serial lirc_dev 8139too forcedeth rtc CPU: 0 EIP: 0060:[<f8e2d40f>] Tainted: PF VLI EFLAGS: 00010246 (2.6.10) EIP is at dvb_frontend_start+0x1f/0x100 [dvb_core] eax: 00000000 ebx: 00000000 ecx: 00000000 edx: f65caa20 esi: f7180500 edi: f7180500 ebp: e79cdea8 esp: e79cde94 ds: 007b es: 007b ss: 0068 Process scan (pid: 3654, threadinfo=e79cc000 task=e79b6500) Stack: 00000000 e79cdeb0 c0159e72 00000000 e77b5060 e79cdec8 f8e2dbd7 f7180500 e77b5060 00000000 f65caa20 f8e383e0 e77b5060 e79cdeec f8e25164 f777bdac e77b5060 00000001 00000000 e77b5060 f8e38460 00000000 e79cdf18 c015a022 Call Trace: [<c010344f>] show_stack+0x7f/0xa0 [<c01035ea>] show_registers+0x15a/0x1c0 [<c01037e0>] die+0xf0/0x180 [<c0111e2d>] do_page_fault+0x28d/0x63e [<c01030a7>] error_code+0x2b/0x30 [<f8e2dbd7>] dvb_frontend_open+0x57/0xa0 [dvb_core] [<f8e25164>] dvb_device_open+0xf4/0x1c0 [dvb_core] [<c015a022>] chrdev_open+0xf2/0x1e0 [<c01502a6>] dentry_open+0x146/0x230 [<c015015b>] filp_open+0x5b/0x60 [<c0150556>] sys_open+0x46/0x90 [<c0102693>] syscall_call+0x7/0xb Code: 9e 2e c7 e9 77 fe ff ff 8d 74 26 00 55 89 e5 83 ec 14 a1 d0 90 e3 f8 89 75 fc 89 5d f8 8b 75 08 85 c0 8b 5e 0c 0f 85 c2 00 00 00 <8b> 83 ac 01 00 00 85 c0 74 1e 8b 83 dc 01 00 00 85 c0 75 0c 31 Let me know what I can do to help the bugfixing process. Thanks, Roberto Sebastiano