[vdr] segmentation fault immediately after start of vdr

[Walter Schittek <waltersch@gmx.net>]

Hi,

I am trying my first installation of vdr and am not able to get it 
running. Every time I start it, it only says "segmentation fault" and 
terminates immediately. I suppose that I have made something wrong or 
omitted something that is selfunderstood for all of you, but not for me 
as a beginner.

The DVB driver seems to work; I can use szap and xawtv with my DVB card.

Now, I will tell you every step I made in installing the DVB driver and 
vdr, so that you hopefully can see what went wrong:

I have one single DVB-s card: Hauppauge WinTV Nexus-s rev. 2.1 (model 
564) with Tuner Alps BSRU6 and Philips SAA7146A Chip.
I have made sure that it uses an IRQ (11) that is not shared. For that, 
I needed to deactivate USB in BIOS setup.
I am working with SuSE kernel 2.4.19-4GB. I have not yet compiled a new 
kernel, but the kernel has
    Video4Linux Support (CONFIG_VIDEODEV),
    Input Core Support (CONFIG_INPUT) and
    Event Device Support (CONFIG_INPUT_EVDEV)
already enabled.
I also made
cp /boot/vmlinuz.config /usr/src/linux/.config
cd /usr/src/linux
make oldconfig
make dep

I downloaded the DVB driver linux-dvb.2003-06-08.tar.bz2 from the VDR 
site (http://www.cadsoft.de/people/kls/vdr/download.htm)

I unpacked it into /usr/local/src/ and made a symbolic link from 
directory linux-dvb.2003-06-08 to DVB.

I changed into directory DVB/driver and made
export TOPDIR=/lib/modules/2.4.19-4GB/build
     (if I don't do that, I get an error message "TOPDIR: parameter 
null or not set")
make
./makedev.napi
make insmod

I tested the DVB driver with szap and xawtv, and it works. (The vdr 
problem occurs when I previously used szap/xawtv and also when I made a 
PC restart and new compilation of the driver.)

I downloaded the VDR source vdr-1.2.1.tar.bz2 from the VDR site.
I unpacked it into /usr/local/src/ and made a symbolic link from 
directory vdr-1.2.1 to VDR.

I changed into directory VDR and made
make REMOTE=LIRC
make install

I made sure that the .conf files were in the directory /video, which is 
on a separate partition:
ls /video
.   ca.conf        diseqc.conf     lost+found    svdrphosts.conf
..  channels.conf  keymacros.conf  sources.conf

Working as "root", in directory /usr/local/src/VDR I enter
./vdr     and get
Segmentation fault
and vdr terminates.

Here are the parts of /var/log/messages:
a) after make insmod for the driver:

kernel: Linux video capture interface: v1.00
kernel: DVB: registering new adapter (Technotrend/Hauppauge PCI rev2.1 
or 2.2).
kernel: PCI: Found IRQ 11 for device 01:0b.0
kernel: saa7146_core.o: adjusting pci latency to 64
kernel: stv0299.c: setup for tuner BSRU6, TDQB-S00x
kernel: DVB: registering frontend 0:0 (STV0299/TSA5059/SL1935 based)...
kernel: DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app 
80002616
kernel: DVB: AV7111(0) - firmware supports CI link layer interface
kernel: av7110(0): adac type set to 0

b) when starting vdr:

vdr[2861]: VDR version 1.2.1 started
vdr[2861]: loading /video/sources.conf
vdr[2861]: loading /video/diseqc.conf
vdr[2861]: loading /video/channels.conf
vdr[2861]: loading /video/svdrphosts.conf
vdr[2861]: loading /video/ca.conf
vdr[2861]: loading /video/keymacros.conf
vdr[2861]: probing /dev/dvb/adapter0/frontend0
vdr[2864]: EIT processing thread started (pid=2864) - master
kernel: Unable to handle kernel NULL pointer dereference at virtual 
address 00000000
kernel:  printing eip:
kernel: 00000000
kernel: *pde = 00000000
kernel: Oops: 0000 2.4.19-4GB #1 Mon Oct 14 22:11:39 UTC 2002
kernel: CPU:    0
kernel: EIP:    0010:[<00000000>]    Tainted: P
kernel: EFLAGS: 00010282
kernel: eax: e15b0064   ebx: e15b0000   ecx: c6f83fa8   edx: ffffffea
kernel: esi: ca87dbc0   edi: 00000000   ebp: 00000000   esp: c6f83f0c
kernel: ds: 0018   es: 0018   ss: 0018
kernel: Process vdr (pid: 2864, stackpage=c6f83000)
kernel: Stack: c5161439 ca87dbc0 e15b0064 c6f83fa8 00000145 c6cfd000 
ca87dbc0 c0152c80
kernel:        ca87dbc0 c6f83fa8 00000000 40a869ac 00000000 00000000 
c0152d6c 00000006
kernel:        c6cfd000 c6f83f60 c6f83f64 c6f82000 c6f82000 c6f83fa8 
00000000 000001f0
kernel: Call Trace: 
[parport_pc:__insmod_parport_pc_O/lib/modules/2.4.19-4GB/kernel/drivers+-361950151/96] 
[do_pollfd+128/144] [do_poll+220/240] [sys_poll+340/720] [sys_time+17/80]
kernel: Call Trace:    [<c5161439>] [<c0152c80>] [<c0152d6c>] 
[<c0152ed4>] [<c01225c1>]
kernel:   [system_call+51/64]
kernel:   [<c0108e63>]
kernel: Modules: [(dvb-core:<c5160060>:<c5169764>)]
kernel: Code:  Bad EIP value.

Additional informations:

Since I built the DVB card into my PC, /var/log/messages contains the 
following line after each start of the PC:
modprobe: Can't locate module char-major-81-0

char-major-81 is videodev, and char-major-81-0 seems to belong to the 
first DVB card. I always supposed that it's not important, because the 
DVB driver must be activated by "make" and "make insmod" after each 
start of the PC. Thus, it's understandable that the driver for the DVB 
card is not found at PC start.

I have not yet connected the DVB card to my TV, because I wanted to 
first test vdr at the PC. I will have to buy a cable and to get it 
(together with the remote control cable) through a wall, before I can 
test it with the TV.

I also tested vdr version 1.1.26 in the same way to be sure that it's 
not a bug in the actual vdr version. The result is the same.

If you need any more informations from me or want to ask me to make an 
additional test, please ask me privately (besides the list). I will 
bring the results to the list.

Thanks!

Walter



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