View Full Version : The Open-Source ATI R500 Driver
phoronix
06-19-2007, 12:00 PM
Phoronix: The Open-Source ATI R500 Driver
Last week the first open-source ATI R500 (Radeon X1000 series) driver had entered the world. This new driver (named the xf86-video-avivo) is very early into development, but a small set of developers have been working on reverse engineering this GPU class for the past couple of months. This driver does not yet contain any 3D functionality or support for features that most end-users expect. At this point, the driver just contains very basic initialization and set video mode support for a portion of the Radeon X1000 family. Even with this very basic R500 driver, we couldn't help but to explore the Avivo driver for the past few days.
http://www.phoronix.com/vr.php?view=10247
Very interesting. Might try it with my X1900XT 512 soon... is it already supported in git?
I have 6 weeks school holidays starting tomorrow so I could test it for fun.
Out of interest, were you able to test with an X1400?
I added the PCI id for my Lenovo T60 (id is 7145 - M54 Mobility X1400). I get normal looking output on the left side of the screen, but tearing on the right side..
Thanks,
Jon.
Michael
06-19-2007, 05:09 PM
Very interesting. Might try it with my X1900XT 512 soon... is it already supported in git?
I have 6 weeks school holidays starting tomorrow so I could test it for fun.
Not supported in git... You'll need to add the IDs manually (see the article).
Michael
06-19-2007, 05:09 PM
Out of interest, were you able to test with an X1400?
I added the PCI id for my Lenovo T60 (id is 7145 - M54 Mobility X1400). I get normal looking output on the left side of the screen, but tearing on the right side..
Thanks,
Jon.
Had no problems with it using yesterday's git. When did you checkout from git?
Just about 15 mins ago.
Am assuming I didn't do anything dim when adding the id, it is an RV515 right? Am running with the 1400x1050 panel, so I guess I could try some different resolutions etc..
Thanks.
Michael
06-19-2007, 05:28 PM
Just about 15 mins ago.
Am assuming I didn't do anything dim when adding the id, it is an RV515 right? Am running with the 1400x1050 panel, so I guess I could try some different resolutions etc..
Thanks.
Yes, RV515. It works for me with 1400 x 1050. There was a git commit a few days ago that corrected it for odd resolutions (those that when divided by 64 wasn't an integer) but that should be all fixed.
domzanator
06-20-2007, 02:36 AM
Hi all,
I've tried using the xf86-video-avivo open-source driver for ati but can't seem to get it working. Could someone please push me in the right direction?
This is my output:-
[root@localhost xf86-video-avivo]# ./autogen.sh prefix=/usr/
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/local/bin/autoconf
configure.ac:38: error: possibly undefined macro: AC_DISABLE_STATIC
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:39: error: possibly undefined macro: AC_PROG_LIBTOOL
configure.ac:53: error: possibly undefined macro: XORG_DRIVER_CHECK_EXT
configure.ac:78: error: possibly undefined macro: XORG_MANPAGE_SECTIONS
configure.ac:80: error: possibly undefined macro: XORG_RELEASE_VERSION
autoreconf: /usr/local/bin/autoconf failed with exit status: 1
[root@localhost xf86-video-avivo]# pwd
/usr/xf86-video-avivo
Michael
06-20-2007, 08:31 AM
Hi all,
I've tried using the xf86-video-avivo open-source driver for ati but can't seem to get it working. Could someone please push me in the right direction?
This is my output:-
[root@localhost xf86-video-avivo]# ./autogen.sh prefix=/usr/
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/local/bin/autoconf
configure.ac:38: error: possibly undefined macro: AC_DISABLE_STATIC
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:39: error: possibly undefined macro: AC_PROG_LIBTOOL
configure.ac:53: error: possibly undefined macro: XORG_DRIVER_CHECK_EXT
configure.ac:78: error: possibly undefined macro: XORG_MANPAGE_SECTIONS
configure.ac:80: error: possibly undefined macro: XORG_RELEASE_VERSION
autoreconf: /usr/local/bin/autoconf failed with exit status: 1
[root@localhost xf86-video-avivo]# pwd
/usr/xf86-video-avivo
Do you have xorg-x11-server-sdk installed?
Michael, can you please show me a link where we can see changes between the git commits in text form? I know projects where it says for example "fixed a bug where it could crash blabla" and then there's the code of the changes (in which I'm not interested in). Does the avivo driver project has something like that? I really am interested in the work they do from now on.
Michael
06-20-2007, 08:53 AM
Michael, can you please show me a link where we can see changes between the git commits in text form? I know projects where it says for example "fixed a bug where it could crash blabla" and then there's the code of the changes (in which I'm not interested in). Does the avivo driver project has something like that? I really am interested in the work they do from now on.
You're looking for gitweb: http://gitweb.freedesktop.org/?p=avivo/xf86-video-avivo.git;a=summary
domzanator
06-22-2007, 09:06 AM
Do you have xorg-x11-server-sdk installed?
Hi Michael,
I've had success in getting through all of these lines: -
yum install git libpciaccess-devel xorg-x11-server-sdk
git clone git://anongit.freedesktop.org/git/avivo/xf86-video-avivo
cd xf86-video-avivo/
./autogen.sh --prefix=/usr/
make
su
make install
<edit /etc/X11/xorg.conf so the driver changes from vesa or fglrx to avivo>
Now i think my problem is that my X1700 is not supported; when i do a lspci this is what comes back with my card M66-P [Mobility Radeon X1700]. I can't find anywhere saying that my card is supported.
Below is the error i get in the Xorg.0.log
(II) Avivo: driver for Radeon r5xx chipsets: RV515 (Radeon X1300),
RV530 (Radeon X1600), RV530 (Radeon X1600), R580 (Radeon X1900 GT),
RV530 (Radeon X1650 Pro), M52 (Mobility Radeon X1300)
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(EE) No devices detected.
Thanks,
Dom
Michael
06-22-2007, 09:12 AM
Hi Michael,
I've had success in getting through all of these lines: -
yum install git libpciaccess-devel xorg-x11-server-sdk
git clone git://anongit.freedesktop.org/git/avivo/xf86-video-avivo
cd xf86-video-avivo/
./autogen.sh --prefix=/usr/
make
su
make install
<edit /etc/X11/xorg.conf so the driver changes from vesa or fglrx to avivo>
Now i think my problem is that my X1700 is not supported; when i do a lspci this is what comes back with my card M66-P [Mobility Radeon X1700]. I can't find anywhere saying that my card is supported.
Below is the error i get in the Xorg.0.log
(II) Avivo: driver for Radeon r5xx chipsets: RV515 (Radeon X1300),
RV530 (Radeon X1600), RV530 (Radeon X1600), R580 (Radeon X1900 GT),
RV530 (Radeon X1650 Pro), M52 (Mobility Radeon X1300)
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(EE) No devices detected.
Thanks,
Dom
Yes, you are getting the no devices detected as the X1700 ID isn't there. It should work with the X1700, but the ID just hasn't been added. See the article (http://www.phoronix.com/vr.php?view=10247) for how to add the IDs. In the article it mentions where you just need to add the PCI IDs and such. If you still are having problems, I can try to tell you exactly what to do for your Mobility X1700.
domzanator
06-22-2007, 09:23 AM
Yes, you are getting the no devices detected as the X1700 ID isn't there. It should work with the X1700, but the ID just hasn't been added. See the article (http://www.phoronix.com/vr.php?view=10247) for how to add the IDs. In the article it mentions where you just need to add the PCI IDs and such. If you still are having problems, I can try to tell you exactly what to do for your Mobility X1700.
Thanks for the quick response... I'm sort of lost...
Could you please let me know what exactly to do?
Michael
06-22-2007, 09:32 AM
Thanks for the quick response... I'm sort of lost...
Could you please let me know what exactly to do?
Okay, I just checked out git this morning for avivo and made modifications for your Mobility Radeon X1700. Below are two files, replace them with the ones you already have.
include/avivo_chipset.h
#ifndef _AVIVO_CHIPSET_H_
#define _AVIVO_CHIPSET_H_
#include "xf86_OSproc.h"
#include "xf86Resources.h"
/* Drivers for PCI hardware need this */
#include "xf86PciInfo.h"
/* Drivers that need to access the PCI config space directly need this */
#include "xf86Pci.h"
#ifdef PCIACCESS
#include <pciaccess.h>
#endif
#define PCI_CHIP_RV515_7142 0x7142
#define PCI_CHIP_RV530_71C2 0x71C2
#define PCI_CHIP_RV530_71C5 0x71C5
#define PCI_CHIP_R580_724B 0x724B
#define PCI_CHIP_M52_7149 0x7149
#define PCI_CHIP_RV530_71C6 0x71C6
#define PCI_CHIP_M66_71D5 0x71D5
enum avivo_chip_type {
CHIP_FAMILY_RV515,
CHIP_FAMILY_R520,
CHIP_FAMILY_RV530,
CHIP_FAMILY_R580,
CHIP_FAMILY_LAST,
};
#ifdef PCIACCESS
extern const struct pci_id_match *avivo_device_match;
#endif
extern SymTabRec avivo_chips[];
extern PciChipsets avivo_pci_chips[];
#endif
xorg/avivo_chipset.c
#ifdef HAVE_CONFIG_H
#include "config.h"
#endif
#include "avivo.h"
#ifdef PCIACCESS
const struct pci_id_match avivo_device_match[] = {
{
PCI_VENDOR_ATI, 0x71c2, PCI_MATCH_ANY, PCI_MATCH_ANY,
0x00030000, 0x00ffffff, 0
},
{
PCI_VENDOR_ATI, 0x71c5, PCI_MATCH_ANY, PCI_MATCH_ANY,
0x00030000, 0x00ffffff, 0
},
{
PCI_VENDOR_ATI, 0x724b, PCI_MATCH_ANY, PCI_MATCH_ANY,
0x00030000, 0x00ffffff, 0
},
{
PCI_VENDOR_ATI, 0x7142, PCI_MATCH_ANY, PCI_MATCH_ANY,
0x00030000, 0x00ffffff, 0
},
{
PCI_VENDOR_ATI, 0x7149, PCI_MATCH_ANY, PCI_MATCH_ANY,
0x00030000, 0x00ffffff, 0
},
{
PCI_VENDOR_ATI, 0x71C6, PCI_MATCH_ANY, PCI_MATCH_ANY,
0x00030000, 0x00ffffff, 0
},
{
PCI_VENDOR_ATI, 0x71d5, PCI_MATCH_ANY, PCI_MATCH_ANY,
0x00030000, 0x00ffffff, 0
},
{ 0, 0, 0 },
};
#endif
/* Supported chipsets. I'm really, really glad that these are
* separate, and the nomenclature is beyond reproach. */
SymTabRec avivo_chips[] = {
{ PCI_CHIP_RV515_7142, "RV515 (Radeon X1300)" },
{ PCI_CHIP_RV530_71C2, "RV530 (Radeon X1600)" },
{ PCI_CHIP_RV530_71C5, "RV530 (Radeon X1600)" },
{ PCI_CHIP_R580_724B, "R580 (Radeon X1900 GT)" },
{ PCI_CHIP_RV530_71C6, "RV530 (Radeon X1650 Pro)" },
{ PCI_CHIP_M52_7149, "M52 (Mobility Radeon X1300)" },
{ PCI_CHIP_M66_71D5, "M66 (Mobility Radeon X1700)" },
{ -1, NULL }
};
PciChipsets avivo_pci_chips[] = {
{ PCI_CHIP_RV530_71C2, PCI_CHIP_RV530_71C2, RES_SHARED_VGA },
{ PCI_CHIP_RV530_71C5, PCI_CHIP_RV530_71C5, RES_SHARED_VGA },
{ PCI_CHIP_R580_724B, PCI_CHIP_R580_724B, RES_SHARED_VGA },
{ PCI_CHIP_RV515_7142, PCI_CHIP_RV515_7142, RES_SHARED_VGA },
{ PCI_CHIP_M52_7149, PCI_CHIP_M52_7149, RES_SHARED_VGA },
{ PCI_CHIP_RV530_71C6, PCI_CHIP_RV530_71C6, RES_SHARED_VGA },
{ PCI_CHIP_M66_71D5, PCI_CHIP_M66_71D5, RES_SHARED_VGA },
{ -1, -1, RES_UNDEFINED }
};
void
avivo_get_chipset(struct avivo_info *avivo)
{
switch (avivo->pci_info->chipType) {
case PCI_CHIP_RV530_71C2:
case PCI_CHIP_RV530_71C6:
case PCI_CHIP_RV530_71C5:
case PCI_CHIP_M66_71D5:
avivo->chipset = CHIP_FAMILY_RV530;
break;
case PCI_CHIP_R580_724B:
avivo->chipset = CHIP_FAMILY_R580;
break;
case PCI_CHIP_M52_7149:
case PCI_CHIP_RV515_7142:
avivo->chipset = CHIP_FAMILY_RV515;
break;
default:
FatalError("Unknown chipset for %x!\n", avivo->pci_info->device);
break;
}
}
Then after you replace those two files, compile it like usual, and then it should be able to detect your card.
domzanator
06-23-2007, 08:34 AM
Thank you for making those modifications for me; i replaced the files and compiled it again. Now the problem is that when i start X with the usual resolution 1024x768 my screen goes all wacky. Could this be an issue with the avivo driver or something in my xorg.conf file?
This is part of my Xorg.0.log file:-
(II) Avivo(0): Printing probed modes for output LFP
(II) Avivo(0): Modeline "1360x768"x59.8 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync (47.7 kHz)
(II) Avivo(0): Modeline "1360x768"x60.0 72.00 1360 1408 1440 1520 768 771 781 790 +hsync -vsync (47.4 kHz)
(II) Avivo(0): Modeline "1280x800"x60.0 83.46 1280 1344 1480 1680 800 801 804 828 -hsync +vsync (49.7 kHz)
(II) Avivo(0): Modeline "1152x864"x60.0 81.62 1152 1216 1336 1520 864 865 868 895 -hsync +vsync (53.7 kHz)
(II) Avivo(0): Modeline "1280x768"x60.0 80.14 1280 1344 1480 1680 768 769 772 795 -hsync +vsync (47.7 kHz)
(II) Avivo(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.8 kHz)
(II) Avivo(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(II) Avivo(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(II) Avivo(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(II) Avivo(0): Output DVI-I connected
(II) Avivo(0): I2C device "DVI-I connector 1:ddc2" registered at address 0xA0.
(II) Avivo(0): I2C device "DVI-I connector 1:ddc2" removed.
(II) Avivo(0): EDID for output DVI-I
(II) Avivo(0): Not using default mode "640x350" (vrefresh out of range)
(II) Avivo(0): Not using default mode "640x400" (vrefresh out of range)
(II) Avivo(0): Not using default mode "720x400" (vrefresh out of range)
(II) Avivo(0): Not using default mode "640x480" (vrefresh out of range)
(II) Avivo(0): Not using default mode "640x480" (vrefresh out of range)
(II) Avivo(0): Not using default mode "640x480" (vrefresh out of range)
(II) Avivo(0): Not using default mode "800x600" (vrefresh out of range)
(II) Avivo(0): Not using default mode "800x600" (vrefresh out of range)
(II) Avivo(0): Not using default mode "800x600" (vrefresh out of range)
(II) Avivo(0): Not using default mode "800x600" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1024x768" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1024x768" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1024x768" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1152x864" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1280x960" (hsync out of range)
(II) Avivo(0): Not using default mode "1280x960" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1280x1024" (hsync out of range)
(II) Avivo(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1600x1200" (hsync out of range)
(II) Avivo(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1792x1344" (hsync out of range)
(II) Avivo(0): Not using default mode "1792x1344" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1856x1392" (hsync out of range)
(II) Avivo(0): Not using default mode "1856x1392" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1920x1440" (hsync out of range)
(II) Avivo(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) Avivo(0): Not using default mode "832x624" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1152x768" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1152x864" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1152x864" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1152x864" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1152x864" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1152x864" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1280x720" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1280x720" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1280x720" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1280x800" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1280x800" (vrefresh out of range)
(II) Avivo(0): Not using default mode "1280x800" (vrefresh out of range)
(==) Avivo(0): Default visual is TrueColor
scrninitparam: vx 1360, vy 1360, dw 1408
(II) Avivo(0): VGA connector associated to crtc(0)
(II) Avivo(0): LFP connector associated to crtc(0)
(II) Avivo(0): DVI-I connector associated to crtc(0)
(II) Avivo(0): VGA connector associated to crtc(0)
(II) Avivo(0): crtc(0) hdisp 1360, htotal 1776, hss 1432, hse 1568, hsk 0
(II) Avivo(0): crtc(0) vdisp 768, vtotal 798, vss 771, vse 781, vsc 0
(II) Avivo(0): crtc(0) Clock: mode 84750, PLL 84750
(II) Avivo(0): crtc(0) PLL : div 12, pmul 0x71(113), pdiv 3
(II) Avivo(0): VGA connector associated to crtc(0)
(II) Avivo(0): LFP connector associated to crtc(0)
(II) Avivo(0): DVI-I connector associated to crtc(0)
(II) Avivo(0): VGA connector associated to crtc(0)
(II) Avivo(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(II) Avivo(0): [ScreenInit OK]
(--) RandR disabled
(II) Setting vga for screen 0.
(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
(II) Avivo(0): Setting screen physical size to 359 x 20
Thanks,
Dom
Michael
06-23-2007, 09:22 AM
You do have an error about AIGLX in your log, do you have the following in your xorg.conf?
Section "ServerFlags"
Option "AIGLX" "off"
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
domzanator
06-23-2007, 10:48 AM
Thanks Michael; that worked a treat. After all the reading i've done you would have thought i would have picked that up. Guess it wasn't my modeline after all. Loving the 1280x800 resolution :) I hope my posts help anyone out there with an ASUS F3JP with a X1700 ati card.
The open-source driver seems rather slow when moving a window around it isn't as smooth and is unstable when changing from X to tty1 (shell) and back again; it just locks up. Hopefully i'm guessing these bugs will be addressed and fixed in the near future.
Thanks again for all your help Michael; keep up the fantastic work with this forum and your site. I really enjoy reading all the Reviews.
Regards,
Dom
You do have an error about AIGLX in your log, do you have the following in your xorg.conf?
Section "ServerFlags"
Option "AIGLX" "off"
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
Michael
06-23-2007, 10:51 AM
Thanks Michael; that worked a treat. After all the reading i've done you would have thought i would have picked that up. Guess it wasn't my modeline after all. Loving the 1280x800 resolution :) I hope my posts help anyone out there with an ASUS F3JP with a X1700 ati card.
The open-source driver seems rather slow when moving a window around it isn't as smooth and is unstable when changing from X to tty1 (shell) and back again; it just locks up. Hopefully i'm guessing these bugs will be addressed and fixed in the near future.
Thanks again for all your help Michael; keep up the fantastic work with this forum and your site. I really enjoy reading all the Reviews.
Regards,
Dom
Thanks for your nice words. I hope you stick around the forums.
Regarding the performance, right now the Avivo driver is slower than VESA but its performance will be greatly improved as development progresses so be sure to stay tuned to Phoronix for additional details.
I wait until the avivo driver has better 2d acceleration and official R580XT support. I can wait...
I hope AIGLX support is also coming, never really tried Compiz because of fglrx and not liking XGL.
khakhovich
06-25-2007, 03:05 PM
Hey guys,
while i'm waiting for ATI to release something that works with FC7.... i tried the following instructions about avivo from:
http://www.phoronix.com/scan.php?page=article&item=753&num=1
as all installation goes smooth no errors.... when i do startx... it complain that module avivo is not found.
have i missed anything?
thanks
crumpet
06-26-2007, 07:46 AM
There was some comment in the past that this driver does not work with the apple mactel macbook pro. Is this still the case?
domzanator
06-26-2007, 09:14 AM
Hey guys,
while i'm waiting for ATI to release something that works with FC7.... i tried the following instructions about avivo from:
http://www.phoronix.com/scan.php?page=article&item=753&num=1
as all installation goes smooth no errors.... when i do startx... it complain that module avivo is not found.
have i missed anything?
thanks
Hey mate,
I've got good news for ya the new ATI drivers work on FC7; i got them working ealier today.
Here's something i posted earlier today :p
I've just got it up and running on Fedora 7 after afew alterations:-
Had to downgrade my x server-
su - (if your not already root)
wget http://ftp.cica.es/fedora/linux/core/test/6.91/Prime/i386/os/Fedora/xorg-x11-server-Xorg-1.2.0-6.fc7.i386.rpm
rpm -U --oldpackage xorg-x11-server-Xorg-1.2.0-6.fc7.i386.rpm
Ran the (8.38.6) ati.run file; installed custom with kernel modules:-
Then there was a dependency that i was missing; which i grabbed with yum -
yum install compat-libstdc++-33
Once that is all done just add fglrx into you xorg file and away you go.
Good luck mate,
Dom
Michael
06-26-2007, 09:19 AM
There was some comment in the past that this driver does not work with the apple mactel macbook pro. Is this still the case?
I have yet to see any commits in git for the Avivo driver showing that the Mac Intel ATI GPUs are yet to be supported. Hopefully soon though.
glisse
06-27-2007, 06:35 AM
I have yet to see any commits in git for the Avivo driver showing that the Mac Intel ATI GPUs are yet to be supported. Hopefully soon though.
In fact i wasn't clear enough the macbook pro 15 will work (i got one) but th 17 won't (PLL are bad), when i was saying that mbp 15 was not working it's the external VGA output which is not working thanks to apple which wired the VGA 2 with DVI 1 (i believe they are the only one to do that) so to detect a monitor i have to probe as if it was VGA 1. I want to find an elegant solution to this but i fear i will need to add a workaround for mbp.
crumpet
06-27-2007, 04:26 PM
Ahh Too bad . I have a 17" mbp.... if I can do anything to help in your tests just let me know as I long to have a working open source driver- I did try to install it but all it did was to flash the screen.
UPDATE: I could see that you have made various updates to the git.. so I reinstalled and today( June 28) it works on the 17" mbp! Now I can get the correct screen resolution of 1680x1050 ... something that was not possible with the vesa driver. Many thanks for all the great work you are doing - I wish I could help but I suspect that I am not competent enough.
napopa
07-14-2007, 03:31 AM
Anyone managed to install avivo drivers on ubuntu feisy?
I tried installing it on Debian yesterday, but I had problems with the ./autogen.sh part. I will try it on Fedora 7 today.
domzanator
07-14-2007, 10:34 PM
I tried installing it on Debian yesterday, but I had problems with the ./autogen.sh part. I will try it on Fedora 7 today.
Hi all,
The avivo driver works on fedora 7; i guessing it would work on ubuntu as well. But i wouldn't move to avivo drivers as of it; still get alot of tiering. I would stick to ATI drivers for now.
Peace,
Dom
danielpugh
08-07-2007, 08:33 AM
hi there, ive nearly got the avivo driver working. it compiles fine etc and when i change xorg.conf it seems to be close to working. The screen is distorted - black line in centre of screen and blue gradients on either side.
when i move the mouse i can see white traces. I think the problem is my laptop (lenovo t60 x1300/r500) has a 1024x768 screen (i think others have got it working on higher res screens).
Any ideas. ATI/fglrx and vesa work fine.
Dan
forgot to mention - its fedora8/ rawhide
atippett
08-23-2007, 03:49 PM
I'm not sure what's suppose to work right now but on trying to run compiz or beryl, I get the following BadAlloc error:
atippett@actlap:~$ compiz --replace
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 143 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Serial number of failed request: 16
Current serial number in output stream: 17
/usr/bin/compiz.real: No GLXFBConfig for default depth, this isn't going to work.
/usr/bin/compiz.real: Failed to manage screen: 0
/usr/bin/compiz.real: No manageable screens found on display :0.0
yoshi314
08-23-2007, 03:53 PM
there's no 3d support yet. there's even little 2d acceleration yet.
don't try anything involving 3d yet.
well, it might work if you use mesa for 3d, but i can't guarantee it.
goffrie
08-23-2007, 06:28 PM
Well, I fetched, compiled libpciaccess, avivo...
It works! Well, sort of. The refresh rate is set by default to 58 Hz no matter what I can think of doing in xorg.conf, and causes a very jittery screen. Using the KDE option panel, changing the refresh rate to 75 Hz fixes the problem. There's also a light blue box right in the middle of the screen; it's 64 pixels by 64 pixels. It's semi-transparent, I can see the stuff behind it, but not very much. I'd say about 70% opaque.
Oh, and my resolution is 1280x1024.
Anybody have any idea as to what's causing the blue box? (And the vertical refresh, too :) )
EDIT: Switching from 2.6.22-ck1 to 2.6.22-gentoo-r5 (and having tons of troubles with 2.6.22-suspend2-r1 in between ;) ) fixes the blue box. Weird. Still, I need to manually set the refresh rate. Does anybody know how to force this in xorg.conf?
vBulletin® v3.7.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.