https://www.thinkwiki.org/w/api.php?action=feedcontributions&feedformat=atom&user=JltThinkWiki - User contributions [en]2026-04-30T18:01:07ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=Fglrx&diff=8603Fglrx2005-08-20T09:30:22Z<p>Jlt: /* Status */</p>
<hr />
<div>== ATI drivers for Linux ==<br />
Linux ATI driver for select Radeon, FireGL and Mobility boards<br />
<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
- On the old drivers, I've noticed appx 40% speed gain with ATI fglrx vs open source drivers. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (ctrl-alt-plus, ctrl-alt-minus), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using "radeon" or "ati" in xorg.conf. 1200FPS glxgears! (''note that glxgears isnt a benchmark tool, its so simple that its value 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 happend the opposite. Think in the car engine rpm, higher rpm in the same car usually its a faster car, change anything and its meaningless. ie: gears, truck, wheel size, etc make it useless'')<br />
<br />
NOTE: 2D acceleration may be disabled when 3D acceleration is enabled. This comes from the Xorg.conf file the fglrx driver provides<br />
# === OpenGL Overlay ===<br />
# Note: When OpenGL Overlay is enabled, Video Overlay<br />
# will be disabled automatically<br />
Option "OpenGLOverlay" "1"<br />
<br />
--- <br />
Just a note to the above. The 2D acceleration for that option refers to video overlay. You can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. It has nothing to do with 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. My 9200SE is supported by both and with ATI 8.12.10 drivers (newer drivers aren't always faster) my meager machine gets about 512 fps and changing ONLY the driver (and OpenGL lib) to the open source radeon driver (from Xorg 6.8.2-r2) I'm getting 707 fps. So - that 40% gain is going in the open-source favor not ATI's for my setup.<br />
<br />
=== Project Homepage / Availability ===<br />
http://www.ati.com/support/drivers/linux/radeon-linux.html<br />
<br />
=== Status ===<br />
Current version: 8.16.20 (17th August 2005)<br />
<br />
=== Problems & Help ===<br />
<br />
'''Driver Version 8.8.25:''' The following patch may be needed for kernels >= 2.6.10:<br />
[http://www.rage3d.com/board/showthread.php?t=33798874 http://www.rage3d.com/board/showthread.php?t=33798874]<br />
<br />
'''Driver Version 8.8.25:''' For kernels >= 2.6.11-rc1 try the following patch:<br />
http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch<br />
<br />
'''If the ATI driver works only without the hardware acceleration''', take into consideration that fglrx_dri.so was linked<br />
against libstdc++.so.5 which may not be present if your system uses gcc-3.4. To fix this, compile gcc-3.3.5 <br />
and copy libstdc++.so.5* to /usr/lib and update the dynamic linker cache.<br />
<br />
'''Troubles using software suspend''' : when the computer comes back of suspend, X only displays a garbaged image and the computer is frozen. You have to install [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] and use it to save/restore the video card state. If you use swsusp2 scripts you just have to uncomment ''"EnableVbetool yes"'' in ''/etc/hibernate/hibernate.conf''. Tested with kernel 2.6.10, Debian packaged ATI drivers and [http://www.suspend2.net swsusp2] patch on a IBM Thinkpad T42p. <br />
<br />
This does not seem to work on the T43: The machine displays a sligthly garbaged image and is frozen upon resume. (It does work as long as the fglrx kernel driver is not inserted.) (Tested on kernel 2.6.12-rc6 with suspend2 2.1.9 and ATI driver version 8.14.13.)<br />
<br />
Works on the T42, tested with SuSE 9.3, kernel-default (2.6.11), ATI driver 8.14.13 (for instructions see: /usr/share/doc/packages/powersave/contrib) <br />
<br />
'''Troubles with large RAM''' : The driver (version 8.14.13 tested on a T43) does not seem to be able to cope with large amounts of RAM: with 512 MB it works, with 1.5 GB it crashes the machine as soon as X is started. The problem is present only if the ''fglrx'' kernel module is loaded, but independetly of whether ''"CONFIG_HIGHMEM"'' is enabled (I.e. the actual amount of RAM available to the system does not seem to matter, but rather how mauch RAM is physically installed.).<br />
<br />
A workaround is to limit RAM by kernel option mem=864m in lilo.conf (lilo) oder menu.lst (grub).<br />
<br />
Version 8.16.20 of the driver seems to fix the problem.<br />
<br />
=== Packages ===<br />
*{{Debian}} Packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html<br />
*{{SUSE}} Packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/<br />
*{{Gentoo}} {{cmdroot|emerge media-video/ati-drivers}}<br />
*{{Fedora}} Packages: http://rpm.livna.org -- {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}<br />
<br />
=== Useful links === <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www2.ati.com/drivers/linux/linux_8.12.10.html ATI Proprietary Linux Release Notes] <tt>(for 8.12.10)</tt><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://ati.cchtml.com/ Unofficial community ATI bugzilla] Very newly setup (!) bugzilla, which might grow to be a source for information about ATI bugs. Might then be monitored by ATI guys ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]). We will see how this develops.<br />
<br />
== ThinkPads that may be supported ==<br />
Supported chips, as found in select IBM ThinkPads:<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 />
<br />
[[Category:Drivers]]</div>Jlthttps://www.thinkwiki.org/w/index.php?title=How_to_make_ACPI_work&diff=8337How to make ACPI work2005-08-20T09:26:57Z<p>Jlt: /* Suspend to RAM (Sleep) */</p>
<hr />
<div>==general==<br />
===Kernel configuration===<br />
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).<br />
To do this open your kernel config and enable ACPI Power Management:<br />
{{kernelconf||||Power management options|Power Management support|<*>|CONFIG_PM}}<br />
{{kernelconf||||Power management options|ACPI|<*>|CONFIG_ACPI_SLEEP}}<br />
<br />
You'd most likely want to enable the following ACPI options:<br />
{{kernelconf|||Power management options|ACPI|Sleep States|<*>|CONFIG_ACPI_SLEEP}}<br />
{{kernelconf|||Power management options|ACPI|AC Adapter|<*>|CONFIG_ACPI_AC}}<br />
{{kernelconf|||Power management options|ACPI|Battery|<*>|CONFIG_ACPI_BATTERY}}<br />
{{kernelconf|||Power management options|ACPI|Fan|<*>|CONFIG_ACPI_FAN}}<br />
{{kernelconf|||Power management options|ACPI|Processor|<*>|CONFIG_ACPI_PROCESSOR}}<br />
{{kernelconf|||Power management options|ACPI|Thermal Zone|<*>|CONFIG_ACPI_THERMAL}}<br />
<br />
If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:<br />
CONFIG_PM=y<br />
CONFIG_ACPI_BOOT=y<br />
CONFIG_ACPI_INTERPRETER=y<br />
CONFIG_ACPI_SLEEP=y<br />
CONFIG_ACPI_SLEEP_PROC_FS=y<br />
CONFIG_ACPI_AC=y<br />
CONFIG_ACPI_BATTERY=y<br />
CONFIG_ACPI_BUTTON=y<br />
CONFIG_ACPI_FAN=y<br />
CONFIG_ACPI_PROCESSOR=y<br />
CONFIG_ACPI_THERMAL=y<br />
CONFIG_ACPI_BUS=y<br />
CONFIG_ACPI_EC=y<br />
CONFIG_ACPI_POWER=y<br />
CONFIG_ACPI_PCI=y<br />
CONFIG_ACPI_SYSTEM=y<br />
<br />
Then recompile your kernel.<br />
<br />
===IBM specific ACPI driver===<br />
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10. So you'll have to compile one yourself or get it as precompiled module for your kernel.<br />
<br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br />
<br />
If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.<br />
<br />
{{HINT|In general it is a good idea to read the README included with the driver.}}<br />
<br />
===ACPI daemon===<br />
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].<br />
<br />
==Screen blanking (Standby)==<br />
Make sure you have <br />
Option "DPMS"<br />
in the Monitor section of your {{path|/etc/X11/XF86Config}} or {{path|/etc/X11/xorg.conf}}.<br />
<br />
Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br /><br />
<br />
Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.<br />
<br />
==Suspend to RAM (Sleep)==<br />
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.<br />
<br />
The following glitches may or may not occur in relation to suspending to RAM:<br />
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). This can be fixed by adding {{bootparm|acpi_sleep|s3_bios}} to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1, but is reported to be needed on 2.6.12.3.<br />
* When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.<br />
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].<br />
* You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.<br />
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.<br />
* Crash on resume<br />
** ...when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool].<br />
** ...might be solved by disabling ''APIC'' (@Processor type and features) in the kernel configuration<br />
* If your suspend is failing, and a tail of {{path|/var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions<br />
* Due to the fact that Sonoma chipset based laptops (T43, T43p) utilize the SATA layer for disk access and SATA does not have power-management support yet Suspend to RAM does not work on these machines. However, Jens Axboe's patch ([http://marc.theaimsgroup.com/?l=linux-kernel&m=111504542402455&w=2] LKML posting) provides SATA power-management support and makes Suspend to RAM work on the T43 at least. (Tested on 2.6.12rc6 which the patch applies to with some offsets. T43p not tested but should work as well. X41: reboot after wake up. R52 uses SATA and sleep doesn't work, so it is probably affected too)<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff 2.6.12 patch]<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.13-rc5.diff 2.6.13-rc5 patch]<br />
<br />
==Suspend to disk (Hibernate)==<br />
There are two drivers for this available:<br />
* swsusp, which is in the kernel and<br />
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself<br />
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].<br />
<br />
Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.<br />
<br />
===using swsusp===<br />
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.<br />
<br />
To enable software suspend change your kernel config as follows:<br />
{{kernelconf||||Power management options|Power management support|<*>|CONFIG_PM}}<br />
{{kernelconf||||Power management options|Software Suspend|<*>|CONFIG_SOFTWARE_SUSPEND}}<br />
{{kernelconf||||Power management options|Default resume partition|[/dev/resume_partition]|CONFIG_PM_STD_PARTITION}}<br />
<br />
<tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.) <br />
<br />
You can override the default resume partition anytime by giving {{bootparm|resume|/dev/resume_partition}} as kernel boot parameter.<br />
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - losing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.<br />
<br />
(In my case, and according to reports from several people, suspending does not work if resume_partition is specified in the kernel config (my version is 2.6.12-3 from kernel.org). It works as a charm if one specifies the resume partition as a kernel parameter instead.)<br />
<br />
To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.<br />
<br />
Ideally you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.<br />
*any running mysql server<br />
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.<br />
<br />
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.<br />
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).<br />
<br />
If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:<br />
<br />
amixer set Master mute >/dev/null 2>&1<br />
amixer set PCM mute >/dev/null 2>&1<br />
amixer set Master unmute >/dev/null 2>&1<br />
amixer set PCM unmute >/dev/null 2>&1<br />
<br />
Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.<br />
<br />
===using SoftwareSuspend2===<br />
First apply Software Suspend 2 patches from http://softwaresuspend.berlios.de/ if they are not already in your kernel.<br />
<br />
Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html<br />
<br />
These are the options for the kernel. Make sure to change the <tt>/dev/resume_partition</tt> to your swap partition, i.e. <tt>/dev/hda5</tt>.<br />
<br />
# Software Suspend 2<br />
CONFIG_SOFTWARE_SUSPEND2=y<br />
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y<br />
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y<br />
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y<br />
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y<br />
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/resume_partition"<br />
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set<br />
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y<br />
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set<br />
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set<br />
<br />
Next, compile and install the kernel.<br />
<br />
In the meantime, add the following to the kernel parameters: {{bootparm|resume2|swap:/dev/resume_partition}}. Again change <tt>/dev/resume_partition</tt> to your swap partition.<br />
<br />
Install the hibernation script:<br />
*For {{Gentoo}} users: emerge hibernate-script<br /><br />
*For {{Fedora}} users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br /><br />
*For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://softwaresuspend.berlios.de/<br />
*{{Debian}} users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your {{path|/etc/mkinitrd/scripts}} directory before creating initrd image.<br />
<br />
Restart using the new kernel and run the script to test it: {{cmdroot|/usr/sbin/hibernate}}<br />
<br />
==ThinkPads using ACPI is recommended on==<br />
*ThinkPad {{770X}}, {{770Z}}<br />
*ThinkPad {{A20m}}, {{A20p}}, {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}}<br />
*ThinkPad {{G40}}, {{G41}}<br />
*ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{R40e}}, {{R50}}, {{R50p}}, {{R51}}, {{R52}}<br />
*ThinkPad {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}<br />
*ThinkPad {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X32}}, {{X40}}, {{X41}}, {{X41T}}<br />
*ThinkPad {{TransNote}}</div>Jlthttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=8198Fglrx2005-08-20T09:24:22Z<p>Jlt: /* Problems & Help */</p>
<hr />
<div>== ATI drivers for Linux ==<br />
Linux ATI driver for select Radeon, FireGL and Mobility boards<br />
<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
- On the old drivers, I've noticed appx 40% speed gain with ATI fglrx vs open source drivers. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (ctrl-alt-plus, ctrl-alt-minus), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using "radeon" or "ati" in xorg.conf. 1200FPS glxgears! (''note that glxgears isnt a benchmark tool, its so simple that its value 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 happend the opposite. Think in the car engine rpm, higher rpm in the same car usually its a faster car, change anything and its meaningless. ie: gears, truck, wheel size, etc make it useless'')<br />
<br />
NOTE: 2D acceleration may be disabled when 3D acceleration is enabled. This comes from the Xorg.conf file the fglrx driver provides<br />
# === OpenGL Overlay ===<br />
# Note: When OpenGL Overlay is enabled, Video Overlay<br />
# will be disabled automatically<br />
Option "OpenGLOverlay" "1"<br />
<br />
--- <br />
Just a note to the above. The 2D acceleration for that option refers to video overlay. You can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. It has nothing to do with 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. My 9200SE is supported by both and with ATI 8.12.10 drivers (newer drivers aren't always faster) my meager machine gets about 512 fps and changing ONLY the driver (and OpenGL lib) to the open source radeon driver (from Xorg 6.8.2-r2) I'm getting 707 fps. So - that 40% gain is going in the open-source favor not ATI's for my setup.<br />
<br />
=== Project Homepage / Availability ===<br />
http://www.ati.com/support/drivers/linux/radeon-linux.html<br />
<br />
=== Status ===<br />
Current version: 8.14.13 (9th June 2005)<br />
<br />
=== Problems & Help ===<br />
<br />
'''Driver Version 8.8.25:''' The following patch may be needed for kernels >= 2.6.10:<br />
[http://www.rage3d.com/board/showthread.php?t=33798874 http://www.rage3d.com/board/showthread.php?t=33798874]<br />
<br />
'''Driver Version 8.8.25:''' For kernels >= 2.6.11-rc1 try the following patch:<br />
http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch<br />
<br />
'''If the ATI driver works only without the hardware acceleration''', take into consideration that fglrx_dri.so was linked<br />
against libstdc++.so.5 which may not be present if your system uses gcc-3.4. To fix this, compile gcc-3.3.5 <br />
and copy libstdc++.so.5* to /usr/lib and update the dynamic linker cache.<br />
<br />
'''Troubles using software suspend''' : when the computer comes back of suspend, X only displays a garbaged image and the computer is frozen. You have to install [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] and use it to save/restore the video card state. If you use swsusp2 scripts you just have to uncomment ''"EnableVbetool yes"'' in ''/etc/hibernate/hibernate.conf''. Tested with kernel 2.6.10, Debian packaged ATI drivers and [http://www.suspend2.net swsusp2] patch on a IBM Thinkpad T42p. <br />
<br />
This does not seem to work on the T43: The machine displays a sligthly garbaged image and is frozen upon resume. (It does work as long as the fglrx kernel driver is not inserted.) (Tested on kernel 2.6.12-rc6 with suspend2 2.1.9 and ATI driver version 8.14.13.)<br />
<br />
Works on the T42, tested with SuSE 9.3, kernel-default (2.6.11), ATI driver 8.14.13 (for instructions see: /usr/share/doc/packages/powersave/contrib) <br />
<br />
'''Troubles with large RAM''' : The driver (version 8.14.13 tested on a T43) does not seem to be able to cope with large amounts of RAM: with 512 MB it works, with 1.5 GB it crashes the machine as soon as X is started. The problem is present only if the ''fglrx'' kernel module is loaded, but independetly of whether ''"CONFIG_HIGHMEM"'' is enabled (I.e. the actual amount of RAM available to the system does not seem to matter, but rather how mauch RAM is physically installed.).<br />
<br />
A workaround is to limit RAM by kernel option mem=864m in lilo.conf (lilo) oder menu.lst (grub).<br />
<br />
Version 8.16.20 of the driver seems to fix the problem.<br />
<br />
=== Packages ===<br />
*{{Debian}} Packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html<br />
*{{SUSE}} Packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/<br />
*{{Gentoo}} {{cmdroot|emerge media-video/ati-drivers}}<br />
*{{Fedora}} Packages: http://rpm.livna.org -- {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}<br />
<br />
=== Useful links === <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www2.ati.com/drivers/linux/linux_8.12.10.html ATI Proprietary Linux Release Notes] <tt>(for 8.12.10)</tt><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://ati.cchtml.com/ Unofficial community ATI bugzilla] Very newly setup (!) bugzilla, which might grow to be a source for information about ATI bugs. Might then be monitored by ATI guys ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]). We will see how this develops.<br />
<br />
== ThinkPads that may be supported ==<br />
Supported chips, as found in select IBM ThinkPads:<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 />
<br />
[[Category:Drivers]]</div>Jlthttps://www.thinkwiki.org/w/index.php?title=IrDA&diff=5973IrDA2005-06-21T23:00:42Z<p>Jlt: /* ISA PnP patch */</p>
<hr />
<div>== ThinkPad IrDA configuration ==<br />
<br />
IrDA can be used to communicate using Infrared to other IrDA compliant devices, such as other Notebooks, PDA's and mobile phones.<br />
<br />
All IBM ThinkPads manufactured in the last years have integrated IrDA that can be used in one of two modes, SIR or FIR.<br />
Some very old ThinkPads only support SIR mode, or might not have IrDA support at all.<br />
<br />
The purpose of this document is to get the IrDA hardware in your ThinkPad operational, setting up communication to other devices is not covered. However, the external links section can prove useful for this.<br />
<br />
=== Serial IR (SIR) ===<br />
SIR is limited to serial datarates up to 115.2Kb/s<br />
<br />
==== Linux 2.4 kernel config ====<br />
Edit /etc/modules.conf and add the following lines<br />
alias tty-ldisc-11 irtty<br />
alias char-major-161 ircomm-tty<br />
<br />
=== Fast IR (FIR) ===<br />
FIR is the preferred mode of IrDA operation and operates at a bandwidth of 4 Mbps<br />
==== BIOS settings ====<br />
Main problem here is that the chips FIR mode needs to be activated. On A, G, R, T and X model ThinkPads, the easiest way to activate FIR mode is by entering BIOS setup during boot-up by pressing F1 when prompted.<br />
Then, selecting 'Config' followed by 'Infrared' will allow you to control the IrDA operation. Here you will need to select the option to Enable the infra-red port. Be sure to save the changes, and then Exit.<br />
<br />
Note: Changing these BIOS settings do not affect Windows 2000 or XP operating systems, but may cause memory resource issues in older windows versions, or other legacy operating systems.<br />
==== PnP settings from Linux ====<br />
If changing the BIOS setting is not an option or if the settings cannot be altered, as on some older ThinkPads, the FIR mode can be activated by running Linux OS with one of the following:<br />
<br />
* setpnp as part of the old pcmcia-utils source package<br />
* tpctl, but only for some old ThinkPads<br />
<br />
setpnp requires a kernel with pnp-bios support compiled in, which the Red Hat and Fedore kernels lack.<br />
==== ISA PnP patch ====<br />
2.6 kernel ISA PnP Patches exist for the nsc-ircc driver, that allow the loading of the driver without the BIOS, setpnp or tpctl hacks.<br><br />
You will still have to call setserial and set the dongle_id parameter, as shown below.<br />
<br />
* [http://steffenpingel.de/patches/nsc-ircc-pnp.diff 2.6.10 patch]<br />
* [http://shamrock.dyndns.org/~ln/linux/nsc-ircc-pnp.2.6.12-rc6.diff 2.6.12-rc6 patch] (applies cleanly on 2.6.12 as well)<br />
<br />
==== Linux 2.4 kernel config ====<br />
Edit /etc/modules.conf and add the following lines<br />
<br />
alias irda0 nsc-ircc<br />
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3<br />
pre-install nsc-ircc setserial /dev/ttyS1 uart none port 0 irq 0<br />
<br />
==== Linux 2.6 kernel config ====<br />
Edit /etc/modprobe.conf and add the following lines<br />
<br />
alias irda0 nsc-ircc<br />
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3<br />
install nsc-ircc /bin/setserial /dev/ttyS1 uart none port 0 irq 0; /sbin/modprobe --ignore-install nsc-ircc<br />
<br />
=== Very Fast IR (VFIR) ===<br />
A newer VFIR standard exists, which supports speeds upto 16Mbps.<br><br />
However for the moment no ThinkPads support this.<br />
=== Known problems ===<br />
* If the FIR mode is not activated, attempts to load the nsc-ircc module will result in an error in syslog of "Wrong chip version ff".<br />
* after suspend the nsc-ircc module needs to be manually reloaded<br />
<br />
=== Some other things you might want to do with IrDA ===<br />
<br />
# add fast PPP support:<br />
modprobe irnet<br />
<br />
# if needed, limit further the size of the transmit window<br />
echo 1 > /proc/sys/net/irda/max_tx_window<br />
<br />
== External links ==<br />
[http://irda.sourceforge.net/ Linux-IrDA Project] (External)<br />
<br />
[http://pcmcia-cs.sourceforge.net/ Linux PCMCIA Project] (External)<br />
<br />
[http://tpctl.sourceforge.net/ tpctl homepage] (External)<br />
<br />
== Supported Models ==<br />
'''IrDA 1.0 (SIR - 115Kbps)'''<br />
* {{365C}}, {{365CD}}, {{365CS}}, {{365CSD}}, {{365E}}, {{365ED}}, {{365X}}, {{365XD}}<br />
* {{560}}<br />
* {{755CD}}, {{755CDV}}, {{755CE}}, {{755CSE}}, {{755CV}}, {{755CX}}<br />
* {{760C}}, {{760CD}}, {{760E}}, {{760ED}}, {{760EL}}, {{760ELD}}, {{760L}}, {{760LD}}, {{760XD}}, {{760XL}}<br />
* {{765D}}, {{765L}}<br />
* {{PC110}}<br />
'''IrDA 1.1 (FIR - 4Mbps)'''<br />
* {{240}}, {{240X}}<br />
* {{380}}, {{380D}}, {{380E}}, {{380ED}}, {{380XD}}, {{380Z}}<br />
* {{385D}}, {{385ED}}, {{385XD}}<br />
* {{390}}, {{390E}}, {{390X}}<br />
* {{560E}}, {{560X}}, {{560Z}}<br />
* {{570}}, {{570E}}<br />
* {{600}}, {{600E}}, {{600X}}<br />
* {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}<br />
* {{A Series}}<br />
* {{i1720}}, {{i1721}}<br />
* {{R Series}}<br />
* {{T Series}}<br />
* {{X Series}}<br />
* {{TransNote}}<br />
<br />
[[Category:Drivers]]</div>Jlthttps://www.thinkwiki.org/w/index.php?title=How_to_make_ACPI_work&diff=6013How to make ACPI work2005-06-21T22:58:56Z<p>Jlt: /* Suspend to RAM (Sleep) */</p>
<hr />
<div>==general==<br />
===Kernel configuration===<br />
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).<br />
To do this open your kernel config, go to <code>Power management options</code>, enable <code>Power Management support</code>, go to <code>ACPI</code> and enable the needed options. You'd most likely want to enable <code>Sleep States</code>, <code>AC Adapter</code>, <code>Battery</code>, <code>Fan</code>, <code>Processor</code> and <code>Thermal Zone</code>. Then recompile your kernel.<br />
<br />
If you prefer editing your .config file directly, you should set at least the following variables:<br />
CONFIG_PM=y<br />
CONFIG_ACPI_BOOT=y<br />
CONFIG_ACPI_INTERPRETER=y<br />
CONFIG_ACPI_SLEEP=y<br />
CONFIG_ACPI_SLEEP_PROC_FS=y<br />
CONFIG_ACPI_AC=y<br />
CONFIG_ACPI_BATTERY=y<br />
CONFIG_ACPI_BUTTON=y<br />
CONFIG_ACPI_FAN=y<br />
CONFIG_ACPI_PROCESSOR=y<br />
CONFIG_ACPI_THERMAL=y<br />
CONFIG_ACPI_BUS=y<br />
CONFIG_ACPI_EC=y<br />
CONFIG_ACPI_POWER=y<br />
CONFIG_ACPI_PCI=y<br />
CONFIG_ACPI_SYSTEM=y<br />
<br />
===IBM specific ACPI driver===<br />
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10.<br /><br />
So you'll have to compile one yourself or get it as precompiled module for your kernel.<br /><br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br /><br />
If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.<br /><br />
In general it is a good idea to read the README included with the driver.<br />
<br />
===ACPI daemon===<br />
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].<br />
<br />
==Screen blanking (Standby)==<br />
Make sure you have <br />
Option "DPMS"<br />
in the Monitor section of your XF86Config/xorg.conf.<br />
<br />
Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br /><br />
<br />
Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.<br />
<br />
==Suspend to RAM (Sleep)==<br />
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.<br />
<br />
The following glitches may or may not occur in relation to suspending to RAM:<br />
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via ctrl-alt-del). This can be fixed by adding <tt>acpi_sleep=s3_bios</tt> to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1.<br />
* When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.<br />
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].<br />
* You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.<br />
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.<br />
* Crash on resume when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool].<br />
* If your suspend is failing, and a tail of /var/log/acpid shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions<br />
* Due to the fact that Sonoma chipset based laptops (T43, T43p) utilize the SATA layer for disk access and SATA does not have power-management support yet Suspend to RAM does not work on these machines. However, Jens Axboe's patch ([http://marc.theaimsgroup.com/?l=linux-kernel&m=111504542402455&w=2] LKML posting) provides SATA power-management support and makes Suspend to RAM work on the T43 at least. (Tested on 2.6.12rc6 which the patch applies to with some offsets. T43p not tested but should work as well.)<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12-rc6.diff 2.6.12-rc6 patch]<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff 2.6.12 patch]<br />
<br />
==Suspend to disk (Hibernate)==<br />
There are two drivers for this available:<br />
* swsusp, which is in the kernel and<br />
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself<br />
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].<br />
<br />
Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.<br />
<br />
===using swsusp===<br />
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.<br />
<br />
To enable it, go to <tt>Power management options</tt> and enable <tt>Power management support</tt> and <tt>Software Suspend</tt> in the kernel config menu. You'll also want to give the swap partition to suspend to in <tt>Default resume partition</tt>.<br />
<br />
In case you prefer to edit your config file directly, you should have the following three entries look like here...<br />
CONFIG_PM=y<br />
CONFIG_SOFTWARE_SUSPEND=y<br />
CONFIG_PM_STD_PARTITION="/dev/resume_partition"<br />
...where <tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)<br />
<br />
You can override the default resume partition anytime by giving <tt>resume=/dev/resume_partition</tt> as kernel boot parameter.<br />
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - loosing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.<br />
<br />
To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.<br />
<br />
Ideally you would do this from a script like <tt>/etc/acpi/actions/hibernate.sh</tt>. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.<br />
*any running mysql server<br />
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.<br />
<br />
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.<br />
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).<br />
<br />
If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:<br />
<br />
amixer set Master mute >/dev/null 2>&1<br />
amixer set PCM mute >/dev/null 2>&1<br />
amixer set Master unmute >/dev/null 2>&1<br />
amixer set PCM unmute >/dev/null 2>&1<br />
<br />
Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.<br />
<br />
===using SoftwareSuspend2===<br />
First apply Software Suspend 2 patches from http://softwaresuspend.berlios.de/ if they are not already in your kernel. I am running 2.6.11-rc4-nitro in a Thinkpad T30 2366.<br />
<br />
Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html<br />
<br />
These are the options for the kernel. You can change the <tt>/dev/hda5</tt> to your swap partition<br />
<br />
# Software Suspend 2<br />
CONFIG_SOFTWARE_SUSPEND2=y<br />
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y<br />
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y<br />
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y<br />
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y<br />
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/hda5"<br />
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set<br />
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y<br />
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set<br />
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set<br />
<br />
Next, compile and install the kernel<br />
<br />
In the meantime, add the following to the kernel parameters <tt>resume2=swap:/dev/hda5</tt>. Again change <tt>/dev/hda5</tt> to your swap partition.<br />
<br />
Install the hibernation script<br />
<br />
For [[:Category:Gentoo | Gentoo]] users: emerge hibernate-script<br /><br />
For [[:Category:Fedora_Core | Fedora Core]] users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br /><br />
For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://softwaresuspend.berlios.de/<br />
<br />
Debian users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your /etc/mkinitrd/scripts directory before creating initrd image.<br />
<br />
Restart using the new kernel and run the script to test it out.<br />
/usr/sbin/hibernate<br />
<br />
<br />
[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]</div>Jlthttps://www.thinkwiki.org/w/index.php?title=Embedded_Security_Subsystem&diff=6098Embedded Security Subsystem2005-06-21T22:57:52Z<p>Jlt: /* Linux Support */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:ESS.jpg|IBM Embedded Security Subsystem]] __NOTOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== The Embedded Security Subsystem ===<br />
The Embedded Security Subsystem is nothing but a chip installed on the Thinkpads mainboard that can take care of certain security related tasks conforming to the TCPA standard. It was first introduced among the T23 models and is now under the name Embedded Security Subsystem 2.0 an integral part of most of the modern Thinkpads. The functions of the chip are bound to three main groups:<br />
* public key functions<br />
* trusted boot functions<br />
* initialization and management functions<br />
<br />
The purpose of the whole thing is to keep the users sensitive data out of range from software based attacks (like viruses, internet attacks etc.). One way the chip offers to achieve this is by providing storage for keys along with the neccessary functions to handle them within itself, so that a i.e. a private key never has to leave the chip (can't be seen by any piece of software). Besides this there are more complex topics covered by the functionality of the chip. If you want to find out more about it you can find good documents on the [http://www.research.ibm.com/gsal/tcpa/ IBM Research TCPA resources page].<br />
</div><br />
|}<br />
<br />
==Linux Support==<br />
Two linux drivers are available, a [[tpm|classical one]] and a [[tpmdd|newer one]].<br />
Coverage of functionality of the first is unknown so far, the second is part of a bigger project aiming to provide a usable security framework.<br />
<br />
David Stafford (one of the developers of the tpm code at IBM) on March 10, 2005 sent me the most recent version of the tpm-kml code. With his permission, I quote his email:<br />
<br />
"I am attaching our latest driver and library.<br />
This version is in the process of kernel mailing list review, and<br />
will hopefully be accepted into the official kernel. It works<br />
much better across various 2.6 kernels. Note that this builds<br />
three modules tpm, tpm_atmel, and tpm_nsc. You modprobe the<br />
tpm_atmel (for all current shipping atmel based systems), or<br />
tpm_nsc (for the coming national based systems).<br />
<br />
Also note that there is a conflict with the snd-intel8x0<br />
kernel module (they each try to grab the LPC bus). You can<br />
either: load the tpm modules first (such as in initrd or<br />
rc.sysinit, before sound), or recompile the snd-intel8x0, turning<br />
off the MIDI and JOYSTICK support. The latest 2.6.11 version<br />
of snd-intel8x0 also reportedly fixes things."<br />
<br />
Compiling this library was easy. Compiling the driver on my 2.6.8-686 (debian testing) laptop failed. But the library works with the driver I compiled from the tpm-2.0 package IBM made available on its pages (see the links below).<br />
<br />
Gijs<br />
<br />
The T43 requires a patch posted to the LKML by Kylene Jo Hall: [http://marc.theaimsgroup.com/?l=linux-kernel&m=111884603309146&w=2 LKML posting]. An updated patch for linux 2.6.12 is available [http://shamrock.dyndns.org/~ln/linux/tpm_2.6.12.diff here].<br />
<br />
==Related Links==<br />
*[http://www.pc.ibm.com/us/think/thinkvantagetech/security.html IBMs ThinkVantage<sup>TM</sup> Technologies Embedded Security Subsystem page]<br />
*[http://www.pc.ibm.com/presentations/us/thinkvantage/56/index.html?shortcut=ess& IBMs ThinkVantage<sup>TM</sup> Technologies Flash presentation - Embedded Security Subsystem]<br />
*[http://www.research.ibm.com/gsal/tcpa/ IBM Research TCPA resources page]<br />
*[http://www.prosec.rub.de/trusted_grub.html Trusted Grub]<br />
<br />
==Models featuring this Technology==<br />
'''IBM Embedded Security Subsystem'''<br />
*ThinkPad {{R31}}<br />
*ThinkPad {{T23}}, {{T30}}<br />
*ThinkPad {{X23}}, {{X24}}<br />
'''IBM Embedded Security Subsystem 2.0'''<br />
*ThinkPad {{R32}}, {{R40}}, {{R50}}, {{R50p}}, {{R51}}, {{R52}}<br />
*ThinkPad {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}<br />
*ThinkPad {{X30}}, {{X31}}, {{X32}}, {{X40}}, {{X41}}, {{X41T}}<br />
[[Category:Glossary]]</div>Jlthttps://www.thinkwiki.org/w/index.php?title=Embedded_Security_Subsystem&diff=5837Embedded Security Subsystem2005-06-18T16:48:43Z<p>Jlt: /* Linux Support */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:ESS.jpg|IBM Embedded Security Subsystem]] __NOTOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== The Embedded Security Subsystem ===<br />
The Embedded Security Subsystem is nothing but a chip installed on the Thinkpads mainboard that can take care of certain security related tasks conforming to the TCPA standard. It was first introduced among the T23 models and is now under the name Embedded Security Subsystem 2.0 an integral part of most of the modern Thinkpads. The functions of the chip are bound to three main groups:<br />
* public key functions<br />
* trusted boot functions<br />
* initialization and management functions<br />
<br />
The purpose of the whole thing is to keep the users sensitive data out of range from software based attacks (like viruses, internet attacks etc.). One way the chip offers to achieve this is by providing storage for keys along with the neccessary functions to handle them within itself, so that a i.e. a private key never has to leave the chip (can't be seen by any piece of software). Besides this there are more complex topics covered by the functionality of the chip. If you want to find out more about it you can find good documents on the [http://www.research.ibm.com/gsal/tcpa/ IBM Research TCPA resources page].<br />
</div><br />
|}<br />
<br />
==Linux Support==<br />
Two linux drivers are available, a [[tpm|classical one]] and a [[tpmdd|newer one]].<br />
Coverage of functionality of the first is unknown so far, the second is part of a bigger project aiming to provide a usable security framework.<br />
<br />
David Stafford (one of the developers of the tpm code at IBM) on March 10, 2005 sent me the most recent version of the tpm-kml code. With his permission, I quote his email:<br />
<br />
"I am attaching our latest driver and library.<br />
This version is in the process of kernel mailing list review, and<br />
will hopefully be accepted into the official kernel. It works<br />
much better across various 2.6 kernels. Note that this builds<br />
three modules tpm, tpm_atmel, and tpm_nsc. You modprobe the<br />
tpm_atmel (for all current shipping atmel based systems), or<br />
tpm_nsc (for the coming national based systems).<br />
<br />
Also note that there is a conflict with the snd-intel8x0<br />
kernel module (they each try to grab the LPC bus). You can<br />
either: load the tpm modules first (such as in initrd or<br />
rc.sysinit, before sound), or recompile the snd-intel8x0, turning<br />
off the MIDI and JOYSTICK support. The latest 2.6.11 version<br />
of snd-intel8x0 also reportedly fixes things."<br />
<br />
Compiling this library was easy. Compiling the driver on my 2.6.8-686 (debian testing) laptop failed. But the library works with the driver I compiled from the tpm-2.0 package IBM made available on its pages (see the links below).<br />
<br />
Gijs<br />
<br />
The T43 requires a patch posted to the LKML by Kylene Jo Hall: [http://marc.theaimsgroup.com/?l=linux-kernel&m=111884603309146&w=2 LKML posting]<br />
<br />
==Related Links==<br />
*[http://www.pc.ibm.com/us/think/thinkvantagetech/security.html IBMs ThinkVantage<sup>TM</sup> Technologies Embedded Security Subsystem page]<br />
*[http://www.pc.ibm.com/presentations/us/thinkvantage/56/index.html?shortcut=ess& IBMs ThinkVantage<sup>TM</sup> Technologies Flash presentation - Embedded Security Subsystem]<br />
*[http://www.research.ibm.com/gsal/tcpa/ IBM Research TCPA resources page]<br />
*[http://www.prosec.rub.de/trusted_grub.html Trusted Grub]<br />
<br />
==Models featuring this Technology==<br />
'''IBM Embedded Security Subsystem'''<br />
*ThinkPad {{R31}}<br />
*ThinkPad {{T23}}, {{T30}}<br />
*ThinkPad {{X23}}, {{X24}}<br />
'''IBM Embedded Security Subsystem 2.0'''<br />
*ThinkPad {{R32}}, {{R40}}, {{R50}}, {{R50p}}, {{R51}}, {{R52}}<br />
*ThinkPad {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}<br />
*ThinkPad {{X30}}, {{X31}}, {{X32}}, {{X40}}, {{X41}}, {{X41T}}<br />
[[Category:Glossary]]</div>Jlthttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=5812Fglrx2005-06-18T16:15:58Z<p>Jlt: /* Problems & Help */</p>
<hr />
<div>== ATI drivers for Linux ==<br />
Linux ATI driver for Radeon, FireGL and Mobility boards<br />
<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
I've noticed appx 40% speed gain with ATI fglrx vs open source drivers. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (ctrl-alt-plus, ctrl-alt-minus), and garbage while using VMware.<br />
<br />
=== Project Homepage / Availability ===<br />
http://www.ati.com/support/drivers/linux/radeon-linux.html<br />
<br />
=== Status ===<br />
Current version: 8.14.13 (9th June 2005)<br />
<br />
=== Problems & Help ===<br />
<br />
'''Driver Version 8.8.25:''' The following patch may be needed for kernels >= 2.6.10:<br />
[http://www.rage3d.com/board/showthread.php?t=33798874 http://www.rage3d.com/board/showthread.php?t=33798874]<br />
<br />
'''Driver Version 8.8.25:''' For kernels >= 2.6.11-rc1 try the following patch:<br />
http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch<br />
<br />
'''If the ATI driver works only without the hardware acceleration''', take into consideration that fglrx_dri.so was linked<br />
against libstdc++.so.5 which may not be present if your system uses gcc-3.4. To fix this, compile gcc-3.3.5 <br />
and copy libstdc++.so.5* to /usr/lib and update the dynamic linker cache.<br />
<br />
'''Troubles using software suspend''' : when the computer comes back of suspend, X only displays a garbaged image and the computer is frozen. You have to install [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] and use it to save/restore the video card state. If you use swsusp2 scripts you just have to uncomment ''"EnableVbetool yes"'' in ''/etc/hibernate/hibernate.conf''. Tested with kernel 2.6.10, Debian packaged ATI drivers and [http://www.suspend2.net swsusp2] patch on a IBM Thinkpad T42p. <br />
<br />
This does not seem to work on the T43: The machine displays a sligthly garbaged image and is frozen upon resume. (It does work as long as the fglrx kernel driver is not inserted.) (Tested on kernel 2.6.12-rc6 with suspend2 2.1.9 and ATI driver version 8.14.13.)<br />
<br />
'''Troubles with large RAM''' : The driver (version 8.14.13 tested on a T43) does not seem to be able to cope with large amounts of RAM: with 512 MB it works, with 1.5 GB it crashes the machine as soon as X is started. The problem is present only if the ''fglrx'' kernel module is loaded, but independetly of whether ''"CONFIG_HIGHMEM"'' is enabled (I.e. the actual amount of RAM available to the system does not seem to matter, but rather how mauch RAM is physically installed.).<br />
<br />
=== Packages ===<br />
*[[:Category:Debian | Debian]] Packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html<br />
*[[:Category:SuSE | SuSE]] Packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/<br />
*[[:Category:Gentoo | Gentoo]] {{cmdroot|emerge media-video/ati-drivers}}<br />
<br />
=== Useful links === <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www2.ati.com/drivers/linux/linux_8.12.10.html ATI Proprietary Linux Release Notes] <tt>(for 8.12.10)</tt><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://ati.cchtml.com/ Unofficial community ATI bugzilla] Very newly setup (!) bugzilla, which might grow to be a source for information about ATI bugs. Might then be monitored by ATI guys ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]). We will see how this develops.<br />
<br />
[[Category:Drivers]] [[Category:Debian]] [[Category:SuSE]] [[Category:Gentoo]]</div>Jlthttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=5796Fglrx2005-06-13T11:31:24Z<p>Jlt: /* Problems & Help */</p>
<hr />
<div>== ATI drivers for Linux ==<br />
Linux ATI driver for Radeon, FireGL and Mobility boards<br />
<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
I've noticed appx 40% speed gain with ATI fglrx vs open source drivers. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (ctrl-alt-plus, ctrl-alt-minus), and garbage while using VMware.<br />
<br />
=== Project Homepage / Availability ===<br />
http://www.ati.com/support/drivers/linux/radeon-linux.html<br />
<br />
=== Status ===<br />
Current version: 8.14.13 (9th June 2005)<br />
<br />
=== Problems & Help ===<br />
<br />
'''Driver Version 8.8.25:''' The following patch may be needed for kernels >= 2.6.10:<br />
[http://www.rage3d.com/board/showthread.php?t=33798874 http://www.rage3d.com/board/showthread.php?t=33798874]<br />
<br />
'''Driver Version 8.8.25:''' For kernels >= 2.6.11-rc1 try the following patch:<br />
http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch<br />
<br />
'''If the ATI driver works only without the hardware acceleration''', take into consideration that fglrx_dri.so was linked<br />
against libstdc++.so.5 which may not be present if your system uses gcc-3.4. To fix this, compile gcc-3.3.5 <br />
and copy libstdc++.so.5* to /usr/lib and update the dynamic linker cache.<br />
<br />
'''Troubles using software suspend''' : when the computer comes back of suspend, X only displays a garbaged image and the computer is frozen. You have to install [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] and use it to save/restore the video card state. If you use swsusp2 scripts you just have to uncomment ''"EnableVbetool yes"'' in ''/etc/hibernate/hibernate.conf''. Tested with kernel 2.6.10, Debian packaged ATI drivers and [http://www.suspend2.net swsusp2] patch on a IBM Thinkpad T42p. <br />
<br />
This does not seem to work on the T43: The machine displays a sligthly garbaged image and is frozen upon resume. (It does work as long as the fglrx kernel driver is not inserted.) (Tested on kernel 2.6.12-rc6 with suspend2 2.1.9 and ATI driver version 8.14.13.)<br />
<br />
=== Packages ===<br />
*[[:Category:Debian | Debian]] Packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html<br />
*[[:Category:SuSE | SuSE]] Packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/<br />
*[[:Category:Gentoo | Gentoo]] {{cmdroot|emerge media-video/ati-drivers}}<br />
<br />
=== Useful links === <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www2.ati.com/drivers/linux/linux_8.12.10.html ATI Proprietary Linux Release Notes] <tt>(for 8.12.10)</tt><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://ati.cchtml.com/ Unofficial community ATI bugzilla] Very newly setup (!) bugzilla, which might grow to be a source for information about ATI bugs. Might then be monitored by ATI guys ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]). We will see how this develops.<br />
<br />
[[Category:Drivers]] [[Category:Debian]] [[Category:SuSE]] [[Category:Gentoo]]</div>Jlthttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=5667Fglrx2005-06-13T11:30:58Z<p>Jlt: /* Problems & Help */</p>
<hr />
<div>== ATI drivers for Linux ==<br />
Linux ATI driver for Radeon, FireGL and Mobility boards<br />
<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
I've noticed appx 40% speed gain with ATI fglrx vs open source drivers. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (ctrl-alt-plus, ctrl-alt-minus), and garbage while using VMware.<br />
<br />
=== Project Homepage / Availability ===<br />
http://www.ati.com/support/drivers/linux/radeon-linux.html<br />
<br />
=== Status ===<br />
Current version: 8.14.13 (9th June 2005)<br />
<br />
=== Problems & Help ===<br />
<br />
'''Driver Version 8.8.25:''' The following patch may be needed for kernels >= 2.6.10:<br />
[http://www.rage3d.com/board/showthread.php?t=33798874 http://www.rage3d.com/board/showthread.php?t=33798874]<br />
<br />
'''Driver Version 8.8.25:''' For kernels >= 2.6.11-rc1 try the following patch:<br />
http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch<br />
<br />
'''If the ATI driver works only without the hardware acceleration''', take into consideration that fglrx_dri.so was linked<br />
against libstdc++.so.5 which may not be present if your system uses gcc-3.4. To fix this, compile gcc-3.3.5 <br />
and copy libstdc++.so.5* to /usr/lib and update the dynamic linker cache.<br />
<br />
'''Troubles using software suspend''' : when the computer comes back of suspend, X only displays a garbaged image and the computer is frozen. You have to install [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] and use it to save/restore the video card state. If you use swsusp2 scripts you just have to uncomment ''"EnableVbetool yes"'' in ''/etc/hibernate/hibernate.conf''. Tested with kernel 2.6.10, Debian packaged ATI drivers and [http://www.suspend2.net swsusp2] patch on a IBM Thinkpad T42p. <br />
<br />
This does not seem to work on the T43: The machine displays a sligthly garbaged image and is frozen upon resume. (It does work as long as the fglrx kernel driver is not inserted.) (Tested on kernel 2.6.12-rc6 with suspend2 2.1.9 and ATI driver version 8.14.13)<br />
<br />
=== Packages ===<br />
*[[:Category:Debian | Debian]] Packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html<br />
*[[:Category:SuSE | SuSE]] Packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/<br />
*[[:Category:Gentoo | Gentoo]] {{cmdroot|emerge media-video/ati-drivers}}<br />
<br />
=== Useful links === <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www2.ati.com/drivers/linux/linux_8.12.10.html ATI Proprietary Linux Release Notes] <tt>(for 8.12.10)</tt><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://ati.cchtml.com/ Unofficial community ATI bugzilla] Very newly setup (!) bugzilla, which might grow to be a source for information about ATI bugs. Might then be monitored by ATI guys ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]). We will see how this develops.<br />
<br />
[[Category:Drivers]] [[Category:Debian]] [[Category:SuSE]] [[Category:Gentoo]]</div>Jlthttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=5666Fglrx2005-06-13T11:29:12Z<p>Jlt: /* Problems & Help */</p>
<hr />
<div>== ATI drivers for Linux ==<br />
Linux ATI driver for Radeon, FireGL and Mobility boards<br />
<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
I've noticed appx 40% speed gain with ATI fglrx vs open source drivers. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (ctrl-alt-plus, ctrl-alt-minus), and garbage while using VMware.<br />
<br />
=== Project Homepage / Availability ===<br />
http://www.ati.com/support/drivers/linux/radeon-linux.html<br />
<br />
=== Status ===<br />
Current version: 8.14.13 (9th June 2005)<br />
<br />
=== Problems & Help ===<br />
<br />
'''Driver Version 8.8.25:''' The following patch may be needed for kernels >= 2.6.10:<br />
[http://www.rage3d.com/board/showthread.php?t=33798874 http://www.rage3d.com/board/showthread.php?t=33798874]<br />
<br />
'''Driver Version 8.8.25:''' For kernels >= 2.6.11-rc1 try the following patch:<br />
http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch<br />
<br />
'''If the ATI driver works only without the hardware acceleration''', take into consideration that fglrx_dri.so was linked<br />
against libstdc++.so.5 which may not be present if your system uses gcc-3.4. To fix this, compile gcc-3.3.5 <br />
and copy libstdc++.so.5* to /usr/lib and update the dynamic linker cache.<br />
<br />
'''Troubles using software suspend''' : when the computer comes back of suspend, X only displays a garbaged image and the computer is frozen. You have to install [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] and use it to save/restore the video card state. If you use swsusp2 scripts you just have to uncomment ''"EnableVbetool yes"'' in ''/etc/hibernate/hibernate.conf''. Tested with kernel 2.6.10, Debian packaged ATI drivers and [http://www.suspend2.net swsusp2] patch on a IBM Thinkpad T42p. This does not seem to work on the T43: The machine displays a sligthly garbaged image and is frozen upon resume. (It does work as long as the fglrx kernel driver is not inserted.)<br />
<br />
=== Packages ===<br />
*[[:Category:Debian | Debian]] Packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html<br />
*[[:Category:SuSE | SuSE]] Packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/<br />
*[[:Category:Gentoo | Gentoo]] {{cmdroot|emerge media-video/ati-drivers}}<br />
<br />
=== Useful links === <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www2.ati.com/drivers/linux/linux_8.12.10.html ATI Proprietary Linux Release Notes] <tt>(for 8.12.10)</tt><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://ati.cchtml.com/ Unofficial community ATI bugzilla] Very newly setup (!) bugzilla, which might grow to be a source for information about ATI bugs. Might then be monitored by ATI guys ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]). We will see how this develops.<br />
<br />
[[Category:Drivers]] [[Category:Debian]] [[Category:SuSE]] [[Category:Gentoo]]</div>Jlthttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=5665Fglrx2005-06-13T11:28:22Z<p>Jlt: /* Problems & Help */</p>
<hr />
<div>== ATI drivers for Linux ==<br />
Linux ATI driver for Radeon, FireGL and Mobility boards<br />
<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
I've noticed appx 40% speed gain with ATI fglrx vs open source drivers. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (ctrl-alt-plus, ctrl-alt-minus), and garbage while using VMware.<br />
<br />
=== Project Homepage / Availability ===<br />
http://www.ati.com/support/drivers/linux/radeon-linux.html<br />
<br />
=== Status ===<br />
Current version: 8.14.13 (9th June 2005)<br />
<br />
=== Problems & Help ===<br />
<br />
'''Driver Version 8.8.25:''' The following patch may be needed for kernels >= 2.6.10:<br />
[http://www.rage3d.com/board/showthread.php?t=33798874 http://www.rage3d.com/board/showthread.php?t=33798874]<br />
<br />
'''Driver Version 8.8.25:''' For kernels >= 2.6.11-rc1 try the following patch:<br />
http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch<br />
<br />
'''If the ATI driver works only without the hardware acceleration''', take into consideration that fglrx_dri.so was linked<br />
against libstdc++.so.5 which may not be present if your system uses gcc-3.4. To fix this, compile gcc-3.3.5 <br />
and copy libstdc++.so.5* to /usr/lib and update the dynamic linker cache.<br />
<br />
'''Troubles using software suspend''' : when the computer comes back of suspend, X only displays a garbaged image and the computer is frozen. You have to install [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] and use it to save/restore the video card state. If you use swsusp2 scripts you just have to uncomment ''"EnableVbetool yes"'' in ''/etc/hibernate/hibernate.conf''. Tested with kernel 2.6.10, Debian packaged ATI drivers and [http://www.suspend2.net swsusp2] patch on a IBM Thinkpad T42p. This does not seem to work on the T43: The machine displays a sligthly garbaged image and is frozen upon resume.<br />
<br />
=== Packages ===<br />
*[[:Category:Debian | Debian]] Packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html<br />
*[[:Category:SuSE | SuSE]] Packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/<br />
*[[:Category:Gentoo | Gentoo]] {{cmdroot|emerge media-video/ati-drivers}}<br />
<br />
=== Useful links === <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www2.ati.com/drivers/linux/linux_8.12.10.html ATI Proprietary Linux Release Notes] <tt>(for 8.12.10)</tt><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://ati.cchtml.com/ Unofficial community ATI bugzilla] Very newly setup (!) bugzilla, which might grow to be a source for information about ATI bugs. Might then be monitored by ATI guys ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]). We will see how this develops.<br />
<br />
[[Category:Drivers]] [[Category:Debian]] [[Category:SuSE]] [[Category:Gentoo]]</div>Jlt