Public bug reported:
Here is a long list of hardware-related bugs that affect Gutsy Tribe 4
x86_64 on a Thinkpad T61 with the following configuration:
- Intel GMA X3100 graphics
- Intel 3945 wireless
- 15" screen w/ 1680x1050 resolution
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 find tty" error. (After Ubuntu is intalled you can set the
controller back to AHCI mode.)
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 (a) switch to a
console (Ctrl-Alt-F1), (b) run "sudo bash", (c) type "killall gdm", and
(d) type "/etc/init.d/gdm start". Note that "/etc/init.d/gdm stop" does
not work for step (c) -- you have to run "killall gdm".
3. Default fonts are too bold above 8 or 9px (the exact number depends
on the font). This probably has something to do with the fact that this
is a high-resolution screen (129dpi) because I have not heard people
with normal-resolution screens complaining about it. 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.
4. 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.
5. 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.
If I come across more T61 hardware-related bugs I'll append them to this
entry.
** Affects: Ubuntu
Importance: Undecided
Status: New
--
Gutsy Tribe 4 x86_64 - Thinkpad T61 Bugs
https://bugs.launchpad.net/bugs/131406
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
