装KDE4.2过程记录，不妥的地方请大家指出（安装基本完成）

lofeng

# emerge -av xorg-server
后的输出如下：

* IMPORTANT: 1 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.


These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] x11-base/xorg-server-1.5.3-r6 USE="hal ipv6 nptl sdl xorg -3dfx -debug -dmx -kdrive -minimal -tslib" INPUT_DEVICES="evdev* keyboard mouse -acecad -aiptek -calcomp -citron -digitaledge -dmc -dynapro -elo2300 -elographics -fpit -hyperpen -jamstudio -joystick -magellan -microtouch -mutouch -palmax -penmount -spaceorb -summa -synaptics -tek4957 -tslib -ur98 -virtualbox -vmmouse -void -wacom" VIDEO_CARDS="vmware -apm -ark -ast -chips -cirrus -dummy -epson -fbdev -fglrx -geode -glint -i128 -i740 (-impact) -imstt -intel -mach64 -mga -neomagic (-newport) -nv -nvidia -r128 -radeon -radeonhd -rendition -s3 -s3virge -savage -siliconmotion -sis -sisusb (-sunbw2) (-suncg14) (-suncg3) (-suncg6) (-sunffb) (-sunleo) (-suntcx) -tdfx -tga -trident -tseng -v4l -vermilion -vesa -via -virtualbox -voodoo -xgi" 0 kB
[ebuild N ] x11-drivers/xf86-input-evdev-2.1.3 USE="hal -debug" 272 kB

偷懒，直接
# emerge -av /usr/portage/x11-drivers/xf86-input-evdev/xf86-input-evdev-2.1.3.ebuild

然后
#startx

顺利进入KDE，鼠标、键盘均有反应，效果也很炫

lofeng

Post by 亞利艾爾;2004624
给你个我个人认为稳当的做法。USE="hal" 打开，INPUT_DEVICES就设置个evdev。把/etc/X11/xorg.conf删除了，也不要再用X -configure创建了。这样之后 emerge -DNu xorg-server就没有事了。

多谢 只是刚开始装xorg-server时不懂hal的作用，没有将INPUT_DEVICES就设置为evdev 所以导致后来的很多问题

nonplus

Post by 亞利艾爾;2004623
　　想不到你这么干净。连HAL都不要了……
　　我是觉得吧，如果我知道那个东西是干什么的，一般还是会根据需要把那个设置一下；如果不知道，就看大部分发行版怎么做了，或者Gentoo文档怎么说。这样出问题好解决。
　　说来FreeDesktop.org在搞DeviceKit吧。现在又什么都Kit了……

呵呵,本子性能太弱,高端东西用不起...
曾经试过开hal dbus用wicd
结果进系统时总要卡上几秒,怒,清了,自己写脚本了事

hal对我来说仅仅只能用于挂载而已,当udev rules可以实现相同功能时hal已然无用
dbus原先的libnotify还要用到,如今,发现dzen,于是dbus也将在我机上走入历史

其实kde4很好,可惜目前好像没法对特效进行单独处理(不编译),后端也还在xine,据说mplayer还在研发,等其完善尝试一下

lofeng

#vim /etc/conf.d/xdm
修改：
DISPLAYMANAGER="kdm"

#rc-update add xdm default

并
#rc-update add hald default（添加这个是因为前面都是在ssh中手动开启hald服务的）

然后重启，出现kdm登陆界面
但是每次输入用户名及密码后回车，仍回到KDM登陆界面
而在命令行中同样的用户、同样的密码是可以登录的

亞利艾爾

你确定你安装了kdebase-startkde了吗？就是desktop那些。一般出这种情况可能有些包没有安装。

lofeng

我装的是kdebase-meta:4.2，最基本的包应该都装上去了

然后重启，出现kdm登陆界面
但是每次输入用户名及密码后回车，仍回到KDM登陆界面
而在命令行中同样的用户、同样的密码是可以登录的

#vim /usr/portage/kde-base/kdm/kdm-4.2.4.ebuild

if use consolekit; then
        echo
        elog "You have compiled 'kdm' with consolekit support. If you want to use kdm,"
        elog "make sure consolekit daemon is running and started at login time"
        elog
        elog "rc-update add consolekit default && /etc/init.d/consolekit start"
        echo
    fi

#/etc/init.d/consolekit status
输出时shopped
然后我
#rc-update add consolekit default

即解决问题

lofeng

KDE起来了
下面去解决/var/log/Xorg.0.log和/var/kdm.log中提到的EE和WW

lofeng

localhost_lofeng ~ # cd /var/log/
localhost_lofeng log # grep EE Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) Unable to locate/open config file
(II) Loading extension MIT-SCREEN-SAVER
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) Failed to load module "vesa" (module does not exist, 0)

不是说是用hal，就不需要xorg.conf文件了么？那怎么还会有“Unable to locate/open config file”这个提示？

以下摘自http://www.x.org/wiki/FAQErrorMessages

This means that [color="red"]the Xserver cannot find a configuration file because it has not been properly configured. Please check FAQMiscellaneous for information how to configure your Xserver.

Another reason for this error may be that you have created a configuration file but it is not in the correct location. The Xserver checks for configuration files at different locations. The usual locations are: /etc/X11/xorg.conf or /etc/X11/XF86Config-4.
Another reason for this message may be that your Xserver cannot read the file because the server binary has the wrong permission. On UN*X like systems the server is usually owned by root and runs with the SUID bit set so that it runs with root privileges even if started by an ordinary user. Therefore it should be able to open the configuration file regardless of who owns it or of its permissions. Please check "How do I check if my server bianry has the correct permissions?" on the FAQMiscellaneous page for futher information

以下摘自：http://www.x.org/wiki/FAQMiscellaneous

You may want to use the graphical tool xorgcfg to do your Xserver configuration or you may let the server generate it's own configuration file by running: X -configure as root. It will create the configuration file xorg.conf.new in the home directory of the user who ran it (usually root). [color="Red"]You should then copy this file to the default location /etc/X11/xorg.conf.
Please note: Xorg can only autodetect PCI and AGP video chipsets. If you still use an ISA/EISA/VL chipset you need to at least know the chipset vendor to specify the correct driver. Most drivers can then autodetect the chipset model.

(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) Failed to load module "vesa" (module does not exist, 0)

这两个问题应该是默认的内核配置中没有包含这两个模块，看来要通过重新编译内核来解决了

lofeng

localhost_lofeng log # grep WW Xorg.0.log
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/misc/".
(WW) The directory "/usr/share/fonts/TTF/" does not exist.
(WW) The directory "/usr/share/fonts/OTF" does not exist.
(WW) The directory "/usr/share/fonts/Type1/" does not exist.
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) Warning, couldn't open module fbdev
(WW) Warning, couldn't open module vesa
(WW) VMWARE(0): Unable to estimate virtual size

那几个font目录找不到应该是因为我安装的是xorg-server而不是xorg-x11，所以有很多字体就没有安装上，这个应该没有问题，可以考虑emerge 相应的字体包。如果有配置文件，应该在配置文件xorg.conf没有问题了，但是用了hal，貌似不用配置文件xorg.conf了。所以那几个包得安装上了。

以下摘自：http://www.nabble.com/About-%22X ... %22-td23920203.html

First, I changed the xorg guide to recommend installing xorg-server rather than xorg-x11. Functionally the two are identical, though the later versions of xorg-x11 (~arch will soon go stable) add in dozens of unnecessary font packages in many different languages. It's all just bloat, so that warning is now in the guide.

(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)

http://acpid.sourceforge.net/
/var/run/acpid.socket 要运行acpid 才有
沒有 /var/run/acpid.socket 并不影响X-widows 的工作

lofeng

Markers: (--) probed, (**) from config file, [color="Red"](==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[color="red"](==)[color="red"] Log file: "/var/log/Xorg.0.log", Time: Thu Jul  9 14:43:01 2009

/var/log/kdm.log中的错误应该源自Xorg.0.log

localhost_lofeng log # [color="Red"]grep EE kdm.log   
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) Unable to locate/open config file
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) Failed to load module "vesa" (module does not exist, 0)
localhost_lofeng log # [color="red"]grep WW kdm.log
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.