https://www.thinkwiki.org/w/api.php?action=feedcontributions&user=Pfps&feedformat=atomThinkWiki - User contributions [en]2024-03-29T14:28:35ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=Installing_Fedora_11_on_a_ThinkPad_T60&diff=43138Installing Fedora 11 on a ThinkPad T602009-05-06T16:57:23Z<p>Pfps: minor cleanup</p>
<hr />
<div>{{NOTE|This is based on the x86-64 pre-release version of Fedora 11, but should give a good indication of what to expect of the final release}}<br />
<br />
{{NOTE|ThinkPad T60p is reported here as well}}<br />
<br />
== Success Chart ==<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
|colspan=2| '''Item''' || '''Working''' || '''Notes'''<br />
|-<br />
|rowspan=3|Installation <br />
| Local CD/DVD install || {{Cyes}} ||<br />
|-<br />
| Network Installation || {{Cyes}} ||<br />
|-<br />
| USB Installation || {{Cyes}} ||<br />
|- <br />
|rowspan=3|Display - Intel<br />
| Laptop Screen || {{Cyes}} || only 1 video mode available<br />
|-<br />
| VGA || {{Cyes}} || with hotplug only ?<br />
|-<br />
| DVI || {{Cyes}} || with hotplug only ?<br />
|-<br />
|rowspan=3|Display - ATI<br />
| Laptop Screen || {{Cyes}} || everything works, including rotation<br />
|-<br />
| VGA || {{Cyes}} || everything works, including rotation and mirroring<br />
|-<br />
| DVI || {{Cunk}} (should work) || no reason this wouldn't work<br />
|-<br />
|rowspan=2|Power Management<br />
| Software Suspend (hibernate) || {{Cyes}} || <br />
|-<br />
| Suspend to Memory (ACPI sleep) || {{Cyes}} || <br />
|-<br />
|colspan=2| Audio || {{Cyes}} ||<br />
|-<br />
|rowspan=5| Wireless || WiFi - Atheros|| {{Cyes}} || occasional disconnect/reconnect<br />
|-<br />
| WiFi - Intel|| {{Cyes}} || no problems at all<br />
|-<br />
| Bluetooth || {{Cyes}} ||<br />
|-<br />
| WWAN - Verizon || {{Cunk}} ||<br />
|-<br />
| WWAN - Cingular || {{Cunk}} ||<br />
|-<br />
| Extra Buttons || Keyboard Section || {{Cpart}} || see ThinkPad keyboard section below<br />
|-<br />
| rowspan=8|Ports<br />
| Ethernet || {{Cyes}} ||<br />
|-<br />
| Modem || {{Cno}} || Requires closed-source driver<br />
|-<br />
| Serial || {{Cyes}} || Requires port-replicator or dock<br />
|-<br />
| IrDA || {{Cno}} || Device is detected, but no device files are created<br />
|-<br />
| PS/2 Keyboard/Mouse || {{Cunk}} (should work)|| Requires port-replicator or dock<br />
|-<br />
| Parallel || {{Cunk}} (should work)|| Requires port-replicator or dock<br />
|-<br />
| USB || {{Cyes}} ||<br />
|-<br />
| PCMCIA/Cardbus || {{Cyes}} || even ATA adaptors (for CF cards, etc) now work!<br />
|-<br />
| colspan=2| Harddisk Active Protection || {{Cno}} || <br />
|-<br />
| colspan=2| Ultrabay device hotswap || {{Cpart}} || see below, use with<br />
caution out of the box<br />
|-<br />
| colspan=2| Fingerprint reader || {{Cunk}} (should work)|| F11 has standard support for Fingerprint readers<br />
|-<br />
| colspan=2| TPM (security subsystem) || {{Cunk}} || Not brave enough to mess around with it<br />
|-<br />
|}<br />
<br />
= Tested and Verified on Fedora 11 =<br />
<br />
Information in this section has been tested and verified using Fedora 11, including the pre-release (post-beta) version. The development version of Fedora 11 (rawhide) is quite stable and even suitable for day-to-day use, if you are a bit brave. You will be automatically switched over to the release version of Fedora 11 if you keep everything up to date.<br />
<br />
== Installation ==<br />
<br />
Installation is straight forward; you can follow the generic Fedora install instructions.<br />
<br />
== Configuration ==<br />
<br />
=== X Server (Intel)===<br />
Basic X server functionality should work out of the box on the ThinkPad LCD (LVDS), as long as no external displays are attached at boot. <br />
<br />
Fedora 11 uses KMS (Kernel Mode Setting) by default, which for now has some up and down sides for external displays.<br />
The down sides are that external displays attached during boot might not function properly (mostly they may have non-optimal resolution), but they do when hot plugged afterwards. Another down side is that currently mirror mode is very limited as the ThinkPad LCD (LVDS) is limited to one single display mode, so only if the external display supports this same mode can you activate mirror mode. On the other hand with KMS enabled the maximum virtual display size is now 4096x4096 (2048x2048 without KMS) meaning you can have an extended desktop.<br />
<br />
These issues have been reported to Red Hat bugzilla.<br />
<br />
On a T60p, displays work well, with multiple mirrored and non-mirrored displays and even with one of the displays being rotated! This may also work on a base T60, as there has been a lot of effort put into getting this to work right.<br />
<br />
One thing that still doesn't work quite right is screensavers and screen blanking. There is something wrong with the timers, which may result in your screen blanking while you are typing. Recovery is a simple as waiting until the screen is completely blank and then type or click to wake up the screen.<br />
<br />
Another thing that doesn't work quite right is screen resolution when booting with multiple screens. If one screen doesn't not have a preferred resolution, a poor resolution may be used for both screens during the booting process. Everything works fine after login, however.<br />
<br />
==== Desktop Effects ====<br />
Compiz (wobbly windows, desktops on a cube) seems to work. Direct display of video may be problematic with Compiz, however.<br />
<br />
=== dpi ===<br />
On the 1400x1050 (and 1600x1200) LCD Fedora comes up with a DPI of 124 (or higher). While this is correct for the physical screen size, it waists a lot of screen real estate.<br />
<br />
To change to the more typical 96 DPI, go to System -> Preferences -> Appearance. Now in Appearance Preferences select the Fonts tab and press the "Details ..." button. Here you can change the dots per inch to 96. Of course, many things will shrink, but that is what you wanted, after all.<br />
<br />
=== Wireless Network ===<br />
<br />
Both the Intel and Atheros wireless should work out of the box.<br />
<br />
Atheros was tested and works, but you may encounter occasional disconnects and reconnects. Intel wireless also works.<br />
<br />
=== ThinkPad keys ===<br />
ThinkPad keys are handled by a mixture of the thinkpad_acpi, acpi button, acpi dock and acpi video drivers.<br />
{{NOTE|Due to Xorg limitations, some keys that cause HAL events work with Xorg (ThinkVantage and Fn-F7) and others do not. This is a known limitation that should be fixed with the next major Xorg (v1.7) release.}}<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
| '''Key''' || '''Function''' || '''Handled by''' ||'''HAL event''' || '''Works''' || '''Notes'''<br />
|-<br />
| Fn-F2 || lock screen || thinkpad_acpi || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-F3 || battery || thinkpad_acpi || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-F4 || suspend || acpi button|| {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-F5 || wireless || thinkpad_acpi || {{Cyes}} || {{Cpart}} || No default action, but can be associated with gnome-keybinding-properties<br />
|-<br />
| Fn-F7 || videomode || thinkpad_acpi || {{Cyes}} || {{Cyes}} || Cycles through only LCD, only external, both (mirrored), and both (non-mirrored)<br />
|-<br />
| Fn-F8 || mouse input select || thinkpad_acpi || {{Cyes}} || {{Cpart}} || No default action, but can be associated with gnome-keybinding-properties<br />
|-<br />
| Fn-F9 || undock || thinkpad_acpi || {{Cyes}} || {{Cpart}} || No default action, but can be associated with gnome-keybinding-properties<br />
|-<br />
| Fn-F12 || hibernate || acpi button|| {{Cyes}} || {{Cpart}} || does the same as Fn-F4 (suspend), not hibernate <br />
|-<br />
| Fn-Home || brightness up || acpi video || {{Cyes}} || {{Cyes}} || includes on-screen display of brightness level<br />
|-<br />
| Fn-End || brightness down || acpi video || {{Cyes}} || {{Cyes}} || includes on-screen display of brightness level<br />
|-<br />
| Fn-PgUp || thinklight || - || {{Cno}} || {{Cyes}} || changing thinkpad_acpi hotkey_mask, causes HAL events. No OSD in any case.<br />
|-<br />
| Fn-Space || zoom || thinkpad_acpi || {{Cyes}} || {{Cno}} ||<br />
|-<br />
| VolumeUp || Volume Up || - || {{Cno}} || {{Cyes}} || changing thinkpad_acpi hotkey_mask, causes HAL events. But OSD is wrong<br />
|-<br />
| VolumeDown || Volume Down || - || {{Cno}} || {{Cyes}} || changing thinkpad_acpi hotkey_mask, causes HAL events. But OSD is wrong<br />
|-<br />
| Mute || Mute || - || {{Cno}} || {{Cyes}} || changing thinkpad_acpi hotkey_mask, causes HAL events and OSD. works as a on/off toggle<br />
|-<br />
| ThinkVantage || Vendor key ||thinkpad_acpi || {{Cyes}} || {{Cpart}} || No default action, but can be associated with gnome-keybinding-properties<br />
|-<br />
| NextTab || Browser Next tab || standard keyboard driver || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| PreviousTab || Browser Previous tab || standard keyboard driver || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-Up || Stop || standard keyboard driver || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-Left || reverse || standard keyboard driver || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-Right || forward || standard keyboard driver || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-Down || play/pause || standard keyboard driver || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Power || Power button || acpi button|| {{Cyes}} || {{Cyes}} || Need to press button for ~1 second to trigger event <br />
|-<br />
| Lid || Lid button || acpi button|| {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Dock || Dock eject button || acpi dock || {{Cyes}} || {{Cpart}} || causes unload of USB devices (including internal BlueTooth!!) and switch to battery mode. Does not restore video to ThinkPad only. Causes HAL event, but not a button event.<br />
|-<br />
| Ultrabay || Ultrabay eject switch || ??? || {{Cno}} || {{Cpart}} || causes a udev event, which can be handled as in [How to hotswap Ultrabay devices], with minor changes, but should be handled better<br />
|-<br />
| Radio switch || Radio kill switch || || {{Cyes}} || {{Cyes}} || previous comment on Bluetooth only may be a result of networkmanager keeping information around - however integration with networkmanager and bluetooth applet is not complete<br />
|-<br />
|}<br />
<br />
=== Ultrabay ===<br />
<br />
The Ultrabay has some glitches out of the box with respect to hotswapping. It is possible to lock the machine when pulling out devices, even the CD/DVD device.<br />
<br />
The culprit is that the Ultrabay pre-eject switch is not hooked into anything useful. It does cause udev events, but nothing is listening for them. When a device that has a mounted partition or CD is actually pulled out it is too late to do the right thing. Fedora 11 will usually just complain, sometimes bitterly, but may also lock up for some unknown reason, even if just pulling out a CD/DVD device with a mounted CD.<br />
<br />
Manually unmounting before removal will help. Manual powering down may also be required for correct performance. <br />
<br />
A better solution is to set up a udev rule and script to handle the pre-eject switch event for Ultrabay devices that have mountable things in them as in [How to hotswap Ultrabay devices].<br />
<br />
The revised solution here works well. Pushing the pre-eject switch either does the unmounting and powering off and then emits a low beep, or fails and then emits a triple beep. After success the device can be safely removed or the eject lever can be pushed back and everything will be remounted. After failure pushing the eject lever back in does nothing, permitting continuing as if nothing happened or allowing changes to be made before the next attempt to remove.<br />
<br />
Unfortunately the code below is complex and may be fragile. A better solution would be very useful.<br />
<br />
To set this solution up, first<br />
create the file /etc/udev/rules.d/50-ibm-ultrabay.rules owned by root and with context system_u:object_r:etc_runtime_t:s0<br />
<br />
<pre><br />
ENV{BAY_EVENT}=="3", ACTION=="change", SUBSYSTEM=="scsi", RUN+="/usr/local/sbin/ultrabay_eject"<br />
</pre><br />
<br />
Then create the executable file /usr/local/sbin/ultrabay_eject<br />
<pre><br />
#!/bin/bash<br />
<br />
ULTRABAY_SYSDIR=/sys$DEVPATH<br />
shopt -s nullglob<br />
logger ultrabay_eject storage device $DEVPATH<br />
<br />
# Umount the filesystem(s) backed by the given major:minor device(s)<br />
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl<br />
for $major_minor (@ARGV) {<br />
$major_minor =~ m/^(\d+):(\d+)$/ or die;<br />
push(@tgt_rdevs, ($1<<8)|$2);<br />
}<br />
# Sort by reverse length of mount point, to unmount sub-directories first<br />
open MOUNTS,"</proc/mounts" or die "$!";<br />
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;<br />
close MOUNTS;<br />
foreach $m (@mounts) {<br />
($dev,$dir)=@$m;<br />
next unless -b $dev; $rdev=(stat($dev))[6];<br />
next unless grep($_==$rdev, @tgt_rdevs);<br />
system("logger","ultrabay_eject","umounting",$dev,$dir);<br />
system("umount","-v","$dir")==0 or $bad=1;<br />
}<br />
exit 1 if $bad;<br />
EOPERL<br />
}<br />
<br />
# Get the UltraBay's /dev/foo block device node<br />
ultrabay_dev_node() {<br />
UDEV_PATH="`readlink -e "$ULTRABAY_SYSDIR/block/"*`" || return 1<br />
UDEV_NAME="`udevinfo -q name -p $UDEV_PATH`" || return 1<br />
echo /dev/$UDEV_NAME<br />
}<br />
<br />
if [ -d $ULTRABAY_SYSDIR ]; then<br />
sync<br />
# Unmount filesystems backed by this device<br />
## This seems to be very inelegant and prone to failure<br />
unmount_rdev `cat $ULTRABAY_SYSDIR/block/*/dev \<br />
$ULTRABAY_SYSDIR/block/*/*/dev` \<br />
|| {<br />
logger ultrabay_eject umounting failed<br />
echo 2 > /proc/acpi/ibm/beep; # triple error tone<br />
exit 1;<br />
}<br />
sync<br />
# Nicely power off the device<br />
DEVNODE=`ultrabay_dev_node` && hdparm -Y $DEVNODE<br />
# Let HAL+KDE notice the unmount and let the disk spin down<br />
sleep 0.5<br />
# Unregister this SCSI device:<br />
sync<br />
echo 1 > $ULTRABAY_SYSDIR/delete<br />
else<br />
logger ultrabay_eject no ultrabay device directory<br />
echo 2 > /proc/acpi/ibm/beep # triple error tone<br />
exit 1<br />
fi<br />
<br />
# We need sleep here so someone can disconnect the bay and the drive<br />
sleep 1<br />
<br />
# Turn off power to the UltraBay<br />
dock=$( /bin/grep ata_bay /sys/devices/platform/dock.?/type )<br />
dock=${dock%%/type:ata_bay} # needed for 2.6.27 and later<br />
if [ -n "$dock" -a -d "$dock" ]; then<br />
logger ultrabay_eject undocking $dock<br />
echo 1 > $dock/undock<br />
fi<br />
# Tell the user we're OK<br />
logger ultrabay_eject done<br />
echo 12 > /proc/acpi/ibm/beep<br />
</pre><br />
<br />
== Untested on Fedora 11 ==<br />
<br />
The Fingerprint reader and the WWAN options have not been tested yet. If you tried them with Fedora 11, please update the table.<br />
<br />
[[Category:T60]][[Category:Fedora]][[Category:T60p]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=How_to_hotswap_Ultrabay_devices&diff=43137How to hotswap Ultrabay devices2009-05-06T16:54:22Z<p>Pfps: add section at beginning on modern solutions to help with clutter</p>
<hr />
<div>The following discusses hotswap (AKA "hotplug") of devices in the [[Ultrabay]].<br />
<br />
This page has a lot of old information. Some cleanup might be useful.<br />
<br />
==Modern solutions==<br />
<br />
Recent kernels (2.6.29+, but probably earlier as well) have most of the stuff you need already, so you can just skip down to [[#Using_libata-acpi_and_udev|a udev solution]] if you want.<br />
<br />
A solution with a slightly more general script that is know to work for the {{T60}} and {{T60p}} under Fedora 11 is given in [[Installing Fedora 11 on a ThinkPad T60]].<br />
<br />
==Which driver?==<br />
This may be confusing, so first a quick history lesson.<br />
<br />
Older ThinkPads (up to the R51, T42p and X40) where fully IDE (PATA) for both the internal HDD and Ultrabay. For this there are two drivers, the modern libata based {{path|ata_piix}} and the old legacy {{path|ide-disk}} driver. Most modern distributions will default to the {{path|ata_piix}} driver, which is really what you want anyway.<br />
<br />
ThinkPads like the R52, T43, T43p, X41 and X41 Tablet are strange hybrids, they have a Serial-ATA (SATA) chipset for the internal disk controller, but through a separate SATA-PATA bridge chip the actual disk is still legacy IDE. The Ultrabay though is still connected to the legacy IDE host controller. This results in a setup where the internal disk is handled by a SATA driver and the Ultrabay is handled by either {{path|ata_piix}} or {{path|ide-disk}}.<br />
<br />
ThinkPads like the R60, T60 and Z60 series are also hybrids, but they use a native SATA HDD internal. Just like with the previous models though you end up with two separate drivers for the internal HDD and the Ultrabay.<br />
<br />
The latest generation ThinkPads like the R400, R500, T400, T500, W500, W700, X200, and X300 are all fully SATA for both the internal HDD and the Ultrabay device, so both are handled by the same SATA driver.<br />
{{Todo|Figure out in which category the X60 series ThinkPads truly belong. Some of these machines might have been shipped with a 1.8" HDD which is likely to be PATA, in fact the HMM even states so. But tabook and ltwbook only lists SATA models, so the 1.8" model might never have shipped. But even if it did there will be a SATA-PATA bridge chip, so from the OS it will look like SATA.}}<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|+Overview of disk interface types<br />
! width=140px|Thinkpad !! internal HDD !! Ultrabay !! Driver<br />
|-<br />
| {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{R50}}, {{R50e}}, {{R50p}}, {{R51}} || Legacy 2.5" IDE (PATA) || Legacy IDE (PATA) || ata_piix<br />
|-<br />
| {{R52}} || Legacy 2.5" PATA HDD with conversion to SATA || Legacy IDE (PATA) || ahci + ata_piix<br />
|-<br />
| {{R60}}, {{R61}} || 2.5" SATA || Legacy IDE (PATA) || ahci + ata_piix<br />
|-<br />
| {{R400}}, {{R500}} ||2.5" SATA || SATA || ahci<br />
|-<br />
| {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}} || Legacy 2.5" IDE (PATA) || Legacy IDE (PATA) || ata_piix<br />
|-<br />
| {{T43}}, {{T43p}} || Legacy 2.5" PATA HDD with conversion to SATA || Legacy IDE (PATA) || ahci + ata_piix<br />
|-<br />
| {{T60}}, {{T60p}}, {{T61}}, {{T61p}} || 2.5" SATA || Legacy IDE (PATA) || ahci + ata_piix<br />
|-<br />
| {{T400}}, {{T500}} ||2.5" SATA || SATA || ahci<br />
|-<br />
| {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X32}} || Legacy 2.5" IDE (PATA) || Legacy IDE (PATA) || ata_piix<br />
|-<br />
| {{X40}} || Legacy 1.8" IDE (PATA) || Legacy IDE (PATA) || ata_piix<br />
|-<br />
| {{X41}}, {{X41t}} || Legacy 1.8" PATA HDD with conversion to SATA || Legacy IDE (PATA) || ahci + ata_piix<br />
|-<br />
| {{X60}}, {{X60s}}, {{x60t}}, {{x61}}, {{x61s}}, {{x61t}} || 2.5" HDD is SATA, 1.8" HDD is PATA with SATA conversion || Legacy IDE (PATA) || ahci + ata_piix<br />
|-<br />
| {{X200}}, {{X200 Tablet}}, {{X300}}, {{X301}} ||2.5" SATA || SATA || ahci<br />
|-<br />
| {{W500}}, {{W700}} ||2.5" SATA || SATA || ahci<br />
|-<br />
|}<br />
<br />
<br />
==Choosing the right driver: new style <tt>ata_piix</tt> vs old style <tt>piix</tt> together with <tt>ide-disk</tt>==<br />
For ICH5,6,7,8, systems, whether you have an older IDE only thinkpad, or a newer thinkpad like the T/Z61p, there is one SATA bus for the system hard drive and an IDE bus for the Ultrabay (even if your Ultrabay happens to have a SATA drive, as it'll be seen as an IDE device), you'll have two drivers to chose from for your ultrabay: the old IDE/<tt>piix</tt>+<tt>ide-disk</tt> driver, and the newer PATA (=IDE) support of the newer <tt>ata_piix</tt> driver.<BR><br />
<tt>piix</tt>+<tt>ide-disk</tt> are part of the old original IDE driver and your Ultrabay device will show up as <tt>/dev/hda</tt>.<BR><tt>ata-piix</tt> is the new SATA/PATA (=IDE) driver that will cause your Ultrabay hard drive to show up as <tt>/dev/sda</tt> and your CD-ROM as <tt>/dev/sr0</tt>.<br />
<br />
The two things to know are: (1) you want to use <tt>ata_piix</tt> and (2) if you build <tt>piix</tt> in (CONFIG_BLK_DEV_PIIX enabled), or load it as a module, it'll take over the IDE bus and prevent ATA_PIIX from seeing your Ultrabay. You don't want that.<br />
<br />
The longer details are:<BR><br />
You don't want the <tt>piix</tt>+<tt>ide-disk</tt> combo because even as modules, you will not be able to unload <tt>piix</tt> to reset the bus if there are issues swapping devices (with <tt>ata_piix</tt>, even if you forget to unregister a drive before removing it, you can unload the module and reload it to reset the bus after the fact if you have a newer ThinkPad with a separate AHCI/SATA bus for the boot drive).<br />
<br />
As for hotswap, with <tt>piix</tt>+<tt>ide-disk</tt>, you can read the section below, but after more than one day of trying on 2.6.22.15 (as <tt>piix</tt>+<tt>ide-disk</tt> was taking over my IDE bus, and stopping me from using ata_piix before I removed it), I was not able to get hotswapping to work with piix+ide-disk (lt_hotswap would not even build on 2.6.22.15).<br />
<br />
hotswap just works with <tt>ata_pixx</tt> on 2.6.22, and reportedly with anything newer than 2.6.18, so you want to get rid of <tt>piix</tt>+<tt>ide-disk</tt>.<br />
There are several ways to do that:<br />
* if <tt>piix</tt> is built in your kernel (CONFIG_BLK_DEV_PIIX):<br />
** rebuild your kernel with CONFIG_BLK_DEV_PIIX turned off.<br />
** if you don't want to rebuild your kernel, try disabling the IDE bus grabbing by that driver with <tt>ide0=noprobe hda=noprobe hdb=noprobe</tt> in your grub/lilo config (adjust the drive letters as appropriate, but note that this did not work for me on 2.6.22.15: the drive didn't show up on the <tt>piix</tt> bus, but it didn't show up on the <tt>ata_piix</tt> bus either).<br />
* if <tt>piix</tt> is built in as a module<br />
** you can move out the module in {{path|/lib/modules/ver/kernel/drivers/ide/pci/piix.ko}} and reboot.<br />
** or build a new kernel, again with CONFIG_BLK_DEV_PIIX turned off.<br />
** or add <tt>options ide_core options="ide0=noprobe hda=noprobe hdb=noprobe"</tt> to your modprobe.conf is supposed to work too (but didn't work on 2.6.22.15, see comment above)<br />
<br />
Then, continue this document to see how to do hotswap with <tt>ata_piix</tt> (if you are lucky enough to have a newer SATA ThinkPad where the <tt>ata_piix</tt> driver only runs the Ultrabay, and you have a separate <tt>bus</tt> and <tt>ahci</tt> driver for your main drive, it is recommended to have <tt>ata_piix</tt> as a module (<tt>CONFIG_ATA_PIIX=m</tt>) so that you can unload/reload it if your bus gets in a bad state after a failed hotswap)<br />
{{NOTE|Debian users: at least up the the kernel released with Lenny, Debian applies a patch in the Debian kernel sources which prevents the use of <tt>ata_piix</tt> with PATA devices (like the IDE bus for the Ultrabay). You will have to either use an upstream kernel or (re)patch the Debian kernel sources. <br />
You may want to have a look at the following Debian bug reports as well: [http://bugs.debian.org/444182 #444182], [http://bugs.debian.org/463833 #463833].}}<br />
<br />
==When using the <tt>ata_piix</tt> driver==<br />
The following applies when using the <tt>ata_piix</tt> driver, which is necessary for many recent ThinkPad models that use an [[Intel ICH6-M]] controller. See also [[Problems with SATA and Linux]]. <br />
<br />
Mainline kernels before 2.6.18 cannot reliably recognize newly (re-)inserted Ultrabay drives without a reboot. There are experimental hotplug patches against pre-2.6.18 mainline kernels [http://home-tj.org/wiki/index.php/Libata-tj-stable here].<br />
<br />
* Available hotplug patches<br />
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.16.16-20060512.tar.bz2 Patch tarball against 2.6.16.16] ([http://lwn.net/Articles/183407/ Announce])<br />
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17-20060625-1.tar.bz2 Patch tarball against 2.6.17/2.6.17.1] ([http://article.gmane.org/gmane.linux.ide/11598 Announce])<br />
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17.4-20060710.tar.bz2 Patch tarball against 2.6.17.4]<br />
**[http://whoopie.gmxhome.de/linux/patches/2.6.17.14-tj/00-libata-tj-2.6.17.4-20060710.patch Patch against 2.6.17.14]<br />
<br />
* Confirmed to work on the following laptops, with bus the following ID <br />
**ThinkPad {{T23}}<br />
**ThinkPad {{T30}}<br />
**ThinkPad {{T43}}, {{T43p}}<br />
**ThinkPad {{R52}}<br />
**ThinkPad {{T60}} ID=4<br />
**ThinkPad {{T61}} ID=0<br />
**ThinkPad {{Z61p}} ID=4 (0-3:ahci, 5-6: ata_piix)<br />
ID will typically be 1 if you only have an IDE bus (0 is boot drive, 1 is Ultrabay), and it'll be 4 if you have a SATA bus your system boots from (ID 0-3) and an IDE bus for your Ultrabay (ID 4-5).<BR><br />
<b>Note that even on a given laptop model the ID can vary depending on whether your kernel has drivers that configure your boot drive is using the old style IDE driver (which doesn't add IDs before your Ultrabay), or whether your boot drive is using the new style driver (which adds IDs before your Ultrabay)</b><br />
<br />
Hotplug just works with kernels newer than 2.6.18 ( or older kernels that were patched to support <tt>ata_piix</tt> hotplug (don't try it otherwise!))<BR><br />
First, it is recommended you find the right SCSI ID for your drive to hotswap and unregister it before removing it (this works with all recent mainline kernels):<br />
{{cmdroot|echo 1 > /sys/class/scsi_device/$ID:0:0:0/device/delete}} <br />
{{cmdroot|echo eject > /proc/acpi/ibm/bay}}<br />
The drive can now be ejected (without this, your IDE bus may complain if you just yank a drive, but you can usually recover by unloading/reloading the <tt>ata_piix</tt> module on a SATA laptop if your main drive is not on the <tt>ata_piix</tt> bus)<br />
<br />
You can then issue the following after inserting an Ultrabay drive to rescan the port:<br />
{{cmdroot|echo 0 0 0 > /sys/class/scsi_host/host$ID/scan}}<br />
The inserted drive should now be recognized by the kernel, and appropriate {{path|/dev/*}} entries created automatically (e.g., by <tt>udev</tt>).<br />
<br />
Ted T'so has also written this hotswap patch, which may or may not be needed for you, see [http://www.mail-archive.com/linux-acpi@vger.kernel.org/msg04716.html hotswap patch] and report back<br />
<br />
===Scripts for hotswapping===<br />
<br />
The following scripts and [[acpid]] daemon configuration files do the following:<br />
* Automatically unmounts the relevant filesystems and power off the Ultrabay when the Ultrabay eject lever is released. Screams if some filesystem can't be unmounted.<br />
* Rescans the Ultrabay port when then Ultrabay eject lever is pushed back in.<br />
<br />
They assumes you're using the <tt>ata_piix</tt> driver with an appropriate kernel (see above).<br />
<br />
Create {{path|/usr/local/sbin/ultrabay_insert}} with permissions 755:<br />
<pre><br />
#!/bin/bash<br />
echo 12 > /proc/acpi/ibm/beep<br />
sync<br />
echo 0 0 0 > /sys/class/scsi_host/host1/scan<br />
</pre><br />
<br />
Create {{path|/usr/local/sbin/ultrabay_eject}} with permissions 755:<br />
<pre><br />
#!/bin/bash<br />
ULTRABAY_SYSDIR='/sys/class/scsi_device/1:0:0:0/device'<br />
shopt -s nullglob<br />
<br />
# Umount the filesystem(s) backed by the given major:minor device(s)<br />
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl<br />
for $major_minor (@ARGV) {<br />
$major_minor =~ m/^(\d+):(\d+)$/ or die;<br />
push(@tgt_rdevs, ($1<<8)|$2);<br />
}<br />
# Sort by reverse length of mount point, to unmount sub-directories first<br />
open MOUNTS,"</proc/mounts" or die "$!";<br />
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;<br />
close MOUNTS;<br />
foreach $m (@mounts) {<br />
($dev,$dir)=@$m;<br />
next unless -b $dev; $rdev=(stat($dev))[6];<br />
next unless grep($_==$rdev, @tgt_rdevs);<br />
system("umount","-v","$dir")==0 or $bad=1;<br />
}<br />
exit 1 if $bad;<br />
EOPERL<br />
}<br />
<br />
# Get the UltraBay's /dev/foo block device node<br />
ultrabay_dev_node() {<br />
UDEV_PATH="`readlink -e "$ULTRABAY_SYSDIR/block:"*`" || return 1<br />
UDEV_NAME="`udevinfo -q name -p $UDEV_PATH`" || return 1<br />
echo /dev/$UDEV_NAME<br />
}<br />
<br />
if [ -d $ULTRABAY_SYSDIR ]; then<br />
sync<br />
# Unmount filesystems backed by this device<br />
unmount_rdev `cat $ULTRABAY_SYSDIR/block\:*/dev \<br />
$ULTRABAY_SYSDIR/block\:*/*/dev` \<br />
|| {<br />
echo 10 > /proc/acpi/ibm/beep; # error tone<br />
exit 1;<br />
}<br />
sync<br />
# Nicely power off the device<br />
DEVNODE=`ultrabay_dev_node` && hdparm -Y $DEVNODE<br />
# Let HAL+KDE notice the unmount and let the disk spin down<br />
sleep 0.5<br />
# Unregister this SCSI device:<br />
sync<br />
echo 1 > $ULTRABAY_SYSDIR/delete<br />
fi<br />
sync<br />
# We really need a 3 sec pause here otherwise the system will freeze..<br />
sleep 3<br />
# Turn off power to the UltraBay:<br />
if [ -d /sys/devices/platform/bay.0 ]; then<br />
echo 1 > /sys/devices/platform/bay.0/eject<br />
elif [ -e /proc/acpi/ibm/bay ]; then<br />
echo eject > /proc/acpi/ibm/bay<br />
fi<br />
# Tell the user we're OK<br />
echo 12 > /proc/acpi/ibm/beep<br />
</pre><br />
<br />
<br />
Use the modified version below if the above doesn't work for you (for kernels 2.6.25+ due to "ULTRABAY_SYSDIR/block\:*/dev" path change). It was tested on a Thinkpad X41 with Fedora 9 and kernel 2.6.25.11:<br />
<br />
<pre><br />
#!/bin/bash<br />
ULTRABAY_SYSDIR='/sys/class/scsi_device/1:0:0:0/device'<br />
shopt -s nullglob<br />
<br />
# Umount the filesystem(s) backed by the given major:minor device(s)<br />
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl<br />
for $major_minor (@ARGV) {<br />
$major_minor =~ m/^(\d+):(\d+)$/ or die;<br />
push(@tgt_rdevs, ($1<<8)|$2);<br />
}<br />
# Sort by reverse length of mount point, to unmount sub-directories first<br />
open MOUNTS,"</proc/mounts" or die "$!";<br />
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;<br />
close MOUNTS;<br />
foreach $m (@mounts) {<br />
($dev,$dir)=@$m;<br />
next unless -b $dev; $rdev=(stat($dev))[6];<br />
next unless grep($_==$rdev, @tgt_rdevs);<br />
system("umount","-v","$dir")==0 or $bad=1;<br />
}<br />
exit 1 if $bad;<br />
EOPERL<br />
}<br />
<br />
# Get the UltraBay's /dev/foo block device node<br />
ultrabay_dev_node() {<br />
UDEV_PATH="`readlink -e "$ULTRABAY_SYSDIR/block/"*`" || return 1<br />
UDEV_NAME="`udevinfo -q name -p $UDEV_PATH`" || return 1<br />
echo /dev/$UDEV_NAME<br />
}<br />
<br />
if [ -d $ULTRABAY_SYSDIR ]; then<br />
sync<br />
# Unmount filesystems backed by this device<br />
unmount_rdev `cat $ULTRABAY_SYSDIR/block/*/dev \<br />
$ULTRABAY_SYSDIR/block/*/*/dev` \<br />
|| {<br />
echo 10 > /proc/acpi/ibm/beep; # error tone<br />
exit 1;<br />
}<br />
sync<br />
# Nicely power off the device<br />
DEVNODE=`ultrabay_dev_node` && hdparm -Y $DEVNODE<br />
# Let HAL+KDE notice the unmount and let the disk spin down<br />
sleep 0.5<br />
# Unregister this SCSI device:<br />
sync<br />
echo 1 > $ULTRABAY_SYSDIR/delete<br />
fi<br />
<br />
# We really need a 3 sec pause here otherwise the system will freeze..<br />
sleep 3<br />
<br />
# Turn off power to the UltraBay:<br />
dock=$( /bin/grep ata_bay /sys/devices/platform/dock.?/type )<br />
dock=${dock%%/type:ata_bay} # needed for 2.6.27 and later<br />
if [ -n "$dock" -a -d "$dock" ]; then<br />
echo 1 > $dock/undock<br />
elif [ -d /sys/devices/platform/bay.0 ]; then<br />
echo 1 > /sys/devices/platform/bay.0/eject<br />
elif [ -e /proc/acpi/ibm/bay ]; then<br />
echo eject > /proc/acpi/ibm/bay<br />
fi<br />
# Tell the user we're OK<br />
echo 12 > /proc/acpi/ibm/beep<br />
</pre><br />
<br />
<br />
Create {{path|/etc/acpi/events/ultrabay-insert}}:<br />
<pre><br />
event=ibm/bay MSTR 00000001 00000000<br />
action=/usr/local/sbin/ultrabay_insert<br />
</pre><br />
<br />
Create {{path|/etc/acpi/events/ultrabay-eject}}:<br />
<pre><br />
event=ibm/bay MSTR 00000003 00000000<br />
action=/usr/local/sbin/ultrabay_eject<br />
</pre><br />
<br />
Restart <tt>acpid</tt>.<br />
<br />
If the <tt>ata_piix</tt> driver is built in the kernel, it will catch bay events and you will see the<br />
following message in your system log:<br />
<pre><br />
thinkpad_acpi: another device driver is already handling bay events<br />
thinkpad_acpi: disabling subdriver bay<br />
</pre><br />
You should load <tt>thinkpad_acpi</tt> before <tt>ata_piix</tt> if you want it to handle bay events.<br />
<br />
===Using the generic bay driver and udev===<br />
<br />
Starting from kernel 2.6.23-rc3, it's possible to use the generic <tt>bay</tt> driver in combination with udev to hotswap. Please check if CONFIG_ACPI_BAY is enabled (module or built-in) in your kernel configuration.<br />
<br />
Create {{path|/etc/udev/rules.d/ibm-ultrabay.rules}}:<br />
ENV{BAY_EVENT}=="3", KERNEL=="bay.0", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_eject"<br />
ENV{BAY_EVENT}=="1", KERNEL=="bay.0", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_insert"<br />
<br />
Starting with kernel 2.6.28, the <tt>bay</tt> driver was removed from the mainline kernel. The <tt>dock</tt> driver replaced it completely. Make sure CONFIG_ACPI_DOCK is enabled in the kernel, and use the following udev rules:<br />
<br />
ENV{EVENT}=="undock", KERNEL=="dock.2", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_eject"<br />
ENV{EVENT}=="dock", KERNEL=="dock.2", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_insert"<br />
<br />
However, the ultra_eject script needs to be changed, otherwise udev goes into an infinite event loop. It will send undock events every few seconds forever. That means as soon as the ultrabay is plugged in again, it will be immediately ejected. For kernels 2.6.28 and higher, the bay cannot be powered off using this method, so change the end of the script to read:<br />
# Turn off power to the UltraBay:<br />
if [ -d /sys/devices/platform/bay.0 ]; then<br />
echo 1 > /sys/devices/platform/bay.0/eject<br />
elif [ -e /proc/acpi/ibm/bay ]; then<br />
echo eject > /proc/acpi/ibm/bay<br />
fi<br />
# Tell the user we're OK<br />
echo 12 > /proc/acpi/ibm/beep<br />
<br />
Alternatively, instead of modifying the script, use the libata-acpi method below.<br />
This was tested on a T61p running Gentoo with tuxonice 2.6.28-r8 without any issues.<br />
<br />
===Using libata-acpi and udev===<br />
<br />
Starting from kernel 2.6.26-rc5, it's possible to use <tt>libata-acpi</tt> in combination with udev to hotswap. Please check if CONFIG_ATA_ACPI is enabled in your kernel configuration.<br />
<br />
For 2.6.25, you need two patches which can be easily backported ([http://article.gmane.org/gmane.linux.acpi.devel/31159],[http://article.gmane.org/gmane.linux.acpi.devel/31369]).<br />
<br />
Create {{path|/etc/udev/rules.d/ibm-ultrabay.rules}}:<br />
<pre><br />
ENV{BAY_EVENT}=="3", ACTION=="change", SUBSYSTEM=="scsi", RUN+="/usr/local/sbin/ultrabay_eject"<br />
</pre><br />
<br />
===Model-specific notes===<br />
See the table above for a list of ata_piix supported laptops and the bus ID to use.<br />
<br />
===HAL support===<br />
<br />
{{NOTE| Starting from HAL 0.5.11, you need to replace "storage.physical_device" with "info.parent".}}<br />
<br />
Many programs, KDE included, rely on [[HAL]] to get notifications and information about device hotplugging. You need to tell HAL that devices connected the UltraBay port are hotpluggable. To do so, create the file {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as follows:<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --> <br />
<br />
<deviceinfo version="0.2"><br />
<device><br />
<br />
<!-- UltraBay Devices --><br />
<match key="storage.bus" string="scsi"><br />
<match key="storage.physical_device" string="/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_0_scsi_device_lun0"><br />
<merge key="storage.hotpluggable" type="bool">true</merge><br />
</match><br />
</match><br />
<br />
</device><br />
</deviceinfo><br />
</pre><br />
<br />
The string "8086_2653" may need to be changed to match your ThinkPad model; see below.<br />
<br />
====Details====<br />
<br />
By default, HAL doesn't know that UltraBay devices are hotpluggable:<br />
<br />
# PHYSDEV=/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_0_scsi_device_lun0<br />
# UDI=`hal-find-by-property --key storage.physical_device --string $PHYSDEV` || echo Failed<br />
# hal-get-property --udi $UDI --key block.device<br />
/dev/sdb<br />
# hal-get-property --udi $UDI --key storage.hotpluggable<br />
false<br />
<br />
After creating {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as above and re-plugging the device, it will get marked correctly:<br />
<br />
# PHYSDEV=/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_0_scsi_device_lun0<br />
# UDI=`hal-find-by-property --key storage.physical_device --string $PHYSDEV` || echo Failed<br />
# hal-get-property --udi $UDI --key block.device<br />
/dev/sdb<br />
# hal-get-property --udi $UDI --key storage.hotpluggable<br />
true<br />
<br />
The string "8086_2653" gives the PCI ID of the [[Intel 82801FBM]] southbridge. If your model has a different southbridge, or the UltraBay is attached to a different port, then you can find the appropriate <tt>storage.physical_device</tt> value by finding out the block device of the currently running UltraBay device (<tt>/dev/sdb</tt> in the following example) and then running:<br />
<br />
# DEVICE=/dev/sdb<br />
# UDI=`hal-find-by-property --key block.device --string $DEVICE` || echo Failed<br />
# hal-get-property --udi $UDI --key storage.physical_device<br />
/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_0_scsi_device_lun0<br />
<br />
If you have a different <tt>storage.physical_device</tt> value, please report your findings.<br />
<br />
{| border=1<br />
|+ Known South Bridge PCI IDs<br />
! ID !! ThinkPad model !! South Bridge chip<br />
|-<br />
| 8086_248a || 2366-83U (T30), 2647-MG3 (T23)|| Intel 82801CAM IDE U100 (rev 2)<br />
|-<br />
| 8086_2653 || 2525FAG (X41), ? (T43) || Intel 82801FBM (ICH6-M)<br />
|-<br />
| 8086_24ca || 237358U (T40), 2373KXU (T42p) || Intel 82801DBM (ICH4-M)<br />
|-<br />
| 8086_27c4 || X60 || Intel 82801GBM (ICH7 Family)<br />
|-<br />
| 8086_27df || Z61p, T60, T60p || Intel 82801GBM/GHM (ICH7 Family)<br />
|-<br />
| 8086_2850 || T61, T61p || Intel 82801H (ICH8 Family)<br />
|}<br />
<br />
==When using the <tt>ide-disk</tt> driver==<br />
The following applies if you use the <tt>ide-disk</tt> driver for the UltraBay device.<BR><br />
<b>Note that essentially, you shouldn't be using this driver, and use ata_piix instead unless you're running an older kernel where ata_piix won't work for you</b><br />
<br />
Hotswapping is supposed to be supported as well, using either hdparm/[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] or [[lt_hotswap]] to (un)register IDE devices. The latter is the recommended method with kernels from 2.6, since it will leave DMA working. However, for recent models (R52, T43, X41, Z60 and later) no method is known to work while maintaining DMA support; see [[Problems with SATA and Linux]].<br />
<br />
Only IDE devices (HDD's, optical drives, zip drives) require special treatment - batteries, floppies and other devices can just be pulled from the bay, provided they are not mounted or in use at the time. However, you should still power them down first using the [[ibm-acpi]] eject function.<br />
<br />
The [[ibm-acpi]] kernel module has an eject function ({{cmdroot|echo eject > /proc/acpi/ibm/bay}}). This only manages the ACPI calls to power down the device and the bay. It does not actually unregister the device from the IDE driver. {{cmdroot|cat /proc/acpi/ibm/bay}} shows "unoccupied" unless an IDE device is present, but the eject function still works and should still be used.<br />
<br />
To unregister the device, you can either use the [http://packages.debian.org/unstable/admin/hotswap Debian hotswap] package, or [[lt_hotswap]]. Note that lt_hotswap doesn't seem to even build on recent (at 2.6.22 or newer, although it probably broke before 2.6.22) and on newer kernels, you should not build/load the old IDE PIIX (CONFIG_BLK_DEV_PIIX) and use the natively hotswapping ata_piix (CONFIG_ATA_PIIX) as explained on the top of this page.<br />
<br />
[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] also allows the drive to be swapped as a normal user by default, which is useful. You should use <tt>hotswap</tt> to unregister the device and then {{cmdroot|echo eject > /proc/acpi/ibm/bay}}. However, if you use this method on a 2.6 kernel, you will lose DMA support for the reinserted drive. This is due to kernel issues. This method was reported to work on a ThinkPad {{T23}} (kernels 2.6.8.1, 2.6.14.2 and 2.6.15-arch) and {{T42}} (kernel 2.6.13), but fails on a ThinkPad {{T43}} (kernel 2.6.14.3).<br />
<br />
[[lt_hotswap]] is now the recommended method to un- and reregister the IDE device. It installs as a kernel module and has support for automatically unregistering (if loaded with the auto_eject=1 option) the device when the eject event is generated by [[ibm-acpi]]. It will leave DMA support intact. It has supported to work on a ThinkPad {{T22}} and {{T40}} and should work with many other models (but not recent models which require the <tt>ata_piix</tt> driver for disk DMA support). With the [[lt_hotswap]] kernel module loaded, run: {{cmdroot|modprobe -r ide_cd && modprobe -r cdrom && echo "MSTR eject" > /proc/acpi/lths}}<br />
<br />
===HAL support===<br />
<br />
HAL support also can also be configured To do so, create the file {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as follows:<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --><br />
<br />
<deviceinfo version="0.2"><br />
<device><br />
<br />
<!-- UltraBay Devices --><br />
<match key="storage.bus" string="ide"><br />
<match key="storage.physical_device" string="/org/freedesktop/Hal/devices/pci_8086_24ca_ide_1_0"><br />
<merge key="storage.hotpluggable" type="bool">true</merge><br />
</match><br />
</match><br />
<br />
</device><br />
</deviceinfo><br />
</pre><br />
For more details see HAL section for ata driver.<br />
<br />
==Other comments==<br />
<br />
If you are hot-swapping a hard disk on a disk tray, make sure the disk does not have a password set, otherwise it will not be recognized on reinsertion.<br />
<br />
[[Category:Scripts]]<br />
[[Category:HOWTOs]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installing_Fedora_10_on_a_ThinkPad_T61p&diff=43136Installing Fedora 10 on a ThinkPad T61p2009-05-06T16:41:05Z<p>Pfps: point to another solution variant</p>
<hr />
<div>== Introduction ==<br />
<br />
This document outlines configuring Fedora 10 on your Thinkpad T61p. Most items will work out of the box and a base install will provide you with an almost completely working system. Everything not mentioned on this wikipage is assumed to be working out of the box. Due to the modular nature of the T61 Series there are many different configurations, please read carefully and only make the changes specific to your system.<br />
<br />
Feel free to update this Wiki with your information however please ask questions on the Talk page.<br />
<br />
Please look here for further informations as well:<br />
* [[Installing_Fedora_10_Generic_Notes | Installing Fedora 10 Generic Notes]]<br />
<br />
== Installation Notes ==<br />
The Graphical installer works just fine with the NVIDIA Cards. However, on WUXGA Models the Font within the installer can be tiny because of the wrong calculation of the screen's DPI value.<br />
You can use either the i386 or the x86_64 version on your ThinkPad. If you don't have more than 3GB of RAM you'll probably be better off installing the i386 version unless you have a good reason to use 64-bit software. But even if you do have more than 3GB of RAM you might want to install the i386 version for better software compatibility. The installer will then automatically choose the PAE kernel which enables the system to use the full amount of RAM installed.<br />
<br />
Please note, that the SATA Mode must be set to '''AHCI'''. By default it is set to '''Compatibility''' within the BIOS.<br />
<br />
== Display/Video ==<br />
Currently you have three options what graphics drivers are concerned:<br />
<ol><br />
<li>the 2D nv driver shipped with Fedora</li><br />
<li>the (currently only) 2D nouveau driver also shipped with Fedora</li><br />
<li>the proprietary 2D/3D nVidia drivers (preferably installed from [http://rpmfusion.org/ RPMFusion])</li><br />
</ol><br />
<br />
One big pro of the open-source drivers (nv/nouveau) is the support for XRandR 1.2. That allows you to hotplug screens (e.g. a Projector) and configure them without restarting the X Server. Using those drivers will also automatically enable the Fn-F7 button's function of switching between screens.<br />
The official NVIDIA drivers do '''not''' have this feature at the moment (so the Fn-F7 button is currently without function if you use them). So if you do presentations a lot you might want to use the open-source drivers.<br />
<br />
=== Installing the official NVIDIA drivers from RPMFusion ===<br />
Now that's easy:<br />
<br />
yum install xorg-x11-drv-nvidia akmod-nvidia<br />
<br />
This will install the X11 driver as well as the kernel module. Note that this is a special kind of kernel module; a so called akmod. It automatically tries to rebuild the kernel module if it isn't found. You will never have to wait for the RPMFusion maintainers to recompile the module when a new kernel is released again.<br />
<br />
== UltraBay Hotswap ==<br />
{{Todo|Maybe create a little RPM Package for easy install}}<br />
If you want to hotswap UltraBay devices there are some changes you need to make for it to work.<br />
First of all create <tt>/etc/udev/rules.d/60-ibm-ultrabay.rules</tt> and add the following:<br />
<br />
ENV{BAY_EVENT}=="3", KERNEL=="bay.0", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/libexec/ultrabay_eject"<br />
ENV{BAY_EVENT}=="1", KERNEL=="bay.0", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/libexec/ultrabay_insert"<br />
<br />
Then grab the hotswap scripts from [[How to hotswap UltraBay devices]] and put them in <tt>/usr/libexec/</tt>.<br />
{{NOTE|Change the path to <tt>/sys/class/scsi_host/host1</tt> and <tt>/sys/class/scsi_device/1:0:0:0</tt> according to your machine.<br />
For the T61p this usually is <tt>/sys/class/scsi_host/host3</tt> and <tt>/sys/class/scsi_device/3:0:0:0</tt>}}<br />
That's it. Now you should be able to hotswap your UltraBay devices without hanging your machine.<br />
<br />
See [[Installing Fedora 11 on a ThinkPad T60]] for a slightly different way of doing this that might be a bit easier.<br />
<br />
== Suspend ==<br />
At the moment suspend and resume are erroneous on the T61p. This is an issue currently being worked on.<br />
<br />
[[Category:T61p]]<br />
[[Category:Fedora]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T60p&diff=43135Installation instructions for the ThinkPad T60p2009-05-06T16:34:23Z<p>Pfps: fix tyop</p>
<hr />
<div>[[Category:T60p]]<br />
Specific installation notes for the ThinkPad {{T60p|T60p}}.<br />
<br />
'''Note:''' you may want to look at [[Installation_instructions_for_the_ThinkPad_T60|Installation instructions for the ThinkPad T60]] as the two models have lots in common, especially if your distro/version doesn't appear here.<br />
<br />
==Distribution-specific instructions==<br />
<br />
=== Ubuntu / Kubuntu ===<br />
<br />
*[[Installing_Ubuntu_6.06_Kubuntu_6.06_Gentoo_2006.0_on_a_ThinkPad_T60p|Ubuntu and Kubuntu 6.06 Dapper Drake]]<br />
*[[Installing_Ubuntu_7.04 Feisty Fawn_on_a_ThinkPad_T60p | Ubuntu_7.04 Feisty Fawn]]<br />
*[[Installing_Ubunut_8.10 Intrepid Ibex_on_a_Thinkpad_T60p | Ubuntu_8.10 Intrepid Ibex]]<br />
<br />
My own notes and observations: -<br />
<br />
Happy New Year, and it's looking good so far .... suspend and resume ARE working on the T60p, really :-) <br />
http://www.davehay.f2s.com/2009/01/happy-new-year-and-its-looking-good-so.html<br />
<br><br />
Solved - ATI Catalyst Control Centre not saving configuration<br />
<br><br />
http://www.davidmhay.co.uk/2008/12/solved-ati-catalyst-control-centre-not.html<br />
<br><br />
Ubuntu 8.10 ( Intrepid Ibex ) and Suspend/Resume on the Thinkpad T60p ( 2007-AE7 )<br />
<br><br />
http://www.davidmhay.co.uk/2008/12/ubuntu-810-intrepid-ibex-and.html<br />
<br><br />
Installing and Using Ubuntu 8.10 on my Thinkpad T60p<br />
<br><br />
http://www.davidmhay.co.uk/2008/11/installing-and-using-ubuntu-810-on-my.html<br />
<br><br />
More from the land of the Ibex<br />
<br><br />
http://www.davidmhay.co.uk/2008/10/more-from-land-of-ibex.html<br />
<br><br />
Intrepidly going where no one ( apart from an ibex ) has gone before ...<br />
<br><br />
http://www.davidmhay.co.uk/2008/10/intrepidly-going-where-no-one-apart.html<br />
<br />
=== Red Hat Enterprise Linux / CentOS ===<br />
<br />
*[[Installing_Red_Hat_Enterprise_Linux_4_on_a_ThinkPad_T60p | Red Hat Enterprise Linux 4]]<br />
<br />
=== Fedora ===<br />
<br />
*See also [[Installation instructions for the ThinkPad T60#Fedora|installing Fedora on the ThinkPad T60]]<br />
*{{Install|Fedora| 11| T60}} has some T60p-specific stuff<br />
*[[Installing_Fedora_7_on_a_ThinkPad_T60p | Fedora 7]]<br />
*[[Installing_Fedora_Core_6_on_a_ThinkPad_T60p | Fedora Core 6]]<br />
<br />
=== Gentoo ===<br />
<br />
*[[Installing_Ubuntu_6.06_Kubuntu_6.06_Gentoo_2006.0_on_a_ThinkPad_T60p|Gentoo 2006.0]]<br />
<br />
<br />
=== Suse Linux ===<br />
<br />
Works out of the box, SLES SP1</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T60p&diff=43134Installation instructions for the ThinkPad T60p2009-05-06T16:33:57Z<p>Pfps: put FC6 in Fedora section</p>
<hr />
<div>[[Category:T60p]]<br />
Specific installation notes for the ThinkPad {{T60p|T60p}}.<br />
<br />
'''Note:''' you may want to look at [[Installation_instructions_for_the_ThinkPad_T60|Installation instructions for the ThinkPad T60]] as the two models have lots in common, especially if your distro/version doesn't appear here.<br />
<br />
==Distribution-specific instructions==<br />
<br />
=== Ubuntu / Kubuntu ===<br />
<br />
*[[Installing_Ubuntu_6.06_Kubuntu_6.06_Gentoo_2006.0_on_a_ThinkPad_T60p|Ubuntu and Kubuntu 6.06 Dapper Drake]]<br />
*[[Installing_Ubuntu_7.04 Feisty Fawn_on_a_ThinkPad_T60p | Ubuntu_7.04 Feisty Fawn]]<br />
*[[Installing_Ubunut_8.10 Intrepid Ibex_on_a_Thinkpad_T60p | Ubuntu_8.10 Intrepid Ibex]]<br />
<br />
My own notes and observations: -<br />
<br />
Happy New Year, and it's looking good so far .... suspend and resume ARE working on the T60p, really :-) <br />
http://www.davehay.f2s.com/2009/01/happy-new-year-and-its-looking-good-so.html<br />
<br><br />
Solved - ATI Catalyst Control Centre not saving configuration<br />
<br><br />
http://www.davidmhay.co.uk/2008/12/solved-ati-catalyst-control-centre-not.html<br />
<br><br />
Ubuntu 8.10 ( Intrepid Ibex ) and Suspend/Resume on the Thinkpad T60p ( 2007-AE7 )<br />
<br><br />
http://www.davidmhay.co.uk/2008/12/ubuntu-810-intrepid-ibex-and.html<br />
<br><br />
Installing and Using Ubuntu 8.10 on my Thinkpad T60p<br />
<br><br />
http://www.davidmhay.co.uk/2008/11/installing-and-using-ubuntu-810-on-my.html<br />
<br><br />
More from the land of the Ibex<br />
<br><br />
http://www.davidmhay.co.uk/2008/10/more-from-land-of-ibex.html<br />
<br><br />
Intrepidly going where no one ( apart from an ibex ) has gone before ...<br />
<br><br />
http://www.davidmhay.co.uk/2008/10/intrepidly-going-where-no-one-apart.html<br />
<br />
=== Red Hat Enterprise Linux / CentOS ===<br />
<br />
*[[Installing_Red_Hat_Enterprise_Linux_4_on_a_ThinkPad_T60p | Red Hat Enterprise Linux 4]]<br />
<br />
=== Fedora ===<br />
<br />
*See also [[Installation instructions for the ThinkPad T60#Fedora|installing Fedora on the ThinkPad T60]]<br />
*{{Install|Fedora| 11| T60}}, has some T60p-specific stuff<br />
*[[Installing_Fedora_7_on_a_ThinkPad_T60p | Fedora 7]]<br />
*[[Installing_Fedora_Core_6_on_a_ThinkPad_T60p | Fedora Core 6]]<br />
<br />
=== Gentoo ===<br />
<br />
*[[Installing_Ubuntu_6.06_Kubuntu_6.06_Gentoo_2006.0_on_a_ThinkPad_T60p|Gentoo 2006.0]]<br />
<br />
<br />
=== Suse Linux ===<br />
<br />
Works out of the box, SLES SP1</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T60p&diff=43133Installation instructions for the ThinkPad T60p2009-05-06T16:32:29Z<p>Pfps: F11 and point to T60</p>
<hr />
<div>[[Category:T60p]]<br />
Specific installation notes for the ThinkPad {{T60p|T60p}}.<br />
<br />
'''Note:''' you may want to look at [[Installation_instructions_for_the_ThinkPad_T60|Installation instructions for the ThinkPad T60]] as the two models have lots in common, especially if your distro/version doesn't appear here.<br />
<br />
==Distribution-specific instructions==<br />
<br />
=== Ubuntu / Kubuntu ===<br />
<br />
*[[Installing_Ubuntu_6.06_Kubuntu_6.06_Gentoo_2006.0_on_a_ThinkPad_T60p|Ubuntu and Kubuntu 6.06 Dapper Drake]]<br />
*[[Installing_Ubuntu_7.04 Feisty Fawn_on_a_ThinkPad_T60p | Ubuntu_7.04 Feisty Fawn]]<br />
*[[Installing_Ubunut_8.10 Intrepid Ibex_on_a_Thinkpad_T60p | Ubuntu_8.10 Intrepid Ibex]]<br />
<br />
My own notes and observations: -<br />
<br />
Happy New Year, and it's looking good so far .... suspend and resume ARE working on the T60p, really :-) <br />
http://www.davehay.f2s.com/2009/01/happy-new-year-and-its-looking-good-so.html<br />
<br><br />
Solved - ATI Catalyst Control Centre not saving configuration<br />
<br><br />
http://www.davidmhay.co.uk/2008/12/solved-ati-catalyst-control-centre-not.html<br />
<br><br />
Ubuntu 8.10 ( Intrepid Ibex ) and Suspend/Resume on the Thinkpad T60p ( 2007-AE7 )<br />
<br><br />
http://www.davidmhay.co.uk/2008/12/ubuntu-810-intrepid-ibex-and.html<br />
<br><br />
Installing and Using Ubuntu 8.10 on my Thinkpad T60p<br />
<br><br />
http://www.davidmhay.co.uk/2008/11/installing-and-using-ubuntu-810-on-my.html<br />
<br><br />
More from the land of the Ibex<br />
<br><br />
http://www.davidmhay.co.uk/2008/10/more-from-land-of-ibex.html<br />
<br><br />
Intrepidly going where no one ( apart from an ibex ) has gone before ...<br />
<br><br />
http://www.davidmhay.co.uk/2008/10/intrepidly-going-where-no-one-apart.html<br />
<br />
=== Red Hat Enterprise Linux / CentOS ===<br />
<br />
*[[Installing_Red_Hat_Enterprise_Linux_4_on_a_ThinkPad_T60p | Red Hat Enterprise Linux 4]]<br />
<br />
=== Red Hat Fedora ===<br />
*[[Installing_Fedora_Core_6_on_a_ThinkPad_T60p | Fedora Core 6]]<br />
<br />
=== Fedora ===<br />
<br />
*See also [[Installation instructions for the ThinkPad T60#Fedora|installing Fedora on the ThinkPad T60]]<br />
*{{Install|Fedora| 11| T60}}, has some T60p-specific stuff<br />
*[[Installing_Fedora_7_on_a_ThinkPad_T60p | Fedora 7]]<br />
<br />
=== Gentoo ===<br />
<br />
*[[Installing_Ubuntu_6.06_Kubuntu_6.06_Gentoo_2006.0_on_a_ThinkPad_T60p|Gentoo 2006.0]]<br />
<br />
<br />
=== Suse Linux ===<br />
<br />
Works out of the box, SLES SP1</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T60&diff=43131Installation instructions for the ThinkPad T602009-05-06T16:27:07Z<p>Pfps: add F11</p>
<hr />
<div>Specific installation notes for the ThinkPad {{T60}}.<br />
<br />
==Distribution-specific instructions==<br />
<br />
=== Ubuntu ===<br />
*{{Install|Ubuntu| 8.04 (Hardy Heron)| T60}}<br />
*{{Install|Ubuntu| 7.10 (Gutsy Gibbon)| T60}}<br />
*{{Install|Ubuntu| 7.04 (Feisty Fawn)| T60}}<br />
*{{Install|Ubuntu| 6.10 (Edgy Eft)| T60}}<br />
*{{Install|Ubuntu| 6.06 Flight 5|T60}}<br />
<br />
=== Debian ===<br />
*{{Install|Debian| Lenny|T60}}<br />
*{{Install|Debian| Etch|T60}}<br />
<br />
=== Fedora ===<br />
*{{Install|Fedora| 11| T60}}<br />
*{{Install|Fedora| 8| T60}}<br />
*{{Install|Fedora| 7| T60}}<br />
*{{Install|Fedora| Core 6| T60}}<br />
*{{Install|Fedora| Core 5| T60}}<br />
<br />
=== openSUSE / SUSE LINUX ===<br />
<br />
*{{Install|Suse| 10.1| T60}}<br />
*[[Installing openSUSE 10.2 on an IBM ThinkPad T60]]<br />
<br />
=== Gentoo ===<br />
<br />
* For Gentoo, there exists [[Installation_instructions_for_the_ThinkPad_T60p|installation instructions for T60p]], the sister model.<br />
<br />
=== CentOS ===<br />
<br />
*[[Installation CentOS 5 on a Thinkpad T60]]<br />
<br />
=== ArchLinux ===<br />
*{{Install|Arch| Core 2008| T60}}<br />
<br />
== Compatibility ==<br />
* [http://www.emperorlinux.com/mfgr/lenovo/toucan/?tab=details&id=358 Thinkpad T60] page on [http://www.emperorlinux.com emperorlinux.com] (compatibility review and custom kernel)</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installing_Fedora_11_on_a_ThinkPad_T60&diff=43130Installing Fedora 11 on a ThinkPad T602009-05-06T15:31:42Z<p>Pfps: add T60p, newer stuff, ultrabay eject</p>
<hr />
<div>{{NOTE|This is based on the x86-64 pre-release version of Fedora 11, but should give a good indication of what to expect of the final release}}<br />
<br />
{{NOTE|ThinkPad T60p is reported here as well}}<br />
<br />
== Success Chart ==<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
|colspan=2| '''Item''' || '''Working''' || '''Notes'''<br />
|-<br />
|rowspan=3|Installation <br />
| Local CD/DVD install || {{Cyes}} ||<br />
|-<br />
| Network Installation || {{Cyes}} ||<br />
|-<br />
| USB Installation || {{Cyes}} ||<br />
|- <br />
|rowspan=3|Display - Intel<br />
| Laptop Screen || {{Cyes}} || only 1 video mode available<br />
|-<br />
| VGA || {{Cyes}} || with hotplug only ?<br />
|-<br />
| DVI || {{Cyes}} || with hotplug only ?<br />
|-<br />
|rowspan=3|Display - ATI<br />
| Laptop Screen || {{Cyes}} || everything works, including rotation<br />
|-<br />
| VGA || {{Cyes}} || everything works, including rotation and mirroring<br />
|-<br />
| DVI || {{Cunk}} (should work) || no reason this wouldn't work<br />
|-<br />
|rowspan=2|Power Management<br />
| Software Suspend (hibernate) || {{Cyes}} || <br />
|-<br />
| Suspend to Memory (ACPI sleep) || {{Cyes}} || <br />
|-<br />
|colspan=2| Audio || {{Cyes}} ||<br />
|-<br />
|rowspan=5| Wireless || WiFi - Atheros|| {{Cyes}} || occasional disconnect/reconnect<br />
|-<br />
| WiFi - Intel|| {{Cyes}} || no problems at all<br />
|-<br />
| Bluetooth || {{Cyes}} ||<br />
|-<br />
| WWAN - Verizon || {{Cunk}} ||<br />
|-<br />
| WWAN - Cingular || {{Cunk}} ||<br />
|-<br />
| Extra Buttons || Keyboard Section || {{Cpart}} || see ThinkPad keyboard section below<br />
|-<br />
| rowspan=8|Ports<br />
| Ethernet || {{Cyes}} ||<br />
|-<br />
| Modem || {{Cno}} || Requires closed-source driver<br />
|-<br />
| Serial || {{Cyes}} || Requires port-replicator or dock<br />
|-<br />
| IrDA || {{Cno}} || Device is detected, but no device files are created<br />
|-<br />
| PS/2 Keyboard/Mouse || {{Cunk}} (should work)|| Requires port-replicator or dock<br />
|-<br />
| Parallel || {{Cunk}} (should work)|| Requires port-replicator or dock<br />
|-<br />
| USB || {{Cyes}} ||<br />
|-<br />
| PCMCIA/Cardbus || {{Cyes}} || even ATA adaptors (for CF cards, etc) now work!<br />
|-<br />
| colspan=2| Harddisk Active Protection || {{Cno}} || <br />
|-<br />
| colspan=2| Ultrabay device hotswap || {{Cpart}} || see below, use with<br />
caution out of the box<br />
|-<br />
| colspan=2| Fingerprint reader || {{Cunk}} (should work)|| F11 has standard support for Fingerprint readers<br />
|-<br />
| colspan=2| TPM (security subsystem) || {{Cunk}} || Not brave enough to mess around with it<br />
|-<br />
|}<br />
<br />
= Tested and Verified on Fedora 11 =<br />
<br />
Information in this section has been tested and verified using Fedora 11, including the pre-release (post-beta) version. The development version of Fedora 11 (rawhide) is quite stable and even suitable for day-to-day use, if you are a bit brave. You will be automatically switched over to the release version of Fedora 11 if you keep everything up to date.<br />
<br />
== Installation ==<br />
<br />
Installation is straight forward; you can follow the generic Fedora install instructions.<br />
<br />
== Configuration ==<br />
<br />
=== X Server (Intel)===<br />
Basic X server functionality should work out of the box on the ThinkPad LCD (LVDS), as long as no external displays are attached at boot. <br />
<br />
Fedora 11 uses KMS (Kernel Mode Setting) by default, which for now has some up and down sides for external displays.<br />
The down sides are that external displays attached during boot might not function properly (mostly they may have non-optimal resolution), but they do when hot plugged afterwards. Another down side is that currently mirror mode is very limited as the ThinkPad LCD (LVDS) is limited to one single display mode, so only if the external display supports this same mode can you activate mirror mode. On the other hand with KMS enabled the maximum virtual display size is now 4096x4096 (2048x2048 without KMS) meaning you can have an extended desktop.<br />
<br />
These issues have been reported to Red Hat bugzilla.<br />
<br />
On a T60p, displays work well, with multiple mirrored and non-mirrored displays and even with one of the displays being rotated! This may also work on a base T60, as there has been a lot of effort put into getting this to work right.<br />
<br />
One thing that still doesn't work quite right is screensavers and screen blanking. There is something wrong with the timers, which may result in your screen blanking while you are typing. Recovery is a simple as waiting until the screen is completely blank and then type or click to wake up the screen.<br />
<br />
Another thing that doesn't work quite right is screen resolution when booting with multiple screens. If one screen doesn't not have a preferred resolution, a poor resolution may be used for both screens during the booting process. Everything works fine after login, however.<br />
<br />
==== Desktop Effects ====<br />
Compiz (wobbly windows, desktops on a cube) seems to work. Direct display of video may be problematic with Compiz, however.<br />
<br />
=== dpi ===<br />
On the 1400x1050 (and 1600x1200) LCD Fedora comes up with a DPI of 124 (or higher). While this is correct for the physical screen size, it waists a lot of screen real estate.<br />
<br />
To change to the more typical 96 DPI, go to System -> Preferences -> Appearance. Now in Appearance Preferences select the Fonts tab and press the "Details ..." button. Here you can change the dots per inch to 96. Of course, many things will shrink, but that is what you wanted, after all.<br />
<br />
=== Wireless Network ===<br />
<br />
Both the Intel and Atheros wireless should work out of the box.<br />
<br />
Atheros was tested and works, but you may encounter occasional disconnects and reconnects. Intel wireless also works.<br />
<br />
=== ThinkPad keys ===<br />
ThinkPad keys are handled by a mixture of the thinkpad_acpi, acpi button, acpi dock and acpi video drivers.<br />
{{NOTE|Due to Xorg limitations, some keys that cause HAL events work with Xorg (ThinkVantage and Fn-F7) and others do not. This is a known limitation that should be fixed with the next major Xorg (v1.7) release.}}<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
| '''Key''' || '''Function''' || '''Handled by''' ||'''HAL event''' || '''Works''' || '''Notes'''<br />
|-<br />
| Fn-F2 || lock screen || thinkpad_acpi || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-F3 || battery || thinkpad_acpi || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-F4 || suspend || acpi button|| {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-F5 || wireless || thinkpad_acpi || {{Cyes}} || {{Cpart}} || No default action, but can be associated with gnome-keybinding-properties<br />
|-<br />
| Fn-F7 || videomode || thinkpad_acpi || {{Cyes}} || {{Cyes}} || Cycles through only LCD, only external, both (mirrored), and both (non-mirrored)<br />
|-<br />
| Fn-F8 || mouse input select || thinkpad_acpi || {{Cyes}} || {{Cpart}} || No default action, but can be associated with gnome-keybinding-properties<br />
|-<br />
| Fn-F9 || undock || thinkpad_acpi || {{Cyes}} || {{Cpart}} || No default action, but can be associated with gnome-keybinding-properties<br />
|-<br />
| Fn-F12 || hibernate || acpi button|| {{Cyes}} || {{Cpart}} || does the same as Fn-F4 (suspend), not hibernate <br />
|-<br />
| Fn-Home || brightness up || acpi video || {{Cyes}} || {{Cyes}} || includes on-screen display of brightness level<br />
|-<br />
| Fn-End || brightness down || acpi video || {{Cyes}} || {{Cyes}} || includes on-screen display of brightness level<br />
|-<br />
| Fn-PgUp || thinklight || - || {{Cno}} || {{Cyes}} || changing thinkpad_acpi hotkey_mask, causes HAL events. No OSD in any case.<br />
|-<br />
| Fn-Space || zoom || thinkpad_acpi || {{Cyes}} || {{Cno}} ||<br />
|-<br />
| VolumeUp || Volume Up || - || {{Cno}} || {{Cyes}} || changing thinkpad_acpi hotkey_mask, causes HAL events. But OSD is wrong<br />
|-<br />
| VolumeDown || Volume Down || - || {{Cno}} || {{Cyes}} || changing thinkpad_acpi hotkey_mask, causes HAL events. But OSD is wrong<br />
|-<br />
| Mute || Mute || - || {{Cno}} || {{Cyes}} || changing thinkpad_acpi hotkey_mask, causes HAL events and OSD. works as a on/off toggle<br />
|-<br />
| ThinkVantage || Vendor key ||thinkpad_acpi || {{Cyes}} || {{Cpart}} || No default action, but can be associated with gnome-keybinding-properties<br />
|-<br />
| NextTab || Browser Next tab || standard keyboard driver || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| PreviousTab || Browser Previous tab || standard keyboard driver || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-Up || Stop || standard keyboard driver || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-Left || reverse || standard keyboard driver || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-Right || forward || standard keyboard driver || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Fn-Down || play/pause || standard keyboard driver || {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Power || Power button || acpi button|| {{Cyes}} || {{Cyes}} || Need to press button for ~1 second to trigger event <br />
|-<br />
| Lid || Lid button || acpi button|| {{Cyes}} || {{Cyes}} ||<br />
|-<br />
| Dock || Dock eject button || acpi dock || {{Cyes}} || {{Cpart}} || causes unload of USB devices (including internal BlueTooth!!) and switch to battery mode. Does not restore video to ThinkPad only. Causes HAL event, but not a button event.<br />
|-<br />
| Ultrabay || Ultrabay eject switch || ??? || {{Cno}} || {{Cpart}} || causes a udev event, which can be handled as in [How to hotswap Ultrabay devices], with minor changes, but should be handled better<br />
|-<br />
| Radio switch || Radio kill switch || || {{Cyes}} || {{Cyes}} || previous comment on Bluetooth only may be a result of networkmanager keeping information around - however integration with networkmanager and bluetooth applet is not complete<br />
|-<br />
|}<br />
<br />
=== Ultrabay ===<br />
<br />
The Ultrabay has some glitches out of the box with respect to hotswapping. It is possible to lock the machine when pulling out devices, even the CD/DVD device.<br />
<br />
The culprit is that the Ultrabay pre-eject switch is not hooked into anything useful. It does cause udev events, but nothing is listening for them. When a device that has a mounted partition or CD is actually pulled out it is too late to do the right thing. Fedora 11 will usually just complain, sometimes bitterly, but may also lock up for some unknown reason, even if just pulling out a CD/DVD device with a mounted CD.<br />
<br />
Manually unmounting before removal will help. Manual powering down may also be required for correct performance. <br />
<br />
A better solution is to set up a udev rule and script to handle the pre-eject switch event for Ultrabay devices that have mountable things in them as in [How to hotswap Ultrabay devices].<br />
<br />
The revised solution here works well. Pushing the pre-eject switch either does the unmounting and powering off and then emits a low beep, or fails and then emits a triple beep. After success the device can be safely removed or the eject lever can be pushed back and everything will be remounted. After failure pusing the eject lever back in does nothing, permitting continuing as if nothing happened or allowing changes to be made before the next attempt to remove.<br />
<br />
Unfortunately the code below is complex and may be fragile. A better solution would be very useful.<br />
<br />
To set this solution up, first<br />
create the file /etc/udev/rules.d/50-ibm-ultrabay.rules<br />
<br />
<pre><br />
ls -lZ /etc/udev/rules.d/50-ibm-ultrabay.rules<br />
-rw-r--r--. root root system_u:object_r:etc_runtime_t:s0 /etc/udev/rules.d/50-ibm-ultrabay.rules<br />
cat /etc/udev/rules.d/50-ibm-ultrabay.rules<br />
ENV{BAY_EVENT}=="3", ACTION=="change", SUBSYSTEM=="scsi", RUN+="/usr/local/sbin/ultrabay_eject"<br />
</pre><br />
<br />
Then create the executable file /usr/local/sbin/ultrabay_eject<br />
<pre><br />
#!/bin/bash<br />
<br />
ULTRABAY_SYSDIR=/sys$DEVPATH<br />
shopt -s nullglob<br />
logger ultrabay_eject storage device $DEVPATH<br />
<br />
# Umount the filesystem(s) backed by the given major:minor device(s)<br />
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl<br />
for $major_minor (@ARGV) {<br />
$major_minor =~ m/^(\d+):(\d+)$/ or die;<br />
push(@tgt_rdevs, ($1<<8)|$2);<br />
}<br />
# Sort by reverse length of mount point, to unmount sub-directories first<br />
open MOUNTS,"</proc/mounts" or die "$!";<br />
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;<br />
close MOUNTS;<br />
foreach $m (@mounts) {<br />
($dev,$dir)=@$m;<br />
next unless -b $dev; $rdev=(stat($dev))[6];<br />
next unless grep($_==$rdev, @tgt_rdevs);<br />
system("logger","ultrabay_eject","umounting",$dev,$dir);<br />
system("umount","-v","$dir")==0 or $bad=1;<br />
}<br />
exit 1 if $bad;<br />
EOPERL<br />
}<br />
<br />
# Get the UltraBay's /dev/foo block device node<br />
ultrabay_dev_node() {<br />
UDEV_PATH="`readlink -e "$ULTRABAY_SYSDIR/block/"*`" || return 1<br />
UDEV_NAME="`udevinfo -q name -p $UDEV_PATH`" || return 1<br />
echo /dev/$UDEV_NAME<br />
}<br />
<br />
if [ -d $ULTRABAY_SYSDIR ]; then<br />
sync<br />
# Unmount filesystems backed by this device<br />
## This seems to be very inelegant and prone to failure<br />
unmount_rdev `cat $ULTRABAY_SYSDIR/block/*/dev \<br />
$ULTRABAY_SYSDIR/block/*/*/dev` \<br />
|| {<br />
logger ultrabay_eject umounting failed<br />
echo 2 > /proc/acpi/ibm/beep; # triple error tone<br />
exit 1;<br />
}<br />
sync<br />
# Nicely power off the device<br />
DEVNODE=`ultrabay_dev_node` && hdparm -Y $DEVNODE<br />
# Let HAL+KDE notice the unmount and let the disk spin down<br />
sleep 0.5<br />
# Unregister this SCSI device:<br />
sync<br />
echo 1 > $ULTRABAY_SYSDIR/delete<br />
else<br />
logger ultrabay_eject no ultrabay device directory<br />
echo 2 > /proc/acpi/ibm/beep # triple error tone<br />
exit 1<br />
fi<br />
<br />
# We need sleep here so someone can disconnect the bay and the drive<br />
sleep 1<br />
<br />
# Turn off power to the UltraBay<br />
dock=$( /bin/grep ata_bay /sys/devices/platform/dock.?/type )<br />
dock=${dock%%/type:ata_bay} # needed for 2.6.27 and later<br />
if [ -n "$dock" -a -d "$dock" ]; then<br />
logger ultrabay_eject undocking $dock<br />
echo 1 > $dock/undock<br />
fi<br />
# Tell the user we're OK<br />
logger ultrabay_eject done<br />
echo 12 > /proc/acpi/ibm/beep<br />
</pre><br />
<br />
<br />
== Untested on Fedora 11 ==<br />
<br />
The Fingerprint reader and the WWAN options have not been tested yet. If you tried them with Fedora 11, please update the table.<br />
<br />
[[Category:T60]][[Category:Fedora]][[Category:T60p]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installing_Fedora_10_on_a_ThinkPad_T60&diff=43129Installing Fedora 10 on a ThinkPad T602009-05-06T14:12:11Z<p>Pfps: add F11 stuff</p>
<hr />
<div>The news is that almost everything I tried works out of the box. Just make a Live USB stick and install normally.<br />
<br />
== Fedora 11 ==<br />
<br />
I haven't tried Ultrabay hard disk bays under Fedora 10, but in Fedora 11 they mostly work, except that the pre-eject button isn't hooked to anything by default. The tips in [How to hotswap Ultrabay devices] can be used to gracefully unmount, with some minor changes.<br />
<br />
PCMCIA to ATA adaptors (that, for example, allow compact flash cards to be attached to the PCMCIA card slot) have been problematic in the past, but appear to work fine now.</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installing_Fedora_10_on_a_ThinkPad_T60&diff=42816Installing Fedora 10 on a ThinkPad T602009-04-21T13:02:31Z<p>Pfps: everything works out of the box</p>
<hr />
<div>The news is that everything I tried works out of the box. Just make a Live USB stick and install normally.</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T60p&diff=42815Installation instructions for the ThinkPad T60p2009-04-21T13:00:20Z<p>Pfps: collapse T60p with T60</p>
<hr />
<div>[[Category:T60p]]<br />
Specific installation notes for the ThinkPad {{T60p|T60p}}.<br />
<br />
'''Note:''' you may want to look at [[Installation_instructions_for_the_ThinkPad_T60|Installation instructions for the ThinkPad T60]] as the two models have lots in common, especially if your distro/version doesn't appear here.<br />
<br />
==Distribution-specific instructions==<br />
<br />
=== Ubuntu / Kubuntu ===<br />
<br />
*[[Installing_Ubuntu_6.06_Kubuntu_6.06_Gentoo_2006.0_on_a_ThinkPad_T60p|Ubuntu and Kubuntu 6.06 Dapper Drake]]<br />
*[[Installing_Ubuntu_7.04 Feisty Fawn_on_a_ThinkPad_T60p | Ubuntu_7.04 Feisty Fawn]]<br />
*[[Installing_Ubunut_8.10 Intrepid Ibex_on_a_Thinkpad_T60p | Ubuntu_8.10 Intrepid Ibex]]<br />
<br />
My own notes and observations: -<br />
<br />
Happy New Year, and it's looking good so far .... suspend and resume ARE working on the T60p, really :-) <br />
http://www.davehay.f2s.com/2009/01/happy-new-year-and-its-looking-good-so.html<br />
<br><br />
Solved - ATI Catalyst Control Centre not saving configuration<br />
<br><br />
http://www.davidmhay.co.uk/2008/12/solved-ati-catalyst-control-centre-not.html<br />
<br><br />
Ubuntu 8.10 ( Intrepid Ibex ) and Suspend/Resume on the Thinkpad T60p ( 2007-AE7 )<br />
<br><br />
http://www.davidmhay.co.uk/2008/12/ubuntu-810-intrepid-ibex-and.html<br />
<br><br />
Installing and Using Ubuntu 8.10 on my Thinkpad T60p<br />
<br><br />
http://www.davidmhay.co.uk/2008/11/installing-and-using-ubuntu-810-on-my.html<br />
<br><br />
More from the land of the Ibex<br />
<br><br />
http://www.davidmhay.co.uk/2008/10/more-from-land-of-ibex.html<br />
<br><br />
Intrepidly going where no one ( apart from an ibex ) has gone before ...<br />
<br><br />
http://www.davidmhay.co.uk/2008/10/intrepidly-going-where-no-one-apart.html<br />
<br />
=== Red Hat Enterprise Linux / CentOS ===<br />
<br />
*[[Installing_Red_Hat_Enterprise_Linux_4_on_a_ThinkPad_T60p | Red Hat Enterprise Linux 4]]<br />
<br />
=== Red Hat Fedora ===<br />
*[[Installing_Fedora_Core_6_on_a_ThinkPad_T60p | Fedora Core 6]]<br />
<br />
=== Fedora ===<br />
*[[Installing_Fedora_7_on_a_ThinkPad_T60p | Fedora 7]]<br />
*[[Installing_Fedora_10_on_a_ThinkPad_T60 | Fedora 9,10,11]]<br />
<br />
=== Gentoo ===<br />
<br />
*[[Installing_Ubuntu_6.06_Kubuntu_6.06_Gentoo_2006.0_on_a_ThinkPad_T60p|Gentoo 2006.0]]<br />
<br />
<br />
=== Suse Linux ===<br />
<br />
Works out of the box, SLES SP1</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T60p&diff=42814Installation instructions for the ThinkPad T60p2009-04-21T12:59:05Z<p>Pfps: add link to current fedora</p>
<hr />
<div>[[Category:T60p]]<br />
Specific installation notes for the ThinkPad {{T60p|T60p}}.<br />
<br />
'''Note:''' you may want to look at [[Installation_instructions_for_the_ThinkPad_T60|Installation instructions for the ThinkPad T60]] as the two models have lots in common, especially if your distro/version doesn't appear here.<br />
<br />
==Distribution-specific instructions==<br />
<br />
=== Ubuntu / Kubuntu ===<br />
<br />
*[[Installing_Ubuntu_6.06_Kubuntu_6.06_Gentoo_2006.0_on_a_ThinkPad_T60p|Ubuntu and Kubuntu 6.06 Dapper Drake]]<br />
*[[Installing_Ubuntu_7.04 Feisty Fawn_on_a_ThinkPad_T60p | Ubuntu_7.04 Feisty Fawn]]<br />
*[[Installing_Ubunut_8.10 Intrepid Ibex_on_a_Thinkpad_T60p | Ubuntu_8.10 Intrepid Ibex]]<br />
<br />
My own notes and observations: -<br />
<br />
Happy New Year, and it's looking good so far .... suspend and resume ARE working on the T60p, really :-) <br />
http://www.davehay.f2s.com/2009/01/happy-new-year-and-its-looking-good-so.html<br />
<br><br />
Solved - ATI Catalyst Control Centre not saving configuration<br />
<br><br />
http://www.davidmhay.co.uk/2008/12/solved-ati-catalyst-control-centre-not.html<br />
<br><br />
Ubuntu 8.10 ( Intrepid Ibex ) and Suspend/Resume on the Thinkpad T60p ( 2007-AE7 )<br />
<br><br />
http://www.davidmhay.co.uk/2008/12/ubuntu-810-intrepid-ibex-and.html<br />
<br><br />
Installing and Using Ubuntu 8.10 on my Thinkpad T60p<br />
<br><br />
http://www.davidmhay.co.uk/2008/11/installing-and-using-ubuntu-810-on-my.html<br />
<br><br />
More from the land of the Ibex<br />
<br><br />
http://www.davidmhay.co.uk/2008/10/more-from-land-of-ibex.html<br />
<br><br />
Intrepidly going where no one ( apart from an ibex ) has gone before ...<br />
<br><br />
http://www.davidmhay.co.uk/2008/10/intrepidly-going-where-no-one-apart.html<br />
<br />
=== Red Hat Enterprise Linux / CentOS ===<br />
<br />
*[[Installing_Red_Hat_Enterprise_Linux_4_on_a_ThinkPad_T60p | Red Hat Enterprise Linux 4]]<br />
<br />
=== Red Hat Fedora ===<br />
*[[Installing_Fedora_Core_6_on_a_ThinkPad_T60p | Fedora Core 6]]<br />
<br />
=== Fedora ===<br />
*[[Installing_Fedora_7_on_a_ThinkPad_T60p | Fedora 7]]<br />
*[[Installing_Fedora_10_on_a_ThinkPad_T60p | Fedora 9,10,11]]<br />
<br />
=== Gentoo ===<br />
<br />
*[[Installing_Ubuntu_6.06_Kubuntu_6.06_Gentoo_2006.0_on_a_ThinkPad_T60p|Gentoo 2006.0]]<br />
<br />
<br />
=== Suse Linux ===<br />
<br />
Works out of the box, SLES SP1</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installing_Fedora_on_a_ThinkPad_T60&diff=36651Installing Fedora on a ThinkPad T602008-02-28T00:30:32Z<p>Pfps: /* Tuning */</p>
<hr />
<div>Creation timestamp: [[User:Whizkid|Whizkid]] 05:00, 6 February 2008 (CET)<br />
<br />
This document is meant to be the definitive resource to getting the latest current release of Fedora running on a ThinkPad T60. I welcome improvements to the page, especially for hardware I don't have (video chips, WiFi cards, WWAN devices).<br />
<br />
This document is current for Fedora 8. Fedora 9 Alhpa 1 has just been released, but we have a few months before that goes gold.<br />
<br />
=Installation Methods=<br />
Every T60 has a drive that can read DVDs. Nothing else is needed during the install, and it's the method I'm documenting first. Other methods of installation are detailed on the Fedora web site. For a smaller download, you can use the LiveCD, but fewer packages are available until you connect to the Internet.<br />
<br />
=Pre-installation=<br />
Fedora 8 does not have a method to shrink NTFS partitions during installation. You can use Knoppix or other LiveCD's to do that if you want to dual-boot. Links to pages on how to do that would be nice right about.... here.<br />
<br />
Installation tips:<br />
*Set the optical drive mode to High Performance during the installation to speed it up a little. To do that: Get into the BIOS. Select Config->Power->CDROM Speed->High.<br />
<br />
=Installation Steps=<br />
For any disc, I recommend completing the media test at least once on each disc you burn. Anaconda is the name of Fedora's installer program.<br />
==Installation DVD==<br />
*Boot the DVD. Skip ahead to '''Anaconda'''.<br />
==Live CD==<br />
*Boot the CD. After some initialization, you are eventually presented with the login screen. Click '''Fedora Live''' or wait 60 seconds. You are presented with the GNOME desktop. Double-click the icon titled '''Install to Hard Drive'''. Continue to the next section.<br />
==Anaconda==<br />
*You are presented with a title screen and no instructions. (That's what we're here for!) Click Next.<br />
*Select the installation language. Click Next. (Not presented if using LiveCD. It uses the current language.)<br />
*Select your keyboard language. Click Next. The installer looks for existing installations. You are prompted to choose a clean installation or upgrade. I'm documenting a clean install. Click Next.<br />
*You are asked how to partition your drive. The default is to remove existing Linux partitions. That's a fine choice. Turn on the Review check box to see how it will partition the drive if you're curious. Click Next.<br />
*Confirm that you want to delete partitions.<br />
If you checked the Review box above, you are presented with the new disk layout. Edit as you please then click Next.<br />
*The installer looks for other installed operating systems. You are asked where the boot loader will be installed. If you want to keep ThinkVantage functionality, check '''Configure advanced boot loader options'''. You can change the label of the other operating systems on the drive and select a default OS. Click Next.<br />
If you selected advanced option configuration, you are asked where the boot loader should be installed. Select the first sector of the boot partition, not the MBR, if you want ThinkVantage to work at startup, or if you want another OS to manage the boot process. Click Next.<br />
*You are asked whether the wired Ethernet controller should be active on boot. Since I use mine with WiFi most of the time, I turn that off and set the hostname manually. Click Next. Click Continue to confirm no network devices at boot if asked.<br />
*Select your time zone, choose whether or not the clock uses UTC and click Next.<br />
*Enter your root password. Do it again. Click Next.<br />
*If using the DVD, the installer looks for common installation packages. Since everything is out of date already, I turn off all options and customize later. Click Next. The installer checks dependencies.<br />
*You are asked one last time to confirm installation. Nothing has yet been written to the disk and this is the last point you can abort installation without changing anything on the drive. Click Next.<br />
<br />
The partition table is written, partitions are formatted, the install image is copied and packages are installed. The disc is ejected and you are asked to reboot the machine. The process took 17 minutes on my T60 with a 2.0GHz Core Duo and 5400RPM hard drive with the DVD, or about 6 minutes using the LiveCD.<br />
<br />
=First Boot=<br />
During the first boot, the system may wait a long time while trying to connect to a WiFi access point, even though your WiFi card may not have been detected by the installer.<br />
*A welcome screen is presented. Your screen should now be in its native resolution. Click Forward.<br />
*A license information screen is presented. Click Forward.<br />
*Firewall configuration is presented. Configure as you like. Click Forward.<br />
*SELinux setting is presented. Click Forward.<br />
*Set your local date and time. Click Forward.<br />
*Your hardware profile is shown. If you opt in and send your profile, your machine is counted by the Fedora team to get an idea of the population on which Fedora runs. Consider opting in to let them know we have these machines and want Fedora to run well on them. Click Forward.<br />
*Create a user. Click Finish. Done!<br />
<br />
=Get Updates=<br />
Get a network connection going and get all recent updates. Reboot if a new kernel is installed. I like to use NetworkManager.<br />
==Configuring NetworkManager==<br />
This section does not apply if you login using network authentication. NetworkManager is not perfect, and requires you to enter a keyring password at times, but it's a convenient way to connect to different networks, especially wireless networks.<br />
*First make sure neither network device is enabled at boot time. Network devices that are enabled at boot time will attempt to get an IP address using DHCP by default. If you are near a secured WiFi hotspot, you will not get an IP address and the system will wait until it times out. Select System->Administration->Network. For each device listed, double-click it and turn off '''Activate device when computer starts'''. You may wish to enable '''Allow all users to enable and disable the device'''. Save changes and quit.<br />
*Select System->Administration->Services. Check NetworkManager and NetworkManagerDispatcher and start each one. Save the configuration.<br />
Your wired network will automatically connect and your wireless networks should now be visible.<br />
To connect to a wireless network, click the NetworkManager notification icon and click the network to join.<br />
<br />
Shortly after you connect to the internet, you should be notified that there are updates available. If you are asked for the install media, you can disable that repository.<br />
<br />
=Device Configuration=<br />
==Audio==<br />
The Intel 82801G (ICH7) High Definition Audio Controller is identified and enabled automatically. The AD198x Analog PCM device works for audio. The Digital PCM device does not seem to work. Could it be that it only works in a dock?<br />
==Video Chip==<br />
===ATI X1300 and ATI X1400===<br />
Currently, Fedora does not include a driver specific to this card. It selects the '''vesa''' driver, which works fine, but performance is slow. The RadeonHD driver is in progress but also has no accelerated video modes, so is not a recommended option at this time.<br />
ATI's proprietary '''fglrx''' driver now works very well for the T60. The easiest way to get the driver and have automatic updates is to use the Livna repository.<br />
* Click the Fedora 8 repository from the front page of [http://rpm.livna.org].<br />
* Let the Fedora package installer install the RPM package.<br />
* Select Applications->Add/Remove Software.<br />
* Under RPM Fusion - Nonfree, check Hardware Support.<br />
* Click Optional packages.<br />
* Check '''xorg-x11-drv-fglrx''', close and Apply.<br />
* Reboot the machine and log in. (Logging out is not sufficient.)<br />
At this point, you should have 2D and 3D acceleration working. This is while using the vesa driver:<br />
$glxinfo | grep direct<br />
direct rendering: No (...)<br />
OpenGL renderer string: Mesa GLX Indirect<br />
And while using the fglrx driver:<br />
$glxinfo | grep direct<br />
direct rendering: Yes<br />
To disable the '''fglrx''' driver and use '''vesa''':<br />
/usr/sbin/fglrx-config-display disable<br />
and reboot. Use '''enable''' to switch back to the fglrx driver.<br />
Fedora does not install any 3D software by default, but several titles are available in the repositories. Other third-party applications work well too, including Google Earth.<br />
<br />
===Intel video===<br />
==WiFi==<br />
===Intel PRO/Wireless 3945ABG===<br />
This card is detected and enabled automatically. The activity indicator LED doesn't work with the standard driver. That appears to have been fixed in the latest version of the driver, but that is not yet in Fedora.<br />
<br />
==Pointing Devices==<br />
===TrackPoint===<br />
The TrackPoint pointing device works automatically. Information on getting the middle button to act as a scroll wheel goes here.<br />
===Touch Pad===<br />
The touch pad is enabled and works automatically. Press-to-select is enabled by default.<br />
<br />
==Bluetooth==<br />
==Fingerprint Reader==<br />
==WWAN==<br />
===Verizon EVDO===<br />
==Special Keys==<br />
===Fn+F2 Lock Screen===<br />
===Fn+F3 Sleep===<br />
===Fn+F4 Suspend to RAM (Standby) ===<br />
Suspend to RAM works automatically. Closing the lid also put the machine into the same standby mode.<br />
<br />
===Fn+F5 Radio Control===<br />
===Fn+F7 Display Selection===<br />
===Fn+F8 Pointing Devices===<br />
===Fn+F9 Eject===<br />
===Fn+F12 Suspend to Disk (Hibernate)===<br />
Suspend to disk works automatically.<br />
<br />
===Fn+Home/End Brightness===<br />
Brightness control works automatically. GNOME's on-screen display for brightness works. When on AC, brightness is dimmed by default. To disable this, click System->Preferences->System->Power Management. Click the On Battery Power tab, and set the Dim display brightness by: slider to the desired amount.<br />
===Volume===<br />
Volume up, volume down and volume mute work automatically, as does the on-screen display.<br />
===ThinkVantage===<br />
This button doesn't do anything by default, and it's not obvious what it should do when running Linux, if anything.<br />
<br />
==Infrared==<br />
<br />
=Tuning=<br />
This section details how to tune your system for performance or battery life. These are the numbers I got from PowerTop (yum install powertop to install this handy tool).<br />
{| border="1"<br />
|+My power consumption<br />
|-<br />
!Description!!Wakes per second!!Wattage!!Estimated Time<br />
|-<br />
|Default - No changes||45000||27.8W||2.6Hr<br />
|-<br />
|Enable USB suspend||45000||27.8W||2.6Hr<br />
|-<br />
|Kill hald-addon-storage||45000||27.8W||2.6Hr<br />
|-<br />
|Increase writeback time||45000||27.8W||2.6Hr<br />
|-<br />
|Enable USB suspend||45000||27.8W||2.6Hr<br />
|-<br />
|Turn Bluetooth off||45000||27.8W||2.6Hr<br />
|-<br />
|Enable laptop mode||45000||27.8W||2.6Hr<br />
|}<br />
PowerTop didn't help at all this time. I was pretty sure it helped a lot when I installed from DVD. FIXME.<br />
<br />
[[User:Pfps|Pfps]] 01:30, 28 February 2008 (CET) This very high number of wakeups is a problem that has been reported elsewhere, but I am not aware of any fix. My T60p does this sometimes. Sometimes it doesn't. I don't know why. Does anyone have any ideas?<br />
<br />
[[Category:T60]]<br />
[[Category:Fedora]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installing_Fedora_8_on_a_ThinkPad_T60&diff=36341Installing Fedora 8 on a ThinkPad T602008-02-05T00:28:51Z<p>Pfps: add fresh installation on T60p</p>
<hr />
<div>Meaning to get to this, but don't wait for me. Anyone doing a clean install should go ahead and fill this space. Here's the very short version:<br />
<br />
I recently upgraded my T60 from F7 to F8, and that went smoothly.<br />
<br />
Things mostly work when using the vesa driver for video. You can use the ATI driver if you want 3D, and that works great, but then suspend and resume stops working. I get a hang on suspend.<br />
<br />
The free Intel WiFi driver works, but the status LED does not work.<br />
<br />
What's your experience? --[[User:Whizkid|Whizkid]] 19:52, 16 November 2007 (UTC)<br />
<br />
== Fresh install ==<br />
<br />
I did a fresh install on my T60p, which I previously had Fedora Core 6 on.<br />
<br />
Things worked quite well. The vesa driver is working OK over my ATI graphics card. The iwl3945 module is working acceptably (and much less of a pain to keep up to date than the old ipw3945). However, sometimes I'm getting lost connections. I'll try to investigate.<br />
<br />
Hibernate works, but is very slow. I haven't tried suspending. [[User:Pfps|Pfps]] 01:28, 5 February 2008 (CET)<br />
<br />
[[Category:T60]]<br />
[[Category:Fedora]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installing_Fedora_7_on_a_ThinkPad_T60&diff=32139Installing Fedora 7 on a ThinkPad T602007-08-16T20:44:07Z<p>Pfps: /* ATI Mobility Radeon X1300 (M52) & X1400 (M54) */</p>
<hr />
<div>Created by: [[User:spot|TomCallaway]] 09:45, March 20, 2007<br />
<br />
===Abstract===<br />
<br />
This article describes how I got Fedora 7 installed on my IBM/Lenovo ThinkPad T60. Now, I know that Fedora 7 isn't out yet, so this information is specific to the test releases. When Fedora 7 comes out, I'll update this page to reflect any changes.<br />
<br />
===My ThinkPad===<br />
<br />
These are the specifications of my machine. <br />
<br />
* Lenovo ThinkPad T60 (6369-CTO)<br />
* [[Intel Core 2 Duo (Merom)]] T7200 @ 2.00GHz<br />
* [[Intel Graphics Media Accelerator 950]]<br />
* [[Ethernet Controllers#Intel Gigabit (10/100/1000)|Intel Gigabit Ethernet Controller]]<br />
* [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]<br />
* Integrated Bluetooth.<br />
* [[Integrated Fingerprint Reader]]<br />
* 100 GB - Serial ATA-150 Hard Drive.<br />
* 15.4" TFT display with 1680x1050 resolution (widescreen)<br />
* Intel 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
<br />
===What Works?===<br />
<br />
* Fedora<br />
* Most of the function keys, except the ones mentioned below<br />
* The fingerprint reader.<br />
* Video, 2D and 3D.<br />
* Brightness, Volume and Mute with OSD (On-Screen Display).<br />
* ThinkLight, TrackPoint II and the touchpad.<br />
* Bluetooth<br />
* Infrared<br />
* Suspend<br />
<br />
===What Doesn't Work? (Known Issues)===<br />
<br />
* Modem<br />
* Hibernate<br />
<br />
===Kernel Drivers===<br />
<br />
The laptop uses the following hardware specific kernel drivers:<br />
<br />
* iwlwifi (wireless)<br />
* e1000 (ethernet)<br />
* snd_hda_intel (sound)<br />
* nsc_ircc (infrared)<br />
<br />
===Installing Fedora===<br />
<br />
I really have no interest in dual-booting my laptop. There are plenty of good guides to setting up a computer for dual-boot on the internet. I burned a copy of the FC 6.91 DVD iso, booted off of it, and told the installer to delete all existing partitions. The install went off without a hitch. After installation, I ran yum update, and rebooted into the new kernel.<br />
<br />
===Post Install===<br />
The Fedora repositories have some useful packages for ThinkPads. After I installed the OS, I used yum to install the following packages:<br />
<br />
* thinkfinger: Support for the Fingerprint Reader<br />
* tpb: ThinkPad button support utility and onscreen display<br />
* beryl-gnome: Eyecandy!<br />
* iwlwifi-firmware: The firmware for the new intel wireless driver<br />
* xbindkeys: A utility to help us bind the "special" thinkpad keys<br />
* xorg-x11-drv-i810: Driver for the Intel Graphics Chipsets<br />
<br />
===Wireless LAN===<br />
The latest Fedora 7 kernels include a new driver for the Intel 3945 chipset, called iwlwifi. This driver works, but it is a bit new, so you must be patient with it. If you didn't install the iwlwifi-firmware package, do so now. The kernel should have detected the wireless device, and configured iwlwifi for you.<br />
<br />
Step 1: Turn on the radio<br />
Make sure the switch on the front is pushed to the right (you should be able to see green on the left). Then, as root, run:<br />
<br />
: {{cmdroot| /sbin/ifconfig wlan0 up}}<br />
<br />
Step 2: Scan for access points<br />
Even if you know the ESSID, the iwlwifi driver needs to also be told the frequency and access point that you want to connect to. Hopefully, this will be fixed in a later revision of the driver.<br />
<br />
As root, run:<br />
: {{cmdroot| /sbin/iwlist wlan0 scanning}}<br />
<br />
You should see something like:<br />
<br />
<pre><br />
Cell 03 - Address: 00:01:02:03:04:05<br />
ESSID:"freewifi"<br />
Mode:Master<br />
Frequency:2.462 GHz<br />
Signal level=-80 dBm <br />
Encryption key:on<br />
Extra:tsf=000000deadb33fabc<br />
Extra:bcn_int=100<br />
Extra:rssi=-80<br />
Extra:capab=0x0411<br />
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s<br />
</pre><br />
<br />
Assuming that's the AP we want to connect to, note the Frequency, Address, and ESSID.<br />
<br />
Step 3: Tell wlan0 about our AP<br />
Now, we just need to configure wlan0 to find our AP:<br />
As root, run:<br />
<br />
: {{cmdroot| /sbin/iwconfig wlan0 freq 2.462G}}<br />
: {{cmdroot| /sbin/iwconfig wlan0 ap 00:01:02:03:04:05}}<br />
: {{cmdroot| /sbin/iwconfig wlan0 essid "freewifi"}}<br />
<br />
Step 4: Get an IP Address<br />
Assuming the wireless network is DHCP, as root, run:<br />
<br />
: {{cmdroot| /sbin/dhclient wlan0}}<br />
<br />
Now your wireless is up and running!<br />
(Note: Your mileage may vary. There are lots of bug reports against iwlwifi. Maybe it is only a problem with NetworkManager, but my experience is that Fedora 7 test 4 (6.93) has unworkable wifi out of the box, at least on a T60p with an ipw3945.)<br />
As of 15 June 2007, NetworkManager still doesn't work very well with the iwlwifi device.<br />
There is a discussion on this on the fedora test list, starting with<br />
https://www.redhat.com/archives/fedora-test-list/2007-April/msg00539.html<br />
<br />
===Bluetooth===<br />
Bluetooth works out of the box, but Gnome GUI only provides limited functionality (like Obex file transfers).<br />
To configure bluetooth serial ports (those are used to connect to internet via Your bluetooth enabled mobile phone, to use bluetooth GPS devices etc), You have to manually tweak {{path|/etc/bluetooth/rfcomm.conf}} file.<br />
<br />
At first run:<br />
: {{cmduser| hcitool scan}}<br />
<br />
The output should be something like<br />
<pre><br />
Scanning ...<br />
00:0A:D9:ED:89:4E Anttix P900<br />
</pre><br />
<br />
Note the MAC address of Your phone, then run:<br />
: {{cmduser| sdptool browse MAC_ADDRESS_OF_YOUR_PHONE}}<br />
<br />
Find modem channel by looking for an entry like this:<br />
<pre><br />
Service Name: Dial-up Networking<br />
Service Description: Dial-up Networking<br />
Service Provider: Sony Ericsson<br />
Service RecHandle: 0x10001<br />
Service Class ID List:<br />
"Dialup Networking" (0x1103)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 7<br />
Language Base Attr List:<br />
code_ISO639: 0x656e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"Dialup Networking" (0x1103)<br />
Version: 0x0100<br />
</pre><br />
<br />
Now edit {{path|/etc/bluetooth/rfcomm.conf}}.<br />
Uncomment the lines for rfcomm0 and replace MAC and channel numbers with the ones from Your phone.<br />
Also make sure to turn on automatic binding on startup.<br />
The final config will look like this:<br />
<pre><br />
rfcomm0 {<br />
# Automatically bind the device at startup<br />
bind yes;<br />
<br />
# Bluetooth address of the device<br />
device 00:0A:D9:ED:89:4E;<br />
<br />
# RFCOMM channel for the connection<br />
channel 7;<br />
<br />
# Description of the connection<br />
comment "My GSM Dialup Networking";<br />
}<br />
</pre><br />
<br />
Restart bluetooth subsystem:<br />
<br />
{{cmdroot|service bluetooth restart}}<br />
<br />
Now run network configuration tool, add a new modem to device {{path|/dev/rfcomm0}} and configure an internet connection as usual. The phone number depends on Your phone make, but most of the time it's <code>*99#</code>. You might also need to add additional modem initialization string <code>AT+cgdcont=1,"IP","internet",,0,0</code> to configure Your GPRS service name.<br />
<br />
Make sure that Gnome bluetooth applet is running. If not, run it by typing bluetooth-applet.<br />
<br />
Activate the connection. You should be prompted for PIN by both: the phone and the applet. Enter the same number on both sides to pair the connection.<br />
<br />
===Infrared===<br />
T60 has an NSC FIR chip. The driver needs to know a Dongle ID so it must be manually configured.<br />
<br />
Edit {{path|/etc/modprobe.conf}}, add the following two lines:<br />
<pre><br />
alias irda0 nsc-ircc<br />
options nsc-ircc dongle_id=0x09<br />
</pre><br />
<br />
Edit {{path|/etc/sysconfig/irda}}:<br />
<pre><br />
IRDA=yes<br />
DEVICE=irda0<br />
DISCOVERY=yes<br />
</pre><br />
<br />
Start IRDA<br />
<br />
{{cmdroot|service irda start}}<br />
<br />
If You want IRDA to be enabled during system boot, turn it on like this:<br />
<br />
{{cmdroot|chkconfig irda on}}<br />
<br />
===Getting the ThinkVantage Buttons to work===<br />
<br />
Fedora does not recognize all the ThinkVantage buttons correctly by default. This can be fixed quite easily. Just edit /etc/X11/Xmodmap.<br />
<br />
Then paste the following in the file:<br />
<br />
<pre><br />
keycode 234 = XF86Back<br />
keycode 233 = XF86Forward<br />
keycode 159 = XF86Start<br />
keycode 162 = XF86AudioPlay<br />
keycode 164 = XF86AudioStop<br />
keycode 153 = XF86AudioNext<br />
keycode 144 = XF86AudioPrev<br />
keycode 227 = XF86LaunchF<br />
keycode 249 = XF86ZoomIn<br />
</pre><br />
<br />
Save and close the file, then logout and back in again. You can now assign the buttons to do anything you want. For example, use the Back and Forward buttons (next the cursor keys) to flip desktops using the cube effect in Beryl (set this using the Beryl settings manager). You can set most of the other keys using Gnome vis System - Preferences - Keyboard Shortcuts.<br />
<br />
For the ThinkVantage and Zoom buttons, I used xbindkeys. Open a terminal and type:<br />
<br />
: {{cmduser| xbindkeys --defaults > ~/.xbindkeysrc}}<br />
: {{cmduser| xbindkeys-config}}<br />
<br />
Click "New" and assign a remark to the new shortcut. Then press "Grab" and press the combination you want (ex: The ThinkVantage button). You can then set the action you want executed in the "Action" field. <br />
<br />
=== Video Drivers ===<br />
<br />
====Intel Graphics Media Accelerator 950 (GMA950)====<br />
Since the Fedora installer didn't detect the graphics device properly, it uses the Vesa driver. Which works, but that's not really what we want to use. After installing the xorg-x11-drv-i810 package, I edited the /etc/X11/xorg.conf, and changed the driver from "vesa" to "intel". Then, restart X. That's it.<br />
<br />
====ATI Mobility Radeon X1300 (M52) & X1400 (M54)====<br />
ATI's drivers did not work with Fedora 7 because they couldn't handle the xorg version there. Version 8.39.4, and above, are compatible with Fedora 7. Matching kernel modules are provided by the livna repository.<br />
<br />
<br />
: {{cmdroot| rpm -i http://rpm.livna.org/livna-release-7.rpm}}<br />
: {{cmdroot| yum install kmod-fglrx}}<br />
<br />
===The Fingerprint Reader===<br />
<br />
Thanks to the efforts of the ThinkFinger guys, the fingerprint reader works very well in Linux using entirely Free Software. After installing thinkfinger, you need to edit /etc/pam.d/system-auth as root (be careful!):<br />
<br />
Above the line that reads:<br />
<br />
<pre><br />
auth sufficient pam_unix.so nullok try_first_pass<br />
</pre><br />
<br />
Add a new line that reads:<br />
<br />
<pre><br />
auth sufficient pam_thinkfinger.so<br />
</pre><br />
<br />
So, the auth section of your /etc/pam.d/system-auth file should look like:<br />
<br />
<pre><br />
auth required pam_env.so<br />
auth sufficient pam_thinkfinger.so<br />
auth sufficient pam_unix.so nullok try_first_pass<br />
auth requisite pam_succeed_if.so uid >= 500 quiet<br />
auth required pam_deny.so<br />
</pre><br />
<br />
Save the updated /etc/pam.d/system-auth, then as root, run:<br />
<br />
: {{cmdroot| /usr/sbin/tf-tool --add-user spot}}<br />
<br />
Of course, if your username isn't spot, change it! It will prompt you to swipe your finger over the reader three times.<br />
<br />
Thats it! Now, you can login using either a password or a fingerprint.<br />
<br />
===Beryl - eyecandy===<br />
Beryl is shiny desktop eyecandy. To get it running, you can follow the steps here:<br />
http://wiki.beryl-project.org/wiki/Install/Fedora_Core<br />
<br />
===Suspend===<br />
Create a new file {{path|/etc/rc.modules}} and put the following lines into it:<br />
<pre><br />
# Turn on correct suspend flags for T60<br />
echo 3 > /proc/sys/kernel/acpi_video_flags<br />
</pre><br />
Then make it executable:<br />
<br />
{{cmdroot|chmod 755 /etc/rc.modules}}<br />
<br />
After reboot the machine should suspend and wake up fine.<br />
<br />
NOTE: I have tried the above with FC7 and T60p and still have not gotten suspend to work. It worked out of the box on FC6. I have also added the following lines to the kernel parameters but with no luck. pci=noacpi acpi_sleep=s3_bios,s3_mode.<br />
<br />
===Thanks===<br />
Much credit goes to [[User:Keithvassallo|Keithvassallo]] for his [http://thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60 Installing Ubuntu Edgy Eft on the Thinkpad T60] page.<br />
<br />
==References==<br />
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation guides survey (IBM/Lenovo)].<br />
<br />
[[Category:T60]]<br />
[[Category:Fedora]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=32134Fglrx2007-08-16T15:25:38Z<p>Pfps: /* Display Switching (Dynamic Display Management) */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
== ATI fglrx driver ==<br />
This is a proprietary Linux binary-only driver for ATI graphic chips with support for 3D acceleration.<br />
<br />
Also see [[R300|opensource driver]] with 3D support<br />
|}<br />
<br />
==Availability / Project Homepage==<br />
Home page: http://ati.amd.com/support/drivers/linux/linux-radeon.html<br />
<br />
== Packages ==<br />
The ATI drivers have explicit permission for repackaging and redistribution of the Linux drivers. Many distributions are supported within the installer, and many more repackaged by external developers. Please visit the [http://wiki.cchtml.com/index.php/Category:Distributions Distribution Page at the Unofficial ATI driver Wiki]<br />
<br />
*{{Debian}}<br />
** These packages have been added to Debian unstable as <tt>fglrx-driver</tt>, so you can now apt-get them and use module-assistant to install.<br />
** If you are on stable sarge with backport's kernel 2.6.15, download ATI's installer, let it build Debian packages and proceed as usual. There's a [http://jroller.com/page/erAck?entry=lot_day_6_2_fglrx detailed description] available.<br />
** [http://wiki.cchtml.com/index.php/Debian_Installation_Guide Debian Howto]<br />
*{{SUSE}} packages: http://www.suse.de/~sndirsch/ati-installer-HOWTO.html<br />
*{{Gentoo}} {{cmdroot|emerge ati-drivers}}<br />
*{{Fedora}} 4 packages: http://rpm.livna.org<br />
** For stock Fedora kernels: {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}<br />
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]<br />
*{{Fedora}} 5 packages: http://rpm.livna.org<br />
** For stock Fedora kernels: {{cmdroot|yum install xorg-x11-drv-fglrx}}<br />
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]<br />
*{{Fedora}} 7 packages: http://rpm.livna.org<br />
** The newest version of the driver (8.39.4) is supposed to work with Fedora 7, and is available from Livna.<br />
*{{Arch Linux}}<br />
:{{cmdroot|pacman -S ati-fglrx}} (kernel module for 2.6.15-ARCH)<br />
:{{cmdroot|pacman -S ati-fglrx-archck}} (kernel module for 2.6.15-archck)<br />
:{{cmdroot|pacman -S ati-fglrx-utils}} (xorg7 stuff and tools)<br />
*{{Ubuntu}}<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide Dapper Drake Howto]<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Breezy_Installation_Guide Breezy Badger Howto]<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Edgy_Installation_Guide Edgy Eft Howto]<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide Feisty Fawn Howto]<br />
<br />
== Building for Xorg 7.0==<br />
To compile fglrx versions <= 8.24.8 for Xorg 7.0.0, fake Xorg 6.9.0 by <br />
:{{cmdroot|1=export X_VERSION=x690; sh ati-driver-installer-8.24.8-x86.run}}<br />
Next, move the various resulting libraries and modules from /usr/X11R6 to /usr/lib/xorg<br />
<br />
In {{path|/usr/src/ATI}} additional sources are installed for fireglcontrol and fgl_glxgears<br />
<br />
== Status ==<br />
Current version: 8.40.4 ( 13th August 2007).<br />
Major changes:<br />
* 8.40.4: some new TV out control options in CCC, another (non-exciting) maintenance release (see [http://www.phoronix.com/scan.php?page=article&item=804&num=1 Phoronix])<br />
* 8.39.4: kernel 2.6.22 support, TexturedVideo fix, aticonfig segfault fix (see 8.38.7 hotfix), to get rid of the "AMD Testing use only" logo, use [http://www.phoronix.com/forums/showpost.php?p=10641&postcount=44 this] workaround.<br />
* 8.38.7: hotfix release for "Using aticonfig --initial segfaults destroying xorg.conf file when run in X with Vesa driver.", search for "737-28261" on the ATI website.<br />
* 8.38.6: RedHat Enterprise Linux 5 support, Xserver crashes on moving video window between two monitors fixed, corruption when playing multiple vodeps with textured video fixed<br />
* 8.37.6: Xorg Server 1.3 support, CCC 1.0, crash when logging off from X fixed, Xv cropping bug fixed<br />
* 8.36.5: Kernel 2.6.20 support, CCC Beta 0.9 with localization<br />
* 8.35.5: Beta AMD Catalyst Control Center, X-Server termination from console does not result in a blank screen. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.35.5|fglrx patches section]]).<br />
* 8.34.8: Radeon Xpress 1250 support, X-Video on x86_64 fix, hibernation mode fix. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.34.8|fglrx patches section]]).<br />
* 8.33.6: X.Org 7.2 support, kernel 2.6.19 support, some fixes in the installer, 2 more bugfixes. Resume from suspend works if you make sure you have set "VbetoolPost no" and "EnableVbetool no" in your suspend to ram hibernate conf (/etc/hibernate/ram.conf on ubuntu/debian).<br />
* 8.32.5: support for X1650, X.Org 7.2 RC2 support, bugfixes. Suspend-to-ram is broken with specific cards, *no* 2.6.19 support (see [[Problems_with_fglrx#fglrx_8.32.5|fglrx patches section]]).<br />
* 8.31.5: no new features, only bugfixes. Of note, for some users, this version breaks suspend-to-ram and suspend-to-disk.<br />
* 8.30.3: no new features, only bugfixes<br />
* 8.29.6: Linux 2.6.18 support, dropped support for Radeon 8500/9000/9100/9200/9250 (both, mobile and normal versions)<br />
* 8.28.8: Display Switching Support for ThinkPads, ATI Pairmode support, Retaining display device state between restarts, Support for Radeon Xpress 1200, 1250, and 1300<br />
* 8.27.10: X.org 7.1 support, Fedora Core package support<br />
* 8.26.18: support for dynamically attached DFPs and Thermal Event Power Management (both via daemon), minor bug fixes<br />
* 8.25.18: Xorg 7.0 support, FireGLâ„¢V5xxx/V7xxx support, Dynamic Display Management, fixed a lot of critical bugs.<br />
* 8.24.8: support for X1300, X1400, X1600, X1800 (generic and mobility) and 3D accelerated video playback on Avivo<br />
* 8.23.7: support for X850 and X800, OpenGL 2.0 Enhancement, FSAA for some chips<br />
* 8.22.5: added kernel 2.6.15 support -- patch no longer required<br />
* 8.21.7: initial OpenGL 2.0 support<br />
* 8.20.8: fixed resume issues, fixed compile problems with kernels 2.6.13 and 2.6.14<br />
* 8.19.10: has added suspend / resume and dynamic GPU power management support. Using vbetool no longer required.<br />
<br />
== Known problems and solutions ==<br />
See [[Problems with fglrx]].<br />
== User experience ==<br />
=== Speed ===<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
Compared to the old drivers, approximately 40% speed gain have been noticed with fglrx. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (via {{key|ctrl}}{{key|alt}}{{key|plus}}, {{key|ctrl}}{{key|alt}}{{key|minus}}), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using the open source radeon driver: 1200 FPS for glxgears{{footnote|1}}!<br />
However the situation seems to be changing today. With recent x11-drm-20060608 driver (gentoo) and thinkpad t42 (ati 9600) the speed is confirmed as 1900fps without any single crash so far.<br />
<br />
=== 3D acceleration ===<br />
<br />
According to [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] you need these options:<br />
<br />
Section "Module"<br />
...<br />
Load "GLcore"<br />
Load "glx"<br />
Load "dri"<br />
...<br />
EndSection<br />
<br />
# Of course you need to activate the driver<br />
Section "Device"<br />
...<br />
Driver "fglrx"<br />
EndSection<br />
<br />
Don't forget to load the module <tt>fglrx</tt> (<tt>modprobe fglrx</tt>). Under Debian the module can be placed in <tt>/etc/modules</tt>.<br />
<br />
With current fglrx drivers (as of 8.29.6) you must disable composite to get 3D DRI acceleration. To do this, add an extra Extensions section (if necessary) containing:<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable" #make DRI work with fglrx.<br />
EndSection<br />
<br />
If you are unsure whether you have DRI running, issue <tt>glxinfo | grep -i direct</tt> after disabling composite. Note, this <br />
<br />
{{NOTE|1=Video overlay acceleration may be disabled when 3D acceleration is enabled. The following comment from the xorg.conf file bundled with the fglrx driver indicates that:<br />
# === OpenGL Overlay ===<br />
# Note: When OpenGL Overlay is enabled, Video Overlay<br />
# will be disabled automatically<br />
Option "OpenGLOverlay" "1"<br />
However, you can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. This has nothing to do with the acceleration of 2D drawing primitives. Further, your mileage on performance may vary depending on what card you have. The open source drivers don't support newer cards, while the ATI drivers don't support older cards.<br />
<br />
You may be able to preserve VideoOverlay acceleration if you explicitly remove the OpenGLOverlay using:<br />
<br />
Option "VideoOverlay" "True" and Option "OpenGLOverlay" "False". See [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] for detail.}}<br />
<br />
=== Power saving ===<br />
Power saving is much better than with the <tt>radeon</tt> driver, but doesn't work in dual-screen configuration (see [[How to make use of Graphics Chips Power Management features]]).<br />
<br />
=== Suspending with fglrx ===<br />
<br />
On a ThinkPad T42 with Kernel 2.6.19 with Software Suspend 2 and R60 with Kernel 2.6.18-suspend2-r1 (Gentoo) , the following addition to <tt>/etc/hibernate/suspend2.conf</tt> is required:<br />
<br />
# For fglrx<br />
ProcSetting extra_pages_allowance 20000<br />
<br />
=== Display Switching (Dynamic Display Management) ===<br />
<br />
Version 8.25.18 introduces a new feature: Dynamic Display Management. It allows display switching on-the-fly.<br />
<br />
To list all connected and enabled monitors:<br />
:{{cmdroot|1=aticonfig --query-monitor}}<br />
<br />
To switch displays:<br />
:{{cmdroot|1=aticonfig --enable-monitor=STRING,STRING}}, where STRING can be: none, lvds, crt1, crt2, tv, tdms1, tdms2<br />
<br />
Only 2 displays can be enabled at the same time. Any displays that are not on the list will be disabled.<br />
<br />
The '''Catalyst Control Center''', which comes with the driver (at least from Livna in Fedora Core 6) can be used to do this switching. It also does various other kinds of display managements. However, the version that comes with 8.39.4 doesn't seem to handle switching into Big Desktop mode, does anyone know how to get this to work? The control center also complains a lot about rebooting, but rebooting doesn't seem to be required. Does anyone have decent documentation for the control center?<br />
<br />
== Useful links == <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www.rage3d.com/content/articles/atilinuxhowto/ ATI Radeon Linux How-To]<br />
* [http://www.rage3d.com/board/forumdisplay.php?f=61&daysprune=30&order=asc&sort=title Rage3D Linux Discussion Forum]<br />
* [http://www.driverheaven.net/forumdisplay.php?f=103 Radeon Driver Forum at Driverheaven]<br />
* [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html Gentoo ATI Radeon FAQ]<br />
* [http://forums.gentoo.org/viewtopic-t-374745-highlight-t42+ati+dri.html Gentoo T42 ATI. DRI + xorg driver]<br />
* [http://ati.cchtml.com/ Unofficial community ATI bugzilla] - tracks bugs in the driver. Might be monitored by ATI ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]).<br />
<br />
== ThinkPads that may be supported ==<br />
Supported chips, as found in select IBM ThinkPads:<br />
{{NOTE|fglrx version 8.29.6 discontinued support for Radeon 9200 and earlier.}}<br />
* [[ATI Mobility FireGL 9000]]<br />
** {{T40p}}<br />
* [[ATI Mobility FireGL T2]]<br />
** {{R50p}}<br />
** {{T41p}}, {{T42p}}<br />
* [[ATI Mobility FireGL V3200]]<br />
** {{T43p}}<br />
* [[ATI Mobility Radeon 9000]]<br />
** {{R50}}, {{R51}}<br />
** {{T40}}, {{T41}}, {{T42}}<br />
* [[ATI Mobility Radeon 9600]]<br />
** {{T42}}<br />
* [[ATI Mobility Radeon X300]]<br />
** {{R52}}<br />
** {{T43}}<br />
** {{Z60m}}<br />
* [[ATI Mobility Radeon Xpress 200M]]<br />
** {{R51e}}<br />
* [[ATI Mobility Radeon X600]]<br />
** {{Z60m}}<br />
* [[ATI Mobility Radeon X1400]]<br />
** {{T60}}, {{R60}}, {{Z61m}}<br />
* [[ATI Mobility FireGL V5200]]<br />
** {{T60p}}, {{Z61p}}<br />
<br />
== ThinkPads that are NOT supported by fglrx==<br />
Unsupported chips, as found in select IBM ThinkPads:<br />
* [[ATI Mobility Radeon 7500]]<br />
** {{R40}}<br />
** {{T30}}<br />
** {{T42}}<br />
<br />
{{footnotes|<br />
#Note that glxgears isn't a benchmark tool, it's so simple that its FPS values is without any meaning... you can only compare glxgears using the same drivers/machine, if you change any of then you can have higher/lower values and in real life programs/games happen to have the opposite effects. Think in terms of a car engines rpms: higher rpms in the same car usually means a faster car, change anything and it's meaningless, ie: gears, truck, wheel size, etc. make it useless.<br />
}}<br />
[[Category:Drivers]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=32133Fglrx2007-08-16T15:18:18Z<p>Pfps: /* Packages */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
== ATI fglrx driver ==<br />
This is a proprietary Linux binary-only driver for ATI graphic chips with support for 3D acceleration.<br />
<br />
Also see [[R300|opensource driver]] with 3D support<br />
|}<br />
<br />
==Availability / Project Homepage==<br />
Home page: http://ati.amd.com/support/drivers/linux/linux-radeon.html<br />
<br />
== Packages ==<br />
The ATI drivers have explicit permission for repackaging and redistribution of the Linux drivers. Many distributions are supported within the installer, and many more repackaged by external developers. Please visit the [http://wiki.cchtml.com/index.php/Category:Distributions Distribution Page at the Unofficial ATI driver Wiki]<br />
<br />
*{{Debian}}<br />
** These packages have been added to Debian unstable as <tt>fglrx-driver</tt>, so you can now apt-get them and use module-assistant to install.<br />
** If you are on stable sarge with backport's kernel 2.6.15, download ATI's installer, let it build Debian packages and proceed as usual. There's a [http://jroller.com/page/erAck?entry=lot_day_6_2_fglrx detailed description] available.<br />
** [http://wiki.cchtml.com/index.php/Debian_Installation_Guide Debian Howto]<br />
*{{SUSE}} packages: http://www.suse.de/~sndirsch/ati-installer-HOWTO.html<br />
*{{Gentoo}} {{cmdroot|emerge ati-drivers}}<br />
*{{Fedora}} 4 packages: http://rpm.livna.org<br />
** For stock Fedora kernels: {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}<br />
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]<br />
*{{Fedora}} 5 packages: http://rpm.livna.org<br />
** For stock Fedora kernels: {{cmdroot|yum install xorg-x11-drv-fglrx}}<br />
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]<br />
*{{Fedora}} 7 packages: http://rpm.livna.org<br />
** The newest version of the driver (8.39.4) is supposed to work with Fedora 7, and is available from Livna.<br />
*{{Arch Linux}}<br />
:{{cmdroot|pacman -S ati-fglrx}} (kernel module for 2.6.15-ARCH)<br />
:{{cmdroot|pacman -S ati-fglrx-archck}} (kernel module for 2.6.15-archck)<br />
:{{cmdroot|pacman -S ati-fglrx-utils}} (xorg7 stuff and tools)<br />
*{{Ubuntu}}<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide Dapper Drake Howto]<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Breezy_Installation_Guide Breezy Badger Howto]<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Edgy_Installation_Guide Edgy Eft Howto]<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide Feisty Fawn Howto]<br />
<br />
== Building for Xorg 7.0==<br />
To compile fglrx versions <= 8.24.8 for Xorg 7.0.0, fake Xorg 6.9.0 by <br />
:{{cmdroot|1=export X_VERSION=x690; sh ati-driver-installer-8.24.8-x86.run}}<br />
Next, move the various resulting libraries and modules from /usr/X11R6 to /usr/lib/xorg<br />
<br />
In {{path|/usr/src/ATI}} additional sources are installed for fireglcontrol and fgl_glxgears<br />
<br />
== Status ==<br />
Current version: 8.40.4 ( 13th August 2007).<br />
Major changes:<br />
* 8.40.4: some new TV out control options in CCC, another (non-exciting) maintenance release (see [http://www.phoronix.com/scan.php?page=article&item=804&num=1 Phoronix])<br />
* 8.39.4: kernel 2.6.22 support, TexturedVideo fix, aticonfig segfault fix (see 8.38.7 hotfix), to get rid of the "AMD Testing use only" logo, use [http://www.phoronix.com/forums/showpost.php?p=10641&postcount=44 this] workaround.<br />
* 8.38.7: hotfix release for "Using aticonfig --initial segfaults destroying xorg.conf file when run in X with Vesa driver.", search for "737-28261" on the ATI website.<br />
* 8.38.6: RedHat Enterprise Linux 5 support, Xserver crashes on moving video window between two monitors fixed, corruption when playing multiple vodeps with textured video fixed<br />
* 8.37.6: Xorg Server 1.3 support, CCC 1.0, crash when logging off from X fixed, Xv cropping bug fixed<br />
* 8.36.5: Kernel 2.6.20 support, CCC Beta 0.9 with localization<br />
* 8.35.5: Beta AMD Catalyst Control Center, X-Server termination from console does not result in a blank screen. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.35.5|fglrx patches section]]).<br />
* 8.34.8: Radeon Xpress 1250 support, X-Video on x86_64 fix, hibernation mode fix. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.34.8|fglrx patches section]]).<br />
* 8.33.6: X.Org 7.2 support, kernel 2.6.19 support, some fixes in the installer, 2 more bugfixes. Resume from suspend works if you make sure you have set "VbetoolPost no" and "EnableVbetool no" in your suspend to ram hibernate conf (/etc/hibernate/ram.conf on ubuntu/debian).<br />
* 8.32.5: support for X1650, X.Org 7.2 RC2 support, bugfixes. Suspend-to-ram is broken with specific cards, *no* 2.6.19 support (see [[Problems_with_fglrx#fglrx_8.32.5|fglrx patches section]]).<br />
* 8.31.5: no new features, only bugfixes. Of note, for some users, this version breaks suspend-to-ram and suspend-to-disk.<br />
* 8.30.3: no new features, only bugfixes<br />
* 8.29.6: Linux 2.6.18 support, dropped support for Radeon 8500/9000/9100/9200/9250 (both, mobile and normal versions)<br />
* 8.28.8: Display Switching Support for ThinkPads, ATI Pairmode support, Retaining display device state between restarts, Support for Radeon Xpress 1200, 1250, and 1300<br />
* 8.27.10: X.org 7.1 support, Fedora Core package support<br />
* 8.26.18: support for dynamically attached DFPs and Thermal Event Power Management (both via daemon), minor bug fixes<br />
* 8.25.18: Xorg 7.0 support, FireGLâ„¢V5xxx/V7xxx support, Dynamic Display Management, fixed a lot of critical bugs.<br />
* 8.24.8: support for X1300, X1400, X1600, X1800 (generic and mobility) and 3D accelerated video playback on Avivo<br />
* 8.23.7: support for X850 and X800, OpenGL 2.0 Enhancement, FSAA for some chips<br />
* 8.22.5: added kernel 2.6.15 support -- patch no longer required<br />
* 8.21.7: initial OpenGL 2.0 support<br />
* 8.20.8: fixed resume issues, fixed compile problems with kernels 2.6.13 and 2.6.14<br />
* 8.19.10: has added suspend / resume and dynamic GPU power management support. Using vbetool no longer required.<br />
<br />
== Known problems and solutions ==<br />
See [[Problems with fglrx]].<br />
== User experience ==<br />
=== Speed ===<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
Compared to the old drivers, approximately 40% speed gain have been noticed with fglrx. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (via {{key|ctrl}}{{key|alt}}{{key|plus}}, {{key|ctrl}}{{key|alt}}{{key|minus}}), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using the open source radeon driver: 1200 FPS for glxgears{{footnote|1}}!<br />
However the situation seems to be changing today. With recent x11-drm-20060608 driver (gentoo) and thinkpad t42 (ati 9600) the speed is confirmed as 1900fps without any single crash so far.<br />
<br />
=== 3D acceleration ===<br />
<br />
According to [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] you need these options:<br />
<br />
Section "Module"<br />
...<br />
Load "GLcore"<br />
Load "glx"<br />
Load "dri"<br />
...<br />
EndSection<br />
<br />
# Of course you need to activate the driver<br />
Section "Device"<br />
...<br />
Driver "fglrx"<br />
EndSection<br />
<br />
Don't forget to load the module <tt>fglrx</tt> (<tt>modprobe fglrx</tt>). Under Debian the module can be placed in <tt>/etc/modules</tt>.<br />
<br />
With current fglrx drivers (as of 8.29.6) you must disable composite to get 3D DRI acceleration. To do this, add an extra Extensions section (if necessary) containing:<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable" #make DRI work with fglrx.<br />
EndSection<br />
<br />
If you are unsure whether you have DRI running, issue <tt>glxinfo | grep -i direct</tt> after disabling composite. Note, this <br />
<br />
{{NOTE|1=Video overlay acceleration may be disabled when 3D acceleration is enabled. The following comment from the xorg.conf file bundled with the fglrx driver indicates that:<br />
# === OpenGL Overlay ===<br />
# Note: When OpenGL Overlay is enabled, Video Overlay<br />
# will be disabled automatically<br />
Option "OpenGLOverlay" "1"<br />
However, you can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. This has nothing to do with the acceleration of 2D drawing primitives. Further, your mileage on performance may vary depending on what card you have. The open source drivers don't support newer cards, while the ATI drivers don't support older cards.<br />
<br />
You may be able to preserve VideoOverlay acceleration if you explicitly remove the OpenGLOverlay using:<br />
<br />
Option "VideoOverlay" "True" and Option "OpenGLOverlay" "False". See [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] for detail.}}<br />
<br />
=== Power saving ===<br />
Power saving is much better than with the <tt>radeon</tt> driver, but doesn't work in dual-screen configuration (see [[How to make use of Graphics Chips Power Management features]]).<br />
<br />
=== Suspending with fglrx ===<br />
<br />
On a ThinkPad T42 with Kernel 2.6.19 with Software Suspend 2 and R60 with Kernel 2.6.18-suspend2-r1 (Gentoo) , the following addition to <tt>/etc/hibernate/suspend2.conf</tt> is required:<br />
<br />
# For fglrx<br />
ProcSetting extra_pages_allowance 20000<br />
<br />
=== Display Switching (Dynamic Display Management) ===<br />
<br />
Version 8.25.18 introduces a new feature: Dynamic Display Management. It allows display switching on-the-fly.<br />
<br />
To list all connected and enabled monitors:<br />
:{{cmdroot|1=aticonfig --query-monitor}}<br />
<br />
To switch displays:<br />
:{{cmdroot|1=aticonfig --enable-monitor=STRING,STRING}}, where STRING can be: none, lvds, crt1, crt2, tv, tdms1, tdms2<br />
<br />
Only 2 displays can be enabled at the same time. Any displays that are not on the list will be disabled.<br />
<br />
== Useful links == <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www.rage3d.com/content/articles/atilinuxhowto/ ATI Radeon Linux How-To]<br />
* [http://www.rage3d.com/board/forumdisplay.php?f=61&daysprune=30&order=asc&sort=title Rage3D Linux Discussion Forum]<br />
* [http://www.driverheaven.net/forumdisplay.php?f=103 Radeon Driver Forum at Driverheaven]<br />
* [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html Gentoo ATI Radeon FAQ]<br />
* [http://forums.gentoo.org/viewtopic-t-374745-highlight-t42+ati+dri.html Gentoo T42 ATI. DRI + xorg driver]<br />
* [http://ati.cchtml.com/ Unofficial community ATI bugzilla] - tracks bugs in the driver. Might be monitored by ATI ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]).<br />
<br />
== ThinkPads that may be supported ==<br />
Supported chips, as found in select IBM ThinkPads:<br />
{{NOTE|fglrx version 8.29.6 discontinued support for Radeon 9200 and earlier.}}<br />
* [[ATI Mobility FireGL 9000]]<br />
** {{T40p}}<br />
* [[ATI Mobility FireGL T2]]<br />
** {{R50p}}<br />
** {{T41p}}, {{T42p}}<br />
* [[ATI Mobility FireGL V3200]]<br />
** {{T43p}}<br />
* [[ATI Mobility Radeon 9000]]<br />
** {{R50}}, {{R51}}<br />
** {{T40}}, {{T41}}, {{T42}}<br />
* [[ATI Mobility Radeon 9600]]<br />
** {{T42}}<br />
* [[ATI Mobility Radeon X300]]<br />
** {{R52}}<br />
** {{T43}}<br />
** {{Z60m}}<br />
* [[ATI Mobility Radeon Xpress 200M]]<br />
** {{R51e}}<br />
* [[ATI Mobility Radeon X600]]<br />
** {{Z60m}}<br />
* [[ATI Mobility Radeon X1400]]<br />
** {{T60}}, {{R60}}, {{Z61m}}<br />
* [[ATI Mobility FireGL V5200]]<br />
** {{T60p}}, {{Z61p}}<br />
<br />
== ThinkPads that are NOT supported by fglrx==<br />
Unsupported chips, as found in select IBM ThinkPads:<br />
* [[ATI Mobility Radeon 7500]]<br />
** {{R40}}<br />
** {{T30}}<br />
** {{T42}}<br />
<br />
{{footnotes|<br />
#Note that glxgears isn't a benchmark tool, it's so simple that its FPS values is without any meaning... you can only compare glxgears using the same drivers/machine, if you change any of then you can have higher/lower values and in real life programs/games happen to have the opposite effects. Think in terms of a car engines rpms: higher rpms in the same car usually means a faster car, change anything and it's meaningless, ie: gears, truck, wheel size, etc. make it useless.<br />
}}<br />
[[Category:Drivers]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installing_Fedora_7_on_a_ThinkPad_T60&diff=30508Installing Fedora 7 on a ThinkPad T602007-06-15T23:20:57Z<p>Pfps: /* ATI Mobility Radeon X1300 (M52) & X1400 (M54) */</p>
<hr />
<div>Created by: [[User:spot|TomCallaway]] 09:45, March 20, 2007<br />
<br />
===Abstract===<br />
<br />
This article describes how I got Fedora 7 installed on my IBM/Lenovo ThinkPad T60. Now, I know that Fedora 7 isn't out yet, so this information is specific to the test releases. When Fedora 7 comes out, I'll update this page to reflect any changes.<br />
<br />
===My ThinkPad===<br />
<br />
These are the specifications of my machine. <br />
<br />
* Lenovo ThinkPad T60 (6369-CTO)<br />
* [[Intel Core 2 Duo (Merom)]] T7200 @ 2.00GHz<br />
* [[Intel Graphics Media Accelerator 950]]<br />
* [[Ethernet Controllers#Intel Gigabit (10/100/1000)|Intel Gigabit Ethernet Controller]]<br />
* [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]<br />
* Integrated Bluetooth.<br />
* [[Integrated Fingerprint Reader]]<br />
* 100 GB - Serial ATA-150 Hard Drive.<br />
* 15.4" TFT display with 1680x1050 resolution (widescreen)<br />
* Intel 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
<br />
===What Works?===<br />
<br />
* Fedora<br />
* Most of the function keys, except the ones mentioned below<br />
* The fingerprint reader.<br />
* Video, 2D and 3D.<br />
* Brightness, Volume and Mute with OSD (On-Screen Display).<br />
* ThinkLight, TrackPoint II and the touchpad.<br />
* Bluetooth<br />
* Infrared<br />
* Suspend<br />
<br />
===What Doesn't Work? (Known Issues)===<br />
<br />
* Modem<br />
* Hibernate<br />
<br />
===Kernel Drivers===<br />
<br />
The laptop uses the following hardware specific kernel drivers:<br />
<br />
* iwlwifi (wireless)<br />
* e1000 (ethernet)<br />
* snd_hda_intel (sound)<br />
* nsc_ircc (infrared)<br />
<br />
===Installing Fedora===<br />
<br />
I really have no interest in dual-booting my laptop. There are plenty of good guides to setting up a computer for dual-boot on the internet. I burned a copy of the FC 6.91 DVD iso, booted off of it, and told the installer to delete all existing partitions. The install went off without a hitch. After installation, I ran yum update, and rebooted into the new kernel.<br />
<br />
===Post Install===<br />
The Fedora repositories have some useful packages for ThinkPads. After I installed the OS, I used yum to install the following packages:<br />
<br />
* thinkfinger: Support for the Fingerprint Reader<br />
* tpb: ThinkPad button support utility and onscreen display<br />
* beryl-gnome: Eyecandy!<br />
* iwlwifi-firmware: The firmware for the new intel wireless driver<br />
* xbindkeys: A utility to help us bind the "special" thinkpad keys<br />
* xorg-x11-drv-i810: Driver for the Intel Graphics Chipsets<br />
<br />
===Wireless LAN===<br />
The latest Fedora 7 kernels include a new driver for the Intel 3945 chipset, called iwlwifi. This driver works, but it is a bit new, so you must be patient with it. If you didn't install the iwlwifi-firmware package, do so now. The kernel should have detected the wireless device, and configured iwlwifi for you.<br />
<br />
Step 1: Turn on the radio<br />
Make sure the switch on the front is pushed to the right (you should be able to see green on the left). Then, as root, run:<br />
<br />
: {{cmdroot| /sbin/ifconfig wlan0 up}}<br />
<br />
Step 2: Scan for access points<br />
Even if you know the ESSID, the iwlwifi driver needs to also be told the frequency and access point that you want to connect to. Hopefully, this will be fixed in a later revision of the driver.<br />
<br />
As root, run:<br />
: {{cmdroot| /sbin/iwlist wlan0 scanning}}<br />
<br />
You should see something like:<br />
<br />
<pre><br />
Cell 03 - Address: 00:01:02:03:04:05<br />
ESSID:"freewifi"<br />
Mode:Master<br />
Frequency:2.462 GHz<br />
Signal level=-80 dBm <br />
Encryption key:on<br />
Extra:tsf=000000deadb33fabc<br />
Extra:bcn_int=100<br />
Extra:rssi=-80<br />
Extra:capab=0x0411<br />
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s<br />
</pre><br />
<br />
Assuming that's the AP we want to connect to, note the Frequency, Address, and ESSID.<br />
<br />
Step 3: Tell wlan0 about our AP<br />
Now, we just need to configure wlan0 to find our AP:<br />
As root, run:<br />
<br />
: {{cmdroot| /sbin/iwconfig wlan0 freq 2.462G}}<br />
: {{cmdroot| /sbin/iwconfig wlan0 ap 00:01:02:03:04:05}}<br />
: {{cmdroot| /sbin/iwconfig wlan0 essid "freewifi"}}<br />
<br />
Step 4: Get an IP Address<br />
Assuming the wireless network is DHCP, as root, run:<br />
<br />
: {{cmdroot| /sbin/dhclient wlan0}}<br />
<br />
Now your wireless is up and running!<br />
(Note: Your mileage may vary. There are lots of bug reports against iwlwifi. Maybe it is only a problem with NetworkManager, but my experience is that Fedora 7 test 4 (6.93) has unworkable wifi out of the box, at least on a T60p with an ipw3945.)<br />
As of 15 June 2007, NetworkManager still doesn't work very well with the iwlwifi device.<br />
There is a discussion on this on the fedora test list, starting with<br />
https://www.redhat.com/archives/fedora-test-list/2007-April/msg00539.html<br />
<br />
===Bluetooth===<br />
Bluetooth works out of the box, but Gnome GUI only provides limited functionality (like Obex file transfers).<br />
To configure bluetooth serial ports (those are used to connect to internet via Your bluetooth enabled mobile phone, to use bluetooth GPS devices etc), You have to manually tweak {{path|/etc/bluetooth/rfcomm.conf}} file.<br />
<br />
At first run:<br />
: {{cmduser| hcitool scan}}<br />
<br />
The output should be something like<br />
<pre><br />
Scanning ...<br />
00:0A:D9:ED:89:4E Anttix P900<br />
</pre><br />
<br />
Note the MAC address of Your phone, then run:<br />
: {{cmduser| sdptool browse MAC_ADDRESS_OF_YOUR_PHONE}}<br />
<br />
Find modem channel by looking for an entry like this:<br />
<pre><br />
Service Name: Dial-up Networking<br />
Service Description: Dial-up Networking<br />
Service Provider: Sony Ericsson<br />
Service RecHandle: 0x10001<br />
Service Class ID List:<br />
"Dialup Networking" (0x1103)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 7<br />
Language Base Attr List:<br />
code_ISO639: 0x656e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"Dialup Networking" (0x1103)<br />
Version: 0x0100<br />
</pre><br />
<br />
Now edit {{path|/etc/bluetooth/rfcomm.conf}}.<br />
Uncomment the lines for rfcomm0 and replace MAC and channel numbers with the ones from Your phone.<br />
Also make sure to turn on automatic binding on startup.<br />
The final config will look like this:<br />
<pre><br />
rfcomm0 {<br />
# Automatically bind the device at startup<br />
bind yes;<br />
<br />
# Bluetooth address of the device<br />
device 00:0A:D9:ED:89:4E;<br />
<br />
# RFCOMM channel for the connection<br />
channel 7;<br />
<br />
# Description of the connection<br />
comment "My GSM Dialup Networking";<br />
}<br />
</pre><br />
<br />
Restart bluetooth subsystem:<br />
<br />
{{cmdroot|service bluetooth restart}}<br />
<br />
Now run network configuration tool, add a new modem to device {{path|/dev/rfcomm0}} and configure an internet connection as usual. The phone number depends on Your phone make, but most of the time it's <code>*99#</code>. You might also need to add additional modem initialization string <code>AT+cgdcont=1,"IP","internet",,0,0</code> to configure Your GPRS service name.<br />
<br />
Make sure that Gnome bluetooth applet is running. If not, run it by typing bluetooth-applet.<br />
<br />
Activate the connection. You should be prompted for PIN by both: the phone and the applet. Enter the same number on both sides to pair the connection.<br />
<br />
===Infrared===<br />
T60 has an NSC FIR chip. The driver needs to know a Dongle ID so it must be manually configured.<br />
<br />
Edit {{path|/etc/modprobe.conf}}, add the following two lines:<br />
<pre><br />
alias irda0 nsc-ircc<br />
options nsc-ircc dongle_id=0x09<br />
</pre><br />
<br />
Edit {{path|/etc/sysconfig/irda}}:<br />
<pre><br />
IRDA=yes<br />
DEVICE=irda0<br />
DISCOVERY=yes<br />
</pre><br />
<br />
Start IRDA<br />
<br />
{{cmdroot|service irda start}}<br />
<br />
If You want IRDA to be enabled during system boot, turn it on like this:<br />
<br />
{{cmdroot|chkconfig irda on}}<br />
<br />
===Getting the ThinkVantage Buttons to work===<br />
<br />
Fedora does not recognize all the ThinkVantage buttons correctly by default. This can be fixed quite easily. Just edit /etc/X11/Xmodmap.<br />
<br />
Then paste the following in the file:<br />
<br />
<pre><br />
keycode 234 = XF86Back<br />
keycode 233 = XF86Forward<br />
keycode 159 = XF86Start<br />
keycode 162 = XF86AudioPlay<br />
keycode 164 = XF86AudioStop<br />
keycode 153 = XF86AudioNext<br />
keycode 144 = XF86AudioPrev<br />
keycode 227 = XF86LaunchF<br />
keycode 249 = XF86ZoomIn<br />
</pre><br />
<br />
Save and close the file, then logout and back in again. You can now assign the buttons to do anything you want. For example, use the Back and Forward buttons (next the cursor keys) to flip desktops using the cube effect in Beryl (set this using the Beryl settings manager). You can set most of the other keys using Gnome vis System - Preferences - Keyboard Shortcuts.<br />
<br />
For the ThinkVantage and Zoom buttons, I used xbindkeys. Open a terminal and type:<br />
<br />
: {{cmduser| xbindkeys --defaults > ~/.xbindkeysrc}}<br />
: {{cmduser| xbindkeys-config}}<br />
<br />
Click "New" and assign a remark to the new shortcut. Then press "Grab" and press the combination you want (ex: The ThinkVantage button). You can then set the action you want executed in the "Action" field. <br />
<br />
=== Video Drivers ===<br />
<br />
====Intel Graphics Media Accelerator 950 (GMA950)====<br />
Since the Fedora installer didn't detect the graphics device properly, it uses the Vesa driver. Which works, but that's not really what we want to use. After installing the xorg-x11-drv-i810 package, I edited the /etc/X11/xorg.conf, and changed the driver from "vesa" to "intel". Then, restart X. That's it.<br />
<br />
====ATI Mobility Radeon X1300 (M52) & X1400 (M54)====<br />
At this moment, ATI's drivers do not work with Fedora 7 because they can't handle the xorg version there. A fix might be available sometime in June 2007.<br />
<br />
===The Fingerprint Reader===<br />
<br />
Thanks to the efforts of the ThinkFinger guys, the fingerprint reader works very well in Linux using entirely Free Software. After installing thinkfinger, you need to edit /etc/pam.d/system-auth as root (be careful!):<br />
<br />
Above the line that reads:<br />
<br />
<pre><br />
auth sufficient pam_unix.so nullok try_first_pass<br />
</pre><br />
<br />
Add a new line that reads:<br />
<br />
<pre><br />
auth sufficient pam_thinkfinger.so<br />
</pre><br />
<br />
So, the auth section of your /etc/pam.d/system-auth file should look like:<br />
<br />
<pre><br />
auth required pam_env.so<br />
auth sufficient pam_thinkfinger.so<br />
auth sufficient pam_unix.so nullok try_first_pass<br />
auth requisite pam_succeed_if.so uid >= 500 quiet<br />
auth required pam_deny.so<br />
</pre><br />
<br />
Save the updated /etc/pam.d/system-auth, then as root, run:<br />
<br />
: {{cmdroot| /usr/sbin/tf-tool --add-user spot}}<br />
<br />
Of course, if your username isn't spot, change it! It will prompt you to swipe your finger over the reader three times.<br />
<br />
Thats it! Now, you can login using either a password or a fingerprint.<br />
<br />
===Beryl - eyecandy===<br />
Beryl is shiny desktop eyecandy. To get it running, you can follow the steps here:<br />
http://wiki.beryl-project.org/wiki/Install/Fedora_Core<br />
<br />
===Suspend===<br />
Create a new file {{path|/etc/rc.modules}} and put the following lines into it:<br />
<pre><br />
# Turn on correct suspend flags for T60<br />
echo 3 > /proc/sys/kernel/acpi_video_flags<br />
</pre><br />
Then make it executable:<br />
<br />
{{cmdroot|chmod 755 /etc/rc.modules}}<br />
<br />
After reboot the machine should suspend and wake up fine.<br />
<br />
===Thanks===<br />
Much credit goes to [[User:Keithvassallo|Keithvassallo]] for his [http://thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60 Installing Ubuntu Edgy Eft on the Thinkpad T60] page.<br />
<br />
[[Category:T Series]]<br />
[[Category:Fedora]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installing_Fedora_7_on_a_ThinkPad_T60&diff=30507Installing Fedora 7 on a ThinkPad T602007-06-15T23:19:40Z<p>Pfps: /* Wireless LAN */</p>
<hr />
<div>Created by: [[User:spot|TomCallaway]] 09:45, March 20, 2007<br />
<br />
===Abstract===<br />
<br />
This article describes how I got Fedora 7 installed on my IBM/Lenovo ThinkPad T60. Now, I know that Fedora 7 isn't out yet, so this information is specific to the test releases. When Fedora 7 comes out, I'll update this page to reflect any changes.<br />
<br />
===My ThinkPad===<br />
<br />
These are the specifications of my machine. <br />
<br />
* Lenovo ThinkPad T60 (6369-CTO)<br />
* [[Intel Core 2 Duo (Merom)]] T7200 @ 2.00GHz<br />
* [[Intel Graphics Media Accelerator 950]]<br />
* [[Ethernet Controllers#Intel Gigabit (10/100/1000)|Intel Gigabit Ethernet Controller]]<br />
* [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]<br />
* Integrated Bluetooth.<br />
* [[Integrated Fingerprint Reader]]<br />
* 100 GB - Serial ATA-150 Hard Drive.<br />
* 15.4" TFT display with 1680x1050 resolution (widescreen)<br />
* Intel 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
<br />
===What Works?===<br />
<br />
* Fedora<br />
* Most of the function keys, except the ones mentioned below<br />
* The fingerprint reader.<br />
* Video, 2D and 3D.<br />
* Brightness, Volume and Mute with OSD (On-Screen Display).<br />
* ThinkLight, TrackPoint II and the touchpad.<br />
* Bluetooth<br />
* Infrared<br />
* Suspend<br />
<br />
===What Doesn't Work? (Known Issues)===<br />
<br />
* Modem<br />
* Hibernate<br />
<br />
===Kernel Drivers===<br />
<br />
The laptop uses the following hardware specific kernel drivers:<br />
<br />
* iwlwifi (wireless)<br />
* e1000 (ethernet)<br />
* snd_hda_intel (sound)<br />
* nsc_ircc (infrared)<br />
<br />
===Installing Fedora===<br />
<br />
I really have no interest in dual-booting my laptop. There are plenty of good guides to setting up a computer for dual-boot on the internet. I burned a copy of the FC 6.91 DVD iso, booted off of it, and told the installer to delete all existing partitions. The install went off without a hitch. After installation, I ran yum update, and rebooted into the new kernel.<br />
<br />
===Post Install===<br />
The Fedora repositories have some useful packages for ThinkPads. After I installed the OS, I used yum to install the following packages:<br />
<br />
* thinkfinger: Support for the Fingerprint Reader<br />
* tpb: ThinkPad button support utility and onscreen display<br />
* beryl-gnome: Eyecandy!<br />
* iwlwifi-firmware: The firmware for the new intel wireless driver<br />
* xbindkeys: A utility to help us bind the "special" thinkpad keys<br />
* xorg-x11-drv-i810: Driver for the Intel Graphics Chipsets<br />
<br />
===Wireless LAN===<br />
The latest Fedora 7 kernels include a new driver for the Intel 3945 chipset, called iwlwifi. This driver works, but it is a bit new, so you must be patient with it. If you didn't install the iwlwifi-firmware package, do so now. The kernel should have detected the wireless device, and configured iwlwifi for you.<br />
<br />
Step 1: Turn on the radio<br />
Make sure the switch on the front is pushed to the right (you should be able to see green on the left). Then, as root, run:<br />
<br />
: {{cmdroot| /sbin/ifconfig wlan0 up}}<br />
<br />
Step 2: Scan for access points<br />
Even if you know the ESSID, the iwlwifi driver needs to also be told the frequency and access point that you want to connect to. Hopefully, this will be fixed in a later revision of the driver.<br />
<br />
As root, run:<br />
: {{cmdroot| /sbin/iwlist wlan0 scanning}}<br />
<br />
You should see something like:<br />
<br />
<pre><br />
Cell 03 - Address: 00:01:02:03:04:05<br />
ESSID:"freewifi"<br />
Mode:Master<br />
Frequency:2.462 GHz<br />
Signal level=-80 dBm <br />
Encryption key:on<br />
Extra:tsf=000000deadb33fabc<br />
Extra:bcn_int=100<br />
Extra:rssi=-80<br />
Extra:capab=0x0411<br />
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s<br />
</pre><br />
<br />
Assuming that's the AP we want to connect to, note the Frequency, Address, and ESSID.<br />
<br />
Step 3: Tell wlan0 about our AP<br />
Now, we just need to configure wlan0 to find our AP:<br />
As root, run:<br />
<br />
: {{cmdroot| /sbin/iwconfig wlan0 freq 2.462G}}<br />
: {{cmdroot| /sbin/iwconfig wlan0 ap 00:01:02:03:04:05}}<br />
: {{cmdroot| /sbin/iwconfig wlan0 essid "freewifi"}}<br />
<br />
Step 4: Get an IP Address<br />
Assuming the wireless network is DHCP, as root, run:<br />
<br />
: {{cmdroot| /sbin/dhclient wlan0}}<br />
<br />
Now your wireless is up and running!<br />
(Note: Your mileage may vary. There are lots of bug reports against iwlwifi. Maybe it is only a problem with NetworkManager, but my experience is that Fedora 7 test 4 (6.93) has unworkable wifi out of the box, at least on a T60p with an ipw3945.)<br />
As of 15 June 2007, NetworkManager still doesn't work very well with the iwlwifi device.<br />
There is a discussion on this on the fedora test list, starting with<br />
https://www.redhat.com/archives/fedora-test-list/2007-April/msg00539.html<br />
<br />
===Bluetooth===<br />
Bluetooth works out of the box, but Gnome GUI only provides limited functionality (like Obex file transfers).<br />
To configure bluetooth serial ports (those are used to connect to internet via Your bluetooth enabled mobile phone, to use bluetooth GPS devices etc), You have to manually tweak {{path|/etc/bluetooth/rfcomm.conf}} file.<br />
<br />
At first run:<br />
: {{cmduser| hcitool scan}}<br />
<br />
The output should be something like<br />
<pre><br />
Scanning ...<br />
00:0A:D9:ED:89:4E Anttix P900<br />
</pre><br />
<br />
Note the MAC address of Your phone, then run:<br />
: {{cmduser| sdptool browse MAC_ADDRESS_OF_YOUR_PHONE}}<br />
<br />
Find modem channel by looking for an entry like this:<br />
<pre><br />
Service Name: Dial-up Networking<br />
Service Description: Dial-up Networking<br />
Service Provider: Sony Ericsson<br />
Service RecHandle: 0x10001<br />
Service Class ID List:<br />
"Dialup Networking" (0x1103)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 7<br />
Language Base Attr List:<br />
code_ISO639: 0x656e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"Dialup Networking" (0x1103)<br />
Version: 0x0100<br />
</pre><br />
<br />
Now edit {{path|/etc/bluetooth/rfcomm.conf}}.<br />
Uncomment the lines for rfcomm0 and replace MAC and channel numbers with the ones from Your phone.<br />
Also make sure to turn on automatic binding on startup.<br />
The final config will look like this:<br />
<pre><br />
rfcomm0 {<br />
# Automatically bind the device at startup<br />
bind yes;<br />
<br />
# Bluetooth address of the device<br />
device 00:0A:D9:ED:89:4E;<br />
<br />
# RFCOMM channel for the connection<br />
channel 7;<br />
<br />
# Description of the connection<br />
comment "My GSM Dialup Networking";<br />
}<br />
</pre><br />
<br />
Restart bluetooth subsystem:<br />
<br />
{{cmdroot|service bluetooth restart}}<br />
<br />
Now run network configuration tool, add a new modem to device {{path|/dev/rfcomm0}} and configure an internet connection as usual. The phone number depends on Your phone make, but most of the time it's <code>*99#</code>. You might also need to add additional modem initialization string <code>AT+cgdcont=1,"IP","internet",,0,0</code> to configure Your GPRS service name.<br />
<br />
Make sure that Gnome bluetooth applet is running. If not, run it by typing bluetooth-applet.<br />
<br />
Activate the connection. You should be prompted for PIN by both: the phone and the applet. Enter the same number on both sides to pair the connection.<br />
<br />
===Infrared===<br />
T60 has an NSC FIR chip. The driver needs to know a Dongle ID so it must be manually configured.<br />
<br />
Edit {{path|/etc/modprobe.conf}}, add the following two lines:<br />
<pre><br />
alias irda0 nsc-ircc<br />
options nsc-ircc dongle_id=0x09<br />
</pre><br />
<br />
Edit {{path|/etc/sysconfig/irda}}:<br />
<pre><br />
IRDA=yes<br />
DEVICE=irda0<br />
DISCOVERY=yes<br />
</pre><br />
<br />
Start IRDA<br />
<br />
{{cmdroot|service irda start}}<br />
<br />
If You want IRDA to be enabled during system boot, turn it on like this:<br />
<br />
{{cmdroot|chkconfig irda on}}<br />
<br />
===Getting the ThinkVantage Buttons to work===<br />
<br />
Fedora does not recognize all the ThinkVantage buttons correctly by default. This can be fixed quite easily. Just edit /etc/X11/Xmodmap.<br />
<br />
Then paste the following in the file:<br />
<br />
<pre><br />
keycode 234 = XF86Back<br />
keycode 233 = XF86Forward<br />
keycode 159 = XF86Start<br />
keycode 162 = XF86AudioPlay<br />
keycode 164 = XF86AudioStop<br />
keycode 153 = XF86AudioNext<br />
keycode 144 = XF86AudioPrev<br />
keycode 227 = XF86LaunchF<br />
keycode 249 = XF86ZoomIn<br />
</pre><br />
<br />
Save and close the file, then logout and back in again. You can now assign the buttons to do anything you want. For example, use the Back and Forward buttons (next the cursor keys) to flip desktops using the cube effect in Beryl (set this using the Beryl settings manager). You can set most of the other keys using Gnome vis System - Preferences - Keyboard Shortcuts.<br />
<br />
For the ThinkVantage and Zoom buttons, I used xbindkeys. Open a terminal and type:<br />
<br />
: {{cmduser| xbindkeys --defaults > ~/.xbindkeysrc}}<br />
: {{cmduser| xbindkeys-config}}<br />
<br />
Click "New" and assign a remark to the new shortcut. Then press "Grab" and press the combination you want (ex: The ThinkVantage button). You can then set the action you want executed in the "Action" field. <br />
<br />
=== Video Drivers ===<br />
<br />
====Intel Graphics Media Accelerator 950 (GMA950)====<br />
Since the Fedora installer didn't detect the graphics device properly, it uses the Vesa driver. Which works, but that's not really what we want to use. After installing the xorg-x11-drv-i810 package, I edited the /etc/X11/xorg.conf, and changed the driver from "vesa" to "intel". Then, restart X. That's it.<br />
<br />
====ATI Mobility Radeon X1300 (M52) & X1400 (M54)====<br />
At this moment, ATI's drivers do not work with Fedora 7. --[[User:Whizkid|Whizkid]] 18:21, 6 June 2007 (UTC)<br />
<br />
===The Fingerprint Reader===<br />
<br />
Thanks to the efforts of the ThinkFinger guys, the fingerprint reader works very well in Linux using entirely Free Software. After installing thinkfinger, you need to edit /etc/pam.d/system-auth as root (be careful!):<br />
<br />
Above the line that reads:<br />
<br />
<pre><br />
auth sufficient pam_unix.so nullok try_first_pass<br />
</pre><br />
<br />
Add a new line that reads:<br />
<br />
<pre><br />
auth sufficient pam_thinkfinger.so<br />
</pre><br />
<br />
So, the auth section of your /etc/pam.d/system-auth file should look like:<br />
<br />
<pre><br />
auth required pam_env.so<br />
auth sufficient pam_thinkfinger.so<br />
auth sufficient pam_unix.so nullok try_first_pass<br />
auth requisite pam_succeed_if.so uid >= 500 quiet<br />
auth required pam_deny.so<br />
</pre><br />
<br />
Save the updated /etc/pam.d/system-auth, then as root, run:<br />
<br />
: {{cmdroot| /usr/sbin/tf-tool --add-user spot}}<br />
<br />
Of course, if your username isn't spot, change it! It will prompt you to swipe your finger over the reader three times.<br />
<br />
Thats it! Now, you can login using either a password or a fingerprint.<br />
<br />
===Beryl - eyecandy===<br />
Beryl is shiny desktop eyecandy. To get it running, you can follow the steps here:<br />
http://wiki.beryl-project.org/wiki/Install/Fedora_Core<br />
<br />
===Suspend===<br />
Create a new file {{path|/etc/rc.modules}} and put the following lines into it:<br />
<pre><br />
# Turn on correct suspend flags for T60<br />
echo 3 > /proc/sys/kernel/acpi_video_flags<br />
</pre><br />
Then make it executable:<br />
<br />
{{cmdroot|chmod 755 /etc/rc.modules}}<br />
<br />
After reboot the machine should suspend and wake up fine.<br />
<br />
===Thanks===<br />
Much credit goes to [[User:Keithvassallo|Keithvassallo]] for his [http://thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60 Installing Ubuntu Edgy Eft on the Thinkpad T60] page.<br />
<br />
[[Category:T Series]]<br />
[[Category:Fedora]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=30506Fglrx2007-06-15T23:17:01Z<p>Pfps: /* Packages */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
== ATI fglrx driver ==<br />
This is a proprietary Linux binary-only driver for ATI graphic chips with support for 3D acceleration.<br />
<br />
Also see [[R300|opensource driver]] with 3D support<br />
|}<br />
<br />
==Availability / Project Homepage==<br />
Home page: http://ati.amd.com/support/drivers/linux/linux-radeon.html<br />
<br />
== Packages ==<br />
The ATI drivers have explicit permission for repackaging and redistribution of the Linux drivers. Many distributions are supported within the installer, and many more repackaged by external developers. Please visit the [http://wiki.cchtml.com/index.php/Category:Distributions Distribution Page at the Unofficial ATI driver Wiki]<br />
<br />
*{{Debian}} packages: http://www.stanchina.net/~flavio/debian-official/fglrx-driver.html<br />
** These packages have been added to Debian unstable as <tt>fglrx-driver</tt>, so you can now apt-get them and use module-assistant to install.<br />
** If you are on stable sarge with backport's kernel 2.6.15, download ATI's installer, let it build Debian packages and proceed as usual. There's a [http://jroller.com/page/erAck?entry=lot_day_6_2_fglrx detailed description] available.<br />
*{{SUSE}} packages: http://www.suse.de/~sndirsch/ati-installer-HOWTO.html<br />
*{{Gentoo}} {{cmdroot|emerge ati-drivers}}<br />
*{{Fedora}} 4 packages: http://rpm.livna.org<br />
** For stock Fedora kernels: {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}<br />
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]<br />
*{{Fedora}} 5 packages: http://rpm.livna.org<br />
** For stock Fedora kernels: {{cmdroot|yum install xorg-x11-drv-fglrx}}<br />
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]<br />
*{{Fedora}} 7 packages: http://rpm.livna.org<br />
** Unfortunately, as of 15 June, the fglrx driver does not work with Fedora 7, as it cannot handle the xorg version there. A new driver is expected sometime fairly soon.<br />
*{{Arch Linux}}<br />
:{{cmdroot|pacman -S ati-fglrx}} (kernel module for 2.6.15-ARCH)<br />
:{{cmdroot|pacman -S ati-fglrx-archck}} (kernel module for 2.6.15-archck)<br />
:{{cmdroot|pacman -S ati-fglrx-utils}} (xorg7 stuff and tools)<br />
*{{Ubuntu}}<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide Dapper Drake Howto]<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Breezy_Installation_Guide Breezy Badger Howto]<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Edgy_Installation_Guide Edgy Eft Howto]<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide Feisty Fawn Howto]<br />
<br />
== Building for Xorg 7.0==<br />
To compile fglrx versions <= 8.24.8 for Xorg 7.0.0, fake Xorg 6.9.0 by <br />
:{{cmdroot|1=export X_VERSION=x690; sh ati-driver-installer-8.24.8-x86.run}}<br />
Next, move the various resulting libraries and modules from /usr/X11R6 to /usr/lib/xorg<br />
<br />
In {{path|/usr/src/ATI}} additional sources are installed for fireglcontrol and fgl_glxgears<br />
<br />
== Status ==<br />
Current version: 8.37.6 (31st May 2007).<br />
Major changes:<br />
* 8.37.6: Xorg Server 1.3 support, CCC 1.0, crash when logging off from X fixed, Xv cropping bug fixed<br />
* 8.36.5: Kernel 2.6.20 support, CCC Beta 0.9 with localization<br />
* 8.35.5: Beta AMD Catalyst Control Center, X-Server termination from console does not result in a blank screen. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.35.5|fglrx patches section]]).<br />
* 8.34.8: Radeon Xpress 1250 support, X-Video on x86_64 fix, hibernation mode fix. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.34.8|fglrx patches section]]).<br />
* 8.33.6: X.Org 7.2 support, kernel 2.6.19 support, some fixes in the installer, 2 more bugfixes. Resume from suspend works if you make sure you have set "VbetoolPost no" and "EnableVbetool no" in your suspend to ram hibernate conf (/etc/hibernate/ram.conf on ubuntu/debian).<br />
* 8.32.5: support for X1650, X.Org 7.2 RC2 support, bugfixes. Suspend-to-ram is broken with specific cards, *no* 2.6.19 support (see [[Problems_with_fglrx#fglrx_8.32.5|fglrx patches section]]).<br />
* 8.31.5: no new features, only bugfixes. Of note, for some users, this version breaks suspend-to-ram and suspend-to-disk.<br />
* 8.30.3: no new features, only bugfixes<br />
* 8.29.6: Linux 2.6.18 support, dropped support for Radeon 8500/9000/9100/9200/9250 (both, mobile and normal versions)<br />
* 8.28.8: Display Switching Support for ThinkPads, ATI Pairmode support, Retaining display device state between restarts, Support for Radeon Xpress 1200, 1250, and 1300<br />
* 8.27.10: X.org 7.1 support, Fedora Core package support<br />
* 8.26.18: support for dynamically attached DFPs and Thermal Event Power Management (both via daemon), minor bug fixes<br />
* 8.25.18: Xorg 7.0 support, FireGLâ„¢V5xxx/V7xxx support, Dynamic Display Management, fixed a lot of critical bugs.<br />
* 8.24.8: support for X1300, X1400, X1600, X1800 (generic and mobility) and 3D accelerated video playback on Avivo<br />
* 8.23.7: support for X850 and X800, OpenGL 2.0 Enhancement, FSAA for some chips<br />
* 8.22.5: added kernel 2.6.15 support -- patch no longer required<br />
* 8.21.7: initial OpenGL 2.0 support<br />
* 8.20.8: fixed resume issues, fixed compile problems with kernels 2.6.13 and 2.6.14<br />
* 8.19.10: has added suspend / resume and dynamic GPU power management support. Using vbetool no longer required.<br />
<br />
== Known problems and solutions ==<br />
See [[Problems with fglrx]].<br />
== User experience ==<br />
=== Speed ===<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
Compared to the old drivers, approximately 40% speed gain have been noticed with fglrx. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (via {{key|ctrl}}{{key|alt}}{{key|plus}}, {{key|ctrl}}{{key|alt}}{{key|minus}}), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using the open source radeon driver: 1200 FPS for glxgears{{footnote|1}}!<br />
However the situation seems to be changing today. With recent x11-drm-20060608 driver (gentoo) and thinkpad t42 (ati 9600) the speed is confirmed as 1900fps without any single crash so far.<br />
<br />
=== 3D acceleration ===<br />
<br />
According to [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] you need these options:<br />
<br />
Section "Module"<br />
...<br />
Load "GLcore"<br />
Load "glx"<br />
Load "dri"<br />
...<br />
EndSection<br />
<br />
# Of course you need to activate the driver<br />
Section "Device"<br />
...<br />
Driver "fglrx"<br />
EndSection<br />
<br />
Don't forget to load the module <tt>fglrx</tt> (<tt>modprobe fglrx</tt>). Under Debian the module can be placed in <tt>/etc/modules</tt>.<br />
<br />
With current fglrx drivers (as of 8.29.6) you must disable composite to get 3D DRI acceleration. To do this, add an extra Extensions section (if necessary) containing:<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable" #make DRI work with fglrx.<br />
EndSection<br />
<br />
If you are unsure whether you have DRI running, issue <tt>glxinfo | grep -i direct</tt> after disabling composite. Note, this <br />
<br />
{{NOTE|1=Video overlay acceleration may be disabled when 3D acceleration is enabled. The following comment from the xorg.conf file bundled with the fglrx driver indicates that:<br />
# === OpenGL Overlay ===<br />
# Note: When OpenGL Overlay is enabled, Video Overlay<br />
# will be disabled automatically<br />
Option "OpenGLOverlay" "1"<br />
However, you can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. This has nothing to do with the acceleration of 2D drawing primitives. Further, your mileage on performance may vary depending on what card you have. The open source drivers don't support newer cards, while the ATI drivers don't support older cards.<br />
<br />
You may be able to preserve VideoOverlay acceleration if you explicitly remove the OpenGLOverlay using:<br />
<br />
Option "VideoOverlay" "True" and Option "OpenGLOverlay" "False". See [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] for detail.}}<br />
<br />
=== Power saving ===<br />
Power saving is much better than with the <tt>radeon</tt> driver, but doesn't work in dual-screen configuration (see [[How to make use of Graphics Chips Power Management features]]).<br />
<br />
=== Suspending with fglrx ===<br />
<br />
On a ThinkPad T42 with Kernel 2.6.19 with Software Suspend 2 and R60 with Kernel 2.6.18-suspend2-r1 (Gentoo) , the following addition to <tt>/etc/hibernate/suspend2.conf</tt> is required:<br />
<br />
# For fglrx<br />
ProcSetting extra_pages_allowance 20000<br />
<br />
=== Display Switching (Dynamic Display Management) ===<br />
<br />
Version 8.25.18 introduces a new feature: Dynamic Display Management. It allows display switching on-the-fly.<br />
<br />
To list all connected and enabled monitors:<br />
:{{cmdroot|1=aticonfig --query-monitor}}<br />
<br />
To switch displays:<br />
:{{cmdroot|1=aticonfig --enable-monitor=STRING,STRING}}, where STRING can be: none, lvds, crt1, crt2, tv, tdms1, tdms2<br />
<br />
Only 2 displays can be enabled at the same time. Any displays that are not on the list will be disabled.<br />
<br />
== Useful links == <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www.rage3d.com/content/articles/atilinuxhowto/ ATI Radeon Linux How-To]<br />
* [http://www.rage3d.com/board/forumdisplay.php?f=61&daysprune=30&order=asc&sort=title Rage3D Linux Discussion Forum]<br />
* [http://www.driverheaven.net/forumdisplay.php?f=103 Radeon Driver Forum at Driverheaven]<br />
* [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html Gentoo ATI Radeon FAQ]<br />
* [http://forums.gentoo.org/viewtopic-t-374745-highlight-t42+ati+dri.html Gentoo T42 ATI. DRI + xorg driver]<br />
* [http://ati.cchtml.com/ Unofficial community ATI bugzilla] - tracks bugs in the driver. Might be monitored by ATI ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]).<br />
<br />
== ThinkPads that may be supported ==<br />
Supported chips, as found in select IBM ThinkPads:<br />
{{NOTE|fglrx version 8.29.6 discontinued support for Radeon 9200 and earlier.}}<br />
* [[ATI Mobility FireGL 9000]]<br />
** {{T40p}}<br />
* [[ATI Mobility FireGL T2]]<br />
** {{R50p}}<br />
** {{T41p}}, {{T42p}}<br />
* [[ATI Mobility FireGL V3200]]<br />
** {{T43p}}<br />
* [[ATI Mobility Radeon 9000]]<br />
** {{R50}}, {{R51}}<br />
** {{T40}}, {{T41}}, {{T42}}<br />
* [[ATI Mobility Radeon 9600]]<br />
** {{T42}}<br />
* [[ATI Mobility Radeon X300]]<br />
** {{R52}}<br />
** {{T43}}<br />
** {{Z60m}}<br />
* [[ATI Mobility Radeon Xpress 200M]]<br />
** {{R51e}}<br />
* [[ATI Mobility Radeon X600]]<br />
** {{Z60m}}<br />
* [[ATI Mobility Radeon X1400]]<br />
** {{T60}}, {{R60}}, {{Z61m}}<br />
* [[ATI Mobility FireGL V5200]]<br />
** {{T60p}}, {{Z61p}}<br />
<br />
== ThinkPads that are NOT supported by fglrx==<br />
Unsupported chips, as found in select IBM ThinkPads:<br />
* [[ATI Mobility Radeon 7500]]<br />
** {{R40}}<br />
** {{T30}}<br />
** {{T42}}<br />
<br />
{{footnotes|<br />
#Note that glxgears isn't a benchmark tool, it's so simple that its FPS values is without any meaning... you can only compare glxgears using the same drivers/machine, if you change any of then you can have higher/lower values and in real life programs/games happen to have the opposite effects. Think in terms of a car engines rpms: higher rpms in the same car usually means a faster car, change anything and it's meaningless, ie: gears, truck, wheel size, etc. make it useless.<br />
}}<br />
[[Category:Drivers]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installing_Fedora_7_on_a_ThinkPad_T60&diff=29569Installing Fedora 7 on a ThinkPad T602007-04-30T21:36:59Z<p>Pfps: /* Wireless LAN */</p>
<hr />
<div>Created by: [[User:spot|TomCallaway]] 09:45, March 20, 2007<br />
<br />
===Abstract===<br />
<br />
This article describes how I got Fedora 7 installed on my IBM/Lenovo ThinkPad T60. Now, I know that Fedora 7 isn't out yet, so this information is specific to the test releases. When Fedora 7 comes out, I'll update this page to reflect any changes.<br />
<br />
===My ThinkPad===<br />
<br />
These are the specifications of my machine. <br />
<br />
* Lenovo ThinkPad T60 (6369-CTO)<br />
* [[Intel Core 2 Duo (Merom)]] T7200 @ 2.00GHz<br />
* [[Intel Graphics Media Accelerator 950]]<br />
* [[Ethernet Controllers#Intel Gigabit (10/100/1000)|Intel Gigabit Ethernet Controller]]<br />
* [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]<br />
* Integrated Bluetooth.<br />
* [[Integrated Fingerprint Reader]]<br />
* 100 GB - Serial ATA-150 Hard Drive.<br />
* 15.4" TFT display with 1680x1050 resolution (widescreen)<br />
* Intel 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
<br />
===What Works?===<br />
<br />
* Fedora<br />
* Most of the function keys, except the ones mentioned below<br />
* The fingerprint reader.<br />
* Video, 2D and 3D.<br />
* Brightness, Volume and Mute with OSD (On-Screen Display).<br />
* ThinkLight, TrackPoint II and the touchpad.<br />
* Bluetooth<br />
* Infrared<br />
* Suspend<br />
<br />
===What Doesn't Work? (Known Issues)===<br />
<br />
* Modem<br />
* Hibernate<br />
<br />
===Kernel Drivers===<br />
<br />
The laptop uses the following hardware specific kernel drivers:<br />
<br />
* iwlwifi (wireless)<br />
* e1000 (ethernet)<br />
* snd_hda_intel (sound)<br />
* nsc_ircc (infrared)<br />
<br />
===Installing Fedora===<br />
<br />
I really have no interest in dual-booting my laptop. There are plenty of good guides to setting up a computer for dual-boot on the internet. I burned a copy of the FC 6.91 DVD iso, booted off of it, and told the installer to delete all existing partitions. The install went off without a hitch. After installation, I ran yum update, and rebooted into the new kernel.<br />
<br />
===Post Install===<br />
The Fedora repositories have some useful packages for ThinkPads. After I installed the OS, I used yum to install the following packages:<br />
<br />
* thinkfinger: Support for the Fingerprint Reader<br />
* tpb: ThinkPad button support utility and onscreen display<br />
* beryl-gnome: Eyecandy!<br />
* iwlwifi-firmware: The firmware for the new intel wireless driver<br />
* xbindkeys: A utility to help us bind the "special" thinkpad keys<br />
* xorg-x11-drv-i810: Driver for the Intel Graphics Chipsets<br />
<br />
===Wireless LAN===<br />
The latest Fedora 7 kernels include a new driver for the Intel 3945 chipset, called iwlwifi. This driver works, but it is a bit new, so you must be patient with it. If you didn't install the iwlwifi-firmware package, do so now. The kernel should have detected the wireless device, and configured iwlwifi for you.<br />
<br />
Step 1: Turn on the radio<br />
Make sure the switch on the front is pushed to the right (you should be able to see green on the left). Then, as root, run:<br />
<br />
: {{cmdroot| /sbin/ifconfig wlan0 up}}<br />
<br />
Step 2: Scan for access points<br />
Even if you know the ESSID, the iwlwifi driver needs to also be told the frequency and access point that you want to connect to. Hopefully, this will be fixed in a later revision of the driver.<br />
<br />
As root, run:<br />
: {{cmdroot| /sbin/iwlist wlan0 scanning}}<br />
<br />
You should see something like:<br />
<br />
<pre><br />
Cell 03 - Address: 00:01:02:03:04:05<br />
ESSID:"freewifi"<br />
Mode:Master<br />
Frequency:2.462 GHz<br />
Signal level=-80 dBm <br />
Encryption key:on<br />
Extra:tsf=000000deadb33fabc<br />
Extra:bcn_int=100<br />
Extra:rssi=-80<br />
Extra:capab=0x0411<br />
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s<br />
</pre><br />
<br />
Assuming that's the AP we want to connect to, note the Frequency, Address, and ESSID.<br />
<br />
Step 3: Tell wlan0 about our AP<br />
Now, we just need to configure wlan0 to find our AP:<br />
As root, run:<br />
<br />
: {{cmdroot| /sbin/iwconfig wlan0 freq 2.462G}}<br />
: {{cmdroot| /sbin/iwconfig wlan0 ap 00:01:02:03:04:05}}<br />
: {{cmdroot| /sbin/iwconfig wlan0 essid "freewifi"}}<br />
<br />
Step 4: Get an IP Address<br />
Assuming the wireless network is DHCP, as root, run:<br />
<br />
: {{cmdroot| /sbin/dhclient wlan0}}<br />
<br />
Now your wireless is up and running!<br />
(Note: Your mileage may vary. There are lots of bug reports against iwlwifi. Maybe it is only a problem with NetworkManager, but my experience is that Fedora 7 test 4 (6.93) has unworkable wifi out of the box, at least on a T60p with an ipw3945.)<br />
<br />
Currently, NetworkManager doesn't work very well with the iwlwifi device.<br />
(This is a bit of an understatement - NetworkManager and iwlwifi together produce kernel oops and lots of other problems. There is a discussion on this on the fedora test list, starting with<br />
https://www.redhat.com/archives/fedora-test-list/2007-April/msg00539.html .)<br />
<br />
===Bluetooth===<br />
Bluetooth works out of the box, but Gnome GUI only provides limited functionality (like Obex file transfers).<br />
To configure bluetooth serial ports (those are used to connect to internet via Your bluetooth enabled mobile phone, to use bluetooth GPS devices etc), You have to manually tweak {{path|/etc/bluetooth/rfcomm.conf}} file.<br />
<br />
At first run:<br />
: {{cmduser| hcitool scan}}<br />
<br />
The output should be something like<br />
<pre><br />
Scanning ...<br />
00:0A:D9:ED:89:4E Anttix P900<br />
</pre><br />
<br />
Note the MAC address of Your phone, then run:<br />
: {{cmduser| sdptool browse MAC_ADDRESS_OF_YOUR_PHONE}}<br />
<br />
Find modem channel by looking for an entry like this:<br />
<pre><br />
Service Name: Dial-up Networking<br />
Service Description: Dial-up Networking<br />
Service Provider: Sony Ericsson<br />
Service RecHandle: 0x10001<br />
Service Class ID List:<br />
"Dialup Networking" (0x1103)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 7<br />
Language Base Attr List:<br />
code_ISO639: 0x656e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"Dialup Networking" (0x1103)<br />
Version: 0x0100<br />
</pre><br />
<br />
Now edit {{path|/etc/bluetooth/rfcomm.conf}}.<br />
Uncomment the lines for rfcomm0 and replace MAC and channel numbers with the ones from Your phone.<br />
Also make sure to turn on automatic binding on startup.<br />
The final config will look like this:<br />
<pre><br />
rfcomm0 {<br />
# Automatically bind the device at startup<br />
bind yes;<br />
<br />
# Bluetooth address of the device<br />
device 00:0A:D9:ED:89:4E;<br />
<br />
# RFCOMM channel for the connection<br />
channel 7;<br />
<br />
# Description of the connection<br />
comment "My GSM Dialup Networking";<br />
}<br />
</pre><br />
<br />
Restart bluetooth subsystem:<br />
<br />
{{cmdroot|service bluetooth restart}}<br />
<br />
Now run network configuration tool, add a new modem to device {{path|/dev/rfcomm0}} and configure an internet connection as usual. The phone number depends on Your phone make, but most of the time it's <code>*99#</code>. You might also need to add additional modem initialization string <code>AT+cgdcont=1,"IP","internet",,0,0</code> to configure Your GPRS service name.<br />
<br />
Make sure that Gnome bluetooth applet is running. If not, run it by typing bluetooth-applet.<br />
<br />
Activate the connection. You should be prompted for PIN by both: the phone and the applet. Enter the same number on both sides to pair the connection.<br />
<br />
===Infrared===<br />
T60 has an NSC FIR chip. The driver needs to know a Dongle ID so it must be manually configured.<br />
<br />
Edit {{path|/etc/modprobe.conf}}, add the following two lines:<br />
<pre><br />
alias irda0 nsc-ircc<br />
options nsc-ircc dongle_id=0x09<br />
</pre><br />
<br />
Edit {{path|/etc/sysconfig/irda}}:<br />
<pre><br />
IRDA=yes<br />
DEVICE=irda0<br />
DISCOVERY=yes<br />
</pre><br />
<br />
Start IRDA<br />
<br />
{{cmdroot|service irda start}}<br />
<br />
If You want IRDA to be enabled during system boot, turn it on like this:<br />
<br />
{{cmdroot|chkconfig irda on}}<br />
<br />
===Getting the ThinkVantage Buttons to work===<br />
<br />
Fedora does not recognize all the ThinkVantage buttons correctly by default. This can be fixed quite easily. Just edit /etc/X11/Xmodmap.<br />
<br />
Then paste the following in the file:<br />
<br />
<pre><br />
keycode 234 = XF86Back<br />
keycode 233 = XF86Forward<br />
keycode 159 = XF86Start<br />
keycode 162 = XF86AudioPlay<br />
keycode 164 = XF86AudioStop<br />
keycode 153 = XF86AudioNext<br />
keycode 144 = XF86AudioPrev<br />
keycode 227 = XF86LaunchF<br />
keycode 249 = XF86ZoomIn<br />
</pre><br />
<br />
Save and close the file, then logout and back in again. You can now assign the buttons to do anything you want. For example, use the Back and Forward buttons (next the cursor keys) to flip desktops using the cube effect in Beryl (set this using the Beryl settings manager). You can set most of the other keys using Gnome vis System - Preferences - Keyboard Shortcuts.<br />
<br />
For the ThinkVantage and Zoom buttons, I used xbindkeys. Open a terminal and type:<br />
<br />
: {{cmduser| xbindkeys --defaults > ~/.xbindkeysrc}}<br />
: {{cmduser| xbindkeys-config}}<br />
<br />
Click "New" and assign a remark to the new shortcut. Then press "Grab" and press the combination you want (ex: The ThinkVantage button). You can then set the action you want executed in the "Action" field. <br />
<br />
===The Intel Graphics Chipset===<br />
<br />
Since the Fedora installer didn't detect the graphics device properly, it uses the Vesa driver. Which works, but that's not really what we want to use. After installing the xorg-x11-drv-i810 package, I edited the /etc/X11/xorg.conf, and changed the driver from "vesa" to "intel". Then, restart X. That's it.<br />
<br />
===The Fingerprint Reader===<br />
<br />
Thanks to the efforts of the ThinkFinger guys, the fingerprint reader works very well in Linux using entirely Free Software. After installing thinkfinger, you need to edit /etc/pam.d/system-auth as root (be careful!):<br />
<br />
Above the line that reads:<br />
<br />
<pre><br />
auth sufficient pam_unix.so nullok try_first_pass<br />
</pre><br />
<br />
Add a new line that reads:<br />
<br />
<pre><br />
auth sufficient pam_thinkfinger.so<br />
</pre><br />
<br />
So, the auth section of your /etc/pam.d/system-auth file should look like:<br />
<br />
<pre><br />
auth required pam_env.so<br />
auth sufficient pam_thinkfinger.so<br />
auth sufficient pam_unix.so nullok try_first_pass<br />
auth requisite pam_succeed_if.so uid >= 500 quiet<br />
auth required pam_deny.so<br />
</pre><br />
<br />
Save the updated /etc/pam.d/system-auth, then as root, run:<br />
<br />
: {{cmdroot| /usr/sbin/tf-tool --add-user spot}}<br />
<br />
Of course, if your username isn't spot, change it! It will prompt you to swipe your finger over the reader three times.<br />
<br />
Thats it! Now, you can login using either a password or a fingerprint.<br />
<br />
===Beryl - eyecandy===<br />
Beryl is shiny desktop eyecandy. To get it running, you can follow the steps here:<br />
http://wiki.beryl-project.org/wiki/Install/Fedora_Core<br />
<br />
===Suspend===<br />
Create a new file {{path|/etc/rc.modules}} and put the following lines into it:<br />
<pre><br />
# Turn on correct suspend flags for T60<br />
echo 3 > /proc/sys/kernel/acpi_video_flags<br />
</pre><br />
Then make it executable:<br />
<br />
{{cmdroot|chmod 755 /etc/rc.modules}}<br />
<br />
After reboot the machine should suspend and wake up fine.<br />
<br />
===Thanks===<br />
Much credit goes to [[User:Keithvassallo|Keithvassallo]] for his [http://thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60 Installing Ubuntu Edgy Eft on the Thinkpad T60] page.<br />
<br />
[[Category:T Series]]<br />
[[Category:Fedora]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installing_Fedora_Core_6_on_a_ThinkPad_T60&diff=26981Installing Fedora Core 6 on a ThinkPad T602006-12-13T17:05:04Z<p>Pfps: </p>
<hr />
<div>== Installation ==<br />
<br />
Installation of Fedora Core 6 (Zod) on a Thinkpad T60 (2623). The installation completes successfully but installs the i586 kernel instead of the required i686 kernel. The wrong kernel is due to a [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211941 known bug] in the Anaconda installer.<br />
<br />
'''Note''' : At the time of this writing (Dec 1, 2006), the installer correctly installs the i686 kernel. Check your kernel version before you proceed. --[[User:Navinsamuel|Navinsamuel]] 22:20, 6 December 2006 (CET)<br />
<br />
== Works Out of the Box ==<br />
<br />
; Dual Cores (SMP processing)<br />
: As of Kernel 2.6.18, used in Fedora Core 6, there is no loger a single cpu and smp kernel image. SMP is now configured on-the-fly. FC6's kernel will automatically discover the T60's dual core cpu and bring up CPU0 and CPU1.<br />
<br />
; Wired Networking <br />
: Kernel recognizes eth0 and correctly loads the e1000 driver.<br />
<br />
; Video at 1400x1050<br />
: Fedora does not ship the proprietary ATi driver, as a reult the VESA driver is used. Installation of the ATi fgrlx driver is described later in this article.<br />
<br />
; Touchpad / Mouse<br />
: The TrackPoint middle button does not work as a scroll wheel by default.<br />
: PFPS: Note that although the touchpad and trackpoint work, Fedora Core 6 does a bad job of setting up xorg.conf. It is better to fix it up (see below).<br />
<br />
; Sound <br />
: The first-boot sound test fails to play the test sound. However, sound support is correctly configured and the snd-hda-intel driver is loaded at startup.<br />
<br />
; Suspend to RAM <br />
: Works out of the box under Gnome. Gnome power management intregrates with HAL (Linux's hardware abstraction layer) and DBUS, which correctly put this computer into a suspsend to RAM state and wake it up correctly.<br />
<br />
== Requires Tweaking == <br />
<br />
* Wireless Networking (Requires ipw3945 driver)<br />
* ATi OpenGL Direct Rendering<br />
* Hibernate<br />
* IrDA<br />
<br />
== Post Install ==<br />
<br />
=== Replacing the Kernel ===<br />
<br />
'''Note''' : The steps below will not be required if the i686 version is already installed by default, which would be the case if you downloaded Zod recently (as of Dec 1, 2006). --[[User:Navinsamuel|Navinsamuel]] 22:20, 6 December 2006 (CET)<br />
<br />
As previously mentioned, the i586 kernel is installed on this machine instead of the i686 version. The i686 version is required to install the ATI video drivers and Intel Wireless drivers required to get this machine 100% operational. It is best to do this first, before updating any packages.<br />
<br />
Installing the new kernel can be done by various methods as documented on the [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211941 Red Hat Bugzilla bug]. However, the safest method is to use [[yum]] to do the kernel swap.<br />
<br />
'''Note''' : If you have a multi-boot system, backup your Grub configuration file or atleast note it's contents elsewhere. If you don't, you can end up in a real mess! --[[User:Navinsamuel|Navinsamuel]] 22:20, 6 December 2006 (CET)<br />
<br />
To swap kernels:<br />
# Open up a terminal window are become root.<br />
# Execute: yum remove kernel<br />
# Make note of any other packages that will be removed due to dependency issues. The packages will have to be reinstalled in the next step.<br />
# Install the kernel.i686 package and any other packages removed in the previous step.<br />
# Fix your [[Grub]] configuration<br />
# Reboot<br />
<br />
On a minimal install, the only dependencies removed were gnome-session, compiz, gnome-volume-manager, and pcmciautils. Getting things back on track required:<br />
<br />
# yum install kernel.i686 gnome-session compiz gnome-volume-manager pcmciautils<br />
<br />
After [Yum] completes, you will have to fix the boot loader or you will be unable to boot after a restart.<br />
<br />
If you have '''not''' used Fedora's default installation using LVM partitions, you can use the following configuration for grub. As root, fire up your favorite text editor and add the following lines to your grub configuration (/boot/grub/grub.conf) just below the initial comments:<br />
<br />
<pre><br />
title FC6 2.6.18-1.2798<br />
kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=LABEL=/ rhgb quiet<br />
initrd /initrd-2.6.18-1.2798.fc6.img<br />
</pre><br />
<br />
If you have an LVM partition, use the method detailed at Redhat's site.<br />
<br />
=== Getting Up to Date ===<br />
<br />
Before completing installation, it's best to get up to date by running yum update as root or by using the new graphical updater, Pup, that ships with Fedora Core 6. After all updates are installed, reboot before continuing the post-install tasks.<br />
<br />
=== Setting Up Additional Repositories ===<br />
<br />
In order to get the ATI driver and the Intel Wireless working, you will need to add two repositories to your computer; [http://rpm.livna.org/ Livna RPMs] and [http://atrpms.net/ AT-RPMs].<br />
<br />
; Enabling Livna's Repository <br />
: As root, rpm -ivh http://rpm.livna.org/livna-release-6.rpm .<br />
<br />
; Enabling AT-RPMs Repository<br />
: As root, use your favorite editor to create /etc/yum.repos.d/atrpms.repo and type in:<br />
<br />
<pre><br />
[atrpms]<br />
name=Fedora Core $releasever - $basearch - ATrpms<br />
baseurl=http://dl.atrpms.net/fc$releasever-$basearch/atrpms/stable<br />
gpgkey=http://ATrpms.net/RPM-GPG-KEY.atrpms<br />
gpgcheck=1<br />
enabled=0<br />
</pre><br />
<br />
<b>Important:</b> Disabling the AT-RPMs repository by default (using enabled=0) in the above configuration is important. Some repositories have been known not to play well together. See [http://forums.fedoraforum.org/showthread.php?t=94861 this post] on the [http://forums.fedoraforum.org/ Fedora Forms] for more information. However, AT-RPMs does provide a packaged version of the Intel wireless drivers and firmware that we'll use to set up wireless networking later. As long as AT-RPMs is disabled by default, Yum won't install software from their repository unless we explicitly tell it to do so.<br />
<br />
== ATi Video Driver (fglrx) ==<br />
<br />
Installing the fglrx driver is easy if you've enabled the Livna.org RPM repository as discribed earlier in this article. Unfortunately, the proprietary ATi driver currently does not support desktop effects or composite rendering used be default in Fedora Core 6.<br />
<br />
To install the drivers, as root:<br />
[root@scottt60 ~]# yum install kmod-fglrx.i686 xorg-x11-drv-fglrx<br />
<br />
While the driver installs, X fails to use direct Open GL rendering. There are two things that need to be done to get the driver working. First, we must disable effects by adding these lines to the bottom of /etc/X11/xorg.conf:<br />
<br />
<pre><br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
</pre><br />
<br />
Next, we need to add ATi's driver directory to dynamic linker (ld) search path and update the linker configuration:<br />
<br />
<pre><br />
[root@scottt60 ~]# echo "/usr/lib/ati-fglrx/" > /etc/ld.so.conf.d/ati-fglrx.conf<br />
[root@scottt60 ~]# ldconfig<br />
</pre><br />
<br />
After ldconfig completes, restart X. You can check if you've completed your installation correctly by running fglrxinfo. Your output should look like this:<br />
<br />
<pre><br />
[scott@scottt60 ~]$ fglrxinfo <br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Mobility Radeon X1400 Generic<br />
OpenGL version string: 2.0.6174 (8.31.5)<br />
</pre><br />
<br />
Congratulations, your video configuration is complete.<br />
<br />
== Better UltraNav (touchpad) support [PFPS] ==<br />
<br />
To get the touchpad to work right, it is much better to change /etc/X11/xorg.conf. There is quite a bit of information on how to do this scattered over the web, but very little information on why various changes have to be made. (I expect that the changes I made here are not specific to the T60, but would work on most Thinkpads with an UltraNav.)<br />
<br />
I ended up crafting my own xorg.conf, which does the job, and produces no (extra) errors or warnings. (Note that the generated xorg.conf is very sparse, and generates warnings due to missing monitors and font directories. These appear to be benign.)<br />
<br />
<pre><br />
# Xorg configuration created by pyxf86config<br />
# modified by pfps for Synaptics touchpad<br />
<br />
Section "ServerLayout"<br />
Identifier "Default Layout"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "TouchPad" "AlwaysCore"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
Option "XkbModel" "pc105"<br />
Option "XkbLayout" "us"<br />
EndSection<br />
<br />
# synaptics touchpad device<br />
Section "InputDevice"<br />
Identifier "TouchPad"<br />
Driver "synaptics"<br />
Option "Device" "/dev/input/mouse0" # may not be needed<br />
Option "Protocol" "auto-dev" # automatically find device?<br />
Option "LeftEdge" "1700"<br />
Option "RightEdge" "5300"<br />
Option "TopEdge" "1700"<br />
Option "BottomEdge" "4200"<br />
Option "FingerLow" "25"<br />
Option "FingerHigh" "30"<br />
Option "MaxTapTime" "0" # turn off tapping<br />
Option "MaxTapMove" "220"<br />
Option "VertScrollDelta" "100"<br />
Option "MinSpeed" "0.09"<br />
Option "MaxSpeed" "0.18"<br />
Option "AccelFactor" "0.0015"<br />
Option "SHMConfig" "on"<br />
EndSection<br />
<br />
# default mouse - handles other pointing devices, including trackpoint<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "Auto"<br />
Option "Emulate3Buttons" "no"<br />
Option "Buttons" "3"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Videocard0"<br />
Driver "vesa"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Videocard0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
</pre><br />
<br />
<br />
== Wireless Networking ==<br />
<br />
'''Note''' : The wireless issue still exists as of Dec 1, 2006 and you WILL have to follow the instructions below to get it working correctly. --[[User:Navinsamuel|Navinsamuel]] 22:30, 6 December 2006 (CET)<br />
<br />
To use the T60's built in wireless networking driver, you will need to install ipw3945 driver. The AT-RPMs repository, mentioned earlier in this article, provides the necessary packages. As root:<br />
<br />
# yum --enablerepo=atrpms install ipw3945d ipw3945-ucode ipw3945-kmdl-2.6.18-1.2798.fc6.i686<br />
<br />
<br />
'''Note''' : You may notice that yum throws up an error (as of Dec 1, 2006) indicating that it could not locate 'ipw3945-kmdl-2.6.18-1.2798.fc6.i686'. Try the one below instead. --[[User:Navinsamuel|Navinsamuel]] 22:32, 6 December 2006 (CET)<br />
<br />
# yum --enablerepo=atrpms install ipw3945-kmdl-2.6.18-1.2849.fc6.i686<br />
<br />
<br />
Once installed, you must add a startup script to have ipw3945d started at boot. Create the following script in a file named /etc/init.d/ipw3945d<br />
<pre><br />
#! /bin/bash<br />
#<br />
# ipw3490d Load / unload Intel ipw3490 daemon<br />
#<br />
# chkconfig: 2345 09 90<br />
# description: Load / unload Intel ipw3490 daemon<br />
#<br />
### BEGIN INIT INFO<br />
# Provides: ipw3490d<br />
### END INIT INFO<br />
<br />
# Source function library.<br />
. /etc/init.d/functions<br />
<br />
if [ ! -f /etc/sysconfig/network ]; then<br />
exit 0<br />
fi<br />
<br />
case "$1" in<br />
start)<br />
echo -n "Starting ipw3945d: "<br />
/sbin/ipw3945d > /dev/null 2>&1<br />
echo<br />
;;<br />
stop)<br />
echo -n "Stopping ipw3945d: "<br />
killproc ipw3945d<br />
echo<br />
;;<br />
status)<br />
status ipw3945d<br />
;;<br />
restart)<br />
cd "$CWD"<br />
$0 stop<br />
$0 start<br />
;;<br />
*)<br />
echo $"Usage: $0 {start|stop|restart|status}"<br />
exit 1<br />
esac<br />
<br />
exit 0<br />
</pre><br />
<br />
Now, make it executable and add the script with chkconfig to be started on boot:<br />
<br />
# chmod 750 /etc/init.d/ipw3945d<br />
# chkconfig --add ipw3945d<br />
<br />
Make sure things are setup correctly by running chkconfig --list ipw345d. Your output should look something like:<br />
<br />
# chkconfig --list ipw3945d<br />
ipw3945d 0:off 1:off 2:on 3:on 4:on 5:on 6:off<br />
<br />
If everything looks okay, reboot. Once restarted you should be able to run <code>ifconfig eth1</code> and see information about your wireless card. If you prefer a GUI, you can run the network configuration tool (System, Administration, Network). Click New on the Devices tab, then Wireless Connection. "Intel Corporation PRO/Wireless 3945ABG Network Connection(eth1)" or something similar should appear in the list of wireless devices.<br />
<br />
== Infrared (IrDA) ==<br />
By default, Fedora will make the IR device appear as ttyS2, but the BIOS has the port default to COM2, or ttyS1. Paste this text into /etc/sysconfig/irda:<br />
<pre><br />
IRDA=yes<br />
DEVICE=/dev/ttyS1<br />
#DONGLE=actisys+<br />
DISCOVERY=yes<br />
</pre><br />
<br />
Start (or restart) the irda service. Then ensure it starts for your favorite runlevel using either chkconfig or the Service Configuration tool. You can then use irdadump (as root) to confirm your configuration is correct by monitoring port activity when another IR device is near.<br />
<br />
=External Sources=<br />
*This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation survey (IBM/Lenovo)].<br />
<br />
[[Category:Fedora]]<br />
[[Category:T60]]</div>Pfpshttps://www.thinkwiki.org/w/index.php?title=Installing_Fedora_Core_6_on_a_ThinkPad_T60&diff=26980Installing Fedora Core 6 on a ThinkPad T602006-12-13T16:57:27Z<p>Pfps: /* Works Out of the Box */</p>
<hr />
<div>== Installation ==<br />
<br />
Installation of Fedora Core 6 (Zod) on a Thinkpad T60 (2623). The installation completes successfully but installs the i586 kernel instead of the required i686 kernel. The wrong kernel is due to a [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211941 known bug] in the Anaconda installer.<br />
<br />
'''Note''' : At the time of this writing (Dec 1, 2006), the installer correctly installs the i686 kernel. Check your kernel version before you proceed. --[[User:Navinsamuel|Navinsamuel]] 22:20, 6 December 2006 (CET)<br />
<br />
== Works Out of the Box ==<br />
<br />
; Dual Cores (SMP processing)<br />
: As of Kernel 2.6.18, used in Fedora Core 6, there is no loger a single cpu and smp kernel image. SMP is now configured on-the-fly. FC6's kernel will automatically discover the T60's dual core cpu and bring up CPU0 and CPU1.<br />
<br />
; Wired Networking <br />
: Kernel recognizes eth0 and correctly loads the e1000 driver.<br />
<br />
; Video at 1400x1050<br />
: Fedora does not ship the proprietary ATi driver, as a reult the VESA driver is used. Installation of the ATi fgrlx driver is described later in this article.<br />
<br />
; Touchpad / Mouse<br />
: The TrackPoint middle button does not work as a scroll wheel by default.<br />
: PFPS: Note that although the touchpad and trackpoint work, Fedora Core 6 does a bad job of setting up xorg.conf. It is better to fix it up (see below).<br />
<br />
; Sound <br />
: The first-boot sound test fails to play the test sound. However, sound support is correctly configured and the snd-hda-intel driver is loaded at startup.<br />
<br />
; Suspend to RAM <br />
: Works out of the box under Gnome. Gnome power management intregrates with HAL (Linux's hardware abstraction layer) and DBUS, which correctly put this computer into a suspsend to RAM state and wake it up correctly.<br />
<br />
== Requires Tweaking == <br />
<br />
* Wireless Networking (Requires ipw3945 driver)<br />
* ATi OpenGL Direct Rendering<br />
* Hibernate<br />
* IrDA<br />
<br />
== Post Install ==<br />
<br />
=== Replacing the Kernel ===<br />
<br />
'''Note''' : The steps below will not be required if the i686 version is already installed by default, which would be the case if you downloaded Zod recently (as of Dec 1, 2006). --[[User:Navinsamuel|Navinsamuel]] 22:20, 6 December 2006 (CET)<br />
<br />
As previously mentioned, the i586 kernel is installed on this machine instead of the i686 version. The i686 version is required to install the ATI video drivers and Intel Wireless drivers required to get this machine 100% operational. It is best to do this first, before updating any packages.<br />
<br />
Installing the new kernel can be done by various methods as documented on the [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211941 Red Hat Bugzilla bug]. However, the safest method is to use [[yum]] to do the kernel swap.<br />
<br />
'''Note''' : If you have a multi-boot system, backup your Grub configuration file or atleast note it's contents elsewhere. If you don't, you can end up in a real mess! --[[User:Navinsamuel|Navinsamuel]] 22:20, 6 December 2006 (CET)<br />
<br />
To swap kernels:<br />
# Open up a terminal window are become root.<br />
# Execute: yum remove kernel<br />
# Make note of any other packages that will be removed due to dependency issues. The packages will have to be reinstalled in the next step.<br />
# Install the kernel.i686 package and any other packages removed in the previous step.<br />
# Fix your [[Grub]] configuration<br />
# Reboot<br />
<br />
On a minimal install, the only dependencies removed were gnome-session, compiz, gnome-volume-manager, and pcmciautils. Getting things back on track required:<br />
<br />
# yum install kernel.i686 gnome-session compiz gnome-volume-manager pcmciautils<br />
<br />
After [Yum] completes, you will have to fix the boot loader or you will be unable to boot after a restart.<br />
<br />
If you have '''not''' used Fedora's default installation using LVM partitions, you can use the following configuration for grub. As root, fire up your favorite text editor and add the following lines to your grub configuration (/boot/grub/grub.conf) just below the initial comments:<br />
<br />
<pre><br />
title FC6 2.6.18-1.2798<br />
kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=LABEL=/ rhgb quiet<br />
initrd /initrd-2.6.18-1.2798.fc6.img<br />
</pre><br />
<br />
If you have an LVM partition, use the method detailed at Redhat's site.<br />
<br />
=== Getting Up to Date ===<br />
<br />
Before completing installation, it's best to get up to date by running yum update as root or by using the new graphical updater, Pup, that ships with Fedora Core 6. After all updates are installed, reboot before continuing the post-install tasks.<br />
<br />
=== Setting Up Additional Repositories ===<br />
<br />
In order to get the ATI driver and the Intel Wireless working, you will need to add two repositories to your computer; [http://rpm.livna.org/ Livna RPMs] and [http://atrpms.net/ AT-RPMs].<br />
<br />
; Enabling Livna's Repository <br />
: As root, rpm -ivh http://rpm.livna.org/livna-release-6.rpm .<br />
<br />
; Enabling AT-RPMs Repository<br />
: As root, use your favorite editor to create /etc/yum.repos.d/atrpms.repo and type in:<br />
<br />
<pre><br />
[atrpms]<br />
name=Fedora Core $releasever - $basearch - ATrpms<br />
baseurl=http://dl.atrpms.net/fc$releasever-$basearch/atrpms/stable<br />
gpgkey=http://ATrpms.net/RPM-GPG-KEY.atrpms<br />
gpgcheck=1<br />
enabled=0<br />
</pre><br />
<br />
<b>Important:</b> Disabling the AT-RPMs repository by default (using enabled=0) in the above configuration is important. Some repositories have been known not to play well together. See [http://forums.fedoraforum.org/showthread.php?t=94861 this post] on the [http://forums.fedoraforum.org/ Fedora Forms] for more information. However, AT-RPMs does provide a packaged version of the Intel wireless drivers and firmware that we'll use to set up wireless networking later. As long as AT-RPMs is disabled by default, Yum won't install software from their repository unless we explicitly tell it to do so.<br />
<br />
== ATi Video Driver (fglrx) ==<br />
<br />
Installing the fglrx driver is easy if you've enabled the Livna.org RPM repository as discribed earlier in this article. Unfortunately, the proprietary ATi driver currently does not support desktop effects or composite rendering used be default in Fedora Core 6.<br />
<br />
To install the drivers, as root:<br />
[root@scottt60 ~]# yum install kmod-fglrx.i686 xorg-x11-drv-fglrx<br />
<br />
While the driver installs, X fails to use direct Open GL rendering. There are two things that need to be done to get the driver working. First, we must disable effects by adding these lines to the bottom of /etc/X11/xorg.conf:<br />
<br />
<pre><br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
</pre><br />
<br />
Next, we need to add ATi's driver directory to dynamic linker (ld) search path and update the linker configuration:<br />
<br />
<pre><br />
[root@scottt60 ~]# echo "/usr/lib/ati-fglrx/" > /etc/ld.so.conf.d/ati-fglrx.conf<br />
[root@scottt60 ~]# ldconfig<br />
</pre><br />
<br />
After ldconfig completes, restart X. You can check if you've completed your installation correctly by running fglrxinfo. Your output should look like this:<br />
<br />
<pre><br />
[scott@scottt60 ~]$ fglrxinfo <br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Mobility Radeon X1400 Generic<br />
OpenGL version string: 2.0.6174 (8.31.5)<br />
</pre><br />
<br />
Congratulations, your video configuration is complete.<br />
<br />
== Wireless Networking ==<br />
<br />
'''Note''' : The wireless issue still exists as of Dec 1, 2006 and you WILL have to follow the instructions below to get it working correctly. --[[User:Navinsamuel|Navinsamuel]] 22:30, 6 December 2006 (CET)<br />
<br />
To use the T60's built in wireless networking driver, you will need to install ipw3945 driver. The AT-RPMs repository, mentioned earlier in this article, provides the necessary packages. As root:<br />
<br />
# yum --enablerepo=atrpms install ipw3945d ipw3945-ucode ipw3945-kmdl-2.6.18-1.2798.fc6.i686<br />
<br />
<br />
'''Note''' : You may notice that yum throws up an error (as of Dec 1, 2006) indicating that it could not locate 'ipw3945-kmdl-2.6.18-1.2798.fc6.i686'. Try the one below instead. --[[User:Navinsamuel|Navinsamuel]] 22:32, 6 December 2006 (CET)<br />
<br />
# yum --enablerepo=atrpms install ipw3945-kmdl-2.6.18-1.2849.fc6.i686<br />
<br />
<br />
Once installed, you must add a startup script to have ipw3945d started at boot. Create the following script in a file named /etc/init.d/ipw3945d<br />
<pre><br />
#! /bin/bash<br />
#<br />
# ipw3490d Load / unload Intel ipw3490 daemon<br />
#<br />
# chkconfig: 2345 09 90<br />
# description: Load / unload Intel ipw3490 daemon<br />
#<br />
### BEGIN INIT INFO<br />
# Provides: ipw3490d<br />
### END INIT INFO<br />
<br />
# Source function library.<br />
. /etc/init.d/functions<br />
<br />
if [ ! -f /etc/sysconfig/network ]; then<br />
exit 0<br />
fi<br />
<br />
case "$1" in<br />
start)<br />
echo -n "Starting ipw3945d: "<br />
/sbin/ipw3945d > /dev/null 2>&1<br />
echo<br />
;;<br />
stop)<br />
echo -n "Stopping ipw3945d: "<br />
killproc ipw3945d<br />
echo<br />
;;<br />
status)<br />
status ipw3945d<br />
;;<br />
restart)<br />
cd "$CWD"<br />
$0 stop<br />
$0 start<br />
;;<br />
*)<br />
echo $"Usage: $0 {start|stop|restart|status}"<br />
exit 1<br />
esac<br />
<br />
exit 0<br />
</pre><br />
<br />
Now, make it executable and add the script with chkconfig to be started on boot:<br />
<br />
# chmod 750 /etc/init.d/ipw3945d<br />
# chkconfig --add ipw3945d<br />
<br />
Make sure things are setup correctly by running chkconfig --list ipw345d. Your output should look something like:<br />
<br />
# chkconfig --list ipw3945d<br />
ipw3945d 0:off 1:off 2:on 3:on 4:on 5:on 6:off<br />
<br />
If everything looks okay, reboot. Once restarted you should be able to run <code>ifconfig eth1</code> and see information about your wireless card. If you prefer a GUI, you can run the network configuration tool (System, Administration, Network). Click New on the Devices tab, then Wireless Connection. "Intel Corporation PRO/Wireless 3945ABG Network Connection(eth1)" or something similar should appear in the list of wireless devices.<br />
<br />
== Infrared (IrDA) ==<br />
By default, Fedora will make the IR device appear as ttyS2, but the BIOS has the port default to COM2, or ttyS1. Paste this text into /etc/sysconfig/irda:<br />
<pre><br />
IRDA=yes<br />
DEVICE=/dev/ttyS1<br />
#DONGLE=actisys+<br />
DISCOVERY=yes<br />
</pre><br />
<br />
Start (or restart) the irda service. Then ensure it starts for your favorite runlevel using either chkconfig or the Service Configuration tool. You can then use irdadump (as root) to confirm your configuration is correct by monitoring port activity when another IR device is near.<br />
<br />
=External Sources=<br />
*This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation survey (IBM/Lenovo)].<br />
<br />
[[Category:Fedora]]<br />
[[Category:T60]]</div>Pfps