You are not logged in.
didn't work here with fglrx ati driver.. rollback to 1.2
The next ati driver supports 1.3, its the arch people who are slow not the ati driver devs:| thats actually quite ironic, since it's often the opposite...
Use the Source, Luke!
Offline
kastor wrote:didn't work here with fglrx ati driver.. rollback to 1.2
The next ati driver supports 1.3, its the arch people who are slow not the ati driver devs:| thats actually quite ironic, since it's often the opposite...
i think that devs are overload... the new came out yesterday.. or something like that.. i suposed.. we have to wait.
Offline
Roberth wrote:kastor wrote:didn't work here with fglrx ati driver.. rollback to 1.2
The next ati driver supports 1.3, its the arch people who are slow not the ati driver devs:| thats actually quite ironic, since it's often the opposite...
i think that devs are overload... the new came out yesterday.. or something like that.. i suposed.. we have to wait.
Why are they overloaded?
Use the Source, Luke!
Offline
They're always overloaded. There are only about 10 of them, you know...
Offline
The next ati driver supports 1.3, its the arch people who are slow not the ati driver devs:| thats actually quite ironic, since it's often the opposite...
Yeah, sorry about being a few days tardy with the newest fglrx - I've been busy in real life. I'm actually building the new drivers now; after some small testing here you'll see them in the repos.
==edit== uploaded, for all but -mm. Gotta find me a patch for that one.
Last edited by Cerebral (2007-06-03 03:45:11)
Offline
.. and when this new xorg-server hits current, I won't even notice it, as I already have a working xorg.conf.
Agree, xorg.conf is like I want it, it took a couple of weeks of my life to get it just right. I ones actually considered having it tattooed on my back (I chose the butt instead).
So the fuss of moving to the next xorg-server will have to give me something substantial in return, don't see any reason to consider.
Offline
Roberth wrote:The next ati driver supports 1.3, its the arch people who are slow not the ati driver devs:| thats actually quite ironic, since it's often the opposite...
Yeah, sorry about being a few days tardy with the newest fglrx - I've been busy in real life. I'm actually building the new drivers now; after some small testing here you'll see them in the repos.
==edit== uploaded, for all but -mm. Gotta find me a patch for that one.
Well real life always comes first:)
Use the Source, Luke!
Offline
The thing is that not all displays come with proper EDID ROMs that can actually be read properly. This usually is not problem on windows since it carries a huge database of displays as plaintext *.ini files. Xorg on the other hand can most of the time only guess and it doesn't do that very well. To sum up, I would always recommend to create your own xorg.conf. Without it, all sorts of problems can occur.
Great about the new xorg-server is for example that it can switch between dual-head and single-head mode without changing xorg.conf
Last edited by kth5 (2007-06-03 12:59:03)
I recognize that while theory and practice are, in theory, the same, they are, in practice, different. -Mark Mitchell
Offline
I've just given 1.3 a try on my system and it fails which is a shame but with the recent advances in X my xorg.conf although still in use is a hell of a lot smaller which is a credit considering how large mine was under the 6.8 monolithic release. Also not sure if it was a freetype/vesa/xorg-server update or what but my fonts look a lot better now.
Offline
Has anyone had any luck with 1.3.0 and the xf86-video-ati driver in testing? I have a dell laptop with an ati radeon m7 (too old for fglrx) and I'm getting a blank screen when I try to run the driver from testing. I get no errors in the logs etc, all the programs etc start (verified with ps). If I do a xrandr from a console it returns the proper display settings etc. So far searching has failed me, everything I get has to do with the fglrx drivers not the xorg ones. Can anyone point me in the right direction? I can post my xorg.conf and the logs if anyone thinks they'll be helpful but I'm not on the laptop right now as I'm quite tired of it at the moment.
andy
Offline
Could someone sum up the improvements/benefits of this new server over the old one? I.e., why should I (or not) upgrade?
Offline
Has anyone had any luck with 1.3.0 and the xf86-video-ati driver in testing? I have a dell laptop with an ati radeon m7 (too old for fglrx) and I'm getting a blank screen when I try to run the driver from testing. I get no errors in the logs etc, all the programs etc start (verified with ps). If I do a xrandr from a console it returns the proper display settings etc. So far searching has failed me, everything I get has to do with the fglrx drivers not the xorg ones. Can anyone point me in the right direction? I can post my xorg.conf and the logs if anyone thinks they'll be helpful but I'm not on the laptop right now as I'm quite tired of it at the moment.
andy
I have Radeon 9000 (250) which is also old for fglrx and looks also for drivers from testing. If I disable DRI than is okay but if DRI module loaded than work okay too but on logoff from KDE computer freezing.
BTW I like Xorg 1.2 much more than 1.3 and configuration of xorg.conf for 1.2 is much easier than 1.3 which doesn't work without xorg.conf. Maybe when final came out would be better. Or Xorg want to be Windows like??
Offline
Could someone sum up the improvements/benefits of this new server over the old one? I.e., why should I (or not) upgrade?
I've only had a very cursory look at 1.3, but the lack of xorg.conf seems interesting in case the automatically detected values are better than the ones I've put in xorg.conf (especially as I use my arch-installed usb pen on multiple computers). Other than that, you know, updated software is normally better etc. I'll probably wait until it goes into current though.
Offline
The thing is that not all displays come with proper EDID ROMs that can actually be read properly. This usually is not problem on windows since it carries a huge database of displays as plaintext *.ini files. Xorg on the other hand can most of the time only guess and it doesn't do that very well.
This is what I don't get. That this is supposed to be such a huge problem. all those .ini's are available from google thus the xorg devs have easy access to them too meaning that it's not really a problem.
google filetype:ini monitorname
KISS = "It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience." - Albert Einstein
Offline
Running xorg-server 1.3.0.0 now 9 days now. Great release.
Offline
Running xorg-server 1.3.0.0 now 9 days now. Great release.
Could you tell us what kind of graphics card do you have, please? Maybe mouse, touchpad...
Thank you.
Offline
Works fine on an HP nx6325 labtop with ATI Xpress 1100 graphics. No dri as expected.
Offline
I have Radeon 9000 (250) which is also old for fglrx and looks also for drivers from testing. If I disable DRI than is okay but if DRI module loaded than work okay too but on logoff from KDE computer freezing.
I have no luck with or without DRI.
andy
Offline
Xorg server from testing detected my ati x300 notebook quiet well. but it didn't made use of my KEYMAP=de-latin1-nodeadkeys settings and came up with QUERTY instead of QUERTZ layout.
Is there a way to save a working xorg.conf out of the autodetection mode?
Offline
Working well here too, on a nvidia 7600go with latest drivers from testing
Offline
Xorg server from testing detected my ati x300 notebook quiet well. but it didn't made use of my KEYMAP=de-latin1-nodeadkeys settings and came up with QUERTY instead of QUERTZ layout.
Is there a way to save a working xorg.conf out of the autodetection mode?
X -configure
Last edited by kth5 (2007-06-11 08:17:54)
I recognize that while theory and practice are, in theory, the same, they are, in practice, different. -Mark Mitchell
Offline
Well I figured out my problem is with the open source ati driver not xorg-server. I can run 6.6.3 with xorg-server 1.3 fine, but 6.6.192 gives the blank screen. Since neither of them support xrandr 1.2 I guess it's no big deal.
andy
Offline
On my desktop computer Xorg-server 1.3 and Intel video driver 2.0 work both great!
I have only a problem: if I use Compiz or Beryl or another composite manager (I didn't try Xfce WM however) I can't play videos, either with GStreamer, Xine and MPlayer. The only way I found is using MPlayer specifying the output to "x11". Did any of you found out a solution? I seached google but I found no way out. Or can someout point out a good front-end for MPlayer that uses GNOME/GTK+?
Last edited by axelgenus (2007-06-15 07:41:42)
Offline
any one else gets a hard-lockup when starting beryl with exa using the intel driver (don't try this if you have unsaved work).
Offline
Just found a problem. If I'm running an application that uses goom from gstreamer0.10-good, doing crtl+alt+f1 then crtl+alt+f7 again crashes Xserver 1.3.0.0
Offline