Install Ubuntu Intrepid Ibex on a T61p

From ThinkWiki
Revision as of 18:34, 23 October 2008 by Gertvdijk (Talk | contribs) (←Created page with '=What works and what doesn't?= ==Working out-of-the-box== *Wireless (Intel 3945ABG or 4965AGN) **Only tested G mode *Wired LAN *Video (VESA) **Hardware Drivers panel offer...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

What works and what doesn't?

Working out-of-the-box

  • Wireless (Intel 3945ABG or 4965AGN)
    • Only tested G mode
  • Wired LAN
  • Video (VESA)
    • Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
  • Touchpoint and Trackpad
    • Including scroll at the right side of the pad by default.
  • Optical drive
    • Optiarc AD-7910A works fine with Brasero disc burning
      • Tested: CD-R, DVD+R
  • Sound card
  • SD/MMC Memory card reader (Ricoh)
    • Only tested SD (non-HC) cards. Didn't take locked (read-only) cards.
  • Control buttons/Hotkeys
    • Volume control buttons
    • Screen brightness control
    • Thinklight control
    • WLAN/BT/OFF toggle
    • Media player control
  • Some ACPI features
    • Battery status, power graphs and history
    • Lid states and events
    • Only tested with a single 6-cell battery
  • ACPI features
    • Suspend to RAM
    • Suspend to Disk (Hibernate) FINALLY!! Be patient, though.

(Small) Tweaks needed for...

  • Microphone/Sound In
    • Might need to be turned on in the mixer
    • Not yet in this howto
  • Choppy Compiz animations
    • NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

Small issues with...

  • The radio killswitch.
    • Bluetooth and WLAN are turned off properly when using the killswitch at the front, but WLAN (3945) doensn't come up when enabling or will only show Channel 1 APs. Reloading the iwl3945 module will sometimes solve the issue.
    • The soft-killswitch (Fn+F5) will only toggle Bluetooth instead of the four modes as in Hardy (BT+WLAN, BT, WLAN, ALL OFF).

Not working

  • Logging out or restarting X
    • With 177 version of the NVidia binary (restricted) graphics driver on a Quadro FX 570M.



This part is taken from Hardy installation instructions.

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choiche between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

This should also install the "NVidia X Server Settings" program in System --> Administration.

At the time of writing I am not able to restart X or log out from my GNOME session. X will fail to start and will eventually fall back to failsafe config (VESA drivers). This happens on my Quadro FX 570M and I'm not sure it is an issue of the new NVidia driver or the new version in Intrepid.

You should even install the binary NVidia driver if you won't use 3D acceleration because the open source nv driver will drain your battery much faster, because it doesn't support PowerMizer at all. This will keep the GPU in full speed all the time and will consume around 12 Watts more because of that (for the Quadro FX 570M), according to Powertop. That is 50% of the total usage!


Fix for choppy Compiz animations

From Compiz animations are choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:


while true; do
    powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`
    if [ $powerstate = "on-line"  ]; then
       nvidia-settings -q all > /dev/null
    sleep 25;

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:


killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

As far as I can see, the EDID misdetection bug is fixed in the 177 version of the NVidia binary driver.


Not able to restart X

This is quite an issue when you want to switch user or log out. I'm not able to trace down the problem, because the Xorg.0.log file doens't give any errors or hints. Surprisingly both Suspend to RAM and Suspend to Disk are not failing.--Gertvdijk 18:34, 23 October 2008 (CEST)

Radio Killswitch

Trace down this problem or look for bug report.

Information, not Ubuntu issues

Brightness control on battery power

By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, espected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to higher it when needed.