[vdr] Re: vdr & mandrake distro

[chris <chris-tux@wanadoo.fr>]

Le Vendredi 12 Mars 2004 16:37, chris a écrit :
well when I use vdr to run I get the following errors but when I start it with 
runvdr script; it is working ! Very impressive to watch an image!!
Still have a lot to understand...
If somebody can explain why I got this before...
TIA
> Le Jeudi 11 Mars 2004 08:30, Mak Addikt a écrit :
> > chris wrote:
> > >I have a lot of difficulties to compile properly vdr on a mdk 9.2
> > > distro. Has anyone succeded already?
> > >TIA for any support
> > >Chris
> >
> > Are  kernel sources installed on your distro ?
> > This is necessary
>
>  well here is how I compiled vdr, first I organized my  ~/bin like this:
> [chris@tux bin]$ ll
> total 8
> lrwxrwxrwx    1 chris    chris          21 mar 12 16:18 DVB ->
> linux-dvb.2003-11-08//
> drwxr-xr-x    6 chris    chris        4096 nov  8 17:10
> linux-dvb.2003-11-08/ lrwxrwxrwx    1 chris    chris           9 fév 21
> 18:58 VDR -> vdr-1.2.6/ drwxr-xr-x    4 chris    chris        4096 mar 12
> 16:25 vdr-1.2.6/ then I move in VDR and type make. I couldn't see any
> errors but I am not a specialist in this type of log file.
> Then I start vdr and got a segmentation fault
> Here is what /var/log/messages said
> mar 12 16:25:34 tux vdr[4100]: VDR version 1.2.6 started
> mar 12 16:25:35 tux vdr[4100]: loading /video/sources.conf
> mar 12 16:25:35 tux vdr[4100]: loading /video/diseqc.conf
> mar 12 16:25:35 tux vdr[4100]: loading /video/channels.conf
> mar 12 16:25:35 tux vdr[4100]: loading /video/svdrphosts.conf
> mar 12 16:25:35 tux vdr[4100]: loading /video/ca.conf
> mar 12 16:25:35 tux vdr[4100]: loading /video/keymacros.conf
> Mar 12 16:25:35 tux kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000ed8
> Mar 12 16:25:35 tux kernel:  printing eip:
> Mar 12 16:25:35 tux kernel: d0e100e9
> Mar 12 16:25:35 tux kernel: *pde = 00000000
> Mar 12 16:25:35 tux kernel: Oops: 0000
> Mar 12 16:25:35 tux kernel: dvb-ttpci alps_bsrv2 alps_tdmb7 alps_tdlb7
> grundig_29504-401 grundig_29504-491 stv0299 ves1820 dvb-core videodev input
> parport_pc lp parport ipt_TOS ipt_REJECT ipt_LOG ipt_state ip_nat_irc
> ip_nat_tftp ip_nat_ftp ip_conntrack_irc ip_conntrack_tftp ip_conntrack_ftp
> ipt_multiport ipt_conntrack iptable_filter iptable_mangle iptable_nat
> ip_conntrack ip_tables snd-seq-midi snd-seq-oss snd-seq-midi-event snd-seq
> snd-pcm-oss snd-mixer-oss snd-au8810 snd-pcm snd-page-alloc snd-timer
> gameport snd-mpu401-uart snd-rawmidi snd-seq-device snd-ac97-codec snd
> soundcore af_packet floppy tulip sd_mod sr_mod scsimon usb-storage
> supermount ide-cd cdrom ide-scsi scsi_mod usb-uhci usbcore rtc ext3 jbd
> Mar 12 16:25:35 tux kernel: CPU:    0
> Mar 12 16:25:35 tux kernel: EIP:
> 0010:[usb-storage:transferred+2285413/93338509]    Not tainted
> Mar 12 16:25:35 tux kernel: EIP:    0010:[<d0e100e9>]    Not tainted
> Mar 12 16:25:35 tux kernel: EFLAGS: 00210046
> Mar 12 16:25:35 tux kernel: EIP is at dvb_video_open+0x29/0xb0 [dvb-ttpci]
> Mar 12 16:25:35 tux kernel: eax: 00000000   ebx: 00000000   ecx: cab62c60
> edx: 00000ed0
> Mar 12 16:25:35 tux kernel: esi: cab62c60   edi: c53bebe0   ebp: c53b7f28
> esp: c53b7f20
> Mar 12 16:25:35 tux kernel: ds: 0018   es: 0018   ss: 0018
> Mar 12 16:25:35 tux kernel: Process vdr (pid: 4100, stackpage=c53b7000)
> Mar 12 16:25:35 tux kernel: Stack: ca750a40 c53bebe0 c53b7f4c c0233f40
> c53bebe0 cab62c60 c015fca0 ca750a48
> Mar 12 16:25:35 tux kernel:        cab62c60 c53bebe0 00000000 c53b7f68
> c0200844 c53bebe0 cab62c60 00000802
> Mar 12 16:25:35 tux kernel:        ca15f000 00000004 c53b7fa0 c02006ae
> c4779e60 c12cf320 00000802 c4779e60
> Mar 12 16:25:35 tux kernel: Call Trace:
> Mar 12 16:25:35 tux kernel:  [devfs_open+304/432] devfs_open+0x130/0x1b0
> [kernel]
> Mar 12 16:25:35 tux kernel:  [<c0233f40>] devfs_open+0x130/0x1b0 [kernel]
> Mar 12 16:25:35 tux kernel:  [dentry_open+388/464] dentry_open+0x184/0x1d0
> [kernel]
> Mar 12 16:25:35 tux kernel:  [<c0200844>] dentry_open+0x184/0x1d0 [kernel]
> Mar 12 16:25:35 tux kernel:  [filp_open+78/96] filp_open+0x4e/0x60 [kernel]
> Mar 12 16:25:35 tux kernel:  [<c02006ae>] filp_open+0x4e/0x60 [kernel]
> Mar 12 16:25:35 tux kernel:  [sys_open+61/144] sys_open+0x3d/0x90 [kernel]
> Mar 12 16:25:35 tux kernel:  [<c0200a5d>] sys_open+0x3d/0x90 [kernel]
> Mar 12 16:25:35 tux kernel:  [system_call+51/64] system_call+0x33/0x40
> [kernel]
> Mar 12 16:25:35 tux kernel:  [<c01c4333>] system_call+0x33/0x40 [kernel]
> Mar 12 16:25:35 tux kernel:
> Mar 12 16:25:35 tux kernel: Code: 8b 42 08 89 42 0c fb ba 03 00 00 00 8d 83
> e0 0e 00 00 b9 01
>
> This is too much for me. Please note that I have a perfect image with
> dvb-szap. The only particularity is that I used the rpm package of driver
> made by guido draheim. Does the sources of the dvb-driver parallel to the
> VDR sources need to be of the same version of the installed driver ?
> Anyway, I used the sources of different version of dvb-driver with no
> success. TIA
> Chris



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.