LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Can't get my ATI Radeon XPRESS vidcard working right (http://www.linuxquestions.org/questions/slackware-14/cant-get-my-ati-radeon-xpress-vidcard-working-right-439553/)

BCarey 04-27-2006 10:05 PM

Can't get my ATI Radeon XPRESS vidcard working right
 
Hi all,

Trying to get the video card working on an HP dv5000 with slack 10.2 and a custom 2.6.13 kernel

I've installed the ati drivers and done a basic config with aticonfig. It seems to start up fine, but startx mutters in the background:


Symbol DRIGetDrawableInfo from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol DRIGetDeviceInfo from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!

and fglrxinfo gives:

Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)

I think it's supposed to mention the ATI card here when it's all set up right.

All the other posts on the subject mention fglrxconfig, which i don't seem to have. They are also all pretty distribution-specific involving things like sax and yast. So I think I need help from a slacker on this one.

Thanks,
Brian

187807 04-27-2006 10:19 PM

What does "custom 2.6.13 kernel" mean? Did you compile it yourself?

If you did compile it yourself double check to be sure that you selected the DRI choice (even if you don't choose any of the cards in the sub-menu choose the DRI choice).

Now, depending on which X you are using the X config file should be /etc/X11/xorg.conf but you MIGHT have an older X where it's called something like XF86config or something like that.

In either case, edit the appropriate file with text editor. You are looking for section that looks like this:

Code:

Section "Device"

    #VideoRam    131072
    # Insert Clocks lines here if appropriate
    Identifier    "** NVIDIA (generic)                  [nv]"
    Driver        "nvidia"
EndSection

Yours will look different but you should have a line that starts with "Driver" like mine above. Within the quotes you should try "fglrx". If you've got your drivers installed correctly it might work. If not just revert to the option you are using now while you are figuring it out. Another "Driver" option might be "ati" as I believe some X stuff now comes with native ati (limited, I believe) drivers.

Sorry can't help you more. Just couple things to try though. you will need to restart your X session after modifying the config file to see if the effects work. There are other options in the X config file involving loading GLX and DRI and another or two I can't remember that different manufacturers might use differently. Just have to research and try.

{edit: vagueness}

Good luck. You'll get it figured out.

187807 04-27-2006 10:20 PM

Oh, and if it wasn't a kernel that you personally compiled then you will want to install the kernel-headers for that kernel as well. Then rerun the ati installer and try the above mentioned.

BCarey 04-27-2006 10:33 PM

Thanks for the quick reply!

Yes, I meant that i compiled it myself. Do you know where the DRI option is? I couldn't find one.

I'm using X 6.8.2, I've got a section in my xorg.conf pointing to fglrx, and lsmod shows that a module called fglrx is loaded.

Any other ideas?

Thanks,
Brian

187807 04-27-2006 10:50 PM

I'm using 64-bit and a different kernel version but it should be in the same or a similar location for your config. Under "Device Drivers"-->"Character Devices" you might see something like I have pasted below.

I'll keep thinking about other problems that might be occuring. I've had the very issue you describe before but downloading a new kernel source, untarbzip2ing and then making and installing, then installing nvidia drivers again worked fine for me with the DRI issue.

anyway, here's the section I was talking about:


Code:

Arrow keys navigate the menu.  <Enter> selects submenus --->.  Highlighted      │
  │  letters are hotkeys.  Pressing <Y> includes, <N> excludes, <M> modularizes      │
  │  features.  Press <Esc><Esc> to exit, <?> for Help, </> for Search.  Legend:[*] │
  │  built-in  [ ] excluded  <M> module  < > module capable                          │
  │ ┌─^(-)─────────────────────────────────────────────────────────────────────────┐ │
  │ │ < > Applicom intelligent fieldbus card support                              │ │
  │ │    Ftape, the floppy tape device driver  --->                              │ │
  │ │ --- /dev/agpgart (AGP Support)                                              │ │
  │ │ < >  Intel 440LX/BX/GX, I8xx and E7x05 chipset support                      │ │
  │ │ <*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)          │ │
  │ │ < >  3dfx Banshee/Voodoo3+                                                  │ │
  │ │ < >  ATI Rage 128                                                          │ │
  │ │ < >  ATI Radeon                                                            │ │
  │ │ < >  Matrox g200/g400                                                      │ │
  │ │ < >  SiS video cards                                                        │ │
  │ │ < >  Via unichrome video cards                                              │ │
  │ │ < >  Savage video cards                                                    │ │
  │ │ < > ACP Modem (Mwave) support                                                │ │
  │ │ < > RAW driver (/dev/raw/rawN) (OBSOLETE)                                    │ │
  │ │[*] HPET - High Precision Event Timer

Good luck

187807 04-27-2006 10:51 PM

btw, might as well grab a 2.6.16.11 source at kernel.org. It's what I'm using now (on 64-bit though) but should work for you, too. nvidia has always been great to me for driver stuff. I mean as far as getting them working with DRI, etc.

BCarey 04-27-2006 11:07 PM

I have also had no problem with NVidia drivers once I got the hang of them. This ATI driver is a little bit of a pain though.

I am building DRI as a module. I am not sure whether it is loading properly. An lsmod doesn't show any module called DRI. Do you think that I should build it into the kernel?

Thanks,
Brian

187807 04-27-2006 11:30 PM

Quote:

Originally Posted by BCarey
I have also had no problem with NVidia drivers once I got the hang of them. This ATI driver is a little bit of a pain though.

I am building DRI as a module. I am not sure whether it is loading properly. An lsmod doesn't show any module called DRI. Do you think that I should build it into the kernel?

Thanks,
Brian

You could try it. I don't usually build stuff as modules, but that's just the way I've always done it. I build stuff in. I don't know why I just do. I know I use stuff that I choose to enable so I just get it in there instead of doing modular stuff.

Just out of curiosity, how are you building this kernel?

That is, I'm guessing you either make xconfig or make menuconfig....then do you just do plain "make" or do you do "make bzImage"?

If you just do "make" it should "build" the modules in stage 2 of the make process there. I always, after doing plain make as regular user, go root and issue the following (your "arch" may differ):

Code:

# make modules_install
# cp arch/x86_64/boot/bzImage /boot/linux-2.x.y.z

Then I modify my /etc/lilo.conf adding the new linux-2.x.y.z at top for default then reboot.

IF you do "make bzImage" then you will probably have to do (as root):

Code:

# make modules
# make modules_install
# cp arch/x86_64/boot/bzImage /boot/linux-2.x.y.z


187807 04-27-2006 11:34 PM

Sounds like you know what you are doing, but just to be sure you may do a:

Code:

$ uname -a
to verify that you are, in fact, using the kernel that you compiled and not another version.

BCarey 04-28-2006 08:53 AM

I do:

make menuconfig
make modules_install

then I copy my kernel and configure lilo. Sometimes I use initrd, other times not.

I have also confirmed my kernel with uname.

Brian


All times are GMT -5. The time now is 05:33 PM.