Re: [vdr] DVB-T card on the move
Udo Richter wrote:
Theunis Potgieter wrote:
udev rules
Any good rules that could be used as a starting point?
Since there's no working solution yet that really satisfied me, I've
digged into this, trying to get automatic persistent numbering of
/dev/dvb/adapterX to work.
My first attempt however failed due to race problems since several dvb
sub-devices appear almost at the same time, and the persistent rules
cannot be updated without difficult synchronization. But at least I want
to post some rules that can be set up manually:
Check the output of udevinfo -a -n /dev/dvb/adapter0/frontend0. Under
'parent device' you'll find something like this:
KERNELS==:00:13.0
SUBSYSTEMS==pci
USB devices will look like this:
KERNELS==4-1
SUBSYSTEMS==usb
With this, you can set up a rule like this:
ACTION==add, SUBSYSTEM==dvb, SUBSYSTEMS==pci,
KERNELS==:00:13.0, \
PROGRAM=/bin/sh -c 'K=%k; echo dvb/adapter0/$${K#dvb*.}', \
NAME=%c
Create a file /etc/udev/rules.d/025_persistent-dvb.rules and put the
rule into it. Do this for _ALL_ your DVB devices, and give each device a
different number in the rule (eg. replace echo dvb/adapter0 in the rule
with other numbers).
This works, as long as no unknown devices appear that could end up using
some adapter number twice.
Cheers,
Udo
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
Rainer Zocholl wrote: This unloading leads to ACPI interrupr errors On the VDR console i could see 3 line ACPI disabling interupt This is not an error. If a DVB driver is unloaded, its IRQ is unused and ACPI disables this IRQ line. As soon as the driver gets loaded again, the ACPI IRQ will be enabled again. For me, this is shown in syslog like this: kernel: ACPI: PCI interrupt for device :00:13.0 disabled kernel: saa7146: unregister extension 'budget dvb'. [...] kernel: ACPI: PCI Interrupt :00:13.0[A] - Link [LNKA] - GSI 11 (level, low) - IRQ 11 kernel: saa7146: register extension 'budget dvb'. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
Rainer Zocholl wrote: For who knows french, there is an interresting thread about udev on the dvbkivabien forum. I did use it to have my nexus always as primary device http://dvbkivabien2.info/viewtopic.php?f=21t=11255 Vous devez tre inscrit et connect pour pouvoir consulter le contenu de ce forum. I assume in english this would be translated as forget it :-( For those who are curious, there's a public login registered on bugmenot.com. Just use user=bugmenot pass=bugmenot. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
[EMAIL PROTECTED](Udo Richter) 16.02.08 12:12 Once upon a time Udo Richter shaped the electrons to say... Rainer Zocholl wrote: This unloading leads to ACPI interrupr errors On the VDR console i could see 3 line ACPI disabling interupt This is not an error. If a DVB driver is unloaded, its IRQ is unused and ACPI disables this IRQ line. Ah, thanks. good to know. As soon as the driver gets loaded again, the ACPI IRQ will be enabled again. For me, this is shown in syslog like this: kernel: ACPI: PCI interrupt for device :00:13.0 disabled kernel: saa7146: unregister extension 'budget dvb'. [...] kernel: ACPI: PCI Interrupt :00:13.0[A] - Link [LNKA] - GSI 11 (level, low) - IRQ 11 kernel: saa7146: register extension 'budget dvb'. So that does not explain the problem. Sad ;-( ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
(Halim Sahin) 06.02.08 in /SPAMDETEC:
Hi,
A dirty but working solution is to unload and load the modules in the
right order in startvdr skript.
Thanks, but
I tried it:
The results were very bad.
vdr do not cold start any more
The drivers/module do not seem to like been unloaded and
reloaded in the right order.
This unloading leads to ACPI interrupr errors
On the VDR console i could see 3 line
ACPI disabling interupt
tried using noacpi: do not help.
I really very frustrated as i ran the hard since years
with 1.4.3 without any problem.
(recently the new 500GB sata Samsung HD500 had developed a bad block)
Any help available?
a how-to
Or at least some one reading here? ;-)
Is see only a hardware solution:
Removing the DVB-T card!
I assume all other users will have done that way, as there seems to be
no *working* help anywhere! Atleat non to be found with teh word
i gave google/yahoo.
This patch sems to lead into a desaster (= no dvb found)
vdr:~# diff -Nau /usr/sbin/runvdr runvdr.mod
--- /usr/sbin/runvdr2008-01-14 21:56:11.0 +0100
+++ runvdr.mod 2008-02-14 23:22:35.0 +0100
@@ -19,6 +19,8 @@
MODULES=`lsmod | grep dvb-core | cut -d'[' -f2 | cut -d']' -f1`
[ $MODULES ] MODULES=$MODULES dvb-core
fi
+logger $MODULES
+
}
function set_permissions()
@@ -39,6 +41,8 @@
get_modulenames
else
if [ $MODULES ]; then
+modprobe dvb-ttpci /dev/null 21 #2.4
+modprobe dvb_ttpci /dev/null 21 #2.6
for MODULE in $MODULES; do
modprobe $MODULE /dev/null 21
done
@@ -67,9 +71,28 @@
VDR_ERR=`mktemp -p /tmp vdr-err.XX`
+
+#revolve that senseless automatic PrimaryDVB = 2
+grep -v ^PrimaryDVB /var/lib/vdr/setup.conf $VDR_ERR
+echo PrimaryDVB = 1 $VDR_ERR
+mv $VDR_ERR /var/lib/vdr/setup.conf
+:$VDR_ERR
+
+
get_modulenames
+logger -t runvdrz unload
+unload_dvb_modules
+sleep 2
+logger -t runvdrz unloaed
+lsmod | grep dvb | logger -t runvdrz
+
+logger -t runvdrz load
[ -z $MODULES ] load_dvb_modules
+logger -t runvdrz loadied
+lsmod | grep dvb | logger -t runvdrz
+
+ echo $MODULES | logger -t runvdrzm
if [ $VDSB_WORKAROUND = yes ] [ -x /usr/bin/szap ] ; then
channel=àwk '/^[^:]/ {print NR; exit}' /var/lib/vdr/channels.conf`
@@ -81,6 +104,7 @@
killall szap
fi
+
while (true) do
set_permissions
Feb 15 19:31:15 vdr runvdr: stopping after fatal fail (vdr: warning - cannot
set dumpable: Invalid argument vdr: error while reading
'/var/lib/vdr/setup.conf' vdr: no primary device found - using first device!)
Feb 15 19:32:00 vdr vdr: [4332] no DVB device found
Rainer
--
Transparency International definiert Korruption als
Missbrauch von anvertrauter Macht zum privaten Nutzen oder Vorteil. [...]
Corruption is operationally defined as the misuse of entrusted power for
private gain. [...]
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
[EMAIL PROTECTED](Udo Richter) 05.02.08 22:51 Theunis Potgieter wrote: udev rules Any good rules that could be used as a starting point? I thought of doing this with udev, but there are some obstacles for that: First, a DVB device has several device files, not just one. vdr:~# ll /dev/dvb/adapter0/ insgesamt 0 crw-rw 1 root video 212, 1 2008-02-11 20:19 audio0 crw-rw 1 root video 212, 6 2008-02-11 20:19 ca0 crw-rw 1 root video 212, 4 2008-02-11 20:19 demux0 crw-rw 1 root video 212, 5 2008-02-11 20:19 dvr0 crw-rw 1 root video 212, 3 2008-02-11 20:19 frontend0 crw-rw 1 root video 212, 7 2008-02-11 20:19 net0 crw-rw 1 root video 212, 8 2008-02-11 20:19 osd0 crw-rw 1 root video 212, 0 2008-02-11 20:19 video0 vdr:~# vdr:~# ll /dev/dvb/adapter1/ insgesamt 0 crw-rw 1 root video 212, 65 2008-02-11 20:19 audio0 crw-rw 1 root video 212, 70 2008-02-11 20:19 ca0 crw-rw 1 root video 212, 68 2008-02-11 20:19 demux0 crw-rw 1 root video 212, 69 2008-02-11 20:19 dvr0 crw-rw 1 root video 212, 67 2008-02-11 20:19 frontend0 crw-rw 1 root video 212, 71 2008-02-11 20:19 net0 crw-rw 1 root video 212, 72 2008-02-11 20:19 osd0 crw-rw 1 root video 212, 64 2008-02-11 20:19 video0 vdr:~# ll /dev/dvb/adapter3/ insgesamt 0 crw-rw 1 root video 212, 196 2008-02-11 20:42 demux0 crw-rw 1 root video 212, 197 2008-02-11 20:42 dvr0 crw-rw 1 root video 212, 195 2008-02-11 20:42 frontend0 crw-rw 1 root video 212, 199 2008-02-11 20:42 net0 And second, the usual trick to add a custom name as symlink doesn't work since VDR only accepts /dev/dvb/adapterX/, so /dev/dvb/myprimarycard/ is out. In setup.conf there is a variable: vdr:~# grep Prim /var/lib/vdr/setup.conf PrimaryDVB = 1 PrimaryLimit = 0 (PrimaryLimit seems to have no sense anymore?) What's the problem of a string there: PrimaryDVB = /dev/dvb/myprimarycard/ Currently there is stored where the last time the first FF card was found, what is not allways working good vdr:~# dmesg | grep frontend DVB: registering frontend 0 (Zarlink MT352 DVB-T)... DVB: registering frontend 1 (ST STV0299 DVB-S)... DVB: registering frontend 2 (ST STV0299 DVB-S)... DVB: registering frontend 3 (ST STV0299 DVB-S)... will lead to PrimaryDVB = 2 After fidling arround i could manage (somettimes) to get: vdr:~# dmesg | grep frontend DVB: registering frontend 0 (ST STV0299 DVB-S)... DVB: registering frontend 1 (ST STV0299 DVB-S)... DVB: registering frontend 2 (ST STV0299 DVB-S)... DVB: registering frontend 3 (Zarlink MT352 DVB-T)... Wow! but the box does not work anymore...no video, no audio, no OSD. PrimaryDVB = 2 now points to frontend 1 where no TV/Sound hardware is connected. So this automatic does not really work, and makes configuration more complicate. (If *i* said: use PrimaryDVB = 2, the box must do. If this is wrong, VDR could/should issue a warning, but not change the recommended PrimaryDVB. It would be easier if there could be a symlink be used instead/addition to the single digit. Remember the history: This PrimaryDVB = 2 stems from a time, when there were only badly working FF cards (with severe(!)hardware bugs). No budgets, no DVB-T to be mixed because not supported or not existing! A card found at slot1 stays at the index... But today? With udev? Why not use both? (to be compatible) If 1 or 2 Digits than old else take as device path. Rainer---= Vertraulich // // =--ocholl, Kiel, Germany ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
(Halim Sahin) 06.02.08 in /SPAMDETEC:
Hi,
A dirty but working solution is to unload and load the modules in the
right order in startvdr skript.
What is the right order?
How do i know which modules to load at all/at least?
It seems to be impossible to move the Zarlink away from frontend 0,
but after i upgrade VDR (debian) i have the ugly state:
picture and sound are coming of the right card (as frontend 1...)
but i don't have no visible OSD!
(LIRC works, control plugin shows the OSD info on port 2002,
but not the OSD)
I can't find any hint where to turn screws,
it's very frustrating!
BTW:
What does the 2 mean in:
Feb 10 22:59:24 vdr vdr: [3621] setting primary device to 2
Frontend 2
/dev/adapther2
no, it seems to be frontend 1
Why isit nummbered 2?
vdr:~# lsmod | awk '/^dvb_core/ {gsub(/,/,\n, $4); print $4}'
budget_ci
budget_core
dvb_ttpci
stv0299
dvb_bt8xx
dst_ca
dst
or51211
lgdt330x
vdr:~# dmesg | grep fronte
DVB: registering frontend 0 (Zarlink MT352 DVB-T)...
DVB: registering frontend 1 (ST STV0299 DVB-S)...
DVB: registering frontend 2 (ST STV0299 DVB-S)...
DVB: registering frontend 3 (ST STV0299 DVB-S)...
vdr:~# lsmod | grep ^dvb_core
dvb_core 75688 9
budget_ci,budget_core,dvb_ttpci,stv0299,dvb_bt8xx,dst_ca,dst,or51211,lgdt330x
vdr:~# dmesg | grep frontend
DVB: registering frontend 0 (Zarlink MT352 DVB-T)...
DVB: registering frontend 1 (ST STV0299 DVB-S)...
DVB: registering frontend 2 (ST STV0299 DVB-S)...
DVB: registering frontend 3 (ST STV0299 DVB-S)...
# cat /etc/modules
...
dvb_ttpci
stv0299
budget_ci
dvb_bt8xx
lgdt330x
or51211
dst
dst_ca
bttv
vdr:~# cat /etc/hotplug/blacklist.d/vdr
dvb_core
dvb_ttpci
budget_core
budget_ci
dvb_bt8xx
stv0299
lgdt330x
or51211
dst
dst_ca
bttv
cat /etc/modprobe.d/blacklist
#don't load the dvb drivers automatically
blacklist dvb_core
blacklist budget_core
blacklist budget_ci
blacklist dvb_ttpci
blacklist b2c2_flexcop_pci
blacklist stv0299
blacklist dvb_ttpci
blacklist lgdt330x
blacklist or51211
blacklist dst
blacklist dst_ca
blacklist dvb_bt8xx
blacklist mt352
blacklist stv0299
blacklist bttv
vdr 2.6.23x2 #2 SMP PREEMPT Sat Oct 20 03:08:47 CEST 2007 i686 GNU/Linux
vdr:~# lsmod | awk '/^dvb_core/ {gsub(/,/,\n, $4); print $4}'
dvb_ttpci
stv0299
dvb_bt8xx
dst_ca
dst
or51211
lgdt330x
vdr:~# modprobe dvb-ttpci
vdr:~# lsmod | awk '/^dvb_core/ {gsub(/,/,\n, $4); print $4}'
dvb_ttpci
stv0299
c't VDR: 1.4.7-4ctvdr1
Kernel : 2.6.23x2
Patches:
--
liemikuutio
jumpplay
subtitles-ttxtsubs
audioindexer
iptv
disableDoubleEpgEntrys
noepg
wareagle-icons
rotor
yaepg
sourcecaps
graphtft-0.1
cuttime
Plugins (APIVERSION 1.4.5):
( N = Native Plugin )
( ! = Falscher Patchlevel )
( - = Deaktiviert )
--
vdr-plugin-autotimeredit (0.1.8-19)
vdr-plugin-console (0.6.0-33)
vdr-plugin-control (0.0.2a-33)
vdr-plugin-epgsearch (0.9.24~beta3-5) conflictcheckonly
vdr-plugin-epgsearch (0.9.24~beta3-5)
vdr-plugin-examples (1.4.7-4ctvdr1) hello
vdr-plugin-examples (1.4.7-4ctvdr1) osddemo
vdr-plugin-examples (1.4.7-4ctvdr1) skincurses
vdr-plugin-examples (1.4.7-4ctvdr1) status
vdr-plugin-examples (1.4.7-4ctvdr1) svccli
vdr-plugin-examples (1.4.7-4ctvdr1) svcsvr
vdr-plugin-examples (1.4.7-4ctvdr1) svdrpdemo
vdr-plugin-femon (1.1.4-1)
vdr-plugin-osdpip (0.0.8-30)
vdr-plugin-osdteletext (0.5.1-31)
vdr-plugin-sky (1.4.7-4ctvdr1)
vdr-plugin-undelete (0.0.6-20)
Addon-Packages:
--
vdr-addon-acpiwakeup (0.0.6)
vdr-addon-noad (0.6.0-8)
vdr-addon-tvmovie2vdr (0.5.14-1)
vdr-genindex (0.1.3-1)
vdr-xpmlogos (0.0.1-3)
Rainer
--
Transparency International definiert Korruption als
Missbrauch von anvertrauter Macht zum privaten Nutzen oder Vorteil. [...]
Corruption is operationally defined as the misuse of entrusted power for
private gain. [...]
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
[EMAIL PROTECTED](serge pecher) 07.02.08 00:23 For who knows french, there is an interresting thread about udev on the dvbkivabien forum. I did use it to have my nexus always as primary device http://dvbkivabien2.info/viewtopic.php?f=21t=11255 Vous devez tre inscrit et connect pour pouvoir consulter le contenu de ce forum. I assume in english this would be translated as forget it :-( Not at all, you just need to register ! Yes, i understand french but: I don't register just to read something. What for should it be good? Too that noread locks search engines out. Why should i want to write to a forum when my posting can't be found by others with the same problem? Thanks, anyway. Nice try. Maybe you can forward the data you think which would solve the problem. TIA. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
For who knows french, there is an interresting thread about udev on the dvbkivabien forum. I did use it to have my nexus always as primary device http://dvbkivabien2.info/viewtopic.php?f=21t=11255 Serge -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Udo Richter Verzonden: dinsdag 5 februari 2008 22:52 Aan: VDR Mailing List Onderwerp: Re: [vdr] DVB-T card on the move Theunis Potgieter wrote: udev rules Any good rules that could be used as a starting point? I thought of doing this with udev, but there are some obstacles for that: First, a DVB device has several device files, not just one. And second, the usual trick to add a custom name as symlink doesn't work since VDR only accepts /dev/dvb/adapterX/, so /dev/dvb/myprimarycard/ is out. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
[EMAIL PROTECTED](Malte Forkel) 05.02.08 08:11
So how can i nail this moving DVB-T card to a fixed postition?
You might try to blacklist the driver modules used for the cards in
/etc/modprobe.d/blacklist and then enter them in /etc/modules in an
order of your liking. If you can read German, have a look at
http://www.vdr-wiki.de/wiki/index.php/Reihenfolge_der_DVB-Treiber_fest
legen.
Tried hacking blacklist
After reboot i got:
vdr:~# dmesg |grep -i front
DVB: registering frontend 0 (Zarlink MT352 DVB-T)...
DVB: registering frontend 1 (ST STV0299 DVB-S)...
DVB: registering frontend 2 (ST STV0299 DVB-S)...
DVB: registering frontend 3 (ST STV0299 DVB-S)...
that's stable but not really what i want ;-)
BTW:
Sometimes i got the note recording starts in 5 minutes
and my livs display is switched to that transponder.
I can only zapp betwen the channles on this transponder
if i switch the transponder, it is tunned back after a few seconds.
Is that caused by that bad hardware handling of linux?
vdr:~# lsmod |awk '/^dvb_core/ {i=split($4, arr, /,/); for (;i1;i--) printf
%s ,arr[i];print arr[1]}'
lgdt330x or51211 dst dst_ca dvb_bt8xx stv0299 dvb_ttpci budget_core budget_ci
vdr:~#
vdr:~#
vdr:~# lsmod
Module Size Used by
ipv6 243364 18
ac 6660 0
battery13320 0
lirc_serial15508 1
lirc_dev 15236 1 lirc_serial
aoe26144 0
budget_ci 18948 0
budget_core12164 1 budget_ci
tda1004x 15364 1 budget_ci
dvb_ttpci 94152 50
lnbp21 3328 2 budget_ci,dvb_ttpci
l64781 7812 1 dvb_ttpci
saa7146_vv 46464 1 dvb_ttpci
saa714619848 4 budget_ci,budget_core,dvb_ttpci,saa7146_vv
ves1820 7300 1 dvb_ttpci
tda8083 6788 1 dvb_ttpci
sp8870 7820 1 dvb_ttpci
stv0297 8192 2 budget_ci,dvb_ttpci
ves1x93 7300 1 dvb_ttpci
ttpci_eeprom3584 2 budget_core,dvb_ttpci
stv029910888 2 budget_ci,dvb_ttpci
hwmon_vid 3968 0
k8temp 6656 0
eeprom 8208 0
i2c_nforce2 7424 0
cpufreq_ondemand9356 0
freq_table 6432 1 cpufreq_ondemand
loop 18436 0
tsdev 9280 0
dvb_bt8xx 15876 2
nxt6000 8068 1 dvb_bt8xx
mt352 7172 1 dvb_bt8xx
dvb_pll11396 1 dvb_bt8xx
sp887x 8068 1 dvb_bt8xx
dst_ca 13952 1 dvb_bt8xx
dst28040 2 dvb_bt8xx,dst_ca
or51211 8836 1 dvb_bt8xx
zl10353 7048 1 dvb_bt8xx
lgdt330x9220 1 dvb_bt8xx
dvb_core 75688 9
budget_ci,budget_core,dvb_ttpci,stv0299,dvb_bt8xx,dst_ca,dst,or51211,lgdt330x
bt878 12008 2 dvb_bt8xx,dst
cx24110 8580 1 dvb_bt8xx
parport_pc 35620 0
parport35528 1 parport_pc
bttv 168948 2 dvb_bt8xx,bt878
video_buf 24708 2 saa7146_vv,bttv
firmware_class 10752 8
budget_ci,tda1004x,dvb_ttpci,sp8870,dvb_bt8xx,sp887x,or51211,bttv
ir_common 35204 2 budget_ci,bttv
compat_ioctl32 2432 1 bttv
i2c_algo_bit7044 1 bttv
psmouse37520 0
btcx_risc 5896 1 bttv
tveeprom 16144 1 bttv
i2c_core 24832 28
budget_ci,budget_core,tda1004x,dvb_ttpci,lnbp21,l64781,ves1820,tda8083,sp8870
,stv0297,ves1x93,ttpci_eeprom,stv0299,eeprom,i2c_nforce2,dvb_bt8xx,nxt6000,mt
352,dvb_pll,sp887x,dst,or51211,zl10353,lgdt330x,cx24110,bttv,i2c_algo_bit,tve
eprom
snd_intel8x0 33180 0
button 9360 0
snd_ac97_codec 92192 1 snd_intel8x0
serio_raw 7812 0
ac97_bus3456 1 snd_ac97_codec
videodev 28032 2 saa7146_vv,bttv
floppy 55908 0
v4l2_common17792 3 saa7146_vv,bttv,videodev
snd_pcm73476 2 snd_intel8x0,snd_ac97_codec
snd_timer 22404 1 snd_pcm
snd50020 4 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 9056 1 snd
snd_page_alloc 11272 2 snd_intel8x0,snd_pcm
rtc13848 0
v4l1_compat13572 3 saa7146_vv,bttv,videodev
shpchp 32276 0
pci_hotplug29856 1 shpchp
sis_agp10244 1
agpgart32972 1 sis_agp
evdev 10624 0
ext3 127112 5
jbd68276 1 ext3
dm_mirror 23168 0
dm_snapshot18088 0
dm_mod 54208 2 dm_mirror,dm_snapshot
generic 5892 0 [permanent]
sd_mod 28672 8
sis551313192 0 [permanent]
ide_core
Re: [vdr] DVB-T card on the move
[EMAIL PROTECTED](serge pecher) 06.02.08 17:39 Once upon a time serge pecher shaped the electrons to say... For who knows french, there is an interresting thread about udev on the dvbkivabien forum. I did use it to have my nexus always as primary device http://dvbkivabien2.info/viewtopic.php?f=21t=11255 Vous devez tre inscrit et connect pour pouvoir consulter le contenu de ce forum. I assume in english this would be translated as forget it :-( ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
Hi,
A dirty but working solution is to unload and load the modules in the
right order in startvdr skript.
HTH.
Halim
On Mi, Feb 06, 2008 at 08:08:00 +0100, Rainer Zocholl wrote:
[EMAIL PROTECTED](Malte Forkel) 05.02.08 08:11
So how can i nail this moving DVB-T card to a fixed postition?
You might try to blacklist the driver modules used for the cards in
/etc/modprobe.d/blacklist and then enter them in /etc/modules in an
order of your liking. If you can read German, have a look at
http://www.vdr-wiki.de/wiki/index.php/Reihenfolge_der_DVB-Treiber_fest
legen.
Tried hacking blacklist
After reboot i got:
vdr:~# dmesg |grep -i front
DVB: registering frontend 0 (Zarlink MT352 DVB-T)...
DVB: registering frontend 1 (ST STV0299 DVB-S)...
DVB: registering frontend 2 (ST STV0299 DVB-S)...
DVB: registering frontend 3 (ST STV0299 DVB-S)...
that's stable but not really what i want ;-)
BTW:
Sometimes i got the note recording starts in 5 minutes
and my livs display is switched to that transponder.
I can only zapp betwen the channles on this transponder
if i switch the transponder, it is tunned back after a few seconds.
Is that caused by that bad hardware handling of linux?
vdr:~# lsmod |awk '/^dvb_core/ {i=split($4, arr, /,/); for (;i1;i--) printf
%s ,arr[i];print arr[1]}'
lgdt330x or51211 dst dst_ca dvb_bt8xx stv0299 dvb_ttpci budget_core budget_ci
vdr:~#
vdr:~#
vdr:~# lsmod
Module Size Used by
ipv6 243364 18
ac 6660 0
battery13320 0
lirc_serial15508 1
lirc_dev 15236 1 lirc_serial
aoe26144 0
budget_ci 18948 0
budget_core12164 1 budget_ci
tda1004x 15364 1 budget_ci
dvb_ttpci 94152 50
lnbp21 3328 2 budget_ci,dvb_ttpci
l64781 7812 1 dvb_ttpci
saa7146_vv 46464 1 dvb_ttpci
saa714619848 4 budget_ci,budget_core,dvb_ttpci,saa7146_vv
ves1820 7300 1 dvb_ttpci
tda8083 6788 1 dvb_ttpci
sp8870 7820 1 dvb_ttpci
stv0297 8192 2 budget_ci,dvb_ttpci
ves1x93 7300 1 dvb_ttpci
ttpci_eeprom3584 2 budget_core,dvb_ttpci
stv029910888 2 budget_ci,dvb_ttpci
hwmon_vid 3968 0
k8temp 6656 0
eeprom 8208 0
i2c_nforce2 7424 0
cpufreq_ondemand9356 0
freq_table 6432 1 cpufreq_ondemand
loop 18436 0
tsdev 9280 0
dvb_bt8xx 15876 2
nxt6000 8068 1 dvb_bt8xx
mt352 7172 1 dvb_bt8xx
dvb_pll11396 1 dvb_bt8xx
sp887x 8068 1 dvb_bt8xx
dst_ca 13952 1 dvb_bt8xx
dst28040 2 dvb_bt8xx,dst_ca
or51211 8836 1 dvb_bt8xx
zl10353 7048 1 dvb_bt8xx
lgdt330x9220 1 dvb_bt8xx
dvb_core 75688 9
budget_ci,budget_core,dvb_ttpci,stv0299,dvb_bt8xx,dst_ca,dst,or51211,lgdt330x
bt878 12008 2 dvb_bt8xx,dst
cx24110 8580 1 dvb_bt8xx
parport_pc 35620 0
parport35528 1 parport_pc
bttv 168948 2 dvb_bt8xx,bt878
video_buf 24708 2 saa7146_vv,bttv
firmware_class 10752 8
budget_ci,tda1004x,dvb_ttpci,sp8870,dvb_bt8xx,sp887x,or51211,bttv
ir_common 35204 2 budget_ci,bttv
compat_ioctl32 2432 1 bttv
i2c_algo_bit7044 1 bttv
psmouse37520 0
btcx_risc 5896 1 bttv
tveeprom 16144 1 bttv
i2c_core 24832 28
budget_ci,budget_core,tda1004x,dvb_ttpci,lnbp21,l64781,ves1820,tda8083,sp8870
,stv0297,ves1x93,ttpci_eeprom,stv0299,eeprom,i2c_nforce2,dvb_bt8xx,nxt6000,mt
352,dvb_pll,sp887x,dst,or51211,zl10353,lgdt330x,cx24110,bttv,i2c_algo_bit,tve
eprom
snd_intel8x0 33180 0
button 9360 0
snd_ac97_codec 92192 1 snd_intel8x0
serio_raw 7812 0
ac97_bus3456 1 snd_ac97_codec
videodev 28032 2 saa7146_vv,bttv
floppy 55908 0
v4l2_common17792 3 saa7146_vv,bttv,videodev
snd_pcm73476 2 snd_intel8x0,snd_ac97_codec
snd_timer 22404 1 snd_pcm
snd50020 4 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 9056 1 snd
snd_page_alloc 11272 2 snd_intel8x0,snd_pcm
rtc13848 0
v4l1_compat13572 3 saa7146_vv,bttv,videodev
shpchp 32276 0
pci_hotplug29856 1 shpchp
sis_agp10244 1
agpgart32972 1 sis_agp
evdev 10624 0
ext3 127112
Re: [vdr] DVB-T card on the move
Not at all, you just need to register ! serge -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Rainer Zocholl Verzonden: woensdag 6 februari 2008 21:04 Aan: vdr@linuxtv.org Onderwerp: Re: [vdr] DVB-T card on the move [EMAIL PROTECTED](serge pecher) 06.02.08 17:39 Once upon a time serge pecher shaped the electrons to say... For who knows french, there is an interresting thread about udev on the dvbkivabien forum. I did use it to have my nexus always as primary device http://dvbkivabien2.info/viewtopic.php?f=21t=11255 Vous devez tre inscrit et connect pour pouvoir consulter le contenu de ce forum. I assume in english this would be translated as forget it :-( ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
[EMAIL PROTECTED](Malte Forkel) 05.02.08 08:11
So how can i nail this moving DVB-T card to a fixed postition?
You might try to blacklist the driver modules used for the cards in
/etc/modprobe.d/blacklist and then enter them in /etc/modules in an
order of your liking. If you can read German, have a look at
http://www.vdr-wiki.de/wiki/index.php/Reihenfolge_der_DVB-Treiber_fest
legen.
Good luck, Malte
Thanks. the link sounds good, and can era german (and sometimes
understand it ;-)
I too had funny effect with:
RemotePlugin Mplayer
because of that move.
I ran 1.4.3 in
http://www.vdr-portal.de/board/thread.php?postid=479909#post479909
is stated that vdr_1.4.0-1ctvdr2_i386 had fixed the problem.
They recommand to hack /usr/sbin/runvdr
function get_modulenames()
{
if [ $KVERS_2_6 ]; then
MODULES=`lsmod | awk '/^dvb_core/ {gsub(/,/,\n, $4); print $4}' | tac`
[ $MODULES ] MODULES=$MODULES dvb_core
else
MODULES=`lsmod | grep dvb-core | cut -d'[' -f2 | cut -d']' -f1`
[ $MODULES ] MODULES=$MODULES dvb-core
fi
}
RAINER---= Vertraulich
//
//
=--ocholl, Kiel, Germany
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
[EMAIL PROTECTED](Theunis Potgieter) 05.02.08 06:13 udev rules Yes, i know ;-) can i pin the card to the MAC address like any other network card? If how? Rainer ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
Theunis Potgieter wrote: udev rules Any good rules that could be used as a starting point? I thought of doing this with udev, but there are some obstacles for that: First, a DVB device has several device files, not just one. And second, the usual trick to add a custom name as symlink doesn't work since VDR only accepts /dev/dvb/adapterX/, so /dev/dvb/myprimarycard/ is out. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] DVB-T card on the move
Hello for years i was running VDR 1.4.3. Now i felt forced to use ctvdr and 1.4.7 with a Linux 2.6.23x2 #2 SMP PREEMPT on a Main Board: K7S8XE+ AMI BIOS P1.70 (04/27/2004) and an AMD Duron(tm) 1350MHz (under clocked from 1500) with 512MB RAM i found this miracle(?): The systen has 4 cards: vdr:~# dmesg | grep -i frontend DVB: registering frontend 0 (Zarlink MT352 DVB-T)... DVB: registering frontend 1 (ST STV0299 DVB-S)... DVB: registering frontend 2 (ST STV0299 DVB-S)... DVB: registering frontend 3 (ST STV0299 DVB-S)... with setup.conf PrimaryDVB = 2 i got sound and live screen After a slight (benign) change reboot i have no live image and no sound anymore. Panic! What happend? vdr:~# dmesg | grep front DVB: registering frontend 0 (ST STV0299 DVB-S)... DVB: registering frontend 1 (ST STV0299 DVB-S)... DVB: registering frontend 2 (ST STV0299 DVB-S)... DVB: registering frontend 3 (Zarlink MT352 DVB-T)... Mystery... another warm reboot without any change: vdr:~# dmesg | grep front DVB: registering frontend 0 (ST STV0299 DVB-S)... DVB: registering frontend 1 (Zarlink MT352 DVB-T)... DVB: registering frontend 2 (ST STV0299 DVB-S)... DVB: registering frontend 3 (ST STV0299 DVB-S)... And again: vdr:~# dmesg | grep front DVB: registering frontend 0 (ST STV0299 DVB-S)... DVB: registering frontend 1 (ST STV0299 DVB-S)... DVB: registering frontend 2 (ST STV0299 DVB-S)... DVB: registering frontend 3 (Zarlink MT352 DVB-T)... vdr:~# lspci 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 746 Host (rev 10) 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] (rev 36) 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01) 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0) 00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90) 00:05.0 RAID bus controller: Silicon Integrated Systems [SiS] RAID bus controller 180 SATA/PATA [SiS] (rev 01) 00:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) 00:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 00:0a.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev11) 00:0b.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) 00:0d.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400/G450 (rev 85) vdr:~# So how can i nail this moving DVB-T card to a fixed postition? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
udev rules On 05 Feb 2008 00:27:00 +0100, Rainer Zocholl [EMAIL PROTECTED] wrote: Hello for years i was running VDR 1.4.3. Now i felt forced to use ctvdr and 1.4.7 with a Linux 2.6.23x2 #2 SMP PREEMPT on a Main Board: K7S8XE+ AMI BIOS P1.70 (04/27/2004) and an AMD Duron(tm) 1350MHz (under clocked from 1500) with 512MB RAM i found this miracle(?): The systen has 4 cards: vdr:~# dmesg | grep -i frontend DVB: registering frontend 0 (Zarlink MT352 DVB-T)... DVB: registering frontend 1 (ST STV0299 DVB-S)... DVB: registering frontend 2 (ST STV0299 DVB-S)... DVB: registering frontend 3 (ST STV0299 DVB-S)... with setup.conf PrimaryDVB = 2 i got sound and live screen After a slight (benign) change reboot i have no live image and no sound anymore. Panic! What happend? vdr:~# dmesg | grep front DVB: registering frontend 0 (ST STV0299 DVB-S)... DVB: registering frontend 1 (ST STV0299 DVB-S)... DVB: registering frontend 2 (ST STV0299 DVB-S)... DVB: registering frontend 3 (Zarlink MT352 DVB-T)... Mystery... another warm reboot without any change: vdr:~# dmesg | grep front DVB: registering frontend 0 (ST STV0299 DVB-S)... DVB: registering frontend 1 (Zarlink MT352 DVB-T)... DVB: registering frontend 2 (ST STV0299 DVB-S)... DVB: registering frontend 3 (ST STV0299 DVB-S)... And again: vdr:~# dmesg | grep front DVB: registering frontend 0 (ST STV0299 DVB-S)... DVB: registering frontend 1 (ST STV0299 DVB-S)... DVB: registering frontend 2 (ST STV0299 DVB-S)... DVB: registering frontend 3 (Zarlink MT352 DVB-T)... vdr:~# lspci 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 746 Host (rev 10) 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] (rev 36) 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01) 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0) 00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90) 00:05.0 RAID bus controller: Silicon Integrated Systems [SiS] RAID bus controller 180 SATA/PATA [SiS] (rev 01) 00:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) 00:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 00:0a.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev11) 00:0b.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) 00:0d.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400/G450 (rev 85) vdr:~# So how can i nail this moving DVB-T card to a fixed postition? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
Theunis Potgieter [EMAIL PROTECTED] wrote: udev rules ha, that was even funny. :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T card on the move
Rainer Zocholl schrieb: So how can i nail this moving DVB-T card to a fixed postition? You might try to blacklist the driver modules used for the cards in /etc/modprobe.d/blacklist and then enter them in /etc/modules in an order of your liking. If you can read German, have a look at http://www.vdr-wiki.de/wiki/index.php/Reihenfolge_der_DVB-Treiber_festlegen. Good luck, Malte ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
