On 01/05/18 04:07 PM, Thierry Moreau wrote:
Dear happy few Crux fans,
As hinted in a previous post, I installed the generic Crux ARM 64 bits root fs image (RC2) on a MicroSD partition having booted the ArchLinux O/S image (as a shortcut for u-boot installation).
It is now working except for a strange behavior for the agetty (or any other process) output to /dev/tty1 USUALLY does not show up on the hdmi display, but SOMETIMES works fine. It worked on two occasions, but I am unable to identify a causal pattern (at first a cable handling sequence seemed at stake). I have ssh access to the system for troubleshooting.
This has been diagnosed and a workaround has been implemented. Basically a screen-blank-screen-unblank cycle has to be done early in the boot sequence to turn on the console screen. A more elegant fix would be in the kernel customization for Odroid C2 / Amlogic meson gxbb SOC. The diagnostic: the above "SOMETIMES works fine" was the screen blank 15 minutes timer followed by a keyboard event. Thus, what remains is 1) some documentation of how I did the installation, and 2) X11 stuff. The latter requires closed source libraries for the Mali 450 / utgard GPU. - Thierry
The HDMI connection is working coherently in the following sense: the EDID information is indeed reflected in
/sys/devices/virtual/amhdmitx/amhdmitx0/edid
and when I change the HDMI parameters, the display (a 7 in. camera monitor sold in the professional video market) indeed reports the change in a temporary pop-up tile (in the otherwise blank screen).
I.e. the HDMI parameter change is effected by
echo -n 480i60hz >/sys/devices/virtual/amhdmitx/amhdmitx0/disp_mode
and then
echo -n 480p60hz >/sys/devices/virtual/amhdmitx/amhdmitx0/disp_mode
(change from 480i to 480p).
I will refer to the Hardkernel/Odroid community forum for help and I will keep the Crux arm list informed.
Regards,
- Thierry Moreau _______________________________________________ crux-arm mailing list crux-arm@crux-arm.nu https://crux-arm.nu/mailman/listinfo/crux-arm