Thema: Linux-Kernel 2.6.8 verfügbar, ves1x93 probs

[schorpp]

Aug 19 08:48:38 tom1 kernel: saa7146: register extension 'dvb'.
Aug 19 08:48:38 tom1 kernel: ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 11 (level, low) -> IRQ 11
Aug 19 08:48:38 tom1 kernel: saa7146: found saa7146 @ mem e09bb000 (revision 1, irq 11) (0x13c2,0x0000).
Aug 19 08:48:38 tom1 kernel: DVB: registering new adapter (Siemens/Technotrend/Hauppauge PCI rev1.3).
Aug 19 08:48:38 tom1 kernel: Siemens/Technotrend/Hauppauge PCI rev1.3 adapter 0 has MAC addr = 00:d0:5c:01:13:31
Aug 19 08:48:38 tom1 kernel: gpioirq unknown type=0 len=0
Aug 19 08:48:38 tom1 kernel: DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261c
Aug 19 08:48:38 tom1 kernel: DVB: AV7111(0) - firmware supports CI link layer interface
Aug 19 08:48:38 tom1 kernel: av7110(0): adac type set to 0
Aug 19 08:48:38 tom1 kernel: videodev: "av7110" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/
Aug 19 08:48:38 tom1 kernel: saa7146_vv: saa7146 (0): registered device video0 [v4l2]
Aug 19 08:48:38 tom1 kernel: av7110: found av7110-0.
Aug 19 08:48:38 tom1 input.agent[9434]:      evbug: blacklisted
Aug 19 08:48:38 tom1 input.agent[9434]:      evdev: already loaded
Aug 19 08:48:38 tom1 input.agent[9438]:      evbug: blacklisted
Aug 19 08:48:38 tom1 input.agent[9438]:      evdev: already loaded
Aug 19 08:49:33 tom1 kernel: ves1x93: Detected ves1893a rev2
Aug 19 08:49:33 tom1 kernel: DVB: registering frontend 0:0 (VES1893)...


tom1:~# femon
using '/dev/dvb/adapter0/frontend0'
opening frontend failed: No such device or address
tom1:~#

Aug 19 08:59:50 tom1 vdr[9507]: ERROR: /dev/dvb/adapter0/frontend0: No such device or address
Aug 19 08:59:50 tom1 vdr[9507]: no DVB device found


tom1:~# ls -l /dev/dvb/adapter0
total 0
crw-rw----  1 root video 250, 1 Aug 18 15:48 audio0
crw-rw----  1 root video 250, 6 Aug 18 15:48 ca0
crw-rw----  1 root video 250, 4 Aug 18 15:48 demux0
crw-rw----  1 root video 250, 5 Aug 18 15:48 dvr0
crw-rw----  1 root video 250, 3 Aug 18 15:48 frontend0
crw-rw----  1 root video 250, 7 Aug 18 15:48 net0
crw-rw----  1 root video 250, 8 Aug 18 15:48 osd0
crw-rw----  1 root video 250, 0 Aug 18 15:48 video0
tom1:~#

aufm 2.4.25 gehts, ich schreibs hier wenns behoben ist...

[schorpp]

 Hallo :-)

wenn ihr nach Umstellung auf Kernel 2.6.8.1 der VDR kein Device mehr findet, liegt es daran das die Major Devicenummer gändert wurde.

Alt: 250

Neu : 212

Frank

Hier das abgeänderte MAKEDEV-DVB.sh Script

#!/bin/sh
# Create device nodes for the Linux DVB API with DVB_API_VERSION 2.
# The devices created are suitable for most current PC DVB cards,
# i.e. cards having one frontend, one demux and optionally one
# MPEG decoder.
# The script creates devices for four cards by default.

if [ -e /dev/.devfsd ]; then
echo "It seems you are using devfs. Good!"
exit 0
fi

# get rid of old DVB API devices; do it twice for good measure...
rm -rf /dev/ost
rm -rf /dev/ost
rm -rf /dev/dvb
rm -rf /dev/dvb

mkdir /dev/dvb
chmod 755 /dev/dvb

for i in `seq 0 3`; do
echo "Creating DVB devices in /dev/dvb/adapter$i"
mkdir /dev/dvb/adapter$i
chmod 755 /dev/dvb/adapter$i
mknod -m 0660 /dev/dvb/adapter$i/video0 c 212 `expr 64 \* $i + 0`
mknod -m 0660 /dev/dvb/adapter$i/audio0 c 212 `expr 64 \* $i + 1`
mknod -m 0660 /dev/dvb/adapter$i/frontend0 c 212 `expr 64 \* $i + 3`
mknod -m 0660 /dev/dvb/adapter$i/demux0 c 212 `expr 64 \* $i + 4`
mknod -m 0660 /dev/dvb/adapter$i/dvr0 c 212 `expr 64 \* $i + 5`
mknod -m 0660 /dev/dvb/adapter$i/ca0 c 212 `expr 64 \* $i + 6`
mknod -m 0660 /dev/dvb/adapter$i/net0 c 212 `expr 64 \* $i + 7`
mknod -m 0660 /dev/dvb/adapter$i/osd0 c 212 `expr 64 \* $i + 8`
chown root.video /dev/dvb/adapter$i/*
done

[schorpp]

wer ne tt/siemens rev 1.3 dvbs hat, und unter "bild-tonunterbrechungen" leidet, bitte letztes kernel-dvb cvs von linuxtv.org nehmen oder das hier rein:

Das Problem ist schon gelöst:

--- ../linux/drivers/media/dvb/frontends/ves1x93.c.001  2004-08-25 21:27:08.000000000 +0200
+++ ../linux/drivers/media/dvb/frontends/ves1x93.c      2004-09-12 16:30:54.000000000 +0200
@@ -453,6 +453,21 @@
                fe_status_t *status = arg;
                u8 sync = ves1x93_readreg (i2c, 0x0e);
 
+               /*
+                * The ves1893 sometimes returns sync values that make no sense,
+                * because, e.g., the SIGNAL bit is 0, while some of the higher
+                * bits are 1 (and how can there be a CARRIER w/o a SIGNAL?).
+                * Tests showed that the the VITERBI and SYNC bits are returned
+                * reliably, while the SIGNAL and CARRIER bits ar sometimes wrong.
+                * If such a case occurs, we read the value again, until we get a
+                * valid value.
+                */
+               int maxtry = 10; /* just for safety - let's not get stuck here */
+               while ((sync & 0x03) != 0x03 && (sync & 0x0c) && maxtry--) {
+                       msleep(10);
+                       sync = ves1x93_readreg (i2c, 0x0e);
+               }
+
                *status = 0;
 
                if (sync & 1)

verm. c) klaus schmidinger, vdr