Thinkpad Related Resources
- ThinkPad Troubleshooting by topic
- Linux Driver Matrix for ThinkPads
- Disassembly Instructions for ThinkPads (Covering most models!)
- isa sound issues
modprobe cs4232 io=0x530 irq=5 dma=1 dma2=0 mpuio=0x330 mpuirq=5 synthirq=-1 synthio=-1
- isa sound issues
modprobe cs4232 io=0x530 dma=1 dma2=0 irq=5
- fan issues
to the grub boot options.
echo 0x2f 0x07 > /proc/acpi/ibm/ecdump
typing that command and redirecting that output to the embedded control dump (ecdump) file will turn that fan on at it's maximum speed.
this simple script found here:http://www.thinkwiki.org/wiki/ACPI_fan_control_script and take care of any unnecessary end-user interaction with the fan control. other useful information can be found their as well, about controlling the fan.
RAM slot failure, it's a solder failure, usually starts in the second slot and worsens from there. http://www.thinkwiki.org/wiki/Problem_with_failing_memory_slot As-is these machines.
In the frame buffer environment (pre-GUI) the top portion of the screen has a stripe of garbled (red) characters. This fix worked for this chipset:
$ lspci -k | grep -A1 VGA 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400 Kernel modules: radeon $ sudo gedit /etc/default/grup
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to read
GRUB_CMDLINE_LINUX_DEFAULT="radeon.modeset=0 quiet splash".
$ sudo update-grub
Reboot. Is fixed, no?
- Wireless device recognized, not working
- First thought was that the integrated Bluetooth device was having some kind of hardware conflict with the wireless card. Running
rfkill listshowed the wireless card subject to a hardware block, which usually stems from a wireless switch. However, flipping the wireless switch (physical switch immediately below the center of the palm rest, SoftKey = Fn+F2) would bring the bluetooth up and then down, but leave the wireless as it was. Turns out, the solution was a BIOS option.
- Enter BIOS (F1 on POST)
- Go to Config -> Network
- Set the Wireless LAN Radio Frequency option to On
And you're golden. Sheesh.
- Systems with BIOS passwords do not netboot correctly: System reboots when an option is selected
- Install a hard drive, network boot should behave normally. Working hypothesis is the locked BIOS passes incorrect system information about a drive being present, and clobbers the netboot.
- Working hypothesis is wrong, after cracking the BIOS password and updating to BIOS version 2.29, the problem is the same until a HDD is installed. Lynnae 22:58, 6 September 2012 (UTC)