2015-12-13, 02:51
(2015-12-12, 21:07)Diodato Wrote: Darn, thought that the recent USB3-related fixes in SeaBIOS would allow me to use during boot my cheap wireless keyboard instead of grabbing that old wired keyboard but no.
Otherwise would not bothered updating the BIOS. But I did and now I see that the changes in the video BIOS part
made things a lot worse in my setup. At least with my pretty old TV.
Now when selecting the boot device I can see only the second line of the text. The first line where it says the current version of the BIOS is trimmed and no setting of the TV image size can bring it back. Also the leftmost two characters are cropped.
But that's not all.... now after each reboot of my chromebox the TV ends up in the overscan mode (16:9) and not "Just Scan" (1:1 pixel size name for Samsung TVs). Need to manually change it each time to fullscreen no overscan mode. Am angry at myself to have updated the BIOS...
So a question to @Matt: how can I flash back a previous version of BIOS? A version prior the changes made in the video part?
I'm not sure how those issues would be video BIOS related, because it's not doing anything other than setting a single video mode on startup. Whether your TV overscans or not, or how it sets the video mode, should not be related to what the video BIOS is doing when initialized at boot. I can create a test firmware for you though which reverts only the video BIOS, so we can determine if it fact it is the issue. PM me for the script link.
(2015-12-12, 23:46)giant25 Wrote: I'm having a problem with "No signal" on the HDMI port connected to my dual-boot Chromebox after a reboot. I have a new Samsung UN65JU6500 4k TV and have read through this forum. I've tried creating an autostart.sh in /storage/.config, which looks like this:
Any idea on what could be going on? Please let me know if there's any other info I can provide that might help. I've also tried putting HDMI1 in PC and UHD color as suggested earlier in this thread. I'm on the latest Firmware on my Samsung TV. Thanks.
is this a box you just set up, or was it previously working and how doesn't due to an update?
