livecd - fatal display problems unless acpi=off

[Ed Heil]

If I boot the Karmic Koala alpha 4 livecd without acpi=off, when the splash screen is supposed to appear, a bunch of vertical colored lines on a black background appear instead. This is true even if I boot into "safe graphics mode." I tried the other options under "Modes" and "Options" and unless I use acpi=off, I always get the vertical lines on a black background.

I was trying Karmic Koala in order to see if suspend to RAM (sleep) mode would work with it. I can't get sleep mode to work with Jaunty Jackalope, but it works with Hardy Heron.

ProblemType: Bug
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: I82801CAICH3 [Intel 82801CA-ICH3], device 0: Intel ICH [Intel 82801CA-ICH3]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3431 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801CAICH3'/'Intel 82801CA-ICH3 with CS4299 at irq 10'
   Mixer name : 'Cirrus Logic CS4299 rev 4'
   Components : 'AC97a:43525934'
   Controls : 36
   Simple ctrls : 22
Date: Sun Aug 30 15:56:38 2009
DistroRelease: Ubuntu 9.10
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090812.3)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: TOSHIBA Satellite 1200
Package: linux-image-2.6.31-5-generic 2.6.31-5.24
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- acpi=off
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-5-generic N/A
 linux-firmware 1.15
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-5-generic i686
dmi.bios.date: 07/09/2002
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.20
dmi.board.name: ATW05
dmi.board.vendor: TOSHIBA
dmi.board.version: Null
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV1.20:bd07/09/2002:svnTOSHIBA:pnSatellite1200:pvrPS120U-00DJX7:rvnTOSHIBA:rnATW05:rvrNull:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite 1200
dmi.product.version: PS120U-00DJX7
dmi.sys.vendor: TOSHIBA

[Jeremy Foshee (jeremyfoshee)]

Hi Ed,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 421532

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Ed Heil (edheil)]

The machine on which I reported this bug isn't working anymore, so I'm afraid I'm not able to provide any updates anymore.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]