Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: VDR problem.



Allan Jacobsen wrote:
> 
> Klaus Schmidinger wrote:
> >
> > Allan Jacobsen wrote:
> > >
> > > Hi
> > >
> > > I sold my old PC where I have been running VDR for over
> > > a year, but I am having problems now when I have moved
> > > the card to another old PC.
> > > As I am still on a 2.2 kernel (2.2.19) I downloaded
> > > the DVB driver version 0.8.2 and the VDR version 0.7.2
> > > The hardware driver compiles fine and loads OK, but
> > > the vdr program can not find the device.
> > > I have looked through the sources and it looks like the
> > > hardware driver uses devices in /dev/ost/... while vdr
> > > look for /dev/video...
> > > I tried to simply make /dev/video with the same major
> > > and minor numbers as /dev/ost/video but no luck.
> > > Anyone with any good ideas ?
> >
> > The combination "driver 0.8.2" and "VDR 0.72" should work together
> > just fine. Are you _absolutely_, _positively_ sure you are using
> > _that_ combination?
> >
> 
> Yes 8-(
> 
> The files are "siemens_dvb-0.8.2.tar.gz" and "vdr-0.72.tgz"
> respectively, sizes 651965 and 197335 bytes.
> 
> I just recompiled both the driver and vdr to be 100% sure.
> 
> This is the content of the syslog:
> Jul 12 23:25:54 ghost kernel: i2c-core.o: i2c core module
> Jul 12 23:25:55 ghost kernel: Linux video capture interface: v1.00
> Jul 12 23:25:55 ghost kernel: saa7146_core.o: saa7146(1): bus:0, rev:1,
> mem:0xc8859c00.
> Jul 12 23:25:55 ghost kernel: VES1893: attaching VES1893 at 0x10 to
> adapter saa7146(1)
> Jul 12 23:25:58 ghost kernel: dvb: ARM firmware successfully loaded.
> Jul 12 23:25:58 ghost kernel: dvb: firmware = f0240009
> Jul 12 23:25:58 ghost kernel: dvb: MAC = 00 d0 5c 1e a3 4e
> Jul 12 23:25:58 ghost kernel: dvb: 1 dvb(s) found!
> Jul 12 23:25:58 ghost kernel: tuner: chip found @ 0x61
> Jul 12 23:26:28 ghost kernel: dvb: 1 dvb(s) released properly.
> Jul 12 23:26:28 ghost kernel: VES1893: detach_client
> Jul 12 23:26:29 ghost kernel: VES1893: attaching VES1893 at 0x10 to
> adapter saa7146(1)
> Jul 12 23:26:31 ghost kernel: dvb: ARM firmware successfully loaded.
> Jul 12 23:26:31 ghost kernel: dvb: firmware = f0240009
> Jul 12 23:26:31 ghost kernel: dvb: MAC = 00 d0 5c 1e a3 4e
> Jul 12 23:26:31 ghost kernel: dvb: 1 dvb(s) found!
> Jul 12 23:26:31 ghost kernel: tuner: chip found @ 0x61
> Jul 12 23:29:03 ghost vdr[883]: VDR version 0.72 started
> Jul 12 23:29:03 ghost vdr[883]: loading /video/setup.conf
> Jul 12 23:29:03 ghost vdr[883]: loading /video/channels.conf
> Jul 12 23:29:04 ghost vdr[883]: loading /video/keys-pc.conf
> Jul 12 23:29:04 ghost vdr[883]: ERROR: no video device found, giving up!
> 
> This is "cat /proc/devices":
> Character devices:
>   1 mem
>   2 pty
>   3 ttyp
>   4 ttyS
>   5 cua
>   7 vcs
>  10 misc
>  81 video_capture
> 128 ptm
> 136 pts
> 249 ost/ca
> 250 ost/video
> 251 ost/sec
> 252 ost/audio
> 253 ost/frontend
> 254 ost/demux
> 
> Block devices:
>   2 fd
>   8 sd
>  65 sd
> 
> and this is lsmod:
> Module                  Size  Used by
> tuner                   3792   0  (unused)
> dvb                  2945840   1
> dvb_demux               4576   0  [dvb]
> dmxdev                  5344   0  [dvb]
> VES1820                 3264   0  (unused)
> VES1893                 3184   0  (unused)
> saa7146_v4l            14864   0  (unused)
> saa7146_core           13360   0  [dvb saa7146_v4l]
> videodev                2720   2  [dvb]
> i2c-core               10240   0  [tuner dvb VES1820 VES1893
> saa7146_core]
> ca                       624   0  (unused)
> frontend                 720   0  (unused)
> sec                      624   0  (unused)
> audio                    768   0  (unused)
> video                    800   0  (unused)
> dmx                      832   0  (unused)
> demux                    576   1  [dvb dvb_demux]
> dvbdev                  1376   1  [dvb ca frontend sec audio video dmx]
> ne                      6288   1
> 8390                    6080   0  [ne]
> 
> It look very much like something is wrong in /dev but
> what....

Please check if your devices look exactly like this:

lrwxrwxrwx    1 root     root            4 Apr  6 18:11 /dev/vbi -> vbi0
crw-rw----    1 root     video     81, 224 Jan 19 09:36 /dev/vbi0
crw-rw----    1 root     video     81, 225 Jan 19 09:36 /dev/vbi1
crw-rw----    1 root     video     81, 226 Jan 19 09:36 /dev/vbi2
crw-rw----    1 root     video     81, 227 Jan 19 09:36 /dev/vbi3
lrwxrwxrwx    1 root     root            6 Apr  6 18:11 /dev/video -> video0
crw-rw----    1 root     video     81,   0 Jan 19 09:36 /dev/video0
crw-rw----    1 root     video     81,   1 Jan 19 09:36 /dev/video1
crw-rw----    1 root     video     81,   2 Jan 19 09:36 /dev/video2
crw-rw----    1 root     video     81,   3 Jan 19 09:36 /dev/video3

If not, create them with 'mknod' accordingly.
Also, if you're not running VDR as user 'root', make sure the user that runs
VDR has full read and write access to these devices.

Klaus
-- 
_______________________________________________________________

Klaus Schmidinger                       Phone: +49-8635-6989-10
CadSoft Computer GmbH                   Fax:   +49-8635-6989-40
Hofmark 2                               Email:   kls@cadsoft.de
D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de
_______________________________________________________________


-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.



Home | Main Index | Thread Index