system don't loading with 2.6.32-21-generic

[Yuriy]

After I select in Grub menu 2.6.32-21-generic , Ubuntu logo appear and loading suspend (black screen). I can load system only with 2.6.32-21-generic (recovery mode) in low graphic. When I use 2.6.32-20-generic, system load normally, but after graphic crash.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: wildstorm 1278 F.... pulseaudio
BootDmesg:

CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with ALC202 at irq 17'
   Mixer name : 'Realtek ALC202 rev 0'
   Components : 'AC97a:414c4740'
   Controls : 37
   Simple ctrls : 23
Date: Sat Apr 24 09:47:59 2010
HibernationDevice: RESUME=UUID=5c4bb73d-b5f1-42b8-9d3b-c448ee106b8a
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 002: ID 09da:000a A4 Tech Co., Ltd Port Mouse
 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:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA Satellite 1135
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=436b6e88-992a-4e59-bafe-868529b21af0 ro single
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
WifiSyslog:
 Apr 24 09:40:25 antares NetworkManager: <info> (wlan0): supplicant connection state: completed -> group handshake
 Apr 24 09:40:25 antares NetworkManager: <info> (wlan0): supplicant connection state: group handshake -> completed
dmi.bios.date: 09/02/2003
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.70A
dmi.board.name: BTW30
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.70A:bd09/02/2003:svnTOSHIBA:pnSatellite1135:pvrPS113U-05X9YVB:rvnTOSHIBA:rnBTW30:rvrNull:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite 1135
dmi.product.version: PS113U-05X9YVB
dmi.sys.vendor: TOSHIBA

[Jeremy Foshee (jeremyfoshee)]

Hi Yuriy,

If you could also please 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.]

[Yuriy (wildstorm)]

I try kernel 2.6.34-999-generic, and now system loading normally but still can't detect graphic card, and proceed to low graphic mode.

[jyanek (yanekjg)]

I can confirm the same issue Yuriy is having. I have the same laptop system (TOSHIBA Satellite 1135), running 9.10 Release Candidate. The only way I can boot is if I either 1) use failsafe graphics, or 2), change my Xorg.conf file to use a "vesa" device instead of "intel". Using "intel" will stop the system load just after the UBUNTU graphic appears. Using "vesa" will allow boot to desktop; however, in low-graphics mode.

[Yuriy (wildstorm)]

Graphics working with 2.6.33-020633-generic

[Yuriy (wildstorm)]

I am very sorry, but i mistake about 2.6.33-020633-generic. Graphics work but still proceed to safe mode.

[jyanek (yanekjg)]

Working: Graphics work in 2.6.34-999_2.6.34-999.201004301209. Note that the VESA mode was not detected, so I completely removed the xorg.conf file. System booted up normally with no issues. Able to configure graphics, including effects.

[Yuriy (wildstorm)]

In 2.6.34-999_2.6.34-999.201005011008 graphics not working.

[jyanek (yanekjg)]

Yuriy -- Do you have an Xorg.conf file? When I deleted mine (renamed it), loading on the upstream worked fine (using the 4/30 build. I did not try the 5/01 build).

[Yuriy (wildstorm)]

I have not Xorg.conf file.

[jyanek (yanekjg)]

Working with upstream version 2.6.34-999.201005041005. I see that 2.6.32-22.33 is in the process of coming from the mainstream update manager. Once that fully is downloaded and installed, I will test this mainstream kernel.

Note that 2.6.34-999.201005041005 does pose some stability issues on this Toshiba (non-boot related); however, I presume it is due to other issues.

[jyanek (yanekjg)]

Does not work with mainstream 2.6.32-22.33 which was released today.

[penalvch (penalvch)]

Yuriy, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

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