SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
that will work in SUSE (I believe SUSE uses YaST2 or apt4rpm), but I have no clue what the syntaxt will be and what the fglrx driver name would be? This should install the driver (obviously I have to get kernel-sources, gcc, make before that, like
#yast install kernel-sources gcc make
<aside>This is now driving me up the wall. To make matters worse I can no longer use my Dapper discs on this laptop so can not install Dapper (with GNOME 2.14+). I am relucntant to corrupt my existing Breezy by upgrading). For some reason when I boot with Dapper installation disc, it hangs at the initial splash screen. Only happens with Dapper not any other distro). I am not sure what happened?. I had dapper installed on this machine using Dapper F3 version before now even that disc is reading corrupt sectors on disc integrity checks...man what gives?)
Hi smiley, it seems that you are having a rough time.
About your problem in SuSE, the xorg.conf files that you have tested should have worked, at this point I don't think that this is the problem. A final thing to check, did you read if the error in the file /var/log/Xorg.0.log is the same when you changed xorg.conf files?.
It's possible that something else went wrong when installing SuSE, therefore I can suggest you to try a reinstallation if that is possible. When you are installing you can check if the monitor and graphic card are recognized, you can even modify this, make sure that all the specs are correct, the resolution and finally you can choose manually the "vesa" driver. After that, sax2 will write an xorg.conf file that I hope you can use until you install the ATI driver.
I reinstalled, and at the end "hardware configuration", I decided to change the Monitor to VESA and the resolution to 1024x768 and test!
the screen froze in intense white and then flickeing black and white, and could not do anything. So I manually rebooted and guess what I have a GUI login: I have 800x600 resolution (better than being in the dark)
Could not init font path element /usr/X11R6/lib/X11/fonts/truetype/, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/URW/, removing from list!
(EE) FBDEV(0): FBIOBLANK: Invalid argument
Sorry it took so long to respond. You said this in your earlier post.
For finding *X11* and *fglrx*, I meant for you to type the command like this.
find /usr -name *X11*
find /usr -name *fglrx*
Leaving out -name will give you a lot of results which I'm sure you saw. Can you please post the output of the two commands I just showed you?
Also, to revert everything back to the default GUI, type in <sax2 -r -a>.
Sorry ceros, thanks again. I am now in the GUI environment with very bad resolution 800x600 using the vesa driver (see my posts above). Now I think I have to install the ati-driver-installer-8.23.7-i386.run from the ati site and make it executable. But before that I think I have to install kernel-sources, gcc and make.
I am checking with YaST gui if I can update my software and i am getting errors. I have a live internet connection. I think I will need to point Yast to the SUSE repo rathe rthan CD, so that it can update and allow software installation.
I am saying this because of my Ubuntu exprience. I am new to SUSE and would like som ehelp from here.
1. Go to YaST and install/verify that you have the following packages:
kernel-source (the one that matches your kernel, type "uname -r" to know your exact kernel name)
gcc
make
2. Download the latest ATI driver from www.ati.com.
3. *** Most important step ***
Build the kernel module. For this step you can follow two paths:
First and easy one: Just go to the directory where you downloaded the installer and as root simply type:
Quote:
sh ./ati-driver-installer-***
This is the installer provided by ATI, follow the instructions, it should recognize your system OS, kernel and start building the module. At the end, you should have the option to see and html page with the summary of the installation.
Please note that sometimes you finished the installer without any warning if something went wrong. To make sure you have the kernel module type:
Quote:
# modprobe fglrx
If it complains that it can't be found, then you have to find out what happened, post the content of the file:
Quote:
cat /usr/share/fglrx/fglrx-install.log
Second path is more laborious and we can follow that one only if you have not luck with this one.
4. Configure the file xorg.conf, now "Don't continue with this step if you didn't finish correctly the third step". Always make a backup of your xorg.conf file before attempting to change it manually or automatically. Then type in a console as root:
Quote:
# fglrxconfig
You can also use aticonfig, anyway, follow the instructions, choose the adequate configuration, monitor specs, screen resolutions, choose now the "flgrx" driver. When you finished this, you'll have a new xorg,conf file. You can test it as you did in previous posts.
Hope this helps, keep in mind that I don't think that the ATI installer will work with X org 6.9 yet. If you success in this endeavor then I'll follow you.
# POSIX Shared Memory (/dev/shm) support is required for 3D apps
# glibc version 2.2 or 2.3
# Linux kernel 2.4 or higher
# XOrg 6.7 or 6.8; XFree86 version 4.1, 4.2, or 4.3
Here are the minimum requirements. For POSIX shared memory, check to see if it's been mounted correcty <mount |grep "shm">. You should get something like this "tmpfs on /dev/shm type tmpfs (rw)." Then <ls /dev> and check for a directory named "shm."
For glibc, type in <yast2 -i>. Look for glibc. It might also help to install the glibc-devel package as well.
Suse 10.0 supports kernel release 2.6.13 as of now so I'm sure Suse 10.1 is higher.
Xorg 6.9 is used in Suse 10.1.
Once you get the latest driver installer from ATI, cd into the directory containing the installer, <sh ./ati-driver-installer-8.23.7-i386.run. A GUI wizard should come up. Select you want to generate your own disribution specific package. Select the package for Suse 10.1. The package is placed in your current directory.
Click finish then <yast2 -i "type the package's name here">. Go through the wizard and the drivers should be installed.
Finally, type in <aticonfig --initial --input=/etc/X11/xorg.conf>. It should say something has been loaded or found, I forget which. Suse has it's own xorg.conf tool so it's best to use Suse's tool. Type in <sax2 -r -m 0=fglrx>. Another wizard comes up. Check your settings and click OK. Then click "test" in the pop up window. If the test window comes up, then everything will work. Save your settings, click on restart to get out of sax2. Logoff, then log back on. At this point if your logged on, everything is working. You can chack glxgears to see what your getting now.
As I'm typing this, I think victor beat me to posting just about the same thing. I hope this post helps you anyways.
Go to Yast's installation source wizard <yast2 inst_source>. Pick a mirror and then add an installation source in the wizard. The directories are
pub/opensuse/distribution/SL-10.0-OSS/inst-source -- For the OSS installation source.
pub/suse/i386/10.0/SUSE-Linux10.0-GM-Extra -- For the extra non-GPL packages that are in the store bought CDs.
pub/suse/i386/10.1/SUSE-Linux10.1-Beta8-Extra -- This is an install directory for 10.1 beta 8 non-GPL packages.
Great! victorh's instructions worked upto a point. fglrxconfig or aticonfig were not recognized so I used ceros instruictions from here on. and used sax2 to configure and test. So when I click test, it gave me the right resolution, but when I saved the settings, wen tinto black screen. So I waited for 5 mins, then rebooted manually (could not wait any longer). But I was pleasantly surprised to be in a GUI with 1920x1200 resolution crisp screen!!
here is my fglrxinfo
Code:
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY FireGL V5000 Pentium 4 (SSE2) (FireGL) (GNU_ICD)
OpenGL version string: 2.0.5695 (8.23.7)
and here are the glxgears outputs, just the first or so lines
Code:
suse@linux-ruub:~> glxgears
13787 frames in 5.0 seconds = 2757.252 FPS
14501 frames in 5.0 seconds = 2900.177 FPS
14556 frames in 5.0 seconds = 2911.052 FPS
14546 frames in 5.0 seconds = 2909.097 FPS
14400 frames in 5.0 seconds = 2879.820 FPS
14344 frames in 5.0 seconds = 2868.763 FPS
14533 frames in 5.0 seconds = 2906.315 FPS
14495 frames in 5.0 seconds = 2898.848 FPS
9903 frames in 5.0 seconds = 1980.598 FPS
One other big question: where is the source list for the beta testing? I see ceros has suggested using the 10.0 sources and one non-GPL 10.1 source, how about the normal beta sources (OSS ones). As I have OSS Open SUSE installed right now?
Yeah, I haven't been able to find the 10.1 beta 8 OSS sources either. Maybe you'll have better luck finding it through Google. So does typing in <sax2> still work? Also, I'm kind of curious as to why <aticonfig> doesn't work. Can you look for it, <find / -name aticonfig>?
This will sound really stupid, how do I enter the ceros' source list to yast, it keeps complaining are they http or ftp and are they directories or other.
Also victorh, is your link above also a source to add to yast, then how to do it?
here is the find -name aticonfig output:
Code:
# find / -name aticonfig
/usr/X11R6/bin/aticonfig
find: /proc/4013/task: No such file or directory
find: /proc/4013/fd: No such file or directory
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.