vchiq problem

[clausmuus]

Hi,

since I use the latest firmware, and vc libs, I get this error message:

Code Select Expand

20:23:13.561775 [info]   2702 Core - Starting up...
20:23:13.564580 [info]   2702 Core - Signal handlers set up successfully
20:23:13.566692 [EMERG]  2702 Core - Could not retrieve free virtual console, please change permissions
20:23:13.572944 [notice] 2702 Remote - Init LibCEC
* failed to open vchiq instance
If I look in the firmware and kernel change log, I see, that there a lot of changes to the vchiq.
Do you also has this problem with the latest version or do you know a solution?

Claus

[clausmuus]

Ich denke mal, es hängt mit diesem Update der Firmware zusammen:  "Update to new firmware. Includes vdec3 but without vchiq. Updated code at LKG45"
https://github.com/raspberrypi/firmware/commit/6ada03c1c23372546a036821098aa1ab6009cb41

Claus

[MartenR]

No, it does not have to do with vchiq. Here the code for getting a free virtual console fails. May be there is no free console in the moment? (If you do console switching with a skript before startung vomp, remove this)
The code which fails is on main.cc, search for the error message.
Please check the permissions of /dev/tty, mine are:

Code Select Expand

crw-rw-rw- 1 root root 5, 0 Jan  1  1970 /dev/tty


Marten

[Uwe]

Hi Marten,
the code is working with you? Here it does not work with that, too. Error as above by clausmus...

[clausmuus]

Hi Marten,

what is a free (non open) tty? I can switch via chvt to every console up to 63. Only console 1-4 is in use. However, I get this error message, that there is no free vt.
Do you know, if I must first init a free console?

Claus

[MartenR]

@Uwe:
Sure the code is working. If I use it over ssh, /dev/tty could not be opened and vomp continues without switching the console.
If I log into a local console everything  is fine.
@clausmuus
A non open tty is a tty with no attached program, so no x and no terminal.
You do not have to init the console.

@both
tell me how you start the program and check the permissions.

Marten

[clausmuus]

Hi,

I start the vompclient via "vompclinet -s 127.0.0.1 -n 2>&1 >/var/log/vompclient" in the init script as root. I also try to start it via ssh (as root). I don't try to start it (until now) as demon (every time I use the option -n or -d).
The Permissions of the tty are:

Code Select Expand

crw-rw-rw-    1 root     tty         5,   0 Jan  1  1970 /dev/tty
crw-rw----    1 root     tty         4,   0 Jan  1  1970 /dev/tty0
crw-------    1 root     root        4,   1 Jan  1  1970 /dev/tty1
crw-rw----    1 root     tty         4,  10 Jan  1  1970 /dev/tty10
crw-rw----    1 root     tty         4,  11 Jan  1  1970 /dev/tty11
crw-rw----    1 root     tty         4,  12 Jan  1  1970 /dev/tty12
...
I think the permissions are ok (sins I start it as root) and lot's of tty are free.
I do not switch the console at startup, so the vompclinet will be started as the tty1 is shown.

Claus

[MartenR]

Can you check, if it works with older versions of the firmware.. Since I do not see any other difference to my setup except, that I stick to the firmware in the debian packages on raspbian.

Marten

[clausmuus]

I have test it already with the firmware Version of Sep 26. That don't helps.

Claus

[MartenR]

The problem is a have no idea what is different at your setup...
Did you test it on rasbian, do you have there the same problem???

Marten

[clausmuus]

No, I don't test it on raspian. I use raspian only in a VM to build my distry.
I will test today, to disable the auto select and switch to a free console before start the vompclient.
I will also test and older installation with the newest vompclient.

Claus

[clausmuus]

Hi,

now I test an update of a older installation with the latest firmware and the same vompclient as I use in my newer installation. This starts without problems. I think I have now a lot of work, until I find the different between this both installation. I was sure, this both was the only different,...

Claus

[clausmuus]

I have found the reason. It's the new kernel. Now I must see, witch part of the kernel makes the problem. Mainly the frequence scaling is added in the new kernel.

Claus

[MartenR]

Maybe it helps, the problem is an ioctl to the kernel.
Look at the kernel configuration for konsole handling, since this is failing.

Marten

[clausmuus]

Hi,

after I use again the latest version (a some days newer version) of the kernel, the problem gone.
So it was only a problem of a single kernel version.

Claus