Mailing List archive

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

[linux-dvb] Power key






Recently i wanted to turn VDR of.

Press new beautiful key "Power Off"
The yellow cancel-warning occurs
5 sec disappears
and:
Nothing happens.

Pressing again "Power off"
Nothing happens, no yellow canel-warning, nothing.

Menu:
Is there, VDR is alive.
No timer is marked recording.


Hm...

had turned the analog tuner on. so there was no receiption
in digital.
That caused VDR to reload:

Sep  6 19:59:29 msi vdr[1288]: loading /video/commands.conf
Sep  6 19:59:29 msi vdr[1288]: probing /dev/ost/qpskfe0
Sep  6 19:59:29 msi vdr[1290]: EIT processing thread started (pid=1290) - master
Sep  6 19:59:29 msi vdr[1288]: probing /dev/ost/qpskfe1
Sep  6 19:59:29 msi vdr[1291]: EIT processing thread started (pid=1291)
Sep  6 19:59:29 msi vdr[1288]: probing /dev/ost/qpskfe2
Sep  6 19:59:29 msi vdr[1288]: probing /dev/ost/qamfe2
Sep  6 19:59:29 msi vdr[1288]: found 2 video devices
Sep  6 19:59:29 msi vdr[1288]: setting primary DVB to 1
Sep  6 19:59:29 msi vdr[1288]: switching to channel 1
Sep  6 19:59:29 msi vdr[1292]: LIRC remote control thread started (pid=1292)
Sep  6 19:59:29 msi kernel: lirc_serial: Interrupt 4, port 03f8 obtained
Sep  6 19:59:29 msi vdr[1288]: SVDRP listening on port 2001
Sep  6 19:59:29 msi vdr[1288]: setting watchdog timer to 60 seconds
Sep  6 19:59:29 msi vdr[1288]: setting watchdog timer to 60 seconds
Sep  6 19:59:34 msi vdr[1288]: timer 16 start
Sep  6 19:59:34 msi vdr[1288]: switching to channel 5
Sep  6 19:59:34 msi vdr[1288]: Title: 'Mag' Subtitle:''
Sep  6 19:59:34 msi vdr[1288]: record /video/Mag/_/2001-09-06.19:29.50.02.rec
Sep  6 19:59:34 msi vdr[1288]: recording to '/video/Mag/_/2001-09-06.19:29.50.02.rec/003.vdr'
Sep  6 19:59:34 msi vdr[1294]: output thread started (pid=1294)
Sep  6 19:59:34 msi vdr[1295]: input thread started (pid=1295)

this timer is 19:29 til 20:00...

Sep  6 19:59:37 msi vdr[1288]: max. latency time 1 seconds
Sep  6 19:59:54 msi vdr[1288]: Power button pressed
Sep  6 19:59:54 msi vdr[1288]: confirm: Recording - shut down anyway?
Sep  6 20:00:05 msi vdr[1288]: not confirmed
Sep  6 20:00:05 msi vdr[1288]: max. latency time 11 seconds
Sep  6 20:00:06 msi vdr[1294]: output thread ended (pid=1294)
Sep  6 20:00:06 msi vdr[1295]: input thread ended (pid=1295)
Sep  6 20:00:06 msi vdr[1288]: buffer stats: 12972 (1%) used
Sep  6 20:00:06 msi vdr[1288]: timer 16 stop
Sep  6 20:00:07 msi vdr[1288]: next timer event at Thu Sep  6 20:59:00 2001
Sep  6 20:00:20 msi last message repeated 11 times
Sep  6 20:00:21 msi kernel: lirc_serial: AIEEEE: 0 1 3b97b9b5 3b97b99a 38800 1da3d
Sep  6 20:00:21 msi vdr[1288]: Power button pressed
Sep  6 20:00:21 msi vdr[1288]: next timer event at Thu Sep  6 20:59:00 2001
Sep  6 20:00:22 msi vdr[1288]: Power button pressed
Sep  6 20:00:22 msi vdr[1288]: next timer event at Thu Sep  6 20:59:00 2001
Sep  6 20:00:22 msi vdr[1288]: Power button pressed
Sep  6 20:00:22 msi vdr[1288]: next timer event at Thu Sep  6 20:59:00 2001
Sep  6 20:00:23 msi vdr[1288]: Power button pressed
Sep  6 20:00:23 msi vdr[1288]: next timer event at Thu Sep  6 20:59:00 2001
Sep  6 20:00:37 msi last message repeated 14 times
Sep  6 20:00:37 msi vdr[1288]: Power button pressed
Sep  6 20:00:37 msi vdr[1288]: next timer event at Thu Sep  6 20:59:00 2001
Sep  6 20:00:38 msi vdr[1288]: Power button pressed





Some probs:

A "resumed" timer seems not to be re-marked in OSD.
(OK, here it might be OK, but i saw that in other cases too)

There is no feedback that and why the power key is not accepted, 
only in /var/log_messages.

Now the power key seems to be locked entirely, why?

So i have to ssh to the box, log in and
shutdown via telnet, only because i just wanted to
swap the main power cabel now, and not at 3:00 when no timer is
active in the near future.;-)

If the box would have more timers running, then the power key 
would never be accepted, because always a record will be in
the near future.
That can't be the intention or?
(I of cause have an "emergency" exit in command.conf, but
how to explain my room service guy the (s)he has to turn on the
TV, scroll thru menu in the case my videorecorder blocks the
plug (s)he needs for the hoover and do not react on the poweroff
key? ;-)



Would it be possible to show a warning like in 
/var/log/message

"next timer event at 
"Thu Sep  6 20:59:00 2001
"<name of the timer>

or
"confirm to continue recording <name of timer>"
(Intentionally _not_ "confirm to abort" imagine there
is no TV set turned on, the user would be irretated why his
power off do not work)


Suggestions:

The MinEventTimeOut is not allowed to block the 
RC-Power Key (I think there is the problem). It's the explicit 
wish of the user to turn the device off, so turn it off :-).


A running record must give a warning, but can't disable
the power key. (It's user's wish! It's his fault, he has been warned.
)


Maybe there should be a way to keep the VDR turned off
(StandBy vs PowerOff)

PowerOff/"SoftPlugOut": VDR do not set the wakeup timer 
and turn it off regard less of running records.

StandBy: Set wakeup and turn the machine off now but only 
if no record is running or will start in less than 2 minutes(*).
MinEventTimeOut does not matter in this case.
MinEventTimeOut might be much longer than those 2 minutes
to take the power up stress into account.



(*) duration of the last shutdown reboot cycle e.g.


my 0.2c



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


Home | Main Index | Thread Index