i am new to linux plateform and installed 11.2 under KDE an hour ago.
when the system booted for the first time , the resolution was not optimum. my monitor is samsung 2033 (1600x900) and gfx card (ATI HD 4850).
i downloaded the ATI 9.10 driver for linux and installed according to the instructions given in the pdf.
and when i rebooted the pc again , i see a message saying that kwin is unstable and is crashed !:â(
moreover , its not showing the title bar on the windows that i open
so plz help me solve this problem and i request you to give the solution step by step as i m a noob !
Note :- i had installed 11.1 earlier for 10-15 days but i did not have gfx card that time ! Bought a new pc
When installing the previous 9.10, assuming you installed âthe hardwayâ, then in one of the steps you installed the driver package with " rpm -Uvh fgl*.rpm ".
So now you need to remove that package. You can do so by typing with root permissions:
rpm -e $(rpm -qa '*fglrx*')
The instruction is in the ATI/The Hard Way - openSUSE link, but I concede it is a pain to read all that and figure out just what applies and what does not apply.
Launch the Terminal Application/Window and navigate to the ATI Proprietary Linux
driver download.
Enter the command sh ./ati-driver-installer-9-10-x86.x86_64.run to launch the ATI
Proprietary Linux driver installer.
after installing it i did ,
Launch the Terminal Application/Window and run:
For versions of X.Org newer than 7, /usr/bin/aticonfig --initial to configure the
driver for your ATI product.
and for uninstalling :-
Launch the Terminal Application/Window and navigate to the /usr/share/ati folder.
With superuser permissions, enter the command âsh ./fglrx-uninstall.shâ.
Reboot
now , To restore the original Xorg configuration file:-
Locate backup configuration files: ls /etc/X11/xorg.conf.original-*
Take the latest version with the highest number and copy it over the existing
xorg.conf file: cp /etc/X11/xorg.conf.original-<number> /etc/X11/xorg.conf
in my case the number was â0â and finally when i rebooted the system it failed to load the gui !
now should i continue with the hard way guide in the present state or is there something that i should do before continuing ?
dk0505, sorry to read of your difficulties on your first openSUSE attempt.
The proprietary ATI driver is not very mature when it comes to openSUSE-11.2 (it works well with 11.1) and unfortunately there have also been reports of the open source ATI driver having some problems with 3D/special desktop effects with some users on 11.2.
When I read your post, one thing that puzzles me very much is you make no mention of installing the proprietary driver package with " rpm -Uvh fgl*.rpm " (where you need to substitute the exact name of the rpm) where that rpm is built by running the ATI proprietary " .run" file . When the ATI "ati-driver-installer-9-10-x86.x86_64.run " is launched, my recollection is it will create an "fgl.rpm" file. That file must then be installed for the driver to be installed. And ONLY after that rpm file is installed, should one run " aticonfig --initial " âŚ
It does appear to me that you missed a step.
Now I have no idea as to what the effect is of running " aticonfig --initial " without first installing the rpm. I hope it is harmless, but I donât know.
Iâm not sure this post is helpful, but I hope it is. Please advise as to what you did wrt the fgl*.rpm ?
Iâm no ATI expert. We have 2 PCs in our place that use ATI hardware
my wifeâs PC (running openSUSE-11.2), which has an ATI RV280 (equivalent to a Radeon 9200 Pro), on which I only have used the âradeonâ open source driver, and
our Dell Studio 1537 laptop (running openSUSE-11.1) which has an ATI Radeon 3450 HD graphics, on which I currently use the proprietary ATI graphic driver, that I used installing âthe hardwayâ per the link I provided
I had âassumedâ one had to follow all steps in âthe hardwayâ method. If it is possible to skip those steps without any risk, then that is new to me, BUT as noted, I am no ATI expert.
Please see the installer instructions. These are the instructions that I followed (the driver ver was 9.10 obviously) for installing and then uninstalling(when it didnt work !)
Those instructions bring up a GUI, where possibly as part of the GUI the rpm is installed? I do not know, as I have never followed that method.
The âhardwayâ method specifies command line options with the command ⌠ie assuming kernel-source, kernel-syms, linux-kernel-header, and the baseline development pattern are installed, and assuming one is in run level 3 with root permissions, and assuming oneâs terminal is in the directory where the .run installer is located, one types something like (for a 64-bit openSUSE-11.2):
mv /etc/X11/xorg/conf /etc/X11/xorg.conf.mybackup
rpm -e $(rpm -qa '*fglrx*')
sh ati*.run --listpkg
sh ati*.run --buildpkg SuSE/SUSE112-AMD64
rpm -Uvh fgl*.rpm
ldconfig
aticonfig --initial
and then restarts.
Those commands need to be modified as appropriate to fit in with the specifics of oneâs situation. ⌠and again, I am no expert.
this thread should be applicable to the discussion here, because it will illuminate the difficulty that everyone is having, kudos to NicoK for taking the time to research it.
Seems to be a syntax change in the version of rpm that 11.2 ships with, and ATI simply missed it. Rpm v4.7.1 also drops the --repackage option which i miss.
a machine that has a 3850HD card runs better than ever before with the new drivers, so i hope this fix gets to be available for the masses.
<kernel-flavor> depends on your installed kernel. Check with
âuname -râ for installed default/smp/bigsmp kernel. Use âsax2 -râ
for X.Org configuration.ââ
And as per the guide , if I do the above i dont have to do manual driver package generation and installation right ?
ErrâŚplease dont mind the silly questionsâŚI already mentioned that i m a new user !:shame:
No, I do not recommend installing the ATI driver via yast at this time. That is because last I had heard they had not yet been built for 11.2.
Typically, for the proprietary ATI driver, there are two methods of installing the driver (in fact there is likely more, but for our purposes we will ONLY talk about these two). These two methods are to either:
(a) Install a software repository (where the repository contains the ATI driver) to the YaST/zypper repository list, and then install a pre-compiled rpm of the ATI driver, or
(b) custom build the ATI driver (which is called âthe hardwayâ ) by running the binary .run file. When that file is run, it creates an rpm with âfglrxâ in the file name, where the âfglrxâ rpm is then installed before the aticonfig program is run. I outlined this âhardwayâ method above.
I do not recommend method (a) at this time, because last I had checked, the latest ATI driver was not yet built as a pre-compiled rpm for openSUSE.
Now to custom build a driver (which is the âhardway methodâ (b) above) , one needs to 1st go to YaST > Software > Software Management and change the âfilterâ to âpatternâ and install the Base Development pattern. That is a big download and will take a while. Once that is complete, one then needs to change the âfilterâ to âsearchâ and search for and install kernel-source, kernel-syms, and linux-kernel-headers.
Then once those are done, one can proceed with the hardway installation that is outlined above, and also outlined where the text in ATI/The Hard Way - openSUSE starts reading like âŚ
OR
You can continue with the following instructions for manual driver package generation and installation...
**Step 1 - Acquire the latest ATI driver**
Go to ATI's website and download the installer -- Latest as of December 21st, 2008 -- Catalyst 8.12.
NOTE: Latest and all previous drivers for 32-bit Linux may be found at this ATI website page, and for 64-bit at this page.
**Step 2 - Generate Distribution Specific Driver Package**
You may want to use Sax2 to create default xorg.conf by executing the command:
..................
.................
.............. etc ..............
In my case I always skip the âsax2 -aâ step, as I do not believe it adds anything.
my apologies for making a confusing issue even more difficult, trying to make a rpm the hard way will surely fail unless Nicok patch or the manual equivalent is done.
oldcpu is, as usual, correct in advising that the radeonhd driver is a good way to get you up and running without much difficulty.