Difference between revisions of "Installing Ubuntu 7.10 (Gutsy Gibbon) Tribe 4 on a ThinkPad T61"

From ThinkWiki
Jump to: navigation, search
(Video)
Line 1: Line 1:
 
'''Some of this is copied verbatim from [https://bugs.launchpad.net/ubuntu/+bug/131406 my bug report #131406]''' Other bits were taken from the [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_Tribe_3_on_a_ThinkPad_T61 Tribe 3 instructions].
 
'''Some of this is copied verbatim from [https://bugs.launchpad.net/ubuntu/+bug/131406 my bug report #131406]''' Other bits were taken from the [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_Tribe_3_on_a_ThinkPad_T61 Tribe 3 instructions].
 +
 +
Please see the discussion section for discussion on merging this with the Tribe 3 article.
  
 
== Initial Install ==
 
== Initial Install ==

Revision as of 01:46, 11 August 2007

Some of this is copied verbatim from my bug report #131406 Other bits were taken from the Tribe 3 instructions.

Please see the discussion section for discussion on merging this with the Tribe 3 article.

Initial Install

Issue #1: The initial install from the live CD graphical installer does not work if the laptop is in SATA AHCI mode. You have to go into the BIOS and set the SATA controller to "Compatibility" mode or else you get a "can't access tty" error. After Ubuntu is intalled and you've done an "apt-get update" you can -- and should -- set the controller back to AHCI mode.

Issue #2: The initial install from the live CD graphical installer hangs with a blank tan screen after gdm loads. It is clear that gdm is running, but the desktop never actually loads. The solution is to:

  1. switch to a console (Ctrl-Alt-F1)
  2. type "sudo bash"
  3. type "killall gdm"
  4. type "/etc/init.d/gdm start"

Note that typing "/etc/init.d/gdm stop" does not work for step 3 -- you must run "killall gdm".

Video

Intel:

At higher resolutions, the gnome toolbars function in a smaller area than the rest of the desktop. This is because the TV output is turned on. If you see the login screen show up in the top-left corner of the screen, taking up only 2/3 of the screen, then you have this issue and you'll need to disable the TV output.

To turn the TV output off and fix the small desktop issue, add the following section in /etc/X11/xorg.conf.

 Section "Monitor"
   Identifier "TVOutput"
   Option "Disable" "true"
 EndSection

and then in the Device Section, add the option:

 Option "monitor-TV" "TVOutput"

Reference: [1]

Nvidia:

If you would like 3D acceleration then you must download and install the proprietary drivers from Nvidia here: http://www.nvidia.com/object/unix.html

To install these drivers:

  1. install build-essentials from Synaptic
  2. Download the drivers from the link above to your home directory
  3. When the download completes hit Ctrl-ALT-F1 to drop to a console.
  4. Login and type:
    1. sudo /etc/init.d/gdm stop
    2. sudo sh NVIDIA-Linux-x86-100.14.11-pkg1.run

If the file you download is newer that 100.14.11 make sure you modify the command appropriately

When asked, permit the installer to modify xorg.conf

Reboot: # sudo shutdown -r now

NOTE!
With each new Kernel release this process must be repeated except you should tell the installer to not update xorg.conf

Audio

Audio does not work out of the box. You need to download and compile ALSA from CVS

Bugs

Font Issues on High-Res Screens: On high-res screens (15" 1680x1050), the default fonts are too bold above 8 or 9px (the exact number depends on the font). I have not heard people with normal-resolution screens complaining about this. You can easily see this by running gnome-specimen and gradually stepping up the font size. At some point (usually around 8-9px) the font will turn bold.

Suspend/Hibernate: Suspend has major problems. Suspend-to-disk always hangs, and the only suspend-to-ram command I've gotten to work at all is "s2ram -f -a1". About half the time s2ram never resumes, and usually when it fails to resume it just shows a blank console with "Linux!" written in the upper left. However, even when it does resume to the desktop, it invariably does something very odd: It *loses* a processor and a half. Before running s2ram you can do a "cat /proc/cpuinfo" and see two processors running at ~1800MHz, but after resuming from a s2ram, the same command will only show a single processor running at ~900MHz, and any further suspends will completely hang the system. Very bizarre.

Console Switching: After a while of running in X mode, it becomes impossible to switch to a console and see anything. I've not figured out any pattern here, but this is what eventually happens after a few hours: You do a Ctrl-Alt-F1 (or F2 or whatever) to go from X to a console, and all you see is a blank screen. The console is actually there and running -- you just cannot see it. You can log in blind and type commands into the console and they'll run just find; you just cannot see what you're doing.

T61