[linux-dvb] Kernel 2.6.12.2 + Haupp. Nexus-s 2.3: no DVB device found, once more !

Emmanuel Roux manux43 at laposte.net
Wed Jul 13 17:57:42 CEST 2005


For those who are searching for a solution to this problem:

create /etc/udev/rules.d/54-dvb.rules   (replace 54 by your udev version)

KERNEL="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
KERNEL="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
KERNEL="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
KERNEL="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
KERNEL="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
KERNEL="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
KERNEL="dvb0.net*",        NAME="dvb/adapter0/net%n"
KERNEL="dvb0.video*",      NAME="dvb/adapter0/video%n"


KERNEL="dvb1.dvr*",        NAME="dvb/adapter1/dvr%n"
KERNEL="dvb1.demux*",      NAME="dvb/adapter1/demux%n"
KERNEL="dvb1.frontend*",   NAME="dvb/adapter1/frontend%n"
KERNEL="dvb1.audio*",      NAME="dvb/adapter1/audio%n"
KERNEL="dvb1.ca*",         NAME="dvb/adapter1/ca%n"
KERNEL="dvb1.osd*",        NAME="dvb/adapter1/osd%n"
KERNEL="dvb1.net*",        NAME="dvb/adapter1/net%n"
KERNEL="dvb1.video*",      NAME="dvb/adapter1/video%n"


KERNEL="dvb2.dvr*",        NAME="dvb/adapter2/dvr%n"
KERNEL="dvb2.demux*",      NAME="dvb/adapter2/demux%n"
KERNEL="dvb2.frontend*",   NAME="dvb/adapter2/frontend%n"
KERNEL="dvb2.audio*",      NAME="dvb/adapter2/audio%n"
KERNEL="dvb2.ca*",         NAME="dvb/adapter2/ca%n"
KERNEL="dvb2.osd*",        NAME="dvb/adapter2/osd%n"
KERNEL="dvb2.net*",        NAME="dvb/adapter2/net%n"
KERNEL="dvb2.video*",      NAME="dvb/adapter2/video%n"


KERNEL="dvb3.dvr*",        NAME="dvb/adapter3/dvr%n"
KERNEL="dvb3.demux*",      NAME="dvb/adapter3/demux%n"
KERNEL="dvb3.frontend*",   NAME="dvb/adapter3/frontend%n"
KERNEL="dvb3.audio*",      NAME="dvb/adapter3/audio%n"
KERNEL="dvb3.ca*",         NAME="dvb/adapter3/ca%n"
KERNEL="dvb3.osd*",        NAME="dvb/adapter3/osd%n"
KERNEL="dvb3.net*",        NAME="dvb/adapter3/net%n"
KERNEL="dvb3.video*",      NAME="dvb/adapter3/video%n"


And that's it...
Manux43

> udev and devfs are on the system. By booting the system, the devices 
> are created in /dev and not /dev/dvb/adapter.
> How can I fix the problem either by configuring pvr or by creating the 
> devices?
>
> Thanks
> Manux43
>
>> On Tuesday 12 July 2005 17:56, manux43 wrote:
>>  
>>
>>> Hello,
>>>
>>> I have a small problem with the vdr... any idea ?
>>> kernel 2.6.12.2 with latest firmware + Haupp. Nexus-s 2.3
>>>
>>> Thanks a lot,
>>> Manux43
>>>
>>> ***************************
>>> log from /var/log/messages
>>> ***************************
>>>
>>>
>>> Jul 12 17:50:00 le_magnetoscope_de_laurence vdr[4586]: VDR
>>> version 1.2.6 started
>>> Jul 12 17:50:00 le_magnetoscope vdr[4586]: loading
>>> /etc/vdr/sources.conf
>>> Jul 12 17:50:00 le_magnetoscope vdr[4586]: loading
>>> /etc/vdr/diseqc.conf
>>> Jul 12 17:50:00 le_magnetoscope vdr[4586]: loading
>>> /etc/vdr/channels.conf
>>> Jul 12 17:50:00 le_magnetoscope vdr[4586]: loading
>>> /etc/vdr/svdrphosts.conf
>>> Jul 12 17:50:00 le_magnetoscope vdr[4586]: loading
>>> /etc/vdr/ca.conf
>>> Jul 12 17:50:00 le_magnetoscope vdr[4586]: loading
>>> /etc/vdr/keymacros.conf
>>> Jul 12 17:50:00 le_magnetoscope vdr[4586]: no DVB device found
>>>
>>>
>>>   
>>
>> Looks like missing device, see below.
>>
>>  
>>
>>> ***************************
>>> log from ls -l /dev
>>> ***************************
>>>
>>> crw-rw----  1 root root   212,   1 2005-07-12 17:31 dvb0.audio0
>>> crw-rw----  1 root root   212,   6 2005-07-12 17:31 dvb0.ca0
>>> crw-rw----  1 root root   212,   4 2005-07-12 17:31 dvb0.demux0
>>> crw-rw----  1 root root   212,   5 2005-07-12 17:31 dvb0.dvr0
>>> crw-rw----  1 root root   212,   3 2005-07-12 17:31 dvb0.frontend0
>>> crw-rw----  1 root root   212,   7 2005-07-12 17:31 dvb0.net0
>>> crw-rw----  1 root root   212,   8 2005-07-12 17:31 dvb0.osd0
>>> crw-rw----  1 root root   212,   0 2005-07-12 17:31 dvb0.video0
>>>
>>>   
>>
>>
>>
>> This looks like a missing devfs oder udev or whatever, vdr will 
>> search in /dev/dvb/adapter?/*
>>
>> That means either the devices are not existing when vdr starts (try a 
>> sleep before starting vdr, or a look waiting for the devices to 
>> appear) or are named wrong for vdr to fing them.
>>
>> Matthias
>>
>> _______________________________________________
>> linux-dvb mailing list
>> linux-dvb at linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>
>>  
>>
>
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>





More information about the linux-dvb mailing list