I have upgraded my laptop to a gateway T1628 it has 3 gig ram 250 hdd amd turion 62*2 this laptop is in nice shape. but there seems to be some minor issues.I have the audio working fine using Kaffeine i can play music and watch movies both just fine, I cannot seem to get the ATI drivers loaded for the graphics or the system, for now i have settled forthe default loaded by suse 11.1, any idea as to how to get yast to load the drivers i am looking for this will complete this laptop configuration, or should i leave it alone. I can also burn using k3b. and i cannot use the webcam do to lack of know how. but that is another forum problem…any feedback as to this problem will help… THANK’S
Did you check if your card has a driver listed at the ATI site. I couldn’t check for you, the site was down for me.
caf4926 adjusted his/her AFDB on Monday 10 Aug 2009 06:16 to write:
>
> Did you check if your card has a driver listed at the ATI site. I
> couldn’t check for you, the site was down for me.
>
>
I managed to get to the site ( after a bit of a lag )and your card needs
the legacy drivers:;
This is a link for the 32/64bit ones:;
http://support.amd.com/us/gpudownload/linux/9-2/Pages/radeon_linux.aspx
The ones in the SuSE repo and the oneclick will probably b0rk you GUI.
You will have to do it the “Hard Way” ™
Here is the wiki article on installing the hard way.
It looks a lot harder than it is.
It is just a case of making sure you have the kernel source, the compiler
and the required tools installed ( see list on wiki )
And also make sure your system has been updated with yast to the latest of
everything including the kernel, this is needed because doing it the hard
way means you have to re-install after a kernel update ( just a matter of
3/4 commands in a terminal)
Then also read the installation note on the ATI site.
One main thing to note and it is important
Do NOT use sax to configure the card, you can only use sax if you use the
repos or the oneclick, it is stated in the ATI docs and is there for a
reason.
Now if you want to install these then do not panic, if you get stuck or want
a walk through before hand just holler.
Just d/load the drivers and shout.
And believe me it is a lot easier than it looks and sounds.
HTH
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
Well, i tried the hard way and it failed badly i had to reload my os and all of my files, i must have done something wrong somewhere i will try again when i have some time to work with it more right now everything else is working fine and i am not that pressed to load these drivers. the graphics are choppy in some games, but i am satisfied with the system overall.
i hope that ATI will get the drivers fixed and make them easy for someone to load them
great article and thanks for the link’s they are a lot of help…
OK i tried before to install these drivers,but i did fail and the problem was missing packages here is what i missed.
xfree86-mesa-libgl
xfree86-libs
using software management i cannot find these packages can anyone guide me in the right direction. i have tried all i can think of to locate them…
these were on the list from ATI to load the drivers to make the RPM for suse11.1
TKS1125 adjusted his/her AFDB on Friday 14 Aug 2009 07:16 to write:
>
> OK i tried before to install these drivers,but i did fail and the
> problem was missing packages here is what i missed.
>
> xfree86-mesa-libgl
> xfree86-libs
>
> using software management i cannot find these packages can anyone guide
> me in the right direction. i have tried all i can think of to locate
> them…
> these were on the list from ATI to load the drivers to make the RPM for
> suse11.1
>
>
If you are doing it the “Hard Way” then you do not need to produce an rpm of
the drivers.
Just let it compile and install the drivers as is.
The reason being that if you use the rpm way and there is a kernel update or
patch then the rpm will have to be recreated against that kernel again and
re-installed, meaning an extra step.
If there is such an update then the procedure would be something like:
Logout of KDE/Gnome select “console login” from login manager screen menu,
login as root:
init 3
cd < to-where-ever-you-put-the-drivers>
sh ./<driver-name-and-version>
<ok through the build and install>
init 5
Note you do not need to run the ati-config script if you have done it once
already on initial install of the propriety drivers, also note there is no
need to reboot.
If you have problems getting back to a GUI for whatever reason then drop
back to a root login in runlevel 3 and then run:
sax2 -r -m 0=vesa
This will recreate a standard xorg.conf then run the ati-config script to
generate the need edits to the xorg.conf file and try init 5 again.
Also when there are newer drivers released ( approx every month ) then you
will have to go through the process again.
If on the other hand you just follow the normal build and install then it
cuts out the not needed step.
The “normal” install procedure does not require the libs that the message is
looking for.
Unless you are compiling an rpm to distribute for other machines of the same
arch and hardware it is just an extra step that you do not need.
HTH
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
baskitcaise adjusted his/her AFDB on Friday 14 Aug 2009 11:01 to write:
> init 3
> cd < to-where-ever-you-put-the-drivers>
> sh ./<driver-name-and-version>
> <ok through the build and install>
> init 5
>
>
> Note you do not need to run the ati-config script if you have done it once
> already on initial install of the propriety drivers, also note there is no
> need to reboot.
Edit:
should read:
Note you do not need to run the “aticonfig” script if you have done it once
already on initial install of the propriety drivers, also note there is no
need to reboot.
Don`t know why I was putting a spurious “-” in the aticonfig, sorry for
confusion.
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
I could really use some advise, i downloaded the ATI drivers from the site, when i cd / to the location and enter the sh./ command nothing happens at all. i made sure that this is the correct driver and not the one click and i get no response at all, any advise, there has got to be something i am doing wrong. can anyone help…
Instructions here:
https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_cat92-inst.pdf
But you should run the installer from level 3.
Download the driver first and put it in /home/username
Login as user at level 3 then switch to su
Usually to run the installer type:
sh packagename
(if you type the first couple of letters of the installer package name and hit TAB it will auto complete)
OK, i followed the instructions and did the install very carefully and the system has blacked out i will probebly have to go back to the default for whatever reason unless there is something i missed.
You should always be able to get back with vesa like this:
Pause the boot by moving the down arrow, then back up to the default boot. But now press backspace, it should delete any text where you can see VGA=…etc
Remove all text and now type just the number:
3
and hit enter
at the login type your user name and then password
now type:
su
then the root password
now type this:
sax2 -r -m 0=vesa
(N.B. the 0 is a zero not a letter)
now reboot: type: reboot
if you don’t get a gui login
login as user at cli and try this at the cli
startx
I am now at the point to where i think this could be a kernel issue as well even the previous try has failed to solve the issue these ati drivers are truely buggy.
When you boot the machine you get a boot menu do you?
How many boot options are there. And can we assume you tried the failsafe boot.
If you can boot and login to level 3 you should be able to do something. You can actaully run yast from level 3 if you go su and type: yast
You really need to tell us why you think it failed and what you are seeing.
TKS1125 adjusted his/her AFDB on Thursday 20 Aug 2009 06:16 to write:
>
> I am now at the point to where i think this could be a kernel issue as
> well even the previous try has failed to solve the issue these ati
> drivers are truely buggy.
>
>
What makes you say the kernel/ATI`s are buggy, is there something in the
logs to point to that?
The only time it could be a kernel issue is if you are running a kernel
version above 2.6.27 ( actually the newer drivers released a couple of days
ago support 2.6.29 ) if you are running a kernel above the default .27 then
you will not be able to get the drivers to work because they do not support
your graphics chipset as it uses the older legacy drivers.
If you have the drivers installed then you can get rid of them by running
the uninstall script.
Then go back to the original/vesa drivers using sax.
Once you get a default xorg.conf re-install the drivers.
Do not use sax to configure, use the aticonfig --initial command and that is
all you need to do, once back in your wm/de you use the catalyst application
to configure.
It is as simple as that.
HTH
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
I had to work a little harder this trip, but i have the system back before the crash and now i am doing some research on what is going on.for some reason unknown the system crashed three times and trying several different ways to load these drivers has failed is it possible that i do not have the correct drivers for this machine and how do i find out,can someone tell me, i know there is a command in the terminal that will show this…
TKS1125 adjusted his/her AFDB on Thursday 20 Aug 2009 14:36 to write:
>
> I had to work a little harder this trip, but i have the system back
> before the crash and now i am doing some research on what is going
> on.for some reason unknown the system crashed three times and trying
> several different ways to load these drivers has failed is it possible
> that i do not have the correct drivers for this machine and how do i
> find out,can someone tell me, i know there is a command in the terminal
> that will show this…
>
>
If ypu go to the AMD/ATI site and use the driver d/loader options then it
will point you to the correct drivers as I have been saying all along:
Now those drivers are the last version to support your chipset, note they
are in the list.
Read the installer, have a look round the group and read what has been
posted before in this thread and install them.
And do not use sax to configure.
The reason I keep banging on about sax is that it will break any config you
have for the ATI drivers and cause no amount of problems, it is easy to fix
but when someone tries to do it without knowing about it and uses sax then
they blame the system and SuSE and everybody and his cat, but it is stated
in the installer not to run sax.
HTH
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
I apoligize for the blame, I do not blame SUSE there is something that is causing the problem and i am now looking into it deeper, i have never had a problem configuring SUSE before. I usually have a system up and running fully configured within a few hours i am looking into a hardware issue as well, i followed each step carefully and tried three different ways and i have produced the same results. therefore i have ruled out SUSE as the main problem
i will keep posting the progress as i love a good challenge and when it is fixed i will know exactly what is needed to deal with such problems…
I also want to say you folks who do a lot of helping are very knowledeable and are a great part of the SUSE forum.
TKS1125 adjusted his/her AFDB on Friday 21 Aug 2009 05:36 to write:
>
> I apoligize for the blame,
Hey no probs, maybe I was a little touchy as well
> I do not blame SUSE there is something that
> is causing the problem and i am now looking into it deeper, i have never
> had a problem configuring SUSE before. I usually have a system up and
> running fully configured within a few hours i am looking into a hardware
> issue as well,
What sort of hardware prob?
One thought that has just come to me is did the install go OK?
I am specifically asking did you have to do anything special to get the
install going?
Like disable ACPI or load any 3rd party drivers before you could get to the
actual installation part?
I had a problem with one machine that had to have ACPI disabled to install
SuSE ( cannot remember which version ) otherwise it would not load the
initial kernel off the install DVD, I found afterwards that this had
persisted after the install and had been appended to the boot line and so I
lost some functionality.
I fixed it quick by just removing the line in the grub menu and so cannot
remember what/why/when this happened sorry.
But something like that can throw a spanner in the works.
> i followed each step carefully and tried three different
> ways and i have produced the same results. therefore i have ruled out
> SUSE as the main problem
> i will keep posting the progress as i love a good challenge and when it
> is fixed i will know exactly what is needed to deal with such
> problems…
If you need a hand or just want to bounce some ideas around then just
holler, if I am not here then others will jump in, but hopefully I should be
here for the next couple of days ( BST )
> I also want to say you folks who do a lot of helping are very
> knowledeable and are a great part of the SUSE forum.
>
>
Aww shucks, stop it, you will make us blush
HTH
Cheers
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
OK, i did not have to do anything different, the install went fine and there were no hangups at all i did see some lines of text when the install was taking place like you would see in the terminal but i figured that was normal…and i could not tell you what it said due to the speed…
OK, i have tried several different methods of insall on this system for ATI, and have produced the same results. the system will black out and can not be recovered. i have contacted ATI through email but have not heard from them as of yet.
here is what i have done so far.
cd to location of driver
sh./ ati 9.3-driver-install sh
this command is the comand to build the driver according to ATI.
once done (i am logged in as level 3 ) i then log in as level 5 and restart the system.
the system gives me 2 boot options normal and failsafe and both black out with no response. i put (widows on the system to check the card to make sure it is not a hardware failure, and the card worked just fine.so i can rule this out. this has been the only problem i have ever had with linux. i will fix it i am not sure how at this point.