Am 26.06.2012 um 17:46 schrieb Guillaume Gardet :

Hi,

Is there any reason to have all the lines commented in the config file 20-omapfb.conf for xorg-x11-drv-omapfb?

Mind to paste what you mean exactly? Alex

Guillaume

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 26.06.2012, at 18:13, Guillaume Gardet wrote:

Le 26/06/2012 17:55, Alexander Graf a écrit :

...

Am 26.06.2012 um 17:46 schrieb Guillaume Gardet :

...

Hi,

Is there any reason to have all the lines commented in the config file 20-omapfb.conf for xorg-x11-drv-omapfb? Mind to paste what you mean exactly?

Have a look on 20-omapfb.conf file in xorg-x11-drv-omapfb: https://build.opensuse.org/package/files?package=xorg-x11-drv-omapfb&project=openSUSE%3AFactory%3AARM

We have 20-omapfb.conf file: ******************************************************************************** #Section "Monitor" #Identifier "Configured Monitor" #EndSection

#Section "Screen" #Identifier "Default Screen" #Device "Configured Video Device" #EndSection

#Section "Device" #Identifier "Configured Video Device" #Driver "omapfb" #Option "fb" "/dev/fb0" #EndSection ********************************************************************************

All lines are useless like this, we should remove the #.

Removing the # makes things work for you? :) Send a sr then! Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 27.06.2012, at 11:56, Guillaume Gardet wrote:

Le 26/06/2012 19:31, Alexander Graf a écrit :

...

On 26.06.2012, at 18:13, Guillaume Gardet wrote:

...

Le 26/06/2012 17:55, Alexander Graf a écrit :

...

Am 26.06.2012 um 17:46 schrieb Guillaume Gardet :

...

Hi,

Is there any reason to have all the lines commented in the config file 20-omapfb.conf for xorg-x11-drv-omapfb? Mind to paste what you mean exactly? Have a look on 20-omapfb.conf file in xorg-x11-drv-omapfb: https://build.opensuse.org/package/files?package=xorg-x11-drv-omapfb&project=openSUSE%3AFactory%3AARM

We have 20-omapfb.conf file: ******************************************************************************** #Section "Monitor" #Identifier "Configured Monitor" #EndSection

#Section "Screen" #Identifier "Default Screen" #Device "Configured Video Device" #EndSection

#Section "Device" #Identifier "Configured Video Device" #Driver "omapfb" #Option "fb" "/dev/fb0" #EndSection ********************************************************************************

All lines are useless like this, we should remove the #. Removing the # makes things work for you? :) Send a sr then!

If I do not uncomment the lines I get: Fatal server error: no screens found

If I uncomment it, and use a 1440x900 resolution, X is now launched but on the DVI output I get a black screen.

Then I tried to launch xterm for example: DISPLAY=:0 xterm And on dmesg, I get: [ 631.098022] fbcvt: 1440x900@60: CVT Name - 1.296MA-R [ 631.120971] Console: switching to colour frame buffer device 180x56 [ 662.495513] omapdss DISPC error: SYNC_LOST on channel lcd, restarting the output with video overlays disabled [ 665.345764] usb 1-2.2: link qh8-0e01/de3c96c0 start 3 [1/2 us] [ 665.567565] omapdss OVERLAY error: overlay 0 horizontally not inside the display area (0 + 1440 >= 720) [ 665.567596] omapdss APPLY error: failed to enable overlay 0: check_settings failed

After a reboot, I tried a lower resolution, 640x480: modprobe omapfb mode='dvi:640x480MR-16@60' and I get on dmesg: [ 162.705108] fbcvt: 640x480@60: CVT Name - .307M3-R [ 162.712066] Console: switching to colour frame buffer device 80x30 Then, I start X which crash: startx& ********** hostname: Name or service not known xauth: file /root/.serverauth.3468 does not exist

X.Org X Server 1.12.2 Release Date: 2012-05-29 X Protocol Version 11, Revision 0 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux linux 3.4.2-1-omap2plus #2 SMP Wed Jun 20 03:23:26 UTC 2012 armv7l Kernel command line: console=ttyO2,115200n8 mpurate=auto buddy=none camera=none vram=12M omapfb.mode=dvi:640x480MR-16@60 omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait Build Date: 14 June 2012 09:32:03PM

Current version of pixman: 0.24.4 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: Sat Jan 1 01:23:49 2000 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d"

Backtrace: 0: X (xorg_backtrace+0x1d) [0xf385e] 1: X (0x8000+0xee304) [0xf6304] 2: /lib/libc.so.6 (__default_rt_sa_restorer_v2+0x0) [0xb6c5dea0]

Segmentation fault at address 0xb6abf000

Fatal server error: Caught signal 11 (Segmentation fault). Server aborting

Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error ------------------------------------------------------------------------------------------- xinit failed. /usr/bin/Xorg is not setuid, maybe that's the reason? If so either use a display manager (strongly recommended) or adjust /etc/permissions.local **********

In the log I have one error: (EE) omapfb(0): FBIOBLANK: Invalid argument

Finally, I tried this config file (which do not use omapfb driver but a generic fbdev): http://newton.ast.man.ac.uk/files/Xfiles/xorg.conf-fbdev

And I get a working X, with startx and I launched an xterm then: DISPLAY=:0 xterm&

So, it seems there are problems with omapfb driver or at least with its configuration. Maybe kernel driver changed and xorg driver was not updated accordingly?

Not sure. I do remember that the omapfb driver was quite buggy, but I don't exactly remember how I got it rolling. Dirk, the beagleboard on your desk has a working omapfb configuration. Mind to tell me which IP it has today, so I can extract the necessary information? Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 27.06.2012, at 16:15, Dirk Müller wrote:

On Wednesday 27 June 2012, Alexander Graf wrote:

...

Dirk, the beagleboard on your desk has a working omapfb configuration. Mind to tell me which IP it has today, so I can extract the necessary information?

It does not get an IP address atm as the ethernet is not working, but you can connect to the screen session as root@oldboy

Hrm, this is what I could find. Probably doesn't help you too much though :(. I do remember that I had omapfb working, but with occasional black screens, since it was exceeding the GPU bus bandwidth. linux:~ # cat /proc/cmdline root=/dev/disk/by-id/mmc-SA04G_0x1540fb4a-part2 loader=uboot disk=/dev/disk/by-id/mmc-SA04G_0x1540fb4a resume=/dev/disk/by-id/mmc-SA04G_0x1540fb4a-part3 kiwistderr=/dev/ttyO2 console=ttyO2 vram=16M linux:~ # cat /etc/X11/xorg.conf.d/20-omapfb.conf Section "Monitor" Identifier "dvi" EndSection Section "Screen" Identifier "Default Screen" Device "Configured Video Device" Monitor "dvi" EndSection Section "Device" Identifier "Configured Video Device" #Driver "omapfb" Driver "fbdev" Option "fb" "/dev/fb0" EndSection linux:~ # -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi Guillaume, This was requested by the xorg maintainers when I submitted the package. Regards, Joop. On Tue, June 26, 2012 5:46 pm, Guillaume Gardet wrote:

Hi,

Is there any reason to have all the lines commented in the config file 20-omapfb.conf for xorg-x11-drv-omapfb?

Guillaume

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 27.06.2012, at 17:29, Guillaume Gardet wrote:

Le 27/06/2012 17:26, Joop Boonen a écrit :

...

Hi Guillaume,

This was requested by the xorg maintainers when I submitted the package.

Ok.

It seems we can use omapdrm (staging driver) with those tools: https://github.com/robclark/xf86-video-omap

Currently with omapfb, we use thsose tools: http://cgit.pingu.fi/xf86-video-omapfb/

Well, once you get something working, we can always a) update the packages to work b) change the configuration to work with JeOS-beagle or create a new XFCE-beagle image :) Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org