Wandboard Dual/DVI Monitor: 1920x1080 possible?

1,544 views
Skip to first unread message
Assigned to wand...@gmail.com by mailf...@gmail.com

Peter Bolch

unread,
Jul 28, 2013, 8:11:14 AM7/28/13
to wand...@googlegroups.com
Is there a chance to get 1920x1080 with a DVI monitor and a WB Dual or just something like 1280x720 maximum (as with the Quad)?

Regards


Peter

ARM Fan

unread,
Jul 30, 2013, 11:21:08 AM7/30/13
to wand...@googlegroups.com
Not an answer but a question: Where did you read that WB Quad over DVI does not support more than 1280x720? Over HDMI you get Full HD, too.

The DVI problem is only because of EDID information reading fails. If you set it normally it should work with Full HD. This at least is my stand of information.

Regards,
Christian

Peter Bolch

unread,
Jul 30, 2013, 1:23:17 PM7/30/13
to wand...@googlegroups.com

I did some tests with my WB quad, WB's Ubuntu 12.04 and three different computer monitors (HDMI->DVI cable) and two different LCD TV (full HD, HDMI->HDMI cable). Best resolution I got was 1280x720.


Regards,

Peter

Tony Prisk

unread,
Jul 31, 2013, 1:33:55 AM7/31/13
to wand...@googlegroups.com

I tested this on my Samsung 22" LED TV (HDMI->HDMI) and was able to get 1920x1080 without issue simply by changing the uboot parameters. This screen shows the resolution when it changes, so in uboot it was showing 1280x720 and when the linux console came up it was in 1920x1080. I was using the Linux SDK kernel, not one of the Ubuntu images - and not booting into X.

Regards
Tony Prisk

Maxim Podbereznyy

unread,
Jul 31, 2013, 2:11:50 AM7/31/13
to wand...@googlegroups.com
You have to specify the resolution manually in u-boot. By default it is set to 720p


2013/7/31 Tony Prisk <senti...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "Wandboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wandboard+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--

Luke Scharf

unread,
Jul 31, 2013, 1:27:28 PM7/31/13
to wand...@googlegroups.com
I'm new to the platform, though not to Linux or to PC bootloaders (or Sun4U).  My Google searches haven't turned up a straightfoward answer to where the U-Boot configuration is stored.

I've seen references to uEnv.txt and to "bootargs".  But I didn't get anything by sending a break over the serial console, or by poking around /boot or /etc.  I'm clearly missing something that's common knowledge among people on this list, but which may be less obvious 

Can anyone point me to what I'm missing?  Does U-Boot work more like LILO (where you write the boot area and never see it again) than like Grub (which reads ext[234] before loading the kernel)?

Thanks!
-Luke

Peter Bolch

unread,
Jul 31, 2013, 1:46:21 PM7/31/13
to wand...@googlegroups.com


Am Mittwoch, 31. Juli 2013 08:11:50 UTC+2 schrieb Maxim Podbereznyy:
You have to specify the resolution manually in u-boot. By default it is set to 720p


 
Maxim, thanks for your reply. I did change the settings manually in u-boot but did not get an resolution better than 1280x720.

Regards

Peter

Tony Prisk

unread,
Aug 1, 2013, 1:36:34 AM8/1/13
to wand...@googlegroups.com

If you boot with a serial debug cable attached (NULL modem cable) you will see a message from u-boot indicating to 'press a key to interrupt boot' or something similar. Hit a key :)

'printenv' will show you the current environment variables.
bootargs is the one that is passed to the linux kernel, which is what you want to change.

setenv bootargs '.......'  will change the bootargs variable. You should enclose it in single-quotes otherwise it will not store correctly.

You probably want something like:
setenv bootargs 'console=ttymxc0,115200 video=mxcfb0:dev=hdmi,1920x1080@60,if=RGB32 root=/dev/sda1 rootwait rw'

Regards
Tony Prisk

Luke Scharf

unread,
Aug 1, 2013, 4:03:42 PM8/1/13
to wand...@googlegroups.com
Thank you -- that's a big help!

I must have missed the message when I watched it boot via the serial console over the weekend.

-Luke


--

Jaime Andrés Quiroga Perdomo

unread,
Apr 2, 2015, 11:44:54 AM4/2/15
to wand...@googlegroups.com, lukes...@clusterbee.net
Hi!, i have a similar problem. On my wandboard Quad, the default resolution is 1920x1080, but the screen is designed to support 1024x768. I tried with:

=>setenv bootargs 'console=ttymxc0,115200 video=mxcfb0:dev=hdmi,1920x1080@60,if=RGB32 root=/dev/sda1 rootwait rw'
=>reset

but im  getting the same 1920x1080 resolution.

How can i modify the resolution and make it permanent to 1024x768?

Thanks in advance.

Jaime Andrés Quiroga Perdomo

unread,
Apr 2, 2015, 11:54:50 AM4/2/15
to wand...@googlegroups.com, lukes...@clusterbee.net
ok, i did:

setenv bootargs 'console=ttymxc0,115200 video=mxcfb0:dev=hdmi,1024x768@60,if=RGB32 root=/dev/sda1 rootwait rw'
boot

and now i have the wanted resolution.

Looking if it is permanent.

Jaime Andrés Quiroga Perdomo

unread,
Apr 2, 2015, 12:03:35 PM4/2/15
to wand...@googlegroups.com, lukes...@clusterbee.net
Well, this is not permanent. How can i do it permanent to ever see the 1024x768 resolution?

 Thanks.

Jorge Rodriguez

unread,
Apr 2, 2015, 3:47:12 PM4/2/15
to wand...@googlegroups.com
Hello,
take a look to fbset documentation. Then write a proper configuration to /etc/fb.modes
For loading that configuration on startup, add a command at the end of /etc/profile:

fbset <your configuration>

Regards,
Jorge Rdz

--
You received this message because you are subscribed to the Google Groups "Wandboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wandboard+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jaime Andrés Quiroga Perdomo

unread,
Apr 2, 2015, 5:54:45 PM4/2/15
to wand...@googlegroups.com
Hi Jorge, thanks for reply. I will try it and submit the results. ;)

Jaime Andrés Quiroga Perdomo

unread,
Apr 3, 2015, 4:42:18 PM4/3/15
to wand...@googlegroups.com

Hello Jorge, i have made:

fbset -xres 1024 -yres 768

Added it to the end of /etc/profile

Reboot, but then, the display shows: "DVI out of range"

I have connected the serial debug cable to restore the file, and now, i have the 1920x1080 resolution again.

What to do next?

Thanks in advance.

Robert Nelson

unread,
Apr 3, 2015, 4:58:28 PM4/3/15
to wand...@googlegroups.com
On Fri, Apr 3, 2015 at 3:42 PM, Jaime Andrés Quiroga Perdomo
<gtro...@gmail.com> wrote:
>
> Hello Jorge, i have made:
>
> fbset -xres 1024 -yres 768
>
> Added it to the end of /etc/profile
>
> Reboot, but then, the display shows: "DVI out of range"
>
> I have connected the serial debug cable to restore the file, and now, i have
> the 1920x1080 resolution again.

Use xrandr...

Regards,

--
Robert Nelson
https://rcn-ee.com/

Jaime Andrés Quiroga Perdomo

unread,
Apr 4, 2015, 12:39:41 PM4/4/15
to wand...@googlegroups.com
Hi!, i found a temporally solution for set the resolution to 1024x768 on DVI monitor by modify the xorg.conf file, adding a modesetting and a subsection, attached my xorg.conf file for Wandboard Quad C1, using a DVI monitor from Hope Industrial Systems, and the official Ubuntu 12.04.3 Image from Wandboard.org.

Now i still trying to make the Ubuntu 14.04 LTS image to work. I cant view anything than the console.

on xrandr i get: can't open display
on xrandr -d :0 : can't  open display

I can see the resolution is fine because the uEnv.txt file. But im always on console. I also run:

sudo apt-get update
sudo apt-get install read-edid xserver-xorg-video-modesetting x11-xserver-utils

all install successful. Then reboot, and view the login console. So, i did:

sudo apt-get install lxde-core

Near the lxde-core install, i can see a console message:

...
(gconftool-2:4452): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
...

Then reboot and, a blinking cursor is shown. However i can acces console form Ctrl+Alt+F1

After login in on console, i did: startlxde

Output: Gtk-Warning ***: Cannot open display:
ubuntu@arm:~$ _




xorg.conf

Jorge Rodriguez

unread,
Apr 4, 2015, 1:42:25 PM4/4/15
to wand...@googlegroups.com
You can try:
fbset -g 1024 768 1024 768 32

Let me know how it works.

Regards,
Jorge.

On Sat, Apr 4, 2015 at 10:39 AM, Jaime Andrés Quiroga Perdomo <gtro...@gmail.com> wrote:
Hi!, i found a temporally solution for set the resolution to 1024x768 on DVI monitor by modify the xorg.conf file, adding a modesetting and a subsection, attached my xorg.conf file for Wandboard Quad C1, using a DVI monitor from Hope Industrial Systems, and the official Ubuntu 12.04.3 Image from Wandboard.org.

Now i still trying to make the Ubuntu 14.04 LTS image to work. I cant view anything than the console.

on xrandr i get: can't open display
on xrandr -d :0 : can't  open display

I can see the resolution is fine because the uEnv.txt file. But im always on console. I also run:

sudo apt-get update
sudo apt-get install read-edid xserver-xorg-video-modesetting x11-xserver-utils

all install successful. Then reboot, and view the login console. So, i did:

sudo apt-get install lxde-core

Near the lxde-core install, i can see a console message:

...
(gconftool-2:4452): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
...

Then reboot and, again on console.


Jaime Andrés Quiroga Perdomo

unread,
Apr 4, 2015, 1:58:28 PM4/4/15
to wand...@googlegroups.com
Good day Jorge,

i did: fbset -g 1024 768 1024 768 32 on the gtkwarning image, and get:

ioctl FBIOPUT_VSCREENINFO: Invalid argument

Then, i changed the uSD for the ubuntu 12.04.3 image and did the same, but this time, the screen is split in 2, with the bottom half filled with black

i rebooted to get normal screen again

Jorge Rodriguez

unread,
Apr 4, 2015, 2:07:30 PM4/4/15
to wand...@googlegroups.com
Hi,
just being curious, what happens if you try:
fbset -g 1024 1536 1024 1536 32
?

Regards,
Jorge.

On Sat, Apr 4, 2015 at 11:58 AM, Jaime Andrés Quiroga Perdomo <gtro...@gmail.com> wrote:
Good day Jorge,

i did: fbset -g 1024 768 1024 768 32 on the gtkwarning image, and get:

ioctl FBIOPUT_VSCREENINFO: Invalid argument

Then, i changed the uSD for the ubuntu 12.04.3 image and did the same, but this time, the screen is split in 2, with the bottom half filled with black

--

Jaime Andrés Quiroga Perdomo

unread,
Apr 4, 2015, 2:10:46 PM4/4/15
to wand...@googlegroups.com
LOL, ok i will try it:

input: fbset -g 1024 1536 1024 1536 32

out: black screen, DVI out of range

Jorge Rodriguez

unread,
Apr 4, 2015, 2:21:39 PM4/4/15
to wand...@googlegroups.com
Hi,
Since I don't have additional information about your monitor (and since xrand is not working on your system), you can try adding the next configurations to /etc/fb.modes   and then try all of the configurations. e.g. # fbset 1024x768-43-lace

mode "1024x768-43-lace"
    # D: 44.90 MHz, H: 35.522 kHz, V: 86.96 Hz
    geometry 1024 768 1024 768 8
    timings 22272 56 8 40 1 176 8
    laced true
    hsync high
    vsync high
endmode

mode "1024x768-60"
    # D: 65.00 MHz, H: 48.363 kHz, V: 60.00 Hz
    geometry 1024 768 1024 768 8
    timings 15385 160 24 29 3 136 6
endmode

mode "1024x768-70"
    # D: 75.00 MHz, H: 56.476 kHz, V: 70.07 Hz
    geometry 1024 768 1024 768 8
    timings 13334 144 24 29 3 136 6
endmode

mode "1024x768-72"
    # D: 75.00 MHz, H: 58.230 kHz, V: 72.245 Hz
    geometry 10224 768 10224 768 8
    timings 13334 104 24 29 3 136 6
endmode

mode "1024x768-75"
    # D: 78.75 MHz, H: 60.023 kHz, V: 75.03 Hz
    geometry 1024 768 1024 768 8
    timings 12699 176 16 28 1 96 3
    hsync high
    vsync high
endmode

mode "1024x768-90"
    # D: 100.0 MHz, H: 76.220 kHz, V: 90.20 Hz
    geometry 1024 768 1024 768 8
    timings 10000 192 0 41 21 96 15
endmode

--

Jaime Andrés Quiroga Perdomo

unread,
Apr 4, 2015, 2:58:01 PM4/4/15
to wand...@googlegroups.com
Gets random blink on every configuration. I will keep the actual configuration on xorg meanwhile.

xrandr output is: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
1024 x 768 60.0*

But i think this output is caused by the modifications on the xorg.conf file.

That i want is, keep the uBoot environment configuration persistent at boot. Imean, i want the:


setenv bootargs 'console=ttymxc0,115200 video=mxcfb0:dev=hdmi,1024x768@60,if=RGB32 root=/dev/sda1 rootwait rw'

Permanent, as in the uEnv.txt file for the Robert Nelson kernel. I also tried his method, but the ubuntu image, simply does not recognize my monitor. The Debian image works well, but i want the Ubuntu 14.04 image.

Why i want it permanent?

Because, when switchin to the terminal by Ctrl+Alt+F1, the resolution is back to 1920x1080. So, the text is almost indistinguishable (strange word, google traductor :P). So, doing it permanent with avoid this issue.

For now, i'm using the ubuntu 12.04.3 image, with the modified xorg.conf file shown above which configures my monitor with 1024x768 by a modeline. But my dream, is to get the Ubuntu 14.04 image working with its GUI and the FTDI support (which is functional already).

Why Ubuntu 14.04.x?

Because, this image has become a challenge, and i will not sleep quiet, until that work. In addition, many people is looking for the same, and is a good idea have the latest LTS release runing on an embedded  system which will be used for the industry. Thanks a lot for your help, and i will persevere, this can't defeat us!!! XD. Regards.

Thanks a lot.
Reply all
Reply to author
Forward
0 new messages