Ubuntu Jaunty Xorg Display Issue

GoogleGroups
1

Hi,

I followed the directions at http://elinux.org/BeagleBoardUbuntu#Xorg_omapfb_Drivers

And even get some output from the HDMI output, but the display is
choppy and has horizontal lines running through the screen. On one LCD
it doesn't even display. On another it flickers a lot with the choppy
and horizontal lines on it.

Below is the output from my Xorg.0.log file.

I am used the following command to create the root filesystem and
kernel:
rootstock --fqdn beagleboard --login ubuntu --password temppwd --
imagesize 2G --seed xserver-xorg-video-omap3,bridge-utils,nano,linux-
firmware,wireless-tools,usbutils,ffmpeg,xfce4,gdm,ubuntu-minimal --
dist karmic --serial ttyS2 --kernel-image http://rcn-ee.net/d
eb/kernel/beagle/karmic/v2.6.31.6-x6.0/linux-image-2.6.31.6-
x6.0_1.0karmic_armel.deb

Any ideas why the display is so crappy and has artifacts?

BTW: I got Angstrom to load and it displays just fine! Unfortunately,
I had issues with getting my webcam to be recognized, but ran in to

X.Org X Server 1.6.4
Release Date: 2009-9-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.28-14-lange51 armv7l Ubuntu
Current Operating System: Linux beagleboard 2.6.31.6-x6.0 #1 PREEMPT
Fri Nov 13 17:02:45 UTC 2009 armv7l
Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw
rootfstype=ext3 rootwait omapfb.mode=dvi:1280x768MR-16@60
Build Date: 26 October 2009 05:21:20PM
xorg-server 2:1.6.4-2ubuntu4 (buildd@)
  Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 31 16:00:11 1969
(==) Using config file: "/etc/X11/xorg.conf"
(==) No Layout section. Using the first Screen section.
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Configured Video Device"
(==) No monitor specified for screen "Default Screen".
  Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
  Entry deleted from font path.
(==) FontPath set to:
  /usr/share/fonts/X11/misc,
  /usr/share/fonts/X11/100dpi/:unscaled,
  /usr/share/fonts/X11/75dpi/:unscaled,
  /usr/share/fonts/X11/Type1,
  /usr/share/fonts/X11/100dpi,
  /usr/share/fonts/X11/75dpi,
  /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
  built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
  If no devices become available, reconfigure HAL or disable
AllowEmptyInput.
(II) Loader magic: 0xd80
(II) Module ABI versions:
  X.Org ANSI C Emulation: 0.4
  X.Org Video Driver: 5.0
  X.Org XInput driver : 4.0
  X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7

(II) No APM support in BIOS or kernel
(II) System resource ranges:
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
  compiled for 1.6.4, module version = 1.0.0
  Module class: X.Org Server Extension
  ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
  compiled for 1.6.4, module version = 1.0.0
  Module class: X.Org Server Extension
  ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
  compiled for 1.6.4, module version = 1.0.0
  ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
  compiled for 1.6.4, module version = 1.13.0
  Module class: X.Org Server Extension
  ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
  compiled for 1.6.4, module version = 1.0.0
  ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
  compiled for 1.6.4, module version = 1.1.0
  ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "omapfb"
(II) Loading /usr/lib/xorg/modules/drivers//omapfb_drv.so
(II) Module omapfb: vendor="X.Org Foundation"
  compiled for 1.6.0, module version = 0.1.1
  ABI class: X.Org Video Driver, version 5.0
(II) omapfb: Driver for OMAP framebuffer (omapfb) and external LCD
controllers:
  omap1/2/3, S1D13745, HWA742
(WW) Falling back to old probe method for OMAPFB
(II) Running in FRAMEBUFFER Mode
(WW) Error opening /sys/devices/platform/omapfb/ctrl/name: No such
file or directory
(WW) Can't autodetect LCD controller, assuming internal
(II) LCD controller: internal
(II) omapfb(0): VideoRAM: 1920KiB (SDRAM)
(II) omapfb(0): Creating default Display subsection in Screen section
  "Default Screen" for depth/fbbpp 16/16
(**) omapfb(0): Depth 16, (--) framebuffer bpp 16
(==) omapfb(0): RGB weight 565
(==) omapfb(0): Default visual is TrueColor
(--) omapfb(0): Virtual size is 1280x768 (pitch 1280)
(**) omapfb(0): Built-in mode "current"
(==) omapfb(0): DPI set to (96, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
  compiled for 1.6.4, module version = 1.0.0
  ABI class: X.Org ANSI C Emulation, version 0.4
(II) omapfb(0): DPMS enabled
(II) omapfb(0): Video plane capabilities:
(II) omapfb(0): Video plane supports the following image formats:
(II) omapfb(0): XVideo extension initialized
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(NI) OMAPFBSaveScreen: Dim backlight?
(EE) config/hal: couldn't initialise context: unknown error (null)
(NI) OMAPFBSaveScreen: Dim backlight?
(NI) OMAPFBSaveScreen: Dim backlight?

2

Nope, but lets get some more useful debug info..

add, "omapfb.debug=y" and "omapdss.debug=y" to your bootargs and
please pastebin your dmesg log.

What display is this? (model/etc)

Regards,

3

Okay here is the link to the pastebin of my dmesg cmd: http://pastebin.com/m1b57042f

I am using a HP DLP Projector Model ep9010. I have also tried on a
View Sonic VA1912wb. On the projector I am able to see some of the
display when there isn't a lot of content on the screen, but when more
content starts displaying the display stops displaying. On the view
sonic it doesn't even display.

Angstrom displays just fine, but Ubuntu doesn't.

Also, I am using a KBOC BB 2 which is a beagleboard clone. It looks
like it uses a TI TF410 for the DVI serializer.

I appreciate you taking the time to look at this, and also teaching me
how to debug these types of issues.

Regards,
Neel

4

Hi Neel,

There's nothing obvious to me.

Can i have you try this uImage and modules? It's contains the latest
patches from Tomi Valkeinen's linux-omap-dss2/linux:gitorious/for-next
tree..

http://www.rcn-ee.net/deb/kernel/testing/2.6.32-x0.0.uImage
http://www.rcn-ee.net/deb/kernel/testing/2.6.32-x0.0-modules.tar.gz

I've barely stress tested it (ehci/musb), so no promises but we are
testing the display. If the display works, i'll add those patches to
the 2.6.31 branch..

Regards,

5

Hi Nelson:
I followed guide ashttp://elinux.org/BeagleBoardUbuntu to run ubuntu
on beagle board.Two questions:
Question 1:I downloaded demo images (9.04 and 9.10), both can boot,
while there is only shell command line, without any GNOME windows. Is
the demo images doesn't include them?
Question 2:I tried to build on my host linux machine via rootstock. My
host dekstop linux is behind a proxy server with correct proxy
setting. While I found the QUME VM can't inherit proxy automatically
from host linux. So build failed to fetch external package. Is there
are way to setup proxy in QUME VM? or setup a local repository to
avoid external internet connection?

Thanks!

6

Hi Nelson:
I followed guide ashttp://elinux.org/BeagleBoardUbuntu to run ubuntu
on beagle board.Two questions:
Question 1:I downloaded demo images (9.04 and 9.10), both can boot,
while there is only shell command line, without any GNOME windows. Is
the demo images doesn't include them?
Question 2:I tried to build on my host linux machine via rootstock. My
host dekstop linux is behind a proxy server with correct proxy
setting. While I found the QUME VM can't inherit proxy automatically
from host linux. So build failed to fetch external package. Is there
are way to setup proxy in QUME VM? or setup a local repository to
avoid external internet connection?

Thanks!

7

Hi Samuel,

Hi Nelson:
I followed guide ashttp://elinux.org/BeagleBoardUbuntu to run ubuntu
on beagle board.Two questions:
Question 1:I downloaded demo images (9.04 and 9.10), both can boot,
while there is only shell command line, without any GNOME windows. Is
the demo images doesn't include them?

It's a bandwidth issue... My goal was to provide 'a' demo image thats
useful to everyone needs. Any of the gui environments would take an
additional 200-300Mb download and not everyone uses the same
enviroment.

So using the demo image, you can setup your network, then install what
ever guy you need gnome "sudo apt-get install metacity gdm" or xfce4
"sudo apt-get install xfce4 gdm" or kde "sudo apt-get install kde kdm"

Question 2:I tried to build on my host linux machine via rootstock. My
host dekstop linux is behind a proxy server with correct proxy
setting. While I found the QUME VM can't inherit proxy automatically
from host linux. So build failed to fetch external package. Is there
are way to setup proxy in QUME VM? or setup a local repository to
avoid external internet connection?

Probably... How do you setup your proxy on your host machine? What's
the proxy server address, port, is there a user name and password?

Only two applications need proxy access... apt-get and wget...
apt-get stores proxy info in /etc/apt/apt.conf and wget can use
"export http_proxy="...

So let me know that info, I'll patch rootstock and you can test it.. :wink:

Regards,

8

HI, Nelson:
For my proxy setting, I setup proxy in my host linux's shell window,
via:
export http_proxy=http://myproxyserverIP:port/
export ftp_proxy=http://myproxyserverIP:port/
I setup proxy manually when open a new shell windows. Need I fix it
in /etc/bash.bashrc?
The proxy is anonymous access w/o any user name and pwd credential.

I speculate that your enhancement will automatically inherit any host
Linux's proxy, and won't fix on stick a specific proxy setting. Am I
correct?

2 more questions:
Could you elaborate how to handle it if I want to change the armel
kernel via menuconfig?
I noticed that your Basic Beagleboard image command line contains
xfce4. Does it mean if I can successfully build a image after solving
proxy issue, I should get a image with GNOME?

Basic Jaunty (9.04) Beagleboard xfce4 image:
sudo ./rootstock --fqdn beagleboard --login ubuntu --password temppwd
--imagesize 2G --seed xfce4,gdm --dist jaunty \
--serial ttyS2 --kernel-image
http://rcn-ee.net/deb/kernel/beagle/jaunty/v2.6.29-58cf2f1-oer44.1/linux-image-2.6.29-oer44.1_1.0jaunty_armel.deb

Basic Karmic (9.10) Beagleboard xfce4 image:
sudo ./rootstock --fqdn beagleboard --login ubuntu --password temppwd
--imagesize 2G --seed xfce4,gdm --dist karmic \
--serial ttyS2 --kernel-image
http://rcn-ee.net/deb/kernel/beagle/karmic/v2.6.31.6-x6.0/linux-image-2.6.31.6-x6.0_1.0karmic_armel.deb

Thanks!

9

Hi Samuel,

HI, Nelson:
For my proxy setting, I setup proxy in my host linux's shell window,
via:
export http_proxy=http://myproxyserverIP:port/
export ftp_proxy=http://myproxyserverIP:port/
I setup proxy manually when open a new shell windows. Need I fix it
in /etc/bash.bashrc?
The proxy is anonymous access w/o any user name and pwd credential.

I speculate that your enhancement will automatically inherit any host
Linux's proxy, and won't fix on stick a specific proxy setting. Am I
correct?

I added a quick proxy setting for rootstock. Basically no bash
parameters get passed to the qemu virtual machine on startup so it
loses your export variables.. It's pretty simple, but right before
qemu enables the network device, it'll now run "export
http_proxy=http:…" which hopefully is enough to make things work...

Code is here: https://code.launchpad.net/~beagleboard-kernel/+junk/project-rootstock-proxy

you can download it with "bzr" via: bzr branch
lp:~beagleboard-kernel/+junk/project-rootstock-proxy

it's looking for: "-p http://myproxyserverIP:port/" or "--proxy
http://myproxyserverIP:port/"

Let me know how well it works.. If it works i'll bug Oliver and have
it for future rootstock releases...

2 more questions:
Could you elaborate how to handle it if I want to change the armel
kernel via menuconfig?

Sure... Pick your tree, currently: stable=2.6.31 or dev=2.6.32..

https://code.launchpad.net/~beagleboard-kernel/+junk/2.6-dev

I noticed that your Basic Beagleboard image command line contains
xfce4. Does it mean if I can successfully build a image after solving
proxy issue, I should get a image with GNOME?

Basic Jaunty (9.04) Beagleboard xfce4 image:
sudo ./rootstock --fqdn beagleboard --login ubuntu --password temppwd
--imagesize 2G --seed xfce4,gdm --dist jaunty \
--serial ttyS2 --kernel-image
http://rcn-ee.net/deb/kernel/beagle/jaunty/v2.6.29-58cf2f1-oer44.1/linux-image-2.6.29-oer44.1_1.0jaunty_armel.deb

Basic Karmic (9.10) Beagleboard xfce4 image:
sudo ./rootstock --fqdn beagleboard --login ubuntu --password temppwd
--imagesize 2G --seed xfce4,gdm --dist karmic \
--serial ttyS2 --kernel-image
http://rcn-ee.net/deb/kernel/beagle/karmic/v2.6.31.6-x6.0/linux-image-2.6.31.6-x6.0_1.0karmic_armel.deb

Thanks!

xfce4 gives the most useful desktop for the beagleboard, gnome needs a
whole lot of swap... But if you want to install gnome, the package is
called "metacity" lxde was another good option for 9.04, but it's not
as clean in 9.10...

Regards,

10

Hi Robert,

Sorry for the delay, I was out for the weekend. I tried with the files
linked below, but it did not fix the display issues. I did see the
Penguin instead of the beagle board splash. Those splash screens
display fine, the problem occurs when the X server starts and tries to
display a UI.

Here's the dmesg paste bin: http://pastebin.com/m3468ad37

Regards,
Neel

11

Thanks Nelson, i am installing metacity gdm via apt-get, using 9.10
ubuntu.
While I found source "deb http://ports.ubuntu.com/ubuntu-ports karmic-
updates main universe" is extremely slow (6-7B/s)
Is there any know faster mirror source for armel binary? (Or any
popular ubuntu source repository contains both x86 and armel binary
files?)

Thanks!

12

Thanks Nelson! While I found bzr seems still can't support proxy. any
idea to get your branch?

13

you can download it directly with this link:

wget http://bazaar.launchpad.net/~beagleboard-kernel/%2Bjunk/project-rootstock-proxy/download/head%3A/rootstock-20090708103529-eg1jslozsn8cqwvq-1/rootstock

No, unless you can find a local mirror, it's only on the
ports.ubuntu.com server.

Regards,

14

Hi Neel,

Just to clarify since this is rather strange. The flickering only
occurs when xorg starts and the screen is fine during kernel boot?

Does this also occur if you use the "fbdev" driver.. (not that the
omapfb driver even touches the actuall hardware)

Regards,

15

HI, Nelson:
Thanks, I can run your demo 9.04 image correctly, while I hit a issue
when installing OMAP video driver inside 9.04 OS as following:

ubuntu@beagleboard:~$ sudo dpkg -i xserver-xorg-video-
omap3_0.1.1-2_armel.deb
dpkg: regarding xserver-xorg-video-omap3_0.1.1-2_armel.deb containing
xserver-xorg-video-omap3:
xserver-xorg-core conflicts with xserver-xorg-video-2
  xserver-xorg-video-omap3 provides xserver-xorg-video-2 and is to be
installed.
dpkg: error processing xserver-xorg-video-omap3_0.1.1-2_armel.deb (--
install):
conflicting packages - not installing xserver-xorg-video-omap3
Errors were encountered while processing:
xserver-xorg-video-omap3_0.1.1-2_armel.deb

Any idea? should I firstly install xserver-xorg-video-
omapfb_0.1.1-2_armel.deb?

Samuel

16

Hi Samuel,

It's actually an either/or thing... So don't install
"xserver-xorg-video-omapfb" its for omap devices with no 'neon'
hardware...

It should work as-is with the initial rootfile system.. Tested it a
month ago, by chance did you add updates to /etc/apt/source.list and
update the system? If so, i might have to update and rebuilt the
package for that situation..

This won't be an issue in karmic and lucid, since the package is in
ubuntu's repo..

Regards,

17

So, does it mean I should forget 9.04 and switch to 9.10? Thanks!
Samuel

18

BTW, I didn't follow Kernel Modules/SDK/Startup Script part at
http://elinux.org/BeagleBoardUbuntu. Should I follow them before
install xserver-xorg-video-
omap3_0.1.1-2_armel.deb?
Samuel

19

Hi Samuel,

It's up to you, both will work. 9.10 does have new features and is
more optimized then 9.04. Anyways, with 9.04 that package should have
worked, did you have any of the updates added/installed?

No, those sections in the Advanced section are pretty independent...

Regards,

20

BTW, I didn't follow Kernel Modules/SDK/Startup Script part at
http://elinux.org/BeagleBoardUbuntu. Should I follow them before
install xserver-xorg-video-
omap3_0.1.1-2_armel.deb?
Samuel