[0.6] Some minutes in login screen, in tty1, before I can watch tv [Solved]

jbjbjb · January 20, 2016 at 4:24 PM

Hi.

After installing yaVdr 0.6, when yaVdr starts, in tty1 appears a login screen during 1-2 minutes aprox. before I can start watch tv.

Is there a way to avoid that and start directly in the tv screen.

Thanks and regards

Javier B.

seahawk1986 · January 20, 2016 at 4:30 PM

Please post the syslog from booting up until you can watch tv.

jbjbjb · January 21, 2016 at 9:21 AM

Hi.

Here is it:

http://pastebin.com/ysX92VuM

The login screen in tty1 appears about 6:52:10 and the tv screen appears at 6:54:09

Regards.
Javier B.

seahawk1986 · January 21, 2016 at 9:49 AM

There are some daemons crashing during startup: transmission, samba-ad-dc, yavdr-hostwakeup (which seems to have the biggest impact on statup time since it ist restarted).
Please try to set your network device name (you cat get the interface name for example from the output of

Code

ip link

) in the INTERFACE Environment variable in /etc/init/hostwakeup - e.g.:

Code

env INTERFACE=p32p1

or disable the service:

Code

echo manual | sudo tee /etc/init/hostwakeup.override

jbjbjb · January 21, 2016 at 2:13 PM

Hi.

I have configured /etc/init/hostwakeup.conf correctly with:

Code

env INTERFACE=p32p1

but the problem do not seem to be solved. Stil 2 minutes from login screen in tty1, till tv screen.

Syslog after change is:

http://pastebin.com/Yg9cfF7h

Login screen appears at 14:03:08 and tv screen at 14:05:08

Regards.
Javier B.

seahawk1986 · January 21, 2016 at 2:20 PM

irexec and transmission are still crashing repeatedly during startup - did you change the configuration for irexec or eventlircd yourself? I don't know why transmission-daemon crashes (maybe misconfigured?) - but for debugging purposes I would deactivate or uninstall it in the meantime.

jbjbjb · January 21, 2016 at 2:28 PM

Hi.

In order to restart vdr or even computer from the remote control I configured today this (but yesterday started slow equaly):

I edited

Code

/etc/lirc/lircrc

and I added this lines:

Code

begin
  prog = irexec
  button = KEY_STOP
  button = KEY_9
  button = KEY_STOP
  config = restart vdr


begin
  prog = irexec
  button = KEY_STOP
  button = KEY_8
  button = KEY_STOP
  config = sudo reboot
end

Display More

But the macros do not work. I am pending to ask how to configure those macros in yaVdr 0.6.

Regards.
Javier B.

seahawk1986 · January 21, 2016 at 2:38 PM

Well, that is an obvious syntax error... - each block has to end with "end" - like this:

Code

begin
  prog = irexec
  button = KEY_STOP
  button = KEY_9
  button = KEY_STOP
  config = restart vdr
end


begin
  prog = irexec
  button = KEY_STOP
  button = KEY_8
  button = KEY_STOP
  config = sudo reboot
end

Display More

jbjbjb · January 21, 2016 at 2:48 PM

Ok.

I will try the changes.

Now I have reinstalled transmission-daemon, and it seems that transmission error has gone. I also deleted the changes in '/etc/lirc/lircrc' to have a clean startup.

This is the new syslog:

http://pastebin.com/YVv3A8Xv

Login screen appears at 14:40:00 and tv screen at 14:41:50

Any aditional idea of what is happening?

Regards
Javier B.

seahawk1986 · January 21, 2016 at 2:53 PM

Now there seems to be nvidia-persistenced left - what graphics card do you have

Code

lspci -nn | grep VGA

and which nvidia driver is installed?

Code

dpkg -l | grep nvidia

jbjbjb · January 21, 2016 at 3:26 PM

Hi.

Here you have the output:

Code

lspci -nn | grep VGA
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [ION] [10de:0a64] (rev a2)

Code

dpkg -l | grep nvidia
rc  nvidia-304                            304.131-0ubuntu0.14.04.1                     amd64        NVIDIA legacy binary driver - version 304.131
ii  nvidia-340                            340.96-0ubuntu0.14.04.1                      amd64        NVIDIA binary driver - version 340.96
ii  nvidia-common                         1:0.2.91.11                                  amd64        transitional package for ubuntu-drivers-common
rc  nvidia-libopencl1-304                 304.131-0ubuntu0.14.04.1                     amd64        NVIDIA OpenCL Driver and ICD Loader library
rc  nvidia-opencl-icd-304                 304.131-0ubuntu0.14.04.1                     amd64        NVIDIA OpenCL ICD
ii  nvidia-settings                       331.20-0ubuntu8                              amd64        Tool for configuring the NVIDIA graphics driver

Regards.
Javier B.

seahawk1986 · January 21, 2016 at 4:24 PM

You could give nvidia-304 a try, we had several reports that the older driver version might work better.

jbjbjb · January 21, 2016 at 5:01 PM

Hi.

Is there some help web page I can give an eye in order to do that?

I thought the driver installed was the nvidia-304

Javier B.

seahawk1986 · January 21, 2016 at 5:21 PM

Quote from jbjbjb

I thought the driver installed was the nvidia-304

Code

rc  nvidia-304                            304.131-0ubuntu0.14.04.1                     amd64        NVIDIA legacy binary driver - version 304.131
ii  nvidia-340                            340.96-0ubuntu0.14.04.1                      amd64        NVIDIA binary driver - version 340.96

"ii" is an installed package, "rc" is a package that has been installed before but was removed (there is an automatic attempt at installation time to update the nvidia driver using "ubuntu-drivers autoinstall"). Package (de)installation works as always with apt-get:

Code

sudo apt-get remove nvidia-340
sudo apt-get install nvidia-304

jbjbjb · January 21, 2016 at 9:19 PM

Thank you.

Now yaVdr 0.6 starts fine with driver nvidia-304.

Key macros work properly also.

One last question. When I do "sudo apt-get update && sudo apt-get dist-upgrade", the driver nvidia-304 will be updated to the nvidia-340?

Regards.

Javier B.

seahawk1986 · January 21, 2016 at 9:23 PM

Quote from jbjbjb

One last question. When I do "sudo apt-get update && sudo apt-get dist-upgrade", the driver nvidia-304 will be updated to the nvidia-340?

No, the driver version should remain the same.

jbjbjb · January 21, 2016 at 11:39 PM

Thanks a lot for your help.

Javier B.

jbjbjb · January 22, 2016 at 12:29 PM

Hi.

When I removed n-vidia 340 drivers, some errors appeared.

I upload the log here in case the info can be useful to solve the problem in the future.

http://pastebin.com/mS6ExL8c

Regards.
Javier B.

Participate now!