[vdr] Re: Aston 1.05 ... not quite there

[Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>]

Miguel Sanchez wrote:
> 
> ...
> >Well, apparently VDR does send the descriptors - I'm afraid then I don't
> >know why it doesn't decrypt.
> >
> >Does it work with the '-icam' firmware?
> >
> With -icam software it does not work at all. Here you can see the log:
> 
> Aug 17 17:03:24 msanchez vdr[3620]: VDR version 1.2.1 started
> Aug 17 17:03:24 msanchez vdr[3620]: loading /video/setup.conf
> Aug 17 17:03:24 msanchez vdr[3620]: ERROR: unknown config parameter:
> Style = 0
> Aug 17 17:03:24 msanchez vdr[3620]: loading /video/channels.conf
> Aug 17 17:03:24 msanchez vdr[3620]: loading /video/timers.conf
> Aug 17 17:03:24 msanchez vdr[3620]: loading /video/svdrphosts.conf
> Aug 17 17:03:24 msanchez vdr[3620]: loading /video/ca.conf
> Aug 17 17:03:24 msanchez vdr[3620]: loading /video/remote.conf
> Aug 17 17:03:24 msanchez vdr[3620]: probing /dev/dvb/adapter0/frontend0
> Aug 17 17:03:25 msanchez kernel: OutCommand: timeout waiting for COMMAND
> idle
> Aug 17 17:03:25 msanchez kernel: SOutCommand error
> Aug 17 17:03:25 msanchez kernel: outcom error
> Aug 17 17:03:25 msanchez vdr[3620]: ERROR (dvbdevice.c,525): Operation
> not permitted
> Aug 17 17:03:26 msanchez vdr[3623]: EIT processing thread started
> (pid=3623) - master
> Aug 17 17:03:26 msanchez vdr[3620]: CAM doesn't support link layer interface
> Aug 17 17:03:26 msanchez vdr[3624]: tuner thread started on device 1
> (pid=3624)
> Aug 17 17:03:26 msanchez vdr[3620]: probing /dev/dvb/adapter1/frontend0
> Aug 17 17:03:26 msanchez vdr[3620]: found 1 video device
> Aug 17 17:03:26 msanchez vdr[3620]: setting primary device to 1
> Aug 17 17:03:26 msanchez vdr[3620]: SVDRP listening on port 2001
> Aug 17 17:03:26 msanchez vdr[3625]: KBD remote control thread started
> (pid=3625)
> Aug 17 17:03:26 msanchez vdr[3620]: remote control KBD - keys known
> Aug 17 17:03:26 msanchez vdr[3620]: switching to channel 2
> Aug 17 17:03:26 msanchez vdr[3620]: reading EPG data from /video/epg.data
> Aug 17 17:03:27 msanchez kernel: OutCommand: timeout waiting for COMMAND
> idle
> Aug 17 17:03:27 msanchez kernel: SOutCommand error
> Aug 17 17:03:27 msanchez kernel: outcom error
> Aug 17 17:03:29 msanchez kernel: CommandRequest: timeout waiting for
> COMMAND to complete
> Aug 17 17:03:29 msanchez kernel: StopHWFilter error
> Aug 17 17:03:32 msanchez kernel: OutCommand: timeout waiting for COMMAND
> idle
> Aug 17 17:03:32 msanchez kernel: SOutCommand error
> Aug 17 17:03:32 msanchez kernel: outcom error
> Aug 17 17:03:34 msanchez kernel: OutCommand: timeout waiting for COMMAND
> idle
> Aug 17 17:03:34 msanchez kernel: SOutCommand error
> Aug 17 17:03:34 msanchez kernel: outcom error
> Aug 17 17:03:36 msanchez kernel: OutCommand: timeout waiting for COMMAND
> idle
> Aug 17 17:03:36 msanchez kernel: SOutCommand error
> Aug 17 17:03:36 msanchez kernel: outcom error
> Aug 17 17:03:38 msanchez kernel: OutCommand: timeout waiting for COMMAND
> idle
> Aug 17 17:03:38 msanchez kernel: SOutCommand error
> Aug 17 17:03:38 msanchez kernel: outcom error
> Aug 17 17:03:40 msanchez kernel: OutCommand: timeout waiting for COMMAND
> idle
> Aug 17 17:03:40 msanchez kernel: SOutCommand error
> 
> I get not image, audio nor OSD with this firmware.

Looks like you're having severe problems using the '-icam' firmware...

> >>>BTW: when sending log file excerpts, please don't wrap them (I had to edit your
> >>>lines to make them easily readable).
> >>>
> >>>
> >>>
> >>Sorry about the wrapping, it should be fixed by now  [:-(]
> >>
> >>
> >
> >Yes, and if you could post in plain text rather than HTML, it would be even better ;-)
> >
> Done.

So it's either HTML postings _or_ not wrapping log lines?!

Klaus


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