Installed Gutsy can not boot on Santa Rosa

Bug #153823 reported by Xiaoyang Yu
14
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Hardware:
Lenovo ThinkPad T61

Software:
Gutsy alternate amd64 daily build on 2007/10/16.

Bug description:
Gutsy alternate amd64 CD can be installed on T61. But when boot the installed system, it can not boot up properly. Instead, it recommend to use "irqpoll" as the boot option, and entered "BusyBox" interface after a while.

It can boot properly if using the "irqpoll" boot option.

description: updated
Revision history for this message
Matt Zimmerman (mdz) wrote :

My T61 is working fine with kernel 2.6.22-12.36-generic (32-bit). I haven't tried 64-bit on it.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Hi, thanks for reporting. Unfortunately this comes ust a few days too late to be fixed for the 7.10 ISO images, which will be released in a few hours. Since bthere is a work-around, this cannot be considered release-critical. The T61s are reported to work well with the i386 install also.

I've milestones it for gutsy updates.

Could you please attach the information requested on https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks!

Revision history for this message
Xiaoyang Yu (xiaoyang-yu) wrote : RE: [Bug 153823] Re: Installed Gutsy can not boot on Santa Rosa

Thanks for the feedback.

I found that setting the SATA Controller Mode to "Compatibility mode"
instead of "AHCI mode" can solve this problem.

So I will mark this bug as "invalid".

Changed in linux-source-2.6.22:
status: Incomplete → Invalid
Revision history for this message
Xiaoyang Yu (xiaoyang-yu) wrote :

Thanks for the information.

BTW, have you see the following bug on your T61?

Visual Effects can not be enabled on Santa Rosa
https://bugs.launchpad.net/bugs/153818

Revision history for this message
berg (berg-foss) wrote :

if the problem (bug) exists , then its needs a solution.
this workaround is a instantaneous relief but Many other people can be affected by this bug and will don't know how to fix by workaround
and others can have a working system and someday change the emulation mode and receive a unbootable system and kick the Ubuntu :)
then this bug needs a permanent and automatic fix

Changed in linux-source-2.6.22:
status: Invalid → New
Revision history for this message
Xiaoyang Yu (xiaoyang-yu) wrote :

I can not reproduce this bug easily. Looks like this bug may be caused by instable hardware. Let's see if others can also meet this issue.

Revision history for this message
Rolla Selbak (rolla-n-selbak) wrote :

I know that I've had to perform this workaround in the past (it's pretty well-documented on the web). I haven't tried with Gutsy Final, but will today, and report back...

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Rolla, any news with the 7.10 Gusty final release? I'm marking the status "Incomplete" for now and also dropping Importance to "Medium" because of the workaround mentioned. Thanks!

Changed in linux-source-2.6.22:
importance: High → Medium
status: New → Incomplete
Revision history for this message
Rolla Selbak (rolla-n-selbak) wrote :

Hi Leann, I just changed the tag from 'intel-critical' to 'intel-normal', because of the documented workaround, I think 'Medium' on launchpad is good...

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks Rolla. So I assume you still have to use the 'irqpoll' boot option workaround with the new 7.10 Gusty Gibbon release? Thanks!

Revision history for this message
Xiaoyang Yu (xiaoyang-yu) wrote :

I found a similar bug for ACPI, which is not fixed yet.

Kernel Bug Tracker Bug 8853:
irq NN: nobody cared on ThinkPad X61T,T61
http://bugzilla.kernel.org/show_bug.cgi?id=8853

Revision history for this message
Rolla Selbak (rolla-n-selbak) wrote :

I have tested with the new 7.10 Gutsy Gibbon release on my T61 with both i386 and ix86_64 (live-cd). The problem exists for me on both 'install' and 'boot-up'.

Install live-cd: I have to add the 'irqpoll' option _or_ in my BIOS config, switch from 'AHCI' to 'COMPATIBILITY' mode in the SATA config for the install to work.

Boot-up the installed OS: I have to change my BIOS config from 'AHCI' to 'Compatibility' mode in the SATA config. Using 'irqpoll' in the grub boot option seemed to work until I logged in. The gfx was acting erratically after I logged in via the Desktop gui, with the whole screen filled with underscores '_', although it seemed to function normally otherwise.

I didn't test with alternate, or use both 'irqpoll' and 'Compatibility' mode at the same time.

Changed in linux-source-2.6.22:
status: Incomplete → Triaged
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Rolla and Xiaoyang,

Can you guys comment if this is still an issue in the latest Hardy Alpha release? Thanks.

Changed in linux:
status: New → Incomplete
Changed in linux-source-2.6.22:
status: Triaged → Won't Fix
Revision history for this message
Kevin Wang (kevin-xuepu-wang) wrote :

No such issue with alpha5 on SantaRosa platform

Thanks
Kevin

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks Kevin. I'm marking this 'Fix Released' against Hardy. Just for future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thanks again for testing and the update!

Changed in linux:
status: Incomplete → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.