Xorg testers needed [Archive]

Pages : [1] 2

bryceharrington

July 3rd, 2007, 03:34 AM

Heya all,

I've started working on Ubuntu's xorg packages recently, and am looking for others interested in helping improve Ubuntu's Xorg quality. If you're the sort of person who enjoys the thrill of booting nigh-untested Xorg code, (esp. if you have a second box to test on) please read on.

I've posted several packages for testing, to this location, with specifics below:
http://people.ubuntu.com/~bryce/Testing/

A warning before you install any of these - take care to only install these on a machine you can reinstall if needed. While I test each of these personally before I upload them, this testing does involve risking your system getting hosed up. The testing's for a good cause, and more than likely nothing will go wrong, but make sure you have a way to recover.

So with that caveat out of the way, here's the fresh meat for testing:

0. xrandr (1.2.1): I had uploaded libxrandr2 1.2.1 a little bit ago but neglected to also update the commandline tool. This adds a handful of new commandline options (--addmode, --delmode, --newmode, --rmmode, --same-as, --set). I haven't tried them out yet though; if your system supports xrandr, test them out and report your findings.

1. -nv (2.1.1): This upgrade from 2.0.0 adds support for a variety of new G80-based video cards. If you have one of these newer cards, please see if this improves things. I am thinking about SRUing this for Feisty, but only if there are no regressions, so I've also built Feisty debs. It is _really important_ that there be no regressions compared with 2.0.0 for Feisty users, so if you have a Feisty box to test on, please, please install the Feisty deb and report any regression of behavior compared with 2.0.0.

2. -evdev (1.1.5-2ubuntu2): The Pepper project have shared a patch that they describe as giving better support for touchscreen calibrations. I don't have a touchscreen so am not sure what difference it makes; if you do, give it a shot and tell me what you think of it.

3. xorg-server (2:1.3.0.0.dfsg-6ubuntu1): This is a small sync with Debian. I've also added a patch for the ubuntu-mobile folks to help clipping behavior with compositing. I'm not sure how relevant this patch is for non-embedded systems, but would appreciate confirmation that this package update doesn't incur any regressions.

4. mesa (7.0.0): This is already uploaded to gutsy, but I haven't heard much feedback so far. This is mostly a bug fix release, but also adds newer OpenGL support. I'd love to hear if this makes any difference for Linux gamers.

5. fglrx-8.37.6-Feisty: This is actually not scheduled for upload, but wanted to make sure to mention it for any ATI users that have been having troubles. This is a pretty significant upgrade from fglrx 8.34 and fixes a few pretty serious bugs, so if you have had trouble with fglrx (esp. when changing consoles or logging out), and are on Feisty, this package is for you. (There's a 8.38.6 out - anyone know if it's a big improvement over 8.37.6? I .)

Keep in mind when testing these that the things to look for are CHANGES (good or bad) in behavior compared with the previous version. There will still be plenty of bugs in these, we just need to check a) do the things they promise to fix, actually work better? and b) are there any NEW (confirmed and reproduceable) bugs that appear, that weren't in the previous version?

Again, help in testing the above packages will be much appreciated. I know from my experience in other open source projects like Inkscape that a good testing community can make a huge difference in improving quality, and it would kick *** if we could do the same for Ubuntu's Xorg.

Bryce Harrington
bryce@ubuntu.com

tim.lawrenz

July 3rd, 2007, 04:32 AM

Hi Bryce,

I have an asus r2h with a touchscreen that I got calibrated on feisty using the evtouch drivers. I will test the evdev package on gutsy within the next days.

Kind regards,
Tim Lawrenz

23meg

July 3rd, 2007, 08:49 AM

I'm moving this to the new Dev Link forum, with a redirect in the main forum.

I'll do the tests within a few days when I make a fresh Gutsy install.

Miguel

July 3rd, 2007, 09:45 AM

Hi Bryce,

According to phoronix, 8.38.6 doesn't have many improvements. You might be interested to know that ATi has released a "new" version of fglrx, 8.38.7. It has only one change, but it might be important (especially for X1000 series users). If one issues

aticonfig --initial

in 8.38.6 whith root privileges and it's using the vesa driver, aticonfig will segfault *and* destroy the existing /etc/X11/xorg.conf file. By the way, I'm having some issues with Gusty Tribe 2 on my laptop (bugs 122652 and 123712). I don' know if I would still qualify for testing, since one bug keeps me from DRI (mesa 7 testing) and the other gives me a basically unusable screen with the free drivers.

Miguel

July 3rd, 2007, 09:47 AM

Heck, I didn't see an edit button. I just wanted to ask what is the preferred method of testing. A clean install or a dist-upgrade from Feisty?

ShirishAg75

July 3rd, 2007, 10:03 AM

I'm no developer, just a user but I would say a clean install is the preferred way.

HymnToLife

July 3rd, 2007, 10:51 AM

Running your xserver-xorg-core right now with no problem. I see no difference with the old one except maybe a bit shorter X startup time...

yelo3

July 3rd, 2007, 12:18 PM

about the MESA update in gutsy. I have a radeon 9700 the performance has increased a bit, and now starting google earth will not hang the system

I hope that the new fglrx 8.38 will come in gutsy to see if switchin users will crash everything, as in version 8.37

bryceharrington

July 3rd, 2007, 04:10 PM

Miguel, both approaches (upgrading from Feisty and installing clean via Tribe or similar) are worth testing from, since we'll have users coming to Gutsy from both directions. For many packages it shouldn't matter either way. Where it tends to make a difference is when regenerating your xorg.conf (such as via apt-get reconfigure, dexconf, or similar), and sometimes if you have legacy drivers or libraries hanging around.

Testing from a clean install is probably the easiest, and will result in the most easily reproduceable bug reports. Next best would be to install a clean Feisty, (optionally do an update,) and then directly upgrade to Gutsy, as this allows for testing the upgrade process itself. A system that has been running Feisty for some time may have 3rd party packages, config customizations, etc. that may make bug reproduction difficult.

yelo3, thanks, that confirms other reports that new mesa results in some speed improvements. Good to hear google earth is more stable, I'd seen reports of problems there. I'll encourage the google earth users to try this now.

HymnToLife, thanks for confirming xorg-server is good, I will proceed with rolling it out.

Thanks everyone!
Bryce

bryceharrington

July 3rd, 2007, 04:33 PM

Miguel, thanks for the heads up on fglrx 8.38.6. I think I'll focus on some of the other drivers that have higher priority updates available for the near term, but I'd love to hear more feedback on 8.38.* improvements and issues if anyone tests it by hand.

yelo3

July 3rd, 2007, 05:42 PM

Google earth users that are using a radeon should enable in driconf the option "disable low impact fallback" if the performance is 1fps and they see warning messages about missing implementation of r300 something

yelo3

July 4th, 2007, 01:23 PM

Any package for radeon r300 series, to have a better compiz? it is so slow now... Does someone know if GIT version of the drivers will fix the slowness issue?

zanazzi

July 6th, 2007, 06:50 PM

I'd be happy to help if i can, but im new to linux, ran fiest for 4ish months b4 this

I installed gusty a few days ago and dont have anything on this box to loose.

feel free to pm me if i can help.

maniacmusician

July 6th, 2007, 10:21 PM

I'd be happy to help if i can, but im new to linux, ran fiest for 4ish months b4 this

I installed gusty a few days ago and dont have anything on this box to loose.

feel free to pm me if i can help.
There's nothing to PM you about, sir. The directions are in the first post. Bryce would just like you to test those packages and give feedback on how they work. if you feel you're not far enough along to do this, then by all means, refrain from doing so. But if you think you can handle it, please try testing those packages (by installing them on your computer, one by one) and giving some feedback.

ButteBlues

July 6th, 2007, 10:24 PM

Any chance of you getting updated radeon driver?

67GTA

July 7th, 2007, 02:46 AM

bryceharrington

July 9th, 2007, 06:19 AM

Hi all,

Just one new thing to test today (see below). Also, I'm working on a significant update for the xorg package which I will very much need your help testing - I am implementing a new 'bulletproof-x' mode (see http://people.ubuntu.com/~bryce/BulletProofX/ for a preview from a few weeks back). The basic implementation in X and gdm was all pretty straightforward, but to get it to be truly bulletproof is going to require lots of testing on a wide variety of hardware. However, if this can be done, this may be one of Gutsy's big advancements - monitor detection failures are one of the most noticeable, most commented on flaws for Ubuntu, so this is an area Xorg can really benefit from a failsafe fallback.

I'd like to underline maniacmusician's point, which I'm very glad he made. This new X test community definitely needs lots of new folks, but at the same time we need to take a lot of care to make sure we don't inadvertantly incite people into falling into unrecoverable situations. Testing X things is pretty easy, but has a high risk factor of things going terribly wrong, in which case you'll need to have adequate X and/or dpkg skills to restore your system. If you're not yet comfortable operating on the console, you may want to wait on testing until you've gained more skill, or set up a second box you can just do a reinstall on if things go too badly. I will try to always remember to point out things which especially high risk, but everything mentioned on this thread will probably be at least a little dangerous.

The past few weeks the focus has been on getting drivers up to date, and by and large most drivers have received at least one update. I am going to try focusing on getting other X bits updated, but may slip in more driver updates where needed. I don't want this thread to devolve into simply a place to request updates since there are better places for that, so instead, please if you make a request for an update be sure to explain in detail WHY the update is needed from the context of fixing regressions or serious bugs.

The new thing to test today is the Nvidia binary driver, available at http://people.ubuntu.com/~bcollins/lrm-feisty-nvidia-100/. Note that nvidia has changed their numbering scheme; the prior version in Gutsy is 9755. Please see http://www.nvidia.com/object/linux_display_ia32_100.14.11%20.html for a list of changes. For testing, a) check the improvements in the driver interaction with the ACPI daemon, b) check to see if console restore issues in the prior version of the driver can be reproduced on your system (using 'vesa', network LCD displays, etc.) and that they are resolved in this new one, c) if you have an nVidia 7050 or 7025, please check that your card is now supported, d) look hard for any regressions compared with the 9755 version.

I will be maintaining a list of recent-changes for Xorg at https://wiki.ubuntu.com/XorgRecentChanges. Things towards the top of that list are good candidates for testing; stuff towards the end of the list have presumably already been tested, but you might care to take a look at them as well.

bryceharrington

July 9th, 2007, 06:54 AM

A couple other notes -- make sure to reboot after installing new kernel modules, and take care if you have manually installed drivers on your system; these will need to be manually removed before installing new linux-restricted-modules stuff. Also any changes to DISABLED_MODULES will need to be undone.

DeeZiD

July 9th, 2007, 08:09 AM

THX,
I will test the bulletproof-X-system this evening :)
The integration of the newest nvidia drivers sounds interesting, too.

regards Dennis

bryceharrington

July 9th, 2007, 10:14 AM

There is also a new version 2.1.0 intel driver uploaded to gutsy last week, which could use testing. If you've run into issues with -intel previously, please re-test against this new driver and report if they've been resolved. A full list of changes for this is at: https://wiki.ubuntu.com/XorgRecentChanges

Particular highlights include new support for G33, Q33, and Q35, feature work for CRTC, LVDS, and IVCH, and various fixups for i810, i965, and more.

kingof1981

July 12th, 2007, 07:21 PM

hello guy's...
i'm running the new kernel (2.6.22-8.16) and xserver-xorg-core (2:1.3.0.0.dfsg-4ubuntu2)...
both is working well now...
but i don't like that kdm keeps changing the refresh rate...
naja...

SubGothius

July 16th, 2007, 11:09 PM

I just did a clean netboot-install of the latest Gutsy beta on my "OldWorld" PowerMac clone with a correspondingly-ancient IMS/ixMicro TwinTurbo 128+ PCI video card. Everything seemed to go amazingly well, until...

At first X failed to start due to error "imstt(0): no valid modes found" (same problem I had with a recent Debian Lenny testing install), both with the as-installed xorg.conf (and various tweaks thereof) and also subsequently with a known-working xorg.conf I'd saved from Feisty.

However, researching that type of error I ran across some mention of the new Xorg having more autodetect/autoconfig and no longer relying on xorg.conf (at all?), so deleting the xorg.conf file entirely (actually renamed it, just in case ;)) allowed X to start up for me in the latest Gutsy. Not clear yet if I have full graphics accelleration or even what resolution or depth I have (at least 800x600@16bit, maybe even 1024x768@24 I hope?), as there are no selections in the Xfce Monitor setting panel and no obvious way I know of to echo what the current display settings are, but at least Gutsy installed and X is nominally working on my ancient Mac clone! \\:D/

Miguel

July 20th, 2007, 12:46 PM

So you know, I've just installed Tribe 3 (from update-manager) and will try to test it this week-end as thorough as possible with standard packages. One thing that puzzles me though is that from a dist-upgrade, my ATi Mobility Radeon 9600 does have DRi by default, while it didn't have it in either Tribe 2 or the daily CD I burnt last friday. I'm not complaining, though.

msdark

July 24th, 2007, 03:34 AM

SubGothius

July 25th, 2007, 08:23 PM

After running a 'sudo aptitude update && aptitude upgrade', now my X won't start at all, saying something about the vesa driver module not found. So apparenly mv'ing my xorg.conf earlier had forced Xorg to fall back to the generic vesa driver, but now it can't use or even find that? FWIW, restoring my xorg.conf file resulted in the same error as earlier: "imstt(0): no valid modes found"

bryceharrington

July 26th, 2007, 03:15 AM

SubGothius, unfortunately this is a testing thread rather than a troubleshooting thread, and I suspect you're looking for the latter more than the former, so I would encourage you NOT to follow advice in this thread (unless of course it solves your issue!) Instead, I would suggest looking to answers.ubuntu.com or similar for tech support.

Miguel

August 3rd, 2007, 12:38 PM

Hi bryce,

I'm starting my holidays in a couple of hours and will have more time for testing. Now that I have solved my issues with tty[1-6] I'm free to test basically anything ati/fglrx you want. I hope it's not too little and too late. Do you want me to do some bulletproof-X testing?

jbernardo

August 10th, 2007, 05:14 AM

ShirishAg75

August 13th, 2007, 12:53 PM

I know this is a testing thread & some things aren't in their proper places or dunno what happened to those packages. Taken from http://people.ubuntu.com/~bryce/Testing/xorg-server/README

xorg-server-1.3.0.0.dfsg-6ubuntu1

Overview
--------
This is a sync to debian, with the addition of an apport hook.

Installation
------------
Warning: Please ONLY install on non-production test systems

Base Packages
dpkg -i xserver-xorg-core_1.3.0.0.dfsg-6ubuntu1_i386.deb
dpkg -i xserver-xorg-core-dbg_1.3.0.0.dfsg-6ubuntu1_i386.deb
dpkg -i xserver-xorg-dev_1.3.0.0.dfsg-6ubuntu1_i386.deb

Additional Packages
dpkg -i xdmx_1.3.0.0.dfsg-6ubuntu1_i386.deb
dpkg -i xdmx-tools_1.3.0.0.dfsg-6ubuntu1_i386.deb
dpkg -i xnest_1.3.0.0.dfsg-6ubuntu1_i386.deb
dpkg -i xvfb_1.3.0.0.dfsg-6ubuntu1_i386.deb
dpkg -i xserver-xephyr_1.3.0.0.dfsg-6ubuntu1_i386.deb

WARNING: I could install these next two, but couldn't revert
them easily
dpkg -i xprint-common_1.3.0.0.dfsg-6ubuntu1_all.deb
dpkg -i xprint_1.3.0.0.dfsg-6ubuntu1_i386.deb

Reversion
---------
apt-get install xserver-xorg-core=2:1.3.0.0.dfsg-4ubuntu
apt-get install xserver-xorg-core-dbg=2:1.3.0.0.dfsg-4ubuntu
apt-get install xserver-xorg-dev=2:1.3.0.0.dfsg-4ubuntu
apt-get install xserver-xorg-dev=2:1.3.0.0.dfsg-4ubuntu
apt-get install xnest=2:1.3.0.0.dfsg-4ubuntu2
apt-get install xvfb=2:1.3.0.0.dfsg-4ubuntu2
apt-get install xserver-xephyr/feisty

# xprint, xprint-common: Was unable to revert these

Now while I can see the base-packages at http://people.ubuntu.com/~bryce/Testing/xorg-server/

but can't see the additional packages, also there is an mdetect folder, but nothing in it :(

Can somebody enlighten me about it?

bryceharrington

August 13th, 2007, 07:35 PM

The missing things have already been uploaded into Gutsy. I left the README since it's likely I'll have more xorg / xorg-server packages ready for testers.

For testers with Radeon systems, we've just uploaded a new -ati driver a few days ago into Gutsy, 1:6.6.193-1ubuntu1. What we're looking for is if there are new regressions not present in the prior driver (Feisty's 1:6.6.3-2 driver). Note that there are a lot of known issues with the prior -ati that are unfortunately still true with this one, so please make sure to check the bug tracker before reporting issues, and add problem reports to existing bugs.

Bryce

Miguel

August 14th, 2007, 12:53 PM

Bryce,

Where is the 6.6.193 driver supposed to be? I've got an up to date gutsy and the latest I've seen is 6.6.3-2ubuntu6. I am very interested on testing .193, since I really despise fglrx.

By the way, fglrx v. 8.40.4 has been released, with a phoronix codename of "One bug a day keeps AIGLX away". I'm not really into testing it, unless you will be pushing it into gutsy.

bryceharrington

August 14th, 2007, 04:37 PM

Hi Miguel,

xserver-xorg-video-ati 1:6.6.193-1ubuntu1 was uploaded this last weekend, so you should be able to update and start testing it now. :-)

Btw, we've also been looking at the -ati xrandr 1.2 branch, as it sounds pretty cool. However we are concerned it may have too many regressions for Gutsy. But we may package a .deb just for testers here to play with.

Speaking of which - those of you with Intel graphics cards, there is something you can test right now. Gutsy is upgraded to xrandr 1.2, which means you can hot plug monitors and projectors. If you have an intel laptop and a projector, this means you can plug the projector into the laptop without having to restart it, and it should "just work". Further, you can use xrandr to customize the screens (see man xrandr for details).

Note that xrandr is not compatible with Xinerama, and in fact is going to replace Xinerama. So another thing worth testing is multi-monitor displays.

Oh, another cool new thing - displayconfig-gtk is now promoted to main, and is in the desktop seed, so it will be installed by default. In addition to configuring the screen and drivers, it can also handle doing basic dual-screen setups using xrandr. This tool should show up now in your System:Administration menu as "Screen and Device". If not, let us know. Please bang on it and make sure any serious issues are recorded in launchpad for displayconfig-gtk.

DeeZiD

August 14th, 2007, 04:53 PM

@Bryce:
One question.
Will the 100.xx-series NVIDIA driver be included in gutsy?
8xxx series out of the box would be great :popcorn:

regards Dennis

DeeZiD

August 14th, 2007, 04:58 PM

And one suggestion!

PLEASE, Please, please remove the 'Subsection "Display"' from xorg.conf!
It doesn't seem to be necessary right now. :)
If I remove this section I always get the right resolution :KS

Ubuntu even recognize my TFT (1680x1050) and my ASUS notebooks (1440x900) display wrong.

Xorg (nv driver) or nvidia do it right. ;)

(sorry for my bad english :D)
regards Dennis

Miguel

August 14th, 2007, 06:32 PM

xserver-xorg-video-ati 1:6.6.193-1ubuntu1 was uploaded this last weekend, so you should be able to update and start testing it now. :-)

I've just updated my sources and, voila!, -ati 6.6.193 is on the upgrade list. Until now I only saw some source packages in launchpad by Timo Aaltonen, IIRC, but I'm wet behind the ears when it comes to anything other than bug reporting in launchpad. Teesting!!!! Teeesting!!!

Btw, we've also been looking at the -ati xrandr 1.2 branch, as it sounds pretty cool. However we are concerned it may have too many regressions for Gutsy. But we may package a .deb just for testers here to play with.

I'd really love it. You don't happen to be in Spain, do you? I could try to bribe you with a beer or two.

jbernardo

August 15th, 2007, 02:53 AM

Does this repo have the patch "120_fedora_disable_offscreen_pixmaps.diff" removed, as per bug 126425 (https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/126425), so that we can use EXA acceleration with Intel drivers?

I assume that xserver-xorg-core still has this patch applied?

Another thing, I didn't have displayconfig-gtk installed, but maybe that is because I am running kubuntu; after installing, it doesn't show up in kubuntu's menus.

ShirishAg75

August 15th, 2007, 04:02 AM

Bryce,
If you uploaded the remaining stuff, where did you upload them? In http://people.ubuntu.com/~bryce/Testing/xorg-server/ I just see the xorg stuff, the remaining stuff (Additional packages) is where, can you help pinpoint?

Miguel

August 15th, 2007, 06:09 AM

Hi Bryce,

I've got some good news for you. Although I had some hard locks yesterday night, a simple Device section works OK, so all the issues I had might be related to weird options (like fastwrite and all). Anyway, I no longer see the horizontal lines in bug #122652.
deleting /etc/X11/xorg.conf and restarting X gives a fully functional 1280x800 screen
3D performance seems pretty good, although further tests are needed.
fglrx is no longer installed on my system. MUAHAHAHAHA!!!!!

ButteBlues

August 15th, 2007, 06:36 AM

I've also noticed a huge performance surge on my old ATI Mobility 7500 with the new ati driver.

bryceharrington

August 15th, 2007, 08:53 PM

DeeZiD: I'll take a look at updating the nvidia driver. Regarding removing the display section, I'm striving to be a bit conservative here. While removing it may make things better for many of us, I know it could cause new failures for some users who require it to be present.

Miguel: Sorry, I'm in the US, but thanks for the beering offer. :-) That's great to hear that the -ati driver is working so much better for everyone. If anyone has some time, it would be quite helpful if you could look through the lauchpad bugs for the -ati driver and report on any bugs you've experienced previously that are now fixed with this latest driver.

ShirishAg75: By 'upload' I mean upload to gutsy. So you can get the packages via packages.ubuntu.com, or via update-manager/synaptic/apt-get.

bryceharrington

August 17th, 2007, 04:29 AM

Hi all,

Two new drivers in need of testing: The nvidia 100.14.11 and fglrx 8.40.4 binary drivers:

http://people.ubuntu.com/~bryce/Testing/linux-restricted-modules/

These need to be thoroughly tested before we can upload them, since it's now after feature freeze, and since these are pretty significant upgrades from what's currently in Gutsy. However, if you all can help validate that the drivers work well, resolve issues or improve things from the previous version, and have few or no regressions, we may be able to justify having an exception made for them.

A list of changes for both drivers is available in the .changes file.

One thing I notied, is with the fglrx driver, the panel applet is gone, having been replaced with the CCC; I don't know much about this, and am not sure it's included in these packages. If not, let me know and I'll work on getting it properly packaged.

Other things newly uploaded today include a xorg package including the new Bulletproof-X feature, and an update for mesa bringing it to version 7.0.1. Mesa 7.0.1 has numerous bug-fixes, so if you know of any mesa-related issues, it would be great if you could do an update and then test this new version to see if it's resolved.

Bryce

yelo3

August 17th, 2007, 06:37 AM

Unfortunately the fglrx in gutsy introduces a bug in comparison to the one that is in feisty:
After log out or switch users, the system hangs.
I tried the 8.40 from ati site, but still has this problem. Did you introdice any patch in this version you are offering here?

mabovo

August 17th, 2007, 07:39 AM

The free driver for ATI doesn't work with my ATI Radeon 9550 (256MB), i testing Gutsy Tribe 3 now.
I tested the official driver for ati, i mean, fglrx 8.38.7 version and works a litle, but the XGL session works 100% unstable, i mean, when i use the XGL session, the systema works for a littel random time, sometimes 10 min, sometimes only 1 minute... and the screen freeze, and i have nothing to do, only restart the system pushing the button.

The Xorg 7.3 dont work for me, i mean, dont recognize my ATI.

When i look the xorg.conf in the device section put ati for driver, but the grafics doesn't start, i only see a black screen.

I want to test more... if you have a package to test with ati user.... i want this package

(sorry for my english is not my native language i speak spanish)

Saludos!!!!

Ola MsDark!

Tienes noticiado acerca dela nueva atualizacion del driver fglrx por parte de ATI ? (version 8.40.4)

I'd like to know if You dare to test this new release on Ubuntu Gutsy Trube 4.

I have a Radeon 9600 and tested driver 8.39.4 with Tribe 3 and all X messed. I discover that had some problems with USB devices mouse and keyboard disabled when X started and a black screen shows up.

I really want to know if this new driver can cope with Xorg 7.3 but in the ATI site they inform this driver has compatibility with Xorg 7.2 and the installation instructions are for Feisty and not for Gutsy.

Gracias.

mabovo

August 17th, 2007, 10:28 PM

Well, I did it. Installed all debs in the http://people.ubuntu.com/~bryce/Testing/linux-restricted-modules/

Here is my Xorg.0.log

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu
Current Operating System: Linux linux-ubuntu 2.6.22-9-386 #1 Fri Aug 3 00:21:52 GMT 2007 i686
Build Date: 26 July 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
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: Fri Aug 17 23:22:54 2007
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "SyncMaster"
(**) | |-->Device "ATI Technologies Inc RV350 AR [Radeon 9600]"
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(**) |-->Input Device "stylus"
(**) |-->Input Device "cursor"
(**) |-->Input Device "eraser"
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/cyrillic,
/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
(==) RgbPath set to "/etc/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(**) Extension "Composite" is disabled
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x81e5980
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 1.2
X.Org XInput driver : 0.7
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1106,0282 card 1043,80a3 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:00:1: chip 1106,1282 card 0000,0000 rev 00 class 06,00,00 hdr 00
(II) PCI: 00:00:2: chip 1106,2282 card 0000,0000 rev 00 class 06,00,00 hdr 00
(II) PCI: 00:00:3: chip 1106,3282 card 0000,0000 rev 00 class 06,00,00 hdr 00
(II) PCI: 00:00:4: chip 1106,4282 card 0000,0000 rev 00 class 06,00,00 hdr 00
(II) PCI: 00:00:7: chip 1106,7282 card 0000,0000 rev 00 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1106,b188 card 0000,0000 rev 00 class 06,04,00 hdr 01
(II) PCI: 00:0b:0: chip 109e,036e card 0000,0000 rev 11 class 04,00,00 hdr 80
(II) PCI: 00:0b:1: chip 109e,0878 card 0000,0000 rev 11 class 04,80,00 hdr 80
(II) PCI: 00:0d:0: chip 10b7,9200 card 10b7,1000 rev 74 class 02,00,00 hdr 00
(II) PCI: 00:0e:0: chip 1102,0002 card 1102,8040 rev 05 class 04,01,00 hdr 80
(II) PCI: 00:0e:1: chip 1102,7002 card 1102,0020 rev 05 class 09,80,00 hdr 80
(II) PCI: 00:0f:0: chip 1106,3149 card 1043,80ed rev 80 class 01,04,00 hdr 80
(II) PCI: 00:0f:1: chip 1106,0571 card 1043,80ed rev 06 class 01,01,8a hdr 00
(II) PCI: 00:10:0: chip 1106,3038 card 1043,80ed rev 81 class 0c,03,00 hdr 80
(II) PCI: 00:10:1: chip 1106,3038 card 1043,80ed rev 81 class 0c,03,00 hdr 80
(II) PCI: 00:10:2: chip 1106,3038 card 1043,80ed rev 81 class 0c,03,00 hdr 80
(II) PCI: 00:10:3: chip 1106,3038 card 1043,80ed rev 81 class 0c,03,00 hdr 80
(II) PCI: 00:10:4: chip 1106,3104 card 1043,80ed rev 86 class 0c,03,20 hdr 80
(II) PCI: 00:11:0: chip 1106,3227 card 1043,80ed rev 00 class 06,01,00 hdr 80
(II) PCI: 00:11:5: chip 1106,3059 card 1043,810d rev 60 class 04,01,00 hdr 00
(II) PCI: 00:11:6: chip 1106,3068 card 0000,0000 rev 80 class 07,80,00 hdr 00
(II) PCI: 00:12:0: chip 1106,3065 card 1043,80ed rev 78 class 02,00,00 hdr 00
(II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 01:00:0: chip 1002,4152 card 148c,2079 rev 00 class 03,00,00 hdr 80
(II) PCI: 01:00:1: chip 1002,4172 card 148c,2078 rev 00 class 03,80,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000a (VGA_EN is set)
(II) Bus 1 I/O range:
[0] -1 0 0x0000e000 - 0x0000efff (0x1000) IX[B]
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xfbd00000 - 0xfbffffff (0x300000) MX[B]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xd0000000 - 0xfaffffff (0x2b000000) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:17:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI: (0:11:0) Brooktree Corporation Bt878 Video Capture rev 17, Mem @ 0xcbe00000/12
(--) PCI:*(1:0:0) ATI Technologies Inc RV350 AR [Radeon 9600] rev 0, Mem @ 0xd0000000/28, 0xfbe00000/16, I/O @ 0xe000/8, BIOS @ 0xfbd00000/17
(--) PCI: (1:0:1) ATI Technologies Inc RV350 AR [Radeon 9600] (Secondary) rev 0, Mem @ 0xe0000000/28, 0xfbf00000/16
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) PCI Memory resource overlap reduced 0xcc000000 from 0xcfffffff to 0xcbffffff
(II) Active PCI resource ranges:
[0] -1 0 0xfb800000 - 0xfb8000ff (0x100) MX[B]
[1] -1 0 0xfb900000 - 0xfb9000ff (0x100) MX[B]
[2] -1 0 0xfbc00000 - 0xfbc0007f (0x80) MX[B]
[3] -1 0 0xcbf00000 - 0xcbf00fff (0x1000) MX[B]
[4] -1 0 0xcc000000 - 0xcbffffff (0x0) MX[B]O
[5] -1 0 0xfbf00000 - 0xfbf0ffff (0x10000) MX[B](B)
[6] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[7] -1 0 0xfbd00000 - 0xfbd1ffff (0x20000) MX[B](B)
[8] -1 0 0xfbe00000 - 0xfbe0ffff (0x10000) MX[B](B)
[9] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[10] -1 0 0xcbe00000 - 0xcbe00fff (0x1000) MX[B](B)
[11] -1 0 0x00009400 - 0x000094ff (0x100) IX[B]
[12] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]
[13] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]
[14] -1 0 0x0000a800 - 0x0000a81f (0x20) IX[B]
[15] -1 0 0x0000a400 - 0x0000a41f (0x20) IX[B]
[16] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[17] -1 0 0x00009800 - 0x0000981f (0x20) IX[B]
[18] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B]
[19] -1 0 0x0000b000 - 0x0000b0ff (0x100) IX[B]
[20] -1 0 0x0000b400 - 0x0000b40f (0x10) IX[B]
[21] -1 0 0x0000b800 - 0x0000b803 (0x4) IX[B]
[22] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[B]
[23] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[B]
[24] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[25] -1 0 0x0000d400 - 0x0000d407 (0x8) IX[B]
[26] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[27] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]
[28] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B](B)
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xfb800000 - 0xfb8000ff (0x100) MX[B]
[1] -1 0 0xfb900000 - 0xfb9000ff (0x100) MX[B]
[2] -1 0 0xfbc00000 - 0xfbc0007f (0x80) MX[B]
[3] -1 0 0xcbf00000 - 0xcbf00fff (0x1000) MX[B]
[4] -1 0 0xcc000000 - 0xcbffffff (0x0) MX[B]O
[5] -1 0 0xfbf00000 - 0xfbf0ffff (0x10000) MX[B](B)
[6] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[7] -1 0 0xfbd00000 - 0xfbd1ffff (0x20000) MX[B](B)
[8] -1 0 0xfbe00000 - 0xfbe0ffff (0x10000) MX[B](B)
[9] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[10] -1 0 0xcbe00000 - 0xcbe00fff (0x1000) MX[B](B)
[11] -1 0 0x00009400 - 0x000094ff (0x100) IX[B]
[12] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]
[13] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]
[14] -1 0 0x0000a800 - 0x0000a81f (0x20) IX[B]
[15] -1 0 0x0000a400 - 0x0000a41f (0x20) IX[B]
[16] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[17] -1 0 0x00009800 - 0x0000981f (0x20) IX[B]
[18] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B]
[19] -1 0 0x0000b000 - 0x0000b0ff (0x100) IX[B]
[20] -1 0 0x0000b400 - 0x0000b40f (0x10) IX[B]
[21] -1 0 0x0000b800 - 0x0000b803 (0x4) IX[B]
[22] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[B]
[23] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[B]
[24] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[25] -1 0 0x0000d400 - 0x0000d407 (0x8) IX[B]
[26] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[27] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]
[28] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B](B)
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfb800000 - 0xfb8000ff (0x100) MX[B]
[5] -1 0 0xfb900000 - 0xfb9000ff (0x100) MX[B]
[6] -1 0 0xfbc00000 - 0xfbc0007f (0x80) MX[B]
[7] -1 0 0xcbf00000 - 0xcbf00fff (0x1000) MX[B]
[8] -1 0 0xcc000000 - 0xcbffffff (0x0) MX[B]O
[9] -1 0 0xfbf00000 - 0xfbf0ffff (0x10000) MX[B](B)
[10] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[11] -1 0 0xfbd00000 - 0xfbd1ffff (0x20000) MX[B](B)
[12] -1 0 0xfbe00000 - 0xfbe0ffff (0x10000) MX[B](B)
[13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[14] -1 0 0xcbe00000 - 0xcbe00fff (0x1000) MX[B](B)
[15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[17] -1 0 0x00009400 - 0x000094ff (0x100) IX[B]
[18] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]
[19] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]
[20] -1 0 0x0000a800 - 0x0000a81f (0x20) IX[B]
[21] -1 0 0x0000a400 - 0x0000a41f (0x20) IX[B]
[22] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[23] -1 0 0x00009800 - 0x0000981f (0x20) IX[B]
[24] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B]
[25] -1 0 0x0000b000 - 0x0000b0ff (0x100) IX[B]
[26] -1 0 0x0000b400 - 0x0000b40f (0x10) IX[B]
[27] -1 0 0x0000b800 - 0x0000b803 (0x4) IX[B]
[28] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[B]
[29] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[B]
[30] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[31] -1 0 0x0000d400 - 0x0000d407 (0x8) IX[B]
[32] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[33] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]
[34] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B](B)
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(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.3.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(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.3.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules//fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.3.0, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "type1"
(II) Loading /usr/lib/xorg/modules//fonts/libtype1.so
(II) Module type1: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.2
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Type1
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(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.3.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 7.1.0, module version = 8.40.4
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.0
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.2.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.7
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.2.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.7
(II) LoadModule: "wacom"
(II) Loading /usr/lib/xorg/modules/input//wacom_drv.so
(II) Module wacom: vendor="X.Org Foundation"
compiled for 4.3.99.902, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.7
(II) Wacom driver level: 47-0.7.7-7 $
(II) Primary Device is: PCI 01:00:0
(II) ATI Proprietary Linux Driver Version Identifier:8.40.4
(II) ATI Proprietary Linux Driver Release Identifier: UNSUPPORTED-8.402
(II) ATI Proprietary Linux Driver Build Date: Jul 31 2007 22:20:14
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(--) Chipset Supported AMD Graphics Processor (0x4152) found
(II) AMD Video driver is running on a device generally supported by this driver
(II) No signature file
(II) AMD Video driver is unsigned
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfb800000 - 0xfb8000ff (0x100) MX[B]
[5] -1 0 0xfb900000 - 0xfb9000ff (0x100) MX[B]
[6] -1 0 0xfbc00000 - 0xfbc0007f (0x80) MX[B]
[7] -1 0 0xcbf00000 - 0xcbf00fff (0x1000) MX[B]
[8] -1 0 0xcc000000 - 0xcbffffff (0x0) MX[B]O
[9] -1 0 0xfbf00000 - 0xfbf0ffff (0x10000) MX[B](B)
[10] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[11] -1 0 0xfbd00000 - 0xfbd1ffff (0x20000) MX[B](B)
[12] -1 0 0xfbe00000 - 0xfbe0ffff (0x10000) MX[B](B)
[13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[14] -1 0 0xcbe00000 - 0xcbe00fff (0x1000) MX[B](B)
[15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[17] -1 0 0x00009400 - 0x000094ff (0x100) IX[B]
[18] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]
[19] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]
[20] -1 0 0x0000a800 - 0x0000a81f (0x20) IX[B]
[21] -1 0 0x0000a400 - 0x0000a41f (0x20) IX[B]
[22] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[23] -1 0 0x00009800 - 0x0000981f (0x20) IX[B]
[24] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B]
[25] -1 0 0x0000b000 - 0x0000b0ff (0x100) IX[B]
[26] -1 0 0x0000b400 - 0x0000b40f (0x10) IX[B]
[27] -1 0 0x0000b800 - 0x0000b803 (0x4) IX[B]
[28] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[B]
[29] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[B]
[30] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[31] -1 0 0x0000d400 - 0x0000d407 (0x8) IX[B]
[32] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[33] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]
[34] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B](B)
(II) fglrx(0): pEnt->device->identifier=0x8204d98
(II) resource ranges after probing:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfb800000 - 0xfb8000ff (0x100) MX[B]
[5] -1 0 0xfb900000 - 0xfb9000ff (0x100) MX[B]
[6] -1 0 0xfbc00000 - 0xfbc0007f (0x80) MX[B]
[7] -1 0 0xcbf00000 - 0xcbf00fff (0x1000) MX[B]
[8] -1 0 0xcc000000 - 0xcbffffff (0x0) MX[B]O
[9] -1 0 0xfbf00000 - 0xfbf0ffff (0x10000) MX[B](B)
[10] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[11] -1 0 0xfbd00000 - 0xfbd1ffff (0x20000) MX[B](B)
[12] -1 0 0xfbe00000 - 0xfbe0ffff (0x10000) MX[B](B)
[13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[14] -1 0 0xcbe00000 - 0xcbe00fff (0x1000) MX[B](B)
[15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[19] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[20] -1 0 0x00009400 - 0x000094ff (0x100) IX[B]
[21] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]
[22] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]
[23] -1 0 0x0000a800 - 0x0000a81f (0x20) IX[B]
[24] -1 0 0x0000a400 - 0x0000a41f (0x20) IX[B]
[25] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[26] -1 0 0x00009800 - 0x0000981f (0x20) IX[B]
[27] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B]
[28] -1 0 0x0000b000 - 0x0000b0ff (0x100) IX[B]
[29] -1 0 0x0000b400 - 0x0000b40f (0x10) IX[B]
[30] -1 0 0x0000b800 - 0x0000b803 (0x4) IX[B]
[31] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[B]
[32] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[B]
[33] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[34] -1 0 0x0000d400 - 0x0000d407 (0x8) IX[B]
[35] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[36] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]
[37] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B](B)
[38] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[39] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) fglrx(0): === [atiddxPreInit] === begin, [x]
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 1.2
(II) fglrx(0): PCI bus 1 card 0 func 0
(**) fglrx(0): Depth 24, (--) framebuffer bpp 32
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) fglrx(0): Default visual is TrueColor
(**) fglrx(0): Option "DPMS"
(==) fglrx(0): RGB weight 888
(II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
(==) fglrx(0): Gamma Correction for I is 0x06419064
(==) fglrx(0): Gamma Correction for II is 0x06419064
(==) fglrx(0): Buffer Tiling is ON
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(--) fglrx(0): Chipset: "ATI RADEON 9600 Series" (Chipset = 0x4152)
(--) fglrx(0): (PciSubVendor = 0x148c, PciSubDevice = 0x2079)
(--) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI
(--) fglrx(0): Linear framebuffer (phys) at 0xd0000000
(--) fglrx(0): MMIO registers at 0xfbe00000
(==) fglrx(0): ROM-BIOS at 0x000c0000
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.1.0
ABI class: X.Org Video Driver, version 1.2
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 2.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
(II) fglrx(0): VESA VBE OEM: ATI RADEON 9600 PRO
(II) fglrx(0): VESA VBE OEM Software Rev: 1.0
(II) fglrx(0): VESA VBE OEM Vendor: ATI Technologies Inc.
(II) fglrx(0): VESA VBE OEM Product: V350
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmGetBusid returned ''
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
compiled for 7.1.0, module version = 8.40.4
ABI class: X.Org Server Extension, version 0.3
(--) fglrx(0): VideoRAM: 131072 kByte, Type: DDR SGRAM / SDRAM
(II) fglrx(0): AGP card detected
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module already built-in
(II) fglrx(0): Connected Display1: CRT on primary DAC [crt1]
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: SAM Model: 11f Serial#: 1296707897
(II) fglrx(0): Year: 2004 Week: 35
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
(II) fglrx(0): Sync: Separate Composite
(II) fglrx(0): Max H-Image Size [cm]: horiz.: 38 vert.: 30
(II) fglrx(0): Gamma: 2.20
(II) fglrx(0): DPMS capabilities: Off; RGB/Color Display
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): redX: 0.634 redY: 0.354 greenX: 0.304 greenY: 0.581
(II) fglrx(0): blueX: 0.143 blueY: 0.102 whiteX: 0.310 whiteY: 0.330
(II) fglrx(0): Supported VESA Video Modes:
(II) fglrx(0): 720x400@70Hz
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 640x480@67Hz
(II) fglrx(0): 640x480@72Hz
(II) fglrx(0): 640x480@75Hz
(II) fglrx(0): 800x600@56Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 800x600@72Hz
(II) fglrx(0): 800x600@75Hz
(II) fglrx(0): 832x624@75Hz
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): 1024x768@70Hz
(II) fglrx(0): 1024x768@75Hz
(II) fglrx(0): 1280x1024@75Hz
(II) fglrx(0): 1152x870@75Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) fglrx(0): #1: hsize: 1152 vsize 864 refresh: 75 vid: 20337
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 108.0 MHz Image Size: 376 x 301 mm
(II) fglrx(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
(II) fglrx(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
(II) fglrx(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
(II) fglrx(0): Monitor name: SyncMaster
(II) fglrx(0): Serial No: HCJX827952
(II) fglrx(0): EDID (in hex):
(II) fglrx(0): 00ffffffffffff004c2d1f0139314a4d
(II) fglrx(0): 230e01036c261e782a6f86a25a4d9424
(II) fglrx(0): 1a4f54bfef808180714f010101010101
(II) fglrx(0): 010101010101302a009851002a403070
(II) fglrx(0): 1300782d1100001e000000fd00384b1e
(II) fglrx(0): 510e000a202020202020000000fc0053
(II) fglrx(0): 796e634d61737465720a2020000000ff
(II) fglrx(0): 0048434a583832373935320a20200036
(II) fglrx(0): End of Display1 EDID data --------------------
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(II) fglrx(0): Primary Controller - CRT on primary DAC
(II) fglrx(0): Internal Desktop Setting: 0x00000001
(II) fglrx(0): POWERplay version 3. 4 power states available:
(II) fglrx(0): 1. 500/297MHz @ 50Hz [enable load balancing, overdrive]
(II) fglrx(0): 2. 398/297MHz @ 50Hz [enable load balancing, overdrive]
(II) fglrx(0): 3. 513/297MHz @ 50Hz [overclocked, enable load balancing, overdrive]
(II) fglrx(0): 4. 527/297MHz @ 50Hz [overclocked, enable load balancing, overdrive]
(==) fglrx(0): Qbs disabled
(==) fglrx(0): FAST_SWAP disabled
(==) fglrx(0): PseudoColor visuals disabled
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(==) fglrx(0): Center Mode is disabled
(==) fglrx(0): TMDS coherent mode is enabled
(II) fglrx(0): Total of 31 modes found for primary display.
(--) fglrx(0): Virtual size is 1280x1024 (pitch 0)
(**) fglrx(0): *Mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1280x1024" 135.00 1280 1296 1440 1688 1024 1025 1028 1066
(**) fglrx(0): Default mode "1280x1024": 128.9 MHz (scaled from 0.0 MHz), 74.6 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1280x1024" 128.94 1280 1368 1504 1728 1024 1025 1028 1066 +hsync
(**) fglrx(0): Default mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066
(**) fglrx(0): Default mode "1280x1024": 85.5 MHz (scaled from 0.0 MHz), 50.9 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024" 85.51 1280 1344 1480 1680 1024 1025 1028 1083 interlace +hsync
(**) fglrx(0): Default mode "1280x1024": 77.8 MHz (scaled from 0.0 MHz), 46.3 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024" 77.80 1280 1344 1480 1680 1024 1025 1028 1077 interlace +hsync
(**) fglrx(0): *Mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900
(**) fglrx(0): Default mode "1152x864": 96.8 MHz (scaled from 0.0 MHz), 63.0 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1152x864" 96.76 1152 1224 1344 1536 864 865 868 900 +hsync
(**) fglrx(0): Default mode "1152x864": 81.6 MHz (scaled from 0.0 MHz), 53.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 +hsync
(**) fglrx(0): Default mode "1152x864": 64.7 MHz (scaled from 0.0 MHz), 43.0 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1152x864" 64.67 1152 1208 1328 1504 864 865 868 915 interlace +hsync
(**) fglrx(0): Default mode "1152x864": 58.3 MHz (scaled from 0.0 MHz), 39.2 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1152x864" 58.28 1152 1200 1320 1488 864 865 868 911 interlace +hsync
(**) fglrx(0): *Mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1024x768" 78.75 1024 1040 1136 1312 768 769 772 800
(**) fglrx(0): Default mode "1024x768": 78.4 MHz (scaled from 0.0 MHz), 57.7 kHz, 72.0 Hz
(II) fglrx(0): Modeline "1024x768" 78.43 1024 1080 1192 1360 768 769 772 801 +hsync
(**) fglrx(0): Default mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 +hsync +vsync
(**) fglrx(0): Default mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 +hsync +vsync
(**) fglrx(0): *Mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
(II) fglrx(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625
(**) fglrx(0): Default mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.0 Hz
(II) fglrx(0): Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666
(**) fglrx(0): Default mode "800x600": 45.5 MHz (scaled from 0.0 MHz), 43.8 kHz, 70.0 Hz
(II) fglrx(0): Modeline "800x600" 45.50 800 840 920 1040 600 601 604 625 +hsync
(**) fglrx(0): Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.0 Hz
(II) fglrx(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628
(**) fglrx(0): Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.0 Hz
(II) fglrx(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625
(**) fglrx(0): *Mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
(II) fglrx(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 +hsync +vsync
(**) fglrx(0): Default mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.0 Hz
(II) fglrx(0): Modeline "640x480" 31.50 640 664 704 832 480 489 492 520 +hsync +vsync
(**) fglrx(0): Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x480" 25.18 640 656 752 800 480 490 492 525 +hsync +vsync
(**) fglrx(0): Default mode "720x576": 32.7 MHz (scaled from 0.0 MHz), 35.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "720x576" 32.66 720 744 816 912 576 577 580 597 +hsync
(**) fglrx(0): Default mode "640x400": 28.1 MHz (scaled from 0.0 MHz), 33.7 kHz, 75.0 Hz
(II) fglrx(0): Modeline "640x400" 28.07 640 696 736 832 400 413 415 449
(**) fglrx(0): Default mode "640x400": 24.9 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x400" 24.92 640 664 760 792 400 460 462 525
(**) fglrx(0): Default mode "400x300": 24.8 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "400x300" 24.75 400 408 448 528 300 601 602 625 doublescan
(**) fglrx(0): Default mode "400x300": 22.3 MHz (scaled from 0.0 MHz), 45.0 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "400x300" 22.33 400 416 480 496 300 601 605 742 doublescan
(**) fglrx(0): Default mode "320x240": 15.8 MHz (scaled from 0.0 MHz), 37.9 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "320x240" 15.75 320 328 360 416 240 481 482 501 doublescan
(**) fglrx(0): Default mode "320x240": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x240" 12.59 320 328 376 400 240 491 493 525 doublescan
(**) fglrx(0): Default mode "320x200": 13.1 MHz (scaled from 0.0 MHz), 31.5 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "320x200" 13.10 320 352 368 416 200 406 407 417 doublescan
(**) fglrx(0): Default mode "320x200": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x200" 12.59 320 336 384 400 200 457 459 524 doublescan
(--) fglrx(0): Display dimensions: (380, 300) mm
(--) fglrx(0): DPI set to (85, 86)
(--) fglrx(0): Virtual size is 1280x1024 (pitch 1280)
(**) fglrx(0): *Mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1280x1024" 135.00 1280 1296 1440 1688 1024 1025 1028 1066
(**) fglrx(0): Default mode "1280x1024": 128.9 MHz (scaled from 0.0 MHz), 74.6 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1280x1024" 128.94 1280 1368 1504 1728 1024 1025 1028 1066 +hsync
(**) fglrx(0): Default mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066
(**) fglrx(0): Default mode "1280x1024": 85.5 MHz (scaled from 0.0 MHz), 50.9 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024" 85.51 1280 1344 1480 1680 1024 1025 1028 1083 interlace +hsync
(**) fglrx(0): Default mode "1280x1024": 77.8 MHz (scaled from 0.0 MHz), 46.3 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1280x1024" 77.80 1280 1344 1480 1680 1024 1025 1028 1077 interlace +hsync
(**) fglrx(0): *Mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900
(**) fglrx(0): Default mode "1152x864": 96.8 MHz (scaled from 0.0 MHz), 63.0 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1152x864" 96.76 1152 1224 1344 1536 864 865 868 900 +hsync
(**) fglrx(0): Default mode "1152x864": 81.6 MHz (scaled from 0.0 MHz), 53.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 +hsync
(**) fglrx(0): Default mode "1152x864": 64.7 MHz (scaled from 0.0 MHz), 43.0 kHz, 47.0 Hz (I)
(II) fglrx(0): Modeline "1152x864" 64.67 1152 1208 1328 1504 864 865 868 915 interlace +hsync
(**) fglrx(0): Default mode "1152x864": 58.3 MHz (scaled from 0.0 MHz), 39.2 kHz, 43.0 Hz (I)
(II) fglrx(0): Modeline "1152x864" 58.28 1152 1200 1320 1488 864 865 868 911 interlace +hsync
(**) fglrx(0): *Mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1024x768" 78.75 1024 1040 1136 1312 768 769 772 800
(**) fglrx(0): Default mode "1024x768": 78.4 MHz (scaled from 0.0 MHz), 57.7 kHz, 72.0 Hz
(II) fglrx(0): Modeline "1024x768" 78.43 1024 1080 1192 1360 768 769 772 801 +hsync
(**) fglrx(0): Default mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.0 Hz
(II) fglrx(0): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 +hsync +vsync
(**) fglrx(0): Default mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 +hsync +vsync
(**) fglrx(0): *Mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
(II) fglrx(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625
(**) fglrx(0): Default mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.0 Hz
(II) fglrx(0): Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666
(**) fglrx(0): Default mode "800x600": 45.5 MHz (scaled from 0.0 MHz), 43.8 kHz, 70.0 Hz
(II) fglrx(0): Modeline "800x600" 45.50 800 840 920 1040 600 601 604 625 +hsync
(**) fglrx(0): Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.0 Hz
(II) fglrx(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628
(**) fglrx(0): Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.0 Hz
(II) fglrx(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625
(**) fglrx(0): *Mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
(II) fglrx(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 +hsync +vsync
(**) fglrx(0): Default mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.0 Hz
(II) fglrx(0): Modeline "640x480" 31.50 640 664 704 832 480 489 492 520 +hsync +vsync
(**) fglrx(0): Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x480" 25.18 640 656 752 800 480 490 492 525 +hsync +vsync
(**) fglrx(0): Default mode "720x576": 32.7 MHz (scaled from 0.0 MHz), 35.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "720x576" 32.66 720 744 816 912 576 577 580 597 +hsync
(**) fglrx(0): Default mode "640x400": 28.1 MHz (scaled from 0.0 MHz), 33.7 kHz, 75.0 Hz
(II) fglrx(0): Modeline "640x400" 28.07 640 696 736 832 400 413 415 449
(**) fglrx(0): Default mode "640x400": 24.9 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x400" 24.92 640 664 760 792 400 460 462 525
(**) fglrx(0): Default mode "400x300": 24.8 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "400x300" 24.75 400 408 448 528 300 601 602 625 doublescan
(**) fglrx(0): Default mode "400x300": 22.3 MHz (scaled from 0.0 MHz), 45.0 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "400x300" 22.33 400 416 480 496 300 601 605 742 doublescan
(**) fglrx(0): Default mode "320x240": 15.8 MHz (scaled from 0.0 MHz), 37.9 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "320x240" 15.75 320 328 360 416 240 481 482 501 doublescan
(**) fglrx(0): Default mode "320x240": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x240" 12.59 320 328 376 400 240 491 493 525 doublescan
(**) fglrx(0): Default mode "320x200": 13.1 MHz (scaled from 0.0 MHz), 31.5 kHz, 75.0 Hz (D)
(II) fglrx(0): Modeline "320x200" 13.10 320 352 368 416 200 406 407 417 doublescan
(**) fglrx(0): Default mode "320x200": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
(II) fglrx(0): Modeline "320x200" 12.59 320 336 384 400 200 457 459 524 doublescan
(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.3.0, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"(II) Module already built-in
(==) fglrx(0): NoAccel = NO
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.2.0
ABI class: X.Org Video Driver, version 1.2
(==) fglrx(0): HPV inactive
(==) fglrx(0): FSAA enabled: NO
(==) fglrx(0): FSAA Gamma enabled
(==) fglrx(0): FSAA Multisample Position is fix
(==) fglrx(0): NoDRI = NO
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) fglrx(0): Depth moves disabled by default
(==) fglrx(0): Capabilities: 0x00000000
(==) fglrx(0): CapabilitiesEx: 0x00000000
(==) fglrx(0): cpuFlags: 0x4000001f
(==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536
(**) fglrx(0): UseFastTLS=2
(==) fglrx(0): BlockSignalsOnLock=1
(==) fglrx(0): EnablePrivateBackZ = NO
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xfbe00000 - 0xfbe0ffff (0x10000) MX[B]
[1] 0 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B]
[2] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[3] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[4] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[5] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[6] -1 0 0xfb800000 - 0xfb8000ff (0x100) MX[B]
[7] -1 0 0xfb900000 - 0xfb9000ff (0x100) MX[B]
[8] -1 0 0xfbc00000 - 0xfbc0007f (0x80) MX[B]
[9] -1 0 0xcbf00000 - 0xcbf00fff (0x1000) MX[B]
[10] -1 0 0xcc000000 - 0xcbffffff (0x0) MX[B]O
[11] -1 0 0xfbf00000 - 0xfbf0ffff (0x10000) MX[B](B)
[12] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[13] -1 0 0xfbd00000 - 0xfbd1ffff (0x20000) MX[B](B)
[14] -1 0 0xfbe00000 - 0xfbe0ffff (0x10000) MX[B](B)
[15] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[16] -1 0 0xcbe00000 - 0xcbe00fff (0x1000) MX[B](B)
[17] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprU)
[18] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprU)
[19] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprU)
[20] 0 0 0x0000e000 - 0x0000e0ff (0x100) IX[B]
[21] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[22] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[23] -1 0 0x00009400 - 0x000094ff (0x100) IX[B]
[24] -1 0 0x00001400 - 0x000014ff (0x100) IX[B]
[25] -1 0 0x00001000 - 0x000010ff (0x100) IX[B]
[26] -1 0 0x0000a800 - 0x0000a81f (0x20) IX[B]
[27] -1 0 0x0000a400 - 0x0000a41f (0x20) IX[B]
[28] -1 0 0x0000a000 - 0x0000a01f (0x20) IX[B]
[29] -1 0 0x00009800 - 0x0000981f (0x20) IX[B]
[30] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B]
[31] -1 0 0x0000b000 - 0x0000b0ff (0x100) IX[B]
[32] -1 0 0x0000b400 - 0x0000b40f (0x10) IX[B]
[33] -1 0 0x0000b800 - 0x0000b803 (0x4) IX[B]
[34] -1 0 0x0000c000 - 0x0000c007 (0x8) IX[B]
[35] -1 0 0x0000c400 - 0x0000c403 (0x4) IX[B]
[36] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[37] -1 0 0x0000d400 - 0x0000d407 (0x8) IX[B]
[38] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[39] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]
[40] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B](B)
[41] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
[42] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 7.1.0.0
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card3
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card14
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmGetBusid returned ''
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0x2000
(II) fglrx(0): [drm] mapped SAREA 0x2000 to 0xb7f31000
(II) fglrx(0): [drm] framebuffer handle = 0x3000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.37.6
(II) fglrx(0): Date: May 25 2007
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(WW) fglrx(0): Kernel Module version does *not* match driver.
(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0x2000 at 0xb7f31000
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(II) fglrx(0): FBADPhys: 0xd0000000 FBMappedSize: 0x08000000
(==) fglrx(0): Write-combining range (0xd0000000,0x8000000)
(II) fglrx(0): FBMM initialized for area (0,0)-(1280,8191)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1280,1024) (front color buffer - assumption)
(II) fglrx(0): Largest offscreen area available: 1280 x 7167
(==) fglrx(0): Backing store disabled
(==) fglrx(0): Silken mouse enabled
(II) Loading extension FGLRXEXTENSION
(II) Loading extension ATITVOUT
(**) fglrx(0): DPMS enabled
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
Solid Horizontal and Vertical Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(II) fglrx(0): Acceleration enabled
(II) fglrx(0): Direct rendering disabled
(==) fglrx(0): Using hardware cursor
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(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) Initializing built-in extension XEVIE
(EE) AIGLX: Screen 0 is not DRI capable
(II) Loading local sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
(**) Option "CoreKeyboard"
(**) Generic Keyboard: Core Keyboard
(**) Option "Protocol" "standard"
(**) Generic Keyboard: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Generic Keyboard: XkbRules: "xorg"
(**) Option "XkbModel" "abnt2"
(**) Generic Keyboard: XkbModel: "abnt2"
(**) Option "XkbLayout" "br"
(**) Generic Keyboard: XkbLayout: "br"
(**) Option "CustomKeycodes" "off"
(**) Generic Keyboard: CustomKeycodes disabled
(**) Option "Protocol" "ImPS/2"
(**) Configured Mouse: Device: "/dev/input/mice"
(**) Configured Mouse: Protocol: "ImPS/2"
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "true"
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Configured Mouse: Buttons: 9
(**) Configured Mouse: Sensitivity: 1
(**) Option "SendCoreEvents"
(**) stylus: always reports core events
(**) stylus device is /dev/input/wacom
(**) stylus is in absolute mode
(**) stylus: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "BaudRate" "9600"
(**) stylus: serial speed 9600
(**) Option "SendCoreEvents"
(**) cursor: always reports core events
(**) cursor device is /dev/input/wacom
(**) cursor is in relative mode
(**) cursor: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "BaudRate" "9600"
(**) cursor: serial speed 9600
(**) Option "SendCoreEvents"
(**) eraser: always reports core events
(**) eraser device is /dev/input/wacom
(**) eraser is in absolute mode
(**) eraser: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "BaudRate" "9600"
(**) eraser: serial speed 9600
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : Invalid argument
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : Invalid argument
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : Invalid argument
(II) Configured Mouse: ps2EnableDataReporting: succeeded
SetClientVersion: 0 9

Miguel

August 18th, 2007, 06:28 AM

How many fglrx packages do you have installed? I was surprised to see xorg loading first the correct 8.40.4 driver but loading later the kernel module 8.37.6. Furthermore, I guess you shouldn't load AIGLX when running fglrx. Other than that, things seem pretty normal.

In comparison with the free 6.6.193 radeon driver (on a ATi Mobility Radeon 9600), I get no errors and a few warnings:

$ grep WW /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
(WW) Including the default font path /usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/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.
(WW) RADEON(0): Unknown DDCType 6 found
(WW) RADEON(0): LCD DDC Info Table found!
(WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled
(WW) RADEON(0): DRI init changed memory map, adjusting ...
(WW) RADEON(0): MC_FB_LOCATION was: 0xd7ffd000 is: 0xd7ffd000
(WW) RADEON(0): MC_AGP_LOCATION was: 0xffffffc0 is: 0xe07fe000
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32

Bryce,

CCC did indeed replace the previous fglrx control panel. The new app is much more useful, as it allows you to switch on FSAA and similar things from there, as well as doing quite a few things from a GUI that weren't possible with the old panel. I guess they only removed the old tool once the new one worked in x86_64.

On a side note, I wouldn't waste much energy into 8.40.4. If it goes in, it's OK. If not... well, nothing much is really lost. The problem there is that apparently AMD is in low maintenance mode waiting for the new driver. This has shown in the last two releases, with both having notorious bugs (8.38 had the segfaulting aticonfig and 8.39 had the watermark), and both forcing really rare sub-releases.

Regarding testing on 6.6.193, I'm still experiencing with it before looking into launchpad. Anyway, I've seen a couple of things which I don't know if they are usual or not.
Torcs (self compiled 1.3.0) doesn't run well together with compiz-fusion, either windowed or full-screen mode. There is an error line telling the following:

freeglut (/usr/local/lib/torcs/torcs-bin): Unable to create direct context rendering for window 'FREEGLUT'
This may hurt performance.

This happens with a recently configured and compiled torcs (using latest mesa and alll)
Scorched3D runs very slow in high quality and normal settings, and shows weird image artifacts. See the attachment. This is probably due to some of the missing extensions, though. I really want to find out which option is slowing things down before reporting in launchpad.

Other GL games I've tested are supertux (sound is a bit choppy. doesn't depend on desktop effects) and frets on fires (seems to work OK. Some songs have a green hue, but it might be on purpose). I have no Q3 or something installed right now, neither blender to do something more productive.

yelo3

August 18th, 2007, 03:31 PM

Miguel, you are lucky you can use compiz with your radeon card! My card is reakky slow to render it :(

If you play using the radeon driver you should also install driconf and use the option "disable low impact fallback" otherwise some games will not play well!
Can this option be enabled by default?

damagedspline

August 19th, 2007, 01:32 PM

Thanks for the ati 6.6.193, simple 3d on opensourced Xpress 200m - finally !

glxgears reports ~700 fps.

Some questions tough:
1) Does it include the xrandr/tvout for experimentaion?
2) Does the libdrm2 include the latest patches?(2/8/2007)
3) This one goes to the other foss ati tester: Does firefox look more resource cosumee? - there might also be another reason other then the ati driver...

Thanks again

DeeZiD

August 19th, 2007, 01:42 PM

I'm using the nvidia 100.14.11 driver right now (your packages of course).

I don't notice any differences over 96.31 or 97.55 except that the firefox fonts have the right size now!
I didn't know that firefox font problem is nvidia driver related. :confused:

regards Dennis

damagedspline

August 20th, 2007, 02:35 AM

Miguel

August 20th, 2007, 04:50 AM

Sadly to say:
on 01:05.0 VGA compatible controller: ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)

The laptop might overheats if X11 video output is used. I compared running VLC with X11 as opposed to XVideo - Almost 20 Celsius degrees difference.
On this laptop that a lot!

I'd advise switching to Xv.

That's because you are using the CPU for rendering the video, instead of the graphics card. With the latest updates you should be able to use Xv and compiz-fusion, thus not overheating your CPU with video playback.

yelo3

August 20th, 2007, 10:57 AM

I filed a bug upstream about compiz performance on r300 radeon cards. They answered that it is fixed in xserver-xorg-core 1.3.99
Could you upload in into your testing webpage, bryceharrington?

It is really important that this package is included in gutsy, because now compiz is enabled by default on r300 cards, and compiz has to run well!

bryceharrington

August 20th, 2007, 06:33 PM

Hi all,

I wanted to give some more complete information about the decision to postpone xserver 1.4 for Gutsy+1. Please forward this info along to appropriate spots.

First, in the blueprint some have noticed that displayconfig-gtk and Bulletproof-X are listed as dependent on xorg 7.3, and wondered if this means the latter two specs will also be postponed. Actually, the only Xorg 7.3 feature displayconfig-gtk depends on is xrandr 1.2, which we've had integrated into Gutsy for quite some time. So the dependency there has already been met, and there is no conflict, and neither is being postponed.

In fact, displayconfig-gtk is now available in Gutsy and the spec is considered finished, modulo a few bugs. I'd encourage those with Python skills to please test out displayconfig-gtk: After updating your Gutsy to the latest, go to System->Administration->Screens and Graphics. Bug reports or - especially! - patches would be very well received. Come by #ubuntu-x/Freenode or post to displayconfig-gtk in launchpad.

Bulletproof-X is also deployed with the latest xorg update, but I've not switched it on yet due to a few remaining issues. However you can turn it on yourself by updating Gutsy to the latest and then run `sudo /etc/gdm/failsafeInstall`. Then break your xorg.conf (like change your driver to 'foo' - make sure to make a backup of your xorg.conf!) and restart X. This should result in putting you into the failsafe mode. Please test it out, and file bugs you find against xorg in launchpad.

Also, all is not lost with the Xorg 7.3 spec. Remember that when we wrote the spec, we knew that it was a long shot that xserver 1.4 would be released early enough to meet Ubuntu feature freeze, so we determined to take advantage of the Xorg project's stellar work of modularized Xorg by upgrading as many pieces as possible. Nearly all the Xorg drivers, libraries, and apps have been updated to latest as of a week or two ago. We are also including xserver 1.3 rather than Feisty's xserver 1.2, so everyone is likely to see big improvements in X already.

That said, it was difficult making this decision. I really wanted to be able to mark the Xorg 7.3 spec done, and ensure Gutsy users have the latest cool features in xserver. However, we must balance this against the vast bulk of Ubuntu users who have little idea what "X" is, and just want the GUI to work reliably. I felt that time would be best spent focusing on the needs of this latter group, enhancing the stability of Xorg, backporting fixes, and ensuring DisplayConfigGtk and BulletProofX are as reliable as we can make them.

I'm very excited by xserver 1.4's new features including texture-from-pixmap and input hotplugging. The former sounds like it could benefit Compiz performance for certain graphics cards; on the con side, we're very sensitive to Compiz stability at the moment due to the Compiz-by-default spec, so it seems to me that it would be best to deploy this feature when we have ample time for testing. The latter, input hotplugging, promises to allow us to further reduce the size of xorg.conf, however again we'd want to do ample testing to make sure it will work in the bulk of cases before we took full advantage of it. So even if we were able to roll out xserver 1.4 now, it would likely not be until Gutsy+1 that users would be able to see these new features.

Ultimately I think this is just a timing issue, not really anyone's fault. Xorg and Ubuntu both have well published release schedules, just in this instance the gears didn't mesh up.

Looking at the xserver 1.4 changelog, there are a large number of bug fixes. These are perhaps the things we'll all miss the most! I plan to work on backporting as many of these as possible - but I could really more people's help to identify the patches to backport and verify they fix important bugs. This isn't the most sexy work in the world, but at least it's straightforward work and it could make a huge difference to a wide number of potential new Linux converts. I would love to welcome more developers to the Ubuntu X team! Come join #ubuntu-x on Freenode if you'd like to help with the patch extraction and bug squishing. :-)

bryceharrington

August 20th, 2007, 07:37 PM

yelo3, hmm, from others I've heard the opposite - that the fglrx in Feisty has a hang during log out or switch users, but the newer driver has this issue fixed. Is this reported to Launchpad, and if so what's the bug ID number?

Regarding the compiz performance change for r300 - can you point me at the discussion to this? We do not plan on including 1.3.99 or 1.4 in Gutsy (see my previous post for why), but I can backport minor patches if y'all can help point them out.

mabovo, thanks, it's great to see the debs worked well enough for X to start. I notice a lot of warnings and errors about unsupported stuff (I think those are all known issues), and it looks like there's a kernel version mismatch.

Miguel, can you verify that CCC can be run with these debs? I noticed that the old panel app had special packaging code to include it, but didn't do anything special for CCC, so am not certain if it just works, or if I need to do more work to hook it in.

Thanks for the advice on holding off on 8.40.4. Since we're after feature freeze, it will take extra paperwork to get things into Gutsy, and it will be even more critical that the changes not introduce regressions. Josh says he's seeing less tearing as bad as with the previous version and it seems a little smoother. However, I'd like to identify some very specific serious issues that this resolves - and little or no evidence of regressions compared with the current official version. For people wishing to run the latest and greatest, I'll be happy to continue to provide these drivers experimentally from my Testing site.

Miguel, can you see if there is a Launchpad bug report on the issue with Torcs? We've had some reports of various video-playback related problems when combining Compiz with the current version of xorg and mesa, and I'd really like to see some energy going into tracking down these issues, as they're obviously holding compiz back. Have you spotted any reports/fixes upstream?

damagedspline, I don't know about tvout, but the -ati 6.6.193 does not include the xrandr 1.2 branch. I'm hoping we can create a testing .deb of that branch, but for Gutsy we thought it'd be safest to stick with the mainline -ati for stability reasons. (This was another tough decision - I know the xrandr branch would enable "just works" projector and monitor hot plugging for a huge class of hardware.)

DeeZiD, good to hear the firefox fonts are better. My guess is the fix is not due to the new driver. The font size issue is a separate one seb128 and I have been looking at, and recently went back to hardcoding them to 96 dpi; I would guess that is what fixed the issue for you. ;-) (For more info on future plans for getting the dpi correct, please join the discussion on Alex Jone's 'resolution-independence' spec: https://blueprints.launchpad.net/ubuntu/+spec/resolution-independence)

Miguel

August 20th, 2007, 07:57 PM

Miguel, can you verify that CCC can be run with these debs? I noticed that the old panel app had special packaging code to include it, but didn't do anything special for CCC, so am not certain if it just works, or if I need to do more work to hook it in.

You are talking about fglrx 8.40.4, aren't you? Yeah, sure. In any case, 32 bit (the only I can test) CCC did load on my system for 8.39.whatever. Just give me time. I'm going to bed in a couple of minutes and also have to check the latest brasero.

Miguel, can you see if there is a Launchpad bug report on the issue with Torcs? We've had some reports of various video-playback related problems when combining Compiz with the current version of xorg and mesa, and I'd really like to see some energy going into tracking down these issues, as they're obviously holding compiz back. Have you spotted any reports/fixes upstream?

Will do. On the video issue, for me 6.6.3 couldn't reproduce videos using Xv whith compiz activated. On the other hand, 6.6.193 does. I can attach a screenshot if needed. The intel guys still seem to have troubles. Regarding upstream, I'm not much into it, with the exception of the uber-cool things like the XrandR ati driver.

On a sidenote, I also have some bug reporting to do on 6.6.193 (like compiz and EXA not really liking each other, or a combination of options leading displayconfig-gtk to think my monitor is running at 304Hz). Finally, is there any way to have both fglrx and radeon on my system without conflicting?. Something like a quick library switch or similar. Because else, testing both is a bit of a nuisance with aptitude.

Miguel

August 20th, 2007, 07:59 PM

a combination of options leading displayconfig-gtk to think my monitor is running at 304Hz

Well, I was too quick. Here is a funny screenshot of my "refresh rate".

jbernardo

August 21st, 2007, 06:02 AM

On a sidenote, I also have some bug reporting to do on 6.6.193 (like compiz and EXA not really liking each other, or a combination of options leading displayconfig-gtk to think my monitor is running at 304Hz).
Compiz vs EXA is bug 126425 (https://bugs.launchpad.net/ubuntu/+bug/126425) - there is a xorg package attached to that bug report that fixes the problem. That is the one I've been asking here if it was fixed in Bryce's repository.

Miguel

August 21st, 2007, 07:00 AM

Compiz vs EXA is bug 126425 (https://bugs.launchpad.net/ubuntu/+bug/126425) - there is a xorg package attached to that bug report that fixes the problem. That is the one I've been asking here if it was fixed in Bryce's repository.

Cheers Jose! You've saved me quite some time browsing Launchpad (it isn't particularly responsive today).

By the way, Bryce, there was a comment in bug #122652 that had the dreaded horizontal lines on a X700 with 6.6.193 while I had them with 6.6.3. Is it possible to have both versions in the repositories (like xserver-xorg-video-ati-stable) with a Replaces in the deb and/or with xserver-xorg-video-all depending on xserver-xorg-video-ati | xserver-xorg-video-ati-stable?

I don't know if it's much work, if it's feasible or even if it's even worth it. But one of the few good things having an ati (R300 or 400) card these days is the choice you have WRT to the drivers.

yelo3

August 21st, 2007, 07:06 AM

yelo3, hmm, from others I've heard the opposite - that the fglrx in Feisty has a hang during log out or switch users, but the newer driver has this issue fixed. Is this reported to Launchpad, and if so what's the bug ID number?

Dear bryceharrington, I'm glad you answered to my request.
I made a mistake, also in feisty there was the logout bug! I will test your fglrx soon and tell you what happens. It is not reported to launchpad. I dind't do it because it isn't an opensource driver, but if it is needed I will do this.

Regarding the compiz performance change for r300 - can you point me at the discussion to this? We do not plan on including 1.3.99 or 1.4 in Gutsy (see my previous post for why), but I can backport minor patches if y'all can help point them out.

I opened a compiz bug here
https://bugs.launchpad.net/bugs/132707
look at the upstream bug (maybe you can ask which patch fixes everything), it says fix released in server 1.3.99 + EXA.
I cannot test EXA in xserver 1.3 since it does not work. see this bug
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/88696

I wanted to add that if the compiz problem is not solved, my graphic card NEEDS to be blacklisted in "compiz-by-default"

yelo3

August 21st, 2007, 08:39 AM

tested fglrx 8.40.4

I see a small ATI logo in the bottom right corner "Testing use only unsupported hardware". Is it normal?
3d accel works (3d game nexuiz, after disabling opengl 2.0 shaders), with half cpu usage (I think I'm not using a great video card, radeon 9700 mobility 64MB)
there is no CCC in the menu, but from the console, amdccle runs well
Unfortunately the logout bug is still not fixed

Miguel

August 21st, 2007, 10:18 AM

Tested fglrx 8.40.4. I see a small ATI logo in the bottom right corner "Testing use only unsupported hardware". Is it normal?

It isn't normal because it isn't the expected behaviour. It is normal in a sense, however, because it's a known bug that some suffer. Have a look at phoronix.com for the keyword "Watermark".

3d accel works (3d game nexuiz, after disabling opengl 2.0 shaders), with half cpu usage (I think I'm not using a great video card, radeon 9700 mobility 64MB)
there is no CCC in the menu, but from the console, amdccle runs well
Unfortunately the logout bug is still not fixed

Weird... I thought OpenGL 2.0 support was added to fglrx quite a few months ago. It may be related to having a not so new card, though.

Miguel

August 21st, 2007, 12:12 PM

I'd like to say I'm also seeing the AMD Watermark of Shame" on fglrx 8.40.4. There had to be a reason why phoronix wanted to rename 8.40.4 "The Return of the Watermark". LOL

yelo3

August 21st, 2007, 12:43 PM

It's written that the watermark is a signature in /etc/ati and it is not generated when building distribution pagages:
--buildkg Ubuntu/7.10

Miguel

August 21st, 2007, 06:00 PM

Hi guys,

I'm having aptitude dist-upgrade woes with the new kernel. Is anybody else suffering from the same? I fear it's due to me having installed the 8.40.4 drivers and the restricted modules, but I'm not sure. In any case, aptitude is complaining about linux-image-generic (this is off my head) being a virtual package. This is what I get (translated to english, be careful):

The dependencies of the following packages can not be met:
linux-image-generic: Depends on virtual package linux-image-2.6.22-10-generic
: Depends on virtual package linux-ubuntu-modules-2.6.22-10-generic
Resolving dependencies...
The next actions will solve these dependencies

Remove the following packages:
linux-image-generic

The score is -241

Miguel

August 21st, 2007, 06:28 PM

I forgot to say, but the AMD CCC did load and work using fglrx 8.40.4.

yelo3

August 21st, 2007, 06:32 PM

bryceharrington: about the new patches from xserver 1.3.99 a fedora developer told me in the upstream bug that they applied those patches to the current xserver in fedora rawhide (I think it is the testing branch that will be fedora 8). Then he stated

I think the ubuntu guys should be able to find them, but the build system RPMS
are at

http://koji.fedoraproject.org/koji/buildinfo?buildID=13789

please consider to build an xserver with those patches, so we can test it!

bryceharrington

August 21st, 2007, 07:51 PM

Hi all,

I've started a wiki page for us to keep track of backporting fixes from 1.3.99: https://wiki.ubuntu.com/X/Fixes_to_Backport

I did a pass through the changelog looking for interesting changes and looked up the commit ID's to make it easier to find patches. The list is pretty daunting, but it's a starting point. I'm hoping we can whittle down to something doable.

Please take a look through the list and see if there are additional fixes we need, or if there are some fixes listed that you know we either don't need, or would be too much work to backport. Either report back here, send me a private note, or edit the page directly - whatever's most convenient for you. Mark changes with a "*" to nominate it for backporting, or "?" if you're not sure but think it'd be worth considering.

bryceharrington

August 21st, 2007, 08:13 PM

yelo, thanks for the pointer to the fedora backported patches. I'll definitely take a look through those this week.

Timo has sync'd up our xserver with debian's, to pull in about a dozen fixes they'd gathered, and we're hoping to get this out in Gutsy soonish. After that, I plan on another update that includes a bunch of backport fixes, and will try to include all of these.

bryceharrington

August 21st, 2007, 08:31 PM

Miguel, that's great news that CCC worked okay! Thanks for testing that. Sorry, I don't have a clue about the linux-image-generic issue.

yelo, there were a whole bunch of reports of crash-on-logout issues, and if I recall, several reporters of those bugs reported still having trouble even with the newer fglrx that reportedly fixed it. So you may not be alone...

That watermark sounds pretty wild. I've done up a patch to add that --buildpkg flag, so next time I roll a linux-restricted-modules we'll get rid of that. Thanks for pointing that out.

damagedspline

August 22nd, 2007, 01:37 AM

That's because you are using the CPU for rendering the video, instead of the graphics card. With the latest updates you should be able to use Xv and compiz-fusion, thus not overheating your CPU with video playback.

Actually, when I try to activate Compiz-Fusion it crashes X.

Has anyone managed to run compiz on an Xpress 200m card?

I opened a bug at launchpad since sudden shutdown due to overheating is not pleasent (https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/133604).

Another bug I opened was traced to Flash media & Java that ran in firefox in almost every site I entered. (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/124765)

Since Xv should become the default output module, which package should be included in the bug?

yelo3

August 22nd, 2007, 05:24 AM

reporting from upstream

(In reply to comment #10)
> xserver-1.3.0-newglx-offscreen-pixmaps.patch
> xserver-1.3.0-exaupgrade.patch

These look unrelated, just xserver-1.3.0-mesa7.patch seems to contain all the
needed xserver bits. Then you also need to make sure you have xf86-video-ati
commit 975da595f032c145ad74079ff8edeaead779dc7b and build it against the
patched xserver. Mesa 7.0.1 already contains all the needed Mesa bits.

yelo3

August 22nd, 2007, 05:33 AM

bryceharrington could you please follow the upstream discussion here?
https://bugs.freedesktop.org/show_bug.cgi?id=12068

Miguel

August 22nd, 2007, 06:01 AM

Actually, when I try to activate Compiz-Fusion it crashes X. Has anyone managed to run compiz on an Xpress 200m card?

I opened a bug at launchpad since sudden shutdown due to overheating is not pleasent: Bug #133604 (https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/133604)

Another bug I opened was traced to Flash media & Java that ran in firefox in almost every site I entered: Bug #124765 (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/124765)

Since Xv should become the default output module, which package should be included in the bug?

Mmm... I always thought Xv was the default video mode. Gstreamer video properties is set to "automatic" on my system. What it seems, though, is that you get overheating whenever the CPU hits 100%. It happens to me when playing unaccelerated video, in some crappy sites with Flash and when loading Java. That's why I misunderstood you. In any case, I suppose you have tried using the fewest xorg.conf options possible, heven't you? From your Bug #133604, I'd try commenting all Options except Dynamic Clocks (On my Mobility 9600 this saves around 2W). I'm clueless and witless for the overheating issues, though.

damagedspline

August 22nd, 2007, 03:24 PM

Mmm... I always thought Xv was the default video mode. Gstreamer video properties is set to "automatic" on my system. What it seems, though, is that you get overheating whenever the CPU hits 100%. It happens to me when playing unaccelerated video, in some crappy sites with Flash and when loading Java. That's why I misunderstood you. In any case, I suppose you have tried using the fewest xorg.conf options possible, heven't you? From your Bug #133604, I'd try commenting all Options except Dynamic Clocks (On my Mobility 9600 this saves around 2W). I'm clueless and witless for the overheating issues, though.

Maybe it is, maybe it's not... I dont know anymore...my laptop's tempeature was never *that* high.

I've tried with Dynamic Clocks (only) and results are the same - and with various combinations. I've tried changing the default output module to xv (using gstreamer-properties) but didn't affected the flash...

maybe the opensourced radeon driver is just not ready yet... I'll revert myself to fglrx... BAHHH :(

Thanks, anyway

yelo3

August 22nd, 2007, 04:00 PM

In my experience FLASH animations use lots of cpu.
an instance is the site www.asus.com
the animation is not so big, but the cpu usage is 66%

bryceharrington</