Home > Ati Drivers > Ati Drivers Opensuse 13.1

Ati Drivers Opensuse 13.1

Now run the ati config commands: aticonfig --initial --input=/etc/X11/xorg.conf 9. MS Windows Interop 13. yes/no [y/n]: y The report was uploaded to sprunge.us. Unfortunately, the version of X-server is too new for the driver. news

Thank you very much, Sebastian. Troubleshooting things to try Version: openSUSE-11.3 and later As of openSUSE-11.3, the legacy graphic configuration wizard "sax2" is no longer included with openSUSE. At openSUSE project level, we still have 13.1, 13.2, 42.1 and 42.2 that are mostly active. 13.1 is already almost out of the game of evergreen, 13.2 will follow soon, and If you installed openSUSE 11.4 or above on a computer with a Radeon chipset, the radeon driver should already be installed and running. read this article

I wish good luck to those who want to try those drivers, I've got a look inside, and got a blame face. Have fun Tags: 11.4, 12.1, 12.2, 12.3, 13.1, 13.2, amd, ATI, fglrx, Kernel, Tumbleweed, xorg Posted in Base System, Desktop, GNOME, KDE, Kernel, X.org | 20 Comments » Proprietary AMD/ATI Catalyst If this works, you "may" wish to stop here. But there's two things that bring me out of the game, first I don't have those newer gpu, and don't have the need to replace my hd5750 for the moment.

Again, boot to run level 3 like the 3rd step above. You can use YaST to do this. Graphics Drivers Note that there's no need to install the below non-free video drivers, if the free drivers used by default work for your needs. 15.1 Nvidia This section describes two That brings you to a full screen text login Login as a regular user Type "su" (no quotes - enter root password) to switch users to the administrator/root.

OpenSuSE 11.0 & 11.1 With The Latest Driver[edit] You can easily install the latest versions of the ATi driver on OpenSuSE 11.0+. Please follow the guidance in the openSUSE release notes - Initializing Graphics with KMS (Kernel Mode Setting). And you're done. https://en.opensuse.org/SDB:ATI_drivers AGPMode Option "AGPMode" "8" Acceptable values are 1", "2", "4" and 8.

If something goes wrong, remove the driver with the parameter -u. Warnings There's really no warranties the drivers will work, for you! su -c 'sh makerpm-amd-15.11.sh -ur' The system report 'amd-report.txt' was generated. [ OK ] Do you want to read the system report 'amd-report.txt' now? Version: Leap 42.1 and olderThe fglrx driver does not work on Leap 42.2+ or Tumbleweed as it has been abandoned by AMD.

Repository zypper ar -cfg -n FGLRX http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_Leap_42.2/ FLGRX zypper -v refresh -f FGLRX zypper -v install fglrx64_amdcccle_SUSE422 fglrx64_core_SUSE422 fglrx64_graphics_SUSE422  fglrx64_opencl_SUSE422 fglrx64_xpic_SUSE422 Future AMD has stopped any development for FGLRX, so it If you try to run glxgears or any other OpenGL based app and see error messages that look like this: X Error of failed request: BadRequest (invalid request code or no If you dig a bit around, you should be able to build them, but you're alone on that way, you've been warned! BACKUP your current /etc/X11/xorg.conf file, preferably to your home directory.

It should be on by default. http://advianetwork.com/ati-drivers/ati-drivers-8-27-10.html Note: For example on openSUSE 13.2, fglrx64_xpic_SUSE132 is for 64-bit and fglrx_xpic_SUSE132 is for 32-bit Click Accept to confirm your changes. Warning Be careful adjusting these settings. Leap being available only for x86_64 bit plateform, the driver follow the same available arch.

I hope this release will give better results for all of you who own an apu (especially the recent one), and also fix a number of issue with the hybrid chipset In fact this step does in part what the old sax2 configuration wizard used to do for openSUSE (but this is less capable). Introduction 2. More about the author Let boot your system in console mode, once you see a prompt login, use the root account Recreate the initrd without the free radeon loaded: # mkinitrd Reboot in console mode

You may well be able to reboot into the previous kernel without the problem (usually after an upgrade the last kernel is offered via a boot menu option). They differ a bit compared to Sebastian Siebert last version in the sense of making Leap 422 as a possible target. For complete original story, refer to the original post.

For the moment it works for Kernel 4.4-rc3.

Afterwards reboot the computer. 15.1.2 Install the Nvidia Driver in the Terminal You can install the Nvidia driver in the terminal. If you are locked down and forced for any reasons to use fglrx with your gpu, and are still using 42.1, then don't upgrade to 42.2, without a plan B It For older gpu, the fglrx-legacy is still 13.1, and thus didn't work with openSUSE 12.3 or above. So 2 drivers to maintain, but as always with proprietary software, the legacy version became rapidly obsolete, and non usable.

ColorTiling Option "ColorTiling" "on" Turning this on improves 3D performance. Don't show this warning the next time xf86-video-ati ATI video driver for the Xorg X server ati is an Xorg driver for ATI/AMD video cards. You will need to do this edit from a text editor (such as the mc editor(recommended - see link for installation/use details) or the vi editor or the nano editor or click site After doing the preceding, to test if this works, you can reboot your system by typing: su -c 'shutdown -r now' Hopefully that will allow a boot to a graphical X

So if one of those component change in Leap fglrx will be broken. I'm considering the release of thoses rpms as experimental, they work for some, and sometimes are convenient. A full list of options is available on the radeon man page. Version: 42.1http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_Leap_42.1/ Version: 13.2http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_13.2/ Version: 13.1http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_13.1/ Version: 12.3http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_12.3/ Version: 12.2http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_12.2/ Version: 12.1http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_12.1/ Version: 11.4http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_11.4/ Version: 11.3http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_11.3/ Version: 11.2http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_11.2/ Note: This list is also useful for the zypper client install below.

If setting it to "AGP" or "PCIE" causes problems, you can set it to "PCI" but you'll have a performance drop. Search for installed fglrx packages: zypper se fglrx Remove any packages found from the search string, without quotes: zypper rm "name found package" Then run the following command to ensure one X11 Configuration When fglrx is installed, aticonfig creates a /etc/X11/xorg.conf, containing configuration details for running fglrx. Links to the new repository openSUSE_Leap_42 Have fun!

Check your xorg.conf if you have one If so, consider removing /etc/X11/xorg.conf: Since in most cases the radeon module auto-magically configures your hardware without the need of configuration files Try this Downloads Support Community Development Search Wiki > SDB:AMD fglrx Sign up | Login Username Password Cancel Navigation Project Distribution Support Contact Site map Help Wiki Create a Page Change a Page Boot-to-run-level-3 Note if your boot screen looks no where near like the above, it is likely you are using grub2 (which is the default boot manager) and you need to follow In case of kernel panic If upon rebooting after uninstalling the fglrx driver you get kernel panics involving radeon missing (with error messages such as "unable to handle null pointer dereference")

Story Today, while packing my stuff for the SUSECON15 in Amsterdam, I was pleased on irc to have feedback of users who were able to run fglrx Tumbleweed packages on their For users trying to blacklist "nouveau" driver, examples of how to specify NO_KMS_IN_INITRD from a text yast are here, illustrated sequentially below (note one must also blacklist nouveau as described above). You have to start by disabling it so you could fallback to it quickly when new stable version will be published. If it says "No" then check your Xorg logs for more information.