DVI Woes

Adam_Yergovich · October 20, 2008, 7:16pm

Hello,

So i recently got a samsung 331 hi def monitor with dvi connector just for the beagleboard. Much to my dismay, when plugged in it only displayed "mode not supported", which is listed in the manual as "Check the maximum resolution and connected device's Video frequency". I suspect that it is the frequency that is causing the problem, however i'm not sure what to do about it.

On the advice of some folks in chat i looked into updating xloader and uboot to the ones with the Angstrom demo, but i seemed to end up with the same problem(x-loader 1.4.2).

I suspect that it is an issue with the frequency, but am not really sure. More over if i got a different screen what frequency am i looking for?

Anyone have any advice for getting it to work?

-Adam

mansr · October 20, 2008, 7:28pm

Adam Yergovich <ayergo@jkmicro.com> writes:

Hello,

So i recently got a samsung 331 hi def monitor with dvi connector just
for the beagleboard. Much to my dismay, when plugged in it only
displayed "mode not supported", which is listed in the manual as "Check
the maximum resolution and connected device's Video frequency". I
suspect that it is the frequency that is causing the problem, however
i'm not sure what to do about it.

On the advice of some folks in chat i looked into updating xloader and
uboot to the ones with the Angstrom demo, but i seemed to end up with
the same problem(x-loader 1.4.2).

I suspect that it is an issue with the frequency, but am not really
sure. More over if i got a different screen what frequency am i looking
for?

Anyone have any advice for getting it to work?

You need to replace the pre-flashed u-boot with e.g. the one from
OpenEmbedded/Angstrom and also use the OE omapfb patches. You can see
what timings are being used by dmesg | grep omapfb.

Adam_Yergovich · October 20, 2008, 7:45pm

Måns Rullgård wrote:

Adam Yergovich <ayergo@jkmicro.com> writes:

Hello,

So i recently got a samsung 331 hi def monitor with dvi connector just for the beagleboard. Much to my dismay, when plugged in it only displayed "mode not supported", which is listed in the manual as "Check the maximum resolution and connected device's Video frequency". I suspect that it is the frequency that is causing the problem, however i'm not sure what to do about it.

On the advice of some folks in chat i looked into updating xloader and uboot to the ones with the Angstrom demo, but i seemed to end up with the same problem(x-loader 1.4.2).

I suspect that it is an issue with the frequency, but am not really sure. More over if i got a different screen what frequency am i looking for?

Anyone have any advice for getting it to work?

You need to replace the pre-flashed u-boot with e.g. the one from
OpenEmbedded/Angstrom and also use the OE omapfb patches. You can see
what timings are being used by dmesg | grep omapfb.

I've got the u-boot and x-loader from Angstrom here:

http://www.angstrom-distribution.org/demo/beagleboard/

and reflashed them.

Now how do i "use the OE omapfb patches" and where might they be found?

Thanks for the tip on dmesg, i do indeed now see what it is set to. Are there other configurations available? I've managed to get bit-bake working for the Angstrom image, but am unclear on how to change settings such as this.

-Adam

mansr · October 20, 2008, 8:49pm

Adam Yergovich <ayergo@jkmicro.com> writes:

Måns Rullgård wrote:

Adam Yergovich <ayergo@jkmicro.com> writes:

Hello,

So i recently got a samsung 331 hi def monitor with dvi connector just
for the beagleboard. Much to my dismay, when plugged in it only
displayed "mode not supported", which is listed in the manual as "Check
the maximum resolution and connected device's Video frequency". I
suspect that it is the frequency that is causing the problem, however
i'm not sure what to do about it.

Thanks for the tip on dmesg, i do indeed now see what it is set to. Are
there other configurations available? I've managed to get bit-bake
working for the Angstrom image, but am unclear on how to change settings
such as this.

What messages do you see?

Adam_Yergovich · October 20, 2008, 9:31pm

Måns Rullgård wrote:

Adam Yergovich <ayergo@jkmicro.com> writes:

Måns Rullgård wrote:

Adam Yergovich <ayergo@jkmicro.com> writes:

Hello,

So i recently got a samsung 331 hi def monitor with dvi connector just for the beagleboard. Much to my dismay, when plugged in it only displayed "mode not supported", which is listed in the manual as "Check the maximum resolution and connected device's Video frequency". I suspect that it is the frequency that is causing the problem, however i'm not sure what to do about it.

Thanks for the tip on dmesg, i do indeed now see what it is set to. Are there other configurations available? I've managed to get bit-bake working for the Angstrom image, but am unclear on how to change settings such as this.

What messages do you see?

I see:

root@beagleboard:/dev# dmesg | grep omapfb

omapfb: configured for panel omap3beagle

omapfb: DISPC version 3.0 initialized

omapfb: Framebuffer initialized. Total vram 1572864 planes 1

omapfb: Pixclock 54000 kHz hfreq 45.6081 kHz vfreq 57.7 Hz

Which is indeed not supported by my monitor according to the manual for it.

-Adam

mansr · October 20, 2008, 10:12pm

Adam Yergovich <ayergo@jkmicro.com> writes:

Måns Rullgård wrote:

Adam Yergovich <ayergo@jkmicro.com> writes:

Måns Rullgård wrote:

Adam Yergovich <ayergo@jkmicro.com> writes:

Hello,

So i recently got a samsung 331 hi def monitor with dvi connector just
for the beagleboard. Much to my dismay, when plugged in it only
displayed "mode not supported", which is listed in the manual as "Check
the maximum resolution and connected device's Video frequency". I
suspect that it is the frequency that is causing the problem, however
i'm not sure what to do about it.

Thanks for the tip on dmesg, i do indeed now see what it is set to. Are
there other configurations available? I've managed to get bit-bake
working for the Angstrom image, but am unclear on how to change settings
such as this.

What messages do you see?

I see:

root@beagleboard:/dev# dmesg | grep omapfb

omapfb: configured for panel omap3beagle
omapfb: DISPC version 3.0 initialized
omapfb: Framebuffer initialized. Total vram 1572864 planes 1
omapfb: Pixclock 54000 kHz hfreq 45.6081 kHz vfreq 57.7 Hz

Nothing like "Using mode 1024x768@60"? If not, you're missing some
patches.

Which is indeed not supported by my monitor according to the manual
for it.

Most monitors seem to accept 57.7 Hz as an approximation of 60 Hz.
Maybe yours is extra picky.

FWIW, my Samsung TV has no trouble with 1280x720 at almost 60 Hz.

Adam_Yergovich · October 20, 2008, 10:48pm

Måns Rullgård wrote:

Adam Yergovich <ayergo@jkmicro.com> writes:

Måns Rullgård wrote:

Adam Yergovich <ayergo@jkmicro.com> writes:

Måns Rullgård wrote:

Adam Yergovich <ayergo@jkmicro.com> writes:

Hello,

So i recently got a samsung 331 hi def monitor with dvi connector just for the beagleboard. Much to my dismay, when plugged in it only displayed "mode not supported", which is listed in the manual as "Check the maximum resolution and connected device's Video frequency". I suspect that it is the frequency that is causing the problem, however i'm not sure what to do about it.

Thanks for the tip on dmesg, i do indeed now see what it is set to. Are there other configurations available? I've managed to get bit-bake working for the Angstrom image, but am unclear on how to change settings such as this.

What messages do you see?

I see:

root@beagleboard:/dev# dmesg | grep omapfb

omapfb: configured for panel omap3beagle omapfb: DISPC version 3.0 initialized omapfb: Framebuffer initialized. Total vram 1572864 planes 1 omapfb: Pixclock 54000 kHz hfreq 45.6081 kHz vfreq 57.7 Hz

Nothing like "Using mode 1024x768@60"? If not, you're missing some
patches.

Nope, nothing like that. I am just using the demo images here:

http://www.angstrom-distribution.org/demo/beagleboard/

Are there some fully patched files somewhere that i can try? Is there any way to change the settings on the beagleboard for the DVI-D output?

-Adam

Adam_Yergovich · October 20, 2008, 11:43pm

Adam Yergovich wrote:

Måns Rullgård wrote:

Adam Yergovich <ayergo@jkmicro.com> writes:

Måns Rullgård wrote:

Adam Yergovich <ayergo@jkmicro.com> writes:

Måns Rullgård wrote:

Adam Yergovich <ayergo@jkmicro.com> writes:

Hello,

So i recently got a samsung 331 hi def monitor with dvi connector just for the beagleboard. Much to my dismay, when plugged in it only displayed "mode not supported", which is listed in the manual as "Check the maximum resolution and connected device's Video frequency". I suspect that it is the frequency that is causing the problem, however i'm not sure what to do about it.

Thanks for the tip on dmesg, i do indeed now see what it is set to. Are there other configurations available? I've managed to get bit-bake working for the Angstrom image, but am unclear on how to change settings such as this.

What messages do you see?

I see:

root@beagleboard:/dev# dmesg | grep omapfb

omapfb: configured for panel omap3beagle omapfb: DISPC version 3.0 initialized omapfb: Framebuffer initialized. Total vram 1572864 planes 1 omapfb: Pixclock 54000 kHz hfreq 45.6081 kHz vfreq 57.7 Hz

Nothing like "Using mode 1024x768@60"? If not, you're missing some
patches.

Nope, nothing like that. I am just using the demo images here:

http://www.angstrom-distribution.org/demo/beagleboard/

Are there some fully patched files somewhere that i can try? Is there any way to change the settings on the beagleboard for the DVI-D output?

When using the beagle board hardware check kernel/uboot/etc i get:

display mode 1024x768x16 hsynch 22kHz vsynch 28 Hz

any way to change the settings for this?

-Adam

Glen_Duncan · October 21, 2008, 12:30am

The kernel in the Angstrom Demo isn’t patched to handle 720p. Try this one:

http://dominion.thruhere.net/koen/OE/uImage-2.6.26+2.6.27-rc7+r14+gite1c49d7d22af768188e2a54c167ed79919361e55-r14-beagleboard.bin

Download it, rename it to ‘uImage’, and copy it to the DOS partition of your SD card. Then make sure your environment on the BB is set.
From the BB bootloader, type:

setenv bootargs ‘console=tttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait video=omapfb:vram:2M,vram:4M,mode:720p60’

Then type: ‘savenv’ followed by: ‘boot’ or simply power cycle.

-Glen

mansr · October 21, 2008, 12:37am

spec <playaspec@gmail.com> writes:

The kernel in the Angstrom Demo isn't patched to handle 720p. Try
this one:

http://dominion.thruhere.net/koen/OE/uImage-2.6.26+2.6.27-rc7+r14
+gite1c49d7d22af768188e2a54c167ed79919361e55-r14-beagleboard.bin

Download it, rename it to 'uImage', and copy it to the DOS partition
of your SD card. Then make sure your environment on the BB is set.
From the BB bootloader, type:

setenv bootargs 'console=tttyS2,115200n8 root=/dev/mmcblk0p2 rw
rootwait video=omapfb:vram:2M,vram:4M,mode:720p60'

This will give almost 60 Hz, which is close enough for most monitors.
If yours doesn't like it, try 480p60, which gives timings exactly per
spec (though only low resolution). There's work underway to give
correct timings for as many modes as possible, but it won't be ready
for yet a while.

Then type: 'savenv' followed by: 'boot' or simply power cycle.

If you just want to test, "boot" without "saveenv" will work. On the
next boot, the old value will be back.

Koen_Kooi2 · October 21, 2008, 7:47am

When using the beagle board hardware check kernel/uboot/etc i get:

All TI u-boots are broken wrt to display timing.

Robert_Kuhn1 · October 21, 2008, 12:34pm

So it would be a solution to use a newer u-boot?

Robert

Robert_Kuhn1 · October 21, 2008, 2:33pm

...or is it possible to use fbset to set the framebuffer to (for
example) 10244768@60Hz?

I tried it with
root@beagleboard:/etc# cat fb.modes
   mode "1024x768-60"
        geometry 1024 768 2048 4096 8
        timings 15880 144 24 29 0 120 3
   endmode

and

   root@beagleboard:/etc# fbset 1024x768-60
   mode "1024x768-60"
        # D: 62.972 MHz, H: 47.997 kHz, V: 59.996 Hz
        geometry 1024 768 2048 4096 8
        timings 15880 144 24 29 0 120 3
        accel false
        rgba 5/11,6/5,5/0,0/0
   endmode

but
root@beagleboard:/etc# fbset -i

   mode "1024x768-29"
        # D: 23.981 MHz, H: 22.370 kHz, V: 28.680 Hz
        geometry 1024 768 1024 1536 16
        timings 41700 40 4 8 2 4 2
        accel false
        rgba 5/11,6/5,5/0,0/0
   endmode

and my monitor says 65Hz...
Robert

mansr · October 21, 2008, 2:37pm

Robert Kuhn wrote:

...or is it possible to use fbset to set the framebuffer to (for
example) 10244768@60Hz?

No. On the fly mode switching is not supported yet.

Adam_Yergovich · October 21, 2008, 4:42pm

Robert Kuhn wrote:

When using the beagle board hardware check kernel/uboot/etc i get:

All TI u-boots are broken wrt to display timing.

So it would be a solution to use a newer u-boot?

Have also tried the Angstrom flavor of uboot and x-loader as stated above so unfortunately not viable.

So clearly there is some work to be done here in two branches.

First for Angstrom, as noted by Mans, on the fly mode switching is not supported yet via fbset. What are the current issues with getting this to work and relavent source code/maintainer?

Second for the Beagle hardware verification images, what is are the issues with getting it to work and what is the interaction between uboot and the kernel that causes the problem?

I'll start digging through the source code for the beagle code (as its not clear to me yet how to dig through the Angstrom code). Any advice is appreciated and thanks much for everything so far.

-Adam

Robert_Kuhn1 · October 27, 2008, 6:58pm

Hello,

...or is it possible to use fbset to set the framebuffer to (for
example) 10244768@60Hz?

No. On the fly mode switching is not supported yet.

How can I change the resolution using Angstrom at all? For example to
800x600 or 640x480 or something like that?

Robert

jkridner · November 2, 2008, 1:09pm

http://elinux.org/BeagleBoardFAQ#Display_resolutions_.231

Robert_Kuhn1 · November 3, 2008, 9:29am

Hello,

How can I change the resolution using Angstrom at all? For example to
800x600 or 640x480 or something like that?

I tried the newest kernel from mansr
(http://git.mansr.com/?p=linux-omap;a=summary) which should contain
the listed patches. My bootargs are:
setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootdelay=2
rootfstype=ext2 ro video=omapfb:mode:1024x768@60 psplash=false
but instead of 1024x768 I get 1280x720@58Hz and a scrambled display
(fuzzy lines).

I compiled with 'make CROSS_COMPILE=arm-angstrom-linux-gnueabi-
omap3_beagle_defconfig'

Do I have to use a git kernel?

Robert

Robert_Kuhn1 · November 3, 2008, 10:19am

Hello,

I worte:

I tried the newest kernel from mansr
(http://git.mansr.com/?p=linux-omap;a=summary) which should contain
the listed patches. My bootargs are:
setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootdelay=2
rootfstype=ext2 ro video=omapfb:mode:1024x768@60 psplash=false
but instead of 1024x768 I get 1280x720@58Hz and a scrambled display
(fuzzy lines).

Perhaps I have a wrong config? Does someone has a working
(Framebuffer..) .config for the kernel by mans?

Robert

Koen_Kooi2 · November 3, 2008, 11:06am

The .27 angstrom kernels have all the patches Måns wrote, so why not
use that?