While trying to use smartctl and fsck, on eMMC, SDcard, & nvme, I only received errors stating that the device is in use, but I’ll try again after unmounting the devices.
I also noticed that my eMMC file system is Type 88 Linux. While trying to verify if this is correct, I have only found 2 posts which only mention SD formats, ext4 & Type 83 Linux.
What is the correct file format for the eMMC?
UPDATE: Gparted indicated that mmcblk1p1-p6 had errors due to no file format. So, I formatted them to ext4. That bricked the EDGE-V. So, I uploaded the image again. But, that only returned me to exactly the same problem.
Gparted indicates again that mmcblk1p1-6 have unknown file systems. p7 (rootfs) is ext4, as before.
Thanks
Why not just do a clean wipe and install everything again? The official image does not appear to have any issues with the emmc file system. If you’re having an issue with the HDMI, maybe the SoC is borked? (we don’t encounter fuzzy green squares on a regular basis) 
Yes. I did ‘Erase Flash’ in the AndroidTool before ‘Upgrade Firmware’.
I’m inclined to agree that the problem is hardware.
What’s the next step?
@TheHermit we can arrange a product exchange. At the same time, @kenny wants to verify one thing before that.
- Take a photograph of your Edge-V with the HDMI, USB-C, and other cables plugged in when you encountered the green squares.
There is a known issue whereby if the HDMI and other cables are pressed against each other tightly, because the cable-heads are too large, users would then encounter HDMI graphical issues, artefacts such as loss of colour, green haze, etc. As you know, the Edge-V boards are very small, and the ports closely spaced together - so we’ve had some people experience this issue in the past.
Okay no other fat cables pushing against the HDMI? Did you attempt to use a different HDMI cable?
If all of the above is true / tried out, then its quite certain to be an issue with the onboard GPU, or some other sub-system related to the HDMI output.
1 Like
Yes I tried a 4k HDMI, too
This is what I’m seeing after it returns from power saver.
This is what happens during shutdown from either eMMC or SDcard. Notice the bottom half is okay, once lightdm has unloaded.
That’s odd. So the HDMI issue is intermittent?
Actually, it is very predictable. But, ~50% of the time, it will only be green instead of the multiple colored squares during startup, probably depending upon whether it is warmed up.
After ~15 minutes, the power saver blanks the screen, so I can move the mouse and everything looks and behaves normally.
That’s very odd. Just out of curiosity, do you have another screen lying around?
Only a 7" Raspberry Pi Touchscreen. I’m on it, but I need to untie cables and restart the EDGE-V. Could be a while, if I have to wait for the power saver. We’ll see.
Well no harm giving that a try too. Because if it is a hardware issue, the issue would (most of the time) be persistent.
Powered on fine. I’m at login. But, that won’t work for me. The touchscreen is for a Raspberry Pi project.
And the RPi screen is connected via MIPI-DSI and TP, and not over HDMI?
No. It’s connected to the same HDMI. BTW, the other monitor is a 50" Toshiba FireTV. I’ve use several other SBCs on it, including ROCK Pi 4, RPi 3B+, and RPi 4B+
Ok, the issue is unlikely with the Edge-V’s GPU. Could you play around with it in the “Rpi screen mode” for a while longer, and see if the fuzzy green squares appear again?
It’s not that we wouldn’t want to exchange your board, its just that you know the 2-way shipping will take a very long time, and be inconvenient for you.
Yeah, but I’ve already waited 3 weeks, just to get to this point. I’ve spent several hundred $ on the ROCK Pi POS. I really need to have the EDGE-V fully functional. Don’t mean to be difficult. But, I’m in no hurry.
Okay I understand. What is the resolution of the Rpi screen? The 50" Toshiba is 4K right?
Ithink it is 1080 x 720, if I remember corectly. Yes, the Toshiba is 4K. I purchased it specifically for the EDGE-V.
Okay play around with both the 4K and 720P displays for a bit, going from one to the other, and see if the issue recurs. I’ll ask @kenny for his feedback when he is available.