https://www.thinkwiki.org/w/api.php?action=feedcontributions&user=Rlcomstock3&feedformat=atomThinkWiki - User contributions [en]2024-03-29T16:02:01ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=Talk:Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61&diff=37492Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T612008-04-28T23:13:14Z<p>Rlcomstock3: /* Nvidia */</p>
<hr />
<div>==Nvidia==<br />
<br />
Would it be possible to clean up the "How to Suspend with nVidia 140m/570m" section? I was going to do it but after reading through i realized that my knowledge was too limited to do it well. but i think it could serously benifit from a good cleaning!<br />
<br />
<br />
When trying to do anything with Twinview in fullscreen mode will cause it to span both monitors instead of just being on the second. This essencially kills the functionality of twinview.<br />
<br />
eg 1 --> you are an office working bringing your notebook to work to show a presentation but you can't use full screen.<br />
<br />
eg 2 --> you want take your notebook to a friends house to watch a movie on his/her projector and fullscreen mode gets half displayed on the projector and half on the notebook monitor.<br />
<br />
FIX for Twinview problem: After changing settings in nvidia-settings save them to the x config file, restart x and fullscreen will only fill the monitor you are in.<br />
<br />
Has anyone found a fix for this? <br />
<br />
Does the Ubuntu wiki <https://help.ubuntu.com/community/NvidiaTVOut> work?<br />
What adjustments are needed for Gutsy and NVIDIA Quadro NVS 140M?<br />
Is it hotpluggable --like Twinview using 'nvidia-settings'?<br />
<br />
Is it possible toset this up in Applications->System Tools->Nvidia Settings?<br />
<br />
When i use Twinview with diffenent sizes of screens in 'clone' mode it crops my screen to match the smaller one. This makes my monitor pretty much useless. How do I get 'clone' to stretch (or shrink) instead of crop?<br />
<br />
==Microphone==<br />
<br />
<br />
This discussion was going on in the wiki and seems a bit confusing. If possible I think we should get a consensus on the problem (if it still exists as of the final release) and solutions. --[[User:Darrena|Darrena]] 18:19, 21 October 2007 (UTC)<br />
<br />
This problem does still exist. <br />
<br />
There are multiple fixes because the GUI can be a bit confusing and the microphone can be configured to work in multilple ways.<br />
<br />
**If the microphone section was confusing it should have been cleaned up not removed! <br />
<br />
---<br />
<br />
We should focus on providing clear instructions in the article and not provide a dumping ground for various thoughts and ideas. Everyone should certainly share what worked for them no matter how complicated but all of that should happen in the talk page so less technical users are not confused by the instructions. So far one person has said that their mic worked out of the box on a Beta install. Notice that the change I made was to point to the talk page so that the information was not lost but it made people aware that the various items are still being looked at. Personally I have never been able to get the mic to work with sound recorder but it seems to work fine with Ekiga once I set the default source via alsamixer. Also I think that recommending that people switch to OSS from alsa is going to cause even more confusion among less experienced users. In general sound is in poor shape right now but we can all hope that Pulseaudio will resolve this in time for 8.10. My suggestion would be to instruct users how to select the default source in alsamixer and then all apps that use Alsa /should/ work. I tested with Ekiga, Wengophone and Skype (Shudder!) and those seem to be the important apps to people. So if most people agree then I will write up a quick description of setting the default source in alsamixer and unmuting the mic. I don't care which solution we present but it should be as simple as possible and not require users to make changes beyond the initial setup and using ALSA seems to meet that requirement IMO. --[[User:Darrena|Darrena]] 18:19, 21 October 2007 (UTC)<br />
<br />
<br />
'''Attn:''' Microphone (both internal and external) seems to be working for me with all applications after applying all updates (No need to change device to OSS) Make sure the relevant things (internal microphone, mic boost) etc aren't muted either in alsamixer or gnome-volume-control. <br />
<br />
Microphone may not work with applications (like sound recorder and skype) even though sound can be heard through the speakers or headphones. If you have success in using the built in microphone please update this section.<br />
<br />
<br />
It worked for me after i followed the instructions in this thread for ALSA<br />
http://ubuntuforums.org/showthread.php?p=2635174#post2635174<br />
<br />
I had to tick the following tracks to make my mic work in Sound Recorder<br />
PCM, Microphone, Capture, Capture1, Input Source, Input Source, Internal Mic, Speaker.<br />
<br />
For those that find the above instructions vague:<br />
<br />
The whole 'Volume Control Center' could be better labelled but here is what i believe to be true: <br />
the microphone will work but only through the OSS mixer. the ALSA mixer is what causes the listed problem (not working with applications like skype) but the sound quality of alsa mixer is far better than the OSS mixer and it would be much more convenient to control so it would be hugely beneficial to get it working. Nonetheless here are more detailed instructions for getting sound working.<br />
<br />
In the Playback tab you should have PCM, which is the only important one. If you have anything else there you should mute them. [On an X61 at least under playback was the option 'internal mic', unmute that and max it out, mute internal mic boost, make sure capture one is about 70% and thats all it took to get mine working]<br />
<br />
In the 'recording' tab should be 'Capture' and 'Capture 1'(if they aren't you have to check them in Edit-->Preferences) 'Capture' controls the volume for the ALSA mic input and 'Capture 1' controls the volume for the OSS mic input. Mute 'Capture' and increase the volume of 'Capture 1'<br />
<br />
The 'switches' tab should be as you set it up in the audio section of this wiki. headphones [check] and speakers [check].<br />
<br />
The options tab (which i haven't quite figured out) should have a list of two 'Input Sources' I have mine set to 'Internal Mic' on the top and 'Mic' on the bottom. i don't know if that is correct but it is working for me.<br />
<br />
Now go to File-->Change Device--> Analog Devices (OSS Mixer)<br />
You should see a 'Playback' tab with 'Microphone', 'PCM-2' and 'In-gain'.<br />
If you do not see these then open Edit-->Preferences and select them.<br />
Place your microphone volume at your desired level (mine is at about 7/8ths) and mute it when you are not using it, otherwise you get the crackle. The 'PCM-2' seems to only go fully up or fully down, i leave it fully up. I haven't figured out what effect the 'In-gain' has yet. (you'll be the first to know when i do)<br />
<br />
This should give you the ability to record sound or skype but it is tedious as you will have to mute and unmute the microphone in the Analog Devices OSS area. Maybe there is a way to simplfy this method but i haven't found it. Hopefully soon recording with the ALSA mixer will work.<br />
<br />
<br />
== Core 2 Duo running at 800 mHz? ==<br />
The applications Sysinfo and PowerTOP both say that my CPU is running at 800 MHz. When I first open Sysinfo, it says a number around 2 GHz but it then drops to 800 MHz. Sysinfo says something about laptop CPU frequency changing (being "dynamic"), but it remains static at 800 MHz. [[User:SteveSims|SteveSims]] 00:51, 13 September 2007 (UTC)<br />
<br />
<br />
This is normal. This is the "frequency scaling" feature of the laptop. Whenever the processors aren't being used they drop down to 800MHz to conserve power. All you have to do is run some CPU-intensive task and you'll see them jump up to 2GHz. There's a little applet that you can add to the top panel called "CPU Frequency Scaling Monitor" that will let you watch the processor speed up and down in real time: Right-click on the top panel bar and select "Add to Panel" to find it; it's under "System and Hardware" --[[User:Mike Richards|Mike Richards]] 06:31, 13 September 2007 (UTC)<br />
<br />
<br />
==Desktop_Applet crash on login after update (2007-09-16) with x86 and AMD64 versions (Fixed in daily build 20070918, reappears in 20070919.1)==<br />
I found out that my Thinkpad T61 is a 64-bit machine so I installed the 64-bit version of Ubuntu 7.10 Tribe 5. I tried updating the machine, which worked fine until it had to configure and install my updates. With about 12 minutes remaining it hangs up and the terminal within the Update Manager says that some components must be restarted (and the update hangs) so I restart my computer. When I log in, I get an error message that says something about a Deskbar_Applet not working, and it asks me if I want to delete it. Regardless of my selection, I can no longer update the machine nor run Applications --> Add/Remove. I thought it must be a difference between AMD64 and Intel's x86-64 near-clone, so I re-installed the 32-bit version. When I updated, the same thing happened after I updated it. I'm guessing this is a bug withing the [http://en.wikipedia.org/wiki/GUI GUI] or the package manager.<br />
<br />
However, I can load Firefox from my panel just fine. [[User:SteveSims|SteveSims]] 05:01, 17 September 2007 (UTC)<br />
<br />
:I had a similar problem. I found if I just avoided updating the system until after a full reboot, things were fine. [[User:Rybu|Rybu]]<br />
<br />
::The most recent update (9-18-2007) solves this problem.<br />
<br />
:::The problem appears again in 20070919.1, at least the AMD64 version (I haven't tested the x86-32 version). [[User:SteveSims|SteveSims]] 21:49, 19 September 2007 (UTC)<br />
<br />
::::And it still exists as of September 20th. [[User:SteveSims|SteveSims]] 04:53, 21 September 2007 (UTC)<br />
<br />
==Touchpad issues==<br />
After updating on September 18th from the original x86 Tribe 5, tapping the touchpad hard no longer clicks, and the right edge no longer scrolls. [[User:SteveSims|SteveSims]] 01:59, 19 September 2007 (UTC)<br />
:Go to System -> Preferences -> Mouse. In the Touchpad tab you can activate tap to click and vertical scrolling. --[[User:Aerials|aerials]] 13:05, 21 September 2007 (UTC)<br />
<br />
<br />
My touch pad is overly sensitive --sometimes opening applications or documents as I attempt to pass the pointer over their icon. I have tried adjusting it in the Prefs-->Mouse.<br />
Are there any other ways to adjust the sensitivity?<br />
Do others have this issue?<br />
<br />
I don't have this issue but I have seen similar issues before on other distros, have you tried installing gsynaptic and see if editing the sensitivity there works? --[[User:Darrena|Darrena]] 01:29, 29 October 2007 (UTC)<br />
<br />
Disabling "vertical scrolling" solved my erratic/over-sensitive touchpad.<br />
<br />
==Daily build 20070918 AMD64 won't install==<br />
Double-clicking on the Install icon in the LiveCD does nothing. No window loads, I can't install it from the LiveCD. [[User:SteveSims|SteveSims]] 01:59, 19 September 2007 (UTC)<br />
<br />
==Volume/Sound Buttons==<br />
<br />
In Kubuntu 7.10 beta work mute button but anything display on screen/desktop. When I press the volume up button, on the screen display a window and always write 11%, and the volume not hight (if mute is on then mute disabled). When I press the volume down button display 0% but the volume not down.<br />
<br />
When the mute is enabled the kmix not display mute. [[User:Fitopaldi|Fitopaldi]]<br />
<br />
If add this lines to ''~/.kde/share/config/khotkeysrc'' the volume up button and volume down button works perfectly with kmix with DCOP.<br />
<br />
[Data_4]<br />
Comment=<br />
DataCount=2<br />
Enabled=true<br />
Name=Thinkpad<br />
SystemGroup=0<br />
Type=ACTION_DATA_GROUP<br />
<br />
[Data_4Conditions]<br />
Comment=<br />
ConditionsCount=0<br />
<br />
[Data_4_1]<br />
Comment=<br />
Enabled=true<br />
Name=Volume up<br />
Type=DCOP_SHORTCUT_ACTION_DATA<br />
<br />
[Data_4_1Actions]<br />
ActionsCount=1<br />
<br />
[Data_4_1Actions0]<br />
Arguments=1<br />
Call=increaseVolume<br />
RemoteApp=kmix<br />
RemoteObj=Mixer0<br />
Type=DCOP<br />
<br />
[Data_4_1Conditions]<br />
Comment=<br />
ConditionsCount=0<br />
<br />
[Data_4_1Triggers]<br />
Comment=Simple_action<br />
TriggersCount=1<br />
<br />
[Data_4_1Triggers0]<br />
Key=XF86AudioRaiseVolume<br />
Type=SHORTCUT<br />
<br />
[Data_4_2]<br />
Comment=<br />
Enabled=true<br />
Name=Volume down<br />
Type=DCOP_SHORTCUT_ACTION_DATA<br />
<br />
[Data_4_2Actions]<br />
ActionsCount=1<br />
<br />
[Data_4_2Actions0]<br />
Arguments=1<br />
Call=decreaseVolume<br />
RemoteApp=kmix<br />
RemoteObj=Mixer0<br />
Type=DCOP<br />
<br />
[Data_4_2Conditions]<br />
Comment=<br />
ConditionsCount=0<br />
<br />
[Data_4_2Triggers]<br />
Comment=Simple_action<br />
TriggersCount=1<br />
<br />
[Data_4_2Triggers0]<br />
Key=XF86AudioLowerVolume<br />
Type=SHORTCUT<br />
<br />
But this is a temporal solution. ;) With this solution not work the volume info screen. [[User:Fitopaldi|Fitopaldi]]<br />
<br />
Don't know if this is of any interest: under Kubuntu 7.04 with the kernel from Gutsy the volume up/down buttons worked for me. --[[User:Rawk|Rawk]] 18:48, 23 October 2007 (UTC)<br />
<br />
==Brightness buttons==<br />
<br />
The brightness buttons used to work on my system. But now that I have 2 displays, they don't work anymore. When I first installed Ubuntu 7.10 the brightness buttons did not work but I found some tips on-line to enable them... unfortunately I don't remember what those tips were... silly me... I'll dig up the info and put it into the wiki, soon. [[User:Rybu|Rybu]]<br />
<br />
In Kubuntu Gutsy don't work anymore. When I first installed Kubuntu 7.10 (tribe 5) yes work on console screen, but later the first update not work this. (NVIDIA GPU) [[User:Fitopaldi|Fitopaldi]]<br />
<br />
<br />
I had the same problem and fixed it this way:<br />
Edit {{path|/etc/acpi/thinkpad-brightness-up.sh}} and insert before <code><pre>exit</pre></code> (line 5) this:<br />
<code><pre>echo 4 > /proc/acpi/ibm/cmos</pre></code><br />
Do the same with {{path|/etc/acpi/thinkpad-brightness-down.sh}} using <code><pre>echo 5 > /proc/acpi/ibm/cmos</pre></code><br />
The module thinkpad_acpi has to be loaded, but I think it's done automaticaly. If you use echo up/down > /proc/acpi/ibm/brightness it's not possible to use all levels (bug in thinkpad_acpi?). [[User:Rawk|Rawk]] 17:06, 17 November 2007 (UTC)<br />
<br />
==Compiling existing information==<br />
<br />
This [[http://gentoo-wiki.com/HARDWARE_Lenovo_Thinkpad_T61]] link has some useful information that is worthwhile compiling into the wiki here. [[User:Rybu|Rybu]]<br />
<br />
==Desktop effects don't consistenly work==<br />
I installed new themes and updated today and suddenly the new desktop effects that were added to 7.10 don't work.<br />
<br />
However, Deskbar_Applet doesn't crash with the update, even though it does with today's most current LiveCD. [[User:SteveSims|SteveSims]] 06:37, 21 September 2007 (UTC)<br />
<br />
==NetworkManger Intermittently Fails To Start, No Networking When It Fails==<br />
After the most recent Kernel patch under Gutsy, NetworkManager doesn't always manage to run when I boot, and when it fails I have no networking. If I try init.d/networking restart, it fails with 'unknown device' for all devices. Looking through the logs, my best guess is ath0 isn't ready when NetworkManager starts, so it starts cycling through other devices until it crashes. Does anyone have any ideas? It seems to only work about 1-2 boots out of 10.<br />
<br />
==I installed libdvdcss2, but DVD playback still doesn't work==<br />
I have all the GStreamer plugins. When I insert a DVD movie, Movie Player loads and I hear sound but there's no video. If I try to open a video from a location, I get this dialog box:<br><br />
[[Image:totem no plugins.png|300px]]<br />
<br />
:I always like the idea of using GStreamer instead of Xine, but the fact is, I've never really gotten DVDs to work very well without installing totem-xine. Maybe you don't want to do that, but if you haven't tried it, consider installing totem-xine? --[[User:Plumpy|Plumpy]] 23:32, 25 September 2007 (UTC)<br />
<br />
:::Here's what I get when I install totem-xine from Synaptic:<br />
<br />
:::[[Image:Totem-xine_no_DVD_playback.png]]<br>[[User:SteveSims|SteveSims]] 00:32, 26 September 2007 (UTC)<br />
<br />
:::::I decided to install some more xine plugins but now Totem closes immediately after opening if I insert a DVD. Here's a log of my xine package installations:<br />
<pre>Commit Log for Tue Sep 25 17:25:49 2007<br />
<br />
<br />
Installed the following packages:<br />
libxine1-console (1.1.7-1ubuntu1)<br />
libxine1-gnome (1.1.7-1ubuntu1)<br />
libxine1-plugins (1.1.7-1ubuntu1)<br />
<br />
Commit Log for Tue Sep 25 17:23:33 2007<br />
<br />
<br />
Installed the following packages:<br />
libpostproc1d (3:0.cvs20070307-5ubuntu4)<br />
libxine1-ffmpeg (1.1.7-1ubuntu1)<br />
<br />
Commit Log for Tue Sep 25 17:14:25 2007<br />
<br />
<br />
Removed the following packages:<br />
totem-gstreamer<br />
<br />
Installed the following packages:<br />
libmodplug0c2 (1:0.7-5.2ubuntu1)<br />
libpulse0 (0.9.6-1ubuntu2)<br />
libxcb-shape0 (1.0-3)<br />
libxcb-shm0 (1.0-3)<br />
libxcb-xv0 (1.0-3)<br />
libxcb1 (1.0-3)<br />
libxine1 (1.1.7-1ubuntu1)<br />
libxvmc1 (2:1.0.4-2ubuntu1)<br />
totem-xine (2.20.0-0ubuntu1)<br />
</pre><br />
<br />
== x86 vs 64bit on core 2 duo ==<br />
<br />
What to choose? Why, why not?<br />
<br />
: In my case, I've installed the 64bit kernel. I develop some of my own software which has a fair amount of optimizations with the 64-bit architecture. [[User:Rybu|Rybu]]<br />
<br />
:: 64-bit will run faster. I say install the AMD64 version. Don't let your new, fast 64-bit processor go to waste! [[User:SteveSims|SteveSims]] 06:16, 5 October 2007 (UTC)<br />
<br />
== Black screen at boot ==<br />
<br />
When try to boot gutsy-desktop-amd64 the screen turns black, even when i use "Safe Graphics" mode. Having a nVIDIA Quadro NVS 140M card<br />
<br />
TURNS OUT I JUST NEED PATIENCE... sorry [[User:Zpon|Zpon]]<br />
<br />
: Was doing a re-install, and got the problem again, have waited a loong time... [[User:Zpon|Zpon]] 09:58, 5 November 2007 (UTC)<br />
<br />
I'm having a similar problem myself, except it started doing this only recently. Ubuntu will boot into low-graphics mode at first( and it will go through a bit of trouble to do that much, but then once it's up and running it seems to run fine. Here's a string of what the boot-up looks like. With the exception of the dialogue( second to last frame) I can just leave it and it'll boot, but it's still frustrating...<br />
http://www.thinkwiki.org/wiki/Image:Ubuntu_T61_Boot_Errors.png<br />
Gah, I don't know how to make it show up as a thumbnail. Sorry.<br />
<br />
The problem should be fixed now https://bugs.launchpad.net/bugs/147623 [[User:Zpon|Zpon]]<br />
<br />
=== Still annoying ===<br />
<br />
I still have this problem at boot up. I also have the nVIDIA card, and I get black screen instead of the splash screen. X eventually comes up, but I'd love to know how to fix this.<br />
<br />
--Do you have 'vga=' enabled as a kernel parameter? If yes then remove that.<br />
:I do not have 'vga=' but it still takes _very_ long time to boot and with a black screen (I also have a black screen when I am booting after successful installation)<br />
<br />
The problem should be fixed now https://bugs.launchpad.net/bugs/147623 [[User:Zpon|Zpon]]<br />
<br />
==Update 2007-10-11 works fine==<br />
Announcement. [[User:SteveSims|SteveSims]] 05:15, 11 October 2007 (UTC)<br />
<br />
== Power Consumption ==<br />
<br />
I have enabled laptop-mode (level 2) and also used PowerTOP to optimize the power consumption of my T61 with NVIDIA 140M. <br />
But even though the brightness is set at minimum the power consumption just does not want to drop below 19W.<br />
Is this a usual behaviour?<br />
<br />
I used to get much lower power utilization but now I am seeing the same thing you do. I plan on doing some deeper looks soon and see why this change.<br />
<br />
== Most programs won't install in the 10-18 install of AMD64 version; probably not a 64-bit issue ==<br />
<br />
I tried installing the GStreamer plugins, VLC Media Player, and KolourPaint (a KDE application) from Add/Remove Programs and it told me the following:<br />
<br />
<pre>Cannot install 'kolourpaint'<br />
<br />
This application conflicts with other installed software. To install 'kolourpaint' the conflicting software must be removed first.<br />
<br />
Switch to the 'synaptic' package manager to resolve this conflict.</pre><br />
<br />
I tried to install these programs/plugins one at a time, and got the same message (albeit with 'vlc', etc. instead of 'kolourpaint').<br />
<br />
Of course, I don't know which packages conflict with them, so I can't use Synaptic to remove the conflicting packages. It did, however, successfully install Sysinfo. I went to Synaptic and found that there were no KDE packages installed. [[User:SteveSims|SteveSims]] 23:28, 19 October 2007 (UTC)<br />
<br />
I just ran sudo apt-get update and I still can't install these things.<br />
<br />
I also tried to install Battle for Wesnoth (at least the wesnoth-all package) and was told that it has unresolvable dependencies. "Depends: wesnoth but it is not going to be installed" and the same thing for about 9 or so other packages. [[User:SteveSims|SteveSims]] 23:53, 19 October 2007 (UTC)<br />
<br />
== Networking craps out == <br />
<br />
The network on my T61 with Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61) card occasionally just goes away. If I <br />
<br />
modprobe -r iwl4965<br />
modprobe iwl4965<br />
/etc/init.d/networking restart<br />
<br />
it will come back, but this is annoying. Anybody have any ideas here?<br />
<br />
<br />
There was a similar problem with an old version of wpa_supplicant a month ago but a fix has existed since Tribe 5. Can you post the relevent messages from /var/log/messages and /var/log/syslog? --[[User:Darrena|Darrena]] 12:00, 20 October 2007 (UTC)<br />
: Logs /var/log/syslog http://pastebin.com/f29dcfc97 and /var/log/messages http://pastebin.com/m2a4e601b - hope this will help track down the problem...<br />
: I get the same problems, several times a day, very annoying [[User:Zpon|Zpon]] 09:58, 5 November 2007 (UTC)<br />
<br />
== Rotate Display when docked ==<br />
<br />
I have a Thinkpad T61 running Windows Vista Ultimate (ick). I also have a minidock. Currently (when not crashing) I have it setup to use the wireless NIC when undocked. When I dock the laptop, it switches to the hardline NIC and rotates the display for my 19" portrait monitor. The resolution also changes, of course.<br />
<br />
Is this possible with Ubuntu (or any distro) or will I have to do some manual fiddling everytime I dock/undock?<br />
<br />
<br />
----<br />
Yes it is possible but the how depends on your video card. If it is the intel card you can use xrandr to create a script to set the video up exactly how you want it and then bind that to a key. --[[User:Darrena|Darrena]] 21:04, 18 November 2007 (UTC)<br />
<br />
== Bluetooth script error ==<br />
<br />
cat /proc/acpi/ibm/bluetooth | awk '{ print $2 }' | while read line;<br />
do<br />
if [ $line == "enabled" ]; then<br />
echo disable > /proc/acpi/ibm/bluetooth<br />
else<br />
echo enable > /proc/acpi/ibm/bluetooth<br />
fi<br />
break<br />
done<br />
<br />
should be:<br />
<br />
cat /proc/acpi/ibm/bluetooth | awk '{ print $2 }' | while read line;<br />
do<br />
if [ $line = "enabled" ]; then<br />
echo disable > /proc/acpi/ibm/bluetooth<br />
else<br />
echo enable > /proc/acpi/ibm/bluetooth<br />
fi<br />
break<br />
done<br />
<br />
right?<br />
<br />
==GM965 instead of X3100 Intel graphics?==<br />
My device manager shows this:<br><br />
[[Image:GM965_X3100.png|300px]]<br />
<br>The T61 should have an X3100, and both are integrated onto the motherboard, so is Linux treating my X3100 like a GM965?<br />
<br />
== Fn+F5 does not work by default ==<br />
<br />
I have a 7664-18G with Bluetooth Version 2.0 + EDR, Intel 4965AGN. Using the script provided I can start Bluetooth, and wifi works also (without anything), but I can not use the function button to switch off/on wifi and/or bluetooth.<br />
<br />
Could someone help me fixing this? [[User:Nagyv|Nagyv]] 10:47, 9 January 2008 (CET)<br />
<br />
== Hibernate ==<br />
<br />
Has anyone gotten hibernate (suspend to disk) to work yet? The hibernation part seems to go fine, but upon waking the screen is striped with colors and unresponsive.</div>Rlcomstock3https://www.thinkwiki.org/w/index.php?title=Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61&diff=37491Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T612008-04-28T19:36:55Z<p>Rlcomstock3: /* Nvidia N140m: */</p>
<hr />
<div>==Introduction==<br />
<br />
This document outlines configuring Ubuntu 7.10 (Gutsy Gibbon) on your Thinkpad T61. Most items will work out of the box and a base install should provide you with a completely working system. Due to the modular nature of the T61 there are many different configuration, please read carefully and only make the changes specific to your system. <br />
<br />
Feel free to update this Wiki with your information however please ask questions on the Talk page.<br />
<br />
==Installation Notes ==<br />
<br />
*If booting with the live CD gives you a blank screen you should select the "Safe Graphics" menu choice.<br />
<br />
== Display/Video ==<br />
<br />
=== Accelerated Video and Desktop Effects ===<br />
'''Intel''' 2D and 3D accelerated video work out of the box.<br />
<br />
Due to [https://bugs.launchpad.net/xorg-server/+bug/111257 | bug 111257], compiz is disabled on the Intel i965 based video cards. All systems updated after 11/24/2007 should be fixed.<br />
<br />
'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager {{NOTE| If the Restricted Drivers Manager fails to install the driver you can use the Envy tool from: http://albertomilone.com/nvidia_scripts1.html. This tool is unsupported and the only supported method of installing the Nvidia drivers is via Synaptics and the Restricted Drivers Manager}}<br />
<br />
===Multiple Monitors===<br />
<br />
If you previously used Xinerama this is no longer a supported option, you should use one of the tools described below to configure dual displays.<br />
<br />
====Nvidia N140m:====<br />
<br />
When using the default drivers (The open source "nv" drivers) you can use Administration->"Screens and Graphics" to setup the second monitor<br />
<br />
Using the proprietary drivers you must use the Nvidia tool located at Applications->System Tools-> Nvidia X Server Settings. <br />
<br />
Note: <br />
Twinview 'works' but doing anything with Twinview in fullscreen mode will cause it to span both monitors instead of just being on the second. This essencially kills the functionality of Twinview.<br />
<br />
eg 1 --> you are an office working bringing your notebook to work to show a presentation but you can't use full screen.<br />
<br />
eg 2 --> you want take your notebook to a friends house to watch a movie on his/her projector and fullscreen mode gets half displayed on the projector and half on the notebook monitor. <br />
<br />
To resolve the full screen issue:<br />
<br />
After setting up Twinview with the second monitor save the configuration to your x config file, then restart x. Log in again and now when you fullscreen it will only span the one monitor that the window is in not both. The other screen will be available for other use. You can drag between windows and then fullscreen to fill only the monitor you are in. Tested on T61 using Ubuntu 7.10 with gMPlayer in full screen mode and open office impressions slide show. (Movies and Presentations)<br />
<br />
<br />
If you experience problems getting a working Twinview setup using nvidia-settings, please see [http://www.nvnews.net/vbulletin/showthread.php?t=101780 this thread]<br />
<br />
==== Intel GM965/GL960 ====<br />
If you experience a blank screen and perpetual gui reset when using heavy GLX (3D) applications such as scorched3d, try upgrading to the hardy 2.6.24-3 kernel along with the matching modules:<br />
<br />
add these 2 lines to /etc/apt/sources.list:<br />
deb http://us.archive.ubuntu.com/ubuntu/ hardy main restricted<br />
deb-src http://us.archive.ubuntu.com/ubuntu/ hardy restricted main multiverse universe <br />
run: <br />
sudo apt-get update<br />
sudo apt-get install linux-restricted-modules-2.6.24-3-generic linux-image-2.6.24-3-generic linux-ubuntu-modules-2.6.24-3-generic<br />
<br />
Comment out the 2 new lines from sources.list (put a # in front) and run apt-get update again.<br />
<br />
reboot.<br />
<br />
IMPORTANT: You must comment out the lines from sources.list and run apt-get update again, or you will auto-upgrade to hardy which you do not want to do yet!<br />
<br />
NOTE: the 2.6.24 kernel uses the new fully open iwl3945 driver for wifi, instead of the old restricted ipw3945. you may need to tweak your wifi settings after rebooting.<br />
<br />
====Intel X3100====<br />
<br />
Plugging in an external monitor works, but is a clone of the built-in LCD by default. Using the Screens and Graphics tool located under Administration you can setup the second monitor as an extension of the existing screen or a clone for presentations, but it does not let you enable a second display on a second monitor.<br />
<br />
'''Setting up dual monitors via the command line'''<br />
<br />
If you like doing it via the command line and are using the Intel drivers or the open-source "nv" driver you can use this example (''Note all this should be possible using the Screens and Graphics tool so only make this change if you prefer the command line method''):<br />
<br />
This is an example for a 1680x1050 built-in LCD and a 1600x1200 external LCD:<br />
Add a "Virtual 3280 1200" line in the Display SubSection of the Screen Section in your xorg.conf:<br />
<br />
Go to Applications -> Accessories -> Terminal and type the following:<br />
<br />
{{cmdroot|sudo /etc/init.d/gdm stop}}<br />
<br />
{{cmdroot|xrandr --output LVDS --auto}}<br />
<br />
To set the built-in LCD to ouput 1680x1050<br />
<br />
{{cmdroot|xrandr --output VGA --right-of LVDS}}<br />
<br />
To extend the desktop<br />
<br />
To enable Compiz Fusion. refer to http://temporaryland.wordpress.com/2007/12/06/finding-the-right-distro-for-my-thinkpad-followup/ and follow the instructions as per for Linux Mint 4.0.<br />
<br />
=== Fonts on High-Res Screens ===<br />
<br />
On high-res screens (e.g. 15" 1680x1050), some users consider the default fonts too be too large ([https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/99145 Launchpad bug report]). You can fix this by following these steps:<br />
<br />
# Open System->Preferences->Appearance<br />
# Select the "Fonts" tab<br />
# Click the "Details" button (lower right)<br />
# Adjust the Resolution down to 96dpi<br />
# Make sure you have Subpixel (LCD) Smoothing enabled<br />
# Save the preferences<br />
<br />
If you also want small fonts on the GDM login window, you can do this:<br />
<br />
# Open System->Administration->Login Window<br />
# Select the 'Security' tab<br />
# Click the 'Configure X-Server' button<br />
# Append '-dpi 96' (without quotes) to the text in the 'Command' field<br />
# Reboot the computer.<br />
<br />
=== Brightness ===<br />
====Intel X3100:====<br />
The brightness controls should work out of the box on a fresh install.<br />
<br />
====Nvidia Quadro N140 and 570M:====<br />
With Nvidia Driver 169.07 (2007/12/20) the brightness controls work properly on a Thinkpad T61 with Nvidia Quadro NVS 140M. Please see the section above on installing drivers with the Envy tool above.<br />
<br />
Previous Driver:<br />
The brightness controls do not work out of the box, however you can switch to a virtual terminal (ctrl+alt+F1) increase or decrease the brightness and then switch back to X (ctrl+alt+F7) without disrupting the running applications (You should save anything open just to be safe). There is a new from nvidia that fixes the brightness-controls. To install this driver use the Envy tool described above.<br />
<br />
If brightness buttons do not work (after installing the latest nvidia drivers) you can edit /etc/acpi/thinkpad-brightness-up.sh and /etc/acpi/thinkpad-brightness-down.sh:<br />
<br />
Add this line before "exit" in {{path|/etc/acpi/thinkpad-brightness-up.sh}}<br />
echo 4 > /proc/acpi/ibm/cmos<br />
<br />
Also insert this line before "exit" in {{path|/etc/acpi/thinkpad-brightness-down.sh}}<br />
echo 5 > /proc/acpi/ibm/cmos<br />
<br />
== Audio ==<br />
<br />
=== Inextricably Linked to the Modem ===<br />
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover that your audio is also disabled. In this situation, your drivers may still load, but you will get an error message whenever you try to play audio.<br />
<br />
===Enabling Audio controls===<br />
<br />
By default, the sound may be disabled and the volume control buttons on the laptop (up by the ThinkVantage button) and the volume control applet (up by the clock) will not control the speaker volume (they actually control the microphone). To fix this:<br />
<br />
# Right-click on the volume control applet (by the clock) and select "Open Volume Control"<br />
# In the "Switches" tab, make sure "Headphone" and "Speaker" are both checked.<br />
# Close the Volume control.<br />
# Right-click on the volume control applet again and select "Preferences".<br />
# Make sure the device is set to "HDA Intel (Alsa mixer)" and highlight the "PCM" option.<br />
# Close the preferences.<br />
# Select System->Preferences->Sound.<br />
# In the "Default Mixer Tracks" section, make sure "PCM" is highlighted.<br />
# Close the sound preferences.<br />
<br />
You should now hear sound and be able to control the volume using the laptop buttons or volume applet.<br />
<br />
A recent BIOS update [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989] fixes the mute button, you can then configure it to mute/unmute audio in Keyboard Shortcuts.<br />
<br />
===Microphone===<br />
The internal microphone is considered a generic capture source and is muted by default. To unmute the microphone:<br />
<br />
*Right Click on the volume icon next to the clock and click on "Open Volume Control"<br />
<br />
*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):<br />
Internal Mic<br />
Input Source<br />
Capture<br />
<br />
*Click Close and there should be two additional tabs "Recording" and "Options". - <br />
<br />
*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it. <br />
<br />
*Click Options and under capture source select internal mic (This step may not be necessary).<br />
<br />
To test your mic using Sound Recorder select Capture as the sound source.<br />
<br />
This solution has been tested with Sound Recorder, Akiga, Skype, and OpenWengo.<br />
<br />
===Sound Cracking===<br />
<br />
There have been intermittent reports of users experiencing cracking when listening to audio. Here are a few possible solutions:<br />
<br />
* Try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)<br />
<br />
* If this issue is only occurring for Rhythmbox go to Edit > Preferences > Playback > and Check "Use Crossfading Backend". Restart Rhythmbox and you should have better audio quality.<br />
<br />
* Check that the microphone is muted and modify your mixer settings by moving items like PCM down halfway and see if the cracking goes away.<br />
<br />
===Hissing===<br />
Some users experience hissing during playback, and even when idle. To solve this mute the microphone when it is not in use:<br />
<br />
# Run "alsamixer" in the terminal.<br />
# Arrow over to "Mic", and hit "M" to mute.<br />
# Arrow over to the first "Docking", and hit "M" to mute.<br />
# Arrow to the first "Internal", and hit "M" to mute.<br />
<br />
Now, make sure that "Headphone" and/or "Speaker" are _not_ muted, and that "PCM" is at a reasonable level (say ~70) so you don't make your ears bleed, and try playing something back. ''(<Esc> will exit alsamixer)''<br />
<br />
== Modem ==<br />
<br />
The modem works with the Linuxant drivers available at http://www.linuxant.com<br />
<br />
==Bluetooth== <br />
Bluetooth works out of the box. Pressing Fn-F5 once will enable bluetooth, disable wireless, pressing again, enable both and pressing one more time will disable bluetooth. <br />
<br />
If you would like to set bluetooth state independently the script below determines the current bluetooth state and toggles the device on or off. <br />
<br />
First create a new file named bluetooth-toggle:<br />
{{cmdroot|sudo touch /usr/sbin/bluetooth-toggle}}<br />
<br />
Now open a editor:<br />
{{cmdroot|sudo gedit /usr/sbin/bluetooth-toggle}}<br />
<br />
Paste the following script:<br />
<br />
#!/bin/bash<br />
cat /proc/acpi/ibm/bluetooth | awk '{ print $2 }' | while read line;<br />
do<br />
if [ $line == "enabled" ]; then<br />
echo disable > /proc/acpi/ibm/bluetooth<br />
else<br />
echo enable > /proc/acpi/ibm/bluetooth<br />
fi<br />
break<br />
done<br />
<br />
Now set the execute permissions: <br />
{{cmdroot|sudo chmod +x /usr/sbin/bluetooth-toggle}}<br />
<br />
You can invoke the script out of the console by typing sudo bluetooth-toggle or create a menu icon by using the menu editor under preferences using gksudo bluetooth-toggle as command line.<br />
<br />
<thinkwiki></thinkwiki><br />
== Fingerprint Reader ==<br />
<br />
The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here] and [https://wiki.ubuntu.com/ThinkFinger here].<br />
Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger<br />
<br />
Note that ThinkFinger in it's current version does not work with KDE and Kubuntu in any way (it crashes KDM and is not integrated at all).<br />
<br />
Prebuilt packages are available from jldugger using Launchpad's PPA:<br />
<br />
Add the thinkfinger package repository by creating {{path|/etc/apt/sources.list.d/thinkfinger.list}} with these two lines:<br />
<br />
deb http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse<br />
deb-src http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse<br />
<br />
Then update the package database and install packages:<br />
<br />
{{cmduser|sudo apt-get update}}<br />
{{cmduser|sudo apt-get install libpam-thinkfinger libthinkfinger-dev libthinkfinger-doc libthinkfinger0 thinkfinger-tools}}<br />
<br />
After the package is installed edit {{path|/etc/pam.d/common-auth}} and replace the line<br />
<br />
auth required pam_unix.so nullok_secure<br />
<br />
with<br />
<br />
auth sufficient pam_thinkfinger.so<br />
auth required pam_unix.so try_first_pass nullok_secure<br />
<br />
Edit {{path|/etc/modules}} and add the following line:<br />
<br />
uinput<br />
<br />
Load the module manually for this session:<br />
<br />
{{cmduser| sudo modprobe uinput}}<br />
<br />
Summary:<br />
* Recording fingerprints works<br />
* Login works<br />
* The password must be entered to unlock a locked screensaver<br />
* sudo works<br />
* gksu and gksudo hang : for example it is necessary to run synaptic twice and enter your password upon failure. To be able to use the Finger print reader in the session subsequently, kill the hanging gksu/gksudo process. A workaround is editing the Gnome System Menu (alacarte) to specify sudo instead of gksu/gksudo for the launching command and choose type "Application in Terminal" : this opens an extra terminal window for each superuser application you want to use though.<br />
<br />
== Trackpad scrolling ==<br />
<br />
Trackpad scrolling works out of the box in the standard thinkpad way: Slide your finger up and down the very right edge of the trackpad.<br />
Note that /etc/X11/xorg.conf will be changed and the edge scrolling will be disabled after running nvidia-xconfig , copy the trackpad section from the backup of xorg.conf<br />
<br />
To enable using the middle mouse button to scroll, add the following lines to the "Configured Mouse" section in<br />
{{path|/etc/X11/xorg.conf}}:<br />
<br />
Option "EmulateWheel" "true"<br />
Option "EmulateWheelButton" "2"<br />
<br />
== Hibernate/Suspend ==<br />
<br />
=== Blank screen fix for intel graphics cards===<br />
<br />
This fix is for Intel Graphics Cards only.<br />
<br />
When resuming from suspend or hibernate, the screen will be black until you switch to a console (ex: Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). To fix this, open (as sudo) <b>/etc/default/acpi-support</b> and find the line:<br />
<br />
<pre># DOUBLE_CONSOLE_SWITCH=true</pre><br />
<br />
uncomment it so that it says:<br />
<br />
<pre>DOUBLE_CONSOLE_SWITCH=true</pre><br />
<br />
and then save and close the file. You may then reboot or just restart ACPI:<br />
<br />
<pre>sudo /etc/init.d/acpi-support restart<br />
sudo /etc/init.d/acpid restart</pre><br />
<br />
afterward, the screen should come back properly on resume.<br />
<br />
This seem to enable painless suspend/resume for T61 with Intel graphics for most people, but on my newer (April 08) ThinkPad T61 suspend/resume continues to be somewhat unstable: resuming sometimes takes very long time, and I am unable to switch to text console after resume with Ctrl+Alt+F1. To fix that, I had to add <b>acpi_sleep=s2_bios</b> kernel parameter to <b>/boot/grub/menu.lst</b><br />
<br />
=== How to Suspend with nVidia 140m/570m ===<br />
<br />
The suspend to RAM will work with the nVidia card and the proprietary drivers, but it requires some file editing. It did not work for me out of the box. Using the package manager, download and install the latest nVidia drivers (100.14.19+2.6.2.4-12.4 at time of writing). I also had to use the 2.6.22-12-generic kernel image (the 2.6.22-13 image did not work with this driver --- I'm assuming it has to match wit the nVidia version, but I am not an expert).<br />
<br />
Once you have it installed and working, you have to make a change to {{path|/etc/default/acpi-support}}. Open the file in your favorite editor and change the following lines:<br />
<br />
$ sudo nano /etc/default/acpi-support<br />
<br />
{{path|/etc/default/acpi-support}}<br />
# Should we save and restore state using the VESA BIOS Extensions?<br />
SAVE_VBE_STATE=false<br />
...<br />
# Should we attempt to warm-boot the video hardware on resume?<br />
POST_VIDEO=false<br />
...<br />
# Set the following to "platform" if you want to use ACPI to shut down<br />
# your machine on hibernation<br />
HIBERNATE_MODE=platform<br />
<br />
<br />
This allowed me to suspend and resume, but after two suspends the wireless wouldn't work anymore. Theoretically, ACPI unloads the network drivers before suspending, but it doesn't seem to work correctly so I added these to the blacklist modules manually (in the same file as above:<br />
<br />
{{path|/etc/default/acpi-support}}<br />
# Add modules to this list to have them removed before suspend and reloaded<br />
# on resume. An example would be MODULES="em8300 yenta_socket"<br />
#<br />
# Note that network cards and USB controllers will automatically be unloaded <br />
# unless they're listed in MODULES_WHITELIST<br />
MODULES="iwl4965 iwlwifi_mac80211 cfg80211"<br />
<br />
Your wifi modules may be different. (I have the intel AGN wireless card -- I don't know if these modules are different for other cards.)<br />
<br />
Add the s3_mode option to kernel boot parameters (according to [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/139089 Launchpad BUG 139089])<br />
<br />
{{path|/boot/grub/menu.lst}}<br />
## Add acpi_sleep=s3_mode to kernel boot parameters<br />
# defoptions=quiet splash acpi_sleep=s3_mode<br />
<br />
Rebuild menu.lst using<br />
<br />
<pre>$ sudo update-grub</pre><br />
<br />
Remove hibernate and uswsusp packages in case they are installed<br />
<br />
<pre>$ sudo apt-get remove hibernate uswsusp --purge</pre><br />
<br />
This allows me to suspend to ram; I haven't had any problems with it so far. I haven't gotten hibernate (suspend to disk) working, so there may be additional things you need to do for that. (I think part of my problem is that I don't have enough swap, but I don't care enough to actually fix it.)<br />
<br />
If the system has been left in suspend off for a while, wireless might not reconnect at all (Thinkpad T61 8892-02U). Restarting netapplet <br />
solves the problem.<br />
<br />
{{path|/etc/default/acpi-support}}<br />
# Add services to this list to stop them before suspend and restart them in <br />
# the resume process.<br />
STOP_SERVICES="netapplet"<br />
<br />
<br />
Running both the ACPI daemon and the APM daemon may also cause problems. You may disable the APM daemon by going to the System->Administration->Services. Enter your password if prompted then uncheck "Power Management (apmd)". The service will be disabled the next time you boot your computer.<br />
<br />
You may also stop the service manually:<br />
<pre>$ sudo /etc/init.d/apmd stop </pre><br />
<br />
''' The fix does not work for me '''<br />
<br />
I have a T61 7664-17U(NVS 140m, 4965agn). The computers suspend, but when it wakes up it hangs up and I have to pull out the battery to restart it. -- also not with s3_mode?<br />
<br />
If your screen is black but you can still reboot with ctrl+alt+delete your system resumes but the nvidia graphics chip does not. In this case the following may help (At least for me with T61 6460):<br />
<br />
{{path|/etc/default/acpi-support}}<br />
SAVE_VIDEO_PCI_STATE=true<br />
<br />
== Items that work out of the box ==<br />
<br />
'''Intel Video:''' 2D and 3D acceleration works<br />
<br />
'''Nvidia:''' 2D works, 3D requires the installation of the proprietary drivers<br />
<br />
'''Wireless:''' Atheros and Intel cards both tested.<br />
<br />
'''Bluetooth:''' Tested with both a bluetooth headset and an HTC 8525<br />
<br />
'''Network Card''' Intel 10/100/1000 tested<br />
<br />
'''Firewire''' Tested with hard drive<br />
<br />
'''Wireless switch''' <br />
<br />
'''4-in-1 card reader'''<br />
<br />
'''Webcam'''<br />
<br />
'''Headphones''' You may need to enable Headphone out: Right-click on the volume control and select open volume control. Click the switches tab and then check the headphones box.<br />
<br />
'''Keyboard Shortcuts:'''<br />
* Fn-PgUp activates/deactivates the thinklight<br />
* Fn-Up will trigger stop on a media player<br />
* Fn-Down will toggle pause and play on a media player<br />
* Fn-Left/Right go to prev/next tracks on a media player<br />
* Fn-F2 properly locks the screen<br />
* Fn-F3 shows remaining battery >>does not work on all machines<<<br />
* Fn-F4 suspends (to ram)<br />
* Fn-F12 hibernates (to disk)<br />
* PrtSc opens the screenshot dialog<br />
<br />
'''Docking Stations:'''<br />
<br />
All docking station models should work and the following features have been tested:<br />
<br />
* DVI or Analog video: You can switch to it using "Administration->Screens and Graphics", if you are using the proprietary Nvidia drivers you must use the Nvidia Control Panel.<br />
<br />
* Network Pass-through<br />
<br />
* Modem Pass-through<br />
<br />
* USB ports: Connected upon docking<br />
<br />
* PS/2 Ports<br />
<br />
== Items that don't work ==<br />
<br />
=== Interrupt problem (PROBABLY SOLVED) ===<br />
This bug is supposed to be solved by updating the system BIOS to the [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989 2.09]-Version (with 1.08 AMT). Still testing...<br />
* https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369<br />
* USB ports can end up temporarily disabled<br />
* Wifi can break<br />
* integrated cardreader can be disabled<br />
* bluetooth can be disabled<br />
* Setting IRQ's to "Auto" from factory default of "11" in the BIOS seems to help some people.<br />
* The two USB ports on the left side of the computer may fail to connect storage devices during a session but will load them at boot up. (SOLVED! with BIOS update 2.09)<br />
* booting with the "irqpoll" option seems to work for some people against the problem that usb-ports stop working.<br />
* GLX (3d graphics) on intel 965 video card is broken: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/120834 (SOLVED! - see section above)<br />
<br />
=== Wireless activity LED ===<br />
<br />
The LED is not implemented in either the IWL4965 or Atheros drivers.<br />
<br />
patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.<br />
<br />
== Power consumption ==<br />
<br />
Gutsy is the first version of Ubuntu to feature a tickless kernel (i386 only, not in AMD64 yet). Power consumption<br />
can be monitored using the powertop tool under Ubuntu and using Lenovo battery monitor<br />
under Windows.<br />
<br />
$ sudo apt-get install powertop<br />
$ sudo powertop<br />
<br />
I couldn't find any difference in power consumption between the i386 tickless kernel (even with 70ms average sleep in C4)<br />
and AMD64 kernel (2ms average sleep in C4). It would be expected that considerably less power would be consumed for the <br />
i386 tickless kernel.<br />
<br />
There is also a graph available by Right-clicking on the battery icon and selecting Power History.<br />
<br />
These are the figures measured on a T61 15.4" 1680x1050 screen 7300 processor (2GHz) 2GB RAM, Intel X3100 graphics<br />
with 4965 wifi, Bluetooth and UWB.<br />
<br />
{| border=1 cellpadding=5<br />
|- <br />
| 12.3W<br />
| Windows XP Pro, all radios on, about 50% brightness<br />
|-<br />
| 16.7W<br />
| Gutsy, all radios on, 50% brightness<br />
|-<br />
| 19.6W<br />
| Gutsy, all radios on, 100% brightness<br />
|-<br />
| 14.2W<br />
| Gutsy, all radios on, 10% brightness<br />
|-<br />
| -1.0W<br />
| Turning the physical radio switch to off on the front reduces power consumption by 1 watt.<br />
|}<br />
<br />
<br />
Adding the Nvidia card increases the laptops power requirements.<br />
<br />
These are the figures measured on a T61 14" 1440x900 screen 2.2ghz Core2Duo 2GB RAM, Nvidia 140m video, IWL4965 wifi and Bluetooth (Disabled):<br />
<br />
{| border=1 cellpadding=5<br />
|-<br />
| 18.3W<br />
| Gutsy, all radios on, 50% brightness<br />
|-<br />
| 19.4W<br />
| Gutsy, all radios on, 100% brightness<br />
|-<br />
| 16.0W<br />
| Gutsy, all radios on, 10% brightness<br />
|-<br />
|}<br />
<br />
== See also ==<br />
* [[Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61]]<br />
<br />
[[Category: T61]] [[Category: Ubuntu 7.10]]</div>Rlcomstock3