I am getting a 2" black line around the screen - please, help!

:slight_smile: God day all,

First of all, english is my second language. If I spell wrong or use a less good expression, please write me and correct me. I will not take offend. :wink:
My problem then.
I have installed Open Suse 11.2 today. The problem I have is that I have a black line around the screen, about 2". It is a standard problem for my laptop. Problem is, the answer who is working for Linux Ubuntu and other distro based on Ubuntu does not work here in Suse.

My laptop is a Toshiba Satellite S1800 - 364E. How do I configure the display so it shows fullscreen at 1024X734 (or somewhere close to it :))? Please, help me.

Best regards

Am I correct that this laptop has Trident CyberBlade XP AGP 4x graphics ? Can you tell us what graphic hardware this laptop has?

Does the command:

/sbin/lspci -nnk | grep VGA

provide that information? If not then maybe the same command (without the “VGA” filter) will tell the command ?

/sbin/lspci -nnk

ALSO, please, can you also tell us what graphics driver your openSUSE-11.2 Linux is using?

There is guidance here for that: openSUSE Graphic Card Practical Theory Guide for Users - openSUSE Forums in particular, please take a look at post#14 where if this is a Trident device, you may need to open /var/log/Xorg.0.log with a text editor, and tell us if your driver is FBDEV, or VESA, or TRIDENT ? I note when I type “man trident” that the CyberBlade/e4, CyberBladeXP, and CyberBladeAi1/XP, BladeXP are all supported by the trident driver in the xorg-x11-driver-video rpm that is already installed on your PC.

In which case if your PC is using the FBDEV or VESA driver, you will need to reboot to run level 3, and run sax2 with root permissions:

sax2 -r -m 0=trident

to create a custom /etc/X11/xorg.conf file for the trident hardware/driver.

But before I give you details on how to do that, can you please first confirm

  1. what graphic hardware the laptop has ? (see above)
  2. what graphic driver is being used now ? (see above)

Thank you and good luck.

God day OldCPU,

And thank you for helping me. :slight_smile:

  1. Command /sbin/lspci -nnk | grep VGA
    leopold@linux-qo9l:~> /sbin/lspci -nnk | grep VGA
    01:00.0 VGA compatible controller [0300]: Trident Microsystems CyberBlade XPAi1 [1023:8820] (rev 82). I think that means I have a Trident MS CyberBlade XPAi1 graphic hardware. Or card, as I would say in my own language.
  2. Not quite sure if I got it right:. But here is what I could find out, after reading, rereading and re-rereading your fine post:

With cat /var/log/Xorg.0.log | grep ‘(‘II’)’’ ‘FBDEV gives:
leopold@linux-qo9l:~> cat /var/log/Xorg.0.log | grep ‘(‘II’)’’ ‘FBDEV
(II)FBDEV: driver for framebuffer: fbdev’

Command (==) VESA(0): gives:
leopold@linux-qo9l:~> cat /var/log/Xorg.0.log | grep ‘(‘II’)’’ 'VESA
(II) VESA: driver for VESA chipsets: vesa

Command cat /var/log/Xorg.0.log | grep ‘(‘II’)’’ ‘RADEON gives:
leopold@linux-qo9l:~> cat /var/log/Xorg.0.log | grep ‘(‘II’)’’ 'RADEON

Command sax2 -r -m 0=trident gives:
leopold@linux-qo9l:~> sax2 -r -m 0=trident
Absolute path to ‘sax2’ is ‘/usr/sbin/sax2’, so running it may require superuser privileges (eg. root).

It does look like Trident hardware.

Well it looks like those commands did not work.

Can you instead open the file /var/log/Xorg.0.log with a text editor, copy the contents, and post the contents of the file to the web site New - Pastie, and press ‘paste’ on that site? It will then give you a website/url address. Please then post here the URL address that it gives?

Its good that did NOT work for you, because you should NOT run that from a terminal in X window (ie do NOT run it with a graphic desktop running).

What you could do is try the trident driver.

First reboot your PC to run level 3 (which will be a full screen text mode). Do this by rebooting and as soon as the VERY 1st boot/splash screen appears at the VERY START of the reboot, press 3 so that you see 3 appear in the options line. Then do a regular boot and this should boot to a full screen text mode. Login as a regular user with regular user password. Then type ‘su’ (no quotes and enter root password) to get root permissions.

Then if you have an existing /etc/X11/xorg.conf file back it up by typing (with root permissions):

cp /etc/X11/xorg.conf /etc/X11/xorg.conf.mybackup.txt

Note linux is case sensitive so pay attention to where upper case and lower case is used.

Then generate a custom xorg.conf file to replace the previous one by typing:

sax2 -r -m 0=trident

where that is zero equals trident.

If you installed from a liveCD and it tells you sax2 is not yet installed, you can install (and then try again above) it with:

zypper install sax2

but I think that not required

Then after that completes (hopefully successfully) restart with

shutdown -r now

and do not press 3 this time.

If that fails then reboot again to run level 3 (by pressing 3 at the boot/splash menu) and login as a user, switch to root permissions, and restore your backed up xorg.conf file with:

mv /etc/X11/xorg.conf.mybackup.txt /etc/X11/xorg.conf 

but hopefully that will not be needed.

Thank you OldCPU,

And sorry for taking so long to respond. Since the Satellite is a test machine I shall take the time and test the instruction that you take the time to write. I have under the week or so since your replay have tried some of the things you wrote to no success. The strange thing is that I get full resolution when I am logging in, but not after the login is finished.

I shall try to install Suse 11.3 when it is coming out on a second computer at home. But the question is how I partition it to dual-boot Windows. But that is in a other thread.

Again, thank you OldCPU for taking the time to help a newbi! :slight_smile:

Best regards

please take notes and let us know what works and what does not work.

Actually this is not strange. This is expected behaviour when the graphic driver is not setup optimally. The reason is simple, up until the point at which you log in, there is a different very very basic software driver being used to display on your laptop screen. BUT as soon as you login, a higher performance driver (needed for X window) is loaded, and thats where the problem likely is located. Either the wrong driver is selected, or the correct driver is not tuned properly.