ThinkWiki - User contributions [en]

Thermal Sensors

2009-07-27T07:55:50Z

Dummyaccount: /* ThinkPad {{T400}} */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page summarizes known information about the locations and properties of thermal sensors on ThinkPad laptops.
|}

==Accessing the sensors==

===Basic ACPI system temperature sensors===
The primary means of accessing the thermal sensors is through the [[thinkpad-acpi]] module, up to 16 sensors are supported. When the module is loaded, the sensors (some of which may be inactive) are shown through the standard sysfs hwmon interface used by the lm-sensors utilities, and also in {{path|/proc/acpi/ibm/thermal}} (which is deprecated, and will be removed someday).

lm-sensors/libsensors uses the hwmon interface exposed through {{path|/sys/bus/platform/devices/thinkpad_hwmon/}} to read the temperatures, note that the sysfs interface returns normal open errors instead of weird values for sensors that are not active (which the simplistic '''sensors''' command ignore). lm-sensors/libsensors can be configured to give proper names to each sensor, which will be used by any properly written sensor applet.

{{cmdroot|sensors}}
{{cmdresult|thinkpad-isa-0000
Adapter: ISA adapter
fan1: 3914 RPM
CPU: +45.0°C
LAN/Heatsink/HDAPS: +44.0°C
PC-CARD slot: +35.0°C
GPU: +48.0°C
Main battery charger: +35.0°C
ERROR: Can't get value of subfeature temp6_input: Can't read
Bay battery charger: +0.0°C
Main battery cells: +30.0°C
ERROR: Can't get value of subfeature temp8_input: Can't read
Bay battery cells: +0.0°C
MCH: +42.0°C
PLL clock/ICH/WLAN: +50.0°C
Voltage regulator: +43.0°C}}

The old method to access the thermal readings is through the {{path|/proc}} interface:

:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128}}

A value of -128 (i.e., 0x80 hex) means the sensor is not connected. For example, above the two -128 values belong to the UltraBay battery, which is not plugged in.

If the ThinkPad supports the extended sensor set, eight more values will be displayed:

:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128 48 50 49 -128 -128 -128 -128 -128}}

===HDAPS temperature sensor===
The [[Active Protection System]] firmware also reports a temperature, which is identical to one of the ACPI sensors. The corresponding sensor is actually not inside the HDAPS chip, and sometimes not even close to it.
:{{cmdroot|cat /sys/bus/platform/drivers/hdaps/hdaps/temp1}}
:{{cmdresult|41}}

===Harddisks SMART temperature sensor===
The system hard disk temperature can be read through the disk's SMART interface:
:{{cmdroot|<nowiki>smartctl -A /dev/hda | grep Temperature</nowiki>}}
:{{cmdresult|194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31}}

Or, for SATA-equipped models running a recent Linux kernel (see [[Problems with SATA and Linux]]):

:{{cmdroot|<nowiki>smartctl -A -d ata /dev/sda | grep Temperature</nowiki>}}
:{{cmdresult|194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31}}

When the [[UltraBay Slim HDD Adapter]] or [[UltraBay Slim SATA HDD Adapter]] are used, the second hard disk will typically provide another temperature readout via its SMART interface, analogously to the above.

Reading this sensor will typically cause a drive spin-up and head unload.

===Hitachi harddisks <tt>SENSE CONDITION</tt> temperature sensor===

Recent Hitachi disks provide a non-standard <tt>SENSE CONDITION</tt> command which reads the disk temperature without causing a spin-up or head load. The reported value is the same as when using SMART. This can be invoked, e.g., using {{cmdroot|hdparm -H}}, or the relevant code in {{CodeRef|tp-fancontrol}}. When using the <tt>libata</tt> driver, this requires kernel >= 2.6.19-rc1.

==Utilities for viewing temperatures==

The following utilities display the ThinkPad-specific thermal sensor readouts:
* The above shell commands.
* The "Sensors" builtin of [[GKrellM]] can show 6 specific ACPI sensors (out of up to 11).
* [http://kima.sourceforge.net/ Kima] is a KDE applet that can display the 8 first ACPI sensors as well as the HDAPS sensor.
* [http://www.kraus.tk/projects/IBMDoK/ IBMDoK], another KDE applet. Shows 4 specific sensors (out of up to 11). So far only tested at the {{T60}}.
* There is an [http://munin.projects.linpro.no/wiki/plugin-ibm_acpi ibm_acpi plugin] for [http://munin.projects.linpro.no/ Munin].
* [http://sensors-applet.sourceforge.net/ GNOME Sensors Applet] supports ibm_acpi.

==Sensor locations==
This information is model specific.

===ThinkPad {{A31}}===
Found by Milos Popovic using cooling spray to cool down components on a completely removed, running motherboard, to locate the sensors. Also reported [http://forum.thinkpads.com/viewtopic.php?t=31837 here].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Battery (this one heats up when on battery power)
0x7A 3 Power (sensor near power diodes and CPU; heats up when high power consumption, has crosstalk from CPU)
0x7B 4 Ultrabay 2000 battery?
0x7C 5 Northbridge (sensor next to Northbridge, also somewhat near GPU)
0x7D 6 PCMCIA/ambient (sensor is a National Semiconductor LM75 Digital Temperature Sensor/Thermal Watchdog chip
next to the 9-pin VGA connector; sits right under PCMCIA slots but doesn't touch)
0x7E 7 Battery (this one stays near ambient temperature, even when on battery power)
0x7F 8 Ultrabay 2000 battery?
0xC0 none zero
0xC1 none zero
0xC2 none zero
The following photos (resolution reduced for server space) show the locations found for the listed temperature sensors.
{{gallery_start}}
{{thumb|A31_2652M3U_systemboardtop_DSCN6105_tempsensors_lores.jpg|ThinkPad A31 sensor locations on top of motherboard.}}
{{thumb|A31_2652M3U_systemboardbottom_DSCN6105_tempsensors_lores.jpg|ThinkPad A31 sensor locations on bottom of motherboard.}}
{{gallery_end}}
On this A31 systemboard (FRU 26P8398), there is a [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2313 Maxim MAX1668] 5-channel remote/local temperature sensor (4 remote + 1 self temperature) on top of the systemboard, and a [http://www.national.com/pf/LM/LM75.html National Semiconductor LM75] single-channel "digital temperature sensor and thermal watchdog" chip. It would appear that the LM75 has the ability to hard shutdown the processor (without software intervention) if its temperature exceeds a given threshold. I'm not sure if it is wired for this, nor whether the Thinkpad changes the threshold temperature from the chip's power-up default of 80Â°C. A software application with drivers on the LM75 webpage is available that claims to allow direct access to the thermal sensor chip (this hasn't been tried, but could be useful in other models to determine if this sensor is somewhere on the MB, and which register it corresponds to). The MAX1668's self-temperature reading does not appear anywhere in the above temperature registers; it's not clear whether it is read at all, and whether it is to be found elsewhere in the EC memory. These two chips (LM75 and MAX1668) account for some of the sensors.

===ThinkPad {{R51}}===
The [[ibm-acpi]] documentation includes the report by Thomas Gruber:
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Mini-PCI
0x7A 3 HDD
0x7B 4 GPU
0x7C 5 System battery
0x7D 6 UltraBay battery
0x7E 7 System battery
0x7F 8 UltraBay battery
0xC0 none ?
0xC1 none ?
0xC2 none ?

===ThinkPad {{T40}}===
The location of one of the sensors is identified [http://forum.thinkpads.com/viewtopic.php?t=11574 here].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 System board under rear left corner of Mini-PCI module
0x7A 3 ?
0x7B 4 GPU
0x7C 5 Battery
0x7D 6 n/a
0x7E 7 Battery
0x7F 8 n/a
0xC0 none n/a
0xC1 none n/a
0xC2 none n/a

===ThinkPad {{T43}}, {{T43p}}===
Found by Shmidoax using cooling spray to cool down components and observe the effect on the sensors.
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Between PCMCIA slot and CPU (same as HDAPS module)
0x7A 3 PCMCIA slot
0x7B 4 GPU
0x7C 5 System battery (front left = charging circuit)
0x7D 6 UltraBay battery
0x7E 7 System battery (rear right)
0x7F 8 UltraBay battery
0xC0 9 Bus between Northbridge and DRAM; Ethernet chip
0xC1 10 Southbridge, WLAN and clock generator (under Mini-PCI card, under touchpad)
0xC2 11 Power circuitry, on underside of system board under F2 key
{{gallery_start}}
{{thumb|T43-thermal-sensors.jpg|ThinkPad T43 sensor locations}}
{{thumb|T43-2668-thermal-sensors-zoom.jpg|ThinkPad T43 sensor locations detail}}
{{thumb|T43p-H8S2161.jpg|ThinkPad T43/p 26xx Embedded Controller Renesas H8S/2161BV}}
{{gallery_end}}

===ThinkPad {{T60}}===
Found by Marco Kraus for use in [http://www.kraus.tk/projects/IBMDoK/ IBMDok].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU 0
0x79 2 HDD
0x7A 3 HDD
0x7B 4 GPU
0x7C 5 Battery
0x7D 6 n/a
0x7E 7 Battery
0x7F 8 n/a
0xC0 9 ?
0xC1 10 ?
0xC2 11 ?

The CPU thermal sensors seem to be exposed in both {{path|/proc/acpi/thermal_zone/THM0/temperature}} and {{path|/proc/acpi/thermal_zone/THM1/temperature}}, though the latter curiously seems to exist only in this file and nowhere in {{path|/proc/acpi/ibm/ecdump}}.

===ThinkPad {{T61}}===
Found By Daniel Castro. There are two sensors for the battery but I'm not sure of the difference or exact location of them. There are still 3 sensors that I couldn't figure out. If anyone can help please update it.

Index in "thermal" Location
1 CPU
2 MiniPCI
3 HDD
4 n/a (-128)
5 Battery 1
6 n/a (-128)
7 Battery 2
8 n/a (-128)
9 ?
10 ?
11 ?
12 n/a (-128)
13 n/a (-128)
14 n/a (-128)
15 n/a (-128)
16 n/a (-128)

The reading for Battery 1 is always 50C, even right after turning the computer on, and it never seems to change, so I monitor the other one.

--[[User:Lunatico|Lunatico]] 23:44, 10 August 2008 (CEST)

===ThinkPad {{X31}}===
I figured these out by myself ([[User:BDKMPSS|BDKMPSS]]), as there are just a few available, this wasn't a huge problem. I verified my presumptions with a contactless thermometer.
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 n/a
0x7A 3 GPU?
0x7B 4 near or the ICH4M Southbrige, on the back of the Motherboard
0x7C 5 Battery
0x7D 6 Extended-Life-Battery; may also UltraBay battery
0x7E 7 Battery
0x7F 8 Extended-Life-Battery; may also UltraBay battery
0xC0 none n/a
0xC1 none n/a
0xC2 none n/a

0x7A "GPU?" is pretty hot and seems like the GPU, but as the Chipset and the GPU are cooled with the same heatsink it is difficult to separate them without roasting the machine. However the left and GPU side of the heatsink is much closer to the shown value than the right Chipset side.

===ThinkPad {{T400}}===
Experimenting with a hair dryer, fgl_glxgears, grep and tools like that I ([[User:Dummyaccount|Dummyaccount]]) came to the following conclusions for the sensor-index mapping. More comments are provided at [http://www.cosy.sbg.ac.at/~shuber/misc-t400.php#temp_sensors].

Index in "thermal" Location
1 CPU neighbourhood (also via ACPI THM0)
2 Ultrabay
3 Express card
4 ATI graphics module
5 Main battery (always around 50°C)
6 n/a (probably ultrabay battery)
7 Main Battery (fits about the value reported by smapi)
8 n/a (probably ultrabay battery)
9 Hard disc
10 Intel graphics module
11 Heatsink?
12 n/a
13 n/a
14 n/a
15 n/a
16 n/a

===ThinkPad {{T500}}===
According to [http://forum.thinkpads.com/viewtopic.php?f=45&t=75032], the sensors in the T500 "may be identical to those reported for the [[#ThinkPad T61|T61]]", with the possibility that #11 may be the CPU heatsink. "It is very closely correlated to cpu load but shows a lot more inertia than sensor 1 which changes almost instantaneously with cpu load."

I ([[User:Nandhp]]) experimented with running glxgears, this produces a spike in #9, which does not occur under regular CPU load. #5 and #7 both belong to the main battery, for they disappear when it is removed. [http://www.kernel.org/doc/Documentation/laptops/thinkpad-acpi.txt] suggests #6 and #8 should be for the UltraBay battery. It also implies that #4 should be for the GPU, however, my model (which has an integrated GPU) does not have a #4 sensor. --[[User:Nandhp|Nandhp]] 19:27, 17 June 2009 (UTC)

Index in "thermal" Location
1 CPU (also via ACPI THM0)
2 ? (very similar to HDD smart temp)
3 ? (also via ACPI THM1)
4 n/a
5 Main Battery A
6 n/a (probably Second Battery A)
7 Main Battery B
8 n/a (probably Second Battery B)
9 ? (possibly (integrated) GPU)
10 ?
11 ? (possibly heatsink)
12 n/a
13 n/a
14 n/a
15 n/a
16 n/a

Thermal Sensors

2009-07-27T07:54:51Z

Dummyaccount: /* Sensor locations */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page summarizes known information about the locations and properties of thermal sensors on ThinkPad laptops.
|}

==Accessing the sensors==

===Basic ACPI system temperature sensors===
The primary means of accessing the thermal sensors is through the [[thinkpad-acpi]] module, up to 16 sensors are supported. When the module is loaded, the sensors (some of which may be inactive) are shown through the standard sysfs hwmon interface used by the lm-sensors utilities, and also in {{path|/proc/acpi/ibm/thermal}} (which is deprecated, and will be removed someday).

lm-sensors/libsensors uses the hwmon interface exposed through {{path|/sys/bus/platform/devices/thinkpad_hwmon/}} to read the temperatures, note that the sysfs interface returns normal open errors instead of weird values for sensors that are not active (which the simplistic '''sensors''' command ignore). lm-sensors/libsensors can be configured to give proper names to each sensor, which will be used by any properly written sensor applet.

{{cmdroot|sensors}}
{{cmdresult|thinkpad-isa-0000
Adapter: ISA adapter
fan1: 3914 RPM
CPU: +45.0°C
LAN/Heatsink/HDAPS: +44.0°C
PC-CARD slot: +35.0°C
GPU: +48.0°C
Main battery charger: +35.0°C
ERROR: Can't get value of subfeature temp6_input: Can't read
Bay battery charger: +0.0°C
Main battery cells: +30.0°C
ERROR: Can't get value of subfeature temp8_input: Can't read
Bay battery cells: +0.0°C
MCH: +42.0°C
PLL clock/ICH/WLAN: +50.0°C
Voltage regulator: +43.0°C}}

The old method to access the thermal readings is through the {{path|/proc}} interface:

:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128}}

A value of -128 (i.e., 0x80 hex) means the sensor is not connected. For example, above the two -128 values belong to the UltraBay battery, which is not plugged in.

If the ThinkPad supports the extended sensor set, eight more values will be displayed:

:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128 48 50 49 -128 -128 -128 -128 -128}}

===HDAPS temperature sensor===
The [[Active Protection System]] firmware also reports a temperature, which is identical to one of the ACPI sensors. The corresponding sensor is actually not inside the HDAPS chip, and sometimes not even close to it.
:{{cmdroot|cat /sys/bus/platform/drivers/hdaps/hdaps/temp1}}
:{{cmdresult|41}}

===Harddisks SMART temperature sensor===
The system hard disk temperature can be read through the disk's SMART interface:
:{{cmdroot|<nowiki>smartctl -A /dev/hda | grep Temperature</nowiki>}}
:{{cmdresult|194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31}}

Or, for SATA-equipped models running a recent Linux kernel (see [[Problems with SATA and Linux]]):

:{{cmdroot|<nowiki>smartctl -A -d ata /dev/sda | grep Temperature</nowiki>}}
:{{cmdresult|194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31}}

When the [[UltraBay Slim HDD Adapter]] or [[UltraBay Slim SATA HDD Adapter]] are used, the second hard disk will typically provide another temperature readout via its SMART interface, analogously to the above.

Reading this sensor will typically cause a drive spin-up and head unload.

===Hitachi harddisks <tt>SENSE CONDITION</tt> temperature sensor===

Recent Hitachi disks provide a non-standard <tt>SENSE CONDITION</tt> command which reads the disk temperature without causing a spin-up or head load. The reported value is the same as when using SMART. This can be invoked, e.g., using {{cmdroot|hdparm -H}}, or the relevant code in {{CodeRef|tp-fancontrol}}. When using the <tt>libata</tt> driver, this requires kernel >= 2.6.19-rc1.

==Utilities for viewing temperatures==

The following utilities display the ThinkPad-specific thermal sensor readouts:
* The above shell commands.
* The "Sensors" builtin of [[GKrellM]] can show 6 specific ACPI sensors (out of up to 11).
* [http://kima.sourceforge.net/ Kima] is a KDE applet that can display the 8 first ACPI sensors as well as the HDAPS sensor.
* [http://www.kraus.tk/projects/IBMDoK/ IBMDoK], another KDE applet. Shows 4 specific sensors (out of up to 11). So far only tested at the {{T60}}.
* There is an [http://munin.projects.linpro.no/wiki/plugin-ibm_acpi ibm_acpi plugin] for [http://munin.projects.linpro.no/ Munin].
* [http://sensors-applet.sourceforge.net/ GNOME Sensors Applet] supports ibm_acpi.

==Sensor locations==
This information is model specific.

===ThinkPad {{A31}}===
Found by Milos Popovic using cooling spray to cool down components on a completely removed, running motherboard, to locate the sensors. Also reported [http://forum.thinkpads.com/viewtopic.php?t=31837 here].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Battery (this one heats up when on battery power)
0x7A 3 Power (sensor near power diodes and CPU; heats up when high power consumption, has crosstalk from CPU)
0x7B 4 Ultrabay 2000 battery?
0x7C 5 Northbridge (sensor next to Northbridge, also somewhat near GPU)
0x7D 6 PCMCIA/ambient (sensor is a National Semiconductor LM75 Digital Temperature Sensor/Thermal Watchdog chip
next to the 9-pin VGA connector; sits right under PCMCIA slots but doesn't touch)
0x7E 7 Battery (this one stays near ambient temperature, even when on battery power)
0x7F 8 Ultrabay 2000 battery?
0xC0 none zero
0xC1 none zero
0xC2 none zero
The following photos (resolution reduced for server space) show the locations found for the listed temperature sensors.
{{gallery_start}}
{{thumb|A31_2652M3U_systemboardtop_DSCN6105_tempsensors_lores.jpg|ThinkPad A31 sensor locations on top of motherboard.}}
{{thumb|A31_2652M3U_systemboardbottom_DSCN6105_tempsensors_lores.jpg|ThinkPad A31 sensor locations on bottom of motherboard.}}
{{gallery_end}}
On this A31 systemboard (FRU 26P8398), there is a [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2313 Maxim MAX1668] 5-channel remote/local temperature sensor (4 remote + 1 self temperature) on top of the systemboard, and a [http://www.national.com/pf/LM/LM75.html National Semiconductor LM75] single-channel "digital temperature sensor and thermal watchdog" chip. It would appear that the LM75 has the ability to hard shutdown the processor (without software intervention) if its temperature exceeds a given threshold. I'm not sure if it is wired for this, nor whether the Thinkpad changes the threshold temperature from the chip's power-up default of 80Â°C. A software application with drivers on the LM75 webpage is available that claims to allow direct access to the thermal sensor chip (this hasn't been tried, but could be useful in other models to determine if this sensor is somewhere on the MB, and which register it corresponds to). The MAX1668's self-temperature reading does not appear anywhere in the above temperature registers; it's not clear whether it is read at all, and whether it is to be found elsewhere in the EC memory. These two chips (LM75 and MAX1668) account for some of the sensors.

===ThinkPad {{R51}}===
The [[ibm-acpi]] documentation includes the report by Thomas Gruber:
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Mini-PCI
0x7A 3 HDD
0x7B 4 GPU
0x7C 5 System battery
0x7D 6 UltraBay battery
0x7E 7 System battery
0x7F 8 UltraBay battery
0xC0 none ?
0xC1 none ?
0xC2 none ?

===ThinkPad {{T40}}===
The location of one of the sensors is identified [http://forum.thinkpads.com/viewtopic.php?t=11574 here].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 System board under rear left corner of Mini-PCI module
0x7A 3 ?
0x7B 4 GPU
0x7C 5 Battery
0x7D 6 n/a
0x7E 7 Battery
0x7F 8 n/a
0xC0 none n/a
0xC1 none n/a
0xC2 none n/a

===ThinkPad {{T43}}, {{T43p}}===
Found by Shmidoax using cooling spray to cool down components and observe the effect on the sensors.
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Between PCMCIA slot and CPU (same as HDAPS module)
0x7A 3 PCMCIA slot
0x7B 4 GPU
0x7C 5 System battery (front left = charging circuit)
0x7D 6 UltraBay battery
0x7E 7 System battery (rear right)
0x7F 8 UltraBay battery
0xC0 9 Bus between Northbridge and DRAM; Ethernet chip
0xC1 10 Southbridge, WLAN and clock generator (under Mini-PCI card, under touchpad)
0xC2 11 Power circuitry, on underside of system board under F2 key
{{gallery_start}}
{{thumb|T43-thermal-sensors.jpg|ThinkPad T43 sensor locations}}
{{thumb|T43-2668-thermal-sensors-zoom.jpg|ThinkPad T43 sensor locations detail}}
{{thumb|T43p-H8S2161.jpg|ThinkPad T43/p 26xx Embedded Controller Renesas H8S/2161BV}}
{{gallery_end}}

===ThinkPad {{T60}}===
Found by Marco Kraus for use in [http://www.kraus.tk/projects/IBMDoK/ IBMDok].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU 0
0x79 2 HDD
0x7A 3 HDD
0x7B 4 GPU
0x7C 5 Battery
0x7D 6 n/a
0x7E 7 Battery
0x7F 8 n/a
0xC0 9 ?
0xC1 10 ?
0xC2 11 ?

The CPU thermal sensors seem to be exposed in both {{path|/proc/acpi/thermal_zone/THM0/temperature}} and {{path|/proc/acpi/thermal_zone/THM1/temperature}}, though the latter curiously seems to exist only in this file and nowhere in {{path|/proc/acpi/ibm/ecdump}}.

===ThinkPad {{T61}}===
Found By Daniel Castro. There are two sensors for the battery but I'm not sure of the difference or exact location of them. There are still 3 sensors that I couldn't figure out. If anyone can help please update it.

Index in "thermal" Location
1 CPU
2 MiniPCI
3 HDD
4 n/a (-128)
5 Battery 1
6 n/a (-128)
7 Battery 2
8 n/a (-128)
9 ?
10 ?
11 ?
12 n/a (-128)
13 n/a (-128)
14 n/a (-128)
15 n/a (-128)
16 n/a (-128)

The reading for Battery 1 is always 50C, even right after turning the computer on, and it never seems to change, so I monitor the other one.

--[[User:Lunatico|Lunatico]] 23:44, 10 August 2008 (CEST)

===ThinkPad {{X31}}===
I figured these out by myself ([[User:BDKMPSS|BDKMPSS]]), as there are just a few available, this wasn't a huge problem. I verified my presumptions with a contactless thermometer.
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 n/a
0x7A 3 GPU?
0x7B 4 near or the ICH4M Southbrige, on the back of the Motherboard
0x7C 5 Battery
0x7D 6 Extended-Life-Battery; may also UltraBay battery
0x7E 7 Battery
0x7F 8 Extended-Life-Battery; may also UltraBay battery
0xC0 none n/a
0xC1 none n/a
0xC2 none n/a

0x7A "GPU?" is pretty hot and seems like the GPU, but as the Chipset and the GPU are cooled with the same heatsink it is difficult to separate them without roasting the machine. However the left and GPU side of the heatsink is much closer to the shown value than the right Chipset side.

===ThinkPad {{T400}}===
Experimenting with a hair dryer, fgl_glxgears, grep and tools like that I ([[User:Dummyacount|Dummyaccount]]) came to the following conclusions for the sensor-index mapping. More comments are provided at [http://www.cosy.sbg.ac.at/~shuber/misc-t400.php#temp_sensors].

Index in "thermal" Location
1 CPU neighbourhood (also via ACPI THM0)
2 Ultrabay
3 Express card
4 ATI graphics module
5 Main battery (always around 50°C)
6 n/a (probably ultrabay battery)
7 Main Battery (fits about the value reported by smapi)
8 n/a (probably ultrabay battery)
9 Hard disc
10 Intel graphics module
11 Heatsink?
12 n/a
13 n/a
14 n/a
15 n/a
16 n/a

===ThinkPad {{T500}}===
According to [http://forum.thinkpads.com/viewtopic.php?f=45&t=75032], the sensors in the T500 "may be identical to those reported for the [[#ThinkPad T61|T61]]", with the possibility that #11 may be the CPU heatsink. "It is very closely correlated to cpu load but shows a lot more inertia than sensor 1 which changes almost instantaneously with cpu load."

I ([[User:Nandhp]]) experimented with running glxgears, this produces a spike in #9, which does not occur under regular CPU load. #5 and #7 both belong to the main battery, for they disappear when it is removed. [http://www.kernel.org/doc/Documentation/laptops/thinkpad-acpi.txt] suggests #6 and #8 should be for the UltraBay battery. It also implies that #4 should be for the GPU, however, my model (which has an integrated GPU) does not have a #4 sensor. --[[User:Nandhp|Nandhp]] 19:27, 17 June 2009 (UTC)

Index in "thermal" Location
1 CPU (also via ACPI THM0)
2 ? (very similar to HDD smart temp)
3 ? (also via ACPI THM1)
4 n/a
5 Main Battery A
6 n/a (probably Second Battery A)
7 Main Battery B
8 n/a (probably Second Battery B)
9 ? (possibly (integrated) GPU)
10 ?
11 ? (possibly heatsink)
12 n/a
13 n/a
14 n/a
15 n/a
16 n/a

Issues with the Wiki

2009-07-27T07:42:05Z

Dummyaccount: /* Cannot get new password */

This page is a provisorium. It's a list of things that are going wrong after the update to help [[User:akw|Akw]] track and fix them.

== Suggestions and requests ==
=== Enable users to cite references ===
Thinkwiki would look cleaner and neater if an article were able to cite its references and track them in one place, rather than having external links strewn throughout the article.

Enabling the <ref> and <references> tag, provided by the [http://www.mediawiki.org/wiki/Extension:Cite/Cite.php Cite Mediawiki extension] would allow users to cite their references. Estimated amount of work to include this plugin: < 1 hour.

=== Enabling user Javascript and CSS for MediaWiki ===

Could ThinkWiki's MediaWiki installation get these options enabled (typically set in LocalSettings.php):

* [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss wgAllowUserCss]
* [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserJs wgAllowUserJs]

These options allow users to have their own custom Javascript and CSS. I (and others) like to have our own custom themes and Javascript when working with MediaWiki-powered websites.

--[[User:SamatJain|SamatJain]] 22:04, 28 July 2007 (UTC)

This is a great security risk. What is it good for?

--[[User:Thinker|Thinker]] 00:14, 29 July 2007 (UTC)

It allowers users to set their own customizations via Javascript and CSS. It's a minor security risk which is why MediaWiki ships with it off, but Wikipedia and other popular websites using MediaWiki ship with it on.

--[[User:SamatJain|SamatJain]] 20:49, 29 July 2007 (UTC)

There is nothing minor about it. The web security model is site-wise when dealing with MediaWiki, there is no easy (read: manageable) way for an user, even one that uses NoScript+Firefox or something else equally powerful, to really filter out trusted from untrusted content when you start allowing people to write JavaScript into a Wiki.

CSS is less of a problem, but it could still hork the site if one is not careful, and MediaWiki already allows us to change the pages well enough. If you need to change thinkwiki CSS for your own viewing pleasure, any browser worth its bytes lets you layer your own CSS on top of a site's. I would not be strongly against enabling CSS, but I don't see any reason to do it, either.

JavaScript submissions, OTOH, is something that must remain disabled. IMO, if you really can't survive without tacking different JavaScript code than what thinkwiki already has, you can use greasemonkey or some other such system to do it in your own browser.

If thinkwiki starts allowing users to set javascript on their pages, I would have to block javascript completely on my side, for example. At that time, it is likely I will just go away. Other contributors might feel the same. It is not that I have anything against JavaScript. It is the fact that I cannot *trust* user-submitted JavaScript.

--[[User:Hmh|hmh]] 12:26, 30 July 2007 (UTC)

These options only enable Javascript and CSS for user pages, i.e. for User:User/Monobook.css and User/Monobook.js, specifically ''not'' for other pages. Disabling these options was done by default as a precaution against XSS vulnerabilies [http://www.gossamer-threads.com/lists/wiki/mediawiki-announce/28572 long since been fixed]. Unfortunately, while I agree with you about disabling user Javascript as a precaution, I do not think the wgAllowUserCss option has any effect unless the wgAllowUserJs option is enabled as well.

--[[User:SamatJain|SamatJain]] 18:52, 30 July 2007 (UTC)

I don't get the point ether.
Why you want to use css/javascript on user pages? You always say why you think its no problem, but not what you want to do. If you need some funky looking stuff or buttons there you should use something like myspace. This Wikis (and almost all other) purpose is collecting the main - Thinkpad - content, not something cool/funky/special on userpages

As Hmh, I would block js immediately and may leave the site, even if its only on userpages, because I don't want to mind clicking "the false links"

--[[User:BDKMPSS|BDKMPSS]], 30 July 2007

[http://en.wikipedia.org/wiki/MediaWiki#Customisation Wikipedia's section on MediaWiki customization] describes some of the extensions and addons available. For example, [http://en.wikipedia.org/wiki/User:Cacycle/wikEd wikiEd] is a WYSIWYG editor such that instead of having to remember MediaWiki's markup, they use an editor that's only enabled for use them. This kind of extending is difficult to do with Stylish or Greasemonkey.

I'll repeat, since I've not been apparently misunderstood:
* Users ''won't'' be able to add Javascript or CSS to arbitrary pages, only those under their user profile (these are called "user pages")
* Only those users logged in will see these their own changes, no other users will.
Given these things, I don't understand why people need to threaten they're going to stop contributing to ThinkWiki? There isn't a way you're going to turn ThinkWiki into MySpace. If you don't use specifically use any CSS or Javascript through these features, it will not effect you at all.

What I personally want to do, I want to use a MediaWiki modification I wrote, [http://meta.wikimedia.org/wiki/Gallery_of_user_styles#Nullbook Nullbook]. I feel as if I am much more efficient with this theme.

--[[User:SamatJain|SamatJain]] 21:58, 30 July 2007 (UTC)

I don't understand what exactly $wgAllowUserJs is supposed to do, and its [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss documentation] is worthless. The crux of the matter is this: if those features are enabled, is there any way ''you'' can cause ''me'' to execute JavaScript (or apply CSS) that ''you'' wrote, in ''any'' page on ThinkWiki? If not, why?

--[[User:Thinker|Thinker]] 22:17, 30 July 2007 (UTC)

[http://meta.wikimedia.org/wiki/User_styles User styles on the MediaWiki site] describes a bit more how these options work and what is provided to any modification that depends upon them. Unless there exist security-related bugs (which is the reason these features are tagged possible security risks, and why they are proactively disabled by default), by design, no, there is no way that I can cause you to execute Javascript or apply CSS that I had put into one of my own "user pages" (i.e. those under [[User:SamatJain]]).

--[[User:SamatJain|SamatJain]] 22:53, 30 July 2007 (UTC)

'''If and only if''' such javascript and css changes are limited so that the user who made them is the only one who gets them, then I have nothing against it.

That said, I'd prefer if the relevant mediawiki code was audited a bit before it is enabled.

PS: Whomever is doing it, please stop screwing around with the formatting: there must be one empty line before and after signatures, it makes the dialog a '''lot''' more readable.

--[[User:Hmh|hmh]] 02:53, 1 August 2007 (UTC)

== Troubles encountered ==

=== Cannot get new password ===

I created a new account ([[User:Shuber2]]). I didn't get a confirmation e-mail, I couldn't log in at the first place and I didn't get a new password after request. Furthermore it would be nice if there would be any e-mail address to contact for such troubles.

--[[User:Dummyaccount|Dummyaccount]] Mon Jul 27 07:20:04 UTC 2009

=== Cannot validate Email addresses ===
I was waiting now for an hour and no validation email arrives.
I double checked my entered email address.

--[[User:Sandoz|Sandoz]] 13:05, 20 March 2009 (UTC)

I also cannot validate my email address. I've tried two different addresses - nothing gets delivered. - robertmuil 2009/06/15.

=== It is not possible to create a new account ===

I tried several times to create an account for myself. After entering all the verification as a human and the necessary account information, passwords etc. I reach a page with the plain message: "Could not open socket". This happens reproducibly with both firefox 3.0.1 (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1) Gecko/2008071618 Iceweasel/3.0.1 (Debian-3.0.1-1)) and konqueror 3.5.9 on an uptodate debian lenny system. The only way to report such problems is by finding someone with a valid login, because I couldn't find a way to report by e-mail or any other means.

Thanks for fixing this.

--johannes at physik blm tu-muenchen de

=== Problems with Language.php ===

Some pages are not happy with mediawiki 1.11.0, and return:
Warning: array_slice() [function.array-slice]: The first argument should be an array in /home/thinkwiki/htdocs/mediawiki-1.11.0/languages/Language.php on line 1153

For an example, see: [[User:Akw | Akw's user page]]

--[[User:Hmh|hmh]] 01:14, 20 October 2007 (UTC)

=== Problem with cmdroot ===

Following String is not handled correct by template cmdroot:
"fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image"

see here:
{{cmdroot|fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

=== Can not open page to edit without introducing modifications ===

If I open the [[X31]] model page and without touching anything I hit preview, the div token is decomposed and appears in the preview page, and of course, the photo is not in the right place.

--[[User:Ungoliant|Ungoliant]] 19:24, 20 February 2007 (CET)

=== Uploading SVG files ===

'''Can not upload SVG'''
I get the upload warning:
".svg" is not a recommended image file format.
--[[User:Matt|Matt]] 14:02, 3 December 2006 (CET)

=== SpamBlackList not working ===

* [[ThinkWiki:SpamBlackList]] does not appear to work anymore

--[[User:Tonko|Tonko]] 03:40, 11 March 2006 (CET)

=== Multiline cmdresult template ===

You can't (easliy do a multiline {{cmdresult|cmdresult}}, can you? See:

{{cmdresult|foo
bar
baz}}

or

{{cmdresult|foo
bar (after whitespace)
baz (after whitespace)}}

This works (but is not so nice)

{{cmdresult|foo

bar (after empty line)

baz (after empty line)}}

Any suggestions?

--[[User:Pebolle|Paul Bolle]] 10:27, 24 January 2006 (CET)

----

I think the best way is to use single cmdresult calls for each line and prefix them with a colon. Like so:
<pre><nowiki>
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}
</nowiki></pre>, which results in
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}

Alternatively, you can use at the ende of each line within one call, like this:
<tt><nowiki>{{cmdresult|foo 
bar 
baz}}</nowiki></tt>
, which will result in

{{cmdresult|foo 
bar 
baz}}

--[[User:Wyrfel|Wyrfel]] 12:13, 24 January 2006 (CET)

=== Server time out-of-sync ===

The server time would appear to be off a lot, is it possible to setup ntpd, or to run ntpdate every hour or so using cron?

--[[User:Tonko|Tonko]] 05:11, 22 February 2006 (CET)

=== Missing imagemagick on server ===

Error creating thumbnail: /home/thinkwiki/htdocs/mediawiki-1.10.0/bin/ulimit4.sh: line 4: /usr/bin/convert: No such file or directory

I think the computer this wiki is running on is missing the imagemagick software tools especially convert to create thumbnails of images

--[[User:Markusw|Markusw]] 10:21, 26 August 2007 (UTC)

=== Your signature with timestamp button ===

This Button simply doesn't work, it adds <nowiki>--~~~~</nowiki> 
I think its a bunch on javascript so I may add: 
I use Firefox (branded as Icewasel) on Debian Testing 
Preferences: 
Raw signatures (without automatic link) OFF 
Show edit toolbar (JavaScript) ON 
(Oh... Yes its javascript)

EDIT:
Even in my Windows XP SP2 Virtual Machine it don't work in Internet Explorer 7.0

--[[User:BDKMPSS|BDKMPSS]] 29 July 2007

I have been using this button for quite a while now, and it seems to work just fine. It does insert <nowiki>--~~~</nowiki>, but upon submitting previews or saving the page, it gets converted into my signature.

--[[User:Hmh|hmh]] 01:27, 20 October 2007 (UTC)

hm... (wow a nice joke...)

lets try this

--[[User:BDKMPSS|BDKMPSS]] 00:30, 21 October 2007 (UTC)

OK, its all fine... I'm sorry but this seems to be extremely non-intuitive...

--[[User:BDKMPSS|BDKMPSS]] 00:32, 21 October 2007 (UTC)

Yeah, intuitive it ain't...

--[[User:Hmh|hmh]] 00:43, 22 October 2007 (UTC)

=== Problem with the feeds (RSS and Atom) ===
The feed does not validate, and thus not load in Firefox or Liferea.

The problem is, that there is a trailing newline before <?xml version="1.0" encoding="utf-8"?> which is not allowed

--[[User:Zhenech|Zhenech]] 12:14, 11 December 2007 (UTC)

=== Search is broken ===

The search feature is completely borked: every query I try returns zero results.

--[[User:RichardNeill|RichardNeill]] 02:16, 13 January 2008 (CET)

They work just fine here, through Google (the search box launches a Google search, and returns it in a ThinkWiki-style page).

Check your browser "defense" settings, you may be blocking too much.

--[[User:Hmh|hmh]] 04:23, 13 January 2008 (CET)

== Problems fixed ==

* List emptied, since everything in it was more than one year old

Issues with the Wiki

2009-07-27T07:41:35Z

Dummyaccount: /* Cannot get new password */

This page is a provisorium. It's a list of things that are going wrong after the update to help [[User:akw|Akw]] track and fix them.

== Suggestions and requests ==
=== Enable users to cite references ===
Thinkwiki would look cleaner and neater if an article were able to cite its references and track them in one place, rather than having external links strewn throughout the article.

Enabling the <ref> and <references> tag, provided by the [http://www.mediawiki.org/wiki/Extension:Cite/Cite.php Cite Mediawiki extension] would allow users to cite their references. Estimated amount of work to include this plugin: < 1 hour.

=== Enabling user Javascript and CSS for MediaWiki ===

Could ThinkWiki's MediaWiki installation get these options enabled (typically set in LocalSettings.php):

* [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss wgAllowUserCss]
* [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserJs wgAllowUserJs]

These options allow users to have their own custom Javascript and CSS. I (and others) like to have our own custom themes and Javascript when working with MediaWiki-powered websites.

--[[User:SamatJain|SamatJain]] 22:04, 28 July 2007 (UTC)

This is a great security risk. What is it good for?

--[[User:Thinker|Thinker]] 00:14, 29 July 2007 (UTC)

It allowers users to set their own customizations via Javascript and CSS. It's a minor security risk which is why MediaWiki ships with it off, but Wikipedia and other popular websites using MediaWiki ship with it on.

--[[User:SamatJain|SamatJain]] 20:49, 29 July 2007 (UTC)

There is nothing minor about it. The web security model is site-wise when dealing with MediaWiki, there is no easy (read: manageable) way for an user, even one that uses NoScript+Firefox or something else equally powerful, to really filter out trusted from untrusted content when you start allowing people to write JavaScript into a Wiki.

CSS is less of a problem, but it could still hork the site if one is not careful, and MediaWiki already allows us to change the pages well enough. If you need to change thinkwiki CSS for your own viewing pleasure, any browser worth its bytes lets you layer your own CSS on top of a site's. I would not be strongly against enabling CSS, but I don't see any reason to do it, either.

JavaScript submissions, OTOH, is something that must remain disabled. IMO, if you really can't survive without tacking different JavaScript code than what thinkwiki already has, you can use greasemonkey or some other such system to do it in your own browser.

If thinkwiki starts allowing users to set javascript on their pages, I would have to block javascript completely on my side, for example. At that time, it is likely I will just go away. Other contributors might feel the same. It is not that I have anything against JavaScript. It is the fact that I cannot *trust* user-submitted JavaScript.

--[[User:Hmh|hmh]] 12:26, 30 July 2007 (UTC)

These options only enable Javascript and CSS for user pages, i.e. for User:User/Monobook.css and User/Monobook.js, specifically ''not'' for other pages. Disabling these options was done by default as a precaution against XSS vulnerabilies [http://www.gossamer-threads.com/lists/wiki/mediawiki-announce/28572 long since been fixed]. Unfortunately, while I agree with you about disabling user Javascript as a precaution, I do not think the wgAllowUserCss option has any effect unless the wgAllowUserJs option is enabled as well.

--[[User:SamatJain|SamatJain]] 18:52, 30 July 2007 (UTC)

I don't get the point ether.
Why you want to use css/javascript on user pages? You always say why you think its no problem, but not what you want to do. If you need some funky looking stuff or buttons there you should use something like myspace. This Wikis (and almost all other) purpose is collecting the main - Thinkpad - content, not something cool/funky/special on userpages

As Hmh, I would block js immediately and may leave the site, even if its only on userpages, because I don't want to mind clicking "the false links"

--[[User:BDKMPSS|BDKMPSS]], 30 July 2007

[http://en.wikipedia.org/wiki/MediaWiki#Customisation Wikipedia's section on MediaWiki customization] describes some of the extensions and addons available. For example, [http://en.wikipedia.org/wiki/User:Cacycle/wikEd wikiEd] is a WYSIWYG editor such that instead of having to remember MediaWiki's markup, they use an editor that's only enabled for use them. This kind of extending is difficult to do with Stylish or Greasemonkey.

I'll repeat, since I've not been apparently misunderstood:
* Users ''won't'' be able to add Javascript or CSS to arbitrary pages, only those under their user profile (these are called "user pages")
* Only those users logged in will see these their own changes, no other users will.
Given these things, I don't understand why people need to threaten they're going to stop contributing to ThinkWiki? There isn't a way you're going to turn ThinkWiki into MySpace. If you don't use specifically use any CSS or Javascript through these features, it will not effect you at all.

What I personally want to do, I want to use a MediaWiki modification I wrote, [http://meta.wikimedia.org/wiki/Gallery_of_user_styles#Nullbook Nullbook]. I feel as if I am much more efficient with this theme.

--[[User:SamatJain|SamatJain]] 21:58, 30 July 2007 (UTC)

I don't understand what exactly $wgAllowUserJs is supposed to do, and its [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss documentation] is worthless. The crux of the matter is this: if those features are enabled, is there any way ''you'' can cause ''me'' to execute JavaScript (or apply CSS) that ''you'' wrote, in ''any'' page on ThinkWiki? If not, why?

--[[User:Thinker|Thinker]] 22:17, 30 July 2007 (UTC)

[http://meta.wikimedia.org/wiki/User_styles User styles on the MediaWiki site] describes a bit more how these options work and what is provided to any modification that depends upon them. Unless there exist security-related bugs (which is the reason these features are tagged possible security risks, and why they are proactively disabled by default), by design, no, there is no way that I can cause you to execute Javascript or apply CSS that I had put into one of my own "user pages" (i.e. those under [[User:SamatJain]]).

--[[User:SamatJain|SamatJain]] 22:53, 30 July 2007 (UTC)

'''If and only if''' such javascript and css changes are limited so that the user who made them is the only one who gets them, then I have nothing against it.

That said, I'd prefer if the relevant mediawiki code was audited a bit before it is enabled.

PS: Whomever is doing it, please stop screwing around with the formatting: there must be one empty line before and after signatures, it makes the dialog a '''lot''' more readable.

--[[User:Hmh|hmh]] 02:53, 1 August 2007 (UTC)

== Troubles encountered ==

=== Cannot get new password ===

I created a new account ([[User:Shuber]]). I didn't get a confirmation e-mail, I couldn't log in at the first place and I didn't get a new password after request. Furthermore it would be nice if there would be any e-mail address to contact for such troubles.

--[[User:Dummyaccount] Mon Jul 27 07:20:04 UTC 2009

=== Cannot validate Email addresses ===
I was waiting now for an hour and no validation email arrives.
I double checked my entered email address.

--[[User:Sandoz|Sandoz]] 13:05, 20 March 2009 (UTC)

I also cannot validate my email address. I've tried two different addresses - nothing gets delivered. - robertmuil 2009/06/15.

=== It is not possible to create a new account ===

I tried several times to create an account for myself. After entering all the verification as a human and the necessary account information, passwords etc. I reach a page with the plain message: "Could not open socket". This happens reproducibly with both firefox 3.0.1 (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1) Gecko/2008071618 Iceweasel/3.0.1 (Debian-3.0.1-1)) and konqueror 3.5.9 on an uptodate debian lenny system. The only way to report such problems is by finding someone with a valid login, because I couldn't find a way to report by e-mail or any other means.

Thanks for fixing this.

--johannes at physik blm tu-muenchen de

=== Problems with Language.php ===

Some pages are not happy with mediawiki 1.11.0, and return:
Warning: array_slice() [function.array-slice]: The first argument should be an array in /home/thinkwiki/htdocs/mediawiki-1.11.0/languages/Language.php on line 1153

For an example, see: [[User:Akw | Akw's user page]]

--[[User:Hmh|hmh]] 01:14, 20 October 2007 (UTC)

=== Problem with cmdroot ===

Following String is not handled correct by template cmdroot:
"fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image"

see here:
{{cmdroot|fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

=== Can not open page to edit without introducing modifications ===

If I open the [[X31]] model page and without touching anything I hit preview, the div token is decomposed and appears in the preview page, and of course, the photo is not in the right place.

--[[User:Ungoliant|Ungoliant]] 19:24, 20 February 2007 (CET)

=== Uploading SVG files ===

'''Can not upload SVG'''
I get the upload warning:
".svg" is not a recommended image file format.
--[[User:Matt|Matt]] 14:02, 3 December 2006 (CET)

=== SpamBlackList not working ===

* [[ThinkWiki:SpamBlackList]] does not appear to work anymore

--[[User:Tonko|Tonko]] 03:40, 11 March 2006 (CET)

=== Multiline cmdresult template ===

You can't (easliy do a multiline {{cmdresult|cmdresult}}, can you? See:

{{cmdresult|foo
bar
baz}}

or

{{cmdresult|foo
bar (after whitespace)
baz (after whitespace)}}

This works (but is not so nice)

{{cmdresult|foo

bar (after empty line)

baz (after empty line)}}

Any suggestions?

--[[User:Pebolle|Paul Bolle]] 10:27, 24 January 2006 (CET)

----

I think the best way is to use single cmdresult calls for each line and prefix them with a colon. Like so:
<pre><nowiki>
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}
</nowiki></pre>, which results in
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}

Alternatively, you can use at the ende of each line within one call, like this:
<tt><nowiki>{{cmdresult|foo 
bar 
baz}}</nowiki></tt>
, which will result in

{{cmdresult|foo 
bar 
baz}}

--[[User:Wyrfel|Wyrfel]] 12:13, 24 January 2006 (CET)

=== Server time out-of-sync ===

The server time would appear to be off a lot, is it possible to setup ntpd, or to run ntpdate every hour or so using cron?

--[[User:Tonko|Tonko]] 05:11, 22 February 2006 (CET)

=== Missing imagemagick on server ===

Error creating thumbnail: /home/thinkwiki/htdocs/mediawiki-1.10.0/bin/ulimit4.sh: line 4: /usr/bin/convert: No such file or directory

I think the computer this wiki is running on is missing the imagemagick software tools especially convert to create thumbnails of images

--[[User:Markusw|Markusw]] 10:21, 26 August 2007 (UTC)

=== Your signature with timestamp button ===

This Button simply doesn't work, it adds <nowiki>--~~~~</nowiki> 
I think its a bunch on javascript so I may add: 
I use Firefox (branded as Icewasel) on Debian Testing 
Preferences: 
Raw signatures (without automatic link) OFF 
Show edit toolbar (JavaScript) ON 
(Oh... Yes its javascript)

EDIT:
Even in my Windows XP SP2 Virtual Machine it don't work in Internet Explorer 7.0

--[[User:BDKMPSS|BDKMPSS]] 29 July 2007

I have been using this button for quite a while now, and it seems to work just fine. It does insert <nowiki>--~~~</nowiki>, but upon submitting previews or saving the page, it gets converted into my signature.

--[[User:Hmh|hmh]] 01:27, 20 October 2007 (UTC)

hm... (wow a nice joke...)

lets try this

--[[User:BDKMPSS|BDKMPSS]] 00:30, 21 October 2007 (UTC)

OK, its all fine... I'm sorry but this seems to be extremely non-intuitive...

--[[User:BDKMPSS|BDKMPSS]] 00:32, 21 October 2007 (UTC)

Yeah, intuitive it ain't...

--[[User:Hmh|hmh]] 00:43, 22 October 2007 (UTC)

=== Problem with the feeds (RSS and Atom) ===
The feed does not validate, and thus not load in Firefox or Liferea.

The problem is, that there is a trailing newline before <?xml version="1.0" encoding="utf-8"?> which is not allowed

--[[User:Zhenech|Zhenech]] 12:14, 11 December 2007 (UTC)

=== Search is broken ===

The search feature is completely borked: every query I try returns zero results.

--[[User:RichardNeill|RichardNeill]] 02:16, 13 January 2008 (CET)

They work just fine here, through Google (the search box launches a Google search, and returns it in a ThinkWiki-style page).

Check your browser "defense" settings, you may be blocking too much.

--[[User:Hmh|hmh]] 04:23, 13 January 2008 (CET)

== Problems fixed ==

* List emptied, since everything in it was more than one year old

Issues with the Wiki

2009-07-27T07:39:41Z

Dummyaccount: /* Troubles encountered */

This page is a provisorium. It's a list of things that are going wrong after the update to help [[User:akw|Akw]] track and fix them.

== Suggestions and requests ==
=== Enable users to cite references ===
Thinkwiki would look cleaner and neater if an article were able to cite its references and track them in one place, rather than having external links strewn throughout the article.

Enabling the <ref> and <references> tag, provided by the [http://www.mediawiki.org/wiki/Extension:Cite/Cite.php Cite Mediawiki extension] would allow users to cite their references. Estimated amount of work to include this plugin: < 1 hour.

=== Enabling user Javascript and CSS for MediaWiki ===

Could ThinkWiki's MediaWiki installation get these options enabled (typically set in LocalSettings.php):

* [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss wgAllowUserCss]
* [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserJs wgAllowUserJs]

These options allow users to have their own custom Javascript and CSS. I (and others) like to have our own custom themes and Javascript when working with MediaWiki-powered websites.

--[[User:SamatJain|SamatJain]] 22:04, 28 July 2007 (UTC)

This is a great security risk. What is it good for?

--[[User:Thinker|Thinker]] 00:14, 29 July 2007 (UTC)

It allowers users to set their own customizations via Javascript and CSS. It's a minor security risk which is why MediaWiki ships with it off, but Wikipedia and other popular websites using MediaWiki ship with it on.

--[[User:SamatJain|SamatJain]] 20:49, 29 July 2007 (UTC)

There is nothing minor about it. The web security model is site-wise when dealing with MediaWiki, there is no easy (read: manageable) way for an user, even one that uses NoScript+Firefox or something else equally powerful, to really filter out trusted from untrusted content when you start allowing people to write JavaScript into a Wiki.

CSS is less of a problem, but it could still hork the site if one is not careful, and MediaWiki already allows us to change the pages well enough. If you need to change thinkwiki CSS for your own viewing pleasure, any browser worth its bytes lets you layer your own CSS on top of a site's. I would not be strongly against enabling CSS, but I don't see any reason to do it, either.

JavaScript submissions, OTOH, is something that must remain disabled. IMO, if you really can't survive without tacking different JavaScript code than what thinkwiki already has, you can use greasemonkey or some other such system to do it in your own browser.

If thinkwiki starts allowing users to set javascript on their pages, I would have to block javascript completely on my side, for example. At that time, it is likely I will just go away. Other contributors might feel the same. It is not that I have anything against JavaScript. It is the fact that I cannot *trust* user-submitted JavaScript.

--[[User:Hmh|hmh]] 12:26, 30 July 2007 (UTC)

These options only enable Javascript and CSS for user pages, i.e. for User:User/Monobook.css and User/Monobook.js, specifically ''not'' for other pages. Disabling these options was done by default as a precaution against XSS vulnerabilies [http://www.gossamer-threads.com/lists/wiki/mediawiki-announce/28572 long since been fixed]. Unfortunately, while I agree with you about disabling user Javascript as a precaution, I do not think the wgAllowUserCss option has any effect unless the wgAllowUserJs option is enabled as well.

--[[User:SamatJain|SamatJain]] 18:52, 30 July 2007 (UTC)

I don't get the point ether.
Why you want to use css/javascript on user pages? You always say why you think its no problem, but not what you want to do. If you need some funky looking stuff or buttons there you should use something like myspace. This Wikis (and almost all other) purpose is collecting the main - Thinkpad - content, not something cool/funky/special on userpages

As Hmh, I would block js immediately and may leave the site, even if its only on userpages, because I don't want to mind clicking "the false links"

--[[User:BDKMPSS|BDKMPSS]], 30 July 2007

[http://en.wikipedia.org/wiki/MediaWiki#Customisation Wikipedia's section on MediaWiki customization] describes some of the extensions and addons available. For example, [http://en.wikipedia.org/wiki/User:Cacycle/wikEd wikiEd] is a WYSIWYG editor such that instead of having to remember MediaWiki's markup, they use an editor that's only enabled for use them. This kind of extending is difficult to do with Stylish or Greasemonkey.

I'll repeat, since I've not been apparently misunderstood:
* Users ''won't'' be able to add Javascript or CSS to arbitrary pages, only those under their user profile (these are called "user pages")
* Only those users logged in will see these their own changes, no other users will.
Given these things, I don't understand why people need to threaten they're going to stop contributing to ThinkWiki? There isn't a way you're going to turn ThinkWiki into MySpace. If you don't use specifically use any CSS or Javascript through these features, it will not effect you at all.

What I personally want to do, I want to use a MediaWiki modification I wrote, [http://meta.wikimedia.org/wiki/Gallery_of_user_styles#Nullbook Nullbook]. I feel as if I am much more efficient with this theme.

--[[User:SamatJain|SamatJain]] 21:58, 30 July 2007 (UTC)

I don't understand what exactly $wgAllowUserJs is supposed to do, and its [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss documentation] is worthless. The crux of the matter is this: if those features are enabled, is there any way ''you'' can cause ''me'' to execute JavaScript (or apply CSS) that ''you'' wrote, in ''any'' page on ThinkWiki? If not, why?

--[[User:Thinker|Thinker]] 22:17, 30 July 2007 (UTC)

[http://meta.wikimedia.org/wiki/User_styles User styles on the MediaWiki site] describes a bit more how these options work and what is provided to any modification that depends upon them. Unless there exist security-related bugs (which is the reason these features are tagged possible security risks, and why they are proactively disabled by default), by design, no, there is no way that I can cause you to execute Javascript or apply CSS that I had put into one of my own "user pages" (i.e. those under [[User:SamatJain]]).

--[[User:SamatJain|SamatJain]] 22:53, 30 July 2007 (UTC)

'''If and only if''' such javascript and css changes are limited so that the user who made them is the only one who gets them, then I have nothing against it.

That said, I'd prefer if the relevant mediawiki code was audited a bit before it is enabled.

PS: Whomever is doing it, please stop screwing around with the formatting: there must be one empty line before and after signatures, it makes the dialog a '''lot''' more readable.

--[[User:Hmh|hmh]] 02:53, 1 August 2007 (UTC)

== Troubles encountered ==

=== Cannot get new password ===

I created a new account ([[User:Shuber]]). I didn't get a confirmation e-mail, I couldn't log in at the first place and I didn't get a new password after request. Furthermore it would be nice if there would be any e-mail address to contact for such troubles.

--[[User:Sandoz|Sandoz]] Mon Jul 27 07:20:04 UTC 2009

=== Cannot validate Email addresses ===
I was waiting now for an hour and no validation email arrives.
I double checked my entered email address.

--[[User:Sandoz|Sandoz]] 13:05, 20 March 2009 (UTC)

I also cannot validate my email address. I've tried two different addresses - nothing gets delivered. - robertmuil 2009/06/15.

=== It is not possible to create a new account ===

I tried several times to create an account for myself. After entering all the verification as a human and the necessary account information, passwords etc. I reach a page with the plain message: "Could not open socket". This happens reproducibly with both firefox 3.0.1 (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1) Gecko/2008071618 Iceweasel/3.0.1 (Debian-3.0.1-1)) and konqueror 3.5.9 on an uptodate debian lenny system. The only way to report such problems is by finding someone with a valid login, because I couldn't find a way to report by e-mail or any other means.

Thanks for fixing this.

--johannes at physik blm tu-muenchen de

=== Problems with Language.php ===

Some pages are not happy with mediawiki 1.11.0, and return:
Warning: array_slice() [function.array-slice]: The first argument should be an array in /home/thinkwiki/htdocs/mediawiki-1.11.0/languages/Language.php on line 1153

For an example, see: [[User:Akw | Akw's user page]]

--[[User:Hmh|hmh]] 01:14, 20 October 2007 (UTC)

=== Problem with cmdroot ===

Following String is not handled correct by template cmdroot:
"fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image"

see here:
{{cmdroot|fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

=== Can not open page to edit without introducing modifications ===

If I open the [[X31]] model page and without touching anything I hit preview, the div token is decomposed and appears in the preview page, and of course, the photo is not in the right place.

--[[User:Ungoliant|Ungoliant]] 19:24, 20 February 2007 (CET)

=== Uploading SVG files ===

'''Can not upload SVG'''
I get the upload warning:
".svg" is not a recommended image file format.
--[[User:Matt|Matt]] 14:02, 3 December 2006 (CET)

=== SpamBlackList not working ===

* [[ThinkWiki:SpamBlackList]] does not appear to work anymore

--[[User:Tonko|Tonko]] 03:40, 11 March 2006 (CET)

=== Multiline cmdresult template ===

You can't (easliy do a multiline {{cmdresult|cmdresult}}, can you? See:

{{cmdresult|foo
bar
baz}}

or

{{cmdresult|foo
bar (after whitespace)
baz (after whitespace)}}

This works (but is not so nice)

{{cmdresult|foo

bar (after empty line)

baz (after empty line)}}

Any suggestions?

--[[User:Pebolle|Paul Bolle]] 10:27, 24 January 2006 (CET)

----

I think the best way is to use single cmdresult calls for each line and prefix them with a colon. Like so:
<pre><nowiki>
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}
</nowiki></pre>, which results in
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}

Alternatively, you can use at the ende of each line within one call, like this:
<tt><nowiki>{{cmdresult|foo 
bar 
baz}}</nowiki></tt>
, which will result in

{{cmdresult|foo 
bar 
baz}}

--[[User:Wyrfel|Wyrfel]] 12:13, 24 January 2006 (CET)

=== Server time out-of-sync ===

The server time would appear to be off a lot, is it possible to setup ntpd, or to run ntpdate every hour or so using cron?

--[[User:Tonko|Tonko]] 05:11, 22 February 2006 (CET)

=== Missing imagemagick on server ===

Error creating thumbnail: /home/thinkwiki/htdocs/mediawiki-1.10.0/bin/ulimit4.sh: line 4: /usr/bin/convert: No such file or directory

I think the computer this wiki is running on is missing the imagemagick software tools especially convert to create thumbnails of images

--[[User:Markusw|Markusw]] 10:21, 26 August 2007 (UTC)

=== Your signature with timestamp button ===

This Button simply doesn't work, it adds <nowiki>--~~~~</nowiki> 
I think its a bunch on javascript so I may add: 
I use Firefox (branded as Icewasel) on Debian Testing 
Preferences: 
Raw signatures (without automatic link) OFF 
Show edit toolbar (JavaScript) ON 
(Oh... Yes its javascript)

EDIT:
Even in my Windows XP SP2 Virtual Machine it don't work in Internet Explorer 7.0

--[[User:BDKMPSS|BDKMPSS]] 29 July 2007

I have been using this button for quite a while now, and it seems to work just fine. It does insert <nowiki>--~~~</nowiki>, but upon submitting previews or saving the page, it gets converted into my signature.

--[[User:Hmh|hmh]] 01:27, 20 October 2007 (UTC)

hm... (wow a nice joke...)

lets try this

--[[User:BDKMPSS|BDKMPSS]] 00:30, 21 October 2007 (UTC)

OK, its all fine... I'm sorry but this seems to be extremely non-intuitive...

--[[User:BDKMPSS|BDKMPSS]] 00:32, 21 October 2007 (UTC)

Yeah, intuitive it ain't...

--[[User:Hmh|hmh]] 00:43, 22 October 2007 (UTC)

=== Problem with the feeds (RSS and Atom) ===
The feed does not validate, and thus not load in Firefox or Liferea.

The problem is, that there is a trailing newline before <?xml version="1.0" encoding="utf-8"?> which is not allowed

--[[User:Zhenech|Zhenech]] 12:14, 11 December 2007 (UTC)

=== Search is broken ===

The search feature is completely borked: every query I try returns zero results.

--[[User:RichardNeill|RichardNeill]] 02:16, 13 January 2008 (CET)

They work just fine here, through Google (the search box launches a Google search, and returns it in a ThinkWiki-style page).

Check your browser "defense" settings, you may be blocking too much.

--[[User:Hmh|hmh]] 04:23, 13 January 2008 (CET)

== Problems fixed ==

* List emptied, since everything in it was more than one year old