hello,
i tried it in the german forum first, but i dont think, that someone could help me there, so i try my luck here. i hope its alright. if not, than a mod could maybe delete my thread in the german forum. (thx)
so...here we go...i had my raspi3b connected with a alexa switch. so everytime i cut off the power, the pi lose is power completely...thats bad, so i have it now running 24/7h and only my tv, avr and the leds lose the complete power, when i turn it off with my alexa.
someone said, that maybe my system is damaged (raspbian jessie), so i formatted my sdcard and started new, but with raspbian stretch lite. there i didnt have luck...hyperion isnt working. so i started again from the beginning, but now with the newest version of raspbian jessie! but it also dont work. and i got exact the same error message
ZitatAlles anzeigen
ssh in: Jan 23 09:34:55 raspberrypi hyperiond[1313]: BLACKBORDER INFO: threshold set to 0.18 (46)
ssh in: Jan 23 09:34:55 raspberrypi hyperiond[1313]: BLACKBORDER INFO: mode:default
ssh in: Jan 23 09:34:55 raspberrypi hyperiond[1313]: started
ssh in: Jan 23 09:34:55 raspberrypi hyperiond[1313]: INFO: Json server created and started on port 19444
ssh in: Jan 23 09:34:55 raspberrypi systemd[1]: hyperion.service: main process exited, code=killed, status=6/ABRT
ssh in: Jan 23 09:34:55 raspberrypi systemd[1]: Unit hyperion.service entered failed state.
ssh in: Jan 23 09:34:55 raspberrypi hyperiond[1313]: INFO: Proto server created and started on port 19445
ssh in: Jan 23 09:34:55 raspberrypi hyperiond[1313]: terminate called after throwing an instance of 'std::runtime_error'
ssh in: Jan 23 09:34:55 raspberrypi hyperiond[1313]: what(): VIDIOC_S_INPUT ERROR 22, Invalid argument
ssh in: Jan 23 09:34:55 raspberrypi systemd[1]: hyperion.service holdoff time over, scheduling restart.
ssh in: Jan 23 09:34:55 raspberrypi systemd[1]: Stopping Hyperion Systemd service...
ssh in: Jan 23 09:34:55 raspberrypi systemd[1]: Starting Hyperion Systemd service...
ssh in: Jan 23 09:34:55 raspberrypi systemd[1]: hyperion.service start request repeated too quickly, refusing to start.
ssh in: Jan 23 09:34:55 raspberrypi systemd[1]: Failed to start Hyperion Systemd service.
ssh in: Jan 23 09:34:55 raspberrypi systemd[1]: Unit hyperion.service entered failed state.
ssh in: Jan 23 09:35:00 raspberrypi systemd[1]: Stopped Hyperion Systemd service.
ssh in: Jan 23 09:35:01 raspberrypi systemd[1]: Starting Hyperion Systemd service...
ssh in: Jan 23 09:35:01 raspberrypi systemd[1]: hyperion.service start request repeated too quickly, refusing to start.
ssh in: Jan 23 09:35:01 raspberrypi systemd[1]: Failed to start Hyperion Systemd service.
how could i fix this problem?
Zitatsudo hyperion status
tells me this:
Zitat
pi@raspberrypi:~ $ service hyperion status
● hyperion.service - Hyperion Systemd service
Loaded: loaded (/etc/systemd/system/hyperion.service; enabled)
Active: failed (Result: start-limit) since Wed 2019-01-23 09:34:55 UTC; 17min ago
Main PID: 1313 (code=killed, signal=ABRT)
than i tried this:
Zitatjournalctl -u hyperion.service
No journal files were found, is what i get as answer.
after that i tried
Zitatlsusb
it shows me:
Zitat
pi@raspberrypi:~ $ lsusb
Bus 001 Device 004: ID 1b71:3002
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
im not sure, but should be "1b71:3002" my grabber? i cant remember, but i think i had also a name after that numbers, when hyperion was working. i disconnected than everything....waited about n hour and started up all again. now in hypercon i could grab a picture....so, the grabber seems to work?
now i reached the end of my (small) linux knowing...i hope someone can help me with it. if you need more infos, just tell me.
info: i attached my configfile of my hyperion setup. maybe it helps?
thnaks