在grub界面, 按e 在 splash 后加 text ,按 ctrl + x 进入 终端模式
然后更新到 3.5 内核即可
$ sudo apt-get install linux-generic-lts-quantal
xserver-xorg-lts-quantal
$ sudo dpkg-reconfigure xserver-xorg-lts-quantal
$ sudo reboot
——————————————————————————————————————————————————————————————————————————————
问题 5:
驱动安装
分类:Linux
2013-01-23 20:44927人阅读评论?(0)收藏
linuxLinuxLINUX系统
目录(?)[+]
-
一卸载和删除原有驱动
-
二安装最新的AMD
catalyst 驱动
-
三启用集成显卡的direct渲染并调试Bug
-
四玩转你的双显卡吧
本文只针对含有AMD双显卡的部分机型,已经测试过的包括DELL Vostro 3550/DELL Inspiron 14R (AMD 6630 和Intel HD 3000)。整个安装过程需要使用命令行,但是对于一个初学者来说依然很简单,你只需要将命令粘贴进命令行,并记得按<回车>。Linux版本为Ubuntu12.04,同时本人也尝试过12.10,不过由于驱动和X的兼容性有问题,最终放弃了12.10。详细方式参见http://wiki.cchtml.com/i...Catalyst
一、卸载和删除原有驱动
[plain]view plain?copy?print???
-
sudo sh /usr/share/ati/fglrx-uninstall.sh
-
sudo apt-get remove --purge fglrx fglrx_*
fglrx-amdcccle* fglrx-dev*
sudo sh
/usr/share/ati/fglrx-uninstall.sh
sudo apt-get remove --purge fglrx fglrx_*
fglrx-amdcccle* fglrx-dev*
二、安装最新的AMD catalyst 驱动
下载必备的一些软件库
[plain]view plain?copy?print???
-
sudo apt-get install build-essential cdbs
fakeroot dh-make debhelper debconf libstdc++6
-
sudo apt-get install dkms libqtgui4 wget
execstack libelfg0 dh-modaliases
-
sudo apt-get install linux-headers-generic
xserver-xorg-core libgcc1
sudo apt-get install build-essential cdbs
fakeroot dh-make debhelper debconf libstdc++6
sudo apt-get install dkms libqtgui4 wget
execstack libelfg0 dh-modaliases
sudo apt-get install linux-headers-generic
xserver-xorg-core libgcc1
如果是64位则需要运行下面两段命令(32位则不需要)。
[plain]view plain?copy?print???
-
sudo apt-get install ia32-libs lib32gcc1
libc6-i386
-
cd /usr ; sudo ln -svT lib /usr/lib64
sudo apt-get install ia32-libs lib32gcc1
libc6-i386
cd /usr ; sudo ln -svT lib
/usr/lib64
64位驱动内核模块
[plain]view plain?copy?print???
-
sudo apt-get install dkms
sudo apt-get install dkms
本人使用的是64位操作系统,推荐硬件允许的最好还是用64位。
下载AMD catalyst for Ubuntu 12.4 驱动
[plain]view plain?copy?print???
-
cd ~/; mkdir catalyst12.4; cd catalyst12.4/
-
wget
http://www2.ati.com/drivers/linux/amd-driver-installer-12-4-x86.x86_64.run
-
chmod +x
amd-driver-installer-12-4-x86.x86_64.run
cd ~/; mkdir catalyst12.4; cd
catalyst12.4/
wget
http://www2.ati.com/drivers/linux/amd-driver-installer-12-4-x86.x86_64.run
chmod +x
amd-driver-installer-12-4-x86.x86_64.run
添加补丁(非常重要,之前试过不打补丁,会出现无法启动X或者Compiz等问题)
[plain]view plain?copy?print???
-
./amd-driver-installer-12-4-x86.x86_64.run
--extract driver
-
cd driver/plain/lib/modules/fglrx/build_mod/
-
wget -O fglrx.patch
http://ubuntuone.com/5gNgEmVfzs3ytD5QZ2YGCi
-
patch -p1 < fglrx.patch
./amd-driver-installer-12-4-x86.x86_64.run
--extract driver
cd
driver/plain/lib/modules/fglrx/build_mod/
wget -O fglrx.patch
http://ubuntuone.com/5gNgEmVfzs3ytD5QZ2YGCi
patch -p1 < fglrx.patch
创建安装包
[plain]view plain?copy?print???
-
cd ~/catalyst12.4/driver/
-
./ati-installer.sh 8.961 --buildpkg
Ubuntu/precise
-
cd ../
cd ~/catalyst12.4/driver/
./ati-installer.sh 8.961 --buildpkg
Ubuntu/precise
cd ../
安装驱动
[plain]view plain?copy?print???
-
sudo dpkg -i fglrx*.deb
sudo dpkg -i fglrx*.deb
第一时间配置Xserver(xorg.conf)
[plain]view plain?copy?print???
-
sudo aticonfig --initial -f
sudo aticonfig --initial -f
重启电脑
测试切换集成显卡
[plain]view plain?copy?print???
-
sudo aticonfig --px-dgpu
sudo aticonfig --px-dgpu
有些显卡需要再次重启电脑才能完成切换。
三、启用集成显卡的direct渲染并调试Bug
如果你一旦更新fglrx,或者你的系统自动更新,那么你必须重复步骤二,否则集成GPU将不会做direct渲染。
以root权限打开/etc/X11/Xsession.d/10fglrx
[plain]view plain?copy?print???
-
sudo gedit /etc/X11/Xsession.d/10fglrx
sudo gedit
/etc/X11/Xsession.d/10fglrx
对于32位系统,在第4行末尾加入/usr/lib32/dri/,使文档变成:
[plain]view plain?copy?print???
-
LIBGL_DRIVERS_PATH=/usr/lib/fglrx/dri
-
if [ `uname -m` = ‘x86_64‘ ]; then
-
if [ -d /usr/lib32/fglrx/dri ]; then
-
LIBGL_DRIVERS_PATH=${LIBGL_DRIVERS_PATH}<span style="color: rgb(255, 0,
0); background-color:
yellow;">:/usr/lib32/fglrx/dri:/usr/lib32/dri</span>
-
if [ ! -z $LD_LIBRARY_PATH ]; then
-
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:
-
fi
-
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}/usr/lib32
-
export LD_LIBRARY_PATH
-
fi
-
fi
-
export LIBGL_DRIVERS_PATH
LIBGL_DRIVERS_PATH=/usr/lib/fglrx/dri
if [ `uname -m` = ‘x86_64‘ ];
then
if [ -d /usr/lib32/fglrx/dri ];
then
LIBGL_DRIVERS_PATH=${LIBGL_DRIVERS_PATH}:/usr/lib32/fglrx/dri:/usr/lib32/dri
if [ ! -z $LD_LIBRARY_PATH ];
then
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:
fi
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}/usr/lib32
export LD_LIBRARY_PATH
fi
fi
export LIBGL_DRIVERS_PATH
对于64位系统,在第4行末尾加入/usr/lib/x86_64-linux-gnu/dri/, 文件变成
[plain]view plain?copy?print???
-
LIBGL_DRIVERS_PATH=/usr/lib/fglrx/dri
-
if [ `uname -m` = ‘x86_64‘ ]; then
-
if [ -d /usr/lib32/fglrx/dri ]; then
-
LIBGL_DRIVERS_PATH=${LIBGL_DRIVERS_PATH}<span style="color: rgb(255, 0,
0); background-color:
yellow;">:/usr/lib32/fglrx/dri:/usr/lib/x86_64-linux-gnu/dri</span>
-
if [ ! -z $LD_LIBRARY_PATH ]; then
-
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:
-
fi
-
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}/usr/lib32
-
export LD_LIBRARY_PATH
-
fi
-
fi
-
export LIBGL_DRIVERS_PATH
LIBGL_DRIVERS_PATH=/usr/lib/fglrx/dri
if [ `uname -m` = ‘x86_64‘ ];
then
if [ -d /usr/lib32/fglrx/dri ];
then
LIBGL_DRIVERS_PATH=${LIBGL_DRIVERS_PATH}:/usr/lib32/fglrx/dri:/usr/lib/x86_64-linux-gnu/dri
if [ ! -z $LD_LIBRARY_PATH ];
then
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:
fi
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}/usr/lib32
export LD_LIBRARY_PATH
fi
fi
export LIBGL_DRIVERS_PATH
保存文件并退出
四、玩转你的双显卡吧!
如果你切换的的显卡未生效,请重启电脑。
显示当前使用的显卡
[plain]view plain?copy?print???
-
aticonfig --pxl
aticonfig --pxl
如果使用的是独立显卡,则显示为
PowerXpress: Discrete GPU is active
(High-Performance mode).
如果是集成显卡:
PowerXpress: Integrated GPU is active
(Power-Saving mode).
切换集成显卡
[plain]view plain?copy?print???
-
sudo aticonfig --px-dgpu
sudo aticonfig --px-dgpu
切换独立显卡
[plain]view plain?copy?print???
-
sudo aticonfig --px-igpu
sudo aticonfig --px-igpu
查看Open
GL 库使用情况
[plain]view plain?copy?print???
-
fglrxinfo
fglrxinfo
查看direct
渲染状态
[plain]view plain?copy?print???
-
glxinfo | egrep render
glxinfo | egrep render
安装mesa-utils,测试3D性能(每5秒计算并输出一次fps)
[plain]view plain?copy?print???
-
sudo apt-get install mesa-utils
-
glxgears
sudo apt-get install mesa-utils
glxgears
独立显卡(ATI
6630)状态下
1793 frames
in 5.0 seconds = 358.581 FPS
1781 frames
in 5.0 seconds = 355.736 FPS
集成显卡状态下
301 frames
in 5.0 seconds = 60.115 FPS
298 frames
in 5.0 seconds = 59.585 FPS
明显可以看到区别了吧!
如果重启后黑屏或者无桌面显示,则需要切换到其他命令行界面Ctrl+Alt+F2,删除X配置并重启X
[plain]view plain?copy?print???
-
sudo rm /etc/X11/xorg.conf
-
sudo startx
———————————————————————————————————————————————————————————————————————————————
问题 6:
昨天Ubuntu 12.04LTS 64位版本升级内核后,发现图形界面启动不了。
然后重启,按上下键查看启动信息,发现卡在了saned disabled edit /etc/default/saned。。
Goole了一把,发现是没有gnome-shell.于是就使用CTRL+ALT+F1进入tty1,通过
sudo apt-get install gnome-shell安装,然后sudo reboot重启。
发现还是进入不了图形界面,再次查看日志,发现卡在了 checking battery state
这个原因是因为gdm的问题,安装gdm
sudo apt-get install gdm
在安装过程中会有配置选择,我们选择LightDM,
然后sudo reboot即可。。
然后就如愿的进入了图形界面。。。
———————————————————————————————————————————————————————————————————————————————
问题 7:
Ubuntu内核升级后无法进入系统的解决办法
[日期:2010-05-06] |
来源:www.walleve.com 作者:walleve |
[字体:大 中 小] |
昨天半夜在写代码的时候没怎么注意,Ubuntu系统提醒有可用升级,随手就给升级了,结果起床后开机,发现grub提示两个内核,然后选择最新的内核,直接黑屏很长时间进不去系统。
解决办法是:删除显卡驱动,否则重启后还是白屏
删除显卡驱动的命令是:sudo /usr/share/ati/fglrx-uninstall.sh
重启后进入桌面,over,然后要在终端运行 update-grub2
接着要做的两个事情,1、是否要更新内核。2、必须要重装显卡驱动
1、更新内核的方法如下:
安装新内核,然后update-grub,update-grub2,应该就可以了,然后按照下面删除旧内核文件即可。
apt-get remove 对应的内核版本号,将旧版本的内核删除掉(-image-和-header-两个文件都要删除的,一定要小心执行命令)。
apt-get autoremove 对应的内核版本号, 再清理下就应该可以
修改/boot/grub/grub.cfg(从9.10版本后,menu.list文件就被替换成了grub.cfg),将其中旧内核的文字删除即可,然后重启系统
2、重装显卡驱动
重启后要重装显卡驱动(如果重启出错请参照文章开始讲到的启动出错处理办法)。
重装显卡驱动的办法:
1、删除旧的和错误的驱动程序
cd /usr/share/ati/
sudo ./fglrx-uninstall.sh
sudo apt-get remove xorg-driver-fglrx xserver-xorg-video-ati xserver-xgl
2、安装新的驱动 (需要去ATI官方网站下载)
sudo sh ./ati-driver-installer-8-11-x86.x86_64.run
安装完毕后,把配置文件初始化一下,执行
sudo aticonfig –initial -f
生成 modules.dep 和 map 文件,保证模块和驱动的正常加载。
sudo depmod -a
3、重启
4、检查安装效果
在终端中运行 fglrxinfo,显示结果应该是:
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 2600 XT
OpenGL version string: 2.1.8201 Release
5、看看自己的显卡是否工作在Xv模式下,执行
xvinfo
如果显示的结果很多很多,那就是工作在xv模式下了。如果像下面这样的显示,那还需要再设置
X-Video Extension version 2.2
screen #0
no adaptors present
手工设置xv模式
sudo aticonfig –overlay-type=xv
6、看看其它信息
glxinfo | grep direct
我的结果是
direct rendering: Yes
7、测试一下速度和工作是否正常,程序会显示转动的齿轮和一些数值。
glxgears
fgl_glxgears
——————————————————————————————————————————————————————————————————————————————
问题 8:
Ubuntu
登陆异常-输入正确的密码后还会返回到登陆界面的问题
问题表现:
启动到了登陆界面,输入对应的密码,发现一闪黑屏有返回到登陆界面,如此往复
。。
而在alt-ctrl-f1,里面startx
--
:1,可以运行另外一个x界面,实在令人费解。
这是一个挺令人崩溃的问题,从网上搜索很多相关的案例:
有用户环境变量设置的问题;
有人重设xorg.conf;
检查硬盘错误,修改/etc/fstab,最后一位为2
。。。
但都没有解决我的这个问题,我的修改过程如下。
偶然在一篇文章中看到,可以查看用户主目录下的.xsession-errors文件,里面存放x界面的一些错误信息,获取可以有所帮助。
发现我的.profile里面有报错信息,然后log往后就没有了,修改对应的错误后,可以正常登陆了。
===================
这个竟然影响x登陆,而且这个错误根本不影响,不知道x设计的时候怎么考虑的,而且黑屏后闪一下就没有了,没法看到出错的信息,很悲剧啊。。
记录下来,希望对其他人有帮助。
———————————————————————————————————————————————————————————————————————————————
问题 9:
|
Note:
This is an attempt to create a canonical question that covers all
instances of "low-graphics mode" error that occurs to a user, including
but not limited to installation
of wrong drivers, incorrect or invalid lightdm greeters, low disk space,
incorrect installation of graphics card like ATI and Nvidia, incorrect
configuration of xorg.conf file while setting up multiple monitors among
others.
If you are experiencing the "low-graphics mode" error when trying to
login but none of the following answers work for you, please do ask a
new question and then update the answers of this canonical question as
and when your new question gets answered.
When I try to boot into my computer, I am getting this error:
The system is running in low-graphics mode
Your screen, graphics cards, and input device settings could not be
detected correctly. You will need to configure these yourself.

How do I fix the failsafe X mode and login into my computer?
Answer index:
|
|
|
|
Will try to answer the ones I can:
Assuming the answer by Jokerdino was already checked: http://askubuntu.com/a/141607/7035
Nvidia / Ati issues
This happens when a driver has a problem installing correctly (Most
cases). For this do the following:
-
Boot PC leaving SHIFT pressed to make the GRUB
Menu show.
-
Select Recovery Mode which will continue
booting correctly until the Recovery Menu appeares.
-
Select from the recovery
menu failsafeX.
-
In some cases failsafeX will load fine (You lucky dog), for others
(Me) it will give an error along the lines of "The system is running in
low-graphics mode" and will stay there forever. When this happens,
press CTRL+ALT+F1 to go to
the terminal. Type in your Username and Password.
-
Reinstall the drivers depending on your case:
NVIDIA
sudo apt-get install nvidia-current - More
stable/tested version sudo apt-get install
nvidia-current-updates - More up-to-date version
For other cases see this
answer for details and follow the links there to help you along
the way.
ATI
The simple way is to sudo apt-get install fglrx . If
this does not work keep reading.
Go to http://support.amd.com/us/gpudownload/Pages/index.aspx,
download the one you need, put it in some folder (rename it to "ati.run"
to simplify name). Go to the folder where you downloaded the file and
type chmod +x ati.run to give it Executable
Permission. Now just simply ./sh ati.run and
follow the onscreen steps.
After rebooting all problems should be solved. If you test
‘Additional Drivers‘ with a problem like this it will finish downloading
the package but then it will give an error. It also gives the same error
if you use ‘Software Center‘ and ‘Synaptic‘. The only way was to go to
the failsafeX option and do the workaround about
changing to the tty1 terminal and doing it via
command line.
I also need to add that I do not recommend downloading the Drivers
from the Nvidia site since they:
- Might create additional problems with Ubuntu
- Are not updated automatically
- Are not tested thoroughly in Ubuntu
Always use the nvidia-current package or
the nvidia-current-updates one. This are tested
and approved already for the Ubuntu version you are using and will give
less errors and incompatibility bugs.
Intel
For Intel it is recommended to do the following after doing all the
steps mentioned above but before installing anything (When you are in the
Terminal). You can choose from the Xorg-Edgers which is an Unstable PPA or
the X-Swat which is more stable:
Warning: This PPA is very unstable for some things. So do it with that
in mind.
sudo add-apt-repository ppa:xorg-edgers/ppa
-y
or X-Swat:
sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
-y
After that sudo apt-get update and you should
receive several updates. X-Swat currently does not have Intel drivers in
the latest versions of Ubuntu.
UPDATE: Added this extensive answer to solve many of
the problems that might end with the error mentioned here: Which
driver should I install when using an Nvidia, Ati or Intel video
card
Like always please test and give feedback so I can enhance my answer
since others will be also reading it. The better it is, the more people it
will help.
|
|
answered Nov 16 ‘12 at 15:56
| |
|
|
|
I solved this problem by reinstalling ubuntu-desktop.
When the message that "your system is running in low-graphics mode"
appears, press Ctrl+Alt+F1, then
login with your credentials.
And then, run the following commands:
sudo apt-get install --reinstall ubuntu-desktop
sudo reboot
|
|
answered Apr 26 ‘12 at 18:20
| |
|
|
|
The greeter is invalid
This is a bug in LightDM and a bug
report has already been filed.
The reason why you end up with this failsafe X is because the
pantheon-greeter you installed along with the elementary desktop is now
not available and LightDM is not able to identify an alternative
greeter.
As a workaround, you can edit the LightDM conf file and correct the
error.
Run the following command in a terminal: sudo nano /etc/lightdm/lightdm.conf
and change the line greeter-session=pantheon-greeter
to greeter-session=unity-greeter
and save it.
After changing the file, reboot and you will now be greeted with Unity
greeter.
|
|
|
|
When this happens there is often an error message indicating why it
failed to start X.
Look in
your /var/log/Xorg.0.log.old or /var/log/Xorg.0.log .
The error (if there is one) will be at the tail end of the file. Another
good place to look is the log files
in /var/log/gdm/* (or /var/log/lightdm/* in
oneiric).
Did you happen to manually install fglrx prior to noticing the problem?
If it was not uninstalled properly it can cause weird random issues.
Directions for purging fglrx are available at here.
Is your video card an AGP model? If so, a common issue with ati agp
cards is having an incorrect AGPMode. Sometimes you can adjust this
setting in your BIOS (which perhaps windows screwed with?) There is also a
setting in /etc/X11/xorg.conf for adjusting it in
X.
|
|
answered Nov 1 ‘10 at 22:35
| |
|
|
|
You have too many files on your computer, and have exhausted
disk space
Try moving personal files off the computer onto a USB drive.
To check whether this is the issue:
- Press Ctrl + Alt + F1
- Type
df -h
- If you see that there is no space available on the root
(
/ ) then you need to free some space.
To free space you can:
sudo apt-get autoclean
- Look for large directories with
sudo du -sc /*/* |sort
-g and delete unwanted content,
-
Clean your home directory using a combination of cd ~
du -sc * |sort -g
rm myLargeFile
When this is done, restart: shutdown -r now
|
|
answered May 18 ‘12 at 2:42
| |
|
|
|
Only for ATI graphics cards
When the message that "your system is running in low-graphics mode"
appears: Press Ctrl+Alt+F1 to
see the terminal one. Then login with your credentials, and then run the
following commands: sudo apt-get install fglrx
sudo reboot
The same can be done from the recovery mode (after enabling
networking), if your Ubuntu completly refuses to enter anything but
recovery mode.
|
|
answered Apr 27 ‘12 at 10:56
| |
|
|
|
Let‘s assume, arrogantly, that it is a problem with your X display
manager.
Enter the terminal (you can use a virtual console if you cannot use a graphical
terminal window), the one you said that you have access to, and enter the
following: sudo apt-get install gdm
. . . and choose gdm.
Then type: sudo service gdm restart
(Or ... start instead
of restart .)
According to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070150 this
is a way to workaround a bug with lightdm.
Before typing that, you may need to first stop the other display
manager that is running. This is usually LightDM: sudo service lightdm stop
If you have trouble getting GDM to start, and this is an installed
system rather than a live environment, then you can just reboot and it
will start automatically because you configured it as the default display
manager. (You should be able to shut down and restart normally. Otherwise,
one way to reboot if the GUI is not working properly is to
press Ctrl+Alt+Delete while on
a virtual
console.)
|
|
answered Aug 8 ‘12 at 2:23
| |
|
|
|
- If you have a problem with the restricted (closed source)
driver , then try to remove it.
Open a terminal and give this command gksudo software-properties-gtk
Goto Additional drivers and remove the
dirver. You have to mark the Using X.Org X server --
Nouveau.
Then Reboot.

- If you have not access at all to the Desktop Environment then use
the Recovery Mode.
To remove the Nvidia current driver in Ubuntu
12.10


Select the Network and your root partition will mounted as
Read-Write.

Select the Root 
And then give these commands with order apt-get remove --purge nvidia-current
rm /etc/X11/xorg.conf
apt-get install ubuntu-desktop
reboot
The last command will reboot your system and hopefully you will login
normally in next reboot with the Open Source nouveau driver.
- If you have problem with the open source driver
(nouveau) , in the same manner (from recovery mode) try to
install the restricted (Nvidia) driver with these commands
When you reach the Root selection and after select root
To install nvidia-current driver. apt-get install linux-source
apt-get install linux-headers-$(uname -r)
apt-get install nvidia-current
nvidia-xconfig
reboot
|
|
answered Oct 20 ‘12 at 6:36
| |
|
|
|
Follow these commands: sudo apt-get update
sudo apt-get -d install --reinstall gdm
sudo apt-get remove --purge gdm
(I ran this command above, but was told by the system to use # sudo
apt-get autoremove instead, after the #sudo apt-get remove --purge gdm
command.) sudo apt-get install gdm
select GDM when prompted sudo reboot
That fixed it for me :)
It took very long to start after the reboot, 10+ mins. But I got in
eventually.
|
|
answered Apr 30 ‘12 at 9:41
| |
|
|
|
I have recently received a similar issue with myPangolin Performance
laptop. The folks at System 76 told me to do the following:
Click Okay and then select the option to get a terminal. (alternatively
you can press ctr+alt+f1 to bring up another tty) sudo chown lightdm:lightdm -R /var/lib/lightdm
sudo chown avahi-autoipd:avahi-autoipd -R /var/lib/avahi-autoipd
sudo chown colord:colord -R /var/lib/colord
reboot
These commands did the trick for me.
|
answered May 16 ‘12 at 12:58
| |
|
|
|
This problem destroyed my morning. It turns out that if your root
filesystem runs out of space then Ubuntu will boot into low graphics mode
and it‘s hard to figure out why since the xorg log shows nothing wrong. To
find out from the command line if you‘re low on space type df -h
Sample output from my machine: Filesystem Size Used Avail Use% Mounted on
/dev/sda6 18G 10G 6.6G 61% /
udev 3.9G 4.0K 3.9G 1% /dev
tmpfs 3.9G 108K 3.9G 1% /tmp
tmpfs 1.6G 1.2M 1.6G 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 3.9G 1.3M 3.9G 1% /run/shm
none 100M 16K 100M 1% /run/user
/dev/sda4 317G 33G 285G 11% /media/data
/dev/sda1 197M 16M 182M 8% /boot/efi
If your / mount has a
high Use% (90%+) then this could be your problem.
In my case,~/.xsession.errors had grown to fill most of
my partition and caused me to fall into low-graphics mode. Found my answer
for that in this Ubuntuforums thread: rm ~/.xsession-errors
mkdir ~/.xsession-errors
|
|
|
|
Well, I had the same problem and solved it.
-
Start ubuntu with recovery mode from grub
then choose filesystem check followed
by enable networking.
-
Choose root option to get to terminal. Now uninstall the old
drivers
sh /usr/share/ati/fglrx-uninstall
-
Then reinstall the drivers following the methods for precise from
this websitehttps://help.ubuntu.com/community/BinaryDriverHowto/ATI.
-
After that everything works out just fine, I suggest you do
apt-get update && apt-get upgrade && apt-get
autoremove
-everytime you complete a step. Good luck.
|
|
answered May 2 ‘12 at 13:28
| |
|
|
|
I had the same problem with an Acer Aspire 3810tg. I solved it by doing
the following:
- Do a normal boot
- Press Ctrl-Alt-F1 on the "Your system is running in low-graphics
mode" screen
- Download the correct driver from http://support.amd.com/us/gpudownload/Pages/index.aspx,
in my case (ATI Mobility Radeon HD 4330):
wget
http://www2.ati.com/drivers/linux/amd-driver-installer-12-4-x86.x86_64.run which
should also cover your case (Mobility Radeon HD 4xxx Series)
chmod 755
amd-driver-installer-12-4-x86.x86_64.run to make the file
executable
sudo
./amd-driver-installer-12-4-x86.x86_64.run and follow the
standard steps
- You might need to run:
sudo aticonfig --initial ,
but that was not necessary for me.
In my case the driver installation finished with an error, but it still
worked. I hope this helps.
|
|
answered May 17 ‘12 at 19:12
| |
|
|
|
It is not related to nvidia drivers. Because by default Ubuntu uses
non-nvidia drivers even though you might have nvidia GPUs. I have an
nvidia GPU too.
My Ubuntu used to boot fine until something happened which caused the
same issue. After reading posts, reading logs and little bit trial and
error, turns out the problem is related to lightdm GUI server.
I dont know solution to the problem but there is a quick work around in
3 steps. This will save you from reinstalling Ubuntu.
Step1: When the error shows up, hit Ctrl+Alt+F1. This will open the
commandline interface. Login as root.
Step2: Remove a particular X11 config file. This file is not really
required.
rm /etc/X11/xorg.conf.failsafe
Somehow the existence of the above X11 configuration file causes the OS
to throw that error.
Step3: Restart lightdm GUI server.
service lightdm restart
This will restart the lightdm GUI server and voila your desktop is
back!
|
|
|
|
Try delete your /etc/X11/xorg.conf and restart.
Before restart, run sudo apt-get install xserver-xorg-video-ati xserver-xorg-video-radeon
|
answered Nov 1 ‘10 at 4:26
| |
|
|
|
I had a similar problem.
When I was booting my PC, i was getting the following message: “Ubuntu
is running in low-graphics mode”
When I used startx on the command prompt
however, everything was fine and i could start the xserver.
Now I found out that for some strange reason GDM has been uninstalled
(it took me hours to realize that), i did fix the problem by reinstalling
gdm with: apt-get install gdm
now everything‘s running. Hope this helps you.
|
|
answered Apr 25 ‘11 at 20:10
| |
|
|
|
Install gdm.
During the installation of gdm you will be asked to select either gdm
or lightdm as the default login display manager. Select gdm.
By the way, the fact that you have this problem on 2 different
computers is a sign that there may be an irregular voltage to your
computer power supply. To test for this possibility take one computer to a
different address and try booting it there.
|
|
answered Oct 6 ‘12 at 11:07
| |
|
|
|
Wich ubuntu version are you running? Did you installed graphics drivers
before the problem or is it a post clean-os-install issue? Giving some
more info would be helpful for us to help you.
If you messed with the graphic drivers before the problem came up, get
to the login screen,
press Ctrl+Alt+F1, login, then:
sudo apt-get purge nvidia-*
sudo apt-get autoremove
sudo apt-get linux-source linux-headers-generic
sudo apt-get install nvidia-current
sudo nvidia-xconfig
sudo shutdown -r now
Of course, if you have an ATI videocard you have to change
the nvidia-* and nvidia-current for
your ATI drivers package.
|
|
|
|
Try to boot from grub using a different parameter or even booting an
older kernel from the list.
https://help.ubuntu.com/community/BootOptions
See the section on kernel options. Something like: xforcevesa
Good luck! :)
|
answered Nov 8 ‘10 at 18:30
| |
|
|
|
Follow these commands: sudo apt-get update
sudo apt-get -d install --reinstall gdm
sudo apt-get remove --purge gdm
sudo apt-get install gdm
sudo apt-get remove --purge xserver-xgl compiz compiz-plugins compiz-core compiz-manager csm cgwd cgwd-themes
sudo apt-get install --reinstall compiz compiz-core compiz-fusion-plugins-extra compiz-fusion-plugins-main compiz-gnome compiz-plugins libcompizconfig0
sudo dpkg-reconfigure -phigh xserver-xorg
choose the driver ‘ati‘ and when you get to monitor resolution choose
the resolution you want to run and any resolution ABOVE that resolution
should be removed. Once that is done issue the following:* sudo reboot
You will most likely get errors on specific packages. Repeat the
command removing the problem package until it works.
There will be a time where you will be without the desktop, so have
another internet connected device nearby to reference this from or to
Google with in case of emergency.
This worked for me, hope this helps.
*If you are never prompted, just skip this.
|
answered Feb 1 ‘11 at 3:35
| |
|
|
|
I had a special case of this problem, where I somehow caused the
removal of some packages. I only noticed the actual problem after some
time spent looking at the problem.
So:
- Log into the text mode console
- Enter the command:
sudo apt-get install
ubuntu-desktop
This will ensure all the needed packages are installed. Without some of
those, symptoms like those described here may occur.
|
|
answered Aug 15 ‘11 at 20:15
| |
|
|
|
You said that you were stuck in low graphics mode and now you say that
you can only get a command prompt. What happens when you
type: startx
If you are stuck in a command prompt all is not lost. You can still
reconfigure xserver with: sudo dpkg --reconfigure --phigh
xserver-xorg
|
|
answered Nov 2 ‘10 at 0:22
| |
|
|
|
You need to install the kernel headers manually then reinstall nvidia
for some reason then the nvidia drivers will work
|
answered Oct 20 ‘12 at 8:53
| |
|
|
|
Your Memory may be bad.
If you experience Low graphics mode intermittently like I was.
-
Run a memory check to check for memory errors.
-
Buy New memory(Make sure it is the right type for your
computer)
-
Run the memory test again, to make sure all is good.
The Low Graphics Mode error should now be gone.
|
|
answered Oct 8 ‘11 at 17:43
| |
|
|
|
- Press CTRL+ALT+F1 to open
a terminal
- log in
- look at the end of your
/var/log/Xorg.0.log
-
if the message error is Cannot run in framebuffer mode.
Please specify busIDs. then run the following
commands: sudo apt-get install --reinstall lightdm
sudo reboot
|
|
|
|
I‘m running Ubuntu 12.04 on a Toshiba Portege R100. I got this error
after the first bootup after install. After downloading and updating the
graphics driver (Trident Cyberblade), what worked for me was creating a
driver-specific .conf file as described in this Arch-Linux wiki:https://wiki.archlinux.org/index.php/Trident.
|
|
|
|
Phenomenon: I first saw Booting without
full network configuration message that never ended. After
Action-1 below, I faced The system is running in low-graphics
mode issue.
Action-1: Force to shutdown the machine (by keeping
power button pressed as normal). Choose recovery boot.
Effective solution: Remove &
install xserver-xorg , inspired by this
thread.
Edit) after creating xorg.conf and had it read in xserver, I faced the
same issue again. This time, in addition to
re-install xserver-xorg , I had to
create /etc/X11/xorg.conf file (I did so by copying
the backup file I already made).
|
|
|
|
Go to System, Administration and click on Hardware drivers (in Maverick
it is called Additional Drivers). It will search for and allow you to
install the proper graphics driver which should allow you to run in higher
res.
In Linux there are two ways to do most things, by the GUI or by the
terminal. This is easier for most people used to a graphical user
interface. The second GUI way to do it would be to go to Software Center
or Synaptic and install the packages in the previous post. Search for them
in the search bar. I don‘t think that Ubuntu has used xorg.conf for
awhile, so it would not help to look for it.
|
answered Nov 1 ‘10 at 12:15
| |