View source for Beagleboard talk:BeagleBoneBlack HDMI

From eLinux.org
Jump to: navigation, search

Contents

Thread titleRepliesLast modified
How to force a resolution100:53, 26 June 2018
Resolution information100:50, 26 June 2018

How to force a resolution

I followed the instructions on this page but noticed that it didn't really mention how to make the changes permanent.

This works for my Samsung LED Monitor S24D300HL.

root@beaglebone:~# tail -n6 /etc/gdm/Init/Default
# Use xrandr!
export XAUTHORITY=`ls /var/run/gdm/auth-for-root-*/database`
export DISPLAY=:0
xrandr --output HDMI-0 --mode 1680x1050

exit 0
12:25, 28 January 2016

Append video=1680x1050 to the kernel parameters (the cmdline variable in /boot/uEnv.txt)

00:53, 26 June 2018
 

Resolution information

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

 

Return to Thread:Beagleboard talk:BeagleBoneBlack HDMI/Resolution information.

These issues no longer exist in recent kernels. With kernel 4.14.51-bone16, all modes I've tried (1920x1080@30, 1324x768@60, 1280x1024@60, 1152x864@75, 1024x768@60, 800x600@60, 720x480@60) worked and included audio.

If no display is connected at boot, the creation of the legacy fbdev (/dev/fb0) seems to be deferred until a display is connected. The ALSA output exists regardless, and I can send audio to the output, which is silently discarded. Once I connect my tv, the kernel automatically performs mode selection, creates the legacy fbdev, and starts sending video *and* audio to my tv. The transition appears to be invisible to the ALSA application.

00:50, 26 June 2018