The first parts works but when it comes to the part buildpkg it does not work…
So now after sax2 -r -m 0=vesa i am back but now stucked with the 640x480 and i guess if i am planning to continue using this resolution i have to go to city dump and find an monitor from let us say 1998
This is the parts i do not get you guys are happy with this windows 95 mode or you are stucked in dosprompt mode 24/7???
Oh yes why are 640x480 default mode is it because its impossible to hit the ok buttom great job if
City dump seems an better option then the links i have tried them before.
If you want anyone installing the drivers from ATI or Nvidia an good option might be start with listen to the devolopers of the drivers and go the way they have set up the driver to be installed.
From ATI howto setup the ATI driver
For best performance and ease of use, ATI recommends the following:
Kernel module build environment
o Kernel source code include either the Kernel Source or Kernel Headers packages
The RPM utility should be installed and configured correctly on your system, if you
intend to install via RPM packages
The following packages must be installed in order for the ATI CatalystTM Linux driver to
install and work properly:
XFree86-Mesa-libGL
libstdc++
libgcc
XFree86-libs
fontconfig
freetype
zlib
gcc
To install the driver
sh ./ati-driver-installer-10-2-x86.x86_64.run
To configure the driver
/usr/bin/aticonfig --initial
A big problem is when you go to the packethandler to look for the first thing you need to have installed it does not excist.
XFree86-Mesa-libG
And yes i got the packman resp.
So i am not gonna waist more time here you have a great time in the terminal keep smoking!!!
XFree86-Mesa-libGL? Thats nonsense. Utter nonsence. No, … let me say that different. Thats wrong for openSUSE. Clear ? Its not needed. … I dont want to confuse you, so let me say again. Its not needed.
XFree86-libs ? Thats nonsense. Utter nonsence. No, … let me say that different. Thats wrong for openSUSE. Clear ? Its not needed. … I dont want to confuse you, so let me say again. Its not needed.
Where are you getting this from ??? No one in this forum recommended that to you.
If you choose to ignore guidance given in this forum, then this won’t work for you. Thats your call. Thats your decision.
Now if your hardware is legacy hardware, the proprietary ATI driver will not work for you.
How about telling us what hardware you are using?
Anyway, you have been given GOOD advice on this thread to get this working. You are following advice that is not applicable and is totally, completely and absolutely incorrect. I’m not surprised you get frustrated when you do not follow provided advice.
Typically with Linux, users do NOT install applications direct from the developers. No, instead users install applications that have been packaged by the packagers. The packagers take the developers packages and package them for users.
In a small number of cases, such as proprietary graphic drivers, users will obtain a driver from the manufacturer, and install a graphic driver. Every Linux distribution tends to have a different way of doing this, which is WHY you need to follow the forum instructions or the openSUSE wiki instructions.
… hmmm … I recommend you read that openSUSE concepts link 3 or 4 times, until you understand … Concepts - openSUSE
As a last resort solution, would it not be possible to save that what you type into the terminal to a bash-script and then have it automatically executed on/after login?
I am a KDE user, and in Systemsettings there is the Autostart tab. That’s where I would select applications and scripts to start automatically after login.
I have no idea if there is something like this in Gnome, but I do have a very strong suspicion that there is.
OK, thats good to read. Then if you are using the 10.2 ATI Catalyst, do NOT follow the instructions for 8.24.8. Thats like buying a Porsche and following the instructions for a model-T Ford.
Please, I gave you the links instructions you need above.
Hi
You can just create a file and put it in ~/bin make it executable via
chmod 700 then it’s just a matter of opening the Control Center and
adding in via the startup applications.
#!/bin/bash
/usr/bin/xrandr -s 0
where 0 is the output number from the screen resolution you require
from the output of the xrandr command.