http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc/kernel-config I'm still working on the perfect kernel config, but here's what I http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc/kernel-config Sun, 11 Nov 2007 19:08:44 -0600 http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc/ipw3945-drivers Fedora 7 and 8 both ship iwl3945, an arguably better driver for the Intel 3945ABG wireless cards. However, I find that ipw3945 works more reliably and has the wifi light indicator which works. To use the ipw3945 drivers, you can use the ATRPMs repository. ATRPMs keeps up pretty well with the FC kernel release schedule, and provides drivers to use. I was afraid the wireless would be hit and miss, but so far it works wonderfully. Install Drivers Simply add ATRPMs to your /etc/yum.repos.d directory, set it to DISABLED (**), then run the following as root in a terminal/console: yum --enablerepo=atrpms install ipw3945 This should install only the following files (the two noted in bold will need updating with every new kernel as mentioned later). If for some reason it doesn't install the following, you may try listing each one on the yum install line, so instead of just ipw3945d also specify the other files below: ieee80211-kmdl ipw3945-kmdl ipw3945-ucode ipw3945 ipw3945d The kernel modules and userspace module, firmware, etc, should now be downloaded. Easy Configuration I've found using an init script is easier to use and more reliable than the original solution I found for loading the daemon/modules, so http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc/ipw3945-drivers Fri, 16 Nov 2007 21:44:37 -0600 http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc/acpi-suspend Gathering some various information on the web, I've put together a ACPI Suspend script which seems to work pretty well, and even works perfect on the stock Fedora Core 6 kernel. Basically just need to stop a few services and unload a few modules before suspending. Suspend to ram and disk seems to work rather well. Speed is very acceptable for suspend to disk, and suspend to ram happens almost immediately. Only caveat is gkrellm crashes sometimes on restore, I think it is the CPU monitor plugin I am using. This was most definitely a CPU plugin, I've disabled it and no gkrellm problems since. The script can be downloaded here and should hopefully work for you without any caveats. It defaults to suspend to ram, but if you pass it an argument of hibernate it will suspend to disk. I can run this from X or console and it should work fine. If you run this from console, you'll want to edit the last commands in the script to perhaps go to vt 2 and back rather than vt 7 (where X is for me). If you have any suggestions, send them on. The script does a few various things that I want it to do which you might have no interest in... I've commented those types of things in the script itself. http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc/acpi-suspend Thu, 11 Oct 2007 20:26:07 -0500 http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc/media-key-assignments The V100 has multimedia keys on the top of the keyboard as well as on some Fn key combinations, and below is how I'm using them. You can then assign these keys in your favorite programs as the associated F key listed, such as the Stop key is F15. # Decrease Vol key near LCD xmodmap -e 'keycode 174 = F13' # Increase Vol key near LCD xmodmap -e 'keycode 176 = F14' # Stop (Fn-Up) xmodmap -e 'keycode 164 = F15' # Play (Fn-Down) xmodmap -e 'keycode 162 = F16' # Back (Fn-Left) xmodmap -e 'keycode 144 = F17' # Forward (Fn-Right) xmodmap -e 'keycode 153 = F18' # Mute (Fn-Esc) xmodmap -e 'keycode 160 = F19' And if the caps lock key annoys you as it does me, you can convert it into a control key with the following: xmodmap -e 'remove Lock = Caps_Lock' xmodmap -e 'keysym Caps_Lock = Control_L' xmodmap -e 'add Control = Control_L' Easiest way to use this is to put the commands into your .Xclients, .xinitrc, or a Desktop Environment startup script (such as ~/.kde/Autostart/startup for an example) http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc/media-key-assignments Thu, 08 Mar 2007 21:51:28 -0600 http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc/acpi-event-script I've had an ACPI event script for several years now to automagically tweak the CPU speed, brightness, hard drive APM, etc. I've tweaked it to work nicer with the V100. Unfortunately even with the 6 hour battery, I don't quite get 4 hours under light use (wireless, ssh, a little web browsing). There might be additional things to tweak to help in this regard. The V100 seems to let me spin the disks down better than my old laptop, a Sony SRX87, not sure what the differences are. The Sony would spin back up all the time, where the V100 seems to stay completely off until I force something to load. I haven't left the machine idle and watched it to see how long it'll stay inactive, but so far it seems good. So this script turns down the max CPU (to 1ghz) when off AC, turns the brightness down to 30 (minimum, but usable) and turns on hard drive APM, restores them when back on AC, turns everything down as much as possible when the lid is closed (see bootnote), suspends the laptop when the power button is pressed and Hibernates when the Suspend (Fn+F4) sequence is pressed (see my Suspend script). In case you're wondering, the Fn+F12 (Hibernate) sequence doesn't seem to create an ACPI event, so this setup works for me and is very easy to change. You can grab the file here which is the action.sh and an event file. They should go into your /etc/acpi directory. Please make sure the script matches your laptop in terms of where the CPU information is, batteries, etc. Beyond that, run tail -f /var/log/acpid and see if the script works. If you need help tweaking it, let me know. As a bootnote, here's the other keys which do not create ACPI events: Lid open event (the lid close event "completes" but I can't seem to catch this in my ACPI action script?) -- CORRECTION, had conflicting scripts, this is fine now! Fn-F12 (Hibernate) - Does not seem to create an ACPI or XEV event Fn-F7 (switch monitor) - Does not seem to create an ACPI or XEV event http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc/acpi-event-script Thu, 08 Mar 2007 21:47:34 -0600 http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc/battery-shutdown-script Don't miss my script in the parent of this section, Linux, as it contains a nice battery script tailored for the V100 to shut down nicely when the battery gets too low. Currently it's set to shut down, but I'll be modifying it for hibernation soon. If you run a DE like Gnome or KDE, they can handle this themselves but not in a very flexible way. For instance if I am not paying attention and my battery level gets critical, KDE will immediately shut the laptop down. With my script, I have some minutes of warning before this happens and if I plug it into the AC the machine doesn't shut down on me. http://webgui.theblackmoor.net/home/linux/v100/tips-tricks-scripts-etc/battery-shutdown-script Wed, 07 Mar 2007 11:30:59 -0600