[问题]ubuntu8.04启动特效桌面假死

GnomeShell/Unity/Beryl/AiGLX/XGL/Compiz Fusion
回复
flyingegg
帖子: 9
注册时间: 2007-06-25 20:18
送出感谢: 0
接收感谢: 0
联系:

[问题]ubuntu8.04启动特效桌面假死

#1

帖子 flyingegg » 2008-09-06 23:02

其实不仅仅是8.04,自从IBM r52装上ubuntu7.04只要一启动特效就会出现桌面假死的情况,之前一直都认为是显卡驱动的问题,但是今天ati x300显卡驱动已经装好,
bonnie@flyingegg:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI MOBILITY RADEON X300
OpenGL version string: 2.1.7873 Release

bonnie@flyingegg:~$ glxinfo | grep -e 'direct' -e 'OpenGL'
direct rendering: Yes
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI MOBILITY RADEON X300
OpenGL version string: 2.1.7873 Release
OpenGL extensions:

所有的帖子方法都尝试过,就是摆脱不了桌面假死的噩梦,而且用ttf1的top也监控不出来什么~~~用的是compiz fusion
头像
yq-ysy
论坛版主
帖子: 3563
注册时间: 2008-07-19 12:44
来自: 广西(桂)南宁(邕)
送出感谢: 0
接收感谢: 76 次

#2

帖子 yq-ysy » 2008-09-07 9:10

看看/var/log/Xorg.0.log文件有没有(EE)错误和(WW)警告?
flyingegg
帖子: 9
注册时间: 2007-06-25 20:18
送出感谢: 0
接收感谢: 0
联系:

#3

帖子 flyingegg » 2008-09-07 12:28

yq-ysy 写了:看看/var/log/Xorg.0.log文件有没有(EE)错误和(WW)警告?
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(WW) fglrx(0): Option "VendorName" is not used
(WW) fglrx(0): Option "ModelName" is not used
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(WW) AIGLX: 3D driver claims to not support visual 0x33
(WW) AIGLX: 3D driver claims to not support visual 0x34
(WW) AIGLX: 3D driver claims to not support visual 0x35
(WW) AIGLX: 3D driver claims to not support visual 0x36
(WW) AIGLX: 3D driver claims to not support visual 0x37
(WW) AIGLX: 3D driver claims to not support visual 0x38
(WW) AIGLX: 3D driver claims to not support visual 0x39
(WW) AIGLX: 3D driver claims to not support visual 0x3a
(WW) AIGLX: 3D driver claims to not support visual 0x3b
(WW) AIGLX: 3D driver claims to not support visual 0x3c
(WW) AIGLX: 3D driver claims to not support visual 0x3d
(WW) AIGLX: 3D driver claims to not support visual 0x3e
(WW) AIGLX: 3D driver claims to not support visual 0x3f
(WW) AIGLX: 3D driver claims to not support visual 0x40
(WW) AIGLX: 3D driver claims to not support visual 0x41
(WW) AIGLX: 3D driver claims to not support visual 0x42
(WW) AIGLX: 3D driver claims to not support visual 0x43
(WW) AIGLX: 3D driver claims to not support visual 0x44
(WW) AIGLX: 3D driver claims to not support visual 0x45
(WW) AIGLX: 3D driver claims to not support visual 0x46
(WW) AIGLX: 3D driver claims to not support visual 0x47
(WW) AIGLX: 3D driver claims to not support visual 0x48
(WW) AIGLX: 3D driver claims to not support visual 0x49
(WW) AIGLX: 3D driver claims to not support visual 0x4a
(WW) AIGLX: 3D driver claims to not support visual 0x4b
(WW) AIGLX: 3D driver claims to not support visual 0x4c
(WW) AIGLX: 3D driver claims to not support visual 0x4d
(WW) AIGLX: 3D driver claims to not support visual 0x4e
(WW) AIGLX: 3D driver claims to not support visual 0x4f
(WW) AIGLX: 3D driver claims to not support visual 0x50
(WW) AIGLX: 3D driver claims to not support visual 0x51
(WW) AIGLX: 3D driver claims to not support visual 0x52
(WW) AIGLX: 3D driver claims to not support visual 0x53
(WW) AIGLX: 3D driver claims to not support visual 0x54
(WW) AIGLX: 3D driver claims to not support visual 0x55
(WW) AIGLX: 3D driver claims to not support visual 0x56
(WW) AIGLX: 3D driver claims to not support visual 0x57
(WW) AIGLX: 3D driver claims to not support visual 0x58
(WW) AIGLX: 3D driver claims to not support visual 0x59
(WW) AIGLX: 3D driver claims to not support visual 0x5a
(WW) AIGLX: 3D driver claims to not support visual 0x5b
(WW) AIGLX: 3D driver claims to not support visual 0x5c
(WW) AIGLX: 3D driver claims to not support visual 0x5d
(WW) AIGLX: 3D driver claims to not support visual 0x5e
(WW) AIGLX: 3D driver claims to not support visual 0x5f
(WW) AIGLX: 3D driver claims to not support visual 0x60
(WW) AIGLX: 3D driver claims to not support visual 0x61
(WW) AIGLX: 3D driver claims to not support visual 0x62
(WW) AIGLX: 3D driver claims to not support visual 0x63
(WW) AIGLX: 3D driver claims to not support visual 0x64
(WW) AIGLX: 3D driver claims to not support visual 0x65
(WW) AIGLX: 3D driver claims to not support visual 0x66
(WW) AIGLX: 3D driver claims to not support visual 0x67
(WW) AIGLX: 3D driver claims to not support visual 0x68
(WW) AIGLX: 3D driver claims to not support visual 0x69
(WW) AIGLX: 3D driver claims to not support visual 0x6a
(WW) AIGLX: 3D driver claims to not support visual 0x6b
(WW) AIGLX: 3D driver claims to not support visual 0x6c
(WW) AIGLX: 3D driver claims to not support visual 0x6d
(WW) AIGLX: 3D driver claims to not support visual 0x6e
(WW) AIGLX: 3D driver claims to not support visual 0x6f
(WW) AIGLX: 3D driver claims to not support visual 0x70
(WW) AIGLX: 3D driver claims to not support visual 0x71
(WW) AIGLX: 3D driver claims to not support visual 0x72
(WW) Configured Mouse: No Device specified, looking for one...
头像
yq-ysy
论坛版主
帖子: 3563
注册时间: 2008-07-19 12:44
来自: 广西(桂)南宁(邕)
送出感谢: 0
接收感谢: 76 次

#4

帖子 yq-ysy » 2008-09-08 9:13

flyingegg 写了:(WW) fglrx(0): board is an unknown third party board, chipset is supported
……板是不可知的第三方板……也许你的显卡驱动仍未装好?
呵呵,如何判断显卡驱动是否已经安装成功,这也是个严重问题。
因为默认情况下,大部分显卡Linux都能调用出其最高分辨率,但这并不等于显卡驱动已经安装成功。

就N卡而言,如果“nvidia官方驱动”安装成功,在启动X时能看到Nivida的标志,
而且在/etc/X11/xorg.conf文件的device字段里是支持3D的“nvidia”而不是仅支持2D的“nv”。

如果你使用的是ubuntu系统默认的“非受限驱动”,从8.04版来看,不是每张卡都能顺利启用3D桌面。
flyingegg
帖子: 9
注册时间: 2007-06-25 20:18
送出感谢: 0
接收感谢: 0
联系:

#5

帖子 flyingegg » 2008-09-08 14:35

yq-ysy 写了:
flyingegg 写了:(WW) fglrx(0): board is an unknown third party board, chipset is supported
……板是不可知的第三方板……也许你的显卡驱动仍未装好?
呵呵,如何判断显卡驱动是否已经安装成功,这也是个严重问题。
因为默认情况下,大部分显卡Linux都能调用出其最高分辨率,但这并不等于显卡驱动已经安装成功。

就N卡而言,如果“nvidia官方驱动”安装成功,在启动X时能看到Nivida的标志,
而且在/etc/X11/xorg.conf文件的device字段里是支持3D的“nvidia”而不是仅支持2D的“nv”。

如果你使用的是ubuntu系统默认的“非受限驱动”,从8.04版来看,不是每张卡都能顺利启用3D桌面。
非常感谢。
我以为用fglrxinfo能够正确显示显卡信息就好了呢。
我的驱动是在网上下的开源驱动,据说ati驱动支持aiglx,不知道应该如何去设置。
那有什么解决的办法吗?
头像
yq-ysy
论坛版主
帖子: 3563
注册时间: 2008-07-19 12:44
来自: 广西(桂)南宁(邕)
送出感谢: 0
接收感谢: 76 次

#6

帖子 yq-ysy » 2008-09-08 16:28

flyingegg 写了:
yq-ysy 写了:非常感谢。我以为用fglrxinfo能够正确显示显卡信息就好了呢。
我的驱动是在网上下的开源驱动,据说ati驱动支持aiglx,不知道应该如何去设置。那有什么解决的办法吗?
试试用envyng来帮你装显卡驱动,用envyng安装驱动有个好处就是,
有些需要卸载的冲突软件包它会自动帮你卸载,有些需要安装的支持软件包它会自动帮你安装。如,Nvidia的glx相关软件包等。 ATI也是。看我的另一篇帖子:
viewtopic.php?t=140531&start=0
flyingegg
帖子: 9
注册时间: 2007-06-25 20:18
送出感谢: 0
接收感谢: 0
联系:

#7

帖子 flyingegg » 2008-09-10 7:56

yq-ysy 写了:
flyingegg 写了:
yq-ysy 写了:非常感谢。我以为用fglrxinfo能够正确显示显卡信息就好了呢。
我的驱动是在网上下的开源驱动,据说ati驱动支持aiglx,不知道应该如何去设置。那有什么解决的办法吗?
试试用envyng来帮你装显卡驱动,用envyng安装驱动有个好处就是,
有些需要卸载的冲突软件包它会自动帮你卸载,有些需要安装的支持软件包它会自动帮你安装。如,Nvidia的glx相关软件包等。 ATI也是。看我的另一篇帖子:
viewtopic.php?t=140531&start=0
非常感谢,我周末回家尝试一下。多谢了。呵呵。
回复

回到 “桌面特效”