Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Roms won´t start - strange problem



  • Ok, so a few things:

    The runcommand window and anything terminal based will be launched on the "console" tied to the main process that launches emulationstation.

    If it's launched from SSH, you'll see them in your SSH window.
    If it's launched "normally" from the raspbian boot, it would show on the TV.

    The message you're getting on runcommand seems to suggest the same: it can't find or use the console for whatever it's trying to (that's /dev/tty).

    I don't know enough about autostart and such. If you're confident that this is a very recent change, it'd probably warrant a bit more investigation, but last time it was changed it was 3 months ago, so if you installed this 2 weeks ago, then no changes would have been made since.

    That particular line (965) has been there for 7 months as well.

    If you're keen on troubleshooting, you may want to try to revert to previous versions of runcommand.sh and see if it helps - if you manage to narrow down a version where it runs and one where it doesn't, I'm hopeful it can be fixed.

    That's the best we can offer at this stage.

    If you want to clarify a bit more what you mean by launching with autostart, that may help. Are you running X? Is this launched on boot?


  • Global Moderator

    A summary so far:

    Pi Model or other hardware: Pi3
    RetroPie Version Used: 4.27
    Built From: On top of existing undisclosed version of Raspbian
    Error messages received:
    Log found in /dev/shm/runcommand.log (if relevant): Log found in undisclosed location:

    /opt/retropie/supplementary/runcommand/runcommand.sh: Zeile 965: /dev/tty: Kein passendes Gerät bzw. keine passende Adresse gefunden
    Unable to open /dev/tty
    

    Guide used: https://github.com/RetroPie/RetroPie-Setup/wiki/Manual-Installation
    How to replicate the problem: Launching a file locally fails, resulting in a return to Emulation Station.



  • Thank you for your effort in this.
    I should have said this earlier :-(

    There is no X environment running on the pi.

    I mean when i enable the option that ES/RP starts directly at boot time.
    Then there are no tty screens displayed.

    As you have written correctly, in ssh all is fine.

    Even if i disable the runcommand options its still the same.
    I am near to give up..



  • @Dlay I wouldn't say it's time to give up yet.

    Where do you set the option to launch it at boot? As I said I don't know enough about auto start. Is there a set of other services or commands you're running there? Maybe one is taking hold of the console.

    Can you share the list of services/commands you're running and then testing removing them one by one to see if we narrow it down?

    Then maybe it's easier to search for how to mitigate that.



  • You can set it in Retropie-Setup

    Under C - Configuration / tools
    then 802 - autostart
    then 1 - Start Emulation Station at boot


  • Global Moderator

    @Dlay

    If you would, post the contents of /etc/emulationstation/es_systems.cfg.

    Edit: Nevermind. I had a idea, but your error makes it unlikely.

    Edit 2: A listing of your services and commands would indeed be helpful.



  • what do you mean with services and commands ?



  • @Dlay
    service --status-all


  • Global Moderator

    @Dlay

    Since you've installed RetroPie over an existing system that was originally tasked with other purposes, a list of running services or commands launched at startup might shed some light on the issue and any conflicts that may exist.

    Running services can be discovered with:

    service --status-all
    

    As noted above. Also, an alternative is:

    systemctl list-unit-files | grep enabled
    

    And you should check /etc/rc.local for launch commands.



  • [ + ] acpid
    [ + ] alsa-utils
    [ - ] anacron
    [ - ] asplashscreen
    [ + ] avahi-daemon
    [ + ] bluetooth
    [ - ] bootlogs
    [ - ] bootmisc.sh
    [ - ] checkfs.sh
    [ - ] checkroot-bootclean.sh
    [ - ] checkroot.sh
    [ + ] clamav-daemon
    [ + ] clamav-freshclam
    [ + ] collectd
    [ + ] console-setup
    [ + ] cpufrequtils
    [ + ] cron
    [ + ] dbus
    [ + ] dhcpcd
    [ + ] dphys-swapfile
    [ + ] fake-hwclock
    [ + ] fhem
    [ + ] hdparm
    [ - ] hostname.sh
    [ - ] hwclock.sh
    [ + ] kbd
    [ + ] keyboard-setup
    [ - ] killprocs
    [ + ] kmod
    [ + ] loadcpufreq
    [ - ] lvm2
    [ - ] mdadm
    [ + ] mdadm-raid
    [ - ] mdadm-waitidle
    [ + ] minidlna
    [ + ] monit
    [ - ] motd
    [ - ] mountall-bootclean.sh
    [ - ] mountall.sh
    [ - ] mountdevsubfs.sh
    [ - ] mountkernfs.sh
    [ - ] mountnfs-bootclean.sh
    [ - ] mountnfs.sh
    [ + ] networking
    [ - ] nfs-common
    [ + ] nfs-kernel-server
    [ + ] nginx
    [ + ] nmbd
    [ + ] ntp
    [ + ] php5-fpm
    [ - ] plymouth
    [ - ] plymouth-log
    [ - ] postfix
    [ + ] procps
    [ + ] proftpd
    [ + ] quota
    [ - ] quotarpc
    [ + ] raspi-config
    [ + ] rc.local
    [ + ] resolvconf
    [ - ] rmnologin
    [ + ] rpcbind
    [ + ] rrdcached
    [ - ] rsync
    [ + ] rsyslog
    [ + ] samba
    [ + ] samba-ad-dc
    [ - ] saned
    [ - ] screen-cleanup
    [ - ] sendsigs
    [ + ] smartmontools
    [ + ] smbd
    [ + ] snmpd
    [ + ] ssh
    [ - ] sudo
    [ + ] triggerhappy
    [ + ] udev
    [ + ] udev-finish
    [ - ] umountfs
    [ - ] umountnfs.sh
    [ - ] umountroot
    [ + ] urandom
    [ - ] watchdog
    [ - ] wd_keepalive
    [ - ] x11-common



Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.