Slackware 11.0使用手记If you notice, there are some init scripts that are executable that you might not need and some that you might want. You can disable/enable these Slackware boot scripts by changing the executable bit: chmod -x rc.(script name)One thing that jumped out at me was, since I installed the new 2.6 kernel, the old rc.modules-2.4.33.3 module loading boot script is still executable. I don't need this to run since I'm using the new 2.6 kernel that I've installed, so: chmod -x rc.modules-2.4.33.3Also, the symbolic link rc.modules still pointed to the old 2.4 modules script, so I removed that and re-linked rc.modules to the 2.6 script: rm rc.modulesCPU Frequency Scaling If you've got a laptop or a newer CPU that supports dynamic frequency scaling, then you'll have to recompile the generic kernels Slackware provides - it's not supported by default. If you didn't install the 2.6 kernel source earlier on, you'll have to do that now. You can find the source and header packages in the /extra directory on the DVD. Dynamic frequency scaling means that your CPU's clock speed will be reduced during periods of relative inactivity. If you're just reading something on the screen or typing up an e-mail you don't need a lot of horsepower to complete those tasks, so the CPU's speed will be reduced. This conserves power, reduces heat and greatly extends your battery life for laptop users. Desktop users will find that it keeps their computer running cooler and quieter. When you need the speed for compiling a program, playing a game or starting a new application, the CPU's frequency will be increased to match the workload. I learned that the proc "performance" interface has been deprecated, so you'll have to use the interface in /sys/devices/system/cpu/cpu0/cpufreq to control the frequency governor. When I checked the scaling_governor file, it's "userspace" by default, but I compiled the "conservative" governor too (which gracefully increases/decreases the cpu frequency) so to use this governor: echo conservative > scaling_governorCheck the cpu frequency now: cat /proc/cpuinfoMuch better, huh? Once the action increases, the cpu frequency will incrase to match. If you're in X, you can fire up your favorite CPU monitoring applet and watch the frequency rise and fall as you work. Now, this change isn't permanent but Slackware has given us a handy boot script to add our user-defined boot time options. Open up /etc/rc.d/rc.local and add a line at the end that says: echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governorNow your dynamic cpu frequency scaling will take effect every time you boot. If you want more information on ACPI, check out their website:
http://acpi.sourceforge.net/documentation/ Aren't you learning some interesting stuff about your computer by tweaking these things by hand? I love this stuff... GUI Configuration
My laptop display resolution wasn't configured by default, so I had to edit the xorg.conf file and correctly specify the 1920x1200 resolution at all color depths. Plus, Slackware doesn't come with binary driver support for ATI or nVidia graphics cards but you can easily add them by downloading the latest version and following the install directions for whichever card you have. The Open Addict DELL XPS M170 test laptop comes with a nVidia card, so I grabbed the latest drivers from nvidia.com and installed from that point. No big deal there. KDE is the default desktop environment for most people but you do have the option of installing others like the excellent and lightweight XFCE 4.2.3.2. Slackware 11 ships with KDE version 3.5.4 and X.org 6.9.0, so the desktop is pretty new. Tweaking the desktop was a piece of cake and the GUI felt very light and responsive.  上一篇：slackware 11.0 安装及基本配置 下一篇：Slackware Linux启动过程详解 更多相关文章
|
推荐文章
精彩文章
|
