Display limited to 800x600 [SOLVED]
#11
Giving up for now.  I read a post on here for the A64 that says if the modes have never been implemented then you can't access them.  A Raspberry Pi has 87 HDMI modes but I remember when the last one, CVT, was implemented.  It took an engineer with inside knowledge and it was done I think because there was an endless stream of requests for new modes.  Once CVT goes in, people can make their own new modes.

But my /sys/class/graphics/fb0/modes file has only U:1920x1080p-0 in it.  Oh well, there's always VNC.
 
I can get a 1024x768 mode (only in X Windows) when I set one with lxrandr, but when the screen blanks from lack of activity it comes back up at 1920x1080.  Apt-get just upgraded the kernel too, to:

Linux rock64 4.4.126-rockchip-ayufan-239 #1 SMP Sun May 27 18:38:24 UTC 2018 aarch64 GNU/Linux
  Reply
#12
Get on IRC and go to the #Rock64 room, fast answers there at least. Ayufan shows as being in there at the moment.
  Reply
#13
OK, I got 1024x768, I'm unstuck.

Check the files in /lib/firmware/edid, I had to copy a set from Armbian.
Edit /boot/efi/extlinux and add your mode to the append line like:

drm_kms_helper.edid_firmware=edid/1024x768.bin video-HDMI-A-1:1024X768

Then update initramfs with update-initramfs -u and reboot.

You should have an edid file to match the video mode you want, and even then not all modes work.

Thanks to mth on #Rock64. If you don't want to get on IRC you can search the logs at http://irc.pine64.uk/

Check dmesg | grep edid if you're having problems..
  Reply
#14
Photo 
For completeness, this is from docs-master/Develop reference documents/DISPLAY/rockchip_drm_integration_helper-zh.pdf page 26


   
  Reply
#15
(07-09-2018, 10:51 AM)ab1jx Wrote:
  1. Restart the Rock 64
  2. mount the partition of the SD card where you can find the right files, for us it was sda6, corresponding to the mmcblk0p6 partition.
  3. Replace all the files of /boot/efi of the Rock64 by the corresponding files found on the SD card :
  • extlinux/extlinux.conf
  • dtb
  • image
  • initrd.img
After a restart, the display is OK

(07-09-2018, 05:57 PM)ab1jx Wrote: Seems a bit sledgehammerish (doesn't that replace the kernel too?) but maybe it will get Ayufan's attention to the fact there's a problem.  My guess is this only happens with monitors 5 years or so old and more because the EDID is a different version.  The USB keyboard thing still needs the manual printk fix too.

sledgehammerish, OK, but it worked. Replacing only the extlinux.conf file did not work. Replacing the dtb file did not work. replacing initrd.img file alone breaks the system. The problem was in the 0.5 kernel, and the question was if was possible to replace by the 0.6 kernel without breaking everything. I expected it would, but this didn't and the system is still running well.
  Reply
#16
(07-28-2018, 04:53 AM)Averell Wrote: sledgehammerish, OK, but it worked. Replacing only the extlinux.conf file did not work. Replacing the dtb file did not work. replacing initrd.img file alone breaks the system. The problem was in the 0.5 kernel, and the question was if was possible to replace by the 0.6 kernel without breaking everything. I expected it would, but this didn't and the system is still running well.

When you replace the kernel (or initrd.img) you might have to do "update-initramfs -u", I'm not sure how that works. I didn't backtrack on anything, just picked a mode with drm_kms_helper. Did it before I found the PDF on how to do it, I think I got it from somebody on IRC.
  Reply
#17
(07-28-2018, 05:45 AM)ab1jx Wrote:
(07-28-2018, 04:53 AM)Averell Wrote: sledgehammerish, OK, but it worked. Replacing only the extlinux.conf file did not work. Replacing the dtb file did not work. replacing initrd.img file alone breaks the system. The problem was in the 0.5 kernel, and the question was if was possible to replace by the 0.6 kernel without breaking everything. I expected it would, but this didn't and the system is still running well.

When you replace the kernel (or initrd.img) you might have to do "update-initramfs -u", I'm not sure how that works.  I didn't backtrack on anything, just picked a mode with drm_kms_helper.  Did it before I found the PDF on how to do it, I think I got it from somebody on IRC.

I just did it again a year or so later.  I grabbed an EDID file using tvservice on a Raspberry Pi and put it in /lib/firmware/edid.  I didn't do the update-initramfs.  This time I wanted to get 1920x1080 which the Pi defaulted to anyway.  I'm not sure if it matters but I did this using the monitor I wanted to use, which worked on the Pi but not the Rock64 (until I made the EDID file).  I did have to power it off and back on, not just type reboot, before it worked.

So I have /lib/firmware/edid/piedid2.bin and in /boot/extlinux/extlnux.conf I have  drm_kms_helper.edid_firmware=edid/piedid2.bin  I did have to make the edid directory in /lib/firmware.
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
Question [SOLVED] Alpine Linux won't boot rock7 1 841 10-22-2019, 04:30 PM
Last Post: rock7
  [solved] Unable to start X Osiander 8 3,736 10-03-2018, 03:54 AM
Last Post: jovval
  If you've messed up your eMMC Card - Solved gregb49 11 3,333 07-11-2018, 02:08 PM
Last Post: gregb49
  Any reason why ntp time is 6 minutes slow (Solved) Rocklobster 1 436 05-29-2018, 05:27 AM
Last Post: Rocklobster
  [Solved] Open VPN +Wi-Fi hotspot - Debian S3phi40T 1 810 05-01-2018, 05:51 AM
Last Post: S3phi40T
  [PROBLEM SOLVED] Distcc Help cooker 2 890 05-01-2018, 05:35 AM
Last Post: cooker
  Im having weird crashes on a new rock64 [solved] Trash_Can_Man 4 1,975 02-06-2018, 04:06 AM
Last Post: a1w.ca
Lightbulb MPP+DRM: low level API for video codecs and display (also 4k UHD+HDR+HLG) mcerveny 0 1,127 01-27-2018, 11:23 AM
Last Post: mcerveny
Information Solved - Resize Root Filesystem (Xenial) aussiemate 4 2,649 08-29-2017, 03:43 PM
Last Post: fbms

Forum Jump:


Users browsing this thread: 1 Guest(s)