Opensuse 13.1 does not boot intro Gnome

I installed Opensuse 13.1 but it simply does boot intro gnome. After a while it’s entering run level 3, if i try init 5, it will just load but nothing will happen. The USB media is not corrupted I’ve checked it.
I have a Acer Aspire V5-552g laptop.

Did you try “Recovery Mode” already? (“Advanced Options” in the boot menu)

What graphics card do you have?

I have a AMD Radeon HD 8750M, I am afraid to use the recovery mode because it use it on fedora and what hapend was that gnome utilized to much CPU.I tried fedora just to see if the problem was on opensuse or just gnome in general.

Yes, but you would at least get a graphical system. :wink:

I would suggest to install the proprietary fglrx driver:
http://en.opensuse.org/SDB:AMD_fglrx

Ok will try, but I will use the official AMD website, there I can find the latest version and Opensuse 13.1 it’s on the supported platform list.
http://support.amd.com/en-us/kb-articles/Pages/latest-linux-beta-driver.aspx

I would not recommend that. You would have to reinstall the driver after every kernel update (and possibly other updates as well).
And version 14.4 has been released already on May 2nd, so why would you want to install the release candidate from April?

I’d rather install it from the repo (which does contain the latest 14.4), you would even get driver updates automatically.
Or use Sebastian Siebert’s makerpm-amd script, that downloads the latest driver, creates RPMs and installs them automatically.

See also:
http://lizards.opensuse.org/tag/ati/

(btw, there’s a repo for the latest beta driver as well, but at the moment this is older than the latest stable version)

PS: If you do insist on downloading the driver from the AMD homepage, take the released 14.4 instead of the release candidate:
http://support.amd.com/en-us/kb-articles/Pages/AMDCatalyst14-4LINReleaseNotes.aspx

Oh yes I understand what you mean. but look on the 14.4 release notes it says it only supports opensuse 11.4 and 12.1. But I’m using 13.1

http://support.amd.com/en-us/kb-articles/Pages/AMDCatalyst14-4LINReleaseNotes.aspx

So what? Might be an error in the release notes.
It should work fine on 13.1 (according to the system requirements mentioned).
Why would the release candidate work on 13.1 and the final version not? :wink:

Official 14.4 (final) packages are available for 13.1 in the repo, if you want to be on the safe side use those.
Or use Sebastian Siebert’s script as already mentioned, this also contains official patches for later kernel/Xorg versions and so on if necessary.

And no big deal if it does not work simply boot to recovery mode and remove the driver. But it should work.

From recovery mode I did a : “zypper dup” and the installed the fglrx drivers from opensuse and now I can boot in to my Gnome desktop. Thank you all!

However I still have one problem, when I am in Chrome or in gnome-controlcenter the CPU is still using a high % , on core it’s always at aprox. 100%.

And which process is using the CPU? Use “top” to check.

Is the fglrx driver really in use?
Please install the package “Mesa-demo-x” and post the output of:

glxinfo | grep render

For

glxinfo | grep

the output is:

direct rendering: Yes
OpenGL renderer string: AMD Radeon HD 8600/8700M
    GL_NV_conditional_render, GL_NV_copy_depth_to_color, GL_NV_copy_image, 
    GL_NV_conditional_render, GL_NV_copy_depth_to_color, GL_NV_copy_image, 

I did a ps aux, here is the output on gnome-controlcenter : dan 3656 100 0.8 1208388 64388 ? Sl 07:18 2:21 gnome-control-center --overview

This looks ok, the driver is in use and direct rendering is working.

Hm. Does this only happen with those two applications?
Might not necessarily be related to the graphics then. At least gnome-control-center doesn’t do much rendering anyway.

To be honest i think I will try xfce and kde. Is KDE resurce hungry ?

Not more than GNOME I would say.

On openSUSE, File indexing is disabled by default anyway.

And for graphics requirements it is even lighter, because you can turn off compsiting and desktop effects (this is even done automatically if your card doesn’t support it). Although this shouldn’t make a difference with your card and the fglrx driver, but for recovery mode f.e. it would, because GNOME would use Mesa’s software renderer (slow) whereas KDE would just turn off some/most effects and run fast. :wink: