lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
Zenking has joined #armbian-rockchip
<Zenking> Hi, all!I have OrangePi 5b with Rockchip RK3588S. I can flash Armbian_24.2.1_Orangepi5_bookworm_legacy_5.10.160.img to eMMC and it's ok but I want to try Armbian_24.5.0-trunk.175_Orangepi5_trixie_edge_6.8.0-rc7_minimal.img. There is only red LED and nothing by hdmi at all. I'm slashing by dd while boot from SD-card
<DC-IRC> [Discord] <igorpec> there https://forum.armbian.com/forum/206-orange-pi-5-5b-5-plus/ you have some topics on the issue
<DC-IRC> [Discord] <igorpec> if you are end user, stick to 5.10y.
<DC-IRC> [Discord] <efectn> You need to change devicetree from Armbian env
<Zenking> I'm starting to think so too. Now I need to disable random mac but I think I can manage it by myself. Thanks!
<Zenking> efectn, I did
<DC-IRC> [Discord] <narga_64> Anyone else having problems with 6.1 vendor kernel? `Waiting for system to finish booting...`
<DC-IRC> [Discord] <narga_64> `dmesg` says in its last line:
<DC-IRC> [Discord] <narga_64> `platform mtd_vendor_storage: deferred probe pending`
<DC-IRC> [Discord] <narga_64> Board: Friendlyelec CM3588 NAS, system on eMMC
<DC-IRC> [Discord] <spooky8086> I'd upload the full boot log to pastebin
<DC-IRC> [Discord] <narga_64> <https://paste.armbian.com/abadefilad.yaml>
<DC-IRC> [Discord] <narga_64> ^ Bootlog captured by uart and then dmesg log
<DC-IRC> [Discord] <spooky8086> What is the problem exactly? Is the system not booting?
<DC-IRC> [Discord] <narga_64> It is booting sort of, but doesn't finish the boot process. If I SSH into it, the line `Waiting for system to finish booting...` comes up. You can access the system by doing a `ctrl+c` though.
Zenking has quit [Quit: Leaving]
<DC-IRC> [Discord] <narga_64> Okay it seems like I was not patient enough. System booted after waiting for almost two minutes. This still seems strange since I flashed a fresh legacy image for debugging and did not have to wait this long for it to boot.
<DC-IRC> [Discord] <narga_64> After going through the initial setup and rebooting, I didn't have to wait long.
<DC-IRC> [Discord] <narga_64> Seems like only the boot before finishing the initial setup is affected. If I wait for it to boot, then **not** finish the initial setup but straight reboot by hardware reset, the next boot will also take long.
<DC-IRC> [Discord] <rpardini> @narga_64 that's `systemctl status` hanging. Check which unit it is
<DC-IRC> [Discord] <narga_64> Nice! When I do `systemctl --type=service` right after boot, there are two services which are `inactive, sub=dead, job=start` (none are `failing`). All others seem to be running.
<DC-IRC> [Discord] <narga_64> These two dead services are
<DC-IRC> [Discord] <narga_64> 1) `serial-getty@ttyS2.service`
<DC-IRC> [Discord] <narga_64> 2) `systemd-update-utmp-runlevel.service`
<DC-IRC> [Discord] <narga_64> Status for 1) says "Dependency failed for serial-getty@ttyS2.service - Serial Getty on ttyS2"
<DC-IRC> [Discord] <narga_64> 2) does not have any status warnings or infos
<DC-IRC> [Discord] <narga_64> Yeah I think it's `serial-getty@ttyS2`. When I try to `systemctl start` this service, it also hangs and fails after like 1:30 minutes 👍
motiejus has quit [Remote host closed the connection]
motiejus has joined #armbian-rockchip