Ubuntu takes forever to install on a Toshiba NB 200

Bug #435257 reported by Marc Tardif
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu
Won't Fix
Undecided
Unassigned
linux (Ubuntu)
Expired
Low
Unassigned
Karmic
Won't Fix
Low
Unassigned
Lucid
Won't Fix
Low
Unassigned

Bug Description

I have been trying to install Karmic (20090917) over the network on a Toshiba NB 200. It was so slow that I left it running overnight and it's still not finished in the morning. The installation seems to be stuck at installing base packages. I am attaching the syslog from the installer environment for more information.

Tags: pcert
Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Marc,

Sorry I missed this one. It'll help in the future to make sure bugs are assigned to a specific package. For now I'm reassigning this from Ubuntu to the linux kernel package.

Is the system actually locked up at this point or just creeping along extremely slowly? I'm unfortunately not seeing any obvious error messages in the syslog attached. Would it be possible to access the machine in question and grab at least the full dmesg output (assuming the machine is not completely locked up). It might also help to see the output of ifconfig to see if there are any issues of dropped packets etc.

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joey Stanford (joey) wrote :

Confirmed for Alpha 6 on an NB205. The slow down for me was mirror selection and later. Unsure of the specific cause.

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

Just to add more info here. Since I was in Montreal this week I tested this exact system in the lab by installing Karmic Alpha6 manually from a LiveUSB. Installation succeeded in a normal time frame. I'm having Marc retest doing a netinstall while I'm still here to examine any issues if this reoccurs.

Revision history for this message
Antonio Sánchez (antoniosanchez) wrote :

Hi Marc, Leann, Joey,

We had a similar issue when we tryed to install Jaunty over the network, finally we found that is something related with the Atom power management.

Try to disable C-States of the Processor Power Management setup in BIOS.

Revision history for this message
Andy Whitcroft (apw) wrote :

@Leann -- if this is confirmed as always occuring on this laptop then it probabally deserves a release note entry. Also if there is a work around via BIOS we should confirm and document that.

Changed in linux (Ubuntu Karmic):
importance: Undecided → Low
milestone: none → karmic-updates
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

@Marc,

Can you confirm the workaround Antonio mentioned in comment #5?

Revision history for this message
bkrzem (bkrzem) wrote :

I can confirm that switching "Dynamic CPU Frequency Mode" from "Dynamic" to "Always Low" in BIOS makes installation process much faster. Tested on TOSHIBA NB200-N12 and Ubuntu 9.10 network installation from mini.iso image.
(thanks for the tip Antonio!)

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

I can reproduce the issue on a recent Lucid install (20100419.1), in both desktop and alternate.

It seems setting acpi=off as a kernel parameter for net boot is a valid workaround.

summary: - Karmic takes forever to install on a Toshiba NB 200
+ Ubuntu takes forever to install on a Toshiba NB 200
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :
Revision history for this message
Ameet Paranjape (ameetp) wrote :

Mathieu,

Do both acpi=off and the bios options work as workarounds in Lucid as well? I will write up the release note for this issue on Lucid after you reply. Thanks.

Changed in linux (Ubuntu Karmic):
milestone: karmic-updates → none
milestone: none → karmic-updates
Changed in linux (Ubuntu Lucid):
milestone: karmic-updates → lucid-updates
tags: added: patch
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Ameet, I confirm, the workarounds work on Lucid as well.

Also, I removed the patch tag, there is no patch attached to this bug.

tags: removed: patch
Revision history for this message
Ameet Paranjape (ameetp) wrote :

Proposed release note text:

"Depending on how your BIOS is configured, installation on a Toshiba NB 200* might take a long time. This can be worked around by switching "Dynamic CPU Frequency Mode" from "Dynamic" to "Always Low" in BIOS or setting acpi=off as a kernel parameter for net boot."

Ameet Paranjape (ameetp)
Changed in linux (Ubuntu Lucid):
status: Incomplete → Triaged
Revision history for this message
ZombieSnipe (zombiesnipe) wrote : RE: [Bug 435257] Re: Ubuntu takes forever to install on a Toshiba NB 200

I'm sorry for the delay, you have to install the Netbook remix on the Ubuntu website if you have a laptop version of the Toshiba NB 200.
_________________________________________________________________
Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1

Ameet Paranjape (ameetp)
Changed in linux (Ubuntu Karmic):
status: Incomplete → Triaged
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Changed in ubuntu-release-notes:
status: New → Confirmed
Revision history for this message
Herton R. Krzesinski (herton) wrote :

Does it still happen on latest kernels (Maverick, Natty)?

If yes, I suggest to test with these parameters given to the kernel, it may help narrow down the real issue:
processor.max_cstate=2
processor.max_cstate=1
processor.nocst

If C-states is the issue, probably one of them will workaround the problem. If is not a kernel bug, we can add a dmi blacklist entry to processor.

But as changing frequency setting in bios also worked, may be something is happening on pstates handling, so setting /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor to performance can make a difference too.

Andy Whitcroft (apw)
Changed in linux (Ubuntu):
milestone: lucid-updates → none
status: Triaged → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote : Closing unsupported series nomination.

This bug was nominated against a series that is no longer supported, ie karmic. The bug task representing the karmic nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Karmic):
status: Triaged → Won't Fix
Revision history for this message
Dave Walker (davewalker) wrote :

Marking the ubuntu-release-notes task as Invalid, as the release notes for Karmic have long passed.

Thanks.

Revision history for this message
Kate Stewart (kate.stewart) wrote :

Stale task, does not appear relevent to release note for precise. If problem still exists with precise, reopen and target specifically to precise.

Changed in ubuntu-release-notes:
status: Confirmed → Won't Fix
Revision history for this message
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in linux (Ubuntu Lucid):
status: Triaged → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.