You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some users have reported problems with starting m8c:
pi@retropie:~/code/m8c $ ./m8c
INFO: Looking for USB serial devices.
INFO: Found M8 in /dev/ttyACM1.
INFO: Opening port.
INFO: Enabling and resetting M8 display
INFO: Reset display
and after that, the program returns into terminal.
Sometimes the error might look something like:
INFO: Reading config /home/jonne/.local/share/m8c/config.ini
INFO: Writing config file to /home/jonne/.local/share/m8c/config.ini
INFO: Looking for USB serial devices.
INFO: Found M8 in /dev/ttyACM1.
INFO: Opening port.
ERROR: Error: Failed: Inappropriate ioctl for device
This seems to be a conflict with some Linux kernel versions and libserialport (sigrokproject/libserialport@6f9b03e) and the error can be mitigated by building libserialport from sources:
Remove existing libserialport packages
for example, on Debian based systems apt-get remove libserialport0 libserialport-dev
If the following appears after building libserialport manually
jonne@jonne-ThinkPad-T440p:~/Code/m8c$ ./m8c
./m8c: error while loading shared libraries: libserialport.so.0: cannot open shared object file: No such file or directory
You probably need to link the libraries to the correct place
laamaa
changed the title
Linux / m8c fails to start at "INFO: Reset display"
Linux / m8c fails to start at "INFO: Reset display" / invalid ioctl
Mar 21, 2022
Some users have reported problems with starting m8c:
and after that, the program returns into terminal.
Sometimes the error might look something like:
This seems to be a conflict with some Linux kernel versions and libserialport (sigrokproject/libserialport@6f9b03e) and the error can be mitigated by building libserialport from sources:
for example, on Debian based systems
apt-get remove libserialport0 libserialport-dev
The text was updated successfully, but these errors were encountered: