You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just updated to the latest MrChromebox firmware (MrChromebox-2408.1) for my Chromebook and and realized through trial that the device won’t boot without the internal display connected. Prior to this I was on firmware version 4.20.1 and could boot with just the HDMI connected to a monitor (not sure about headless booting). This would also show the Bios screen.
Now it just powers up (shown by the led indicator) if the internal display isn’t connect, but there is no indication of anything else happening. Pressing the power button once even after 5 minutes turns off the led. HDMI shows no indication of receiving a signal through all this period.
If I power down and attach the internal display, everything works. HDMI output operates like it did with the screen attached before, only after the bios screen.
The text was updated successfully, but these errors were encountered:
hmm, I'm not sure why that would be, I'd have to look at the display init type used for Winky. Nothing has changed on Baytrail devices for some time so I'm surprised to see this regression
Just updated to the latest MrChromebox firmware (MrChromebox-2408.1) for my Chromebook and and realized through trial that the device won’t boot without the internal display connected. Prior to this I was on firmware version 4.20.1 and could boot with just the HDMI connected to a monitor (not sure about headless booting). This would also show the Bios screen.
Now it just powers up (shown by the led indicator) if the internal display isn’t connect, but there is no indication of anything else happening. Pressing the power button once even after 5 minutes turns off the led. HDMI shows no indication of receiving a signal through all this period.
If I power down and attach the internal display, everything works. HDMI output operates like it did with the screen attached before, only after the bios screen.
The text was updated successfully, but these errors were encountered: