> On Monday 22 October 2007, [EMAIL PROTECTED] wrote:
>> > I had thought I had an older graphics card in my system that
>> > wouldn't support Desktop Effects.  But I discovered with glee that
>> > I indeed had a Radeon 9200 which is on the support list in the
>> > wiki.
>> >
>> > So I proceeded to do the one-click install of the ATI proprietary
>> > driver.  But nothing changed.  Sax2 still saw the old driver and
>> > wouldn't let me change to the new driver.
>> >
>> > Going into Yast2 > Hardware > Hardware Information > Display, I see
>> > that the new driver is listed as (secondary.)
>> >
>> > How do I make this driver primary?
>> >
>> > --
>> > ---Bryen---
>>
>> Okay, maybe that wasn't the best thing to do.  I rebooted my box and
>> now I no longer have a graphical login and I get display errors when
>> I run sax2. hwinfo still lists the new driver as a secondary.
>>
>> Thank goodness I discovered w3m the other day and can still get
>> online to email you guys.  :-)
>>
>> Should I just rpm -e the new ATI driver that was installed to revert
>> back to the original state or do I need to do something else as well?
>>  I'd like to see if changing the driver to primary would fix things
>> before I revert back to original state.
>>
>> Might as well make lemons when life gives you lemonade...  (oh wait,
>> did I botch that one up?)
>>
>> Help is greatly appreciated in this momentary minor crisis.
>>
>> Bryen
>
> ===========
> Bryen,
> Have you tried running sax2 to enable the fglrx module or even the
> aticonfig program for the newly installed ati software?
>
> Try:  sax2 -r -m 0=fglrx
>
> I know they have made several changes in the past few years and
> different methods have been used to enable & load the ati driver
> modules, but I think sax2 is capable now to do that for you.
> Documentation is always good at this point also.  ;-)
>
 I ran that command per opensuse wiki documentation and nothing happened. 
Then on the off chance, I decided to reboot, and that's when I lost all
graphical capabilities.  :-(

Further investigation:

As this was all done with one-click install, I just now looked at the
exact rpm's that were installed:

x11-video-fglrxG01-8.41.7-5.1
ati-fglrxG01-kmp-default-8.4.7_2.6.22.5_30-1.1

Looking at that last rpm, the end part of the name, I believe implies the
kernel version.   I have a newer kernel as pushed out by the security
update, and it is 2.6.22.9-04.  Perhaps this is the problem?

Anyway, since I don't want to damage it further, is it at all possible to
revert back to my original state by simply rpm -e-ing the above rpms?

Thanks,
Bryen

-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to