Ok i will post it tomorrow cause now I'm on the rpi3...
Hyperbian + Hyperion ng + ezcap 269
- Tyler983
- Erledigt
-
-
-
These errors are specific for that system/config, if other things work on Rpi3 then you can ignore them on Rpi4 too.
Try remove console=serial0, console=ttyAMA0 and console=ttyS0 from cmdline.txt.
Seems that ttyAMA0 is taken over at start up again (not by bluetooth).https://www.raspberrypi.org/do…ion/configuration/uart.md
It's highly problematic USB to lightberry converter, sorry.
-
I think you’re right, cause I have the same errors on the rpi3 but there less are on...
Where I can remove those strings? -
-
Thx i'll give it a read
another thing... i generate a lut file, but as you explain in the first post, i haven't : the Hyperion configuration folder.Typically /home/pi/.hyperion/.....
I searched it with cyberduck but folder "pi" is empty.
-
Read hyperion logs
-
-
Post dmesg after changes
-
Ok when i'll be at home i'll post it
-
-
OK, lets try this:
Codesudo systemctl stop serial-getty@ttyAMA0.service sudo systemctl disable serial-getty@ttyAMA0.service sudo systemctl mask serial-getty@ttyAMA0.service sudo reboot
If it doesn't help could you provide output after reboot of:
Codels -l /dev/ttyACM0 (try to execute it again with lightberry connected/disconnected to compare, reboot before each action)
and content of /boot/config.txt and logs from hyperion WWW page to check what's happening inside. -
Sudo commands doesn't function, so I tried with lightberry connected and this is the result
pi@raspberrypi:~ $ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0 Sep 26 16:20 /dev/ttyACM0with lightberry disconnected:
pi@raspberrypi:~ $ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0 Sep 26 16:22 /dev/ttyACM0 -
Zitat
[hyperiond DISPMANXGRABBER] (ERROR) Previous line repeats 200 times
Definitely not good. Forget for now about Lightberry. Did you disabled system/platform grabber as it's completely broken in Hyperion.NG alpha 8 on Rpi4? -
Tradotto in:
Italiano
Spettacolo originale
Now I've disabled it... there's something other I ca do?
[LEFT]Original text[/LEFT]
Contribute a better translation -
Yes, post logs from Hyperion after change
-
2020-09-26T15:43:39.709Z [hyperiond DAEMON] (ERROR) The CEC handler can not be instantiated, because it has been left out from the build 2020-09-26T15:44:33.787Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'adalight' signals error: 'Timeout writing data to ttyACM0'
-
With your previos log you've got that error ('Timeout writing data to ttyACM0') only when the light-berry was disconnected. Did you connect it again and rebooted? PS: put debug level to DEBUG as now we can see only errors.
-
Yes, I've pugged lightberry and rebooted it.
this is the log in debug mode:2020-09-26T15:43:39.709Z [hyperiond DAEMON] (ERROR) The CEC handler can not be instantiated, because it has been left out from the build 2020-09-26T15:44:33.787Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'adalight' signals error: 'Timeout writing data to ttyACM0' 2020-09-26T15:48:40.024Z [hyperiond V4L2:AUTO] (DEBUG) (V4L2Grabber.cpp:992:process_image()) Video FPS: 29.88, av. delay: 38ms, good: 1773, bad: 20 (60.03,15)
-
Strange, because there wasn't that error in the log before, maybe it was taken to soon before it occured.
Anyway it isn't fully log from Hyperion in DEBUG mode but a part of it.Summarize:
1) you took full copy of working system from Rpi3 to Rpi4
2) Rpi4 doesnt work. In normal circumstances we can exclude Hyperion as a suspected because the config is the same and it works on Rpi3.
3) But it isn't that case as Alpha 8 has broken system grabber on Rpi4. And system grabber is enabled...
4) We try to overcome Serial port problem again but it's dead end as the Hyperion isn't working (didnt you notice it in the hyperion log?)
5) Now we have AMA0 in unknown state after some experiments. Not sure if it isnt problem but the path of changes to make it work was definitely wrong based on wrong diagnosis.So I propose to disable system grabber on Rpi 3 then to make a full copy of that working system to another card and try to run it on Rpi 4 again
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!