Computer freezes during boot and during viafb loading
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DeviceMatic |
Invalid
|
Undecided
|
Unassigned | ||
Linux |
Confirmed
|
Undecided
|
Unassigned | ||
base-installer |
Invalid
|
Undecided
|
Unassigned | ||
initramfs-tools |
Invalid
|
Undecided
|
Unassigned | ||
ubiquity |
Invalid
|
Undecided
|
Unassigned | ||
xsplash |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
In Progress
|
High
|
Leann Ogasawara | ||
module-init-tools (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Starting a Lucid Live Session, or trying to load viafb module from a Karmic Session, both make the computer completely freeze:
- The screen goes black, but not off.
- The cooler turns on indefinitely (suggesting strong cpu activity).
- The keyboard locks (the user can't even turn on/off capslock or numlock).
It seems that there won't be a fix for this kernel module any soon.
So far there are two possible workarounds for this:
* With a Live CD, remove "quiet splash" and add "viafb.modeset=0" to the boot options.
* Create a Live USB with persisten memory, boot it on another computer and add viafb to the kernel module blacklist.
It is a regression from Karmic. (Not that viafb works on Karmic, but it is not loaded there by default.)
description: | updated |
description: | updated |
affects: | ubuntu → gworkspace (Ubuntu) |
summary: |
- Lucid Alpha 3 Live session gives blank screen and freezes + Lucid Alpha 3 installation CD gives blank screen and freezes |
tags: | added: kernel-series-unknown |
tags: | added: default-application regression-potential |
tags: | added: karmic |
tags: | removed: kernel-series-unknown |
description: | updated |
summary: |
- Lucid Beta 1 installation CD gives blank screen and freezes + Computer freezes during boot and during viafb loading |
tags: | added: iso-testing |
description: | updated |
affects: | gdm → devicematic |
Changed in linux: | |
status: | New → Confirmed |
Please do not just click "Also affects" on a bunch of random projects. I'm going to mark them all invalid and reassign to (guessing) the kernel in Ubuntu, although it may be an X bug instead.