Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

boot fails on R4SE #24

Open
MrZajda opened this issue Jan 3, 2024 · 8 comments
Open

boot fails on R4SE #24

MrZajda opened this issue Jan 3, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@MrZajda
Copy link

MrZajda commented Jan 3, 2024

Describe the issue you are experiencing

HW :Rock 4SE SDcard installation
after power on loader reports :
Model: Radxa ROCK Pi 4A _why?

..ends with message "Starting kernel" and freeze afterwards.

What operating system image do you use?

rock-4se

What version of Home Assistant Operating System is installed?

trying latest 11.2

Did you upgrade the Operating System.

No

Steps to reproduce the issue

  1. install haos_rock-4se_11.2... on SD card using balena etcher
    2.put SD card into rock 4SE sd slot
  2. power on
    ...

Anything in the Supervisor logs that might be useful for us?

not able to report

Anything in the Host logs that might be useful for us?

it is not able to start with default setup

System information

No response

Additional information

No response

@MrZajda MrZajda added the bug Something isn't working label Jan 3, 2024
@citruz
Copy link
Owner

citruz commented Jan 3, 2024

HW :Rock 4SE SDcard installation after power on loader reports : Model: Radxa ROCK Pi 4A _why?

Some boards have no specific configuration for the uboot bootloader so the generic config is used which shows up as 4A. That has worked in the past and shouldn’t be an issue though.

Can you please try older versions such as 9.5 or 10.0?

@MrZajda
Copy link
Author

MrZajda commented Jan 5, 2024

Thanks for such quick response.
I have tried to boot with 10.0 and 9.5. as well with very same results - freezes after kernel starting.

Some screenshots:
Snímek obrazovky 2024-01-05 115859
ached.
Snímek obrazovky 2024-01-05 120051
Snímek obrazovky 2024-01-05 120216
and finally with flooded display effect :)
Snímek obrazovky 2024-01-05 120234

What do you think might be the issue?

Petr

@citruz
Copy link
Owner

citruz commented Jan 9, 2024

The stripes on the display are, believe it or not, a good sign. It means that the kernel has started but probably crashed early in the initialization.
Unfortunately without serial logs this is impossible to debug. Do you have a USB to serial adapter?

@MrZajda
Copy link
Author

MrZajda commented Feb 5, 2024

Sorry , I dont have anything like that.. I am just beginner.
So is there any other possibility to do ?

@citruz
Copy link
Owner

citruz commented Feb 5, 2024

Hmm.. the logs/screenshots you provided all look good. What happens after the stripes appear on the display? Do they stay?

@MrZajda
Copy link
Author

MrZajda commented Feb 6, 2024 via email

@DuncanDotPY
Copy link

Just to add, I've now run into the same issue on a 4c+. I had a long-running & stable homeassistant setup running on it that stopped working all of a sudden.

Initially, I tried to boot an old instance from another SD card which ran into the same issue. I reimaged that old SD with debian and it worked fine. Then reimaged again with different releases of haos-rockpi and all of them failed each time.

So I've ruled out that the SD cards are the issue (as I tried multiple and managed to boot debian). It shouldn't be a software issue considering it was working once upon a time and I tried different versions/older images? But also considering the same board worked for debian it doesn't overtly look like a hardware issue?

So I'm stumped - but I'm a bit of a noob at this stuff also. Any suggestions? I'm going to order another 4c+ and see will it boot my old HA instance. I'll order a USB to serial adapter too.

@cafebeef
Copy link

This seems like an old post, but I tried it with Rock 4se and the latest 13.2.

The problem of stripes appearing on the HDMI display is the same.
However, if I left it as it was, a login prompt appeared on the serial console.
The Home Assistant CLI also appeared on the HDMI display.

I tried it without connecting a LAN cable, but it seems that the NTP time synchronization timeout at startup takes a long time.

I've attached the serial console log.
I hope this helps someone.

serial_output.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants