[SOLVED]Problem with graphic driver after updating system

Hapoofesgeli · 2013-06-30 20:40:12

Hello
I updated system(-Syu)today and then i faced some problems with proprietary drive, so i removed it(according to the wiki page) and installed the open source driver.
But now Cinnamon runs in the software rendering mode and everything is slow.
And i get this message while booting:

[drm:radeon_init] *ERROR* No UMS support in radeon module!

dmesg | egrep "drm|radeon" output:

[    4.804506] [drm] Initialized drm 1.1.0 20060810
[    4.844137] [drm] VGACON disable radeon kernel modesetting.
[    4.844143] [drm:radeon_init] *ERROR* No UMS support in radeon module!

*my graphic card is ATI 5770

What information should i provide and/or what should i do?

Last edited by Hapoofesgeli (2013-07-01 09:52:50)

cfr · 2013-07-01 00:52:20

Welcome to the forums. Did you install ati-dri?

Last edited by cfr (2013-07-01 00:52:49)

ConnorBehan · 2013-07-01 01:31:47

Remove things like "nomodeset", "radeon.modeset=0" and "options radeon modeset=0" in your kernel command line and modprobe.d. Recent versions of the radeon driver only support KMS.

Hapoofesgeli · 2013-07-01 04:36:47

cfr wrote:

Welcome to the forums. Did you install ati-dri?

Thank you, yes i have installed it.

ConnorBehan wrote:

Remove things like "nomodeset", "radeon.modeset=0" and "options radeon modeset=0" in your kernel command line and modprobe.d. Recent versions of the radeon driver only support KMS.

Sorry but what/where exactly are kernel command line & modprobe.d?
I checked /boot/grub/grub.cfg and there are 2 nomodeset quiets in it.
& there is only one file in /etc/modprobe.d/ (alsa-base.conf).

Last edited by Hapoofesgeli (2013-07-01 21:04:42)

ConnorBehan · 2013-07-01 07:38:57

Yes, grub.cfg is where you edit the kernel command line. And that is the only place where you should have to remove "nomodeset" if nothing in your modprobe.d refers to radeon.

If for some reason that doesn't work and radeon still fails to load, try running "modprobe radeon" once you get to the console or even "modprobe radeon modeset=1" to be sure.

jrussell · 2013-07-01 07:42:40

I don't think you should actually be looking at /boot/grub/grub.cfg
/etc/default/grub is what you should be fiddling with

What's the output of

sudo cat /etc/default/grub

You should not edit /boot/grub/grub.cfg directly as it gets generated automatically.

https://wiki.archlinux.org/index.php/GRUB#Configuration

Hapoofesgeli · 2013-07-01 08:39:42

ConnorBehan wrote:

Yes, grub.cfg is where you edit the kernel command line. And that is the only place where you should have to remove "nomodeset" if nothing in your modprobe.d refers to radeon.
If for some reason that doesn't work and radeon still fails to load, try running "modprobe radeon" once you get to the console or even "modprobe radeon modeset=1" to be sure.

First code gives an error and the second one gives a black screen.
But removing nomodeset from /boot/grub/grub.cfg worked and the problem is solved!

---------
Can i install proprietary driver again? what should i do to keep it working after updating the kernel?(should i use Catalyst-hook/Catalyst-generator?)

Thanks everyone!

cfr · 2013-07-01 20:49:49

Please edit the post above where you quote somebody else's words under my name (the second quote in post #4). I know nothing about the radeon driver!

As has been pointed out, unless you plan to always manage grub.cfg manually, you should not edit that file directly but instead customise the kernel command line using /etc/default/grub and regenerating grub.cfg. Otherwise your changes will get nuked when you next have to regenerate the config file e.g. if grub is updated.

Hapoofesgeli · 2013-07-01 21:14:51

cfr wrote:

Please edit the post above where you quote somebody else's words under my name (the second quote in post #4). I know nothing about the radeon driver!
As has been pointed out, unless you plan to always manage grub.cfg manually, you should not edit that file directly but instead customise the kernel command line using /etc/default/grub and regenerating grub.cfg. Otherwise your changes will get nuked when you next have to regenerate the config file e.g. if grub is updated.

Sorry about the post, i don't know why it happened.

How exactly should i do that? there is no nomodeset in it. and how is regenerating grub.cfg?
Thanks.

cfr · 2013-07-01 21:32:04

grub.cfg is regenerated in the same way you originally generated it i.e. using grub-mkconfig -o /boot/grub/grub.cfg. Obviously choose a different name if you want to inspect it before installing it.

If you generate e.g. grub-mkcofnig -o /tmp/grub.cfg does that file include nomodeset? It must be coming from somewhere...

Hapoofesgeli · 2013-07-01 22:10:27

cfr wrote:

grub.cfg is regenerated in the same way you originally generated it i.e. using grub-mkconfig -o /boot/grub/grub.cfg. Obviously choose a different name if you want to inspect it before installing it.
If you generate e.g. grub-mkcofnig -o /tmp/grub.cfg does that file include nomodeset? It must be coming from somewhere...

i regenerated it and restarted system and everything works fine.
And there is no nomodeset in the regenerated grub.cfg.

Arch Linux

#1 2013-06-30 20:40:12

[SOLVED]Problem with graphic driver after updating system

#2 2013-07-01 00:52:20

Re: [SOLVED]Problem with graphic driver after updating system

#3 2013-07-01 01:31:47

Re: [SOLVED]Problem with graphic driver after updating system

#4 2013-07-01 04:36:47

Re: [SOLVED]Problem with graphic driver after updating system

#5 2013-07-01 07:38:57

Re: [SOLVED]Problem with graphic driver after updating system

#6 2013-07-01 07:42:40

Re: [SOLVED]Problem with graphic driver after updating system

#7 2013-07-01 08:39:42

Re: [SOLVED]Problem with graphic driver after updating system

#8 2013-07-01 20:49:49

Re: [SOLVED]Problem with graphic driver after updating system

#9 2013-07-01 21:14:51

Re: [SOLVED]Problem with graphic driver after updating system

#10 2013-07-01 21:32:04

Re: [SOLVED]Problem with graphic driver after updating system

#11 2013-07-01 22:10:27

Re: [SOLVED]Problem with graphic driver after updating system

Board footer