https://www.thinkwiki.org/w/api.php?action=feedcontributions&user=Rasto&feedformat=atomThinkWiki - User contributions [en]2024-03-28T08:24:47ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=Gkrellm-HwMonBat&diff=49791Gkrellm-HwMonBat2010-10-13T22:10:19Z<p>Rasto: /* Description */</p>
<hr />
<div>== Description == <br />
gkrellm-HwMonBat is meant as a replacement for the default battery meter in [[GKrellM]]. <br />
It should look like default, only it optionally shows time remaining/power consumption. On old kernels which don't provide the /proc/acpi/battery interface, one can use [[Gkrellm-ThinkBat]]. <br />
<br />
Latest version: 0.3.2 (2010-10-12)<br />
<br />
== Prerequisites ==<br />
<br />
* [[GKrellM]] (packaged by most Linux distributions)<br />
<br />
== Installation ==<br />
Download the [http://www.100acrewood.org/~rasto/hwmonbat/gkrellm-hwmonbat-latest.tar.gz tarball]. <br />
{{cmduser|make}}<br />
{{cmduser|make install}}<br />
this installs gkrellm-hwmonbat.so to {{path|~/.gkrellm2/plugins}}. You can copy it manually elsewhere. Gtk2.0-dev <br />
needs to be installed in order to compile.<br />
<br />
== Screenshot ==<br />
[[image:gkrellm-thinkbat.png]] [[image:gkrellm-thinkbat2.png]]<br />
<br />
== Bugs ==<br />
Please report any bugs or suggestions to [[User_talk:rasto]]. <br />
<br />
[[Category:Tools]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Gkrellm-HwMonBat&diff=49753Gkrellm-HwMonBat2010-10-12T09:45:42Z<p>Rasto: â†Created page with '== Description == gkrellm-HwMonBat is meant as a replacement for the default battery meter in GKrellM. It should look like default, only it optionally shows time rem...'</p>
<hr />
<div>== Description == <br />
gkrellm-HwMonBat is meant as a replacement for the default battery meter in [[GKrellM]]. <br />
It should look like default, only it optionally shows time remaining/power consumption. It currently supports only <br />
one battery. On old kernels which don't provide the /proc/acpi/battery interface, one can use [[Gkrellm-ThinkBat]]. <br />
<br />
Latest version: 0.3.2 (2010-10-12)<br />
<br />
== Prerequisites ==<br />
<br />
* [[GKrellM]] (packaged by most Linux distributions)<br />
<br />
== Installation ==<br />
Download the [http://www.100acrewood.org/~rasto/hwmonbat/gkrellm-hwmonbat-latest.tar.gz tarball]. <br />
{{cmduser|make}}<br />
{{cmduser|make install}}<br />
this installs gkrellm-hwmonbat.so to {{path|~/.gkrellm2/plugins}}. You can copy it manually elsewhere. Gtk2.0-dev <br />
needs to be installed in order to compile.<br />
<br />
== Screenshot ==<br />
[[image:gkrellm-thinkbat.png]] [[image:gkrellm-thinkbat2.png]]<br />
<br />
== Bugs ==<br />
Please report any bugs or suggestions to [[User_talk:rasto]]. <br />
<br />
[[Category:Tools]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Gkrellm-ThinkBat&diff=49752Gkrellm-ThinkBat2010-10-12T09:41:04Z<p>Rasto: /* Description */</p>
<hr />
<div>== Description == <br />
gkrellm-ThinkBat was meant as a replacement for the default battery meter in [[GKrellM]]. <br />
It should look like default, only it optionally shows time remaining/power consumption. It currently supports only <br />
one battery. It is superceded by [[Gkrellm-HwMonBat]] on newer kernels which provide the /proc/acpi/battery interface. <br />
<br />
Latest version: 0.2.2 (2006-02-13)<br />
<br />
== Prerequisites ==<br />
<br />
* [[GKrellM]] (packaged by most Linux distributions)<br />
* [[tp_smapi]] kernel module<br />
<br />
== Installation ==<br />
Download the [http://www.ksp.sk/~rasto/gkrellm-thinkbat/gkrellm-thinkbat-latest.tar.gz tarball]. <br />
{{cmduser|make}}<br />
{{cmduser|make install}}<br />
this installs gkrellm-thinkbat.so to {{path|~/.gkrellm2/plugins}}. You can copy it manually elsewhere.<br />
<br />
== Screenshot ==<br />
[[image:gkrellm-thinkbat.png]] [[image:gkrellm-thinkbat2.png]]<br />
<br />
== Bugs ==<br />
Please report any bugs or suggestions to [[User_talk:rasto]]. <br />
<br />
== Patches ==<br />
Thomas Coppi has a patch for supporting a second battery(it will show the status of whichever battery is being charged/discharged instead of only BAT0) [http://thisnukes4u.net/files/0001-Support-a-second-battery-if-one-is-present.patch here]<br />
<br />
[[Category:Tools]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Gkrellm-ThinkBat&diff=49751Gkrellm-ThinkBat2010-10-12T09:40:50Z<p>Rasto: /* Description */</p>
<hr />
<div>== Description == <br />
gkrellm-ThinkBat was meant as a replacement for the default battery meter in [[GKrellM]]. <br />
It should look like default, only it optionally shows time remaining/power consumption. It currently supports only <br />
one battery. It is superceded by [[gkrellm-HwMonBat]] on newer kernels which provide the /proc/acpi/battery interface. <br />
<br />
Latest version: 0.2.2 (2006-02-13)<br />
<br />
== Prerequisites ==<br />
<br />
* [[GKrellM]] (packaged by most Linux distributions)<br />
* [[tp_smapi]] kernel module<br />
<br />
== Installation ==<br />
Download the [http://www.ksp.sk/~rasto/gkrellm-thinkbat/gkrellm-thinkbat-latest.tar.gz tarball]. <br />
{{cmduser|make}}<br />
{{cmduser|make install}}<br />
this installs gkrellm-thinkbat.so to {{path|~/.gkrellm2/plugins}}. You can copy it manually elsewhere.<br />
<br />
== Screenshot ==<br />
[[image:gkrellm-thinkbat.png]] [[image:gkrellm-thinkbat2.png]]<br />
<br />
== Bugs ==<br />
Please report any bugs or suggestions to [[User_talk:rasto]]. <br />
<br />
== Patches ==<br />
Thomas Coppi has a patch for supporting a second battery(it will show the status of whichever battery is being charged/discharged instead of only BAT0) [http://thisnukes4u.net/files/0001-Support-a-second-battery-if-one-is-present.patch here]<br />
<br />
[[Category:Tools]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=User:Rasto&diff=49750User:Rasto2010-10-12T09:38:49Z<p>Rasto: Replaced content with '600E, T43, T61, X60, X201'</p>
<hr />
<div>600E, T43, T61, X60, X201</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Template:ThinkWiki_News&diff=36209Template:ThinkWiki News2008-01-24T16:18:46Z<p>Rasto: It's a new year, ya know...</p>
<hr />
<div>{|<br />
{{News|18.01.2008|Again ThinkWiki got shiny new lightning fast [[ThinkWiki:Hardware|hardware]].}}<br />
{{News|14.11.2007|[http://www.lesswatts.org lesswatts.org] now hosts the [http://www.lesswatts.org/projects/acpi/ Linux ACPI] project, as well as [http://www.lesswatts.org/projects/powertop/ powertop] and many other important power management projects.}}<br />
{{News|19.10.2007|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.11.0]]. We apologize for some downtime on Oct. 15th and 16th.}}<br />
{{News|11.10.2007|The ThinkPad turns 15 years old!}}<br />
{{News|13.06.2007|A preliminary version of the reverse-engineered R500 driver is [http://lwn.net/Articles/237920/ available].}}<br />
{{News|06.06.2007|ThinkWiki finally runs on new [[ThinkWiki:Hardware|hardware]].}}<br />
{{News|22.05.2007|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.10.0]].}}<br />
{{News|13.05.2007|Intel released [http://www.linuxpowertop.org/ PowerTOP], helps to prolong battery life.}}<br />
|}</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=26458Fglrx2006-11-16T18:43:46Z<p>Rasto: /* Availability / Project Homepage */</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 x11-drivers/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 />
*{{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 />
<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.31.5 (15th November 2006)<br />
<br />
Major changes:<br />
* 8.31.5: no new features, only bugfixes<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 />
{{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 />
=== 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 />
=== 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}}<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>Rastohttps://www.thinkwiki.org/w/index.php?title=Template:Industry_News&diff=26184Template:Industry News2006-11-03T14:51:07Z<p>Rasto: </p>
<hr />
<div>03.11.2006: New [[fglrx]] driver version 8.30.3 released<br />
<br />
20.09.2006: New [[fglrx]] driver version 8.29.6 released<br />
<br />
18.08.2006: New [[fglrx]] driver version 8.28.8 released<br />
<br />
04.08.2005: According to [http://www.desktoplinux.com/news/NS7778908329.html desktoplinux.com], Lenovo will sell Thinkpads with SuSE Enterprise Desktop 10 preloaded.<br />
<br />
28.07.2006: New [[fglrx]] driver version 8.27.10 released including support for XOrg 7.1<br />
<br />
27.06.2006: New [[fglrx]] driver version 8.26.18 released<br />
<br />
05.06.2006: According to CNET [http://news.com.com/2100-1003_3-6080115.html?part=rss&tag=6080115&subj=news], Lenovo is now denying dropping official Linux support.<br />
<br />
04.06.2006: Sad news! According to CRN [http://www.crn.com/sections/breakingnews/breakingnews.jhtml?articleId=188701277], Lenovo drops official Linux support for its PCs, including ThinkPads.<br />
<br />
24.05.2006 New [[fglrx]] driver version 8.25.18 released<br />
<br />
15.04.2006 Several news ([http://www.notebookreview.com/default.asp?newsID=2843], [http://www.graphiland.fr/produc_t/produc1b.asp?Code=X60&Ed=]) appeared that the next Lenovo models will be the {{R60}}, {{Z61m}}, {{Z61t}} and a new Tablet PC {{X60t}}.</div>Rastohttps://www.thinkwiki.org/w/index.php?title=User_talk:Rasto&diff=22558User talk:Rasto2006-05-31T05:59:10Z<p>Rasto: /* ateros Free software drivers */</p>
<hr />
<div>Hei,<br />
<br />
sorry, my mistake with the fglrx drivers. Didn't think of that there's a source kernel module part., but of course you're right.<br />
<br />
About the date... if you place <nowiki>~~~~</nowiki> (four tildes) in your edit, it will be replaced by your linkified username plus timestamp.<br />
<br />
[[User:Wyrfel|Wyrfel]] 04:36, 26 January 2006 (CET)<br />
----<br />
Thanks :-). There's one more thing that bothers me, but I'm not quite certain about this, so I didn't add it straight away. <br />
I did fglrx installs by running ati-installer. The X11 version doesn't however report any errors most of the time, also when there are. <br />
Also. When it fnishes successfully, it leaves the *.ko files in /lib/modules/fglrx, and doesn't copy them to /lib/modules/linux-whatever/fglrx. <br />
At least very often. I'm using a official kernel, not a debian one. Perhaps this causes some of the confusion about fglrx? Also- it can be, that <br />
you install a new version and the old modules are still being loaded, and therefore accel works and you don't notice anything?<br />
<br />
[[User:Rasto|Rasto]] 14:11, 26 January 2006 (CET)<br />
<br />
<br />
<br />
== ateros Free software drivers ==<br />
<br />
hello you seems to want a free software driver for yout atheros card<br />
the ath-driver isn't the only free software driver you also have someone that has ported the openHal driver to linux<br />
so you have:<br />
*Open BSD that have a 100% free software driver that work(i haven't tested it) (the atheros card doesn't have a firmware so it's 200% free software)<br />
*a linux port of this OpenHAL http://pdos.csail.mit.edu/~jbicket/openhal/<br />
<br />
i have tested the OpenHAL port to linux but it gives me an error while compiling with the r1443 version<br />
# make<br />
Makefile.inc:215: *** TARGET i386-elf is invalid, valid targets are: . Stop.<br />
<br />
mabe you'll have more chance and so you could tell what are the software requirements<br />
by the way uudecode(that is needed) is in the app-arch/sharutils package under gentoo(so you will be able to find it with the name) <br />
<br />
please respond here because i watch this page(i do not have any ibm laptop but google sent me there while searching for some information on the gcc suport of the pentium M(it difers a lot from a P6 core))<br />
<br />
<br />
Actually, I'm not really interested. Madwifi works great and openHAL's support is probably much more limited. There is a long dragging argument <br />
against openHAL, saying it actually violates Atheros' copyright. I'll rather not start this discussion here, this is not the place. <br />
So I will be of no help, as I got no time. Sorry. <br />
<br />
[[User:Rasto|Rasto]] 07:59, 31 May 2006 (CEST)</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Gkrellm-ThinkBat&diff=22004Gkrellm-ThinkBat2006-04-30T09:38:21Z<p>Rasto: /* Description */</p>
<hr />
<div>== Description == <br />
gkrellm-ThinkBat is meant as a replacement for the default battery meter in [http://www.gkrellm.net Gkrellm]. <br />
It should look like default, only it optionally shows time remaining/power consumption. It currently supports only <br />
one battery. <br />
<br />
Latest version: 0.2.2 (2006-02-13)<br />
<br />
== Prerequisites ==<br />
<br />
* [http://freshmeat.net/redir/gkrellm/32404/url_homepage/www.gkrellm.net gkrellm] (packaged by most Linux distributions)<br />
* [[tp_smapi]] kernel module<br />
<br />
== Installation ==<br />
Download the [http://www.ksp.sk/~rasto/gkrellm-thinkbat/gkrellm-thinkbat-latest.tar.gz tarball]. <br />
{{cmduser|make}}<br />
{{cmduser|make install}}<br />
this installs gkrellm-thinkbat.so to {{path|~/.gkrellm2/plugins}}. You can copy it manually elsewhere.<br />
<br />
== Screenshot ==<br />
[[image:gkrellm-thinkbat.png]] [[image:gkrellm-thinkbat2.png]]<br />
<br />
== Bugs ==<br />
Please report any bugs or suggestions to [[User_talk:rasto]]. <br />
<br />
<br />
[[Category:Tools]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=IBM_11a/b/g_Wireless_LAN_Mini_PCI_Adapter_II&diff=21947IBM 11a/b/g Wireless LAN Mini PCI Adapter II2006-04-26T17:33:01Z<p>Rasto: XR works out of the box, there is no firmware on atheros chips and Super A/G can be enabled.</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<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 />
=== IBM 11a/b/g Wireless LAN Mini PCI Adapter II ===<br />
This is a Mini-PCI WiFi Adapter that is installed in a Mini-PCI slot<br />
<br />
=== Features ===<br />
* Chipset: Atheros AR5004X<br />
* Radio Chip: Atheros AR5112<br />
* MAC Processor: Atheros AR5213<br />
* IEEE Standards: 802.11a, 802.11b, 802.11g<br />
* PCI ID: 168c:1014<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:mini-pci-wifi-card.gif|Mini-PCI WiFi Adapter]]<br />
|}<br />
<br />
=== IBM Partnumbers ===<br />
'''Ambit parts'''<br><br />
IBM Option PN (WW): 73P4301<br><br />
IBM Option PN (Philippines, Singapore, Indonesia, Taiwan, China): 73P4302<br><br />
IBM Option PN (Japan): 73P4303<br><br />
IBM FRU PN (WW): 93P4262<br><br />
IBM FRU PN (Philippines, Singapore, Indonesia, Taiwan, China): 93P4264<br><br />
IBM FRU PN (Japan): 93P4266<br><br />
<br />
'''Bartlett parts'''<br><br />
IBM FRU PN (US): 27K9944<br><br />
IBM FRU PN (EU): 27K9946<br><br />
IBM FRU PN (Japan): 27K9948<br><br />
IBM FRU PN (Taiwan): 27K9999<br><br />
<br />
=== Also known (in IBM literature) as.... ===<br />
* 802.11a/b/g Ambit wireless Card<br />
* 802.11a/b/g Bartlett Wireless Card<br />
* ThinkPad 11a/b/g Mini PCI Adapter II<br />
<br />
=== Additional features ===<br />
The chipset itself supports Atheros eXtended Range (XR) technology, and Atheros [[Super A/G]] (Turbo) modes, but this functionality may be disabled.<br />
<br />
=== Linux WiFi driver ===<br />
This is an Atheros chip and works with the [[Madwifi]] driver "out of the box". This card will be also detected by open-source [http://www.ath-driver.org ath-driver], but as of <br />
now (end of January '06), it doesn't support actual wireless operations. <br />
<br />
Make sure that your kernel supports "CONFIG_SECURITY_CAPABILITIES", or you might get some message from the Atheros hal that it does not support all features.<br />
<br />
=== ThinkPads this card may be found in ===<br />
* {{R51}}, {{R52}}<br />
* {{T41p}},{{T42p}},{{T43}}, {{T43p}}<br />
* {{X32}}<br />
* {{X40}}, {{X41}}<br />
* {{Z60m}}<br />
<br />
=== Related Links ===<br />
*Specifications: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57210 MIGR-57210]<br />
*Users Guide: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57217 MIGR-57217]<br />
*Service Parts: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57214 MIGR-57214]<br />
*War stories: [[MCR's laptop death]]<br />
<br />
<br />
[[Category:Components]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Gkrellm-ThinkBat&diff=21512Talk:Gkrellm-ThinkBat2006-04-11T15:09:33Z<p>Rasto: </p>
<hr />
<div>v0.2.1 works perfectly on my T43. Great job!<br />
<br />
--[[User:Thinker|Thinker]] 19:58, 10 February 2006 (CET)<br />
----<br />
<br />
mine doesn't show the wattage like in the screenshot ... Any suggestions?<br />
<br />
--[[User:Papi|Papi]] 23:25, 3 April 2006 (CEST)<br />
<br />
It doesn't show it at all, or it is 0 or such? <br />
If it doesn't show it at all, you should go to Gkrellm Configuration panel (click on GkrellM and hit F1), <br />
go to thinkbat and check "Show estimated remaining time and power consumption"<br />
<br />
--[[User:Rasto|Rasto]] 17:09, 11 April 2006 (CEST)</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Problems_with_SATA_and_Linux&diff=21503Talk:Problems with SATA and Linux2006-04-11T07:59:52Z<p>Rasto: /* occasional hang upon resume with various kernels */</p>
<hr />
<div>__TOC__<br />
<br />
I'm running gentoo on my T43; I had problems with X11 (opensource radeon driver) and a SATA-patched kernel (I tried both 2.6.14 and 2.6.15-gentoo). Suspend to RAM worked nicely, but starting X freezed the machine after a short time. I tried removing radeonfb from the kernel; with vesafb, everything seems to work.<br />
<br />
-- Stefan, 10 Jan 2006<br />
<br />
--------<br />
That's strange - with the libata passthrough (IDE driver not in kernel) as set up in the text, my t43p DVD drive also will not record as hinted in the wikipage... DMA works fine, so DVD playing / ripping is smooth and quick. CD record functions also are absent. I have PATA enabled, and the suspend + SMART patches applied over 2.6.14.2.<br />
--------<br />
I can confirm this with 2.6.14.4, however with 2.6.15/15.1 with sata_pm patch it works.<br />
<br />
-- Rasto, 24 Jan 2006<br />
<br />
--------<br />
regarding the "BIOS error 2010 on user-installed hard disk":<br />
the text says that corruption occurs if you use a harddisk without the specific ibm bios. would be interesting if it is possible to fix this problem in the kernel so that you can use any disk and the kernel doesn't use specific ATA commands which are known to cause problems.<br />
<br />
in the tabook i didn't find any specification of the SATA bridge. it would be interesting:<br />
1) what type it is<br />
2) if it is fixed on the mainboard or if it is possible to solder in a new one<br />
<br />
----<br />
<br />
Another interesting question is whether these ThinkPads can be hacked to accept a real SATA system disk, by bypassing the SATA-to-PATA bridge (this would probably involve some soldering and cutting). If the BIOS can also handle that then it may come in handy, since some new high-capacity 2.5" disks have only SATA versions.<br />
--[[User:Thinker|Thinker]] 02:56, 8 Oct 2005 (CEST)<br />
<br />
----<br />
<br />
'''Z series'''<br />
<br />
Since the Z series uses a SATA controller and disk, without the bridge, would it be possible to make SATA ATAPI support as a module that you could load only when using the optical drive? Then, for everyday use, the experimental options of PATA and ATAPI with ata_piix would not be needed, moving you one step further in the direction of stability.<br />
<br />
----<br />
<br />
I have an R52 with Ubuntu Breezy and no problems with SATA (I personally asked the developers to include the needed patches).<br />
<br />
However, I'd like to know wheter there are any advantages with this configuration. Future proof? Power saving? Speed?<br />
<br />
Anybody cares to comment?<br />
<br />
-- [[User:Micampe|Michele]]<br />
<br />
Straight SATA, like in the Z60m/t, will provide better upgrade options in the long run (the hard disk industry is slowly but surely moving to SATA), and maybe a small performance increase if your drive, controller and OS support command queueing (they probably don't). However, with the hybrid ThinkPad models that use a SATA-to-PATA bridge, like your R52, you get all the drawbacks and none of the benefits; plus there's the horrible issue with [[Problem with non-ThinkPad hard disks|drive compatibility]]. My impression is that Lenovo did this just as a convenient (for them!) transition path, in order to use new chipsets without comitting to (temporarily) scarcer and more expensive drives. In any case, they didn't even have the decency to make the UltraBay Slim accept SATA drives. <br />
<br />
--[[User:Thinker|Thinker]] 18:10, 3 Nov 2005 (CET)<br />
----<br />
There is a [[UltraBay Slim SATA HDD Adapter]], but only compatible with the Z series (at least for the moment).<br />
<br />
--[[User:Tonko|Tonko]] 03:12, 4 Nov 2005 (CET)<br />
<br />
== updated libata_passthru.patch ==<br />
<br />
FYI: when using the Suspend-to-RAM patch from http://lkml.org/lkml/2005/9/23/97 against 2.6.14 the libata_passthru.patch from the article doesn't apply any more, so I've put up an updated version at http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch<br />
<br />
I give no warranties whatsoever whether it works or kills your hardware, but since I just removed duplicate parts already in the Suspend-to-RAM patch it should be ok.<br />
<br />
--[[User:spiney|spiney]] 19:04, 4 Nov 2005 (CET)<br />
<br />
Hi<br />
<br />
Running 2.6.16-rc4 and I'm running into scsci errors and Input/output<br />
errrors when resuming from suspend to ram. The suspend patch is<br />
supposed to be in 2.6.16-rc1 and I'm booting with<br />
<br />
title= 2.6.16-rc4<br />
root (hd0,0)<br />
kernel /boot/kernel-2.6.16-rc4 root=/dev/sda3 ro combined_mode=libata<br />
libata.atapi_enabled=1 acpi_sleep=s3_bios processor.max_cstate=2<br />
elevator=cfq ide1=noprobe<br />
<br />
Thanks.<br />
<br />
----<br />
<br />
Don't know about -rc4, but -rc3 worked without problems, could you try that one instead? Maybe there was some bug introduced between these two versions. What's combined_mode=libata BTW?<br />
<br />
--[[User:Spiney|spiney]] 08:28, 23 February 2006 (CET)<br />
----<br />
<br />
== ATA_ENABLE_PATA PCI IDs ==<br />
<br />
Spiney, could you extend the article to explain what and why are the PCI IDs in the footnote about ATA_ENABLE_PATA?<br />
<br />
--[[User:Thinker|Thinker]] 21:59, 4 Nov 2005 (CET)<br />
----<br />
<br />
Ok, done, feel free to fix the table because I'm a bit struggling with Wiki-style editing. ;) As for the why, those PCI IDs are the only ones affected by the ATA_ENABLE_PATA, as seen in {{path|drivers/scsi/ata_piix.c}} in the kernel source.<br />
<br />
--[[User:spiney|spiney]] 11:19, 5 Nov 2005 (CET)<br />
----<br />
<br />
Will other cards work without ATA_ENABLE_PATA, or just fail? In the former case your instructions are right, but in the latter case we should tell the user to check the list of IDs in his ''current'' kernel and, if there's no match, to give up in the first place instead of following the rest of the instructions.<br />
<br />
--[[User:Thinker|Thinker]] 12:48, 5 Nov 2005 (CET)<br />
----<br />
<br />
AFAICT if the chipset is supported by libata it will work, regardless of what low-level driver is used. Of course if there is no low-level driver for the chipset then even using the harddisk via libata will fail, but that's a different story. At least ATA_ENABLE_PATA will then make no difference since it's Intel PIIX (and compatible) only.<br />
<br />
--[[User:spiney|spiney]] 13:24, 5 Nov 2005 (CET)<br />
----<br />
<br />
Not sure I got you. Is there any case where the instructions will work without ATA_ENABLE_PATA, given that all ThinkPad optical drives are PATA?<br />
<br />
--[[User:Thinker|Thinker]] 13:41, 5 Nov 2005 (CET)<br />
----<br />
<br />
The instructions will work without ATA_ENABLE_PATA unless the Thinkpad uses one of the three chipsets listed in the article, as long as libata works at all, i.e. the system drive shows up as /dev/sda. The #define doesn't change the behaviour of libata for any other chipset, it's [http://linux.yyz.us/sata/sata-status.html#ich5 ata_piix] only.<br />
<br />
Since I don't have a machine with one of the three chipsets (anyone?), I can't tell whether those work at all with libata, but I guess there's a reason why they're not enabled by default. It's just that defining ATA_ENABLE_PATA is only making sense for these three chipsets.<br />
<br />
Any clearer now? If not, just run {{cmd|grep -r ATA_ENABLE_PATA /path/to/kernelsource|}} and see how seldom and where the #define is used.<br />
<br />
--[[User:spiney|spiney]] 14:55, 5 Nov 2005 (CET)<br />
----<br />
<br />
All clear now. I thought it will work only if you have these chipsets ''and'' ATA_ENABLE_PATA=1. Thanks for the explanation!<br />
<br />
--[[User:Thinker|Thinker]] 15:12, 5 Nov 2005 (CET)<br />
----<br />
<br />
Does any of the relevant ThinkPad models (listed in the article) use these chips? They look too old to be found on the SATA models.<br />
<br />
--[[User:Thinker|Thinker]] 23:35, 9 Nov 2005 (CET)<br />
----<br />
<br />
I don't think so, I was about to add "in the unlikely event that you own one of these chipsets" or something.<br />
<br />
--[[User:Spiney|spiney]] 07:56, 10 Nov 2005 (CET)<br />
----<br />
<br />
== DVD DMA with ide/sata as module ==<br />
<br />
Did anyone get DVD DMA to work with either the IDE or SATA drivers compiled as modules? If so, please fill in the missing details in that section. I have it working only with both IDE and SATA built-in.<br />
<br />
--[[User:Thinker|Thinker]] 17:58, 16 Nov 2005 (CET)<br />
----<br />
<br />
Basically using a Live-CD with a recent kernel (is there one with 2.6.14 already?) would be sufficient, since they usually use an initrd or something similar, don't they? I'll give the Debian distribution kernel a try when I get around to it (bit busy atm), after all there's 2.6.14 in sid.<br />
<br />
But for people using their own kernel compiled from source I see no point in doing the module+initrd thing anyway, unless you want LVM for the root filesystem or other funky stuff.<br />
<br />
--[[User:Spiney|spiney]] 19:22, 16 Nov 2005 (CET)<br />
----<br />
<br />
Hi<br />
<br />
Can anyone tell me how those modules are called?<br />
<br />
Thomas<br />
--[[User:Thomas|thomas]] 19:48, 23 Jan 2006 (CET)<br />
----<br />
<br />
Hi, I have problems with kernel 2.6.14.6 and libata passthrough. After executing twice the command "cdrecord --scanbus" as root, I get the following message many times in dmesg: "sr 1:0:0:0: timing out command, waited 0s".<br />
<br />
--[[User:Whoopie|Whoopie]] 12:53, 14 February 2006 (CET)<br />
<br />
== occasional hang upon resume with various kernels ==<br />
<br />
I keep having trouble with resume after suspend to ram. Occasionally, it takes longer to wake up and then is in a semi-hanged <br />
state, i.e. nothing having to do with actual reading from the disk works. (what was running, as aterm <br />
is still running, ls works, when the listing is buffered, but hangs if it is not). <br />
Kernel is 2.6.15 with sata-pm patch. Later 2.6.15 kernels hang always and it's the same with 2.6.16. <br />
Could perhaps somebody, for whom it works without problems post his .config somewhere? <br />
I'm out of ideas. <br />
<br />
--[[User:Rasto|Rasto]] 14:46, 20 March 2006 (CET)<br />
<br />
I have the same problem with my x41 and 2.6.16 or 2.6.16-r1 running on Gentoo. Sometimes resume is ok and sometimes the disk doesn't resume. I can't see any log because the disk is unwritable after resume. The logs on F12 is full of io error.<br />
I tested many different kernel configs, unloading modules before suspend, stopping services...<br />
Like Rasto, I'm out of ideas...<br />
<br />
--[[User:Pplr|Pplr]] 19:21, 8 April 2006 (CEST)<br />
<br />
You could try http://rtr.ca/dell_i9300/kernel/kernel-2.6.16/02_libata_resume_fix.patch<br />
This patch worked for me.<br />
<br />
--[[User:Whoopie|Whoopie]] 21:21, 8 April 2006 (CEST)<br />
<br />
Hello, according to the first lines of the article, resume does not work prior to kernel 2.6.16, i.e. the computer hangs up just a second after it comes back. I just switched from 2.6.15 to 2.6.16 but the problem still remains. I have a Z60M thinkpad. So this has obviously the same problem as the T60.<br />
<br />
-- [[User:Bjoern.thalheim|Björn]] 14:37, 10 April 2006 (CEST)<br />
<br />
Increasing the timeouts seems to do the trick. I applied it about two weeks ago, and it works since. <br />
<br />
-- [[User:Rasto|Rasto]] 09:59, 11 April 2006 (CEST)<br />
<br />
== Suspend to RAM on X41 not working with Debian-packaged 2.6.16 ==<br />
<br />
I just tried the Debian package of the Linux 2.6.16 kernel on my [[X41]] to see if suspend-to-RAM would work. Unfortunately, it didn't. The laptop suspends just fine, but when it's turned back on, the backlight remains off, there is a lot of disk activity for a while, and then the computer just shuts off. When turned on again, it boots normally. Suspend-to-disk works fine, just like before.<br />
<br />
On a different note, CPU throttling broke on my system with the new kernel. I can no longer modprobe acpi-cpufreq. [[User:Ehn|Ehn]] 04:28, 22 March 2006 (CET)<br />
<br />
:The latter issue was solved by using speedstep-centrino instead of acpi-cpufreq. [[User:Ehn|Ehn]] 23:25, 9 April 2006 (CEST)<br />
----<br />
<br />
Neither problem is related to this article, so it's unlikely to be answered here.<br />
<br />
--[[User:Thinker|Thinker]] 17:37, 22 March 2006 (CET)<br />
----<br />
<br />
Hm. It seems to be a problem with sata power management for me, so I guess this could be one of the places. <br />
<br />
[[User:Rasto|Rasto]] 17:45, 22 March 2006 (CET)<br />
---<br />
<br />
Ehn, by "disk activity" do you mean a constantly on HDD LED and no disk movement noises, or ''real'' disk activity with the LED flashing and disk noise? The former is likely to be the SATA problem, the latter rules out the SATA problem.<br />
<br />
--[[User:Thinker|Thinker]] 18:44, 22 March 2006 (CET)<br />
<br />
:The latter. There is real disk activity, indicated by LED flashing <em>and</em> disk movement noise, for about 30 seconds, before the machine gives up and shuts down. If this is not SATA-related, what might it be? [[User:Ehn|Ehn]] 23:23, 9 April 2006 (CEST)<br />
<br />
----<br />
<br />
Sorry, I didn't realize Ehn has two problems, and I considered your post as aimed at my and Ehn's. Never mind then.<br />
<br />
[[User:Rasto|Rasto]] 10:47, 23 March 2006 (CET)<br />
<br />
== Problem with 2.6.16 ==<br />
<br />
ok, seems like we have a new problem:<br />
After upgrading from 2.6.15 to 2.6.16 my DVD device is not recognised anymore by libsata.<br />
The only way to get working is by using the ide layer - without DMA of course.<br />
Can anyone confirm this?<br />
<br />
--[[User:Defiant|Erik]] 17:49, 23 Mar 2006 (CET)<br />
--------<br />
<br />
Try the kernel parameter '''combined_mode=libata''', does this help? Also, have you enabled libata's ATAPI support as described in the article?<br />
<br />
--[[User:Thinker|Thinker]] 20:31, 23 March 2006 (CET)<br />
----<br />
<br />
Yes, I'm using the command line parameter libata.atapi_enable=1 - up to 2.6.15 it works fine.<br />
About the combined_mode parameter: Also tried it, though the Author of this patch mentioned that the default behavior did not changed.<br />
I will continue hungting this problem when I find some time.<br />
<br />
--[[User:Defiant|Erik]] 7:12, 24 Mar 2006 (CET)<br />
-----<br />
<br />
I can confirm Eriks problem. After updating to 2.6.16 I have it, too. libata.atapi_enable=1 is still on kernel command line. With some help of Michael Ott I figured out that this only happens if you have the current suspend2 patches applied.<br />
Using a vanilla 2.6.16 works as expected. <br />
<br />
--[[User:Mobst|mobst]] 14:30, 24 Mar 2006 (CET)<br />
-----<br />
<br />
Ahh thanks. Finding the problem in the suspend2 patch should be an easy task.<br />
I just hope for some free time this weekend!<br />
<br />
--[[User:Defiant|Erik]] 18:31, 24 Mar 2006 (CET)<br />
-----<br />
<br />
Uhm, looks like [[ZolnOtt|ZolnOtt]] was faster, he added the note to<br />
http://thinkwiki.org/wiki/Problems_with_SATA_and_Linux#No_DMA_on_DVD_drive<br />
<br />
--[[User:Defiant|Erik]] 20:02, 24 Mar 2006 (CET)</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Problems_with_SATA_and_Linux&diff=21055Talk:Problems with SATA and Linux2006-03-23T09:47:55Z<p>Rasto: /* Suspend to RAM on X41 not working with Debian-packaged 2.6.16 */</p>
<hr />
<div>I'm running gentoo on my T43; I had problems with X11 (opensource radeon driver) and a SATA-patched kernel (I tried both 2.6.14 and 2.6.15-gentoo). Suspend to RAM worked nicely, but starting X freezed the machine after a short time. I tried removing radeonfb from the kernel; with vesafb, everything seems to work.<br />
<br />
-- Stefan, 10 Jan 2006<br />
<br />
--------<br />
That's strange - with the libata passthrough (IDE driver not in kernel) as set up in the text, my t43p DVD drive also will not record as hinted in the wikipage... DMA works fine, so DVD playing / ripping is smooth and quick. CD record functions also are absent. I have PATA enabled, and the suspend + SMART patches applied over 2.6.14.2.<br />
--------<br />
I can confirm this with 2.6.14.4, however with 2.6.15/15.1 with sata_pm patch it works.<br />
<br />
-- Rasto, 24 Jan 2006<br />
<br />
--------<br />
regarding the "BIOS error 2010 on user-installed hard disk":<br />
the text says that corruption occurs if you use a harddisk without the specific ibm bios. would be interesting if it is possible to fix this problem in the kernel so that you can use any disk and the kernel doesn't use specific ATA commands which are known to cause problems.<br />
<br />
in the tabook i didn't find any specification of the SATA bridge. it would be interesting:<br />
1) what type it is<br />
2) if it is fixed on the mainboard or if it is possible to solder in a new one<br />
<br />
----<br />
<br />
Another interesting question is whether these ThinkPads can be hacked to accept a real SATA system disk, by bypassing the SATA-to-PATA bridge (this would probably involve some soldering and cutting). If the BIOS can also handle that then it may come in handy, since some new high-capacity 2.5" disks have only SATA versions.<br />
--[[User:Thinker|Thinker]] 02:56, 8 Oct 2005 (CEST)<br />
<br />
----<br />
<br />
'''Z series'''<br />
<br />
Since the Z series uses a SATA controller and disk, without the bridge, would it be possible to make SATA ATAPI support as a module that you could load only when using the optical drive? Then, for everyday use, the experimental options of PATA and ATAPI with ata_piix would not be needed, moving you one step further in the direction of stability.<br />
<br />
----<br />
<br />
I have an R52 with Ubuntu Breezy and no problems with SATA (I personally asked the developers to include the needed patches).<br />
<br />
However, I'd like to know wheter there are any advantages with this configuration. Future proof? Power saving? Speed?<br />
<br />
Anybody cares to comment?<br />
<br />
-- [[User:Micampe|Michele]]<br />
<br />
Straight SATA, like in the Z60m/t, will provide better upgrade options in the long run (the hard disk industry is slowly but surely moving to SATA), and maybe a small performance increase if your drive, controller and OS support command queueing (they probably don't). However, with the hybrid ThinkPad models that use a SATA-to-PATA bridge, like your R52, you get all the drawbacks and none of the benefits; plus there's the horrible issue with [[Problem with non-ThinkPad hard disks|drive compatibility]]. My impression is that Lenovo did this just as a convenient (for them!) transition path, in order to use new chipsets without comitting to (temporarily) scarcer and more expensive drives. In any case, they didn't even have the decency to make the UltraBay Slim accept SATA drives. <br />
<br />
--[[User:Thinker|Thinker]] 18:10, 3 Nov 2005 (CET)<br />
----<br />
There is a [[UltraBay Slim SATA HDD Adapter]], but only compatible with the Z series (at least for the moment).<br />
<br />
--[[User:Tonko|Tonko]] 03:12, 4 Nov 2005 (CET)<br />
<br />
== updated libata_passthru.patch ==<br />
<br />
FYI: when using the Suspend-to-RAM patch from http://lkml.org/lkml/2005/9/23/97 against 2.6.14 the libata_passthru.patch from the article doesn't apply any more, so I've put up an updated version at http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch<br />
<br />
I give no warranties whatsoever whether it works or kills your hardware, but since I just removed duplicate parts already in the Suspend-to-RAM patch it should be ok.<br />
<br />
--[[User:spiney|spiney]] 19:04, 4 Nov 2005 (CET)<br />
<br />
Hi<br />
<br />
Running 2.6.16-rc4 and I'm running into scsci errors and Input/output<br />
errrors when resuming from suspend to ram. The suspend patch is<br />
supposed to be in 2.6.16-rc1 and I'm booting with<br />
<br />
title= 2.6.16-rc4<br />
root (hd0,0)<br />
kernel /boot/kernel-2.6.16-rc4 root=/dev/sda3 ro combined_mode=libata<br />
libata.atapi_enabled=1 acpi_sleep=s3_bios processor.max_cstate=2<br />
elevator=cfq ide1=noprobe<br />
<br />
Thanks.<br />
<br />
----<br />
<br />
Don't know about -rc4, but -rc3 worked without problems, could you try that one instead? Maybe there was some bug introduced between these two versions. What's combined_mode=libata BTW?<br />
<br />
--[[User:Spiney|spiney]] 08:28, 23 February 2006 (CET)<br />
----<br />
<br />
== ATA_ENABLE_PATA PCI IDs ==<br />
<br />
Spiney, could you extend the article to explain what and why are the PCI IDs in the footnote about ATA_ENABLE_PATA?<br />
<br />
--[[User:Thinker|Thinker]] 21:59, 4 Nov 2005 (CET)<br />
----<br />
<br />
Ok, done, feel free to fix the table because I'm a bit struggling with Wiki-style editing. ;) As for the why, those PCI IDs are the only ones affected by the ATA_ENABLE_PATA, as seen in {{path|drivers/scsi/ata_piix.c}} in the kernel source.<br />
<br />
--[[User:spiney|spiney]] 11:19, 5 Nov 2005 (CET)<br />
----<br />
<br />
Will other cards work without ATA_ENABLE_PATA, or just fail? In the former case your instructions are right, but in the latter case we should tell the user to check the list of IDs in his ''current'' kernel and, if there's no match, to give up in the first place instead of following the rest of the instructions.<br />
<br />
--[[User:Thinker|Thinker]] 12:48, 5 Nov 2005 (CET)<br />
----<br />
<br />
AFAICT if the chipset is supported by libata it will work, regardless of what low-level driver is used. Of course if there is no low-level driver for the chipset then even using the harddisk via libata will fail, but that's a different story. At least ATA_ENABLE_PATA will then make no difference since it's Intel PIIX (and compatible) only.<br />
<br />
--[[User:spiney|spiney]] 13:24, 5 Nov 2005 (CET)<br />
----<br />
<br />
Not sure I got you. Is there any case where the instructions will work without ATA_ENABLE_PATA, given that all ThinkPad optical drives are PATA?<br />
<br />
--[[User:Thinker|Thinker]] 13:41, 5 Nov 2005 (CET)<br />
----<br />
<br />
The instructions will work without ATA_ENABLE_PATA unless the Thinkpad uses one of the three chipsets listed in the article, as long as libata works at all, i.e. the system drive shows up as /dev/sda. The #define doesn't change the behaviour of libata for any other chipset, it's [http://linux.yyz.us/sata/sata-status.html#ich5 ata_piix] only.<br />
<br />
Since I don't have a machine with one of the three chipsets (anyone?), I can't tell whether those work at all with libata, but I guess there's a reason why they're not enabled by default. It's just that defining ATA_ENABLE_PATA is only making sense for these three chipsets.<br />
<br />
Any clearer now? If not, just run {{cmd|grep -r ATA_ENABLE_PATA /path/to/kernelsource|}} and see how seldom and where the #define is used.<br />
<br />
--[[User:spiney|spiney]] 14:55, 5 Nov 2005 (CET)<br />
----<br />
<br />
All clear now. I thought it will work only if you have these chipsets ''and'' ATA_ENABLE_PATA=1. Thanks for the explanation!<br />
<br />
--[[User:Thinker|Thinker]] 15:12, 5 Nov 2005 (CET)<br />
----<br />
<br />
Does any of the relevant ThinkPad models (listed in the article) use these chips? They look too old to be found on the SATA models.<br />
<br />
--[[User:Thinker|Thinker]] 23:35, 9 Nov 2005 (CET)<br />
----<br />
<br />
I don't think so, I was about to add "in the unlikely event that you own one of these chipsets" or something.<br />
<br />
--[[User:Spiney|spiney]] 07:56, 10 Nov 2005 (CET)<br />
----<br />
<br />
== DVD DMA with ide/sata as module ==<br />
<br />
Did anyone get DVD DMA to work with either the IDE or SATA drivers compiled as modules? If so, please fill in the missing details in that section. I have it working only with both IDE and SATA built-in.<br />
<br />
--[[User:Thinker|Thinker]] 17:58, 16 Nov 2005 (CET)<br />
----<br />
<br />
Basically using a Live-CD with a recent kernel (is there one with 2.6.14 already?) would be sufficient, since they usually use an initrd or something similar, don't they? I'll give the Debian distribution kernel a try when I get around to it (bit busy atm), after all there's 2.6.14 in sid.<br />
<br />
But for people using their own kernel compiled from source I see no point in doing the module+initrd thing anyway, unless you want LVM for the root filesystem or other funky stuff.<br />
<br />
--[[User:Spiney|spiney]] 19:22, 16 Nov 2005 (CET)<br />
----<br />
<br />
Hi<br />
<br />
Can anyone tell me how those modules are called?<br />
<br />
Thomas<br />
--[[User:Thomas|thomas]] 19:48, 23 Jan 2006 (CET)<br />
----<br />
<br />
Hi, I have problems with kernel 2.6.14.6 and libata passthrough. After executing twice the command "cdrecord --scanbus" as root, I get the following message many times in dmesg: "sr 1:0:0:0: timing out command, waited 0s".<br />
<br />
--[[User:Whoopie|Whoopie]] 12:53, 14 February 2006 (CET)<br />
<br />
== occasional hang upon resume with various kernels ==<br />
<br />
I keep having trouble with resume after suspend to ram. Occasionally, it takes longer to wake up and then is in a semi-hanged <br />
state, i.e. nothing having to do with actual reading from the disk works. (what was running, as aterm <br />
is still running, ls works, when the listing is buffered, but hangs if it is not). <br />
Kernel is 2.6.15 with sata-pm patch. Later 2.6.15 kernels hang always and it's the same with 2.6.16. <br />
Could perhaps somebody, for whom it works without problems post his .config somewhere? <br />
I'm out of ideas. <br />
<br />
--[[User:Rasto|Rasto]] 14:46, 20 March 2006 (CET)<br />
<br />
== Suspend to RAM on X41 not working with Debian-packaged 2.6.16 ==<br />
<br />
I just tried the Debian package of the Linux 2.6.16 kernel on my [[X41]] to see if suspend-to-RAM would work. Unfortunately, it didn't. The laptop suspends just fine, but when it's turned back on, the backlight remains off, there is a lot of disk activity for a while, and then the computer just shuts off. When turned on again, it boots normally. Suspend-to-disk works fine, just like before.<br />
<br />
On a different note, CPU throttling broke on my system with the new kernel. I can no longer modprobe acpi-cpufreq. [[User:Ehn|Ehn]] 04:28, 22 March 2006 (CET)<br />
----<br />
<br />
Neither problem is related to this article, so it's unlikely to be answered here.<br />
<br />
--[[User:Thinker|Thinker]] 17:37, 22 March 2006 (CET)<br />
----<br />
<br />
Hm. It seems to be a problem with sata power management for me, so I guess this could be one of the places. <br />
<br />
[[User:Rasto|Rasto]] 17:45, 22 March 2006 (CET)<br />
---<br />
<br />
Ehn, by "disk activity" do you mean a constantly on HDD LED and no disk movement noises, or ''real'' disk activity with the LED flashing and disk noise? The former is likely to be the SATA problem, the latter rules out the SATA problem.<br />
<br />
--[[User:Thinker|Thinker]] 18:44, 22 March 2006 (CET)<br />
----<br />
<br />
Sorry, I didn't realize Ehn has two problems, and I considered your post as aimed at my and Ehn's. Never mind then.<br />
<br />
[[User:Rasto|Rasto]] 10:47, 23 March 2006 (CET)</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Problems_with_SATA_and_Linux&diff=21037Talk:Problems with SATA and Linux2006-03-22T16:45:54Z<p>Rasto: /* Suspend to RAM on X41 not working with Debian-packaged 2.6.16 */</p>
<hr />
<div>I'm running gentoo on my T43; I had problems with X11 (opensource radeon driver) and a SATA-patched kernel (I tried both 2.6.14 and 2.6.15-gentoo). Suspend to RAM worked nicely, but starting X freezed the machine after a short time. I tried removing radeonfb from the kernel; with vesafb, everything seems to work.<br />
<br />
-- Stefan, 10 Jan 2006<br />
<br />
--------<br />
That's strange - with the libata passthrough (IDE driver not in kernel) as set up in the text, my t43p DVD drive also will not record as hinted in the wikipage... DMA works fine, so DVD playing / ripping is smooth and quick. CD record functions also are absent. I have PATA enabled, and the suspend + SMART patches applied over 2.6.14.2.<br />
--------<br />
I can confirm this with 2.6.14.4, however with 2.6.15/15.1 with sata_pm patch it works.<br />
<br />
-- Rasto, 24 Jan 2006<br />
<br />
--------<br />
regarding the "BIOS error 2010 on user-installed hard disk":<br />
the text says that corruption occurs if you use a harddisk without the specific ibm bios. would be interesting if it is possible to fix this problem in the kernel so that you can use any disk and the kernel doesn't use specific ATA commands which are known to cause problems.<br />
<br />
in the tabook i didn't find any specification of the SATA bridge. it would be interesting:<br />
1) what type it is<br />
2) if it is fixed on the mainboard or if it is possible to solder in a new one<br />
<br />
----<br />
<br />
Another interesting question is whether these ThinkPads can be hacked to accept a real SATA system disk, by bypassing the SATA-to-PATA bridge (this would probably involve some soldering and cutting). If the BIOS can also handle that then it may come in handy, since some new high-capacity 2.5" disks have only SATA versions.<br />
--[[User:Thinker|Thinker]] 02:56, 8 Oct 2005 (CEST)<br />
<br />
----<br />
<br />
'''Z series'''<br />
<br />
Since the Z series uses a SATA controller and disk, without the bridge, would it be possible to make SATA ATAPI support as a module that you could load only when using the optical drive? Then, for everyday use, the experimental options of PATA and ATAPI with ata_piix would not be needed, moving you one step further in the direction of stability.<br />
<br />
----<br />
<br />
I have an R52 with Ubuntu Breezy and no problems with SATA (I personally asked the developers to include the needed patches).<br />
<br />
However, I'd like to know wheter there are any advantages with this configuration. Future proof? Power saving? Speed?<br />
<br />
Anybody cares to comment?<br />
<br />
-- [[User:Micampe|Michele]]<br />
<br />
Straight SATA, like in the Z60m/t, will provide better upgrade options in the long run (the hard disk industry is slowly but surely moving to SATA), and maybe a small performance increase if your drive, controller and OS support command queueing (they probably don't). However, with the hybrid ThinkPad models that use a SATA-to-PATA bridge, like your R52, you get all the drawbacks and none of the benefits; plus there's the horrible issue with [[Problem with non-ThinkPad hard disks|drive compatibility]]. My impression is that Lenovo did this just as a convenient (for them!) transition path, in order to use new chipsets without comitting to (temporarily) scarcer and more expensive drives. In any case, they didn't even have the decency to make the UltraBay Slim accept SATA drives. <br />
<br />
--[[User:Thinker|Thinker]] 18:10, 3 Nov 2005 (CET)<br />
----<br />
There is a [[UltraBay Slim SATA HDD Adapter]], but only compatible with the Z series (at least for the moment).<br />
<br />
--[[User:Tonko|Tonko]] 03:12, 4 Nov 2005 (CET)<br />
<br />
== updated libata_passthru.patch ==<br />
<br />
FYI: when using the Suspend-to-RAM patch from http://lkml.org/lkml/2005/9/23/97 against 2.6.14 the libata_passthru.patch from the article doesn't apply any more, so I've put up an updated version at http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch<br />
<br />
I give no warranties whatsoever whether it works or kills your hardware, but since I just removed duplicate parts already in the Suspend-to-RAM patch it should be ok.<br />
<br />
--[[User:spiney|spiney]] 19:04, 4 Nov 2005 (CET)<br />
<br />
Hi<br />
<br />
Running 2.6.16-rc4 and I'm running into scsci errors and Input/output<br />
errrors when resuming from suspend to ram. The suspend patch is<br />
supposed to be in 2.6.16-rc1 and I'm booting with<br />
<br />
title= 2.6.16-rc4<br />
root (hd0,0)<br />
kernel /boot/kernel-2.6.16-rc4 root=/dev/sda3 ro combined_mode=libata<br />
libata.atapi_enabled=1 acpi_sleep=s3_bios processor.max_cstate=2<br />
elevator=cfq ide1=noprobe<br />
<br />
Thanks.<br />
<br />
----<br />
<br />
Don't know about -rc4, but -rc3 worked without problems, could you try that one instead? Maybe there was some bug introduced between these two versions. What's combined_mode=libata BTW?<br />
<br />
--[[User:Spiney|spiney]] 08:28, 23 February 2006 (CET)<br />
----<br />
<br />
== ATA_ENABLE_PATA PCI IDs ==<br />
<br />
Spiney, could you extend the article to explain what and why are the PCI IDs in the footnote about ATA_ENABLE_PATA?<br />
<br />
--[[User:Thinker|Thinker]] 21:59, 4 Nov 2005 (CET)<br />
----<br />
<br />
Ok, done, feel free to fix the table because I'm a bit struggling with Wiki-style editing. ;) As for the why, those PCI IDs are the only ones affected by the ATA_ENABLE_PATA, as seen in {{path|drivers/scsi/ata_piix.c}} in the kernel source.<br />
<br />
--[[User:spiney|spiney]] 11:19, 5 Nov 2005 (CET)<br />
----<br />
<br />
Will other cards work without ATA_ENABLE_PATA, or just fail? In the former case your instructions are right, but in the latter case we should tell the user to check the list of IDs in his ''current'' kernel and, if there's no match, to give up in the first place instead of following the rest of the instructions.<br />
<br />
--[[User:Thinker|Thinker]] 12:48, 5 Nov 2005 (CET)<br />
----<br />
<br />
AFAICT if the chipset is supported by libata it will work, regardless of what low-level driver is used. Of course if there is no low-level driver for the chipset then even using the harddisk via libata will fail, but that's a different story. At least ATA_ENABLE_PATA will then make no difference since it's Intel PIIX (and compatible) only.<br />
<br />
--[[User:spiney|spiney]] 13:24, 5 Nov 2005 (CET)<br />
----<br />
<br />
Not sure I got you. Is there any case where the instructions will work without ATA_ENABLE_PATA, given that all ThinkPad optical drives are PATA?<br />
<br />
--[[User:Thinker|Thinker]] 13:41, 5 Nov 2005 (CET)<br />
----<br />
<br />
The instructions will work without ATA_ENABLE_PATA unless the Thinkpad uses one of the three chipsets listed in the article, as long as libata works at all, i.e. the system drive shows up as /dev/sda. The #define doesn't change the behaviour of libata for any other chipset, it's [http://linux.yyz.us/sata/sata-status.html#ich5 ata_piix] only.<br />
<br />
Since I don't have a machine with one of the three chipsets (anyone?), I can't tell whether those work at all with libata, but I guess there's a reason why they're not enabled by default. It's just that defining ATA_ENABLE_PATA is only making sense for these three chipsets.<br />
<br />
Any clearer now? If not, just run {{cmd|grep -r ATA_ENABLE_PATA /path/to/kernelsource|}} and see how seldom and where the #define is used.<br />
<br />
--[[User:spiney|spiney]] 14:55, 5 Nov 2005 (CET)<br />
----<br />
<br />
All clear now. I thought it will work only if you have these chipsets ''and'' ATA_ENABLE_PATA=1. Thanks for the explanation!<br />
<br />
--[[User:Thinker|Thinker]] 15:12, 5 Nov 2005 (CET)<br />
----<br />
<br />
Does any of the relevant ThinkPad models (listed in the article) use these chips? They look too old to be found on the SATA models.<br />
<br />
--[[User:Thinker|Thinker]] 23:35, 9 Nov 2005 (CET)<br />
----<br />
<br />
I don't think so, I was about to add "in the unlikely event that you own one of these chipsets" or something.<br />
<br />
--[[User:Spiney|spiney]] 07:56, 10 Nov 2005 (CET)<br />
----<br />
<br />
== DVD DMA with ide/sata as module ==<br />
<br />
Did anyone get DVD DMA to work with either the IDE or SATA drivers compiled as modules? If so, please fill in the missing details in that section. I have it working only with both IDE and SATA built-in.<br />
<br />
--[[User:Thinker|Thinker]] 17:58, 16 Nov 2005 (CET)<br />
----<br />
<br />
Basically using a Live-CD with a recent kernel (is there one with 2.6.14 already?) would be sufficient, since they usually use an initrd or something similar, don't they? I'll give the Debian distribution kernel a try when I get around to it (bit busy atm), after all there's 2.6.14 in sid.<br />
<br />
But for people using their own kernel compiled from source I see no point in doing the module+initrd thing anyway, unless you want LVM for the root filesystem or other funky stuff.<br />
<br />
--[[User:Spiney|spiney]] 19:22, 16 Nov 2005 (CET)<br />
----<br />
<br />
Hi<br />
<br />
Can anyone tell me how those modules are called?<br />
<br />
Thomas<br />
--[[User:Thomas|thomas]] 19:48, 23 Jan 2006 (CET)<br />
----<br />
<br />
Hi, I have problems with kernel 2.6.14.6 and libata passthrough. After executing twice the command "cdrecord --scanbus" as root, I get the following message many times in dmesg: "sr 1:0:0:0: timing out command, waited 0s".<br />
<br />
--[[User:Whoopie|Whoopie]] 12:53, 14 February 2006 (CET)<br />
<br />
== occasional hang upon resume with various kernels ==<br />
<br />
I keep having trouble with resume after suspend to ram. Occasionally, it takes longer to wake up and then is in a semi-hanged <br />
state, i.e. nothing having to do with actual reading from the disk works. (what was running, as aterm <br />
is still running, ls works, when the listing is buffered, but hangs if it is not). <br />
Kernel is 2.6.15 with sata-pm patch. Later 2.6.15 kernels hang always and it's the same with 2.6.16. <br />
Could perhaps somebody, for whom it works without problems post his .config somewhere? <br />
I'm out of ideas. <br />
<br />
--[[User:Rasto|Rasto]] 14:46, 20 March 2006 (CET)<br />
<br />
== Suspend to RAM on X41 not working with Debian-packaged 2.6.16 ==<br />
<br />
I just tried the Debian package of the Linux 2.6.16 kernel on my [[X41]] to see if suspend-to-RAM would work. Unfortunately, it didn't. The laptop suspends just fine, but when it's turned back on, the backlight remains off, there is a lot of disk activity for a while, and then the computer just shuts off. When turned on again, it boots normally. Suspend-to-disk works fine, just like before.<br />
<br />
On a different note, CPU throttling broke on my system with the new kernel. I can no longer modprobe acpi-cpufreq. [[User:Ehn|Ehn]] 04:28, 22 March 2006 (CET)<br />
----<br />
<br />
Neither problem is related to this article, so it's unlikely to be answered here.<br />
<br />
--[[User:Thinker|Thinker]] 17:37, 22 March 2006 (CET)<br />
----<br />
<br />
Hm. It seems to be a problem with sata power management for me, so I guess this could be one of the places. <br />
<br />
[[User:Rasto|Rasto]] 17:45, 22 March 2006 (CET)</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Problems_with_SATA_and_Linux&diff=20985Talk:Problems with SATA and Linux2006-03-20T13:46:36Z<p>Rasto: occasional hang upon resume with various kernels</p>
<hr />
<div>I'm running gentoo on my T43; I had problems with X11 (opensource radeon driver) and a SATA-patched kernel (I tried both 2.6.14 and 2.6.15-gentoo). Suspend to RAM worked nicely, but starting X freezed the machine after a short time. I tried removing radeonfb from the kernel; with vesafb, everything seems to work.<br />
<br />
-- Stefan, 10 Jan 2006<br />
<br />
--------<br />
That's strange - with the libata passthrough (IDE driver not in kernel) as set up in the text, my t43p DVD drive also will not record as hinted in the wikipage... DMA works fine, so DVD playing / ripping is smooth and quick. CD record functions also are absent. I have PATA enabled, and the suspend + SMART patches applied over 2.6.14.2.<br />
--------<br />
I can confirm this with 2.6.14.4, however with 2.6.15/15.1 with sata_pm patch it works.<br />
<br />
-- Rasto, 24 Jan 2006<br />
<br />
--------<br />
regarding the "BIOS error 2010 on user-installed hard disk":<br />
the text says that corruption occurs if you use a harddisk without the specific ibm bios. would be interesting if it is possible to fix this problem in the kernel so that you can use any disk and the kernel doesn't use specific ATA commands which are known to cause problems.<br />
<br />
in the tabook i didn't find any specification of the SATA bridge. it would be interesting:<br />
1) what type it is<br />
2) if it is fixed on the mainboard or if it is possible to solder in a new one<br />
<br />
----<br />
<br />
Another interesting question is whether these ThinkPads can be hacked to accept a real SATA system disk, by bypassing the SATA-to-PATA bridge (this would probably involve some soldering and cutting). If the BIOS can also handle that then it may come in handy, since some new high-capacity 2.5" disks have only SATA versions.<br />
--[[User:Thinker|Thinker]] 02:56, 8 Oct 2005 (CEST)<br />
<br />
----<br />
<br />
'''Z series'''<br />
<br />
Since the Z series uses a SATA controller and disk, without the bridge, would it be possible to make SATA ATAPI support as a module that you could load only when using the optical drive? Then, for everyday use, the experimental options of PATA and ATAPI with ata_piix would not be needed, moving you one step further in the direction of stability.<br />
<br />
----<br />
<br />
I have an R52 with Ubuntu Breezy and no problems with SATA (I personally asked the developers to include the needed patches).<br />
<br />
However, I'd like to know wheter there are any advantages with this configuration. Future proof? Power saving? Speed?<br />
<br />
Anybody cares to comment?<br />
<br />
-- [[User:Micampe|Michele]]<br />
<br />
Straight SATA, like in the Z60m/t, will provide better upgrade options in the long run (the hard disk industry is slowly but surely moving to SATA), and maybe a small performance increase if your drive, controller and OS support command queueing (they probably don't). However, with the hybrid ThinkPad models that use a SATA-to-PATA bridge, like your R52, you get all the drawbacks and none of the benefits; plus there's the horrible issue with [[Problem with non-ThinkPad hard disks|drive compatibility]]. My impression is that Lenovo did this just as a convenient (for them!) transition path, in order to use new chipsets without comitting to (temporarily) scarcer and more expensive drives. In any case, they didn't even have the decency to make the UltraBay Slim accept SATA drives. <br />
<br />
--[[User:Thinker|Thinker]] 18:10, 3 Nov 2005 (CET)<br />
----<br />
There is a [[UltraBay Slim SATA HDD Adapter]], but only compatible with the Z series (at least for the moment).<br />
<br />
--[[User:Tonko|Tonko]] 03:12, 4 Nov 2005 (CET)<br />
<br />
== updated libata_passthru.patch ==<br />
<br />
FYI: when using the Suspend-to-RAM patch from http://lkml.org/lkml/2005/9/23/97 against 2.6.14 the libata_passthru.patch from the article doesn't apply any more, so I've put up an updated version at http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch<br />
<br />
I give no warranties whatsoever whether it works or kills your hardware, but since I just removed duplicate parts already in the Suspend-to-RAM patch it should be ok.<br />
<br />
--[[User:spiney|spiney]] 19:04, 4 Nov 2005 (CET)<br />
<br />
Hi<br />
<br />
Running 2.6.16-rc4 and I'm running into scsci errors and Input/output<br />
errrors when resuming from suspend to ram. The suspend patch is<br />
supposed to be in 2.6.16-rc1 and I'm booting with<br />
<br />
title= 2.6.16-rc4<br />
root (hd0,0)<br />
kernel /boot/kernel-2.6.16-rc4 root=/dev/sda3 ro combined_mode=libata<br />
libata.atapi_enabled=1 acpi_sleep=s3_bios processor.max_cstate=2<br />
elevator=cfq ide1=noprobe<br />
<br />
Thanks.<br />
<br />
----<br />
<br />
Don't know about -rc4, but -rc3 worked without problems, could you try that one instead? Maybe there was some bug introduced between these two versions. What's combined_mode=libata BTW?<br />
<br />
--[[User:Spiney|spiney]] 08:28, 23 February 2006 (CET)<br />
----<br />
<br />
== ATA_ENABLE_PATA PCI IDs ==<br />
<br />
Spiney, could you extend the article to explain what and why are the PCI IDs in the footnote about ATA_ENABLE_PATA?<br />
<br />
--[[User:Thinker|Thinker]] 21:59, 4 Nov 2005 (CET)<br />
----<br />
<br />
Ok, done, feel free to fix the table because I'm a bit struggling with Wiki-style editing. ;) As for the why, those PCI IDs are the only ones affected by the ATA_ENABLE_PATA, as seen in {{path|drivers/scsi/ata_piix.c}} in the kernel source.<br />
<br />
--[[User:spiney|spiney]] 11:19, 5 Nov 2005 (CET)<br />
----<br />
<br />
Will other cards work without ATA_ENABLE_PATA, or just fail? In the former case your instructions are right, but in the latter case we should tell the user to check the list of IDs in his ''current'' kernel and, if there's no match, to give up in the first place instead of following the rest of the instructions.<br />
<br />
--[[User:Thinker|Thinker]] 12:48, 5 Nov 2005 (CET)<br />
----<br />
<br />
AFAICT if the chipset is supported by libata it will work, regardless of what low-level driver is used. Of course if there is no low-level driver for the chipset then even using the harddisk via libata will fail, but that's a different story. At least ATA_ENABLE_PATA will then make no difference since it's Intel PIIX (and compatible) only.<br />
<br />
--[[User:spiney|spiney]] 13:24, 5 Nov 2005 (CET)<br />
----<br />
<br />
Not sure I got you. Is there any case where the instructions will work without ATA_ENABLE_PATA, given that all ThinkPad optical drives are PATA?<br />
<br />
--[[User:Thinker|Thinker]] 13:41, 5 Nov 2005 (CET)<br />
----<br />
<br />
The instructions will work without ATA_ENABLE_PATA unless the Thinkpad uses one of the three chipsets listed in the article, as long as libata works at all, i.e. the system drive shows up as /dev/sda. The #define doesn't change the behaviour of libata for any other chipset, it's [http://linux.yyz.us/sata/sata-status.html#ich5 ata_piix] only.<br />
<br />
Since I don't have a machine with one of the three chipsets (anyone?), I can't tell whether those work at all with libata, but I guess there's a reason why they're not enabled by default. It's just that defining ATA_ENABLE_PATA is only making sense for these three chipsets.<br />
<br />
Any clearer now? If not, just run {{cmd|grep -r ATA_ENABLE_PATA /path/to/kernelsource|}} and see how seldom and where the #define is used.<br />
<br />
--[[User:spiney|spiney]] 14:55, 5 Nov 2005 (CET)<br />
----<br />
<br />
All clear now. I thought it will work only if you have these chipsets ''and'' ATA_ENABLE_PATA=1. Thanks for the explanation!<br />
<br />
--[[User:Thinker|Thinker]] 15:12, 5 Nov 2005 (CET)<br />
----<br />
<br />
Does any of the relevant ThinkPad models (listed in the article) use these chips? They look too old to be found on the SATA models.<br />
<br />
--[[User:Thinker|Thinker]] 23:35, 9 Nov 2005 (CET)<br />
----<br />
<br />
I don't think so, I was about to add "in the unlikely event that you own one of these chipsets" or something.<br />
<br />
--[[User:Spiney|spiney]] 07:56, 10 Nov 2005 (CET)<br />
----<br />
<br />
== DVD DMA with ide/sata as module ==<br />
<br />
Did anyone get DVD DMA to work with either the IDE or SATA drivers compiled as modules? If so, please fill in the missing details in that section. I have it working only with both IDE and SATA built-in.<br />
<br />
--[[User:Thinker|Thinker]] 17:58, 16 Nov 2005 (CET)<br />
----<br />
<br />
Basically using a Live-CD with a recent kernel (is there one with 2.6.14 already?) would be sufficient, since they usually use an initrd or something similar, don't they? I'll give the Debian distribution kernel a try when I get around to it (bit busy atm), after all there's 2.6.14 in sid.<br />
<br />
But for people using their own kernel compiled from source I see no point in doing the module+initrd thing anyway, unless you want LVM for the root filesystem or other funky stuff.<br />
<br />
--[[User:Spiney|spiney]] 19:22, 16 Nov 2005 (CET)<br />
----<br />
<br />
Hi<br />
<br />
Can anyone tell me how those modules are called?<br />
<br />
Thomas<br />
--[[User:Thomas|thomas]] 19:48, 23 Jan 2006 (CET)<br />
----<br />
<br />
Hi, I have problems with kernel 2.6.14.6 and libata passthrough. After executing twice the command "cdrecord --scanbus" as root, I get the following message many times in dmesg: "sr 1:0:0:0: timing out command, waited 0s".<br />
<br />
--[[User:Whoopie|Whoopie]] 12:53, 14 February 2006 (CET)<br />
<br />
== occasional hang upon resume with various kernels ==<br />
<br />
I keep having trouble with resume after suspend to ram. Occasionally, it takes longer to wake up and then is in a semi-hanged <br />
state, i.e. nothing having to do with actual reading from the disk works. (what was running, as aterm <br />
is still running, ls works, when the listing is buffered, but hangs if it is not). <br />
Kernel is 2.6.15 with sata-pm patch. Later 2.6.15 kernels hang always and it's the same with 2.6.16. <br />
Could perhaps somebody, for whom it works without problems post his .config somewhere? <br />
I'm out of ideas. <br />
<br />
--[[User:Rasto|Rasto]] 14:46, 20 March 2006 (CET)</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:How_to_reduce_power_consumption&diff=20174Talk:How to reduce power consumption2006-02-17T13:28:37Z<p>Rasto: Gradual battery discharge</p>
<hr />
<div>How about linking to this page from the main page?<br />
<br />
--[[User:Thinker|Thinker]] 21:08, 17 Nov 2005 (CET)<br />
----<br />
<br />
== Best battery discharge times ==<br />
<br />
With your best power saving, what kind of battery power times are you guys experiencing? The best that I can do with my t43p with the standard (6cell) battery is 2h, and with the ultrabay battery is 1 hour. All of the power saving 'tricks' - hard drive spindown, even adjusting the brightness of my display, has relatively modest effect (~20% max), although CPU throttling definitely reduces power consumption.<br />
<br />
In terms of discharge rate, I really can't get below 19,520 mW/h with the hard disk off, wifi on, cpu down to ~700 MHz, and display on minimal brightness with ATI driver power save enabled. In my "normal usage" environment (WiFi on, word processing / non cpu-intensive programming, etc.) I average 21,000 mW/h.<br />
<br />
Of note, I have the UXGA display, which might be a huge power guzzler. I have friends with an X40 that claim 5 hours from the 9 cell...<br />
<br />
--[[User:gsmenden|gsmenden]] 16:56, 10 Feb 2006 (EST)<br />
----<br />
<br />
ThinkPad T43, SXGA+, [[Pentium M undervolting and underclocking|undervolted]], [[ACPI fan control script|fan disabled]], minimum brightness, disk off, WiFi off, [[How to make use of Graphics Chips Power Management features|GPU power saving]]: 13 to 14W, i.e., slightly over 3 hours with a new 6-cell battery. See [[How to reduce power consumption]].<br />
<br />
--[[User:Thinker|Thinker]] 22:46, 10 February 2006 (CET)<br />
<br />
BTW, this machine has 1.5GB of RAM, which probably accounts for a large fraction of a Watt. Also, the DVD drive is plugged in.<br />
--[[User:Thinker|Thinker]] 08:39, 16 February 2006 (CET)<br />
----<br />
<br />
Interesting... that would imply ~5W for the bigger screen? That seems high. Could you tell me your basal rate at 700 Mhz by chance? - everything else should match my system (using your fan control v.28 (-thanks!), minimum brightness, disk off, WiFi off, GPU power saving enabled with ATI driver.)<br />
<br />
--[[User:gsmenden|gsmenden]] 18:16, 10 Feb 2006 (EST)<br />
----<br />
<br />
The 13-14W figure is with automatic cpufreq scaling and low load, so it's effectively at 800MHz (minimum speed for this 1.86GHz processor). Are you undervolting the CPU too?<br />
<br />
--[[User:Thinker|Thinker]] 00:36, 11 February 2006 (CET)<br />
----<br />
To my understanding it would seem very unlikely that the higher resolution/bigger display uses a lot more power than lower resolution/smaller ones - except the case that they would have four light tubes instead of one. I'm pretty sure that X series displays have ónly one.<br />
[[User:Wyrfel|Wyrfel]] 01:20, 11 February 2006 (CET)<br />
----<br />
<br />
for T42 with 14" XGA, ATI 7500 at 80/100MHz, 600MHz@0.7V, hdd off, wifi off, linux:<br />
1) min. brightness - 7,6W<br />
2) brightness is 4 of 7 - 8,6W<br />
3) max. brightness - 10,1W<br />
<br />
2200bg in battery mode consumes ~0,4W. and I bet the iron can go lower runnig windows<br />
with native drivers. the only thing I really miss is powerplay support for 7500.<br />
<br />
--[[User:Bzzt|Bzzt]]<br />
----<br />
<br />
You mean they nearly ''doubled'' the minimal power draw when moving to the T43's Sonoma chipset and Dothan CPU? So you actually get 5-6 hours from a 6-cell battery?! Spooky.<br />
<br />
--[[User:Thinker|Thinker]] 01:42, 11 February 2006 (CET)<br />
----<br />
<br />
well, I'm not sure about 6 hours, but 5h doesn't look hard to achieve. 7,6W is a real bottom here. I couldn't get lower. The regular rate I feel comfort at is rather 10-11W. But even that, 5h is possible with a new 6cell battery.<br />
<br />
PS. this is why I returned 2668-4DU back and bought 2373-FWG. Sonoma really sucks, IMHO. I hope Intel has learnt the lesson and the next lines won't so hungry.<br />
<br />
-bzzz<br />
----<br />
Ok - the 15.1" 1600x1200 must be a real power monster, although I have not applied the undervolting patch. I'll give it a whirl when 2.6.15.4 is released.<br />
<br />
Update - tried the undervolting patch with some nice results - my lap is noticably cooler, and the fan spends more time off. With only a few process running (no kdm and kde -> only very basic window manager) and a black background text sceen, [[Pentium M undervolting and underclocking|undervolted]] down to 700 mV @798 MHz, [[ACPI fan control script|fan disabled]], minimum brightness, hard disk off (standby), WiFi off (ipw not loaded), [[How to make use of Graphics Chips Power Management features|GPU power saving]], DVD unplugged (2nd battery in bay), I can *still* only get down to 17.5 W/h. D'oh!<br />
<br />
Still, the screen is worth it if only for the sheer number of women who note, "my, what a nice screen you have" (just one this afternoon. :) It is a strange phenomenon.<br />
--[[User:gsmenden|gsmenden]] 21:45, 10 February 2006 (EST)<br />
----<br />
<br />
Haha, good one, [[User:gsmenden|gsmenden]] :)<br />
<br />
On my T43 here, I have around 13300mW, when:<br />
<br />
* cstate=C4, 800Mhz, undervolted (0.716V, rather than 0.988V)<br />
* wifi=off, bt=off, fan=off, brightness=minimum<br />
* X300 put into "low" mode (it's a 15" SXGA+ screen)<br />
* pretty "dark" setup (I have basically all-black desktop)<br />
<br />
Full charge is around 77000mWh. With, say, 14000mW one should last 5.5 hours on a 9-cell battery.<br />
<br />
I can't really say that I see any other obvious venues to pursue to reduce power consumption.<br />
<br />
--[[User:igorr|igorr]]<br />
----<br />
<br />
igorr, how do you disable wifi? did you try to eject dvd drive?<br />
<br />
-bzzz<br />
----<br />
<br />
Disabling wifi can be accomplished by [[cmdroot|echo 1 > /sys/class/net/eth1/device/rf_kill]].<br />
<br />
Ejecting the dvd drive? Why would that affect power consumption?<br />
<br />
--[[User:igorr|igorr]]<br />
----<br />
<br />
yeah, rf_kill does right. if I eject dvd drive or simple type echo eject >/proc/acpi/ibm/bay, I save about 0.4W.<br />
<br />
== Gradual battery discharge ==<br />
<br />
Has anyone else noticed, that the battery keeps discharging (although very slowly) when <br />
ac? My battery charges to 95%, and then drops to 90% over the course of few hours. <br />
Then charges again and so on. I'm not at all too happy about it. <br />
Also- what is the relation of last_full to design_capacity? I have one battery, which charges <br />
to 48410 mWh, while the design capacity is 51830 mWh, the other charges to 51960 mWh with the same max. <br />
Although it used to charge to around 54000. Both are new, the first one has around 50 cycles, the second around 10. <br />
<br />
--[[User:Rasto|Rasto]] 14:28, 17 February 2006 (CET)</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Gkrellm-ThinkBat&diff=19921Gkrellm-ThinkBat2006-02-13T12:32:04Z<p>Rasto: Stupid bug went away..</p>
<hr />
<div>== Description == <br />
gkrellm-ThinkBat is meant as a replacement for the default battery meter in Gkrellm [http://www.gkrellm.net Gkrellm]. <br />
It should look like default, only it optionally shows time remaining/power consumption. It currently supports only <br />
one battery. <br />
<br />
Latest version: 0.2.2 (2006-02-13)<br />
<br />
== Prerequisites ==<br />
<br />
* [http://freshmeat.net/redir/gkrellm/32404/url_homepage/www.gkrellm.net gkrellm] (packaged by most Linux distributions)<br />
* [[tp_smapi]] kernel module<br />
<br />
== Installation ==<br />
Download the [http://www.ksp.sk/~rasto/gkrellm-thinkbat/gkrellm-thinkbat-latest.tar.gz tarball]. <br />
{{cmduser|make}}<br />
{{cmduser|make install}}<br />
this installs gkrellm-thinkbat.so to {{path|~/.gkrellm2/plugins}}. You can copy it manually elsewhere.<br />
<br />
== Screenshot ==<br />
[[image:gkrellm-thinkbat.png]] [[image:gkrellm-thinkbat2.png]]<br />
<br />
== Bugs ==<br />
Please report any bugs or suggestions to [[User_talk:rasto]]. <br />
<br />
<br />
[[Category:Tools]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Template:ThinkWiki_News&diff=19713Template:ThinkWiki News2006-02-10T11:03:44Z<p>Rasto: shameless ad, (but I need someone to test it ;-))</p>
<hr />
<div>10.02.2006: Alpha version of [[Gkrellm-ThinkBat|Gkrellm-ThinkBat]] plugin<br />
<br />
30.01.2006: Please test [[KThinkBat|KThinkBat-0.1.5_rc2]]<br />
<br />
17.01.2006: Have a look at our new [[ThinkWiki:Anti_Spam_Policy|anti spam policy]]!<br />
<br />
14.01.2006: ThinkWiki has been upgraded to [[Special:Version|mediawiki 1.5.5]]<br />
<br />
12.01.2006: [[KThinkBat|KThinkBat-0.1.5_alpha2]] now uses the [[Tp_smapi|tp_smapi]] driver<br />
<br />
12.01.2006: ThinkWiki needs more than two bytes to count its registered users.</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Template:Industry_News&diff=19712Template:Industry News2006-02-10T10:57:58Z<p>Rasto: </p>
<hr />
<div>10.02.2006 New [[fglrx]] driver version 8.22.5 released<br />
<br />
28.01.2006 Lenovo and others have [http://www.pc.ibm.com/us/thinkpad/tseries/workstation.html first mention] of [[:Category:T60p|T60p]] models.<br />
<br />
19.01.2006 New [[fglrx]] driver version 8.21.7 released<br />
<br />
14.01.2006 A bit old news: [http://www.businessweek.com/technology/content/dec2005/tc20051221_376268.htm?campaign_id=rss_tech Lenovo hires new CEO from Dell].<br />
<br />
05.01.2006 Lenovo [http://www.pc.ibm.com/ww/thinkpad/x-t.html?re=home_primary_us announces] the next step in X and T series: [[:Category:X60|X60]], [[:Category:X60s|X60s]] and [[:Category:T60|T60]].</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Gkrellm-ThinkBat&diff=19711Gkrellm-ThinkBat2006-02-10T10:52:10Z<p>Rasto: </p>
<hr />
<div>== Description == <br />
gkrellm-ThinkBat is meant as a replacement for the default battery meter in Gkrellm [http://www.gkrellm.net Gkrellm]. <br />
It should look like default, only it optionally shows time remaining/power consumption. It currently supports only <br />
one battery. <br />
<br />
Latest version: 0.2.1 (2006-02-09)<br />
<br />
== Prerequisites ==<br />
<br />
* [http://freshmeat.net/redir/gkrellm/32404/url_homepage/www.gkrellm.net gkrellm] (packaged by most Linux distributions)<br />
* [[tp_smapi]] kernel module<br />
<br />
== Installation ==<br />
Download the [http://www.ksp.sk/~rasto/gkrellm-thinkbat/gkrellm-thinkbat-latest.tar.gz tarball]. <br />
{{cmduser|make}}<br />
{{cmduser|make install}}<br />
this installs gkrellm-thinkbat.so to {{path|~/.gkrellm2/plugins}}. You can copy it manually elsewhere.<br />
<br />
== Screenshot ==<br />
[[image:gkrellm-thinkbat.png]] [[image:gkrellm-thinkbat2.png]]<br />
<br />
== Bugs ==<br />
Please report any bugs or suggestions to [[User_talk:rasto]]. There seems to be a issue with the alert going <br />
off when it's not supposed to, hopefully it is solved in 0.2.1. However, don't bind your battery alarm to a<br />
ejection seat or like.<br />
<br />
<br />
[[Category:Tools]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Gkrellm-ThinkBat&diff=19704Gkrellm-ThinkBat2006-02-09T13:52:26Z<p>Rasto: </p>
<hr />
<div>== Description == <br />
gkrellm-ThinkBat is meant as a replacement for the default battery meter in Gkrellm [http://www.gkrellm.net Gkrellm]. <br />
It should look like default, only it optionally shows time remaining/power consumption. It currently supports only <br />
one battery. <br />
<br />
Latest version: 0.2.1 (2006-02-09)<br />
<br />
== Prerequisites ==<br />
<br />
* [http://freshmeat.net/redir/gkrellm/32404/url_homepage/www.gkrellm.net gkrellm] (packaged by most Linux distributions)<br />
* [[tp_smapi]] kernel module<br />
<br />
== Installation ==<br />
Download the [http://www.ksp.sk/~rasto/gkrellm-thinkbat/gkrellm-thinkbat-latest.tar.gz tarball]. <br />
{{cmduser|make}}<br />
{{cmduser|make install}}<br />
this installs gkrellm-thinkbat.so to {{path|~/.gkrellm2/plugins}}. You can copy it manually elsewhere.<br />
<br />
== Screenshot ==<br />
[[image:gkrellm-thinkbat.png]] [[image:gkrellm-thinkbat2.png]]<br />
<br />
<br />
[[Category:Tools]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Gkrellm-ThinkBat&diff=19542Gkrellm-ThinkBat2006-02-07T17:34:57Z<p>Rasto: /* Installation */</p>
<hr />
<div>== Description == <br />
gkrellm-ThinkBat is meant as a replacement for the default battery meter in Gkrellm [http://www.gkrellm.net Gkrellm]. <br />
It should look like default, only it optionally shows time remaining/power consumption. It currently supports only <br />
one battery. <br />
<br />
Latest version: 0.2 (2006-02-06)<br />
<br />
== Prerequisites ==<br />
<br />
* [http://freshmeat.net/redir/gkrellm/32404/url_homepage/www.gkrellm.net gkrellm] (packaged by most Linux distributions)<br />
* [[tp_smapi]] kernel module<br />
<br />
== Installation ==<br />
Download the [http://www.ksp.sk/~rasto/gkrellm-thinkbat/gkrellm-thinkbat-latest.tar.gz tarball]. <br />
{{cmduser|make}}<br />
{{cmduser|make install}}<br />
this installs gkrellm-thinkbat.so to {{path|~/.gkrellm2/plugins}}. You can copy it manually elsewhere.<br />
<br />
== Screenshot ==<br />
[[image:gkrellm-thinkbat.png]] [[image:gkrellm-thinkbat2.png]]<br />
<br />
<br />
[[Category:Tools]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=File:Gkrellm-thinkbat2.png&diff=19541File:Gkrellm-thinkbat2.png2006-02-07T17:33:32Z<p>Rasto: </p>
<hr />
<div></div>Rastohttps://www.thinkwiki.org/w/index.php?title=Gkrellm-ThinkBat&diff=19540Gkrellm-ThinkBat2006-02-07T17:33:13Z<p>Rasto: /* Screenshot */</p>
<hr />
<div>== Description == <br />
gkrellm-ThinkBat is meant as a replacement for the default battery meter in Gkrellm [http://www.gkrellm.net Gkrellm]. <br />
It should look like default, only it optionally shows time remaining/power consumption. It currently supports only <br />
one battery. <br />
<br />
Latest version: 0.2 (2006-02-06)<br />
<br />
== Prerequisites ==<br />
<br />
* [http://freshmeat.net/redir/gkrellm/32404/url_homepage/www.gkrellm.net gkrellm] (packaged by most Linux distributions)<br />
* [[tp_smapi]] kernel module<br />
<br />
== Installation ==<br />
Download the [http://www.ksp.sk/~rasto/gkrellm-thinkbat/gkrellm-thinkbat-latest.tar.gz tarball]. <br />
{{cmduser|make}}<br />
{{cmduser|make install}}<br />
this istalls gkrellm-thinkbat.so to {{path|~/.gkrellm2/plugins}}. You can copy it manually elsewhere.<br />
<br />
== Screenshot ==<br />
[[image:gkrellm-thinkbat.png]] [[image:gkrellm-thinkbat2.png]]<br />
<br />
<br />
[[Category:Tools]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=File:Gkrellm-thinkbat.png&diff=19539File:Gkrellm-thinkbat.png2006-02-07T17:30:38Z<p>Rasto: </p>
<hr />
<div></div>Rastohttps://www.thinkwiki.org/w/index.php?title=Gkrellm-ThinkBat&diff=19538Gkrellm-ThinkBat2006-02-07T17:30:08Z<p>Rasto: </p>
<hr />
<div>== Description == <br />
gkrellm-ThinkBat is meant as a replacement for the default battery meter in Gkrellm [http://www.gkrellm.net Gkrellm]. <br />
It should look like default, only it optionally shows time remaining/power consumption. It currently supports only <br />
one battery. <br />
<br />
Latest version: 0.2 (2006-02-06)<br />
<br />
== Prerequisites ==<br />
<br />
* [http://freshmeat.net/redir/gkrellm/32404/url_homepage/www.gkrellm.net gkrellm] (packaged by most Linux distributions)<br />
* [[tp_smapi]] kernel module<br />
<br />
== Installation ==<br />
Download the [http://www.ksp.sk/~rasto/gkrellm-thinkbat/gkrellm-thinkbat-latest.tar.gz tarball]. <br />
{{cmduser|make}}<br />
{{cmduser|make install}}<br />
this istalls gkrellm-thinkbat.so to {{path|~/.gkrellm2/plugins}}. You can copy it manually elsewhere.<br />
<br />
== Screenshot ==<br />
[[image:gkrellm-thinkbat.png]]<br />
<br />
<br />
[[Category:Tools]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Gkrellm-ThinkBat&diff=19413Gkrellm-ThinkBat2006-02-06T14:27:14Z<p>Rasto: </p>
<hr />
<div>== Description == <br />
gkrellm-ThinkBat is meant as a replacement for the default battery meter in Gkrellm [http://www.gkrellm.net Gkrellm]. <br />
It should look like default, only it optionally shows time remaining/power consumption. <br />
<br />
Latest version: 0.2 (2006-02-06)<br />
== Installation ==<br />
Download the [http://www.ksp.sk/~rasto/gkrellm-thinkbat/gkrellm-thinkbat-latest.tar.gz tarball]. <br />
{{cmduser|make}}<br />
{{cmduser|make install}}<br />
this istalls gkrellm-thinkbat.so to {{path|~/.gkrellm2/plugins}}. You can copy it manually elsewhere.<br />
<br />
[[Category:Tools]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Tp_smapi&diff=19408Tp smapi2006-02-06T13:48:01Z<p>Rasto: /* Tools using this driver */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |The <tt>tp_smapi</tt> kernel module exposes some features of the ThinkPad's [[SMAPI support for Linux|SMAPI]] functionality via a <tt>sysfs</tt> interface. Currently, the implemented functionality is control of battery charging, extended battery status and control of CD/DVD speed (disabled by default).<br />
<br />
For old ThinkPad models, see also [[tpctl]].<br />
<br />
{{WARN|This driver uses undocumented features and direct hardware access. They thus cannot be guaranteed to work, and may cause arbitrary damage (though so far none was reported)..}}<br />
<br />
|}<br />
<br />
===Features===<br />
*Battery charge/discharge control<br />
*Battery status information<br />
*Optical drive speed control (disabled by default)<br />
<br />
===Project Homepage / Availability===<br />
* Project page: http://tpctl.sourceforge.net/<br />
* You need to download only the [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=171579 tp_smapi kernel module].<br />
<br />
===Installation===<br />
For testing, you can simply compile and load the driver within the current<br />
working directory:<br />
:{{cmdroot|tar xzvf tp_smapi-0.16.tgz}}<br />
:{{cmdroot|cd tp_smapi-0.16}}<br />
:{{cmdroot|make load}}<br />
<br />
To compile and install into the kernel's module path:<br />
:{{cmdroot|make install}}<br />
<br />
If you use the [[HDAPS]] driver, add <tt>HDAPS=1</tt> to also patch the <tt>hdaps</tt> for compatibility with <tt>tp_smapi</tt> (this requires a kernel source tree):<br />
:{{cmdroot|1=make load HDAPS=1}} &nbsp; or &nbsp; {{cmdroot|1=make install HDAPS=1}}<br />
<br />
<br />
To prepare a stand-alone patch against the current kernel tree (including<br />
a compatibility fixes to <tt>hdaps</tt> and <tt>Kconfig</tt> entries):<br />
:{{cmdroot|make patch}}<br />
<br />
To delete all autogenerated files:<br />
:{{cmdroot|make clean}}<br />
<br />
The original kernel tree is never modified by any these commands. <br />
The {{path|/lib/modules}} directory is modified only by {{cmdroot|make install}}.<br />
<br />
===Battery charge control features===<br />
To set the thresholds for starting and stopping battery charging (in percent of current full charge capacity):<br />
:{{cmdroot|echo 40 > /sys/devices/platform/smapi/BAT0/start_charge_thresh}}<br />
:{{cmdroot|echo 70 > /sys/devices/platform/smapi/BAT0/stop_charge_thresh}}<br />
:{{cmdroot|cat /sys/devices/platform/smapi/BAT0/*_charge_thresh}}<br />
{{HINT|Battery charging thresholds can be used to keep Li-Ion ad Li-Polymer batteries partially charged, in order to [[Maintenance#Battery_Treatment|increase their lifetime]].}}<br />
To unconditionally inhibit charging for 17 minutes:<br />
:{{cmdroot|echo 17 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes}}<br />
{{HINT|Charge inhibiting can be used to reduce the power draw of the laptop, in order to use a an under-spec power supply that can't handle the combined power draw of running and charging. It can also be used to control which battery is charged when [[How to use UltraBay batteries|using an Ultrabay battery]].}}<br />
<br />
To cancel charge inhibiting:<br />
:{{cmdroot|echo 0 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes}}<br />
<br />
To force battery discharging even if connected to AC, use one of these:<br />
:{{cmdroot|echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge}}<br />
{{HINT|This can be used to choose which battery is discharged when [[How to use UltraBay batteries|using an UltraBay battery]].}}<br />
<br />
To cancel forced discharge:<br />
:{{cmdroot|echo 0 > /sys/devices/platform/smapi/BAT0/force_discharge}}<br />
<br />
===Battery status features===<br />
To view extended battery status such as charging state, voltage, current, capacity, cycle count and model information:<br />
<br />
<pre><br />
# cat /sys/devices/platform/smapi/BAT0/installed<br />
# cat /sys/devices/platform/smapi/BAT0/state # idle/charging/discharging<br />
# cat /sys/devices/platform/smapi/BAT0/cycle_count <br />
# cat /sys/devices/platform/smapi/BAT0/current_now # instantaneous current<br />
# cat /sys/devices/platform/smapi/BAT0/current_avg # last minute average<br />
# cat /sys/devices/platform/smapi/BAT0/power_now # instantaneous power<br />
# cat /sys/devices/platform/smapi/BAT0/power_avg # last minute average<br />
# cat /sys/devices/platform/smapi/BAT0/last_full_capacity<br />
# cat /sys/devices/platform/smapi/BAT0/remaining_capacity<br />
# cat /sys/devices/platform/smapi/BAT0/design_capacity<br />
# cat /sys/devices/platform/smapi/BAT0/voltage<br />
# cat /sys/devices/platform/smapi/BAT0/design_voltage<br />
# cat /sys/devices/platform/smapi/BAT0/manufacturer<br />
# cat /sys/devices/platform/smapi/BAT0/model<br />
# cat /sys/devices/platform/smapi/BAT0/serial<br />
# cat /sys/devices/platform/smapi/BAT0/barcoding<br />
# cat /sys/devices/platform/smapi/BAT0/chemistry<br />
# cat /sys/devices/platform/smapi/ac_connected<br />
</pre><br />
<br />
The raw status data is also available, including some fields not listed above (in case you can figure them out):<br />
<br />
:{{cmdroot|cat /sys/devices/platform/smapi/BAT0/dump}}<br />
<br />
In all of the above, replace <tt>BAT0</tt> with <tt>BAT1</tt> to address the 2nd battery.<br />
<br />
Note that the battery status readout conflicts with the stock [[HDAPS|hdaps]] driver, so if you use <tt>hdaps</tt> you will need to load <tt>tp_smapi</tt> using {{cmdroot|1=make load HDAPS=1}} (see [[#Conflict_with_hdaps|Conflict with hdaps]] below).<br />
<br />
===Optical drive control features===<br />
<br />
To control the speed of the optical drive:<br />
:{{cmdroot|echo 0 > /sys/devices/platform/smapi/cd_speed # slow}}<br />
:{{cmdroot|echo 1 > /sys/devices/platform/smapi/cd_speed # medium}}<br />
:{{cmdroot|echo 2 > /sys/devices/platform/smapi/cd_speed # fast}}<br />
:{{cmdroot|cat /sys/devices/platform/smapi/cd_speed}}<br />
<br />
=====Enabling this feature=====<br />
Changing the drive speed when a disc is being accessed will hang your computer. This feature is thus '''disabled by default''', but can be enabled using by adding <tt>#define PROVIDE_CD_SPEED</tt> at the top of <tt>tp_smapi.c</tt>. The safe way to set the drive speed is using <tt>hdparm -E num</tt> or <tt>eject -x num</tt> for CD-ROM, and <tt>speedcontrol -x num</tt> (sourcecode [http://safari.iki.fi/speedcontrol.c here]) for DVD. For kernels older than 2.6.15, this may require the [[Problems_with_SATA_and_Linux#No_SMART_support libata pass-through|libata pass-through patch]].<br />
<br />
===Features not yet implemented===<br />
Other things that can be controlled through SMAPI, but are not supported in this version of the driver, include PCI bus power saving, CPU power saving control and fan control (the latter is available through an [[How to control fan speed|alternative method]]). See the included README file for more information.<br />
<br />
===Conflict with <tt>hdaps</tt>===<br />
The extended battery status function conflicts with the [[HDAPS|hdaps]] kernel module (they use the same IO ports). <br />
<br />
You can use <tt>HDAPS=1</tt> (see [[#Installation|Installation]]) to get a patched version of <tt>hdaps</tt> which is compatible with <tt>tp_smapi</tt>. <br />
<br />
Otherwise:<br />
<br />
If you load <tt>hdaps</tt> first, <tt>tp_smapi</tt> will disable its battery status functions (and log a message in the kernel log). If you load <tt>tp_smapi</tt> first, <tt>hdaps</tt> will refuse to load. To switch between the two, <tt>rmmod</tt> both and then load one you need.<br />
<br />
Some of the battery status is also visible through ACPI ({{path|/proc/acpi/battery/*}}).<br />
<br />
The charging control files (<tt>*_charge_thresh</tt>, <tt>inhibit_charge_minutes</tt> and <tt>force_discharge*</tt>) don't have this problem.<br />
<br />
===Model-specific status===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|+<tt>tp_smapi</tt> feature support matrix<br />
|-<br />
! &times; <br />
! <tt>start_charge_<br />thresh</tt> <br />
! <tt>stop_charge_<br />thresh</tt><br />
! <tt>inhbit_charge_<br />minutes</tt><br />
! <tt>force_discharge</tt><br />
! battery status files<br \><font size="-2">(see [[#Conflict_with_hdaps|note about <tt>hdaps</tt>]] above)</font><br />
! <tt>cd_speed</tt><br \><font size="-2">(see [[#Enabling_this_feature|note]] above)</font><br />
|-<br />
! colspan=7 style="text-align:center;background:#efefef;" | G series<br />
|-<br />
! {{G41}}<br />
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}}|| {{Cyes}} <br />
|-<br />
! colspan=7 style="text-align:center;background:#efefef;" | R series<br />
|-<br />
! {{R40}}<br />
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}}|| {{Cyes}} <br />
|-<br />
! {{R50}}<br />
| {{Cunk}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cyes}}|| {{Cunk}} <br />
|-<br />
! {{R50p}}<br />
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}}|| {{Cyes}} <br />
|-<br />
! {{R51}}<br />
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cyes}}|| {{Cunk}} <br />
|-<br />
! {{R52}}<br />
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}}|| {{Cyes}} <br />
|-<br />
! colspan=7 style="text-align:center;background:#efefef;" | T series<br />
|-<br />
! {{T22}}<br />
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} <br />
|-<br />
! {{T23}}<br />
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}}|| {{Cunk}} <br />
|-<br />
! {{T40}}<br />
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}}|| {{Cyes}} <br />
|-<br />
! {{T40p}}<br />
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}}|| {{Cyes}} <br />
|-<br />
! {{T41}}<br />
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}}|| {{Cyes}} <br />
|-<br />
! {{T41p}}<br />
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}}|| {{Cyes}} <br />
|-<br />
! {{T42}}<br />
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}}|| {{Cyes}} <br />
|-<br />
! {{T42p}}<br />
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}}|| {{Cunk}} <br />
|-<br />
! {{T43}}<br />
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}}|| {{Cyes}} <br />
|-<br />
! {{T43p}}<br />
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}}|| {{Cyes}} <br />
|-<br />
! colspan=7 style="text-align:center;background:#efefef;" | X series<br />
|-<br />
! {{X24}}<br />
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}}|| {{Cunk}} <br />
|-<br />
! {{X31}}<br />
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}}|| {{Cunk}} <br />
|-<br />
! {{X32}}<br />
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}}|| {{Cunk}} <br />
|-<br />
! {{X40}}<br />
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cyes}}|| {{Cunk}} <br />
|-<br />
! {{X41}}<br />
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}}|| {{Cunk}} <br />
|}<br />
<br />
Please update the above and report your experience on the [[Talk:tp_smapi|discussion]] page. If the module loads but gives a "<tt>not supported</tt>" or "<tt>not implementeded</tt>" when you try to use some specific file in {{path|/sys/devices/platform/smapi/}}, please report the <tt>dmesg</tt> output and whether the corresponding functionality is available under Windows - maybe your ThinkPad just can't do that.<br />
<br />
[[Category:Drivers]] [[Category:Patches]]<br />
<br />
===Tools using this driver===<br />
<br />
The driver's interface can be accessed directly through the files under {{path|/sys/devices/platform/smapi}}, or via the following tools:<br />
* [[KThinkBat]] - display battery status on the KDE <tt>kicker</tt> panel.<br />
* [[gkrellm-ThinkBat]] - battery status plugin for Gkrellm2</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Super_A/G&diff=19034Talk:Super A/G2006-01-27T12:49:41Z<p>Rasto: </p>
<hr />
<div>I took me some time to find out how to do this, so I posted a brief summary here. It is brief, <br />
so one needs to take time to do it, it can mess up your eeprom big-time. <br />
If you feel, that it shouldn't be here, I can move it somewhere else and leave here a link.<br />
<br />
[[User:Rasto|Rasto]] 13:49, 27 January 2006 (CET)</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Super_A/G&diff=19033Super A/G2006-01-27T12:45:17Z<p>Rasto: </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 />
Atheros chipsets such as AR5001X+ found in [[IBM_11a/b/g_Wireless_LAN_Mini_PCI_Adapter]] and AR5004X found in [[IBM_11a/b/g_Wireless_LAN_Mini_PCI_Adapter_II]]<br />
support atheros Super A and Super G (also known as Turbo) modes. These allow using of two channels for transmition between two Atheros devices, <br />
allowing for speeds up to 108Mbit/s. <br />
|}<br />
These modes are however sometimes turned off on the WiFi card's EEPROM. When using [[Madwifi]] drivers, you can check, whether it is turned on. <br />
<br />
With turbo modes on, madwifi driver should say something like this upon load.<br />
<br />
{{cmdresult|wifi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps}}<br />
<br />
{{cmdresult|wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps}}<br />
<br />
{{cmdresult|wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps}}<br />
<br />
{{cmdresult|wifi0: turboA rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps}}<br />
<br />
{{cmdresult|wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps}}<br />
<br />
If it states onle turboG rate, it may be a problem with countrycode/region domain. Search [[Madwifi]] mailinglists for solution. <br />
If the driver detects no turbo modes and setting region domain doesn't help, you may need to turn them on. This can probably be done <br />
using Microsoft [[:Category:Windows|Windows]]. See [http://forum.thinkpads.com/viewtopic.php?t=4840 this] thread.<br />
<br />
If you really want to get this to work, and you don't have Windows, it is still possible, so read on. <br />
<br />
=== Setting Turbo modes in Linux ===<br />
{{Todo| If anybody knows how to do this in a cleaner or nicer way, please rewrite this.}}<br />
{{WARN| Big Fat Warning 1: Don't continue reading, unless you really have no other choice. Doing this is dangerous, may and probably will render your wireless device <br />
nonfunctional and useless. You are doing it at your own responsibility! }}<br />
{{WARN| Big Fat Warning 2: It is REQUIRED that you have some knowledge of C and and an idea how memory works. Withouth these, don't even bother.}}<br />
{{WARN| Big Fat Warning 3: Proceed with doing this if and only if you at all points understand, what you are doing, and what do you need to do to reverse all changes <br />
you have done.}}<br />
<br />
First of all, you need to get drivers from the [http://www.ath-driver ath-driver] project to work. If these don't work (and they may not!), <br />
trying this unnecessarily dangerous, as any slip will render your card useless, as [[Madwifi]] closed HAL won't load and you won't be able to access the EEPROM <br />
to repair the damage. <br />
<br />
Download [http://www.ksp.sk/~rasto/mod2.c], or find another ar5k modified to do something similar and modify it to do what you want. <br />
<br />
The capability bits, located at 0x00c2 are described in eeprom.c of ath-driver. You need to set the "Disable turbo A" and "Disable turbo G" bits <br />
to 0. Doing this straight away will however violate checksum for EEPROM, which is done XORing subsequent 2-bytes. They should XOR up to 0xffff. <br />
Therefore, if you modify these two bits, you need to add 0x8008 (or whatever orig^new^0xffff gives) somewhere where the EEPROM is not used, <br />
or find out the bits which are actually used <br />
for this. For example bytes around 0x00cc seem to be empty (but may not be with your card! Check it!). <br />
mod2.c contains two commented-out parts. The first can be used for the actual rewriting, the second to dump the relevant parts of EEPROM, which <br />
are 0x00c0 to 0x00c0+832.<br />
If anything bad happens, source code for the ath-driver can be of great help.</div>Rastohttps://www.thinkwiki.org/w/index.php?title=User:Rasto&diff=19031User:Rasto2006-01-27T11:41:19Z<p>Rasto: </p>
<hr />
<div>I own a [[:Category:T43|T43]] 2686-E6U (Contrary to what is in tabook, it has a 14" SXGA+ display and no fingerprint reader), <br />
running [[:Category:Debian|Debian]] unstable. I also take care of my girfriend's [[:Category:600E|600E]] running almost identical software.</div>Rastohttps://www.thinkwiki.org/w/index.php?title=IBM_11a/b/g_Wireless_LAN_Mini_PCI_Adapter_II&diff=19030IBM 11a/b/g Wireless LAN Mini PCI Adapter II2006-01-27T11:16:18Z<p>Rasto: </p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<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 />
=== IBM 11a/b/g Wireless LAN Mini PCI Adapter II ===<br />
This is a Mini-PCI WiFi Adapter that is installed in a Mini-PCI slot<br />
<br />
=== Features ===<br />
* Chipset: Atheros AR5004X<br />
* Radio Chip: Atheros AR5112<br />
* MAC Processor: Atheros AR5213<br />
* IEEE Standards: 802.11a, 802.11b, 802.11g<br />
* PCI ID: 168c:1014<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:mini-pci-wifi-card.gif|Mini-PCI WiFi Adapter]]<br />
|}<br />
<br />
=== IBM Partnumbers ===<br />
'''Ambit parts'''<br><br />
IBM Option PN (WW): 73P4301<br><br />
IBM Option PN (Philippines, Singapore, Indonesia, Taiwan, China): 73P4302<br><br />
IBM Option PN (Japan): 73P4303<br><br />
IBM FRU PN (WW): 93P4262<br><br />
IBM FRU PN (Philippines, Singapore, Indonesia, Taiwan, China): 93P4264<br><br />
IBM FRU PN (Japan): 93P4266<br><br />
<br />
'''Bartlett parts'''<br><br />
IBM FRU PN (US): 27K9944<br><br />
IBM FRU PN (EU): 27K9946<br><br />
IBM FRU PN (Japan): 27K9948<br><br />
IBM FRU PN (Taiwan): 27K9999<br><br />
<br />
=== Also known (in IBM literature) as.... ===<br />
* 802.11a/b/g Ambit wireless Card<br />
* 802.11a/b/g Bartlett Wireless Card<br />
* ThinkPad 11a/b/g Mini PCI Adapter II<br />
<br />
=== Additional features ===<br />
The chipset supports Atheros eXtended Range (XR) technology, and Atheros [[Super A/G]] (Turbo) modes.<br />
<br />
=== Linux WiFi driver ===<br />
This is an Atheros chip and works with the [[Madwifi]] driver "out of the box". This card will be also detected by open-source [http://www.ath-driver.org ath-driver], but as of <br />
now (end of January '06), it doesn't support actual wireless operations. <br />
<br />
Make sure that your kernel supports "CONFIG_SECURITY_CAPABILITIES", or you might get some message from the Atheros hal that it does not support all features.<br />
<br />
=== ThinkPads this card may be found in ===<br />
* {{R51}}, {{R52}}<br />
* {{T41p}},{{T42p}},{{T43}}, {{T43p}}<br />
* {{X32}}<br />
* {{X40}}, {{X41}}<br />
* {{Z60m}}<br />
<br />
=== Related Links ===<br />
*Specifications: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57210 MIGR-57210]<br />
*Users Guide: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57217 MIGR-57217]<br />
*Service Parts: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57214 MIGR-57214]<br />
<br />
<br />
[[Category:Components]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=IBM_11a/b/g_Wireless_LAN_Mini_PCI_Adapter_II&diff=19020IBM 11a/b/g Wireless LAN Mini PCI Adapter II2006-01-26T17:43:56Z<p>Rasto: /* Linux WiFi driver */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<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 />
=== IBM 11a/b/g Wireless LAN Mini PCI Adapter II ===<br />
This is a Mini-PCI WiFi Adapter that is installed in a Mini-PCI slot<br />
<br />
=== Features ===<br />
* Chipset: Atheros AR5004X<br />
* Radio Chip: Atheros AR5112<br />
* MAC Processor: Atheros AR5213<br />
* IEEE Standards: 802.11a, 802.11b, 802.11g<br />
* PCI ID: 168c:1014<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:mini-pci-wifi-card.gif|Mini-PCI WiFi Adapter]]<br />
|}<br />
<br />
=== IBM Partnumbers ===<br />
'''Ambit parts'''<br><br />
IBM Option PN (WW): 73P4301<br><br />
IBM Option PN (Philippines, Singapore, Indonesia, Taiwan, China): 73P4302<br><br />
IBM Option PN (Japan): 73P4303<br><br />
IBM FRU PN (WW): 93P4262<br><br />
IBM FRU PN (Philippines, Singapore, Indonesia, Taiwan, China): 93P4264<br><br />
IBM FRU PN (Japan): 93P4266<br><br />
<br />
'''Bartlett parts'''<br><br />
IBM FRU PN (US): 27K9944<br><br />
IBM FRU PN (EU): 27K9946<br><br />
IBM FRU PN (Japan): 27K9948<br><br />
IBM FRU PN (Taiwan): 27K9999<br><br />
<br />
=== Also known (in IBM literature) as.... ===<br />
* 802.11a/b/g Ambit wireless Card<br />
* 802.11a/b/g Bartlett Wireless Card<br />
* ThinkPad 11a/b/g Mini PCI Adapter II<br />
<br />
=== Linux WiFi driver ===<br />
This is an Atheros chip and works with the [[Madwifi]] driver "out of the box". This card will be also detected by open-source [http://www.ath-driver.org ath-driver], but as of <br />
now (end of January '06), it doesn't support actual wireless operations. <br />
<br />
Make sure that your kernel supports "CONFIG_SECURITY_CAPABILITIES", or you might get some message from the Atheros hal that it does not support all features.<br />
<br />
=== ThinkPads this card may be found in ===<br />
* {{R51}}, {{R52}}<br />
* {{T41p}},{{T42p}},{{T43}}, {{T43p}}<br />
* {{X32}}<br />
* {{X40}}, {{X41}}<br />
* {{Z60m}}<br />
<br />
=== Related Links ===<br />
*Specifications: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57210 MIGR-57210]<br />
*Users Guide: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57217 MIGR-57217]<br />
*Service Parts: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57214 MIGR-57214]<br />
<br />
<br />
[[Category:Components]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:IBM_11a/b/g_Wireless_LAN_Mini_PCI_Adapter_II&diff=19019Talk:IBM 11a/b/g Wireless LAN Mini PCI Adapter II2006-01-26T17:37:54Z<p>Rasto: /* Super A/G */ Deleted, will add to the main page, If I find out how to do it.</p>
<hr />
<div>Hi. Regarding this card (73P4301), it has been stated on [http://www-131.ibm.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=-840&storeId=10000001&langId=-1&dualCurrId=1000073&categoryId=2581910&productId=8770176 IBM/Lenovo's parts sales page] that it is indeed compatible with the Thinkpad X31 series (2672/73, 2884/85), so I would say that the X31 should be included in the last of machines that this card can be found in.<br />
<br />
----<br />
Depends on the point of view. Right now the list contains ThinkPad featuring the cards in their default configuration. If we would change it to a list of ThinkPads supporting the card, it would in fact be a loss of information, since virtuall any recent ThinkPad supports the card, which is true for many of the other cards as well. So there is less point in this information.<br />
<br />
What we could do, however, is to include a second list of ThinkPads supporting the card.<br />
<br />
[[User:Wyrfel|Wyrfel]] 13:20, 14 Aug 2005 (CEST)<br />
----</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Problems_with_fglrx&diff=18999Problems with fglrx2006-01-26T15:47:00Z<p>Rasto: /* Patches */</p>
<hr />
<div>This page discusses issues with the ATI proprietary [[fglrx]] display driver.<br />
<br />
== Known Troubles and Solutions ==<br />
<br />
=== X-specific issues ===<br />
<br />
The current ATI proprietary driver (8.21.7) works with x.org 6.9.<br />
<br />
If you are running an older version (8.20.8) under Debian sid and you upgrade your xserver-xorg, apt will force you to remove any debian-packaged fglrx drivers (package fglrx-driver depends on x.org << 6.8.99). You can just download the driver from the ATI site and install after modifying the Debian packager script to allow dependencies to be satisfied by x.org 6.9, or just download 8.21.7 and install manually. See talk page for step-by-step commands.<br />
<br />
After installing the fglrx driver, you can use module-assist to build the appropriate kernel module.<br />
<br />
=== Kernel-specific troubles ===<br />
<br />
Using the current ATI driver (8.21.7) with 2.6.15 or later needs a [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]. (see table below for detail.) If you can't compile the driver modules with 2.6.15 or later, you should apply this [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch patch] instead. <br />
<br />
If you do not use one of these patches, you may experience peculiar lockups of X. Try {{cmduser|fglrxinfo}} - if your shell hangs at the end of this command, you may have an issue and should try the patch.<br />
<br />
Although unproven, there is a substantial amount of user / developer concern that the above patches prevent hard lockups but do not provide full reliability with 2.6.15 and there are larger / redisgn issues preventing compatibility. It seems surprising that ATI would not have implemented such a simple page count fix in their latest two driver releases since kernel 2.6.15 has been available. Given the closed-source nature of the driver, it is difficult to know for sure. As of now only 2.6.14.x kernels are officially supported by the fglrx driver.<br />
<br />
=== No hardware acceleration ===<br />
<br />
====Acceleration lost after driver update====<br />
If you lose hardware acceleration after a driver update this can be caused by an old fglrx kernel module being loaded.<br />
<br />
Check out {{path|1=/var/log/Xorg.0.log}} for a message like:<br />
:<code>(WW) fglrx(0): Kernel Module version does *not* match driver.</code><br />
:<code>(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work</code><br />
<br />
You can verify this yourself by looking at the version message some lines above. It should read something not matching the installed version like:<br />
:<code>(II) fglrx(0): Kernel Module Version Information:</code><br />
:<code>(II) fglrx(0): Name: fglrx</code><br />
:<code>(II) fglrx(0): Version: 8.10.19</code><br />
<br />
The cause for this trouble might be that there resist multiple versions of the fglrx module within the kernel module search path.<br><br />
Go to {{path|1=/lib/modules/<your linux kernel version>/}} and type {{cmdroot|1=grep fglrx modules.dep}}.<br><br />
If grep finds multiple lines you nailed down the problem. All you have to do now is to delete any versions of the module (look at the filedate) but the most current one. Then run {{cmdroot|1=depmod}} and you are done.<br />
<br />
{{HINT|The current version (8.21.7) of the fglrx module seem to be installed in the <code>extra/</code> subdirectory.<br><br />
Older versions (8.19.10) used to be located in the <code>kernel/drivers/char/drm</code> subdirectory.}}<br />
<br />
====GCC 3.4====<br />
If the ATI driver works only without the hardware acceleration, take into consideration that {{path|fglrx_dri.so}} was linked against libstdc++.so.5 which may not be present if your system uses gcc-3.4.<br />
<br />
To fix this, compile gcc-3.3.5 and copy <tt>libstdc++.so.5*</tt> to {{path|/usr/lib}} and update the dynamic linker cache via {{cmdroot|ldconfig}}.<br />
<br />
====radeonfb framebuffer====<br />
Another possible cause for broken hardware acceleration (2D and 3D) is the radeonfb framebuffer: Switching to vesafb or vesafb-tng is reported to solve the problem on some systems. Also it has proven helpful to not perform {{cmdroot|modprobe fglrx}} after boot but to have the module loaded via {{path|/etc/modules.autoload/kernel2.x}} at boottime instead.<br />
<br />
=== Softlink hell ===<br />
The [[fglrx]] installer replaces the standard X.org OpenGL implementation (Mesa) with its own files, potentially causing collisions with the distribution's file and package management. It is best to install the driver via a package built for your distribution, which will typically include the necessary kludges to make things work. See the [[fglrx]] page for pointers.<br />
<br />
====Discussion====<br />
If using {{cmduser|fglrxinfo}} after installing [[fglrx]] indicates that you are still using the mesa indirect software GL renderer, you likely have some misplaced softlinks. It seems like it has to do with an apt-get upgrade that sometimes replaces these links. Anyway, go to<br />
:{{cmdroot|cd /usr/X11R6/lib}}<br />
and list your GL libraries and links<br />
:{{cmdroot|ls -la *GL*}}<br />
You should see something like the following two lines amoung others:<br />
:{{cmdresult|libGL.so -> libGL.so.1.2}}<br />
:{{cmdresult|libGL.so.1 -> libGL.so.1.2}}<br />
If you see a link to a mesa library (something like {{cmdresult|... -> libGL.mesa.1.2}}), then that's your problem! Restore the softlink like this (use your actual library version, though):<br />
:{{cmdroot|ln -s libGL.so.1.2 libGL.so.1}}<br />
<br />
For some reason, this link might "break" later, giving you the software rendering once more. Even after renaming the mesa library to something like <tt>mesa.bkup</tt>, the system might still find it and link to it despite the name change. If you have to do this a lot, you could write a restoreGL script.<br />
<br />
=====Gentoo=====<br />
{{Gentoo}} has built in tools for managing the OpenGL symlinks. They seem to be replacing the old tool with a new one, so one of the following should work for you:<br />
:{{cmdroot|opengl-update ati}} or<br />
:{{cmdroot|eselect opengl set ati}}<br />
Eselect is new, and still ~x86 (as of the end of 2005), so you may not have it yet. <tt>opengl-update</tt> is the old tried-and-true method for managing the symlinks. If <tt>opengl-update</tt> doesn't fix it for you, you should probably tell [http://bugs.gentoo.org Gentoo Bugzilla] (assuming they don't know yet).<br />
<br />
If {{cmdroot|ldd /usr/X11R6/bin/glxinfo}} shows that your system still uses the xorg-x11 mesa libs after trying one of the above commands, i.e. a line like this:<br />
:{{cmdresult|1=libGL.so.1 => /usr/lib/opengl/xorg-x11/lib/libGL.so.1 (0x400a8000)}}<br />
you will also need to relink {{path|libGl.so.1.2}}:<br />
:{{cmdroot|cd /usr/lib/opengl/xorg-x11/lib/}}<br />
:{{cmdroot|mv libGL.so.1.2 libGL.so.1.2_backup}}<br />
:{{cmdroot|ln -s /usr/lib/libGL.so.1.2 libGL.so.1.2}}<br />
After another restart of X {{cmduser|fglrxinfo}} should show that it's using the right libs now.<br />
<br />
=== Troubles using software suspend ===<br />
When the computer resumes from suspend, X only displays a garbled image and the computer is frozen.<br />
The problem is acknowledged in ATI's release notes and in knowledge base entry [https://support.ati.com/ics/support/KBResult.asp?searchFor=Search+Words&search.x=0&search.y=0&searchOption=id&questionID=737-218+&task=knowledge&searchTime=-1&productID=&folderID=-1&resultLimit=50 737-218]. Driver version 8.19.10 has "initial support for Suspend and Resume" but is working very nicely for most people (verified on T43, T43p and T42) without vbetool.<br />
<br />
If you are using an older version of fglrx, using [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] to save/restore the video card state before/after suspend worked for some people. If you use [[Software Suspend 2|Software Suspend 2 (suspend2)]] scripts, you can simply uncomment <tt>EnableVbetool yes</tt> in {{path|/etc/hibernate/hibernate.conf}}. Be aware though that it breaks suspend/resume for drivers beginning with version 8.19.10, so remember to disable it again when upgrading.<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|+ tested with the following configurations<br />
!model!!distro||kernel!!fglrx!!PM!!success!!comments<br />
|-<br />
|{{T42}}||SUSE 9.3||2.6.11||8.14.13||swsusp||yes||<br />
|-<br />
|{{T41p}}||???||2.6.14||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch]<br />
|-<br />
|{{T42p}}||Debian||2.6.10||Debian packaged||suspend2||yes||<br />
|-<br />
|{{T43}}||Debian sid||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 (but not earlier versions!)<br />
|-<br />
|{{T43}}||Debian etch||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 and without vbetool<br />
|-<br />
|{{T43}}||Ubuntu Breezy||2.6.12-10||8.19.10||swsusp||yes||Perfect. (Finally.)<br />
|-<br />
|{{T43}}||FC4||2.6.14.1||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch], requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)<br />
|-<br />
|{{T43}}||FC4||2.6.14.2||8.19.10||suspend2 2.2-rc11||yes||requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)<br />
|-<br />
|{{T43}}||FC4||2.6.14.3||8.19.10||suspend2 2.2-rc13||no||DRI enabled<br />
|-<br />
|{{T43}}||FC4||2.6.14.3||8.20.8||suspend2 2.2-rc13||no||DRI enabled<br />
|-<br />
|{{R50p}}||???||???||8.19.10||swsusp||yes||<br />
|-<br />
|{{T43p}}||Debian sid||2.6.14||8.19.10||Suspend to RAM||yes||without vbetool or UseDummyXServer, those two ''break'' the resume process here, with DRI enabled<br />
|-<br />
|{{T43p}}||Debian sid||2.6.14.3||8.20.8||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled<br />
|-<br />
|{{R52}}||Debian sid||2.6.15-rc5||8.20.8||swsup||yes||both vbetool and UseDummyXServer disabled, DRI enabled, needs [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]<br />
|}<br />
<br />
=== Troubles with large RAM ===<br />
Version 8.14.13 (and probably earlier versions) of the driver 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 <tt>fglrx</tt> kernel module is loaded, but independently of whether {{kernelconf|CONFIG_HIGHMEM||||||}} is enabled. A workaround is to limit RAM by adding the {{bootparm|mem|864m}} kernel parameter.<br />
<br />
Version 8.16.20 fixes the problem.<br />
<br />
===Display switching ===<br />
The switching between internal and external display doesn't work, because the driver blocks messing around with the chipset via ACPI. If you want to use this feature (i.e. during presentations), you should use the <tt>vesa</tt> server instead (experienced with a R52, Kernel 2.6.11, xorg 6.8.2, fglrx 8.16.20).<br />
<br />
===Composite Support===<br />
ATI has not officially supported composite windowing (alpha channel) enabling hardware acclerated translucent windows (primarily for 'eye candy.') Enabling Composite in KDE and the fglrx driver results in a very pretty desktop but unacceptably slow performance on a T43p with ATI's FireGL T2. It is still unusable in its current state (as of driver 8.19.10).<br />
<br />
ATI promises support in the future when composite is officially supported by Xorg. Discussion of current status of drivers can be found in the Rage3d forums' (rage3d.com/board) Linux area.<br />
<br />
There were some rumors that composite support was fast with the open-source 2d accelerated drivers in x.org 6.9 (as opposed to 6.8.x). Alas, trying this gives better results than the proprietary drivers, but it is still too slow to be reasonably useful.<br />
<br />
===Hardlock on X logout===<br />
Up from driver version 8.19.10 you will expierence a system hard lock when logging out from X, if the session manager (kdm/gdm) is not properly configured. You have to tell the session manager to restart X.<br />
<br />
In the kdm config file (gentoo: {{path|/usr/kde/<VERSION>/share/config/kdm/kdmrc}}) you have to add following to the section <code>[X-:*-Core]</code>: <br />
TerminateServer=true<br />
<br />
In the gdm config file add:<br />
AlwaysRestartServer=true<br />
<br />
Information from the ATI bugtracker: http://ati.cchtml.com/show_bug.cgi?id=239<br />
<br />
===Error messages in system log===<br />
<br />
If you find something like the following in {{path|/var/log/messages}}:<br />
<br />
:{{cmdresult|kernel: mtrr: base(0xc0000000) is not aligned on a size(0x7ff0000) boundary}}<br />
:{{cmdresult|kernel: [fglrx:firegl_addmap] *ERROR* mtrr allocation failed (-22)}}<br />
:{{cmdresult|kernel: [fglrx:firegl_unlock] *ERROR* Process 5132 using kernel context 0}}<br />
<br />
try to execute the following line and reload the fglrx module:<br />
<br />
:{{cmdroot|1=echo "base=0xd0000000 size=0x8000000 type=write-combining" > /proc/mtrr}}<br />
<br />
More detailed instructions can be found [http://ubuntuforums.org/showthread.php?t=115104 here].<br />
<br />
== Patches ==<br />
The following patches might be needed for certain versions of fglrx.<br />
<br />
===fglrx 8.21.7===<br />
<br />
* [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch for kernels >= 2.6.15]<br />
<br />
===fglrx 8.20.8===<br />
<br />
* [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 for kernel 2.6.15]<br />
or<br />
* [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch for kernels >= 2.6.15]<br />
<br />
===fglrx (problem met at least with version 8.18.8)===<br />
* [http://lkml.org/lkml/2005/9/22/183 for kernel >= 2.6.13 ] Missing verify_area bug<br />
<br />
===fglrx 8.8.25 ===<br />
* [http://www.rage3d.com/board/showthread.php?t=33798874 for kernels >= 2.6.10]<br />
* [http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch For kernels >= 2.6.11-rc1]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=User_talk:Rasto&diff=18977User talk:Rasto2006-01-26T13:11:26Z<p>Rasto: </p>
<hr />
<div>Hei,<br />
<br />
sorry, my mistake with the fglrx drivers. Didn't think of that there's a source kernel module part., but of course you're right.<br />
<br />
About the date... if you place <nowiki>~~~~</nowiki> (four tildes) in your edit, it will be replaced by your linkified username plus timestamp.<br />
<br />
[[User:Wyrfel|Wyrfel]] 04:36, 26 January 2006 (CET)<br />
----<br />
Thanks :-). There's one more thing that bothers me, but I'm not quite certain about this, so I didn't add it straight away. <br />
I did fglrx installs by running ati-installer. The X11 version doesn't however report any errors most of the time, also when there are. <br />
Also. When it fnishes successfully, it leaves the *.ko files in /lib/modules/fglrx, and doesn't copy them to /lib/modules/linux-whatever/fglrx. <br />
At least very often. I'm using a official kernel, not a debian one. Perhaps this causes some of the confusion about fglrx? Also- it can be, that <br />
you install a new version and the old modules are still being loaded, and therefore accel works and you don't notice anything?<br />
<br />
[[User:Rasto|Rasto]] 14:11, 26 January 2006 (CET)</div>Rastohttps://www.thinkwiki.org/w/index.php?title=User_talk:Wyrfel&diff=18953User talk:Wyrfel2006-01-25T19:24:03Z<p>Rasto: fglrx drivers</p>
<hr />
<div>See [[User_talk:Akw]]<br />
<br />
--[[User:Akw|akw]] 13:14, 26 Sep 2004 (CEST)<br />
----<br />
I added some ibm flavour to the main stylesheet. What do you think? :-)<br />
<br />
--[[User:Akw|akw]] 21:29, 26 Sep 2004 (CEST)<br />
----<br />
<br />
Looks good.<br />
But I'd remove the stripes on the left, they look a bit too IBMish for my taste.<br />
<br />
I just added pictures to the Category pages. Looks nice. The pictures are partly from IBMs page and they have a disclaimer that says you should make a curtasy by ibm.... statement when using them. We don't use them in their original quality and you can find smallscale versions all over the net. However, we should maybe place some credits page somewhere to include this curtasy line there.<br />
<br />
[[User:Wyrfel|Wyrfel]] 21:39, 26 Sep 2004 (CEST)<br />
----<br />
<br />
== Good work ==<br />
<br />
Good work! Please continue! :-)<br />
<br />
----<br />
Hi Wyrfel,<br />
<br />
thanks for the great logo! As you may have seen, I put in in place.<br />
Unfortunately there is still no price available for the contest winner, but maybe this will change.<br />
<br />
--[[User:Akw|akw]] 14:29, 1 Mar 2005 (CET)<br />
----<br />
<br />
The honour is enough. ;-)<br />
<br />
I can send you the files as PNGs with alpha, they should look a little better then.<br />
Also, I could scale the logo to be a little smaller so that it fits better.<br />
I'm also working on a page redesign with a bigger black header to contain the logo (the bar would need to be about a 100 pixels in height).<br />
<br />
What do you think?<br />
<br />
[[User:Wyrfel|Wyrfel]] 19:55, 1 Mar 2005 (CET)<br />
----<br />
<br />
== Sorry to mess things up... ==<br />
<br />
Hey, <br />
<br />
I want to write a framedrivers howto for the 770e... Where and how should i put it? <br />
<br />
Bashusr<br />
<br />
== Missing ThinkPad's ==<br />
<br />
No category pages exist for the following:<br />
<br />
*720<br />
*720C<br />
<br />
These are ancient MCA machines (like the 700/700C)<br />
<br />
*760<br />
*760E<br />
*760ED<br />
*760L<br />
*760X<br />
*760XD<br />
*765<br />
*765D<br />
*765L<br />
<br />
These are more modern Pentium machines with flip-up keyboard.<br />
There might have been other letter variations, in addition to these.<br />
<br />
== ThinkPad's added ==<br />
<br />
I added the following ThinkPad's<br />
<br />
*370C<br />
*720<br />
*720C<br />
*760C<br />
*760CD<br />
*760E<br />
*760ED<br />
*760XD<br />
*760L<br />
*760LD<br />
*760EL<br />
*760ELD<br />
*760XL<br />
*765D<br />
*765L<br />
<br />
I also noticed that there are pages for a '701' and '755' which I am pretty sure never existed as such (701C, 701CS, 755C, 755CS, 755CD, 755CDV, 755CE, 755CV and 755CX did exist)<br />
<br />
Also the picture for the 755CD and 755CDV is wrong, as the CD-ROM models where thicker<br />
----<br />
<br />
== MediaWiki Update ==<br />
<br />
Hi Wyrfel,<br />
<br />
you suggested an Update of MediaWiki Software. The problem is, that I did a lot of changes to the software, which I maybe need to reimplement in the new software.<br />
<br />
I am going to try this the next few days, stay tuned.<br />
<br />
PS: Sorry for my absence the last few weeks.<br />
<br />
<br />
--[[User:Akw|akw]] 12:38, 10 May 2005 (CEST)<br />
<br />
== template problems ==<br />
<br />
Wyrfel,<br />
<br />
if you use a = sign in the WARN, NOTE or HINT templates like <nowiki>{{WARN|foo=bar}}</nowiki> the following happens:<br />
<br />
{{WARN|foo=bar}}<br />
<br />
The only way I found was to surround the = sign with <nowiki><nowiki></nowiki></nowiki><br />
<br />
--[[User:Tonko|Tonko]] 02:18, 22 Oct 2005 (CEST)<br />
----<br />
Yes, this is an inherent problem with MediaWikis template implementation. It is not possible to do anything about this. The way to deal with it is to call the template with <nowiki>{{WARN|1=foo=bar}}</nowiki>:<br />
{{WARN|1=foo=bar}}<br />
<br />
It is because if you give a parameter to a template the first = within this parameter is taken as separator between parameter name and parameter value. The templates are built without named parameters, which means that parameters are numbered. Hence if you call the template like above you will assign the value to parameter 1, all other = signs until the next | will be ignored and everything works fine. Read the MediaWiki Template documentation for more info.<br />
<br />
[[User:Wyrfel|Wyrfel]] 15:52, 22 Oct 2005 (CEST)<br />
<br />
== Reorganize Predesktop stuff? ==<br />
Wyrfel,<br />
<br />
I'd like to reorganize the Predesktop stuff:<br />
* There should be one (short) Predesktop Area page;<br />
* This (short) page should link to a HPA page (the present PreDesktop Area page) and to the Rescue and Recovery page;<br />
* There should be only a link to the (new) Predesktop Area page on the Technologies pages.<br />
<br />
This might be easier to navigate and explore (at first users just know they have some "Predesktop Area" when looking for help and info, they do not (yet) know which of the two technologies they're actually working with).<br />
<br />
What do you think?<br />
<br />
[[User:Pebolle|Paul Bolle]] 22:34, 8 Nov 2005 (CET)<br />
----<br />
Sounds reasonable. AFAIK there's an HPA page the redirects to the current PreDesktop Area page already. If i'm wrong, however, please create it. It should be categorized in the Glossary category, i think. The PreDesktop Area page should maynly be about PreDesktop Area, anyways, but i agree that it should contain a stronger clarification to separate the Rescue%Recovery partition stuff. I put my trust in you. ;-)<br />
<br />
I'm on the road for the next few weeks, so i'll not so regularly have a glimpse.<br />
<br />
Feel free to do what you find reasonable.<br />
<br />
[[User:Wyrfel|Wyrfel]] 03:51, 9 Nov 2005 (CET)<br />
----<br />
<br />
== Red Hat spelling ==<br />
<br />
Wyrfel,<br />
<br />
Another cleanup I was thinking of was changing "Redhat" to "Red Hat", basically create a new Category page, move all the existing pages to it (which includes a lot of page moves), and then delete the old Category.<br />
<br />
--[[User:Tonko|Tonko]] 17:10, 18 January 2006 (CET)<br />
----<br />
We don't need to move that many pages. I'll do the start. It's mostly the category page and changing the redhat template. (we should keep that spelled as one word, i think) The moving the installation pages, ok, that's a bit of a fuss. But yes, better now than later.<br />
<br />
[[User:Wyrfel|Wyrfel]] 12:12, 19 January 2006 (CET)<br />
----<br />
<br />
== HDAPS ==<br />
<br />
Thanks for re-organising the hdaps info, looks much better now...<br />
<br />
== fglrx drivers ==<br />
<br />
<br />
Driver modules? The thing that resides in /lib/modules/fglrx/build_mod, or wherever when you install the source packages? I really didn't bother looking <br />
what it actually does, but I imagine it being some sort of wrapper around binary modules? Sorry about that. Also- what should I do, to get my name <br />
and date appear after every post? There's probably a command for the date? I couldn't find it. Thanks. <br />
<br />
[[User:Rasto|Rasto]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Problems_with_fglrx&diff=18952Talk:Problems with fglrx2006-01-25T19:23:21Z<p>Rasto: /* Compile ATI driver??? */</p>
<hr />
<div>== using kernel AGP vs fglrx AGP ==<br />
<br />
Anyone know whether this makes a performance and/or stability difference?<br />
<br />
== 8.20.8 and later works with current Debian sid packages ==<br />
<br />
<pre><br />
spiney@t43p:~$ dpkg -l xserver-xorg<br />
Desired=Unknown/Install/Remove/Purge/Hold<br />
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed<br />
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)<br />
||/ Name Version Description<br />
+++-============================-============================-==================<br />
ii xserver-xorg 6.9.0.dfsg.1-2 the X.Org X server<br />
spiney@t43p:~$ fglrxinfo <br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: MOBILITY FireGL V3200 Pentium 4 (SSE2) (FireGL) (GNU_ICD)<br />
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)<br />
</pre><br />
<br />
--[[User:Spiney|spiney]]<br />
----<br />
<br />
Ahh - thanks for the info. You perhaps compiled the modules for the drivers yourself and did not use the debian packaged fglrx-driver? Thus, it must be an unneeded limitation on the debian packaged driver which limits its installation... Full listing at http://packages.debian.org/unstable/x11/fglrx-driver which lists as required packages:<br />
<br />
xserver-xorg (<< 6.8.99)<br />
the X.Org X server <br />
xserver-xorg (>= 6.8.0) <br />
<br />
The first limitation (<<6.8.99) is what prevents installation. I'm sure I could force apt to install it, but I may go back to compiling the modules myself, as using fglrx 8.20.8 with kernel 2.6.15 needs a small patch to compile correctly anyway... --[[User:gsmenden|gsmenden]]<br />
<br />
Spiney, where exactly do you have your package from? I re-build the 8.20.8-package from debian with the <<6.8.99 dependecy removed, but when I try to run X, I get <br />
[R200Setup] X version mismatch - detected X.org 7.0.0.0, required X.org 6.8.0.0<br />
(EE) Failed to load module "fglrx" (module requirement mismatch, 0)<br />
Any hints? --[User:nomeata|nomeata]<br />
<br />
I used the ati-installer (the huge download), created a Debian sid package and installed it, but got the same error. The installer seems to fetch the wrong driver version from the archive, so I extracted it with<br />
<br />
{{cmd|./ati-driver-installer-8.20.8-i386.run --extract <sometempdir>|}}<br />
<br />
and put the necessary files from the created {{path|<sometempdir>/x690}} subdirectory into {{path|/usr}} by hand. All IIRC, it's been some time since. :)<br />
<br />
--[[User:Spiney|spiney]] 07:29, 11 Jan 2006 (CET)<br />
<br />
Thanks for the pointer. This is how you get proper debian packages out of the ati-installer:<br />
./ati-driver-installer-8.20.8-i386.run --extract fglrx-tmp<br />
cd fglrx-tmp<br />
$editor packages/Debian/ati-packager.sh # in the line "sid|unstable) X_DIR=x680;;", put a x690 for the x680<br />
./fglrx-tmp/packages/Debian/ati-packager.sh --buildpkg sid<br />
cd ..<br />
sudo dpkg -i fglrx-kernel-src_8.20.8-1_i386.deb fglrx-driver_8.20.8-1_i386.deb<br />
--[[User:Nomeata|Nomeata]] 00:35, 13 Jan 2006 (CET)<br />
<br />
<br />
----<br />
<br />
Nice - confirmed works on my T43p running sid. From then on (or until 8.21.x comes out) you'll have to tell apt to hold back fglrx-driver package, or it will try to "update" fglrx-driver to 8.20.8-1.1 and therefore revert back to the problematic drivers.<br />
--[[User:gsmenden|gsmenden]]<br />
----<br />
<br />
Thanks for the info, Nomeata, that's a lot cleaner a solution than my manual way.<br />
<br />
--[[User:Spiney|spiney]] 08:32, 13 Jan 2006 (CET)<br />
----<br />
<br />
To get this working under 2.6.15 with x.org 6.9, you will also need to apply a small patch - there is a link on the main article page. After you install the fglrx-driver package with the 6.9 versioning hack above, go to<br />
/usr/src/modules<br />
and copy the patch here. Modify the first two lines of the patch file to take out the "build_mod" directory, e.g. first line should begin with<br />
--- fglrx.orig/firegl_public.c <br />
and call it with the -p0 strip option. It should patch the firegl_public.c file cleanly. You can then install as usual for your kernel (2.6.14.x or 2.6.15) using module-assistant.<br />
<br />
Update - although X will come up in kernel 2.6.15 with the fglrx drivers patched as above, there is some strange behavior exhibited in all of X apllications - frequent hanging of applications when closing windows. Reverting back to the radeon driver in 2.6.15 solves these - so it is likely the ATI proprietary driver causing some problems.<br />
<br />
Yet another update - fglrx 8.21.7 is out as of 1/19/2006, now supporting OpenGL 2.0, so eventually we will have beautiful complex shading / fog effects on Linux, too. It works well with X.Org 6.9 out of the box.<br />
<br />
Unfortunately, this version gives the same problems when used (unpatched) with kernel 2.6.15 with strange lockups occasionally requiring reset of X. I have not tried this with the ~10 line patch listed on the main site, but that patch not work for me with 8.20.8. Anybody else have experience with 2.6.15 and fglrx?<br />
<br />
--[[User:gsmenden|gsmenden]] 12:39, 20 Jan 2006 (EST)<br />
----<br />
<br />
I don't know which patch you mean exactly (10 lines? the patch from lkml is just one line changed, no?), but I've been using 8.20.8 with 2.6.15 for quite some time (actually started with some -rc version IIRC), no lockups at all. No idea about 8.21.7 though, because I switched to 2.6.16-rc1 and can't compile the fglrx module at the moment, need to investigate the cause.<br />
<br />
--[[User:Spiney|spiney]] 07:24, 21 January 2006 (CET)<br />
----<br />
<br />
Ok - strange. Yeah, the actual change is only one line, the rest is just commenting, etc. The lockups that I get are quite rare, but flightgear occasionally gives a hard lock. glxgears and fgl_glxgears work fine, netscape occasionally will hard-lock, and strangely enough issuing a shutdown command often makes the display blank and hard lock. I can't reproduce them too consistently, but these _never_ occur with the radeon driver / mesa or under 2.6.14.x.<br />
<br />
Unfortunately vanilla 8.21.7 with kernel 2.6.15.1 (Xorg 6.9) gives the same X lockups.<br />
<br />
--[[User:gsmenden|gsmenden]] 11:36, 21 Jan 2006 (EST)<br />
----<br />
<br />
I can't compile the 8.21.7 driver modules with 2.6.15.1 at all. They compile with 2.6.14.4 cleanly and 8.20.8 compile with 2.6.15.1. <br />
What I don't understand though is, that when I let the ATI installer build debian packages, it does so without hassle, but the packages don't work. <br />
(this is about 8.21.7 - 2.6.15.1) Also patching doesn't seem to help. It shouldn't of course.<br />
<br />
--[[User:Rasto|Rasto]] 15:04, 23 Jan 2006 (CET)<br />
<br />
I looked at the compile problems last night. I have no idea, how it is possible that it works for other people with 2.6.15, perhaps when you install <br />
precompiled modules? I don't really understand how that ati-installer thing works. Anyway. This may solve the problems with 8.21.7 and 2.6.15- <br />
it is just two minor line changes (+ the one line patch with little extra), but now it compiles. pm_register and similar were moved to linux/pm_legacy.h <br />
in 2.6.15, so that's one problem. It also reports unknown symbol verify_area, but this should not pose a problem, as it is already obsolete and redundant. <br />
If you feel, that the one line should be left as the separate patch, copy it somewhere else and change it. It's here [http://people.ksp.sk/~rasto/fglrx_with_2.6.15.patch], but I'll put it on the main page as well.<br />
<br />
--[[User:Rasto|Rasto]] 18:29, 25 Jan 2006 (CET)<br />
<br />
== Disabling the external VGA port? ==<br />
<br />
Does anyone know how disable the VGA port ''completely'' even when a cable is attached? Fiddling around with the DesktopSetup and ForceMonitor options didn't do the trick for me, and the MonitorLayout option found in some documentation is no longer valid in the current fglrx driver.<br />
<br />
--[[User:Spiney|spiney]] 19:42, 10 Jan 2006 (CET)<br />
----<br />
<br />
== Debian-specific script to switch fglrx<->radeon ==<br />
<br />
Don't know where to put it exactly, but if someone's interested (and using Debian), I've put up a [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_graphics_card_switching_fglrx_radeon script for easily switching graphics driver configurations]. Feedback appreciated (altho I haven't got any to the xscreensaver patch ;)), especially if someone could do something similar for other distributions (Gentoo being half-way there it seems) and incorporate it into the script.<br />
<br />
--[[User:Spiney|spiney]] 15:25, 17 January 2006 (CET)<br />
----<br />
<br />
----<br />
==Compile ATI driver???==<br />
How can you compile a binary only distributed driver? If I'm not getting something wrong, please change the formulation of the just added info.<br />
<br />
[[User:Wyrfel|Wyrfel]] 20:10, 25 January 2006 (CET)</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Problems_with_fglrx&diff=18951Talk:Problems with fglrx2006-01-25T19:19:20Z<p>Rasto: /* 8.20.8 and later works with current Debian sid packages */</p>
<hr />
<div>== using kernel AGP vs fglrx AGP ==<br />
<br />
Anyone know whether this makes a performance and/or stability difference?<br />
<br />
== 8.20.8 and later works with current Debian sid packages ==<br />
<br />
<pre><br />
spiney@t43p:~$ dpkg -l xserver-xorg<br />
Desired=Unknown/Install/Remove/Purge/Hold<br />
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed<br />
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)<br />
||/ Name Version Description<br />
+++-============================-============================-==================<br />
ii xserver-xorg 6.9.0.dfsg.1-2 the X.Org X server<br />
spiney@t43p:~$ fglrxinfo <br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: MOBILITY FireGL V3200 Pentium 4 (SSE2) (FireGL) (GNU_ICD)<br />
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)<br />
</pre><br />
<br />
--[[User:Spiney|spiney]]<br />
----<br />
<br />
Ahh - thanks for the info. You perhaps compiled the modules for the drivers yourself and did not use the debian packaged fglrx-driver? Thus, it must be an unneeded limitation on the debian packaged driver which limits its installation... Full listing at http://packages.debian.org/unstable/x11/fglrx-driver which lists as required packages:<br />
<br />
xserver-xorg (<< 6.8.99)<br />
the X.Org X server <br />
xserver-xorg (>= 6.8.0) <br />
<br />
The first limitation (<<6.8.99) is what prevents installation. I'm sure I could force apt to install it, but I may go back to compiling the modules myself, as using fglrx 8.20.8 with kernel 2.6.15 needs a small patch to compile correctly anyway... --[[User:gsmenden|gsmenden]]<br />
<br />
Spiney, where exactly do you have your package from? I re-build the 8.20.8-package from debian with the <<6.8.99 dependecy removed, but when I try to run X, I get <br />
[R200Setup] X version mismatch - detected X.org 7.0.0.0, required X.org 6.8.0.0<br />
(EE) Failed to load module "fglrx" (module requirement mismatch, 0)<br />
Any hints? --[User:nomeata|nomeata]<br />
<br />
I used the ati-installer (the huge download), created a Debian sid package and installed it, but got the same error. The installer seems to fetch the wrong driver version from the archive, so I extracted it with<br />
<br />
{{cmd|./ati-driver-installer-8.20.8-i386.run --extract <sometempdir>|}}<br />
<br />
and put the necessary files from the created {{path|<sometempdir>/x690}} subdirectory into {{path|/usr}} by hand. All IIRC, it's been some time since. :)<br />
<br />
--[[User:Spiney|spiney]] 07:29, 11 Jan 2006 (CET)<br />
<br />
Thanks for the pointer. This is how you get proper debian packages out of the ati-installer:<br />
./ati-driver-installer-8.20.8-i386.run --extract fglrx-tmp<br />
cd fglrx-tmp<br />
$editor packages/Debian/ati-packager.sh # in the line "sid|unstable) X_DIR=x680;;", put a x690 for the x680<br />
./fglrx-tmp/packages/Debian/ati-packager.sh --buildpkg sid<br />
cd ..<br />
sudo dpkg -i fglrx-kernel-src_8.20.8-1_i386.deb fglrx-driver_8.20.8-1_i386.deb<br />
--[[User:Nomeata|Nomeata]] 00:35, 13 Jan 2006 (CET)<br />
<br />
<br />
----<br />
<br />
Nice - confirmed works on my T43p running sid. From then on (or until 8.21.x comes out) you'll have to tell apt to hold back fglrx-driver package, or it will try to "update" fglrx-driver to 8.20.8-1.1 and therefore revert back to the problematic drivers.<br />
--[[User:gsmenden|gsmenden]]<br />
----<br />
<br />
Thanks for the info, Nomeata, that's a lot cleaner a solution than my manual way.<br />
<br />
--[[User:Spiney|spiney]] 08:32, 13 Jan 2006 (CET)<br />
----<br />
<br />
To get this working under 2.6.15 with x.org 6.9, you will also need to apply a small patch - there is a link on the main article page. After you install the fglrx-driver package with the 6.9 versioning hack above, go to<br />
/usr/src/modules<br />
and copy the patch here. Modify the first two lines of the patch file to take out the "build_mod" directory, e.g. first line should begin with<br />
--- fglrx.orig/firegl_public.c <br />
and call it with the -p0 strip option. It should patch the firegl_public.c file cleanly. You can then install as usual for your kernel (2.6.14.x or 2.6.15) using module-assistant.<br />
<br />
Update - although X will come up in kernel 2.6.15 with the fglrx drivers patched as above, there is some strange behavior exhibited in all of X apllications - frequent hanging of applications when closing windows. Reverting back to the radeon driver in 2.6.15 solves these - so it is likely the ATI proprietary driver causing some problems.<br />
<br />
Yet another update - fglrx 8.21.7 is out as of 1/19/2006, now supporting OpenGL 2.0, so eventually we will have beautiful complex shading / fog effects on Linux, too. It works well with X.Org 6.9 out of the box.<br />
<br />
Unfortunately, this version gives the same problems when used (unpatched) with kernel 2.6.15 with strange lockups occasionally requiring reset of X. I have not tried this with the ~10 line patch listed on the main site, but that patch not work for me with 8.20.8. Anybody else have experience with 2.6.15 and fglrx?<br />
<br />
--[[User:gsmenden|gsmenden]] 12:39, 20 Jan 2006 (EST)<br />
----<br />
<br />
I don't know which patch you mean exactly (10 lines? the patch from lkml is just one line changed, no?), but I've been using 8.20.8 with 2.6.15 for quite some time (actually started with some -rc version IIRC), no lockups at all. No idea about 8.21.7 though, because I switched to 2.6.16-rc1 and can't compile the fglrx module at the moment, need to investigate the cause.<br />
<br />
--[[User:Spiney|spiney]] 07:24, 21 January 2006 (CET)<br />
----<br />
<br />
Ok - strange. Yeah, the actual change is only one line, the rest is just commenting, etc. The lockups that I get are quite rare, but flightgear occasionally gives a hard lock. glxgears and fgl_glxgears work fine, netscape occasionally will hard-lock, and strangely enough issuing a shutdown command often makes the display blank and hard lock. I can't reproduce them too consistently, but these _never_ occur with the radeon driver / mesa or under 2.6.14.x.<br />
<br />
Unfortunately vanilla 8.21.7 with kernel 2.6.15.1 (Xorg 6.9) gives the same X lockups.<br />
<br />
--[[User:gsmenden|gsmenden]] 11:36, 21 Jan 2006 (EST)<br />
----<br />
<br />
I can't compile the 8.21.7 driver modules with 2.6.15.1 at all. They compile with 2.6.14.4 cleanly and 8.20.8 compile with 2.6.15.1. <br />
What I don't understand though is, that when I let the ATI installer build debian packages, it does so without hassle, but the packages don't work. <br />
(this is about 8.21.7 - 2.6.15.1) Also patching doesn't seem to help. It shouldn't of course.<br />
<br />
--[[User:Rasto|Rasto]] 15:04, 23 Jan 2006 (CET)<br />
<br />
I looked at the compile problems last night. I have no idea, how it is possible that it works for other people with 2.6.15, perhaps when you install <br />
precompiled modules? I don't really understand how that ati-installer thing works. Anyway. This may solve the problems with 8.21.7 and 2.6.15- <br />
it is just two minor line changes (+ the one line patch with little extra), but now it compiles. pm_register and similar were moved to linux/pm_legacy.h <br />
in 2.6.15, so that's one problem. It also reports unknown symbol verify_area, but this should not pose a problem, as it is already obsolete and redundant. <br />
If you feel, that the one line should be left as the separate patch, copy it somewhere else and change it. It's here [http://people.ksp.sk/~rasto/fglrx_with_2.6.15.patch], but I'll put it on the main page as well.<br />
<br />
--[[User:Rasto|Rasto]] 18:29, 25 Jan 2006 (CET)<br />
<br />
== Disabling the external VGA port? ==<br />
<br />
Does anyone know how disable the VGA port ''completely'' even when a cable is attached? Fiddling around with the DesktopSetup and ForceMonitor options didn't do the trick for me, and the MonitorLayout option found in some documentation is no longer valid in the current fglrx driver.<br />
<br />
--[[User:Spiney|spiney]] 19:42, 10 Jan 2006 (CET)<br />
----<br />
<br />
== Debian-specific script to switch fglrx<->radeon ==<br />
<br />
Don't know where to put it exactly, but if someone's interested (and using Debian), I've put up a [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_graphics_card_switching_fglrx_radeon script for easily switching graphics driver configurations]. Feedback appreciated (altho I haven't got any to the xscreensaver patch ;)), especially if someone could do something similar for other distributions (Gentoo being half-way there it seems) and incorporate it into the script.<br />
<br />
--[[User:Spiney|spiney]] 15:25, 17 January 2006 (CET)<br />
----<br />
<br />
----<br />
==Compile ATI driver???==<br />
How can you compile a binary only distributed driver? If I'm not getting something wrong, please change the formulation of the just added info.<br />
<br />
[[User:Wyrfel|Wyrfel]] 20:10, 25 January 2006 (CET)<br />
----<br />
<br />
Driver modules? Sorry about that. <br />
[[User:Rasto|Rasto]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Problems_with_fglrx&diff=18950Problems with fglrx2006-01-25T19:17:36Z<p>Rasto: /* Kernel-specific troubles */</p>
<hr />
<div>This page discusses issues with the ATI proprietary [[fglrx]] display driver.<br />
<br />
== Known Troubles and Solutions ==<br />
<br />
=== X-specific issues ===<br />
<br />
The current ATI proprietary driver (8.21.7) works with x.org 6.9.<br />
<br />
If you are running an older version (8.20.8) under Debian sid and you upgrade your xserver-xorg, apt will force you to remove any debian-packaged fglrx drivers (package fglrx-driver depends on x.org << 6.8.99). You can just download the driver from the ATI site and install after modifying the Debian packager script to allow dependencies to be satisfied by x.org 6.9, or just download 8.21.7 and install manually. See talk page for step-by-step commands.<br />
<br />
After installing the fglrx driver, you can use module-assist to build the appropriate kernel module.<br />
<br />
=== Kernel-specific troubles ===<br />
<br />
Using the current ATI driver (8.21.7) with 2.6.15 or later needs a [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]. (see table below for detail.) If you can't compile the driver modules with 2.6.15 or later, you should apply this [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch patch] instead. <br />
<br />
If you do not use one of these patches, you may experience peculiar lockups of X. Try {{cmduser|fglrxinfo}} - if your shell hangs at the end of this command, you may have an issue and should try the patch.<br />
<br />
Although unproven, there is a substantial amount of user / developer concern that the above patches prevent hard lockups but do not provide full reliability with 2.6.15 and there are larger / redisgn issues preventing compatibility. It seems surprising that ATI would not have implemented such a simple page count fix in their latest two driver releases since kernel 2.6.15 has been available. Given the closed-source nature of the driver, it is difficult to know for sure. As of now only 2.6.14.x kernels are officially supported by the fglrx driver.<br />
<br />
=== No hardware acceleration ===<br />
If the ATI driver works only without the hardware acceleration, take into consideration that {{path|fglrx_dri.so}} was linked against libstdc++.so.5 which may not be present if your system uses gcc-3.4.<br />
<br />
To fix this, compile gcc-3.3.5 and copy <tt>libstdc++.so.5*</tt> to {{path|/usr/lib}} and update the dynamic linker cache via {{cmdroot|ldconfig}}.<br />
<br />
Another possible cause for broken hardware acceleration (2D and 3D) is the radeonfb framebuffer: Switching to vesafb or vesafb-tng is reported to solve the problem on some systems. Also it has proven helpful to not perform {{cmdroot|modprobe fglrx}} after boot but to have the module loaded via {{path|/etc/modules.autoload/kernel2.x}} at boottime instead.<br />
<br />
=== Softlink hell ===<br />
The [[fglrx]] installer replaces the standard X.org OpenGL implementation (Mesa) with its own files, potentially causing collisions with the distribution's file and package management. It is best to install the driver via a package built for your distribution, which will typically include the necessary kludges to make things work. See the [[fglrx]] page for pointers.<br />
<br />
====Discussion====<br />
If using {{cmduser|fglrxinfo}} after installing [[fglrx]] indicates that you are still using the mesa indirect software GL renderer, you likely have some misplaced softlinks. It seems like it has to do with an apt-get upgrade that sometimes replaces these links. Anyway, go to<br />
:{{cmdroot|cd /usr/X11R6/lib}}<br />
and list your GL libraries and links<br />
:{{cmdroot|ls -la *GL*}}<br />
You should see something like the following two lines amoung others:<br />
:{{cmdresult|libGL.so -> libGL.so.1.2}}<br />
:{{cmdresult|libGL.so.1 -> libGL.so.1.2}}<br />
If you see a link to a mesa library (something like {{cmdresult|... -> libGL.mesa.1.2}}), then that's your problem! Restore the softlink like this (use your actual library version, though):<br />
:{{cmdroot|ln -s libGL.so.1.2 libGL.so.1}}<br />
<br />
For some reason, this link might "break" later, giving you the software rendering once more. Even after renaming the mesa library to something like <tt>mesa.bkup</tt>, the system might still find it and link to it despite the name change. If you have to do this a lot, you could write a restoreGL script.<br />
<br />
=====Gentoo=====<br />
{{Gentoo}} has built in tools for managing the OpenGL symlinks. They seem to be replacing the old tool with a new one, so one of the following should work for you:<br />
:{{cmdroot|opengl-update ati}} or<br />
:{{cmdroot|eselect opengl set ati}}<br />
Eselect is new, and still ~x86 (as of the end of 2005), so you may not have it yet. <tt>opengl-update</tt> is the old tried-and-true method for managing the symlinks. If <tt>opengl-update</tt> doesn't fix it for you, you should probably tell [http://bugs.gentoo.org Gentoo Bugzilla] (assuming they don't know yet).<br />
<br />
If {{cmdroot|ldd /usr/X11R6/bin/glxinfo}} shows that your system still uses the xorg-x11 mesa libs after trying one of the above commands, i.e. a line like this:<br />
:{{cmdresult|1=libGL.so.1 => /usr/lib/opengl/xorg-x11/lib/libGL.so.1 (0x400a8000)}}<br />
you will also need to relink {{path|libGl.so.1.2}}:<br />
:{{cmdroot|cd /usr/lib/opengl/xorg-x11/lib/}}<br />
:{{cmdroot|mv libGL.so.1.2 libGL.so.1.2_backup}}<br />
:{{cmdroot|ln -s /usr/lib/libGL.so.1.2 libGL.so.1.2}}<br />
After another restart of X {{cmduser|fglrxinfo}} should show that it's using the right libs now.<br />
<br />
=== Troubles using software suspend ===<br />
When the computer resumes from suspend, X only displays a garbled image and the computer is frozen.<br />
The problem is acknowledged in ATI's release notes and in knowledge base entry [https://support.ati.com/ics/support/KBResult.asp?searchFor=Search+Words&search.x=0&search.y=0&searchOption=id&questionID=737-218+&task=knowledge&searchTime=-1&productID=&folderID=-1&resultLimit=50 737-218]. Driver version 8.19.10 has "initial support for Suspend and Resume" but is working very nicely for most people (verified on T43, T43p and T42) without vbetool.<br />
<br />
If you are using an older version of fglrx, using [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] to save/restore the video card state before/after suspend worked for some people. If you use [[Software Suspend 2|Software Suspend 2 (suspend2)]] scripts, you can simply uncomment <tt>EnableVbetool yes</tt> in {{path|/etc/hibernate/hibernate.conf}}. Be aware though that it breaks suspend/resume for drivers beginning with version 8.19.10, so remember to disable it again when upgrading.<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|+ tested with the following configurations<br />
!model!!distro||kernel!!fglrx!!PM!!success!!comments<br />
|-<br />
|{{T42}}||SUSE 9.3||2.6.11||8.14.13||swsusp||yes||<br />
|-<br />
|{{T41p}}||???||2.6.14||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch]<br />
|-<br />
|{{T42p}}||Debian||2.6.10||Debian packaged||suspend2||yes||<br />
|-<br />
|{{T43}}||Debian sid||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 (but not earlier versions!)<br />
|-<br />
|{{T43}}||Debian etch||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 and without vbetool<br />
|-<br />
|{{T43}}||Ubuntu Breezy||2.6.12-10||8.19.10||swsusp||yes||Perfect. (Finally.)<br />
|-<br />
|{{T43}}||FC4||2.6.14.1||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch], requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)<br />
|-<br />
|{{T43}}||FC4||2.6.14.2||8.19.10||suspend2 2.2-rc11||yes||requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)<br />
|-<br />
|{{T43}}||FC4||2.6.14.3||8.19.10||suspend2 2.2-rc13||no||DRI enabled<br />
|-<br />
|{{T43}}||FC4||2.6.14.3||8.20.8||suspend2 2.2-rc13||no||DRI enabled<br />
|-<br />
|{{R50p}}||???||???||8.19.10||swsusp||yes||<br />
|-<br />
|{{T43p}}||Debian sid||2.6.14||8.19.10||Suspend to RAM||yes||without vbetool or UseDummyXServer, those two ''break'' the resume process here, with DRI enabled<br />
|-<br />
|{{T43p}}||Debian sid||2.6.14.3||8.20.8||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled<br />
|-<br />
|{{R52}}||Debian sid||2.6.15-rc5||8.20.8||swsup||yes||both vbetool and UseDummyXServer disabled, DRI enabled, needs [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]<br />
|}<br />
<br />
=== Troubles with large RAM ===<br />
Version 8.14.13 (and probably earlier versions) of the driver 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 <tt>fglrx</tt> kernel module is loaded, but independently of whether {{kernelconf|CONFIG_HIGHMEM||||||}} is enabled. A workaround is to limit RAM by adding the {{bootparm|mem|864m}} kernel parameter.<br />
<br />
Version 8.16.20 fixes the problem.<br />
<br />
===Display switching ===<br />
The switching between internal and external display doesn't work, because the driver blocks messing around with the chipset via ACPI. If you want to use this feature (i.e. during presentations), you should use the <tt>vesa</tt> server instead (experienced with a R52, Kernel 2.6.11, xorg 6.8.2, fglrx 8.16.20).<br />
<br />
===Composite Support===<br />
ATI has not officially supported composite windowing (alpha channel) enabling hardware acclerated translucent windows (primarily for 'eye candy.') Enabling Composite in KDE and the fglrx driver results in a very pretty desktop but unacceptably slow performance on a T43p with ATI's FireGL T2. It is still unusable in its current state (as of driver 8.19.10).<br />
<br />
ATI promises support in the future when composite is officially supported by Xorg. Discussion of current status of drivers can be found in the Rage3d forums' (rage3d.com/board) Linux area.<br />
<br />
There were some rumors that composite support was fast with the open-source 2d accelerated drivers in x.org 6.9 (as opposed to 6.8.x). Alas, trying this gives better results than the proprietary drivers, but it is still too slow to be reasonably useful.<br />
<br />
===Hardlock on X logout===<br />
Up from driver version 8.19.10 you will expierence a system hard lock when logging out from X, if the session manager (kdm/gdm) is not properly configured. You have to tell the session manager to restart X.<br />
<br />
In the kdm config file (gentoo: {{path|/usr/kde/<VERSION>/share/config/kdm/kdmrc}}) you have to add following to the section <code>[X-:*-Core]</code>: <br />
TerminateServer=true<br />
<br />
In the gdm config file add:<br />
AlwaysRestartServer=true<br />
<br />
Information from the ATI bugtracker: http://ati.cchtml.com/show_bug.cgi?id=239<br />
<br />
== Patches ==<br />
The following patches might be needed for certain versions of fglrx.<br />
<br />
===fglrx 8.20.8===<br />
<br />
* [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 for kernel 2.6.15]<br />
<br />
===fglrx (problem met at least with version 8.18.8)===<br />
* [http://lkml.org/lkml/2005/9/22/183 for kernel >= 2.6.13 ] Missing verify_area bug<br />
<br />
===fglrx 8.8.25 ===<br />
* [http://www.rage3d.com/board/showthread.php?t=33798874 for kernels >= 2.6.10]<br />
* [http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch For kernels >= 2.6.11-rc1]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Problems_with_fglrx&diff=18949Talk:Problems with fglrx2006-01-25T19:16:58Z<p>Rasto: /* Compile ATI driver??? */</p>
<hr />
<div>== using kernel AGP vs fglrx AGP ==<br />
<br />
Anyone know whether this makes a performance and/or stability difference?<br />
<br />
== 8.20.8 and later works with current Debian sid packages ==<br />
<br />
<pre><br />
spiney@t43p:~$ dpkg -l xserver-xorg<br />
Desired=Unknown/Install/Remove/Purge/Hold<br />
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed<br />
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)<br />
||/ Name Version Description<br />
+++-============================-============================-==================<br />
ii xserver-xorg 6.9.0.dfsg.1-2 the X.Org X server<br />
spiney@t43p:~$ fglrxinfo <br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: MOBILITY FireGL V3200 Pentium 4 (SSE2) (FireGL) (GNU_ICD)<br />
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)<br />
</pre><br />
<br />
--[[User:Spiney|spiney]]<br />
----<br />
<br />
Ahh - thanks for the info. You perhaps compiled the modules for the drivers yourself and did not use the debian packaged fglrx-driver? Thus, it must be an unneeded limitation on the debian packaged driver which limits its installation... Full listing at http://packages.debian.org/unstable/x11/fglrx-driver which lists as required packages:<br />
<br />
xserver-xorg (<< 6.8.99)<br />
the X.Org X server <br />
xserver-xorg (>= 6.8.0) <br />
<br />
The first limitation (<<6.8.99) is what prevents installation. I'm sure I could force apt to install it, but I may go back to compiling the modules myself, as using fglrx 8.20.8 with kernel 2.6.15 needs a small patch to compile correctly anyway... --[[User:gsmenden|gsmenden]]<br />
<br />
Spiney, where exactly do you have your package from? I re-build the 8.20.8-package from debian with the <<6.8.99 dependecy removed, but when I try to run X, I get <br />
[R200Setup] X version mismatch - detected X.org 7.0.0.0, required X.org 6.8.0.0<br />
(EE) Failed to load module "fglrx" (module requirement mismatch, 0)<br />
Any hints? --[User:nomeata|nomeata]<br />
<br />
I used the ati-installer (the huge download), created a Debian sid package and installed it, but got the same error. The installer seems to fetch the wrong driver version from the archive, so I extracted it with<br />
<br />
{{cmd|./ati-driver-installer-8.20.8-i386.run --extract <sometempdir>|}}<br />
<br />
and put the necessary files from the created {{path|<sometempdir>/x690}} subdirectory into {{path|/usr}} by hand. All IIRC, it's been some time since. :)<br />
<br />
--[[User:Spiney|spiney]] 07:29, 11 Jan 2006 (CET)<br />
<br />
Thanks for the pointer. This is how you get proper debian packages out of the ati-installer:<br />
./ati-driver-installer-8.20.8-i386.run --extract fglrx-tmp<br />
cd fglrx-tmp<br />
$editor packages/Debian/ati-packager.sh # in the line "sid|unstable) X_DIR=x680;;", put a x690 for the x680<br />
./fglrx-tmp/packages/Debian/ati-packager.sh --buildpkg sid<br />
cd ..<br />
sudo dpkg -i fglrx-kernel-src_8.20.8-1_i386.deb fglrx-driver_8.20.8-1_i386.deb<br />
--[[User:Nomeata|Nomeata]] 00:35, 13 Jan 2006 (CET)<br />
<br />
<br />
----<br />
<br />
Nice - confirmed works on my T43p running sid. From then on (or until 8.21.x comes out) you'll have to tell apt to hold back fglrx-driver package, or it will try to "update" fglrx-driver to 8.20.8-1.1 and therefore revert back to the problematic drivers.<br />
--[[User:gsmenden|gsmenden]]<br />
----<br />
<br />
Thanks for the info, Nomeata, that's a lot cleaner a solution than my manual way.<br />
<br />
--[[User:Spiney|spiney]] 08:32, 13 Jan 2006 (CET)<br />
----<br />
<br />
To get this working under 2.6.15 with x.org 6.9, you will also need to apply a small patch - there is a link on the main article page. After you install the fglrx-driver package with the 6.9 versioning hack above, go to<br />
/usr/src/modules<br />
and copy the patch here. Modify the first two lines of the patch file to take out the "build_mod" directory, e.g. first line should begin with<br />
--- fglrx.orig/firegl_public.c <br />
and call it with the -p0 strip option. It should patch the firegl_public.c file cleanly. You can then install as usual for your kernel (2.6.14.x or 2.6.15) using module-assistant.<br />
<br />
Update - although X will come up in kernel 2.6.15 with the fglrx drivers patched as above, there is some strange behavior exhibited in all of X apllications - frequent hanging of applications when closing windows. Reverting back to the radeon driver in 2.6.15 solves these - so it is likely the ATI proprietary driver causing some problems.<br />
<br />
Yet another update - fglrx 8.21.7 is out as of 1/19/2006, now supporting OpenGL 2.0, so eventually we will have beautiful complex shading / fog effects on Linux, too. It works well with X.Org 6.9 out of the box.<br />
<br />
Unfortunately, this version gives the same problems when used (unpatched) with kernel 2.6.15 with strange lockups occasionally requiring reset of X. I have not tried this with the ~10 line patch listed on the main site, but that patch not work for me with 8.20.8. Anybody else have experience with 2.6.15 and fglrx?<br />
<br />
--[[User:gsmenden|gsmenden]] 12:39, 20 Jan 2006 (EST)<br />
----<br />
<br />
I don't know which patch you mean exactly (10 lines? the patch from lkml is just one line changed, no?), but I've been using 8.20.8 with 2.6.15 for quite some time (actually started with some -rc version IIRC), no lockups at all. No idea about 8.21.7 though, because I switched to 2.6.16-rc1 and can't compile the fglrx module at the moment, need to investigate the cause.<br />
<br />
--[[User:Spiney|spiney]] 07:24, 21 January 2006 (CET)<br />
----<br />
<br />
Ok - strange. Yeah, the actual change is only one line, the rest is just commenting, etc. The lockups that I get are quite rare, but flightgear occasionally gives a hard lock. glxgears and fgl_glxgears work fine, netscape occasionally will hard-lock, and strangely enough issuing a shutdown command often makes the display blank and hard lock. I can't reproduce them too consistently, but these _never_ occur with the radeon driver / mesa or under 2.6.14.x.<br />
<br />
Unfortunately vanilla 8.21.7 with kernel 2.6.15.1 (Xorg 6.9) gives the same X lockups.<br />
<br />
--[[User:gsmenden|gsmenden]] 11:36, 21 Jan 2006 (EST)<br />
----<br />
<br />
I can't compile the 8.21.7 drivers with 2.6.15.1 at all. They compile with 2.6.14.4 cleanly and 8.20.8 compile with 2.6.15.1. <br />
What I don't understand though is, that when I let the ATI installer build debian packages, it does so without hassle, but the packages don't work. <br />
(this is about 8.21.7 - 2.6.15.1) Also patching doesn't seem to help. It shouldn't of course.<br />
<br />
--[[User:Rasto|Rasto]] 15:04, 23 Jan 2006 (CET)<br />
<br />
I looked at the compile problems last night. I have no idea, how it is possible that it works for other people with 2.6.15, perhaps when you install <br />
precompiled modules? I don't really understand how that ati-installer thing works. Anyway. This may solve the problems with 8.21.7 and 2.6.15- <br />
it is just two minor line changes (+ the one line patch with little extra), but now it compiles. pm_register and similar were moved to linux/pm_legacy.h <br />
in 2.6.15, so that's one problem. It also reports unknown symbol verify_area, but this should not pose a problem, as it is already obsolete and redundant. <br />
If you feel, that the one line should be left as the separate patch, copy it somewhere else and change it. It's here [http://people.ksp.sk/~rasto/fglrx_with_2.6.15.patch], but I'll put it on the main page as well.<br />
<br />
--[[User:Rasto|Rasto]] 18:29, 25 Jan 2006 (CET)<br />
<br />
== Disabling the external VGA port? ==<br />
<br />
Does anyone know how disable the VGA port ''completely'' even when a cable is attached? Fiddling around with the DesktopSetup and ForceMonitor options didn't do the trick for me, and the MonitorLayout option found in some documentation is no longer valid in the current fglrx driver.<br />
<br />
--[[User:Spiney|spiney]] 19:42, 10 Jan 2006 (CET)<br />
----<br />
<br />
== Debian-specific script to switch fglrx<->radeon ==<br />
<br />
Don't know where to put it exactly, but if someone's interested (and using Debian), I've put up a [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_graphics_card_switching_fglrx_radeon script for easily switching graphics driver configurations]. Feedback appreciated (altho I haven't got any to the xscreensaver patch ;)), especially if someone could do something similar for other distributions (Gentoo being half-way there it seems) and incorporate it into the script.<br />
<br />
--[[User:Spiney|spiney]] 15:25, 17 January 2006 (CET)<br />
----<br />
<br />
----<br />
==Compile ATI driver???==<br />
How can you compile a binary only distributed driver? If I'm not getting something wrong, please change the formulation of the just added info.<br />
<br />
[[User:Wyrfel|Wyrfel]] 20:10, 25 January 2006 (CET)<br />
----<br />
<br />
Driver modules? Sorry about that. <br />
[[User:Rasto|Rasto]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Problems_with_fglrx&diff=18942Problems with fglrx2006-01-25T17:46:08Z<p>Rasto: /* Kernel-specific troubles */</p>
<hr />
<div>This page discusses issues with the ATI proprietary [[fglrx]] display driver.<br />
<br />
== Known Troubles and Solutions ==<br />
<br />
=== X-specific issues ===<br />
<br />
The current ATI proprietary driver (8.21.7) works with x.org 6.9.<br />
<br />
If you are running an older version (8.20.8) under Debian sid and you upgrade your xserver-xorg, apt will force you to remove any debian-packaged fglrx drivers (package fglrx-driver depends on x.org << 6.8.99). You can just download the driver from the ATI site and install after modifying the Debian packager script to allow dependencies to be satisfied by x.org 6.9, or just download 8.21.7 and install manually. See talk page for step-by-step commands.<br />
<br />
After installing the fglrx driver, you can use module-assist to build the appropriate kernel module.<br />
<br />
=== Kernel-specific troubles ===<br />
<br />
Using the current ATI driver (8.21.7) with 2.6.15 or later needs a [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]. (see table below for detail.) If you can't compile the driver with 2.6.15 or later, you should apply this [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch patch] instead. <br />
<br />
If you do not use one of these patches, you may experience peculiar lockups of X. Try {{cmduser|fglrxinfo}} - if your shell hangs at the end of this command, you may have an issue and should try the patch.<br />
<br />
Although unproven, there is a substantial amount of user / developer concern that the above patches prevent hard lockups but do not provide full reliability with 2.6.15 and there are larger / redisgn issues preventing compatibility. It seems surprising that ATI would not have implemented such a simple page count fix in their latest two driver releases since kernel 2.6.15 has been available. Given the closed-source nature of the driver, it is difficult to know for sure. As of now only 2.6.14.x kernels are officially supported by the fglrx driver.<br />
<br />
=== No hardware acceleration ===<br />
If the ATI driver works only without the hardware acceleration, take into consideration that {{path|fglrx_dri.so}} was linked against libstdc++.so.5 which may not be present if your system uses gcc-3.4.<br />
<br />
To fix this, compile gcc-3.3.5 and copy <tt>libstdc++.so.5*</tt> to {{path|/usr/lib}} and update the dynamic linker cache via {{cmdroot|ldconfig}}.<br />
<br />
Another possible cause for broken hardware acceleration (2D and 3D) is the radeonfb framebuffer: Switching to vesafb or vesafb-tng is reported to solve the problem on some systems. Also it has proven helpful to not perform {{cmdroot|modprobe fglrx}} after boot but to have the module loaded via {{path|/etc/modules.autoload/kernel2.x}} at boottime instead.<br />
<br />
=== Softlink hell ===<br />
The [[fglrx]] installer replaces the standard X.org OpenGL implementation (Mesa) with its own files, potentially causing collisions with the distribution's file and package management. It is best to install the driver via a package built for your distribution, which will typically include the necessary kludges to make things work. See the [[fglrx]] page for pointers.<br />
<br />
====Discussion====<br />
If using {{cmduser|fglrxinfo}} after installing [[fglrx]] indicates that you are still using the mesa indirect software GL renderer, you likely have some misplaced softlinks. It seems like it has to do with an apt-get upgrade that sometimes replaces these links. Anyway, go to<br />
:{{cmdroot|cd /usr/X11R6/lib}}<br />
and list your GL libraries and links<br />
:{{cmdroot|ls -la *GL*}}<br />
You should see something like the following two lines amoung others:<br />
:{{cmdresult|libGL.so -> libGL.so.1.2}}<br />
:{{cmdresult|libGL.so.1 -> libGL.so.1.2}}<br />
If you see a link to a mesa library (something like {{cmdresult|... -> libGL.mesa.1.2}}), then that's your problem! Restore the softlink like this (use your actual library version, though):<br />
:{{cmdroot|ln -s libGL.so.1.2 libGL.so.1}}<br />
<br />
For some reason, this link might "break" later, giving you the software rendering once more. Even after renaming the mesa library to something like <tt>mesa.bkup</tt>, the system might still find it and link to it despite the name change. If you have to do this a lot, you could write a restoreGL script.<br />
<br />
=====Gentoo=====<br />
{{Gentoo}} has built in tools for managing the OpenGL symlinks. They seem to be replacing the old tool with a new one, so one of the following should work for you:<br />
:{{cmdroot|opengl-update ati}} or<br />
:{{cmdroot|eselect opengl set ati}}<br />
Eselect is new, and still ~x86 (as of the end of 2005), so you may not have it yet. <tt>opengl-update</tt> is the old tried-and-true method for managing the symlinks. If <tt>opengl-update</tt> doesn't fix it for you, you should probably tell [http://bugs.gentoo.org Gentoo Bugzilla] (assuming they don't know yet).<br />
<br />
If {{cmdroot|ldd /usr/X11R6/bin/glxinfo}} shows that your system still uses the xorg-x11 mesa libs after trying one of the above commands, i.e. a line like this:<br />
:{{cmdresult|1=libGL.so.1 => /usr/lib/opengl/xorg-x11/lib/libGL.so.1 (0x400a8000)}}<br />
you will also need to relink {{path|libGl.so.1.2}}:<br />
:{{cmdroot|cd /usr/lib/opengl/xorg-x11/lib/}}<br />
:{{cmdroot|mv libGL.so.1.2 libGL.so.1.2_backup}}<br />
:{{cmdroot|ln -s /usr/lib/libGL.so.1.2 libGL.so.1.2}}<br />
After another restart of X {{cmduser|fglrxinfo}} should show that it's using the right libs now.<br />
<br />
=== Troubles using software suspend ===<br />
When the computer resumes from suspend, X only displays a garbled image and the computer is frozen.<br />
The problem is acknowledged in ATI's release notes and in knowledge base entry [https://support.ati.com/ics/support/KBResult.asp?searchFor=Search+Words&search.x=0&search.y=0&searchOption=id&questionID=737-218+&task=knowledge&searchTime=-1&productID=&folderID=-1&resultLimit=50 737-218]. Driver version 8.19.10 has "initial support for Suspend and Resume" but is working very nicely for most people (verified on T43, T43p and T42) without vbetool.<br />
<br />
If you are using an older version of fglrx, using [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] to save/restore the video card state before/after suspend worked for some people. If you use [[Software Suspend 2|Software Suspend 2 (suspend2)]] scripts, you can simply uncomment <tt>EnableVbetool yes</tt> in {{path|/etc/hibernate/hibernate.conf}}. Be aware though that it breaks suspend/resume for drivers beginning with version 8.19.10, so remember to disable it again when upgrading.<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|+ tested with the following configurations<br />
!model!!distro||kernel!!fglrx!!PM!!success!!comments<br />
|-<br />
|{{T42}}||SUSE 9.3||2.6.11||8.14.13||swsusp||yes||<br />
|-<br />
|{{T41p}}||???||2.6.14||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch]<br />
|-<br />
|{{T42p}}||Debian||2.6.10||Debian packaged||suspend2||yes||<br />
|-<br />
|{{T43}}||Debian sid||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 (but not earlier versions!)<br />
|-<br />
|{{T43}}||Debian etch||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 and without vbetool<br />
|-<br />
|{{T43}}||Ubuntu Breezy||2.6.12-10||8.19.10||swsusp||yes||Perfect. (Finally.)<br />
|-<br />
|{{T43}}||FC4||2.6.14.1||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch], requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)<br />
|-<br />
|{{T43}}||FC4||2.6.14.2||8.19.10||suspend2 2.2-rc11||yes||requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)<br />
|-<br />
|{{T43}}||FC4||2.6.14.3||8.19.10||suspend2 2.2-rc13||no||DRI enabled<br />
|-<br />
|{{T43}}||FC4||2.6.14.3||8.20.8||suspend2 2.2-rc13||no||DRI enabled<br />
|-<br />
|{{R50p}}||???||???||8.19.10||swsusp||yes||<br />
|-<br />
|{{T43p}}||Debian sid||2.6.14||8.19.10||Suspend to RAM||yes||without vbetool or UseDummyXServer, those two ''break'' the resume process here, with DRI enabled<br />
|-<br />
|{{T43p}}||Debian sid||2.6.14.3||8.20.8||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled<br />
|-<br />
|{{R52}}||Debian sid||2.6.15-rc5||8.20.8||swsup||yes||both vbetool and UseDummyXServer disabled, DRI enabled, needs [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]<br />
|}<br />
<br />
=== Troubles with large RAM ===<br />
Version 8.14.13 (and probably earlier versions) of the driver 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 <tt>fglrx</tt> kernel module is loaded, but independently of whether {{kernelconf|CONFIG_HIGHMEM||||||}} is enabled. A workaround is to limit RAM by adding the {{bootparm|mem|864m}} kernel parameter.<br />
<br />
Version 8.16.20 fixes the problem.<br />
<br />
===Display switching ===<br />
The switching between internal and external display doesn't work, because the driver blocks messing around with the chipset via ACPI. If you want to use this feature (i.e. during presentations), you should use the <tt>vesa</tt> server instead (experienced with a R52, Kernel 2.6.11, xorg 6.8.2, fglrx 8.16.20).<br />
<br />
===Composite Support===<br />
ATI has not officially supported composite windowing (alpha channel) enabling hardware acclerated translucent windows (primarily for 'eye candy.') Enabling Composite in KDE and the fglrx driver results in a very pretty desktop but unacceptably slow performance on a T43p with ATI's FireGL T2. It is still unusable in its current state (as of driver 8.19.10).<br />
<br />
ATI promises support in the future when composite is officially supported by Xorg. Discussion of current status of drivers can be found in the Rage3d forums' (rage3d.com/board) Linux area.<br />
<br />
There were some rumors that composite support was fast with the open-source 2d accelerated drivers in x.org 6.9 (as opposed to 6.8.x). Alas, trying this gives better results than the proprietary drivers, but it is still too slow to be reasonably useful.<br />
<br />
===Hardlock on X logout===<br />
Up from driver version 8.19.10 you will expierence a system hard lock when logging out from X, if the session manager (kdm/gdm) is not properly configured. You have to tell the session manager to restart X.<br />
<br />
In the kdm config file (gentoo: {{path|/usr/kde/<VERSION>/share/config/kdm/kdmrc}}) you have to add following to the section <code>[X-:*-Core]</code>: <br />
TerminateServer=true<br />
<br />
In the gdm config file add:<br />
AlwaysRestartServer=true<br />
<br />
Information from the ATI bugtracker: http://ati.cchtml.com/show_bug.cgi?id=239<br />
<br />
== Patches ==<br />
The following patches might be needed for certain versions of fglrx.<br />
<br />
===fglrx 8.20.8===<br />
<br />
* [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 for kernel 2.6.15]<br />
<br />
===fglrx (problem met at least with version 8.18.8)===<br />
* [http://lkml.org/lkml/2005/9/22/183 for kernel >= 2.6.13 ] Missing verify_area bug<br />
<br />
===fglrx 8.8.25 ===<br />
* [http://www.rage3d.com/board/showthread.php?t=33798874 for kernels >= 2.6.10]<br />
* [http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch For kernels >= 2.6.11-rc1]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Problems_with_fglrx&diff=18941Talk:Problems with fglrx2006-01-25T17:41:17Z<p>Rasto: /* 8.20.8 and later works with current Debian sid packages */</p>
<hr />
<div>== using kernel AGP vs fglrx AGP ==<br />
<br />
Anyone know whether this makes a performance and/or stability difference?<br />
<br />
== 8.20.8 and later works with current Debian sid packages ==<br />
<br />
<pre><br />
spiney@t43p:~$ dpkg -l xserver-xorg<br />
Desired=Unknown/Install/Remove/Purge/Hold<br />
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed<br />
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)<br />
||/ Name Version Description<br />
+++-============================-============================-==================<br />
ii xserver-xorg 6.9.0.dfsg.1-2 the X.Org X server<br />
spiney@t43p:~$ fglrxinfo <br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: MOBILITY FireGL V3200 Pentium 4 (SSE2) (FireGL) (GNU_ICD)<br />
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)<br />
</pre><br />
<br />
--[[User:Spiney|spiney]]<br />
----<br />
<br />
Ahh - thanks for the info. You perhaps compiled the modules for the drivers yourself and did not use the debian packaged fglrx-driver? Thus, it must be an unneeded limitation on the debian packaged driver which limits its installation... Full listing at http://packages.debian.org/unstable/x11/fglrx-driver which lists as required packages:<br />
<br />
xserver-xorg (<< 6.8.99)<br />
the X.Org X server <br />
xserver-xorg (>= 6.8.0) <br />
<br />
The first limitation (<<6.8.99) is what prevents installation. I'm sure I could force apt to install it, but I may go back to compiling the modules myself, as using fglrx 8.20.8 with kernel 2.6.15 needs a small patch to compile correctly anyway... --[[User:gsmenden|gsmenden]]<br />
<br />
Spiney, where exactly do you have your package from? I re-build the 8.20.8-package from debian with the <<6.8.99 dependecy removed, but when I try to run X, I get <br />
[R200Setup] X version mismatch - detected X.org 7.0.0.0, required X.org 6.8.0.0<br />
(EE) Failed to load module "fglrx" (module requirement mismatch, 0)<br />
Any hints? --[User:nomeata|nomeata]<br />
<br />
I used the ati-installer (the huge download), created a Debian sid package and installed it, but got the same error. The installer seems to fetch the wrong driver version from the archive, so I extracted it with<br />
<br />
{{cmd|./ati-driver-installer-8.20.8-i386.run --extract <sometempdir>|}}<br />
<br />
and put the necessary files from the created {{path|<sometempdir>/x690}} subdirectory into {{path|/usr}} by hand. All IIRC, it's been some time since. :)<br />
<br />
--[[User:Spiney|spiney]] 07:29, 11 Jan 2006 (CET)<br />
<br />
Thanks for the pointer. This is how you get proper debian packages out of the ati-installer:<br />
./ati-driver-installer-8.20.8-i386.run --extract fglrx-tmp<br />
cd fglrx-tmp<br />
$editor packages/Debian/ati-packager.sh # in the line "sid|unstable) X_DIR=x680;;", put a x690 for the x680<br />
./fglrx-tmp/packages/Debian/ati-packager.sh --buildpkg sid<br />
cd ..<br />
sudo dpkg -i fglrx-kernel-src_8.20.8-1_i386.deb fglrx-driver_8.20.8-1_i386.deb<br />
--[[User:Nomeata|Nomeata]] 00:35, 13 Jan 2006 (CET)<br />
<br />
<br />
----<br />
<br />
Nice - confirmed works on my T43p running sid. From then on (or until 8.21.x comes out) you'll have to tell apt to hold back fglrx-driver package, or it will try to "update" fglrx-driver to 8.20.8-1.1 and therefore revert back to the problematic drivers.<br />
--[[User:gsmenden|gsmenden]]<br />
----<br />
<br />
Thanks for the info, Nomeata, that's a lot cleaner a solution than my manual way.<br />
<br />
--[[User:Spiney|spiney]] 08:32, 13 Jan 2006 (CET)<br />
----<br />
<br />
To get this working under 2.6.15 with x.org 6.9, you will also need to apply a small patch - there is a link on the main article page. After you install the fglrx-driver package with the 6.9 versioning hack above, go to<br />
/usr/src/modules<br />
and copy the patch here. Modify the first two lines of the patch file to take out the "build_mod" directory, e.g. first line should begin with<br />
--- fglrx.orig/firegl_public.c <br />
and call it with the -p0 strip option. It should patch the firegl_public.c file cleanly. You can then install as usual for your kernel (2.6.14.x or 2.6.15) using module-assistant.<br />
<br />
Update - although X will come up in kernel 2.6.15 with the fglrx drivers patched as above, there is some strange behavior exhibited in all of X apllications - frequent hanging of applications when closing windows. Reverting back to the radeon driver in 2.6.15 solves these - so it is likely the ATI proprietary driver causing some problems.<br />
<br />
Yet another update - fglrx 8.21.7 is out as of 1/19/2006, now supporting OpenGL 2.0, so eventually we will have beautiful complex shading / fog effects on Linux, too. It works well with X.Org 6.9 out of the box.<br />
<br />
Unfortunately, this version gives the same problems when used (unpatched) with kernel 2.6.15 with strange lockups occasionally requiring reset of X. I have not tried this with the ~10 line patch listed on the main site, but that patch not work for me with 8.20.8. Anybody else have experience with 2.6.15 and fglrx?<br />
<br />
--[[User:gsmenden|gsmenden]] 12:39, 20 Jan 2006 (EST)<br />
----<br />
<br />
I don't know which patch you mean exactly (10 lines? the patch from lkml is just one line changed, no?), but I've been using 8.20.8 with 2.6.15 for quite some time (actually started with some -rc version IIRC), no lockups at all. No idea about 8.21.7 though, because I switched to 2.6.16-rc1 and can't compile the fglrx module at the moment, need to investigate the cause.<br />
<br />
--[[User:Spiney|spiney]] 07:24, 21 January 2006 (CET)<br />
----<br />
<br />
Ok - strange. Yeah, the actual change is only one line, the rest is just commenting, etc. The lockups that I get are quite rare, but flightgear occasionally gives a hard lock. glxgears and fgl_glxgears work fine, netscape occasionally will hard-lock, and strangely enough issuing a shutdown command often makes the display blank and hard lock. I can't reproduce them too consistently, but these _never_ occur with the radeon driver / mesa or under 2.6.14.x.<br />
<br />
Unfortunately vanilla 8.21.7 with kernel 2.6.15.1 (Xorg 6.9) gives the same X lockups.<br />
<br />
--[[User:gsmenden|gsmenden]] 11:36, 21 Jan 2006 (EST)<br />
----<br />
<br />
I can't compile the 8.21.7 drivers with 2.6.15.1 at all. They compile with 2.6.14.4 cleanly and 8.20.8 compile with 2.6.15.1. <br />
What I don't understand though is, that when I let the ATI installer build debian packages, it does so without hassle, but the packages don't work. <br />
(this is about 8.21.7 - 2.6.15.1) Also patching doesn't seem to help. It shouldn't of course.<br />
<br />
--[[User:Rasto|Rasto]] 15:04, 23 Jan 2006 (CET)<br />
<br />
I looked at the compile problems last night. I have no idea, how it is possible that it works for other people with 2.6.15, perhaps when you install <br />
precompiled modules? I don't really understand how that ati-installer thing works. Anyway. This may solve the problems with 8.21.7 and 2.6.15- <br />
it is just two minor line changes (+ the one line patch with little extra), but now it compiles. pm_register and similar were moved to linux/pm_legacy.h <br />
in 2.6.15, so that's one problem. It also reports unknown symbol verify_area, but this should not pose a problem, as it is already obsolete and redundant. <br />
If you feel, that the one line should be left as the separate patch, copy it somewhere else and change it. It's here [http://people.ksp.sk/~rasto/fglrx_with_2.6.15.patch], but I'll put it on the main page as well.<br />
<br />
--[[User:Rasto|Rasto]] 18:29, 25 Jan 2006 (CET)<br />
<br />
== Disabling the external VGA port? ==<br />
<br />
Does anyone know how disable the VGA port ''completely'' even when a cable is attached? Fiddling around with the DesktopSetup and ForceMonitor options didn't do the trick for me, and the MonitorLayout option found in some documentation is no longer valid in the current fglrx driver.<br />
<br />
--[[User:Spiney|spiney]] 19:42, 10 Jan 2006 (CET)<br />
----<br />
<br />
== Debian-specific script to switch fglrx<->radeon ==<br />
<br />
Don't know where to put it exactly, but if someone's interested (and using Debian), I've put up a [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_graphics_card_switching_fglrx_radeon script for easily switching graphics driver configurations]. Feedback appreciated (altho I haven't got any to the xscreensaver patch ;)), especially if someone could do something similar for other distributions (Gentoo being half-way there it seems) and incorporate it into the script.<br />
<br />
--[[User:Spiney|spiney]] 15:25, 17 January 2006 (CET)<br />
----</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Problems_with_fglrx&diff=18940Talk:Problems with fglrx2006-01-25T17:40:26Z<p>Rasto: /* 8.20.8 and later works with current Debian sid packages */</p>
<hr />
<div>== using kernel AGP vs fglrx AGP ==<br />
<br />
Anyone know whether this makes a performance and/or stability difference?<br />
<br />
== 8.20.8 and later works with current Debian sid packages ==<br />
<br />
<pre><br />
spiney@t43p:~$ dpkg -l xserver-xorg<br />
Desired=Unknown/Install/Remove/Purge/Hold<br />
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed<br />
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)<br />
||/ Name Version Description<br />
+++-============================-============================-==================<br />
ii xserver-xorg 6.9.0.dfsg.1-2 the X.Org X server<br />
spiney@t43p:~$ fglrxinfo <br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: MOBILITY FireGL V3200 Pentium 4 (SSE2) (FireGL) (GNU_ICD)<br />
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)<br />
</pre><br />
<br />
--[[User:Spiney|spiney]]<br />
----<br />
<br />
Ahh - thanks for the info. You perhaps compiled the modules for the drivers yourself and did not use the debian packaged fglrx-driver? Thus, it must be an unneeded limitation on the debian packaged driver which limits its installation... Full listing at http://packages.debian.org/unstable/x11/fglrx-driver which lists as required packages:<br />
<br />
xserver-xorg (<< 6.8.99)<br />
the X.Org X server <br />
xserver-xorg (>= 6.8.0) <br />
<br />
The first limitation (<<6.8.99) is what prevents installation. I'm sure I could force apt to install it, but I may go back to compiling the modules myself, as using fglrx 8.20.8 with kernel 2.6.15 needs a small patch to compile correctly anyway... --[[User:gsmenden|gsmenden]]<br />
<br />
Spiney, where exactly do you have your package from? I re-build the 8.20.8-package from debian with the <<6.8.99 dependecy removed, but when I try to run X, I get <br />
[R200Setup] X version mismatch - detected X.org 7.0.0.0, required X.org 6.8.0.0<br />
(EE) Failed to load module "fglrx" (module requirement mismatch, 0)<br />
Any hints? --[User:nomeata|nomeata]<br />
<br />
I used the ati-installer (the huge download), created a Debian sid package and installed it, but got the same error. The installer seems to fetch the wrong driver version from the archive, so I extracted it with<br />
<br />
{{cmd|./ati-driver-installer-8.20.8-i386.run --extract <sometempdir>|}}<br />
<br />
and put the necessary files from the created {{path|<sometempdir>/x690}} subdirectory into {{path|/usr}} by hand. All IIRC, it's been some time since. :)<br />
<br />
--[[User:Spiney|spiney]] 07:29, 11 Jan 2006 (CET)<br />
<br />
Thanks for the pointer. This is how you get proper debian packages out of the ati-installer:<br />
./ati-driver-installer-8.20.8-i386.run --extract fglrx-tmp<br />
cd fglrx-tmp<br />
$editor packages/Debian/ati-packager.sh # in the line "sid|unstable) X_DIR=x680;;", put a x690 for the x680<br />
./fglrx-tmp/packages/Debian/ati-packager.sh --buildpkg sid<br />
cd ..<br />
sudo dpkg -i fglrx-kernel-src_8.20.8-1_i386.deb fglrx-driver_8.20.8-1_i386.deb<br />
--[[User:Nomeata|Nomeata]] 00:35, 13 Jan 2006 (CET)<br />
<br />
<br />
----<br />
<br />
Nice - confirmed works on my T43p running sid. From then on (or until 8.21.x comes out) you'll have to tell apt to hold back fglrx-driver package, or it will try to "update" fglrx-driver to 8.20.8-1.1 and therefore revert back to the problematic drivers.<br />
--[[User:gsmenden|gsmenden]]<br />
----<br />
<br />
Thanks for the info, Nomeata, that's a lot cleaner a solution than my manual way.<br />
<br />
--[[User:Spiney|spiney]] 08:32, 13 Jan 2006 (CET)<br />
----<br />
<br />
To get this working under 2.6.15 with x.org 6.9, you will also need to apply a small patch - there is a link on the main article page. After you install the fglrx-driver package with the 6.9 versioning hack above, go to<br />
/usr/src/modules<br />
and copy the patch here. Modify the first two lines of the patch file to take out the "build_mod" directory, e.g. first line should begin with<br />
--- fglrx.orig/firegl_public.c <br />
and call it with the -p0 strip option. It should patch the firegl_public.c file cleanly. You can then install as usual for your kernel (2.6.14.x or 2.6.15) using module-assistant.<br />
<br />
Update - although X will come up in kernel 2.6.15 with the fglrx drivers patched as above, there is some strange behavior exhibited in all of X apllications - frequent hanging of applications when closing windows. Reverting back to the radeon driver in 2.6.15 solves these - so it is likely the ATI proprietary driver causing some problems.<br />
<br />
Yet another update - fglrx 8.21.7 is out as of 1/19/2006, now supporting OpenGL 2.0, so eventually we will have beautiful complex shading / fog effects on Linux, too. It works well with X.Org 6.9 out of the box.<br />
<br />
Unfortunately, this version gives the same problems when used (unpatched) with kernel 2.6.15 with strange lockups occasionally requiring reset of X. I have not tried this with the ~10 line patch listed on the main site, but that patch not work for me with 8.20.8. Anybody else have experience with 2.6.15 and fglrx?<br />
<br />
--[[User:gsmenden|gsmenden]] 12:39, 20 Jan 2006 (EST)<br />
----<br />
<br />
I don't know which patch you mean exactly (10 lines? the patch from lkml is just one line changed, no?), but I've been using 8.20.8 with 2.6.15 for quite some time (actually started with some -rc version IIRC), no lockups at all. No idea about 8.21.7 though, because I switched to 2.6.16-rc1 and can't compile the fglrx module at the moment, need to investigate the cause.<br />
<br />
--[[User:Spiney|spiney]] 07:24, 21 January 2006 (CET)<br />
----<br />
<br />
Ok - strange. Yeah, the actual change is only one line, the rest is just commenting, etc. The lockups that I get are quite rare, but flightgear occasionally gives a hard lock. glxgears and fgl_glxgears work fine, netscape occasionally will hard-lock, and strangely enough issuing a shutdown command often makes the display blank and hard lock. I can't reproduce them too consistently, but these _never_ occur with the radeon driver / mesa or under 2.6.14.x.<br />
<br />
Unfortunately vanilla 8.21.7 with kernel 2.6.15.1 (Xorg 6.9) gives the same X lockups.<br />
<br />
--[[User:gsmenden|gsmenden]] 11:36, 21 Jan 2006 (EST)<br />
----<br />
<br />
I can't compile the 8.21.7 drivers with 2.6.15.1 at all. They compile with 2.6.14.4 cleanly and 8.20.8 compile with 2.6.15.1. <br />
What I don't understand though is, that when I let the ATI installer build debian packages, it does so without hassle, but the packages don't work. <br />
(this is about 8.21.7 - 2.6.15.1) Also patching doesn't seem to help. It shouldn't of course.<br />
<br />
--[[User:Rasto|Rasto]] 15:04, 23 Jan 2006 (CET)<br />
<br />
I looked at the compile problems last night. I have no idea, how it is possible that it workes for other people with 2.6.15, perhaps when you install <br />
precompiled modules? I dont't really understand how that ati-installer thing works. Anyway. This may solve the problems with 8.21.7 and 2.6.15- <br />
it is just two minor line changes (+ the one line patch with little extra), but now it compiles. pm_register and similar were moved to linux/pm_legacy.h <br />
in 2.6.15, so that's one problem. It also reports unknown symbol verify_area, but this should not pose a problem, as it is already obsolete and redundant. <br />
If you feel, that the one line should be left as the separate patch, copy it somewhere else and change it. It's here [http://people.ksp.sk/~rasto/fglrx_with_2.6.15.patch], but I'll put it on the main page as well.<br />
<br />
--[[User:Rasto|Rasto]] 18:29, 25 Jan 2006 (CET)<br />
<br />
== Disabling the external VGA port? ==<br />
<br />
Does anyone know how disable the VGA port ''completely'' even when a cable is attached? Fiddling around with the DesktopSetup and ForceMonitor options didn't do the trick for me, and the MonitorLayout option found in some documentation is no longer valid in the current fglrx driver.<br />
<br />
--[[User:Spiney|spiney]] 19:42, 10 Jan 2006 (CET)<br />
----<br />
<br />
== Debian-specific script to switch fglrx<->radeon ==<br />
<br />
Don't know where to put it exactly, but if someone's interested (and using Debian), I've put up a [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_graphics_card_switching_fglrx_radeon script for easily switching graphics driver configurations]. Feedback appreciated (altho I haven't got any to the xscreensaver patch ;)), especially if someone could do something similar for other distributions (Gentoo being half-way there it seems) and incorporate it into the script.<br />
<br />
--[[User:Spiney|spiney]] 15:25, 17 January 2006 (CET)<br />
----</div>Rastohttps://www.thinkwiki.org/w/index.php?title=User:Rasto&diff=18900User:Rasto2006-01-24T13:51:01Z<p>Rasto: </p>
<hr />
<div>I own a [[:Category:T43|T43]] 2686-E6U (Contrary to what is in tabook, it has a 14" SXGA+ display and no fingerprint reader), <br />
running [[:Category:Debian|Debian]] unstable. I also take care of one [[:Category:600E|600E]] running almost identical software.</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Installation_instructions_for_the_ThinkPad_600E&diff=18899Talk:Installation instructions for the ThinkPad 600E2006-01-24T13:30:56Z<p>Rasto: </p>
<hr />
<div>I'm not so sure about the ACPI. From my experience, ACPI (as of 2.6.14.4) doesn't work with 600E very well. <br />
There seems to be a problem with interrupts, meaning I can't get pcmcia cards to work. And this is a constant <br />
issue, across many different kernels and two different debian installations. <br />
<br />
-- [[Rasto]]</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Problems_with_SATA_and_Linux&diff=18889Talk:Problems with SATA and Linux2006-01-24T10:44:12Z<p>Rasto: </p>
<hr />
<div>I'm running gentoo on my T43; I had problems with X11 (opensource radeon driver) and a SATA-patched kernel (I tried both 2.6.14 and 2.6.15-gentoo). Suspend to RAM worked nicely, but starting X freezed the machine after a short time. I tried removing radeonfb from the kernel; with vesafb, everything seems to work.<br />
<br />
-- Stefan, 10 Jan 2006<br />
<br />
--------<br />
That's strange - with the libata passthrough (IDE driver not in kernel) as set up in the text, my t43p DVD drive also will not record as hinted in the wikipage... DMA works fine, so DVD playing / ripping is smooth and quick. CD record functions also are absent. I have PATA enabled, and the suspend + SMART patches applied over 2.6.14.2.<br />
--------<br />
I can confirm this with 2.6.14.4, however with 2.6.15/15.1 with sata_pm patch it works.<br />
<br />
-- Rasto, 24 Jan 2006<br />
<br />
--------<br />
regarding the "BIOS error 2010 on user-installed hard disk":<br />
the text says that corruption occurs if you use a harddisk without the specific ibm bios. would be interesting if it is possible to fix this problem in the kernel so that you can use any disk and the kernel doesn't use specific ATA commands which are known to cause problems.<br />
<br />
in the tabook i didn't find any specification of the SATA bridge. it would be interesting:<br />
1) what type it is<br />
2) if it is fixed on the mainboard or if it is possible to solder in a new one<br />
<br />
----<br />
<br />
Another interesting question is whether these ThinkPads can be hacked to accept a real SATA system disk, by bypassing the SATA-to-PATA bridge (this would probably involve some soldering and cutting). If the BIOS can also handle that then it may come in handy, since some new high-capacity 2.5" disks have only SATA versions.<br />
--[[User:Thinker|Thinker]] 02:56, 8 Oct 2005 (CEST)<br />
<br />
----<br />
<br />
'''Z series'''<br />
<br />
Since the Z series uses a SATA controller and disk, without the bridge, would it be possible to make SATA ATAPI support as a module that you could load only when using the optical drive? Then, for everyday use, the experimental options of PATA and ATAPI with ata_piix would not be needed, moving you one step further in the direction of stability.<br />
<br />
----<br />
<br />
I have an R52 with Ubuntu Breezy and no problems with SATA (I personally asked the developers to include the needed patches).<br />
<br />
However, I'd like to know wheter there are any advantages with this configuration. Future proof? Power saving? Speed?<br />
<br />
Anybody cares to comment?<br />
<br />
-- [[User:Micampe|Michele]]<br />
<br />
Straight SATA, like in the Z60m/t, will provide better upgrade options in the long run (the hard disk industry is slowly but surely moving to SATA), and maybe a small performance increase if your drive, controller and OS support command queueing (they probably don't). However, with the hybrid ThinkPad models that use a SATA-to-PATA bridge, like your R52, you get all the drawbacks and none of the benefits; plus there's the horrible issue with [[Problem with non-ThinkPad hard disks|drive compatibility]]. My impression is that Lenovo did this just as a convenient (for them!) transition path, in order to use new chipsets without comitting to (temporarily) scarcer and more expensive drives. In any case, they didn't even have the decency to make the UltraBay Slim accept SATA drives. <br />
<br />
--[[User:Thinker|Thinker]] 18:10, 3 Nov 2005 (CET)<br />
----<br />
There is a [[UltraBay Slim SATA HDD Adapter]], but only compatible with the Z series (at least for the moment).<br />
<br />
--[[User:Tonko|Tonko]] 03:12, 4 Nov 2005 (CET)<br />
<br />
== updated libata_passthru.patch ==<br />
<br />
FYI: when using the Suspend-to-RAM patch from http://lkml.org/lkml/2005/9/23/97 against 2.6.14 the libata_passthru.patch from the article doesn't apply any more, so I've put up an updated version at http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch<br />
<br />
I give no warranties whatsoever whether it works or kills your hardware, but since I just removed duplicate parts already in the Suspend-to-RAM patch it should be ok.<br />
<br />
--[[User:spiney|spiney]] 19:04, 4 Nov 2005 (CET)<br />
<br />
== ATA_ENABLE_PATA PCI IDs ==<br />
<br />
Spiney, could you extend the article to explain what and why are the PCI IDs in the footnote about ATA_ENABLE_PATA?<br />
<br />
--[[User:Thinker|Thinker]] 21:59, 4 Nov 2005 (CET)<br />
----<br />
<br />
Ok, done, feel free to fix the table because I'm a bit struggling with Wiki-style editing. ;) As for the why, those PCI IDs are the only ones affected by the ATA_ENABLE_PATA, as seen in {{path|drivers/scsi/ata_piix.c}} in the kernel source.<br />
<br />
--[[User:spiney|spiney]] 11:19, 5 Nov 2005 (CET)<br />
----<br />
<br />
Will other cards work without ATA_ENABLE_PATA, or just fail? In the former case your instructions are right, but in the latter case we should tell the user to check the list of IDs in his ''current'' kernel and, if there's no match, to give up in the first place instead of following the rest of the instructions.<br />
<br />
--[[User:Thinker|Thinker]] 12:48, 5 Nov 2005 (CET)<br />
----<br />
<br />
AFAICT if the chipset is supported by libata it will work, regardless of what low-level driver is used. Of course if there is no low-level driver for the chipset then even using the harddisk via libata will fail, but that's a different story. At least ATA_ENABLE_PATA will then make no difference since it's Intel PIIX (and compatible) only.<br />
<br />
--[[User:spiney|spiney]] 13:24, 5 Nov 2005 (CET)<br />
----<br />
<br />
Not sure I got you. Is there any case where the instructions will work without ATA_ENABLE_PATA, given that all ThinkPad optical drives are PATA?<br />
<br />
--[[User:Thinker|Thinker]] 13:41, 5 Nov 2005 (CET)<br />
----<br />
<br />
The instructions will work without ATA_ENABLE_PATA unless the Thinkpad uses one of the three chipsets listed in the article, as long as libata works at all, i.e. the system drive shows up as /dev/sda. The #define doesn't change the behaviour of libata for any other chipset, it's [http://linux.yyz.us/sata/sata-status.html#ich5 ata_piix] only.<br />
<br />
Since I don't have a machine with one of the three chipsets (anyone?), I can't tell whether those work at all with libata, but I guess there's a reason why they're not enabled by default. It's just that defining ATA_ENABLE_PATA is only making sense for these three chipsets.<br />
<br />
Any clearer now? If not, just run {{cmd|grep -r ATA_ENABLE_PATA /path/to/kernelsource|}} and see how seldom and where the #define is used.<br />
<br />
--[[User:spiney|spiney]] 14:55, 5 Nov 2005 (CET)<br />
----<br />
<br />
All clear now. I thought it will work only if you have these chipsets ''and'' ATA_ENABLE_PATA=1. Thanks for the explanation!<br />
<br />
--[[User:Thinker|Thinker]] 15:12, 5 Nov 2005 (CET)<br />
----<br />
<br />
Does any of the relevant ThinkPad models (listed in the article) use these chips? They look too old to be found on the SATA models.<br />
<br />
--[[User:Thinker|Thinker]] 23:35, 9 Nov 2005 (CET)<br />
----<br />
<br />
I don't think so, I was about to add "in the unlikely event that you own one of these chipsets" or something.<br />
<br />
--[[User:Spiney|spiney]] 07:56, 10 Nov 2005 (CET)<br />
----<br />
<br />
== DVD DMA with ide/sata as module ==<br />
<br />
Did anyone get DVD DMA to work with either the IDE or SATA drivers compiled as modules? If so, please fill in the missing details in that section. I have it working only with both IDE and SATA built-in.<br />
<br />
--[[User:Thinker|Thinker]] 17:58, 16 Nov 2005 (CET)<br />
----<br />
<br />
Basically using a Live-CD with a recent kernel (is there one with 2.6.14 already?) would be sufficient, since they usually use an initrd or something similar, don't they? I'll give the Debian distribution kernel a try when I get around to it (bit busy atm), after all there's 2.6.14 in sid.<br />
<br />
But for people using their own kernel compiled from source I see no point in doing the module+initrd thing anyway, unless you want LVM for the root filesystem or other funky stuff.<br />
<br />
--[[User:Spiney|spiney]] 19:22, 16 Nov 2005 (CET)<br />
----<br />
<br />
Hi<br />
<br />
Can anyone tell me how those modules are called?<br />
<br />
Thomas<br />
--[[User:Thomas|thomas]] 19:48, 23 Jan 2006 (CET)<br />
----</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:Problems_with_SATA_and_Linux&diff=18888Talk:Problems with SATA and Linux2006-01-24T10:43:58Z<p>Rasto: </p>
<hr />
<div>I'm running gentoo on my T43; I had problems with X11 (opensource radeon driver) and a SATA-patched kernel (I tried both 2.6.14 and 2.6.15-gentoo). Suspend to RAM worked nicely, but starting X freezed the machine after a short time. I tried removing radeonfb from the kernel; with vesafb, everything seems to work.<br />
<br />
-- Stefan, 10 Jan 2006<br />
<br />
--------<br />
That's strange - with the libata passthrough (IDE driver not in kernel) as set up in the text, my t43p DVD drive also will not record as hinted in the wikipage... DMA works fine, so DVD playing / ripping is smooth and quick. CD record functions also are absent. I have PATA enabled, and the suspend + SMART patches applied over 2.6.14.2.<br />
--------<br />
I can confirm this with 2.6.14.4, however with 2.6.15/15.1 with sata_pm patch it works.<br />
u<br />
-- Rasto, 24 Jan 2006<br />
<br />
--------<br />
regarding the "BIOS error 2010 on user-installed hard disk":<br />
the text says that corruption occurs if you use a harddisk without the specific ibm bios. would be interesting if it is possible to fix this problem in the kernel so that you can use any disk and the kernel doesn't use specific ATA commands which are known to cause problems.<br />
<br />
in the tabook i didn't find any specification of the SATA bridge. it would be interesting:<br />
1) what type it is<br />
2) if it is fixed on the mainboard or if it is possible to solder in a new one<br />
<br />
----<br />
<br />
Another interesting question is whether these ThinkPads can be hacked to accept a real SATA system disk, by bypassing the SATA-to-PATA bridge (this would probably involve some soldering and cutting). If the BIOS can also handle that then it may come in handy, since some new high-capacity 2.5" disks have only SATA versions.<br />
--[[User:Thinker|Thinker]] 02:56, 8 Oct 2005 (CEST)<br />
<br />
----<br />
<br />
'''Z series'''<br />
<br />
Since the Z series uses a SATA controller and disk, without the bridge, would it be possible to make SATA ATAPI support as a module that you could load only when using the optical drive? Then, for everyday use, the experimental options of PATA and ATAPI with ata_piix would not be needed, moving you one step further in the direction of stability.<br />
<br />
----<br />
<br />
I have an R52 with Ubuntu Breezy and no problems with SATA (I personally asked the developers to include the needed patches).<br />
<br />
However, I'd like to know wheter there are any advantages with this configuration. Future proof? Power saving? Speed?<br />
<br />
Anybody cares to comment?<br />
<br />
-- [[User:Micampe|Michele]]<br />
<br />
Straight SATA, like in the Z60m/t, will provide better upgrade options in the long run (the hard disk industry is slowly but surely moving to SATA), and maybe a small performance increase if your drive, controller and OS support command queueing (they probably don't). However, with the hybrid ThinkPad models that use a SATA-to-PATA bridge, like your R52, you get all the drawbacks and none of the benefits; plus there's the horrible issue with [[Problem with non-ThinkPad hard disks|drive compatibility]]. My impression is that Lenovo did this just as a convenient (for them!) transition path, in order to use new chipsets without comitting to (temporarily) scarcer and more expensive drives. In any case, they didn't even have the decency to make the UltraBay Slim accept SATA drives. <br />
<br />
--[[User:Thinker|Thinker]] 18:10, 3 Nov 2005 (CET)<br />
----<br />
There is a [[UltraBay Slim SATA HDD Adapter]], but only compatible with the Z series (at least for the moment).<br />
<br />
--[[User:Tonko|Tonko]] 03:12, 4 Nov 2005 (CET)<br />
<br />
== updated libata_passthru.patch ==<br />
<br />
FYI: when using the Suspend-to-RAM patch from http://lkml.org/lkml/2005/9/23/97 against 2.6.14 the libata_passthru.patch from the article doesn't apply any more, so I've put up an updated version at http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch<br />
<br />
I give no warranties whatsoever whether it works or kills your hardware, but since I just removed duplicate parts already in the Suspend-to-RAM patch it should be ok.<br />
<br />
--[[User:spiney|spiney]] 19:04, 4 Nov 2005 (CET)<br />
<br />
== ATA_ENABLE_PATA PCI IDs ==<br />
<br />
Spiney, could you extend the article to explain what and why are the PCI IDs in the footnote about ATA_ENABLE_PATA?<br />
<br />
--[[User:Thinker|Thinker]] 21:59, 4 Nov 2005 (CET)<br />
----<br />
<br />
Ok, done, feel free to fix the table because I'm a bit struggling with Wiki-style editing. ;) As for the why, those PCI IDs are the only ones affected by the ATA_ENABLE_PATA, as seen in {{path|drivers/scsi/ata_piix.c}} in the kernel source.<br />
<br />
--[[User:spiney|spiney]] 11:19, 5 Nov 2005 (CET)<br />
----<br />
<br />
Will other cards work without ATA_ENABLE_PATA, or just fail? In the former case your instructions are right, but in the latter case we should tell the user to check the list of IDs in his ''current'' kernel and, if there's no match, to give up in the first place instead of following the rest of the instructions.<br />
<br />
--[[User:Thinker|Thinker]] 12:48, 5 Nov 2005 (CET)<br />
----<br />
<br />
AFAICT if the chipset is supported by libata it will work, regardless of what low-level driver is used. Of course if there is no low-level driver for the chipset then even using the harddisk via libata will fail, but that's a different story. At least ATA_ENABLE_PATA will then make no difference since it's Intel PIIX (and compatible) only.<br />
<br />
--[[User:spiney|spiney]] 13:24, 5 Nov 2005 (CET)<br />
----<br />
<br />
Not sure I got you. Is there any case where the instructions will work without ATA_ENABLE_PATA, given that all ThinkPad optical drives are PATA?<br />
<br />
--[[User:Thinker|Thinker]] 13:41, 5 Nov 2005 (CET)<br />
----<br />
<br />
The instructions will work without ATA_ENABLE_PATA unless the Thinkpad uses one of the three chipsets listed in the article, as long as libata works at all, i.e. the system drive shows up as /dev/sda. The #define doesn't change the behaviour of libata for any other chipset, it's [http://linux.yyz.us/sata/sata-status.html#ich5 ata_piix] only.<br />
<br />
Since I don't have a machine with one of the three chipsets (anyone?), I can't tell whether those work at all with libata, but I guess there's a reason why they're not enabled by default. It's just that defining ATA_ENABLE_PATA is only making sense for these three chipsets.<br />
<br />
Any clearer now? If not, just run {{cmd|grep -r ATA_ENABLE_PATA /path/to/kernelsource|}} and see how seldom and where the #define is used.<br />
<br />
--[[User:spiney|spiney]] 14:55, 5 Nov 2005 (CET)<br />
----<br />
<br />
All clear now. I thought it will work only if you have these chipsets ''and'' ATA_ENABLE_PATA=1. Thanks for the explanation!<br />
<br />
--[[User:Thinker|Thinker]] 15:12, 5 Nov 2005 (CET)<br />
----<br />
<br />
Does any of the relevant ThinkPad models (listed in the article) use these chips? They look too old to be found on the SATA models.<br />
<br />
--[[User:Thinker|Thinker]] 23:35, 9 Nov 2005 (CET)<br />
----<br />
<br />
I don't think so, I was about to add "in the unlikely event that you own one of these chipsets" or something.<br />
<br />
--[[User:Spiney|spiney]] 07:56, 10 Nov 2005 (CET)<br />
----<br />
<br />
== DVD DMA with ide/sata as module ==<br />
<br />
Did anyone get DVD DMA to work with either the IDE or SATA drivers compiled as modules? If so, please fill in the missing details in that section. I have it working only with both IDE and SATA built-in.<br />
<br />
--[[User:Thinker|Thinker]] 17:58, 16 Nov 2005 (CET)<br />
----<br />
<br />
Basically using a Live-CD with a recent kernel (is there one with 2.6.14 already?) would be sufficient, since they usually use an initrd or something similar, don't they? I'll give the Debian distribution kernel a try when I get around to it (bit busy atm), after all there's 2.6.14 in sid.<br />
<br />
But for people using their own kernel compiled from source I see no point in doing the module+initrd thing anyway, unless you want LVM for the root filesystem or other funky stuff.<br />
<br />
--[[User:Spiney|spiney]] 19:22, 16 Nov 2005 (CET)<br />
----<br />
<br />
Hi<br />
<br />
Can anyone tell me how those modules are called?<br />
<br />
Thomas<br />
--[[User:Thomas|thomas]] 19:48, 23 Jan 2006 (CET)<br />
----</div>Rastohttps://www.thinkwiki.org/w/index.php?title=Talk:IBM_11a/b/g_Wireless_LAN_Mini_PCI_Adapter_II&diff=18819Talk:IBM 11a/b/g Wireless LAN Mini PCI Adapter II2006-01-23T14:35:35Z<p>Rasto: /* Super A/G */</p>
<hr />
<div>Hi. Regarding this card (73P4301), it has been stated on [http://www-131.ibm.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=-840&storeId=10000001&langId=-1&dualCurrId=1000073&categoryId=2581910&productId=8770176 IBM/Lenovo's parts sales page] that it is indeed compatible with the Thinkpad X31 series (2672/73, 2884/85), so I would say that the X31 should be included in the last of machines that this card can be found in.<br />
<br />
----<br />
Depends on the point of view. Right now the list contains ThinkPad featuring the cards in their default configuration. If we would change it to a list of ThinkPads supporting the card, it would in fact be a loss of information, since virtuall any recent ThinkPad supports the card, which is true for many of the other cards as well. So there is less point in this information.<br />
<br />
What we could do, however, is to include a second list of ThinkPads supporting the card.<br />
<br />
[[User:Wyrfel|Wyrfel]] 13:20, 14 Aug 2005 (CEST)<br />
----<br />
<br />
== Super A/G ==<br />
Do SuperA/G modes work for anybody? I have MiniPCI atheros with T43, and a PCMCIA one. <br />
The PCMCIA doesn't seem to have problem with turbo, the MiniPCI one however does. Both are<br />
5004/5112 chipsets.<br />
<br />
This [http://www.atheros.com/pt/AR5004XBulletin.htm chipset] definately should support Super A and Super G modes.<br />
<br />
OK. I'm actively trying to find out more about this. Please, could you guys check, if turbo modes <br />
work for you, if you have Atheros? <br />
It is quite easy to tell, at driver load, madwifi display something like this,<br />
wifi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps<br />
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps<br />
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps<br />
if there are no turbo modes present. If there are turbo modes present, it also shows turbo rates, <br />
although only up to 54Mbps (they are actually double that). <br />
Also, it should be possible to change to turbo mode: <br />
:{{cmdroot|iwpriv ath0 mode 3}}<br />
:{{cmdroot|iwpriv ath0 turbo 1}}<br />
:{{cmdroot|iwpriv ath0 get_turbo}}<br />
:{{cmdresult|ath0 get_turbo:1}}<br />
<br />
----<br />
OK. It is probably so, that the card is actually crippled by Lenovo- or not set to use it's full potential. <br />
Why would this be, I have no idea. I'm trying to compare the EEPROM of this card with the one on a different <br />
atheros of the same chipset. Also, it is interesting that atheros claims, that all thinkpads (although T43/p is <br />
not there and except the Z60's ) that have a/b/g chipsets have the AR5001X+, not AR5004X. [http://customerproducts.atheros.com/customerproducts/] <br />
The chipset stated on this page should therefore be changed, or both should be mentioned.<br />
Also it might be a good idea to ask somebody at IBM about the turbo modes, if anyone except me cares. <br />
It is a bit problematic for me to do.<br />
--[[User:Rasto|Rasto]]</div>Rasto