当前时区为 UTC + 8 小时



发表新帖 回复这个主题  [ 7 篇帖子 ] 
作者 内容
1 楼 
 文章标题 : 使用xgl+beryl的怪事,数字键和人任务栏问题
帖子发表于 : 2006-10-31 18:18 

注册: 2006-09-30 21:21
帖子: 46
送出感谢: 0 次
接收感谢: 0 次
数字键盘那块变成了num灯亮为不可输入,灯灭为可输入
但是周围的加减等符号却是正常的
任务栏的图表没在那改?
scim的输入也有毛病


页首
 用户资料  
 
2 楼 
 文章标题 :
帖子发表于 : 2006-10-31 19:53 

注册: 2006-10-04 23:16
帖子: 183
送出感谢: 0 次
接收感谢: 0 次
数字键的问题我也遇到了,还不知道该咋整


页首
 用户资料  
 
3 楼 
 文章标题 :
帖子发表于 : 2006-11-01 13:57 

注册: 2006-09-30 21:21
帖子: 46
送出感谢: 0 次
接收感谢: 0 次
把gnome-settings-daemon添加到会话的启动程序中可以解决这些问题
但是新的问题来 了,把gnome-settings-daemon添加到会话的启动程序中后,再beryl-manager选beryl管理器的话,也会出现框架周围的闪动,而且好像很占资源,还没几分钟就死机了


页首
 用户资料  
 
4 楼 
 文章标题 :
帖子发表于 : 2006-11-01 14:08 
头像

注册: 2006-10-01 14:34
帖子: 608
送出感谢: 0 次
接收感谢: 0 次
哪咋办?


页首
 用户资料  
 
5 楼 
 文章标题 :
帖子发表于 : 2006-11-01 14:29 

注册: 2006-09-30 21:21
帖子: 46
送出感谢: 0 次
接收感谢: 0 次
哈哈,刚解决sudo gedit /usr/bin/startxgl.sh
把最后一行改成
exec dbus-launch --exit-with-session gnome-session

我在会话启动程序里没有添加任何的东西,都是默认的
只需要把startxgl改成
#!/bin/sh
Xgl -fullscreen :1 -ac -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec dbus-launch --exit-with-session gnome-session
即可

我的是ati9550的显卡,显卡驱动装上去之后3d的测试效果并不理想
现在用xgl+beryl在edgy下基本正常,不过cpu使用率太高了
我是按照下面的方法(网址忘了,帖出来算了,但是其中的关于startxgl就按照我上面的改就是了,我只更改过会话里的会话选项,把beryl-manager和beryl-xgl加了进去,不过应该没什么用)
引用:
Install/Ubuntu/Edgy/XGL
From Beryl Wiki
Jump to: navigation, search
Contents
[hide]

* 1 Introduction
* 2 Installing Graphic Card drivers
* 3 Adding repositories
* 4 Installing Xgl & Beryl
* 5 Configuration
* 6 Running Beryl


[edit]
Introduction

Installing Xgl and Beryl in (K)Ubuntu Edgy Eft is simple. Getting it working is slightly more complex, but this how-to should make it all as easy as possible.

Not to compete, but here is a very easy and all graphical guide, without the use of terminal, and a lot of screenshots. Link to guide - here

Maybe a section on migrating from the previous Compiz setup, including what packages need to be removed first, such as Compiz, to avoid conflict.
[edit]
Installing Graphic Card drivers
Note:

Before you try to install Xgl, you should have direct rendering enabled; how to do this depends on your video card - see here for nVidia 8xxx series drivers, and here for ATi fglrx drivers.

You can check where direct rendering is enabled by running

glxinfo |grep direct

in a terminal. If it shows

direct rendering: Yes

then you can continue with installing Xgl.
[edit]
Adding repositories

First, you need to add the Beryl repository to your /etc/apt/sources.list - this can be done (as root) with a text editor, or by using Synaptic or Adept. The line to be added is

deb http://ubuntu.beryl-project.org/ edgy main-edgy

Append 'main-edgy-amd64' to that line for x86_64 architectures. Note that other mirrors are available if you find yourself getting slow speeds from the primary host - go here to see a list of available sites.

The packages in the repository are signed with a key, so you can verify that they are valid. To add the key, use Synaptic/Adept or run:

wget http://ubuntu.beryl-project.org/quinn.key.asc --quiet -O - | sudo apt-key add -


Note that apt-key must be run as root, or using sudo.
[edit]
Installing Xgl & Beryl

Xgl is contained in the Ubuntu package xserver-xgl. Next, run:

sudo apt-get update
sudo apt-get install beryl beryl-core beryl-plugins beryl-plugins-data \
beryl-settings beryl-manager emerald emerald-themes xserver-xgl

Alternatively, install the packages using Adept or Synaptic.
[edit]
Configuration

Now that Beryl and Xgl are installed, you need a way to start them up. It is best to have a separate session (in gdm or kdm) for Xgl, as some applications don't run properly in an Xgl session.

To create the session, create the file '/usr/share/xsessions/xgl.desktop', and give it the following contents using your favourite text editor (again, as root or using sudo):

[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/bin/startxgl.sh
Icon=
Type=Application

Note that xgl.desktop calls a file that currently doesn't exist - '/usr/bin/startxgl.sh'. The contents of this file vary, according to whether you are using GNOME or KDE (users of other WMs, feel free to add your startxgl.sh to the end of this list).

Again, create this as root/sudo in your favourite text editor (for example: sudo gedit /usr/bin/startxgl.sh):

For an NVIDIA graphics card:

GNOME

#!/bin/sh
Xgl :1 -fullscreen -ac -accel xv:fbo -accel glx:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session

KDE

#!/bin/sh
Xgl :1 -fullscreen -ac -accel xv:fbo -accel glx:pbuffer &
sleep 4
export DISPLAY=:1
exec startkde

OR: For an ATI graphics card:

GNOME

#!/bin/sh
Xgl -fullscreen :1 -ac -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session

KDE

#!/bin/sh
Xgl :1 -fullscreen -ac -accel xv:pbuffer -accel glx:pbuffer &
sleep 4
export DISPLAY=:1
exec startkde

Now (yet again as root/sudo), you need to make the script executable - this can be done in Nautilus or Konqueror, or in the terminal:

sudo chmod a+x /usr/bin/startxgl.sh

Now when GDM or KDM starts, you should have a session called 'Xgl' available for selection; if you log into this session, Xgl will run (via the startxgl.sh script) and load GNOME or KDE for you. Logging into your normal session will give you a standard, un-accelerated desktop for trouble-shooting or running programs which don't play nicely with Xgl.
[edit]
Running Beryl

Now it's time to test Beryl. Open a terminal, and run:

beryl-manager

If all goes well Beryl should throw out a splash screen, and your windows will suddenly become wobbly! Also note that there is a new icon in your system tray - this allows you to control Beryl, run BSM (the Beryl settings manager) or Emerald (the theme manager). It also provides fallback to another window manager, in case Beryl crashes.

If you don't get a splash screen immediately, you may need to tell the manager to load Beryl - right-click on the red gem, go to "Select Window Manager" and choose "Beryl". If that doesn't work, there's a problem somewhere! Hopefully, useful debugging output will be in the terminal session; Ubuntu users can ask for help at #ubuntu-xgl, or the stock #xgl channel on irc://irc.freenode.net/

Assuming all goes well, you can set up Beryl Manager to start up every time you load into your Xgl session.

GNOME

* Go to System ---> Preferences ---> Sessions
* Go to the Startup Programs tab
* Click the 'Add' button and type in 'beryl-manager'
* Click the 'Add' button and type in 'beryl-xgl'
* Exit

KDE

Simpler - but less graphical. In a terminal:

ln -s /usr/bin/beryl-manager ~/.kde/Autostart/beryl-manager


Note on Window Decorations

If Window decorations does not show up, try running beryl-xgl. Open a terminal, and run:

beryl-xgl

In case this solves the problem, add beryl-xgl to Startup Programs or Autostart using the methods mentioned above, replacing beryl-manager with beryl-xgl.



For those who want to still utilize gnome GTK themes and icon settings you will need todo the following:

1. Go to System --> Preferences --> Sessions
2. Click the "Add" button and type in 'gnome-settings-daemon'
3. Exit
4. For people using who want to start this before you restart X simply type 'gnome-settings-daemon &' in a console.


页首
 用户资料  
 
6 楼 
 文章标题 :
帖子发表于 : 2006-11-01 14:30 

注册: 2006-09-30 21:21
帖子: 46
送出感谢: 0 次
接收感谢: 0 次
顺便贴上我的xorg.conf
代码:
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "ServerLayout"
   Identifier     "Default Layout"
   Screen      0  "aticonfig-Screen[0]" 0 0
   InputDevice    "Generic Keyboard"
   InputDevice    "Configured Mouse"
   InputDevice    "stylus" "SendCoreEvents"
   InputDevice    "cursor" "SendCoreEvents"
   InputDevice    "eraser" "SendCoreEvents"
EndSection

Section "Files"

   # path to defoma fonts
   FontPath     "/usr/share/X11/fonts/misc"
   FontPath     "/usr/share/X11/fonts/cyrillic"
   FontPath     "/usr/share/X11/fonts/100dpi/:unscaled"
   FontPath     "/usr/share/X11/fonts/75dpi/:unscaled"
   FontPath     "/usr/share/X11/fonts/Type1"
   FontPath     "/usr/share/X11/fonts/100dpi"
   FontPath     "/usr/share/X11/fonts/75dpi"
   FontPath     "/usr/share/fonts/X11/misc"
   FontPath     "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
   Load  "i2c"
   Load  "bitmap"
   Load  "ddc"
   Load  "dri"
   Load  "extmod"
   Load  "freetype"
   Load  "glx"
   Load  "int10"
   Load  "type1"
   Load  "vbe"
EndSection

Section "InputDevice"
   Identifier  "Generic Keyboard"
   Driver      "kbd"
   Option       "CoreKeyboard"
   Option       "XkbRules" "xorg"
   Option       "XkbModel" "pc105"
   Option       "XkbLayout" "us"
   Option       "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
   Identifier  "Configured Mouse"
   Driver      "mouse"
   Option       "CorePointer"
   Option       "Device" "/dev/input/mice"
   Option       "Protocol" "ExplorerPS/2"
   Option       "ZAxisMapping" "4 5"
   Option       "Emulate3Buttons" "true"
EndSection

Section "InputDevice"

                                                      # /dev/input/event
                                                      # for USB
   Identifier  "stylus"
   Driver      "wacom"
   Option       "Device" "/dev/wacom"          # Change to
   Option       "Type" "stylus"
   Option       "ForceDevice" "ISDV4"               # Tablet PC ONLY
EndSection

Section "InputDevice"

                                                      # /dev/input/event
                                                      # for USB
   Identifier  "eraser"
   Driver      "wacom"
   Option       "Device" "/dev/wacom"          # Change to
   Option       "Type" "eraser"
   Option       "ForceDevice" "ISDV4"               # Tablet PC ONLY
EndSection

Section "InputDevice"

                                                      # /dev/input/event
                                                      # for USB
   Identifier  "cursor"
   Driver      "wacom"
   Option       "Device" "/dev/wacom"          # Change to
   Option       "Type" "cursor"
   Option       "ForceDevice" "ISDV4"               # Tablet PC ONLY
EndSection

Section "Monitor"
   Identifier   "SyncMaster"
   Option       "DPMS"
EndSection

Section "Monitor"
   Identifier   "aticonfig-Monitor[0]"
   Option       "VendorName" "ATI Proprietary Driver"
   Option       "ModelName" "Generic Autodetecting Monitor"
   Option       "DPMS" "true"
EndSection

Section "Device"
   Identifier  "ATI Technologies, Inc. RV350 AS [Radeon 9600]"
   Driver      "fglrx"
   BusID       "PCI:1:0:0"
EndSection

Section "Device"
   Identifier  "aticonfig-Device[0]"
   Driver      "fglrx"
   Option       "VideoOverlay" "on"
   Option       "OpenGLOverlay" "off"
   Option       "DRI" "true"
   Option       "ColorTiling" "on"
   Option       "EnablePageFlip" "true"
   Option       "AccelMethod" "EXA"
   Option       "XAANoOffscreenPixmaps"
   Option       "RenderAccel" "true"
   Option       "AGPFastWrite" "on"
EndSection

Section "Screen"
   Identifier "Default Screen"
   Device     "ATI Technologies, Inc. RV350 AS [Radeon 9600]"
   Monitor    "SyncMaster"
   DefaultDepth     24
   SubSection "Display"
      Depth     1
      Modes    "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
   EndSubSection
   SubSection "Display"
      Depth     4
      Modes    "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
   EndSubSection
   SubSection "Display"
      Depth     8
      Modes    "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
   EndSubSection
   SubSection "Display"
      Depth     15
      Modes    "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
   EndSubSection
   SubSection "Display"
      Depth     16
      Modes    "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
   EndSubSection
   SubSection "Display"
      Depth     24
      Modes    "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
   EndSubSection
EndSection

Section "Screen"
   Identifier "aticonfig-Screen[0]"
   Device     "aticonfig-Device[0]"
   Monitor    "aticonfig-Monitor[0]"
   DefaultDepth     24
   SubSection "Display"
      Viewport   0 0
      Depth     24
   EndSubSection
EndSection

Section "DRI"
   Mode         0666
EndSection

Section "Extensions"
        Option  "Composite" "0"
EndSection


页首
 用户资料  
 
7 楼 
 文章标题 :
帖子发表于 : 2006-11-01 14:37 

注册: 2006-09-30 21:21
帖子: 46
送出感谢: 0 次
接收感谢: 0 次
xorg.conf里面出现了两处"device",我不知道其中的一个是不是可以删掉
我用论坛里的硬盘安装desktop的引导包硬盘安装不了,老是黑屏
后来我就把第一个device下的driver处改成了vesa,这样才进入安装
安装好之后马上装8.29的ati驱动,装好驱动之后就有了两个device,前面的没有被覆盖掉,仍旧是vesa,所以我干脆把vesa也改成了fglrx


页首
 用户资料  
 
显示帖子 :  排序  
发表新帖 回复这个主题  [ 7 篇帖子 ] 

当前时区为 UTC + 8 小时


在线用户

正在浏览此版面的用户:没有注册用户 和 3 位游客


不能 在这个版面发表主题
不能 在这个版面回复主题
不能 在这个版面编辑帖子
不能 在这个版面删除帖子
不能 在这个版面提交附件

前往 :  
本站点为公益性站点,用于推广开源自由软件,由 DiaHosting VPSBudgetVM VPS 提供服务。
我们认为:软件应可免费取得,软件工具在各种语言环境下皆可使用,且不会有任何功能上的差异;
人们应有定制和修改软件的自由,且方式不受限制,只要他们自认为合适。

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
简体中文语系由 王笑宇 翻译