[SOLVED] Disabling Safe Graphics mode post-install

[kiddokun]

Hey there, I installed F15 alpha 1 on my test machine today, but I made the mistake of choosing "safe graphics" mode when booting the livecd... thinking it would only apply to the livecd.

Now when I boot the installed system I have the basic boot splash instead of the pretty one.
Also, currently 3D acceleration doesn't seem to be working (I do not gonme shell, and glxgears uses 100% cpu), which is rather odd considering that this is an intel i915 chipset (I've never seen those drivers break).

Is there a way to reset the graphics mode to standard instead of safe mode (without reinstalling everything)?

[Boricua]

Originally Posted by kiddokun

Hey there, I installed F15 alpha 1 on my test machine today, but I made the mistake of choosing "safe graphics" mode when booting the livecd... thinking it would only apply to the livecd.

Now when I boot the installed system I have the basic boot splash instead of the pretty one.
Also, currently 3D acceleration doesn't seem to be working (I do not gonme shell, and glxgears uses 100% cpu), which is rather odd considering that this is an intel i915 chipset (I've never seen those drivers break).

Is there a way to reset the graphics mode to standard instead of safe mode (without reinstalling everything)?

Hi, I believe you are in the same situation I am. See:

http://forums.fedoraforum.org/showthread.php?t=260719

[hephasteus]

Originally Posted by kiddokun

Hey there, I installed F15 alpha 1 on my test machine today, but I made the mistake of choosing "safe graphics" mode when booting the livecd... thinking it would only apply to the livecd.

Now when I boot the installed system I have the basic boot splash instead of the pretty one.
Also, currently 3D acceleration doesn't seem to be working (I do not gonme shell, and glxgears uses 100% cpu), which is rather odd considering that this is an intel i915 chipset (I've never seen those drivers break).

Is there a way to reset the graphics mode to standard instead of safe mode (without reinstalling everything)?

100 percent cpu usage isn't odd at all on glxgears. If you don't have 3d mode then you are using the software rasterizer. Which means all graphics are rendered on the cpu. Which means the renderer is going to use every bit of the cpu to render.

[kiddokun]

Originally Posted by hephasteus

100 percent cpu usage isn't odd at all on glxgears. If you don't have 3d mode then you are using the software rasterizer. Which means all graphics are rendered on the cpu. Which means the renderer is going to use every bit of the cpu to render.

Yeah, I know that... that's why I'm using it as an indicator that I somehow don't have hardware 3D acceleration currently.

Anyway my question still stands

---------- Post added at 11:03 PM ---------- Previous post was at 07:42 PM ----------

I have found the solution! It turns out that the "basic video" mode does two things: it configures X.org to use the VESA driver, and it tells grub to disable kernel modesetting to force it to really use VESA no matter what (my inspiration for the solution came from doing the reverse of the instructions on this page).

So, to go back to a full graphics experience, you need to do the following (as root):

1. rm /etc/X11/xorg.conf
2. nano /etc/grub.conf # in this file, edit the kernel boot lines to remove the "nomodeset" argument
3. reboot

I now see the pretty boot splash and can use GNOME Shell again.

[Boricua]

Originally Posted by kiddokun

]I have found the solution! It turns out that the "basic video" mode does two things: it configures X.org to use the VESA driver, and it tells grub to disable kernel modesetting to force it to really use VESA no matter what (my inspiration for the solution came from doing the reverse of the instructions on this page).

So, to go back to a full graphics experience, you need to do the following (as root):

1. rm /etc/X11/xorg.conf
2. nano /etc/grub.conf # in this file, edit the kernel boot lines to remove the "nomodeset" argument
3. reboot

I now see the pretty boot splash and can use GNOME Shell again.

I tried that a week ago and didn't work, so I guess my problem is somewhat different.