Xorg 7.4 upgrade - report

ale · Apr 4, 2009

In fact the messages are gone.
No apparent problems at the moment.
I've also built xorg-server using WITH_HAL for the first time and moused is still enabled and working.

hydra · Apr 5, 2009

Xorg 7.4 finally works for me, I'm really glad I can keep my system up to date.

ale · Apr 5, 2009

BTW, it seems that now DontZap defaults to true.
That means that you can use ctrl+alt+bkspace to kill xorg or, for example, to restart gdm.
I really can't understand the reasons of this stupid setting.
To have it working again, in xorg.conf

Code:

Section "ServerFlags"
        Option  "DontZap" "false"
EndSection

adamk · Apr 5, 2009

ale said:
BTW, it seems that now DontZap defaults to true.
That means that you can use ctrl+alt+bkspace to kill xorg or, for example, to restart gdm.
I really can't understand the reasons of this stupid setting.
To have it working again, in xorg.conf

Code:

Section "ServerFlags" Option "DontZap" "false" EndSection

There were a lot of complaints on the Xorg mailing list that people were accidentally hitting that key combination. I guess they figured that those who want DontZap enabled are not as smart as the rest of us and won't be able to figure out how to enable it

Adam

ale · Apr 5, 2009

adamk said:
There were a lot of complaints on the Xorg mailing list that people were accidentally hitting that key combination.

Accidentally?
I think that unless they have 8-9 fingers per hand, that can't be done accidentally.
And what about ctrl+alt+del?

octix · Apr 5, 2009

Hi.

I have upgraded xorg to 1.6 and I do experience some strange behavior.

1. I started to get this warning: (WW) intel(0): DRI2 requires UXA (tried to load it, but apparently it doesn't exist)
2. Cannot watch any movie

it crashes! it just hangs...

Yes, I did portupgrade -a and have latest intel driver...

PS: i have an intel x3100 video card...

adamk · Apr 5, 2009

Did you set the AccelMethod option to UXA? I'm not sure if DRI2 will actually be supported, or if it requires more changes to the DRM, but that's how you can change from XAA or EXA to UXA.

Adam

octix · Apr 5, 2009

Yes. It gets even worse... I get a blank screen and it stops.

Looking in modules dir i couldn't find uxa lib..

./ libfb.la* libshadowfb.so* libxaa.la*
../ libfb.so* libvbe.la* libxaa.so*
drivers/ libint10.la* libvbe.so* libxf8_16bpp.la*
extensions/ libint10.so* libvgahw.la* libxf8_16bpp.so*
input/ libshadow.la* libvgahw.so* linux/
libexa.la* libshadow.so* libwfb.la* multimedia/
libexa.so* libshadowfb.la* libwfb.so*

Do I need to install it manually? I couldn't find it in ports...

man uxa gives nothing... comparing to man exa

Thanks.

octix · Apr 5, 2009

Also in logs I have: "exaCopyDirty: Pending damage region empty!"
Don't know what does this mean...

adamk · Apr 5, 2009

It's quite possible that UXA is not available yet on FreeBSD or requires a newer version of the intel DDX than what is available in ports.

octix · Apr 6, 2009

Thanks. I could live with that, but cannot figure out the cause of crashing of X when I try to play a movie.. mplayer or xine..

How can I debug more? X.log.0.old or just .0 doesn't give me much...

octix · Apr 6, 2009

OK. Apparently it's intel's new driver... i switched to vesa for now and it works.. i mean no crashes..

And I think here is the sa me issue http://forums.freebsd.org/showthread.php?p=18894

pe3sos · Apr 6, 2009

Xorg USB mouse

My I got a problem i start dbus and hald
in rc.conf I have
dbus_enable="yes"
hald_enable="yes"

i killed moused

in xorg.conf i have tested

/dev/mouse
/dev/sysmouse
/dev/ums0
/dev/input/mice

I have a USB mouse and a USB keyboard?
Any ideeea:-?

pe3sos · Apr 6, 2009

write in xorg.conf at section driver Intel or intel for me works

Philippe-Pierre · Apr 9, 2009

Hello all,

I'm running FreeBSD 7.1 release.
After the last update from the ports (yesterday) I lost my french azerty keyboard config (fr-latin9). I now have a basic azerty keyboard without the french accents, and the "Alt" key is useless for typing (but works as a modkey to control my windows manager, which is dwm).

I can't seem to find anything related to such a problem in UPDATING.

I noticed that I now absolutly need

Code:

Option "AllowEmptyInput" "off"

in xorg.conf, I have no mouse nor keyboard under X without this line.

Moreover, the lines

Code:

Option      "XkbLayout"   "fr"
        Option      "XkbVariant"   "latin9"

seem to be useless. If I remove them, I still have this basic azerty keyboard.

I tried, as recommended in this thread, to enable dbus and hal at startup, but no luck.

Here is my xorg.conf

Code:

Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
	Option "AllowEmptyInput" "off"
	#Option "AutoAddDevices" "off"
EndSection

Section "Files"
	#RgbPath      "/usr/local/share/X11/rgb"
	ModulePath   "/usr/local/lib/xorg/modules"
	FontPath     "/usr/local/lib/X11/fonts/misc/"
	FontPath     "/usr/local/lib/X11/fonts/TTF/"
	FontPath     "/usr/local/lib/X11/fonts/OTF"
	FontPath     "/usr/local/lib/X11/fonts/Type1/"
	FontPath     "/usr/local/lib/X11/fonts/100dpi/"
	FontPath     "/usr/local/lib/X11/fonts/75dpi/"
        FontPath     "/usr/local/lib/X11/fonts/Speedo/"
        FontPath     "/usr/local/lib/X11/fonts/bitstream-vera/"
	FontPath     "/usr/local/lib/X11/fonts/Liberation/"
        FontPath     "/usr/local/lib/X11/fonts/terminus-font/"
#	FontPath     "/usr/local/lib/X11/fonts/dejavu/"
	FontPath     "/usr/local/lib/X11/fonts/freefont-ttf/"
        FontPath     "/usr/local/lib/X11/fonts/URW/"
        FontPath     "/usr/local/lib/X11/fonts/urwfonts-ttf/"
EndSection

Section "Module"
	Load  "extmod"
	Load  "record"
	Load  "dbe"
	Load  "glx"
	Load  "GLcore"
#	Load  "xtrap"
	Load  "dri"
#	Load  "freetype"
#	Load  "type1"
EndSection

#Section "ServerFlags"
#  Option  "AllowEmptyInput"       "False"
#EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
 	Option      "XkbRules"    "xorg"
        Option      "XkbModel"    "pc105"
        Option      "XkbLayout"   "fr"
        Option      "XkbVariant"   "latin9"
	Option	    "Autorepeat" "250 30" # ajout
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "auto"
	Option	    "Device" "/dev/sysmouse"
#	Option      "Device" "/dev/psm0"
	Option	    "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
	#DisplaySize	  380   300	# mm
	Identifier   "Monitor0"
	VendorName   "SAM"
	ModelName    "SyncMaster"
 ### Comment all HorizSync and VertRefresh values to use DDC:
	HorizSync    30.0 - 81.0
	VertRefresh  56.0 - 75.0
	Option	    "DPMS"
EndSection

Section "Monitor"
	Identifier   "Monitor1"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
EndSection

Section "Device"
	Identifier  "Card0"
	Driver      "radeon"
	VendorName  "ATI Technologies Inc"
	BoardName   "RV280 [Radeon 9200 PRO]"
	BusID       "PCI:1:0:0"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	SubSection "Display"
		Viewport   0 0
		Depth     1
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     4
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     8
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     15
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     16
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes	"1280x1024"
	EndSubSection
EndSection

I don't have a clue what's happening here... I've been running freebsd for three years, upgraded every month, and it's the first big problem (and seemingly undocumented) that I encounter.

I guess I have to rely on more experienced users to solve this

.

Thanks in advance, people

ale · Apr 9, 2009

Try creating /usr/local/etc/hal/fdi/policy/10-x11-input.fdi like this

Code:

<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
  <device>
    <match key="info.capabilities" contains="input.keyboard">
      <merge key="input.xkb.layout" type="string">fr</merge>
    </match>
  </device>
</deviceinfo>

Make also sure that the other ports are updated.
Yesteday morning I had a problem caused by xkeyboard-config that has been solved after updating again.

tangram · Apr 9, 2009

Add the following to /etc/rc.conf:

Code:

moused_nondefault_enable="NO"
moused_enable="NO" 
dbus_enabled="YES"
hald_enabled="YES"

Next copy the a needed hal policy:

Code:

# cp /usr/local/share/hal/fdi/policy/10osvednor/a0-x11-input.fdi /usr/local/etc/hal/fdi/policy/

Edit the file by changing >pt< to your country's keyboard layout (should be fr):

Code:

<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keyboard">
<merge key="input.xkb.layout" type="string">pt</merge>
</match>
</device>
</deviceinfo>

And that's it.

Philippe-Pierre · Apr 9, 2009

Thank you! ale, tangram, and all the contributors of this thread!

I did exactly what you adviced, and everything is fine now.
I only had to do the very laste update of xkeyboard-config, as ale was expecting, for the trick to be done.

Well I'm already missing moused when in the console, but one can't have everything, can he?

Thanks again, pals.

tangram · Apr 9, 2009

Yeah... and I'm missing having my mouse button properly mapped.

Hal and its bloody fdi policies don't accept the old xorg.conf option "ButtonMapping" and that way I can't map my MX500 buttons the way I like for Enemy Territory.

Rather annoying the Xorg's move to hal. It caughted many users off guard not only in FreeBSD but also in all Unix-like systems out there.

arp242 · Apr 9, 2009

You can just disable HAL for the Xorg server, then it seems to work pretty well ...

I don't really see the point of HAL, the *lack* of automagic background stuff is a *good* thing and one of the reasons I like FreeBSD.
And XML configuration is totally brainf*cked, the less said about that the better.

ale · Apr 9, 2009

I've both hald and moused enabled and everything is working fine.

I've started to build xorg-server with hal only since the commit before 1.6.
I don't know if that's the reason and one day it will stop working for me too.

This is what I have in /etc/rc.conf for my ps/2 mouse

Code:

moused_port="/dev/psm0"
moused_type="auto"
moused_enable="YES"

And this is from my /etc/X11/xorg.conf

Code:

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "auto"
        Option      "Device" "/dev/sysmouse"
        Option      "ZAxisMapping" "4 5"
EndSection

ale · Apr 9, 2009

Carpetsmoker said:
And XML configuration is totally brainf*cked, the less said about that the better.

I couldn't agree more.

trev · Apr 11, 2009

trev said:
I have semi-solved the window tearing/artifacts issue:

1) Disable acceleration - but only if you enjoy watching paint dry. [Option "NoAccel" "True"]

or my current preferred option...

2) Switch acceleration from the default of XAA to EXA - this halves the frame rate (240fps to 102fps with glxgears), but the tearing/artifacts go away. [Option "AccelMethod" "EXA", Option "MigrationHeuristic" "greedy"]

I recompiled all the latest X widgets this evening without the above workarounds and... all has returned to normal. Actually, better than normal! The glxgears frame rate is now 398fps compared with 240fps (or 102fps with the workarounds). Ahhhh.

Android1 · Apr 11, 2009

I just installed xserver 1.6, and I am noticing two (2) things.

1. If I startx and kill X, the console seems abnormally speeded up once I return to the console. I am talking about things like scroll and backspace deletion speed. What could be causing this?

2. This is not really a big deal, but I am still curious. If I startx with a configuration file, twn loads and everything seems to work fine. However, if I run "X -config" on the same file, all I get is a blank screen which will stay up indefinitely. This does not seem like normal behavior.

Aside from the aforementioned oddities and the unfortunate decision to disable Ctrl-Alt-Backspace by default, everything seems to be peachy so far. I did freak out, though, when twm loaded with a black background, but apparently, that is its new default behavior. Silly me.

razrx · Apr 17, 2009

ale said:
You are saying that it doesn't work with the configuration generated by # Xorg -configure ?

in my situation this is exactly what happens on a 7.1-RELEASE-p4 box running xorg7.4 (xorg-server 1.6.0) and a ATI Technologies Inc RV380 [Radeon X600 (PCIE)] card with all ports up2date :OOO

i run Xorg -config /root/xorg.conf.new after Xorg -configure (as root).
screen goes blank, Xorg process takes up 100%cpu and will not back out of a ctrl-alt-backspace (i'm aware that latest xorg7.4 no longer allows you to use ctrl-alt-backspace by default and that you have to set the DontZap to "off" option to get the old behavior back).
i currently have xorg-server 1.6.0 built without hal but before this i had it built with hal.

normally i use xdm from /etc/ttys but even using the most basic xorg.conf or using startx (that used to startup fluxbox-1.1.0.1_5 fine with previous xorg) no longer functions :q