TheSHAD0W Posted July 4 Posted July 4 (edited) Armbian 24.5.1. I don't have a serial console setup so I can't tell if it's actually starting to boot or not, but it never gets to the point where a video signal is sent to HDMI. It *does* send a CEC on signal to the TV, which does turn on, and power-cycling the Pi then begins a normal boot process. Pi also boots normally headless. Problem noted on one Insignia model and on a Vizio TV, works as expected on another Insignia model, on a Hisense and on an LG. Issue began after updating the kernel from legacy. Edited July 4 by TheSHAD0W 0 Quote
Werner Posted July 4 Posted July 4 You seem to be the first person reporting such an issue and none of us has a second sight. Therefore without logs there is pretty much nothing we can do. 0 Quote
TheSHAD0W Posted July 4 Author Posted July 4 (edited) https://pastebin.com/2WpTQy3G last 500 lines of syslog. I'll try to get a debug console working but it may be a while... Note that last boot was actually two boot attempts, one with the TV off, and it doesn't look like it sent anything to syslog. Edited July 4 by TheSHAD0W 0 Quote
TheSHAD0W Posted July 6 Author Posted July 6 (edited) Okay, found another klew to this issue... Apparently the pi is outputting video at a default 4K spec, and most of the TVs I'm using aren't accepting it, but one is.... Multiple lines of: Quote begin: Running /scripts/local-block ... done. Then: Quote done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/nncblk0p1 does not exist. Dropping to a shell! I would have played with the shell, but the machine is way up on a wall, and I had to transcribe the above from a photo of the screen. ^^; Edit: And yes, I triple-checked the issue only pops up when the attached TV is turned off. Edited July 6 by TheSHAD0W 0 Quote
TheSHAD0W Posted July 17 Author Posted July 17 Allow me take this opportunity to thank Rockchip for choosing a default communications rate that so many TTL serial adapters can't reach. New adapter on order that can do 1.5 megabit. Like 1 megabit isn't fast enough. Or even 115,200, for a text terminal. 0 Quote
TheSHAD0W Posted July 25 Author Posted July 25 (edited) Okay, after beating on things I now have log captures from debug console for both successful and unsuccessful boot. tvonoff.zip Edit: Most recent release kernel does not fix the issue. Edit 2: LOL why do these files show up as corrupt (or Chinese) in a gui text editor? Edited July 25 by TheSHAD0W 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.