Not sure how to get EDID info via windows, but meanwhile my monitor is:VA2431wm, 1920 x 1080.
Red (and blue) LEDs come on solid at boot, green comes on at about 30 seconds, at which point the blue LED changes to flashing.
And I have a question: why doesn’t the server image at least (but really of of them) boot up first time with SSH enabled with root login, and the ethernet set to DHCP? Nobody who can’t figure out how to reconfigure those is likely to be a serious part of your customer base, and I don’t think we need to accommodate those who would boot this board for the in an environment where it would be exposed to the internet!
For the server image in particular, there are lots and lots of uses where it’s expected to be headless so why trouble us with the need to hook up a monitor?
DVI displays are not designed to interface with HDMI ports so they do not use the normal HDMI timings. u-boot is a low complexity bootloader and is not capable of doing advanced timing configuration like Linux. Use an HDMI display.
All of our images offer the stock behavior of upstream distros. Ubuntu configures the server images this way. You are barking up the wrong tree. They set the server images to be configured via cloud-init and you can enable SSH and other features you mentioned per the release notes.
Having SSH enabled and root login is a security risk. No reasonable distro will do this.
Read the release notes. You are asking for something that already exists.
I went out and bought a new Acer SB220Q bi genuine HDMI (1920 x 1080) and still nothing when booting.
Two questions:
*Am I supposed to see anything from the on-board boot loader, or is it completely silent until it gets some of the system loaded from the drive?
*Is someone maintaining a list of known-to-work monitors? (Don’t worry, I needed the new Acer for another system anyway, but obviously I’m not going to spring for Yet Another Monitor unless it’s promised to be compatible.)
Initial startup is controlled by u-boot, not Linux. GRUB is shown via u-boot. The code for u-boot is low complexity so it does not have all of the advanced features of Linux.
Using the AML-S905X-CC-V2 Sweet Potato board. I am using my own OS image based on the debian one you provide. The screen is a 7" MPI7002 1024x600 touchscreen. Using a 32GB emmc for storage.
Problem:
Some (5% to 10%) of the boards have no video output. Ruled out the possibility that the screen doesn’t work. The screen works after I switch the screen to an identical board with the same image.
Check the HDMI cable and make sure the cable is properly seated. The factory test for every unit include signal, bandwidth, and noise tests. No unit is packaged without passing these tests and any defect over 0.2% (2 out of 1000) would be considered high. 5% is almost impossible.
Where are you sourcing?
Have you verified that all software and firmware are equivalent?
Flashing consecutively does not equate to running the same software. It’s best to test with the same SD card or eMMC or flash drive.
This is likely an issue with 2) since the display is triggered by HPD (Hot Plug Detect). Does xrandr find the display on working units? Does the EDID read work when the display is not working?