Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#19558 - running hal affects mesa rendering engine

Attached to Project: Arch Linux
Opened by david cheung (scruffidog) - Saturday, 22 May 2010, 03:51 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 25 May 2010, 09:41 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: OSS ati opengl renderer affected by HAL running with xorg 1.8. With hal, behavior is as it should be, hardware acceleration. With hal NOT running, only mesa software rendering is available.


Additional info:
* package version(s)
xf86-video-ati 6.13.0-1
xf86-video-vesa 2.3.0-2
xorg-res-utils 1.0.3-3
xorg-server 1.8.0.902-1
xorg-server-utils 7.5-3
xorg-utils 7.6-1
xorg-xinit 1.2.1-1
mesa 7.8.1-2

* config and/or log files etc.

Steps to reproduce:
enable/disable hal: /etc/rc.d/hal start|stop
startx
glxinfo | grep -i opengl

This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 25 May 2010, 09:41 GMT
Reason for closing:  Not a bug
Additional comments about closing:  See last comment. There's no other explanation possible than that one.
Comment by Ionut Biru (wonder) - Saturday, 22 May 2010, 10:21 GMT
that can't be true since hal _only_ handles input devices and not video drivers and other configuration.

please upload Xorg.0.log when having hal and without it.
Comment by david cheung (scruffidog) - Saturday, 22 May 2010, 12:31 GMT
hmmm...seem to have jumped the gun a bit....

hal is not the real underlying issue, it seems. Let me see if I can go through the exact sequence of events:

Previous to xorg server 1.8, I have the hal daemon enabled in /etc/rc.conf. Since hal also starts dbus as a dependency, I took that out of the startup, which is where the problem showed up. Since 1.8 does not require hal anymore, I took it out of the daemon startup and that is where the accelerated rendering issue popped up. Typically since I always rebooted the machine when leaving X, this masked the dbus daemon so the steps to reproducing is not accurate. It is when I used the actual steps outlined above that I realize the problem is somewhere else, like a different daemon, assumptions and general laziness. ;)

Since I believe dbus is still required by X, I will enable it instead hal. There was one other issue I experienced with hal not running and adding a bluetooth mouse, but I'm going to recheck that also.
   Xorg.0.log-no-hal-dbus (37.3 KiB)
   Xorg.0.log-hal-dbus (37.4 KiB)
   Xorg.0.log (36.8 KiB)
Comment by Ionut Biru (wonder) - Saturday, 22 May 2010, 17:04 GMT
you need dbus to be in rc.conf, i suppose your user is not in video group and because dbus is down it can't be authorized using consolekit and from here is your rendering issue. note that dbus is needed by a lot for applications so its a must.

btw, if xorg doesn't need hal that doesn't mean you have to disable it. there are a lot of software that needs hal, especially kde

Loading...