And what about "WS281X-SPI" setting? Is this working or are there also problems expected?
Beiträge von JoeBee
-
-
Well I just tested the configuration: "Test (file)" instead of the WS281x setting.
This started fine. Hm maybe I should just use an Arduino as an intermediate device.Can somebody give me a good link how to configure and what sketch the Arduino needed?
-
your instance is actually failing on initializing the v4l2-grabber - this maybe related to a bug when switching between pal and ntsc, when I had this error, I resolved it by adding „no-switch“ where „pal“ or „ntsc“ are standing in the config. could you verify this?
No this does't helposmc@jb-osmc:~$ sudo service hyperion status
* hyperion.service - Hyperion Systemd service
Loaded: loaded (/etc/systemd/system/hyperion.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Sat 2019-01-19 16:15:47 CET; 13s ago
Process: 1935 ExecStart=/usr/bin/hyperiond /etc/hyperion/hyperion.config.json (code=killed, signal=ABRT)
Main PID: 1935 (code=killed, signal=ABRT)Jan 19 16:15:47 jb-osmc systemd[1]: hyperion.service: Failed with result 'signal'.
Jan 19 16:15:47 jb-osmc systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
Jan 19 16:15:47 jb-osmc systemd[1]: Stopped Hyperion Systemd service.
Jan 19 16:15:47 jb-osmc systemd[1]: hyperion.service: Start request repeated too quickly.
Jan 19 16:15:47 jb-osmc systemd[1]: Failed to start Hyperion Systemd service.
Jan 19 16:15:47 jb-osmc systemd[1]: hyperion.service: Unit entered failed state.
Jan 19 16:15:47 jb-osmc systemd[1]: hyperion.service: Failed with result 'signal'.
osmc@jb-osmc:~$I have to say. the screen grab picture in Hypercon works.
-
I have the same HW Configuration. Current OSMC Version and current Hyperion.
And I have the same problem seems to be that Hyperion is not starting. Any Ideas?
My messages that I get:Code
Alles anzeigenosmc@jb-osmc:~$ sudo systemctl start hyperion.service osmc@jb-osmc:~$ sudo systemctl status hyperion.service * hyperion.service - Hyperion Systemd service Loaded: loaded (/etc/systemd/system/hyperion.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Sat 2019-01-19 15:18:25 CET; 5s ago Process: 1419 ExecStart=/usr/bin/hyperiond /etc/hyperion/hyperion.config.json (code=killed, signal=SEGV) Main PID: 1419 (code=killed, signal=SEGV) Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Service hold-off time over, scheduling restart. Jan 19 15:18:25 jb-osmc systemd[1]: Stopped Hyperion Systemd service. Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Start request repeated too quickly. Jan 19 15:18:25 jb-osmc systemd[1]: Failed to start Hyperion Systemd service. Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Unit entered failed state. Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Failed with result 'signal'. osmc@jb-osmc:~$ osmc@jb-osmc:~$ osmc@jb-osmc:~$ journalctl -xe Jan 19 15:18:25 jb-osmc hyperiond[1419]: "type" : "ws281x" Jan 19 15:18:25 jb-osmc hyperiond[1419]: } Jan 19 15:18:25 jb-osmc hyperiond[1419]: whiteAlgorithm :: Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: Creating linear smoothing Jan 19 15:18:25 jb-osmc hyperiond[1419]: HYPERION (CS) INFO: Created linear-smoothing(interval_ms=50;settlingTime_ms=200;updateDelay=0 Jan 19 15:18:25 jb-osmc hyperiond[1419]: EFFECTENGINE INFO: 27 effects loaded from directory /usr/share/hyperion/effects Jan 19 15:18:25 jb-osmc hyperiond[1419]: EFFECTENGINE INFO: Initializing Python interpreter Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: Hyperion started and initialised Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: Boot sequence 'Rainbow swirl fast' EFFECTENGINE INFO: run effect Rainbow swirl fast on channel 0 Jan 19 15:18:25 jb-osmc hyperiond[1419]: BLACKBORDER INFO: threshold set to 0 (0) Jan 19 15:18:25 jb-osmc hyperiond[1419]: BLACKBORDER INFO: mode:default Jan 19 15:18:25 jb-osmc hyperiond[1419]: started Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: Json server created and started on port 19444 Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: Proto server created and started on port 19445 Jan 19 15:18:25 jb-osmc hyperiond[1419]: DISPMANXGRABBER INFO: Display opened with resolution: 1920x1080 Jan 19 15:18:25 jb-osmc hyperiond[1419]: BLACKBORDER INFO: threshold set to 0 (0) Jan 19 15:18:25 jb-osmc hyperiond[1419]: BLACKBORDER INFO: mode:default Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: Frame grabber created and started Jan 19 15:18:25 jb-osmc hyperiond[1419]: V4L2GRABBER INFO: width=720 height=576 Jan 19 15:18:25 jb-osmc hyperiond[1419]: V4L2GRABBER INFO: pixel format=UYVY Jan 19 15:18:25 jb-osmc hyperiond[1419]: BLACKBORDER INFO: threshold set to 0 (0) Jan 19 15:18:25 jb-osmc hyperiond[1419]: BLACKBORDER INFO: mode:default Jan 19 15:18:25 jb-osmc hyperiond[1419]: V4L2GRABBER INFO: signal threshold set to: {0,0,0} Jan 19 15:18:25 jb-osmc hyperiond[1419]: V4L2GRABBER INFO: started Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: V4L2 grabber created and started Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Main process exited, code=killed, status=11/SEGV Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Unit entered failed state. Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Failed with result 'signal'. Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Service hold-off time over, scheduling restart. Jan 19 15:18:25 jb-osmc systemd[1]: Stopped Hyperion Systemd service. -- Subject: Unit hyperion.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit hyperion.service has finished shutting down. Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Start request repeated too quickly. Jan 19 15:18:25 jb-osmc systemd[1]: Failed to start Hyperion Systemd service. -- Subject: Unit hyperion.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit hyperion.service has failed. -- -- The result is failed. Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Unit entered failed state. Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Failed with result 'signal'. Jan 19 15:18:30 jb-osmc sudo[1426]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/systemctl status hyperion.service Jan 19 15:18:30 jb-osmc sudo[1426]: pam_unix(sudo:session): session opened for user root by osmc(uid=0) Jan 19 15:18:30 jb-osmc sudo[1426]: pam_unix(sudo:session): session closed for user root osmc@jb-osmc:~$
