Announcement

Collapse
No announcement yet.

Where is the fglrx documentation?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Porter
    started a topic Where is the fglrx documentation?

    Where is the fglrx documentation?

    Has anyone compiled a full list of fglrx options that can be used in xorg.conf, and their functions?

    This guy seems to think you can get the X server to give you a full listing, but doesn't explain how: http://lists.opensuse.org/opensuse/2.../msg01172.html


    Other than the wiki at http://wiki.cchtml.com/, what documentation is there?

  • mtippett
    replied
    Originally posted by Kano View Post
    Kanotix adds lots of modemlines by default, but any of those crashes the xserver.
    In lieu of putting something on ati.cchtml.com - just run a atigetsysteminfo.sh and post it here. (Although as I mentioned a single canonical reference saves keystrokes since you can say "Modeline bug as per bug 1201 here").

    Leave a comment:


  • Kano
    replied
    Kanotix adds lots of modemlines by default, but any of those crashes the xserver.

    Leave a comment:


  • mtippett
    replied
    A developer doesn't need to post there for information to be available. If you have concerns with a particular set of modelines that don't work or cause problems (and seem to be the only one who has major issues with them) - document it.

    We don't need to post to monitor and be aware of what is going on. People don't always operate overtly.

    I would expect that 5 minutes putting a canonical reference to your problem in the bugzilla would be far better time spent than 10's of posts refering to one or two issues that you have in forums.

    Leave a comment:


  • Kano
    replied
    Windows adds those modes by default - these are non VESA res, but they are already selectable. I absolutely don't understand why you need "bugzilla" when no developer ever posts there. When you look over to nvidia - they put a link to

    http://www.nvnews.net/vbulletin/foru...?s=&forumid=14

    directly on the left of the download pages

    http://www.nvidia.com/object/linux_d...32_177.13.html

    and developers answer directly there (marked as NVIDIA developers). I don't think that repeating me on differnet places is needed. I create live cds - therefore creating a live environment for testing ATI bugs is realatively easy for me. If you want to try that let me know.

    Leave a comment:


  • mtippett
    replied
    Originally posted by Kano View Post
    Of course a xorg.conf with less options is more easy to handle, but what to do when you really NEED extra options like Modelines for res [email protected] or [email protected] because a CRT never reports those special but very usefull res. Every other driver handles this, but when you try this with fglrx and Xorg 7.1.1 -> Xorg crash. Also your amdcccle is crap, it allows setting of 1152x864 at 100 hz but it is really 75 hz when you check it. For basic settings like res and refreshrate no 3rd party tool should be used - be standard conform and accept the options every other driver knows. For your special cases you can use whatever config tool, but don't forget that there are still users without TFT monitors and CRT users like to use non standard res.
    Do you have any formal information on this issue? There is no way that we can determine where things are going wrong. ati.cchtml.com would be a great place to put that.

    Also note that under Windows, NEEDing extra modes involves installing thirdparty apps like powerstrip. Under Windows you either get the modes that are supplied by the EDID, or you need to install a monitor driver. Under Linux there is no option for a monitor driver beyond users adding modelines.

    Although your modes are non-standard, if you can lodge a fully described bug in bugzilla, it allows people to understand where the issue will be.

    Regards,

    Matthew

    Leave a comment:


  • Redeeman
    replied
    well.. its used.. for instance, having 2 graphical logins on 1 computer uses it.. People connecting to XDMCP(like me) uses it.

    Leave a comment:


  • bridgman
    replied
    Probably. I read Matthew's email as saying "it works a lot of the time but we don't treat multiple servers on one card as something we support and test".

    My understanding was that in general the need for multiple x servers on the same card was a vestige of the "pre-3d days" and was going away, but if that is not the case then we'll need to deal with it somehow.

    Leave a comment:


  • Redeeman
    replied
    i am certain that fglrx atleast USED to support having more than 1 X server started.. on my laptop with radeon 9700pro, beefore i changed to r300/radeon, i have done it to start an extra X session for xdmcp..

    edit:
    this is with the monitor being the SAME on both X servers, with only 1 X server "active" at a time..

    Leave a comment:


  • bridgman
    replied
    Realistically, I think you're going to find that all drivers support multiple x servers just fine until dri (and the associated drm aka kernel module) comes into the picture, then it becomes a lot more iffy.

    As a trivial example, I believe the radeon (-ati) driver can fully accelerate both screens if you are running a single X server, but can only accelerate the primary screen when running two servers on the same card. Running multiple X servers on multiple cards is usually less of a problem than running multiple servers on the same card.
    Last edited by bridgman; 06-21-2008, 06:53 PM.

    Leave a comment:

Working...
X