Announcement

Collapse
No announcement yet.

AGP users, UNITE!!!!

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

  • israel_miranda
    started a topic AGP users, UNITE!!!!

    AGP users, UNITE!!!!

    Hi folks. I have a x700 AGP 256mb video card, and I haven't been able to get working a fglrx driver which supports AIGLX.

    I've lost about a hundred hours(since october 24th 2007) searching the web and making tests, trying to get AIGLX working since the first driver which supports is(8.42)http://www2.ati.com/drivers/linux/linux_8.42.3.html), and none of them worked nice in my card. In 8.42 driver I got it partially working, the bug of the driver not assigning and IRQ to the card, which makes it work very slow, and compiz was full of glitches, making it unusable. The later releases just freeze my entire system, catalyst 7.1, 7.2 and 8.1 . I really lost my patience and even decided to sell my card, to get an nvidia one, but nobody buys AGP cards anymore
    So I'm stuck with it.

    My point is:
    Maybe the agp users are not well represented in the beta testers team. I've talked to bridgman, a user on the forum who works on AMD/ATI, and he said he'd get me in their beta testers mailing list, so we at least make sure the developers know about the problem, they are aware of the problem with AGP cards, but they though it'd be a 2x00 series problem, and it seems not.

    All of you who use AGP cards, please make a post in this thread posting your system configuration:

    ATI Graphic card

    * Monitor type(lcd, crt, tv) and resolutions used

    * Motherboard/chipset model

    * Processor type

    * Ammount of memmory

    * Distro used

    * Kernel version

    * Xorg version

    * fglrx version

    * is AIGLX working ?

    And please, justify the choice of the version of your driver. I use 8.40 because it's stable in my system, even though it doesn't support AIGLX.

    After having this thread with many AGP users, we will be able to organize ourselves better to give more feedback about AGP cards. bridgman told me that there were a lot of AGP users in the beta testers group, but most of them migrated to PCI-E, so they're needing more.

    What I want is understand if it's a driver problem, a distro problem, a Xorg problem, the more reports we have, the easier it'll be to track it.

    Thanks in advance.
    Last edited by israel_miranda; 02-13-2008, 01:56 PM.

  • diszler
    replied
    My system;
    ATI Technologies Inc Unknown device 94c4 (prog-if 00 [VGA controller]) (HD2400 AGP Based)
    CPU: AMD Athlon(tm) 64 Processor 2800+
    Host bridge: nVidia Corporation nForce3 250Gb Host Bridge
    OS FC7 and FC8

    I have been running this setup for a few months without any problems. But here the other day, I suddenly started experiencing problems, after changing som Bios settings (added a new sound card). After this the system suddenly froze after 1-2 minutes of system uptime. Changing the AGP Apeture in Bios up and down would change the amount of time before the system froze, but the system froze sooner or later. I found that changing the PCI VGA Palette Snoop in Bios (or whatever it is called) to disabled fixed the whole thing.

    I also noticed that changning AGP Aperture from 256 to 512 actually increased fgl_glxgears and glxgears with about 100 fps.

    glxgears abt 2690 fps
    fgl_glxgears abt 790 fps

    Nice to actually have improved the system

    Hope this can help someone.....



    morten

    Leave a comment:


  • fred
    replied
    Well I just hope that the next driver release will include support for agp version of the Hd2XXX family. Because right now I'm runing my computer with my old 9800 pro (wich work very well with the new driver) and my brand new HD2600 pro back in it's box.

    Leave a comment:


  • Swoopy
    replied
    Originally posted by [email protected] View Post

    One thing I have always noticed at the start of my X log is that the internal agpgart is not used because IOMMU is enabled in the kernel. So I though Ok I'll recompile the kernel without it so I set that to work and Googled around for some info on iommu's. Basically these are hardware address redirectors. The kind of device designed to throw driver writers into confusion. During my search I came across some boot options for X86_64 kernels. It seems I didn't need to recompile my kernel I could just turn iommu off. Investigating the options further I discovered that there is an option to prevent the iommu from remapping the agp aperture. I added the following to my kernel boot line "iommu=noaperture" and set the bios to give the full 512MB of aperture.
    Reboot startx and Voila' I have a working driver with glxgears at 950 fps not blisteringly fast but at least usable (I had 1200 with the xgl server).

    I know someone on this forum has a direct line to one of the ATI developers so perhaps they could relay this as it is certainly a fix for 64 bit machines. Alas those with 32 bit boxes probably won't get any joy I don't think they have iommu's but I could be wrong so check your X start-up log.

    Colin Close
    Just for completeness' sake in response to Colin's excellent detailed post:

    I have been booting my system with the "iommu=noaperture" setting almost since I installed Ubuntu 7.10 64-bit on my AMD 64x2 dual-core. This was part of solving the "desktop app pause" issues I was having. I was running with an nVidia 6600GT card at the time.

    On my PC, in normal linux boot mode it's on, in recovery mode it's left out. I have tried every fglrx that was released since 7.10 and NONE worked on my system (VIA K8t800pro chipset) and video card (ATI HD2600XT AGP 512 MB).

    Not that I have a desire to disappoint fred but I am almost certain that "iommu=noaperture" is not the 'magic bullet' for fglrx with Radeon HD2xxx AGP cards

    -edit-: yes and I also did try fglrx a couple of times when booted in normal mode with no kernel boot-options included. Just to be sure that iommu wasn't set to noaperture by default when booting in recovery mode.
    My full boot-options in "normal" boot are :
    Code:
    ro quiet splash nodmraid notsc noapic nolapic acpi=strict iommu=noaperture
    Last edited by Swoopy; 02-27-2008, 04:09 AM.

    Leave a comment:


  • fred
    replied
    That is very interesting itchka. Very nice research. I will try some of those trick with my hd 2600 pro

    Maybe it will do the trick

    Leave a comment:


  • itchka@compuserve.co
    replied
    A possible fix for X86_64 users

    I have been lurking in these forums for some time looking for a fix for my Sapphire X1650 which is running on an AMD 64 dual core.
    I saw the previous post and thought I'd give February's ATI offering a try.
    I haven't had a working driver since the first AIGLX enabled version which worked but did not enable the interrupts.
    On earlier drivers using the XGL server I could get my card working with the MaxAtiGart option but I only put it in the xorg.conf.

    So I gave the new driver a try and managed to get a running Xserver but just with a mouse pointer and nothing else. A good deal better than a hard lockup. I took a look at the X log and it showed that the interrupts were being enabled so I decided to try a few things.

    One thing I have always noticed at the start of my X log is that the internal agpgart is not used because IOMMU is enabled in the kernel. So I though Ok I'll recompile the kernel without it so I set that to work and Googled around for some info on iommu's. Basically these are hardware address redirectors. The kind of device designed to throw driver writers into confusion. During my search I came across some boot options for X86_64 kernels. It seems I didn't need to recompile my kernel I could just turn iommu off. Investigating the options further I discovered that there is an option to prevent the iommu from remapping the agp aperture. I added the following to my kernel boot line "iommu=noaperture" and set the bios to give the full 512MB of aperture.
    Reboot startx and Voila' I have a working driver with glxgears at 950 fps not blisteringly fast but at least usable (I had 1200 with the xgl server).
    I know someone on this forum has a direct line to one of the ATI developers so perhaps they could relay this as it is certainly a fix for 64 bit machines. Alas those with 32 bit boxes probably won't get any joy I don't think they have iommu's but I could be wrong so check your X start-up log.

    Colin Close
    Last edited by [email protected]; 02-26-2008, 10:05 PM.

    Leave a comment:


  • fred
    replied
    I wonder if this trick would work for an HD2600 pro AGP card????

    Did anybody else try?

    Leave a comment:


  • Spooky
    replied
    Hi,

    I have/had also the issue with the AGP Rialto Bridge on my hardware configuration, but today I could get it to work.

    In the past I tried much things (change some settings in xorg.conf, in BIOS like AGP Aperture Size ....) to find a workaround agains the black sreen with frozen system during X start with fglrx (7.12 and later) enabled - but nothing has worked.

    The only possibility was to blacklist "via_agp" module in "/etc/modprobe.d/blacklist" but then I got no Xv extension and no 3D acceleration.

    Then (today) after installation of 8.45.5 from ATI OpenSuSE 10.3 repository and the same black screen (via_agp loaded), I tried "aticonfig --max-gart-size 512" and "bingo!" my system starts now with 8.45.5 and 3D acceleration (include Xv) enabled. My current setting for "AGP Aperture Size" in BIOS is 128MB and I believe that 256MB also works for me, but I have there no possibility to set values bigger than 256MB.

    Important: Use "aticonfig --max-gart-size 512" to set/change manual the value, because this add/change the entry in /etc/ati/amdpcsdb and not in xorg.conf !

    Athlon XP 2400+
    ASUS A7V133 (VIA KT133A)
    768MB SD-RAM
    Sapphire X1650 Pro AGP DDR3
    Kernel : 2.6.22.17-0.1
    Distribution: OpenSuSE 10.3

    Spooky
    Last edited by Spooky; 02-23-2008, 08:23 AM.

    Leave a comment:


  • NaterGator
    replied
    Hey yo!! Thought I would post up my results from trying the new 8.02 fglrx driver on my gentoo box. Didn't work, so I'm back to radeon, but this was what I found:

    I have a Gigabyte Radeon X800 XT Platinum Edition
    Samsung 193P LCD (1280x1024 @ 75Hz)
    MSI K8N Neo2 Platinum (nForce 3 Ultra)
    Athlon 64 X2 4800+
    1GB gSkill TCCD
    Gentoo running the gentoo kernel version 2.6.24-r1
    Using Xorg 7.3
    Ati driver 8.55.2 (8.02)
    AIGLX did work after a little tweaking

    I found that firefox scrolling was better, but not great. Running fgl_glxgears gave me the same unbearable corruption seen here:
    http://www.phoronix.com/forums/showt...5092#post25092

    Could be related to my running compiz-fusion with the GTK decorator, but I generally run AIGLX for the compiz windowmanager, so it needs to work ....



    I can tell sligh improvements are being made so far, but so much is broken and the open source driver is working so well that I have no reason to switch. My only complaint with the open source driver and compiz is tearing in videos, but it's alot better than the total lack of video support in the fglrx driver.

    Leave a comment:


  • NeoBrain
    replied
    Originally posted by Compxpert
    Just wondering but what Distro are you running. I think you said Gentoo at one point. Make sure you have your AGP chipset driver complied into your kernel. Had a problem recently after a reinstall and I couldn't figure out why then I realized I never complied support for my agp chipset into my kernel.
    Yes, I am using Gentoo, but I have already tried with givemesuggar and bridgman to figure some way to make it work, without success however.
    I decided to just don't care about it and stay with 8.43 and wait until a functional release comes out, but I just thougt I should post my "AGB ATI experiences" anyways

    Leave a comment:

Working...
X