search

motioneye-project / motioneyeos

A Video Surveillance OS For Single-board Computers
Other
7.9k stars 904 forks source link

Odroid HC1 reboot does not work #2784

Open Klausoleum opened 3 years ago

Klausoleum commented 3 years ago

Hello,

I tried an update on my Odroid HC1 (server without cam). I used the download version of the Odroid XU4 for this. The hardware is the same (HC1 has no HDMI) and has always worked so far. All versions up to and including 11 Sep 2019 (20190911) work perfectly.

With all versions that came after that, the reboot generally does not work. If the power supply is interrupted, the system will restart properly.

Can it be related to the kernel version? From version 20200203, which no longer works on the HC1, the kernel of the XU4 was changed to version 4.14. Unfortunately, the HC1 is now also discontinued.

Does anyone know where my problem is?

motioneye.log boot.log dmesg.log messages.zip

starbasessd commented 3 years ago

Did you look at: https://github.com/ccrisan/motioneyeos/issues/908 https://github.com/ccrisan/motioneyeos/issues/1892

Klausoleum commented 3 years ago

Did you look at:

908

1892

Thanks for the referrals @starbasessd . My system boots great. Only the reboot does not work. After the reboot, only the red LED lights up on the board. The blue LED no longer flashes. After an interruption in the power supply, everything starts up again. I am using a 16GB SanDisk SD-Card

starbasessd commented 3 years ago

Which is the same symptom on some of the other odroids. Works fine first boot, then reboot goes south. Usually because motionEyeOS tries to /extend/format the partitions, but the system oops's. Does yours have emmc?

starbasessd commented 3 years ago

Do you have a USB Thumb or other drive attached?

cap9qd commented 3 years ago

If you change the boot options I will reboot but will puke out quite a bit of kernel info.

Also there are instructions for getting the serial consol running if you're interested.

https://github.com/ccrisan/motioneyeos/issues/2597#issuecomment-766144660

On Sat, Aug 7, 2021, 16:22 starbasessd @.***> wrote:

Do you have a USB Thumb or other drive attached?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2784#issuecomment-894708239, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIBKIUD2HW2VJWAVL2P4ZLTT3WP25ANCNFSM5BXX6KAQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

cap9qd commented 3 years ago

Here is the serial console changes.

https://github.com/ccrisan/motioneyeos/issues/2655#issue-792615486

On Sat, Aug 7, 2021, 16:40 Curtis Parrott @.***> wrote:

If you change the boot options I will reboot but will puke out quite a bit of kernel info.

Also there are instructions for getting the serial consol running if you're interested.

https://github.com/ccrisan/motioneyeos/issues/2597#issuecomment-766144660

On Sat, Aug 7, 2021, 16:22 starbasessd @.***> wrote:

Do you have a USB Thumb or other drive attached?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2784#issuecomment-894708239, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIBKIUD2HW2VJWAVL2P4ZLTT3WP25ANCNFSM5BXX6KAQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

Klausoleum commented 3 years ago

Which is the same symptom on some of the other odroids. Works fine first boot, then reboot goes south. Usually because motionEyeOS tries to /extend/format the partitions, but the system oops's. Does yours have emmc?

i don't use emc. There is only one HDD installed on the SATA port. otherwise nothing is plugged in or connected (except ethernet).

cap9qd commented 3 years ago

We're you able to implement the changes for the reboot fix? Just curious if my observations and changes can br confirmed by someone else with an HC1/2.

On Sat, Aug 7, 2021, 16:54 Klausoleum @.***> wrote:

Which is the same symptom on some of the other odroids. Works fine first boot, then reboot goes south. Usually because motionEyeOS tries to /extend/format the partitions, but the system oops's. Does yours have emmc?

i don't use emc. There is only one HDD installed on the SATA port. otherwise nothing is plugged in or connected (except ethernet).

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2784#issuecomment-894710748, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIBKIUDV2E7BQSDBNWALPMDT3WTQPANCNFSM5BXX6KAQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

starbasessd commented 3 years ago

How does your drive show up? mmcblk0p1 or sda1 or something else?

Klausoleum commented 3 years ago

How does your drive show up? mmcblk0p1 or sda1 or something else?

the hard drive is mounted as sda1

grafik

Klausoleum commented 3 years ago

We're you able to implement the changes for the reboot fix? Just curious if my observations and changes can br confirmed by someone else with an HC1/2. …

yes, I can do it with pleasure. Can you quickly link the reboot to me?

I'm currently back to a working 2019 version. The 2021 version also seems to have a bug when saving videos. after a while, only defective files with 0 or 269 bytes are saved.

If necessary, I can run tests on a different memory card at any time.

starbasessd commented 3 years ago

@Klausoleum Do you have a file in /boot like cmdline.txt? If you do, is there something like root=/dev/mmcblk0p2 or root=/dev/sda2 there? If so, can you change it to root=/dev/mmcblk1p2 I'm wondering if either of the 1st two are hard coded, and needs to be 'fixed' to a floating value.

Klausoleum commented 3 years ago

@starbasessd I found the information in the boot.ini. The right information is already there, just as you wanted to change it.

ODROIDXU-UBOOT-CONFIG setenv fdt_high "0xffffffff"setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; fatload mmc 0:1 0x42000000 uInitrd; fatload mmc 0:1 0x44000000 exynos5422-odroidxu4.dtb; bootz 0x40008000 - 0x44000000" setenv bootargs "console=tty1 root=/dev/mmcblk1p2 rootwait ro no_console_suspend panic=10 quiet loglevel=1" boot

starbasessd commented 3 years ago

Sorry, it was a shot...