This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

can't create /var/run/matrix-gui-e.pid

Other Parts Discussed in Thread: AM3894

Hi all,

I'm porting ezsdk Linux dm816evm 5.03.01.05 to custom board with Sitara AM3894 processor. And I having a problem with GUI appearing on monitor. Linux boots but there is no picture on monitor, but I can see that monitor has a backlight so I suppose that video drivers are loaded properly.

I have typed lsmod to console and this is a output message I got:

root@dm816x-evm:~# lsmod
Module                  Size  Used by
bufferclass_ti          4946  0
omaplfb                10794  0
pvrsrvkm              155450  2
ipv6                  209855  12
ti81xxhdmi             14478  0
ti81xxfb               21771  1
vpss                   72346  3 omaplfb,ti81xxhdmi,ti81xxfb
syslink              1113011  0

As I can see after Linux boots is this message Starting Matrix GUI application/etc/rc5.d/S99matrix-gui-e: line 46: can't create /var/run/matrix-gui-e.pid: nonexistent directory and I think this is the reason I don't get any output on monitor over HDMI.

This is boot log 3731.linux_qt_sitara.txt

BR,

Srdjan

  • Srdjan Radulovic said:
    As I can see after Linux boots is this message Starting Matrix GUI application/etc/rc5.d/S99matrix-gui-e: line 46: can't create /var/run/matrix-gui-e.pid: nonexistent directory and

    If your root filesystem allow write your can create directory manually mkdir -p /var/run

  • Hi Kirill,

    I can't create that folder, linux prevents me, this is message I get:
    root@dm816x-evm:~# mkdir -p /var/run
    mkdir: cannot create directory '/var/run': No such file or directory

    This is list of devices in /var folder:

    root@dm816x-evm:/var# ls -all
    drwxr-sr-x    7 root     root         4096 Dec  9 07:54 .
    drwxr-xr-x   19 root     root         4096 Feb 17  2012 ..
    drwxr-sr-x    2 root     root         4096 Dec  9 09:13 backups
    lrwxrwxrwx    1 root     root           14 Feb 17  2012 cache -> volatile/cache
    drwxr-sr-x    7 root     root         4096 Dec  9 09:42 lib
    drwxr-sr-x    2 root     root         4096 Dec  9 09:13 local
    lrwxrwxrwx    1 root     root           13 Feb 17  2012 lock -> volatile/lock
    lrwxrwxrwx    1 root     root           12 Feb 17  2012 log -> volatile/log
    lrwxrwxrwx    1 root     root           12 Feb 17  2012 run -> volatile/run
    drwxr-sr-x    2 root     root         4096 Dec  9 09:13 spool
    lrwxrwxrwx    1 root     root           12 Feb 17  2012 tmp -> volatile/tmp
    drwxrwxrwt    2 root     root           40 Jan  1  2000 volatile

    BR,

    Srdjan

  • Srdjan Radulovic said:
    root@dm816x-evm:~# mkdir -p /var/run
    mkdir: cannot create directory '/var/run': No such file or directory

    This is list of devices in /var folder:

    root@dm816x-evm:/var# ls -all
    .......................................
    lrwxrwxrwx    1 root     root           12 Feb 17  2012 run -> volatile/run
    ..........................................
    drwxrwxrwt    2 root     root           40 Jan  1  2000 volatile

    Ok, you have directory /var/run, it is a symlink on /var/volatile/run. Check directory /var/volatile and if it isn't contain directory run you can create it mkdir -p /var/volatile/run. If /var/volatile contain directory run recheck access right on it.

    Also you can check mount options for /var in /proc/mounts, it must have rw.
    As example, /proc/mounts from my system:
    ~ # cat /proc/mounts
    rootfs / rootfs rw 0 0
    /dev/root / nfs rw,vers=2,rsize=4096,wsize=4096,hard,nolock,proto=udp,timeo=11,retrans=2,sec=sys,addr=192.168.255.1 0 0
    none /proc proc rw 0 0
    none /sys sysfs rw 0 0
    none /tmp tmpfs rw 0 0
    none /dev tmpfs rw 0 0
    none /var/run tmpfs rw 0 0
    none /dev/pts devpts rw 0 0

  • Hi,

    this is what my /proc/mounts contains:


    root@dm816x-evm:~# cat /proc/mounts

    rootfs / rootfs rw 0 0
    /dev/root / ext3 rw,relatime,errors=continue,barrier=0,data=writeback 0 0
    devtmpfs /dev devtmpfs rw,relatime,size=101672k,nr_inodes=25418,mode=755 0 0
    proc /proc proc rw,relatime 0 0
    tmpfs /mnt/.splash tmpfs rw,relatime,size=40k 0 0
    sysfs /sys sysfs rw,relatime 0 0
    none /dev tmpfs rw,relatime,size=1024k,nr_inodes=8192,mode=755 0 0
    /dev/mmcblk0p2 /media/mmcblk0p2 ext3 rw,relatime,errors=continue,barrier=0,data=writeback 0 0
    /dev/mmcblk0p1 /media/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
    devpts /dev/pts devpts rw,relatime,gid=5,mode=620 0 0
    usbfs /proc/bus/usb usbfs rw,relatime 0 0
    tmpfs /var/volatile tmpfs rw,relatime,size=16384k 0 0
    tmpfs /dev/shm tmpfs rw,relatime,mode=777 0 0
    tmpfs /media/ram tmpfs rw,relatime,size=16384k 0 0

    I checked if my /var/volatile contains directory run and it didn't contain nothing, it was empty. So I made new directory  mkdir -p /var/volatile/run, after a reboot I haven't made a progress. I still don't have no picture on monitor, only backlight. But after reboot, when I check /var/volatile directory run directory doesn't exist any more.

    Regards,

    Srdjan

  • Srdjan Radulovic said:
    root@dm816x-evm:~# cat /proc/mounts
    ..................................
    tmpfs /var/volatile tmpfs rw,relatime,size=16384k 0 0
    ..............................

    So I made new directory  mkdir -p /var/volatile/run, after a reboot I haven't made a progress. I still don't have no picture on monitor, only backlight. But after reboot, when I check /var/volatile directory run directory doesn't exist any more.

    This is a normal, directory /var/volatile exist in RAM, you must create directory in it after each boot.
    You can put commant mkdir -p /var/volatile/run in any running after boot script, e.g. in script run your application.

  • Hi Kirill,

    I've added making of run directory in /va/volatile/run in script load-hd-firmware.sh that loads video drivers but still no picture. After kernel boots now I get this message Starting Matrix GUI application. This is some kind of progress but there is still a problem that is preventing my system to generate output on monitor.

    Regards,

    Srdjan

  • Srdjan Radulovic, I think this is a another question ;)

  • Hi,

    maybe it is, but my problem still stands :)...are you suggesting I should open a new one on forum?

    BR,

    Srdjan