ATI Radeon X1270 drivers

[caf4926]

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

[TKS1125]

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.

[caf4926]

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.

[baskitcaise]

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

[TKS1125]

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....

[baskitcaise]

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:


http://support.amd.com/us/gpudownloa...7&lang=English

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

[TKS1125]

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.

[baskitcaise]

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

[TKS1125]

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......

[TKS1125]

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.