11.2 Fixes For Xpress 200 and other legacy Cards

In the search for answers we may finally have some that will work for all those that are suffering
with newly declared legacy Ati video cards in Opensuse 11.2. I want to be clear about one thing
before I start I know that not everyone has had trouble with their ATI Card in 11.2 this howto is
just for those that have.

There seems to be three major problems for users with the new legacy Ati Hardware in 11.2.

1. People try to install the linux driver from ATI (x11-video-fglrxG01). It does not work in 11.2 at
this time and by all reports will never be updated. Running sax2 -r -m 0=fglrx with legacy hardware
seems to cause a complete xorg failure for most users myself included.

Short Answer: Uninstall the fglrx driver and run sax2 -r -m 0=radeon

2. Black Screens of Death. Good news is we have a fix that is proving to work for many. But we still
need more input from users to declare it final.

Short Answer: Change the vga mode in grubs default boot option to 0xf06

3. 3D Issues. While there will never be a universal fix for this issue. I can offer a possible fix for
desktop effects in 11.2 on legacy hardware including the xpress 200m.

Short Answer: Upgrade to kde 4.3.4. There will be risks involved in doing so. So if your happy
with the way things are don’t upgrade.

This concludes the short answer part of this Howto refer to the long Answer Portion in the next
post For the step by step fixes. If these options work for you please post to let us know about it.


Remember that almost everything in these solutions depends on your xorg running the radeon driver.
So look at your xorg file to make sure it is begin used in place of the fglrx driver.

I am Going to brake this up by the three issues above.

1. Failure by installing ATI’s Catalyst Linux driver

To fix a legacy system after this has been installed you need to do the following.

It is likely that you can’t login to the desktop after rebooting, you will need to bypass this failed part of your install.

When Grub starts erase the kernel boot option and enter

3

This places you in init 3 mode from startup. Once you have booted to the login prompt, login either as your root account or as
your user account. Then enter super user mode by entering.

**Su**

Once your in a super user account enter

Sax2 -r -m 0=radeon 
or 
Sax2 -r -m 0=ati

Both Option Seem to work to place the radeon driver in control. Once you have entered sax2 you should be able to choose
change configuration, do so and check to see if 3d is check and everything else is setup right. (such as 24bit color)

Once you have finished your inspection exit and save your changes. I have found the test option to be trouble some with the
Xpress 200. It causes a crash for me, if it does this to you. You will need to repeat the steps above and this time hit save.

Now you should be able to boot into your desktop by entering startx if not reboot. If your Suffering from a black screen issue you will need
to follow the next step to fix that.


2. Black screen of death

This may be the simplest fix ever but if it works for the xpress 200m and other cards so be it. If you can’t get in to your desktop to start yast
because even after following the step above you where not able to start your desktop. I am placing the steps to get around this below.

Step 1

Start yast

Step 2

Select System>Boot Loader

Once you have opened the boot loader select the default boot option for linux. (Example: Desktop – openSUSE 11.2 - 2.6.31.5-0.1)

Then enter this in the vga mode field.

0xf06

Thats it, now restart and see if it worked. Grub’s kernel boot line should now read vga=0xf06 at startup.


The Back Way In: Special steps for those systems that are really stuck.

Start from grub in init 3 then login and enter super user mode and type yast. This will start the terminal version of the tool, after
doing this simply follow the same step listed above. If your not comfortable with this option follow the steps quoted below to
start your desktop.

After the fresh install has finished you should get a black screen of death on any system running a Xpress 200m.

once you reach grube erase the kernel boot options and type:

3

Hit enter and wait until it asks you for your login name. Enter your login and password then enter super user mode.

su

You will be asked for the root password enter it then enter

kdm

Now the kdm should come up login normally and everything should work just fine.


3. 3D Issues.

Upgrade your kde to kde 4.3.4. There where a number of fixes in this release and its predecessors that are the most likely
cause of my desktop effect not only working but working well.

Howto Upgrad to kde 4.3.4

Upgrade reboot and see if this has helped.

To be fare I also refreshed my xorg install so I will include those steps for those that don’t see an improvement.

This is the Repo you will need to add.

download.opensuse.org/repositories/X11:/XOrg/openSUSE_11.2/ 

Follow the same steps in the howto for upgrading to kde 4.3.4 in the software manager to completely refresh xorg.

The order in which these two are applied maybe important so if your not getting results reverse them and let me know.

This is how we all became legacy

Products Supported

AMD has moved a number of DX9 ATI Radeon™ graphics accelerators products to a legacy driver support structure. This change impacts Windows XP, Windows Vista, and Linux distributions. AMD has moved to a legacy software support structure for these graphics accelerator products in an effort to better focus development resources on future products.

The following products have been moved to the legacy software support structure (including Mobile and All-in-Wonder Variants):

ATI Radeon 9500 Series
ATI Radeon 9550 Series
ATI Radeon 9600 Series
ATI Radeon 9700 Series
ATI Radeon 9800 Series
ATI Radeon X300 Series
ATI Radeon X550 Series
ATI Radeon X600 Series
ATI Radeon X700 Series
ATI Radeon X800 Series
ATI Radeon X850 Series
ATI Radeon X1050 Series
ATI Radeon X1300 Series
ATI Radeon X1550 Series
ATI Radeon X1600 Series
ATI Radeon X1650 Series
ATI Radeon X1800 Series
ATI Radeon X1900 Series
ATI Radeon Xpress Series
ATI Radeon X1200 Series
ATI Radeon X1250 Series
ATI Radeon X2100 Series

AMD may periodically provide Windows XP and Windows Vista driver updates (for the products listed above) for critical fixes only. No new features will be provided in future driver updates. The Linux ATI Catalyst™ driver will only be supported in Linux distributions prior to February 2009 for the legacy products listed above.

Any customers using a combination of a ATI Radeon™ HD 2000 Series, ATI Radeon™ HD 3000 Series, or ATI Radeon™ HD 4000 **Series product with any of the legacy products listed above in a single PC system must use the ATI Catalyst 9.3 or earlier driver. ** All future ATI Catalyst™ releases made available past the ATI Catalyst™ 9.3 release will not include support for the legacy products listed above or any of the features associated with those legacy products.

After the fresh install has finished you should get a black screen of death on any system running a Xpress 200m.

once you reach grube erase the kernel boot options and type:

3

Hit enter and wait until it asks you for your login name. Enter your login and password then enter super user mode.

su

You will be asked for the root password enter it then enter

kdm

Now the kdm should come up login normally and everything should work just fine.

Works, but you have to do the prozedure everytime, starting the 11.2

It gets you in to the system so you can set the boot loader to “0xf06” or “Ask for resolution during boot”. If you set it to Ask for resolution during
boot just select any of the non vesa options these seem to work for those of us effect by the black screen issue.

I want this to be crystal clear 0xf06 is just one option there are many other options under “Ask for resolution during boot” that will work.

For any one having the black screen issue it has been postulated by others in the forum that it is caused by a vesa to radeon issue.
That would explain why the fail safe startup is working for some of us since that is a vesa to vesa startup.

If you follow these steps you shouldn’t have to us the back door option every time. I am still having to change my none vesa boot option
for a single startup here and there but I am not using the back door method at all any more. I go from 0xf06 to 0xf02 and that seem
to do it for the most part. It seems that installing updates to the system always preceeds the black screen at startup issue. But now
when that happens I just restart and change the 6 to a 2.

Let us know if this works to fix your issue.

Step 1

Start yast

Step 2

Select System>Boot Loader

Once you have opened the boot loader select the default boot option for linux. (Example: Desktop – openSUSE 11.2 - 2.6.31.5-0.1)

Then enter this in the vga mode field.

Code:

0xf06

Thats it, now restart and see if it worked. Grub’s kernel boot line should now read vga=0xf06 at startup.

I found this at linuxquestions.org:

VGA Resolution Codes for GRUB & Lilo
Code:

Width-Height-Depth VGA Codes HEX Codes
80x25 (TEXT) 3840 0xF00
80x50 (TEXT) 3841 0xF01
80x43 (TEXT) 3842 0xF02
80x28 (TEXT) 3843 0xF03
80x30 (TEXT) 3845 0xF05
80x34 (TEXT) 3846 0xF06
80x60 (TEXT) 3847 0xF07

These are just for the text modes.

I was having 3d issues: artifacts, system freezes with compositing enabled, with my X1650 on 4.3.1. Upgraded to 4.3.4 and it seemed better, but I was still having the same problems. Adding the xorg repository and switching packages to it seems to solve the problems completely for me. **** my 56k modem.

…and thanks!

I just installed 11.2 on a server I use at home with a Radeon 9800 and everything worked okay except of desktop effects.
There was allot of artifacting so I first upgrade to kde 4.3.4 and that didn’t fix it for this card. Running Sax2 -r -m 0=radeon
also didn’t change anything. Then I followed your xorg update instructions and that fixed it.

I would say that both xorg and kde 4.3.1 may need to be updated to fix desktop effects for legacy ATI cards that don’t fly straight right off.

Also I would like to ask why Sax2 seems to be the only way to set resolutions lower than the highest your system can handle
and still have it remain at that setting after a restart?

ATI Technologies Inc Radeon R350 [Radeon 9800 Pro]

The artifacting is a result of bugs in Mesa 7.6, which have been fixed in the Mesa 7.7 RCs. I installed 7.7-rc1 and the artifacts went away.

Latest Mesa One-Click Install

There seem to be no rules for working or working not. Sometimes it works, sometimes in works not. After Updates it often works. After changing boot-resolution it often works.
May be, sometimes it work every time.- Thanks for all -
Konrad - from near of Hamburg (I hope you could understood me. School is out for many many years.

That will be much easier on peoples bandwidth then an xorg refresh.

Latest Mesa One-Click Install

konboy here’s what I am finding to work since it seems we share a similar issue.

After my last post I did another update and of course it was straight back to the black screen at startup. Now I am looking
for answer here not implying that updates are the only reason for this issue. I learned that changing the boot options at
startup wasn’t enough in fact it seemed that each time I used an option it wouldn’t work again after that. So I went into yast
opened the boot loader, changed the option there and things started working again.

Now just before posting this I noticed that I had 5 new updates waiting so I updated and shutdown the system. I should point
out at this point that the update issue only happens after a complete shutdown and reboot. I can restart all day long if I
like but shutting down is another matter. This time even using init 3 didn’t let me into the kdm. So I ran yast from the
prompt and updated the boot loaders option and restart. Of course things started normally after that, can I explain why
absolutely not. I am simply changing from f06 to f02 in the boot loader each time it fails. I would venture a guess that I
might not even need to change the options just as long as I open the boot loader and let it refresh the grub on exit.

For my system as long as I am not running updates or other yast configuration stuff I am consistently able to boot in with
no issues. I can install new software without causing any issues so far.

Try updating your boot loaders VGA mode to one of the options here after getting a black screen.

Width-Height-Depth VGA Codes HEX Codes
80x25 (TEXT) 3840 0xF00
80x50 (TEXT) 3841 0xF01
80x43 (TEXT) 3842 0xF02
80x28 (TEXT) 3843 0xF03
80x30 (TEXT) 3845 0xF05
80x34 (TEXT) 3846 0xF06
80x60 (TEXT) 3847 0xF07

Let us know if you are able to shutdown and then reboot more that three time after doing this. That seem to be a good yardstick
for whether or not it will continue working.

Here are some question that may help others here give some answers for this issue.

  1. What video card are we dealing with on your system?
  2. Are you using the gdm or the kdm is also relevant to the question.
  3. Any other system info you feel like sharing can’t hurt.

Actually it appears that the only thing needed is a fix in the radeon driver. The KDE upgrade should be completely irrelevant and the complete XOrg/Mesa update works because it includes the fix. The minimum needed to fix the black screen problem should be updating xorg-x11-driver-video to the version in the X11:/XOrg:/11.2 repository.

I have been meaning to submit an update to the moderator to get that fixed. Several other posts point to the mesa issue so thats been clear, the xorg-x11-driver-video refresh is new to this thread if I remember right so thanks.

We will be getting this updated in the next few day’s, at least as far as getting the text to the moderators. Who knows what will happen after that.

I am looking for comparison data on what is and isn’t working and when
it isn’t working. Does anyone else get black screens after doing the following.

  1. I get a black screen every time I update my system like clock work.(after a complete shutdown)

  2. I get one when I use the Restart to windows options (now that could just be a punishment)
    This option skips the grub selection menu and starts windows without asking. (in KDE not sure about gnome)

  3. I can fix the black screen for several boots by opening yast and changing the boot vga mode in Boot loader settings.
    I go from f06 to f02 and thats it. Can’t change the kernel boot line any more, I have used all the non-vesa option up.

So it either starts right or I have to use init 3.

My system stopped booting consistently about a week ago so it back to the drawing board for
answers again. That is why I am asking for data on what is causing black screens for everyone. I am hopping
to find a pattern that will at least lead to a bug report being filed.

Hello,

since some days, mostly works:

booting with 0x317 - works every time
suspend to ram - works mostly
Screensaver doesn’t work (white screen but screen is alive), doesn’t matter :wink:
second screen with 1680x1024 pixel - works difficult but works

Using hp nx6325 with ati xpress200,
x.org-repositories
kde 4.3.4
displaymanager is kdm4

Thanks for all - - merry christmas

konboy

I updated all the file that had newer version in the xorg repo a week and a half ago and things have worked ever since. I want to make it clear that I only updated the files that had newer version as many still had older versions than I currently had installed.

I hope this works for all the Xpress 200 users. The xorg repo is listed earlier in this thread if you need to add it.

Good Luck and Happy holidays.

Hello @ll,

i now installed OpenSuse 11.2 again and followed all Tips to become my nx6325 running.
I can say, it worked now.

I updated KDE to 4.3.4, Xorg and then, installed Mesa Drivers.
After this i started

sax2 -r 0=radeon

,changed login Screen from SUSE to kdm4

/etc/sysconfig/displaymanager

and changed Bootloader to 0317

I could not say, which of these things are necessary and which not. All together seems to work now.

Thanks for all :wink:

magabooks wrote:

>
> I updated all the file that had newer version in the xorg repo a week
> and a half ago and things have worked ever since. I want to make it
> clear that I only updated the files that had newer version as many still
> had older versions than I currently had installed.
>
> I hope this works for all the Xpress 200 users. The xorg repo is listed
> earlier in this thread if you need to add it.
>
> Good Luck and Happy holidays.
>
>

I also updated a few weeks ago and no black screens since :slight_smile:

I have updated some xorg packages since and they’ve all been fine. kwin
compositing is good, suspend to ram sometimes works.

Hello! I’ve been having the Black Screen of Death issue as well, except in Ubuntu.

I found the suggestion here (adding vga=0xf06 to grub) worked for a while, but inexplicably stopped working in the end, promptly after customizing my xorg.conf in fact. I have since reverted my xorg.conf and reinstalled fglrx at runlevel 3, but I’m getting BSOD at every boot… I tried vga=0xf02 but it did nothing. I haven’t tried 0x317 yet but I will as soon as I get home. In the mean time, I am very interested as to what xorg package versions you who have updated successfully are using. Specifically (and I apologize to use debian/ubuntu package names, but i don’t know the openSUSE equivalents) “xserver-xorg” “xserver-xorg-core” and it’s not x but it is involved “libdrm2”.

I’ll have to recheck my xserver-xorg, but I think my xserver-xorg-core package is at 1.5.2 and my libdrm2 is at 2.3.1

followup:

Also my xserver-xorg-video-all is at 7.4 (so xserver-xorg is also probably 7.4). I also need to recheck the minor version numbers and patch version numbers, which I suspect do not match with OpenSUSE’s repositories (ie. your xorg-x11-driver-video looks newer than ubuntu intrepid’s).

My distribution is mainly Ubuntu Jaunty by the way, with everything x-related downgraded to Ubuntu Intrepid for fglrx compatibility. This sort-of works with fglrx 8.543, but I was hoping that 8.593 would be an improvement… actually the few times I got it working it seems to scramble all my opengl applications unless I disable compiz… the very problem it was published to fix… but that’s a discussion for another thread.