Go Back   openSUSE Forums > Archives > SF Archives > ARCHIVES - Tips, Tricks & Tweaks
Forums FAQ Members List Search Today's Posts Mark Forums Read


ARCHIVES - Tips, Tricks & Tweaks Tips and Solutions for SUSE Linux
(Please do not post questions here)

 
Page 1 of 2 1 2
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 26-Sep-2005, 07:46
Snakedriver
Guest
 
Posts: n/a
Default

Background:
This howto is taken from a successful Opensuse RC1 install on my Sager NP4750 x86-64 laptop with an ATI 9700 Mobility (10) 128 builtin video card starting with the Suse ATI RV350 NP driver original setup.

Our objective is to get to where "fglrxinfo" yields:
laptop:/home/jim # fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON 9700 Generic
OpenGL version string: 1.3.5272 (X4.3.0-8.16.20)
and a good install of the ATI Control Panel on the start tree.
Note: if you get vendor string = Mesa-xx, you are not there yet.

Warning: at the end of this build you are going to have to run "fglrxconfig" and that process is going to require that you know the device you mouse is connected through (mine is /dev/psaux on my laptop), mouse version, keyboard, keyboard layout, and monitor specs, to name a few -- so go dig them out now...

For reference run "glxgears: and note your performance.

Drivers:
Get your ATI drivers here:

https://support.ati.com/ics/support/default...dge&folderID=27

Because Suse runs on Xorg (NOT XFree) we want the X. Org Version 8.16.20 of this driver. Go ahead & download both the ATI Driver Installer and the X.Org 6.8 driver. while you are there read Frequently Asked Questions about the ATI Proprietary Linux Driver & bookmark it -- same with ATI Proprietary Linux Release Notes.

Note: the driver installed using the ATI Driver Installer worked for me, but did not install the ATI Control Panel; therfore, I will continue with the X.Org 6.8 fglrx64 driver install and come back to the ATI Driver Installer at the end.


Preparation:
If you just start out without applying a few tricks, you are going to see a number of errors:

/usr/src/kernel-modules/fglrx/firegl_public.c:124:25: error: asm/ioctl32.h: No such file or directory

******************************
Build of kernel module failed!
******************************

WARNING: Symbol version dump /usr/src/linux-2.6.13-8/Module.symvers
is missing; modules will have no dependencies and modversions.

to name a few. However, once we understand these errors, we can overcome them.

Let's get started:

1st Let's backup the xorg.conf files in both /etc/X11 and /var/lib/sax. Use filemanager in superuser mode and copy them to desktop and rename them xorg.confetc & xorg.confvar. Now should you want to get back to your original setup, all you have to do is copy them back (with the correct filename) & delete the fglrx64 rpm in Yast with a following reboot.

2nd satisfy dependencies
ATI says:
The following 32 bit packages must be installed in order for 64 bit drivers to install and work properly:
· XFree86-Mesa-libGL
· libstdc++
· libgcc
· XFree86-libs
· fontconfig
· expat
· freetype
· zlib
But you don't need the XFree stuff = XFree86-Mesa-libGL & XFree86-libs.
You will also need make, gcc, etc = the requirements to build/comlile apps.

3nd I had updated to kernel-2.6.13-9 and there was no kernel-syms to be found to eliminate the missing Module.symvers error. I went back to kernel-2.6.13-8 (google for a howto) & installed a matching kernel-syms from apt (search this forum for apt).
Install kernel-source to match your kernel (use "uname -r"). If you are starting a clean install these are all on the CD/DVD. One more thing to do while we are here:
in a term as root, create a sym link between your kernel and kernel-source:
laptop:/home/jim # cd /usr/src/linux
laptop:/usr/src/linux # ln -s /linux-2.5.13.8 /usr/src/linux
ln: creating symbolic link `/usr/src/linux/linux-2.5.13.8' to `/linux-2.5.13.8': File exists


4th Let's aply a trick so that we dont get: error: asm/ioctl32.h: No such file or directory
Use filemanager superuser mode & copy ioctl32.h from /usr/src/linux-2.6.13-8/include/linux to /usr/src/linux-2.6.13-8/include/asm-x86_64
then, in a term as root:
cd /usr/src/linux-2.6.13-8
create sym link
ln -s /usr/src/linux-2.6.13-8/include/asm /usr/src/linux-2.6.13-8/include/asm-x86_64

We are almost there.

5th: In a term as root:
laptop:/home/jim # cd /usr/src/linux
aptop:/usr/src/linux # cp ../linux-obj/x86_64/default/.config .
laptop:/usr/src/linux # cp ../linux-obj/x86_64/default/Module.symvers .
laptop:/usr/src/linux # make prepare
laptop:/usr/src/linux # rpm -Uhv /home/jim/suse10/fglrx64_6_8_0-8.16.20-1.x86_64.rpm
Preparing... ########################################### [100%]
1:fglrx64_6_8_0 ########################################### [100%]
laptop:/usr/src/linux #
I show you this because it takes a while after the second line writes, for the process to build -- so be patient & wait untill you get back to "laptop:/usr/src/linux #".

We are getting closer.

6th:
In a term as root run:
"fglrxconfig" and use the info you gathered way back at the beginning.
Caution: when you say yes to the last line, it is going to overwrite xorg.conf; so be sure of all your entries -- otherwise just close the window & it will just go away with no affect on your system; then you can get the required info & do it for real.

Lastly:
reboot

Note: There is no need to run "sax2 -r -m 0=fglrx -b /usr/share/doc/packages/fglrx/sax2-profile as stated somewhere in the ATI instructions, as sax2 doesn't work with this rpm version. If you don't get 3D, try "sax2 -m 0=fglrx", I expect it to crash; but it may turn on the module anyhow.

Now let's check our system:

Run:
"fglrxinfo" we are looking for:
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON 9700 Generic
OpenGL version string: 1.3.5272 (X4.3.0-8.16.20)
If you get vendor string = Mesa-x.x, you made a mistake somewhere (or I did in this howto).

Go to start & see if you have the ATI Control Panel.

Run "glxgears": and note your performance increase (mine went from 50-70 to 2606 FPS).

Go to CD/DVD or apt & install some 3D games; run them.
Of course we are wanting them to load without the 2D warning & no artifacs during play.

Welcome to 3D.

Thanks to everyone at this forum who helped me find the missing elements. Come on SuSE10, we're ready for you now!

Have fun

PS: I will return to address the ATI Driver Installer rpm install.
Hope that I havn't missed anything, if so we'll fix it...
Maybe ATI & Suse will have this all fixed in SuSE10 & we all won't have to go thru all this again.
  #2 (permalink)  
Old 26-Sep-2005, 08:02
harryc
Guest
 
Posts: n/a
Default

Thanks Snakedriver, well done!
  #3 (permalink)  
Old 26-Sep-2005, 13:14
Snakedriver
Guest
 
Posts: n/a
Default

Addendum: Address the ATI Driver Installer rpm install

I tried this first & got it to work in 3D, but, it did not generate the ATI Control Panel on the start tree. If you wish to try it, have a go!

Do:
laptop:/home/jim/suse10 # /home/jim/suse10/ati-driver-installer-8.16.20-x86_64.run --get-supported
Creating directory fglrx-install
Verifying archive integrity... All good.
Uncompressing ATI Proprietary Linux Driver-8.16.20........................................... .................................................. .................................................. .................................................. .................................................. .................................................. .........................
==================================================
ATI Technologies Linux Driver Installer/Packager
==================================================
List of supported packages:
Debian/woody
Debian/oldstable
Debian/3.0
Debian/sarge
Debian/stable
Debian/3.1
Debian/etch
Debian/testing
Debian/sid
Debian/unstable
RedHat/RHEL3_64a
RedHat/RHEL4_64a
SuSE/SLES9-AMD64
SuSE/SUSE91-AMD64
SuSE/SUSE100-AMD64
SuSE/SUSE92-AMD64
SuSE/SUSE93-AMD64
Ubuntu/warty
Ubuntu/4.10
Ubuntu/hoary
Ubuntu/5.04
Ubuntu/breezy
Ubuntu/5.10
Removing temporary directory: fglrx-install
laptop:/home/jim/suse10 #


Do:
laptop:/home/jim/suse10 # /home/jim/suse10/ati-driver-installer-8.16.20-x86_64.run --buildpkg SuSE/SUSE100-AMD64
Creating directory fglrx-install
Verifying archive integrity... All good.
Uncompressing ATI Proprietary Linux Driver-8.16.20........................................... .................................................. .................................................. .................................................. .................................................. .................................................. .........................
==================================================
ATI Technologies Linux Driver Installer/Packager
==================================================
Generating package: SuSE/SUSE100-AMD64
/tmp/fglrx
Package /home/jim/suse10/fglrx64_6_8_0_SUSE100-8.16.20-1.x86_64.rpm has been successfully generated
Removing temporary directory: fglrx-install
laptop:/home/jim/suse10 #
Note: this will generate the rpm in the directory in which you issued the command!

Then do every thing as above down to where I installed the fglrx64* rpm.
laptop:/usr/src/linux # rpm -Uhv /home/jim/suse10/fglrx64_6_8_0_SUSE100-8.16.20-1.x86_64.rpm
Preparing... ########################################### [100%]
1:fglrx64_6_8_0_SUSE100 ########################################### [100%]
and it will take off (unlike the above install) and build the fglrx (and other?) modules in the term like:
/usr/src/kernel-modules/fglrx /
make -C /usr/src/linux modules SUBDIRS=/usr/src/kernel-modules/fglrx
etc.

Then, pickup again at step 6 above & you should have your 3D.

Now all the readme's say to run "sax2 -r -m 0=fglrx -b /usr/share/doc/packages/fglrx/sax2-profile", but it crashed on me every time. Upon reboot I had 3D.

Again, this install failed to produce the ATI Control Panel in the start tree.

Have fun...
  #4 (permalink)  
Old 26-Sep-2005, 13:56
afaiq
Guest
 
Posts: n/a
Default

I have also, successfully installed the ATI drivers on my HP zv6000 laptop on SuSE OSS10 x86-64. Went through a number of issues that Snakedriver has outlined here. It also appears that for HP and Compaq laptops (including zv6000), you have to disable the 'sideport' in the BIOS, before ATI drivers will work.

I also do not see the ATI control panel in the menu tree. Snakedriver, do you know the command for it? maybe typing the command in xterm is the solution
  #5 (permalink)  
Old 26-Sep-2005, 14:18
Snakedriver
Guest
 
Posts: n/a
Default

afaiq,
"I also do not see the ATI control panel in the menu tree. Snakedriver, do you know the command for it? "
Sorry, I don't.

That's why I went with the driver other than ATI's suse100 rpm built with their installer.

"you have to disable the 'sideport' in the BIOS"
I guess ATI wants that IRQ.

Have fun.
  #6 (permalink)  
Old 14-Oct-2005, 11:28
heydi
Guest
 
Posts: n/a
Default

Hi,
First I'm quite impressed by your ability to find all those infos and tricks.

Well, I still can't get my card working and I hoped you might help me.

I'm running Suse 10.0 (from the downloaded Eval-DVD) on an AMD 64 PC. My graphic card is an Asus EAX600 XT (PCI-Express bus), which I presumed to be supported by the ATI drivers, supposed to support the ATI X600 series.

I tried to install the drivers several ways, including by rebuilding the package from the fglrx....run application, but I always get the same result:
X will start apparently normally (the screen definition goes to whatever I configured with fglrxconfig and I see the mouse arrow), until... I only touch the mouse or the keyboard! Then it crashes and starts again, and so on...

I don't know really where to go and get info about the reasons of the crash.

Would you have any idea?

Thanks in advance.
  #7 (permalink)  
Old 14-Oct-2005, 13:25
Snakedriver
Guest
 
Posts: n/a
Default

fglrxconfig configures both the keyboard and mouse along with the fglrx (ATI) module.

Make sure that you enter all the selections for you keyboard and mouse correctly or I guarantee you they won't work. The number shown @ each Q&A needs to be answered to match the list of 8 to 10 options immediately above that line -- plus, you need to type in the device your mouse is connected to (mine was /dev/psaux), and so on.

Run "fglrxconfig" again; try to get all your entries to match your hardware.

If you can't use the mouse or keyboard, you may have to reinstall or use Knoppix to replace the file fglrxconfig overwrote -- if you are new to linux, I recommend reinstalling.

Good luck...
  #8 (permalink)  
Old 14-Oct-2005, 14:53
Snakedriver
Guest
 
Posts: n/a
Default

I was in a hurry while ago, thanks for the comments -- comes from being willing to mess around, reading the forums & google/linux.

Have fun...
  #9 (permalink)  
Old 14-Oct-2005, 15:09
heydi
Guest
 
Posts: n/a
Default

Thanks for your quick answer.
However I didn't solve the problem.
My mouse seems to be connected to /dev/input/mice and the keyboard is recognized as pc102 according to xorg.conf (the previous file generated by Sax). Till there I was OK.
My mouse though is recognized by Sax as a PS2++ Logitech Wheel mouse, which is not exactly the case but works. I assumed the good choice to enter in fglrxconfig was PS2 generic wheel mouse or Logitech mouseman (I tried both).
I'm more unsure about the internal AGPGART thing.?...(the graphic card is connected via PCI-Express).

If I use the sax2 -r -m 0=fglrx... command, then I have the same result but I get a sax.log file where I can find :
' (II) fglrx(0): driver needs X.org 6.8.x.y with x.y >= 0.0
' (II) fglrx(0): detected X.org 6.8.2.0
' (WW) fglrx(0): ***********************************************
' (WW) fglrx(0): * DRI initialization failed! *
' (WW) fglrx(0): * (maybe driver kernel module missing or bad) *
' (WW) fglrx(0): * 2D acceleraton available (MMIO) *
' (WW) fglrx(0): * no 3D acceleration available *
' (WW) fglrx(0): ********************************************* *
and further a list of errors like the two following:
' Symbol __glXActiveScreens from module /usr/X11R6/lib64/modules/drivers/fglrx_drv.o is unresolved!
' Symbol DRIGetDrawableInfo from module /usr/X11R6/lib64/modules/drivers/fglrx_drv.o is unresolved!
further, the keyboard and mouse are successfully loaded,
and in the end I finally get :
'14-Oct 21:16:23 <X> [ GLX Info:
' name of display: :0.0
'
' visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
' id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
' ----------------------------------------------------------------------
' 0x21 24 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None
' 0x22 24 dc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None
']
'xapi: Fatal IO error: client killed
'kill: 7577: No such process
'14-Oct 21:16:26 <X> die hard on pid: 7577
'kill: 7577: No such process

So in the end I don't understand where it crashes.
And I can't find the fglrx_drv.o file anywhere. I had no error message during installation of the rpm though.

By the way, rather than using Knoppix, about the xorg.conf, I always make a copy that I can retrieve whatever happens using init 3 as boot option.

Any other idea?
  #10 (permalink)  
Old 14-Oct-2005, 15:24
Snakedriver
Guest
 
Posts: n/a
Default

Let's try this:
you have installed the ati xorg rpm (not the Xfree driver)
run fglrxconfig
close out of everything
reboot
when you get back to desktop
in a term "fglrxinfo"
If it says ATI &
driver fglrx
you have 3D

forget sax2, if you read the fine print in the driver howto, it says sax2 doesn't work with this driver.

It was a snap for me with suse 10...
 
Page 1 of 2 1 2

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2