Xorg freeze after installing 11.04 x64 on Toshiba Satellite A305

[Amit Kotlovski]

I used to have an older version of Ubuntu installed (I think 9.04) and wanted to check 11.04.
I installed using the liveCD while erasing the old installation.

At first the liveCD could not finish boot, ending up with a black screen.
Then I started passing the following boot parameters, which allowed it to open the desktop environment:
acpi=off
noapic
nolapic
nodmraid
nomodtest

I used it to install 11.04 on my hard drive.

Since then, I cannot boot into the ubuntu partition. Neither the normal, nor the rescue option finish boot successfully.

I booted into the liveCD again, chrooted to my hard drive, and ran apt-get update && apt-get upgrade, but it didn't help.

When the computer is stuck during boot, it gives me a black screen, and responds to nothing. No option to get to console, and Caps Lock light isn't responding.

I ran the `ubuntu-bug` utility for sending this bug report on the liveCD, as I currently can't start from the hard drive partition, so I guess it's xorg logs won't show why it couldn't load on the other partition.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xorg 1:7.6+4ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Jul 26 06:16:02 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
GdmLog1:

GdmLog2:

GraphicsCard:
 ATI Technologies Inc Mobility Radeon HD 3400 Series [1002:95c4] (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Device [1179:ff1e]
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: TOSHIBA Satellite A305
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- acpi=off noapic nolapic nodmraid nomodeset
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/24/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.70
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr1.70:bd11/24/2008:svnTOSHIBA:pnSatelliteA305:pvrPSAGCU-05601S:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite A305
dmi.product.version: PSAGCU-05601S
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

[Alex Stek (alaska-alex)]

I'm installing 11.04 AMD 64 Desktop on a Satellite A305-S6898, and am experiencing the same bug. If I specify nomodeset in the boot options in GRUB, it seems to boot fine.

[Amit Kotlovski (amitbk)]

adding nomodeset to the kernel options solved this problem for me too.

See also https://answers.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+question/167307

[Bryce Harrington (bryce)]

Hey amitbk,

You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.

If it's solved in the new release and you think it's worth backporting
the fix, please indicate that. Or if having the fix in the new release
is good enough, feel free to close out the bug (or let us know and we'll
close it.)

If it's not solved, leave the bug report open. I can't promise we'll
get to it (we get way more bugs filed than we can usually get to), but
your testing and feedback can help out if and when we do.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.