On 07/30/14 12:52 PM, Linda A. Walsh wrote:
Łukasz Maśko wrote:
$ cat /var/log/Xorg.0.log | grep LoadModule
[...]
[ 1684.745] (II) LoadModule: "ati"
[ 1684.746] (II) LoadModule: "radeon"
[ 1684.748] (II) LoadModule: "vesa"
[ 1684.749] (II) LoadModule: "fbdev"
You're deffinitely using the vesa driver. The radeon driver is loaded, but
then the vesa driver is initialized as first and it takes control over your
card, so finally, according to line #1700, the radeon driver is unloaded:
----
Side question --
Was it unloaded because Vesa loaded first or because the radeon driver wasn't
able to talk to its kernel component?
I.e. Does it pick drivers based on best match or first match?
It goes through in what in thinks is the best order and tries until one works.
As you can see above, it tried & failed with ati/radeon before falling back to
vesa.
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Engineering - http://blogs.oracle.com/alanc
_______________________________________________
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
