ThinkWiki - User contributions [en]

Installing Ubuntu 9.04 (Jaunty Jackalope) on a ThinkPad T61

2009-04-26T20:58:13Z

VincentP: vertical trackpad scrolling

Comprehensive review: http://www.eastwoodzhao.com/ubuntu-904-jaunty-jackalope-on-thinkpad-t61/

== Items that work out of the box ==

'''Intel Video:''' ???

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested

'''Network Card:''' Intel 10/100/1000 tested

'''Wireless switch:''' Tested

'''Headphones:''' Works out of the box

'''Microphone:''' Just needs to be activated

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated

== Items that need (some) tweaking to obtain full functionality ==

'''Fingerprint Reader:''' Does anyone have directions for this?

'''Middle-click scrolling:''' Does anyone have directions for this? See [[How_to_configure_the_TrackPoint#vertical_scrolling|Vertical scrolling]]

Talk:Ipw2200

2008-08-06T22:02:44Z

VincentP: /* Radio Switch utility needed */

The ipw2000 drivers loads clean on my t42 and the interface eth1 is accessible. However,
the wireless-lan LED does not light and i cant connect. Havent figured out what this is.

== Debian sid / lenny firmware load problem ==
A recent (08/08) debian sid update led to this error :

ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0kmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 21 (level, low) -> IRQ 23
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
ipw2200: Unable to load firmware: -2
ipw2200: failed to register network device
ACPI: PCI interrupt for device 0000:04:02.0 disabled

I tried to reinstall the latest firmware (3.0) into /lib/firmware without success.

Unpacking the firmware archive into /lib/modules solved the problem.

I am not sure of the definitive correct place for ipw2200 firmware in debian sid, but this may help others as I did not find a lot of places on the net mentioning this. Do not hesitate to add details or modify this entry if you know more.

--[[User:VincentP|VincentP]] 00:02, 7 August 2008 (CEST)

== Radio Switch utility needed ==

I have the same problem.
WiFi adapter must be turned on before using. In Windows software utility is executed by Fn+F5 keys. This utility turns WiFi and/or Bluetooth adpters on/off. In Linux Fn+F5 controls only Bluetooth adapter.
Unfortunately I can not find switch utility yet (10 Sep 2005).

----

Try using the usual hotkey hooks to activate the power management features described in the article.
--[[User:Thinker|Thinker]] 04:37, 18 Nov 2005 (CET)
----

== Reliability problems ==

On a T43p ipw2200 v1.0.6 works well 95% of the time with WPA using wpa_supplicant. However it seemingly randomly causes trouble and refuses to connect (it is not the router, as non-linux devices work.) It always recovers with a killall wpa_supplicant, unloading the ipw2200 and ieee80211 modules, and reloading everything (you can even write a "netreset" script to do this for you automatically, as I have done.)

It's frustrating, because this is so un-"linux-like" to have intermittent unreliability. Usually things work 100% or 0% of the time on my linux system. Note, I have not used the 2.6.15-rc kernel version nor 1.0.8 with WPA yet, this problem might be fixed. Can anybody verify? --[[User:Gsmenden|Gsmenden]]
: Same problem here with a Linksys router and WPA, no problem with other routers ... I'll try the new kernel and ipw2200--[[User:Xoby|Xoby]] 18:35, 15 January 2006 (CET)
:: I've tried and still had problems, I also edited my wpa_supplicant file to:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
### Associate with any open access point
### Scans/ESSID changes can be done with wpa_cli
network={
ssid="myssid"
psk="mypass"
priority=1
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP CCMP
}

And successfully transfered more than 5 Gb without any problem--[[User:Xoby|Xoby]] 11:16, 19 January 2006 (CET)

== Sudden breakage... ==
Have any of you had recent problems while running debian sid with ipw2200-1.0.10 and ieee80211-1.1.9 on a t43p? All of a sudden since 2d ago my wireless initialization gives the following error report:

Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; No such device.
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device eth1 ; No such device.
SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
eth1: ERROR while getting interface flags: No such device

I can load the modules without complaint, but can not use the device. I have tried everything obvious to fix it: reinstalling via module-assistant the ipw2200 and ieee80211 drivers, downgrading to old versions, manually installing from sources without module-assistant, disabling then re-enabling the adapter in the BIOS, etc. I have the 2.3 and 2.4 version firmware in the appropriate directory.

I was ready to dismiss this as a hardware problem, but when I boot up knoppix or suse-live-dvd, the wireless works consistently! ??? Odd that this suddenly break - I can not think of anything that triggered this, but I do "apt-get upgrade" approximately daily.

I'm running 2.6.14.6, but my 2.6.15.1 build also suddenly displays identical behavior... [[User:gsmenden|gsmenden]] 11:30, 30 January 2006 (EST)

--------------
Bizarre. Delving through the ipw2200-devel archives reveals several users having similar non-detection issues due to trouble loading the firmware. In the /etc/hotplug area one person solved a similar issue by removing firmware.agent file, which did not work for me.

I decided to completely remove the hotplug system

: apt-get remove --purge hotplug

followed by re-apt-getting hotplug. Voila, everything works as before. Sometimes Debian sid is as flaky as a baklava - an ill-timed "apt-get upgrade" can effectively destroy your system when running unstable, yet "stable" is far, far too behind the times for me... :(

[[User:gsmenden|gsmenden]] 13:55, 30 January 2006 (EST)

== Enhanced power saving with set_power 5 ==

Using "set_power 5" instead of "set_power 7" reduces power consumption in idle times (i.e. no network traffic) by about 1.5 watts on my T43, which is pretty good if you just want to keep your irc or im client running. Does anyone have a clue why that happens? Are there any drawbacks to this? --B.Steinbrink (23:55, 1 December 2006 (CET))

Odd. The only difference between 7 (which is the same as 3, BTW), and 5 is the timeouts; on an idle connection, the radio will be turned off most of the time with both of these. And 1.5W is roughly the full difference between radio on and radio off. Maybe you have some regular event kicking in at just the right intervals to make a difference. --[[User:Thinker|Thinker]] 00:43, 2 December 2006 (CET)

Yeah, I saw 7 being the same as 3, that's why I tried 5. But with the first bigger download I noticed that my connection speed dropped along with the power consumption. I only got 64kbit/s out of the 1MBit/s the DSL line I'm currently using can shuffle around, switching back to 7 made the speed jump up to about 950kbit/s again. So that regular event kicking in was pretty important it seems ;) --B.Steinbrink 01:55, 2 December 2006 (CET)

== Correct!? path? ==
Why /usr/lib/hotplug/firmware is better than /lib/firmware? Hotplug is deprecated, so is /usr/lib/hotplug/firmware.
--[[User:Zhenech|Zhenech]] 09:19, 8 February 2007 (CET)

I have no idea, as firmware in /usr will be unavailable during early boot if /usr is a separate partition... in fact, I'd say it was a Bad Idea to use /usr/<anything>/firmware in the first place.

I have added /lib/firmware back. Anyone that can actually read and follow instructions, either Intel's or the ones in the rest of the page, won't need that comment, anyway.
--[[User:Hmh|hmh]] 12:36, 8 February 2007 (CET)

User talk:VincentP

2005-10-17T13:15:39Z

VincentP:

I've got a Thinkpad X41, running debian unstable...
Most thinks works allright, but it lacks some improvement to be comfortably usable.
Thanks ThinkWiki contributors for your great knowledge resource !

How to make use of Dynamic Frequency Scaling

2005-10-16T23:04:47Z

VincentP: Debian way of setting sysfs values at boottime.

==General==
Linux supports dynamic frequency scaling for systems with the following processors:

*Mobile Pentium III
*Pentium 4
*Pentium M
*Mobile Athlon
*AMD64
*Opteron

==Debian notes==
Instead of compiling your own kernel, you can use the {{Debian}} "stock" kernel. In Unstable/SID the 2.6.12 kernel image with an {{path|/etc/modules}} file that includes:

battery
ac
thermal
processor
acpi-cpufreq
cpufreq-userspace

With the powernowd package and you should be setup.

===Configuring the Kernel===
====2.4 Kernels====
There were various frequency scaling implementations in the 2.4 series of kernels. They all were preliminary and a standard was rised with the introduction of the sysfs filesystem in 2.6 kernels. It is recommended to use a 2.6 kernel, if possible.

====2.6 Kernels====
You need to enable the cpu frequency scaling for your kernel (usually your distros kernel will have this enabled):
:{{kernelconf|CONFIG_CPU_FREQ|<*>|||||}}

You need to enable governors, if not already done in your distros default kernel:
:{{kernelconf|CONFIG_CPU_FREQ_GOV_PERFORMANCE|<*>|||||}}
:{{kernelconf|CONFIG_CPU_FREQ_GOV_POWERSAVE|<*>|||||}}
:{{kernelconf|CONFIG_CPU_FREQ_GOV_USERSPACE|<*>|||||}}

Since 2.6.10 there is the ondemand governor that does cpu frequency scaling in kernel so you dont need userspace programs like powernowd etc.
It can be enabled with:
:{{kernelconf|CONFIG_CPU_FREQ_GOV_ONDEMAND|<*>|||||}}

Since 2.6.12 there is the conservative governor that works like the ondemand governor, but is recommended for laptops and AMD64:
:{{kernelconf|CONFIG_CPU_FREQ_GOV_CONSERVATIVE|<*>|||||}}

==Using the Sys Interface==

The files in {{path|/sys/devices/system/cpu/cpu0/cpufreq/}} provide information and a means of controlling the frequency scaling subsystem.
Seed values are given in Khz. You need to be root to access the /sys filesystem.

Your max speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}
:{{cmdresult|700000}}
Your min speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}
:{{cmdresult|500000}}
If you are using the userspace governor, you can write to {{path|/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}} to change the current speed.
:{{cmdroot|echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 697.252}}
:{{cmdroot|echo 900000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 976.152}}

==Using Frequency Scaling Governors==
You can compile the scaling governors into your kernel or compile it as module. You'll find the governors with 'make menuconfig' here:
:{{kernelconf||| |CPU Frequency scaling|Power management options (ACPI, APM)|||}}

After booting the new kernel you can get a list of available governors with (as root):
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors}}
:{{cmdresult|conservative ondemand powersave userspace performance}}

A Short Overview over the available governors:
:;ondemand
::This driver is a dynamic cpufreq policy governor. It changes frequency based on the processor load.
:;conservative
::New since 2.6.12. Similar to ''ondemand''. Optimized for battery powered environments and AMD64.
:;powersave
::Like the name says, your battery would choose this one ;). It sets the Frequency always to the lowest available.
:;userspace
::You have to choose this one, if a [[#Using Frequency Scaling Daemons|frequency scaling daemon]] should manage your CPU frequency or you want to do it manually.
:;performance
::This governor sets your Frequency always to the highest available.

Now we set our governor:
What is our current governor?
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|userspace}}
Set new governor and watch if it has changed
:{{cmdroot|echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|conservative}}

Congrats! Your governor is active.

You may set the governor in your rc.local, to make it used on every boot.

Debian has no rc.local, so read [http://www.debian.org/doc/FAQ/ch-customizing.en.html#s-custombootscripts this] and [http://www.debian.org/doc/FAQ/ch-customizing.en.html#s-booting this].

A better alternative for Debian than modifying bootscripts, is to install the [http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&version=all&exact=1&keywords=sysfsutils sysfsutils package]. Then edit /etc/sysfs.conf (as root), where you can setup values to sysfs entries that you want to be modified automatically on boot.

==Using Frequency Scaling Daemons==
{{NOTE|It is recommended to use the ondemand frequency scaling governor, available in kernels from 2.6.10. See [[#Using Frequency Scaling Governors|above]]. If you do this you do not need a frequency scaling daemon}}

Don't forget to enable the userspace governor to have a userspace daemon do the frequency scaling. If it is built as module, load it as <tt>cpufreq-userspace</tt>.

There are plenty of userspace frequency scaling daemons available:

*[[How to configure cpufreqd | cpufreqd]]
*[[How to configure cpudynd | cpudynd]]
*[[How to configure speedfreqd | speedfreqd]]
*[[How to configure powersaved | powersaved]]
*[[How to configure powernowd | powernowd]]
*[[How to use cpufrequtils | cpufrequtils]]

==Troubleshooting==
*If you have a Coppermine-piix-smi based Thinkpads like from the A2x, X2x and T2x series you need to enable the <tt>speedstep-ich</tt> driver in the kernel and load it if it's built as module. You might want to look at [[How to get SpeedStep working on Coppermine-piix4-smi based Thinkpads | this page]].

*If you have a p4-class celeron based Thinkpad like the R40e you might want to look at [[How to get SpeedStep working on P4-class-Celeron based Thinkpads | this page]]

[[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:i1200]] [[Category:i1300]] [[Category:i1620]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:TransNote]]