nomodeset prevents resume from suspend, but without it can not see logon screen

Bug #960920 reported by adam jvok
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

My laptop (a Panasonic CF-R4) was perfectly happy with 3.0.0.14-generic.

After the upgrade to 3.0.0.15-generic (and still with 3.0.0.16-generic), I never get to see the logon screen - instead the screen fills with multi coloured vertical lines.
Very pretty, but not a lot of use.
I can ssh to the box, so apart from the screen, it seems to be OK.

I can work around this by setting
GRUB_CMDLINE_LINUX="nomodeset"
in /etc/default/grub
and then
sudo update-grub

After that, I can boot and get the logon screen with no problems.

...BUT, with "nomodest" If I "suspend", then "resume" nolonger works - the screen just stays black, no sign of disk activity, not possible to ssh to the box.

Susepend/resume worked fine without nomdeset in 3.0.0.14-generic.

What I'd really like is:
1. Not to have to set "nomodeset".
2. To be able to suspend/resume normally.

Possibly related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/904569

Any ideas? Thanks.
---
.etc.asound.conf:
 pcm.pulse { type pulse }
 ctl.pulse { type pulse }
 pcm.!default { type pulse }
 ctl.!default { type pulse }
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', '/dev/snd/pcmC0D4p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with STAC9750,51 at irq 17'
   Mixer name : 'SigmaTel STAC9750,51'
   Components : 'AC97a:83847650'
   Controls : 31
   Simple ctrls : 21
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=a54b85f3-787f-44ec-be7c-f5dfa3cab64d
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Matsushita Electric Industrial Co.,Ltd. CF-R4JW4AXR
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_HK.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic root=UUID=8a102561-1df9-4676-b664-9229726a6d43 ro nomodeset quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-16-generic N/A
 linux-backports-modules-3.0.0-16-generic N/A
 linux-firmware 1.60
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: oneiric running-unity
Uname: Linux 3.0.0-16-generic i686
UpgradeStatus: Upgraded to oneiric on 2011-11-05 (136 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev pulse-access sambashare sudo vboxusers
dmi.bios.date: 12/21/2005
dmi.bios.vendor: Phoenix Technologies K.K.
dmi.bios.version: V3.00L10
dmi.board.name: CFR4-3
dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.board.version: 001
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.chassis.version: 001
dmi.modalias: dmi:bvnPhoenixTechnologiesK.K.:bvrV3.00L10:bd12/21/2005:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-R4JW4AXR:pvr003:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCFR4-3:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
dmi.product.name: CF-R4JW4AXR
dmi.product.version: 003
dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 960920

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

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

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
adam jvok (ajvok1) wrote : AcpiTables.txt

apport information

tags: added: apport-collected oneiric running-unity
description: updated
Revision history for this message
adam jvok (ajvok1) wrote : AlsaDevices.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : AplayDevices.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : ArecordDevices.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : BootDmesg.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : Card0.Codecs.codec97.0.ac97.0.0.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : Card0.Codecs.codec97.0.ac97.0.0.regs.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : CurrentDmesg.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : IwConfig.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : Lspci.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : PciMultimedia.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : ProcInterrupts.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : ProcModules.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : UdevDb.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : UdevLog.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote : WifiSyslog.txt

apport information

Revision history for this message
adam jvok (ajvok1) wrote :

Also worth noting: on a a different machine (a dell desktop running 3.0.0.16-generic - 64bit), if suspend/resume works just fine.
But after adding nomodeset to the boot parameters, resume nolonger works on this machine either.

I suspect that something is broken in 3.0.0.15 & 3.0.0.16 regarding nomoedeset and resume.

adam jvok (ajvok1)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
adam jvok (ajvok1) wrote :

Joseph - thanks for the suggestion.

Tested with 3.3.0-999-generic_3.3.0-999.201203210406_i386.deb

1. With nomodeset NOT given as a boot parameter:
- I nolonger get the multi coloured vertical lines and can get to the logon screen with no problem
- Suspend/resume works fine.

2. With nomodeset (which given the above result I would nolonger need to do anyway)
- I nolonger get the multi coloured vertical lines and can get to the logon screen with no problem
- Resume fails. Momentary disk activity, but blank screen, no repsonse to ssh.

So, it seems that my immedaite problem is fixed but that there is still an issue with nomodeset preventing resume working.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Herton R. Krzesinski (herton) wrote :

Do you still see the issue without nomodeset and the kernel 3.0.0-19.32 from -proposed? (See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed).

Also, nomodeset should be a not supported configuration with i915 that drives your intel video device, use of i915 implies modesetting always enabled nowadays I expect, only serves for testing.

Revision history for this message
adam jvok (ajvok1) wrote :

Tested with 3.0.0-19.32 as suggested.
The results are exactly the same as above with 3.3.0-999-generic_3.3.0-999.201203210406_i386.deb.
So,
1. Looks like it is fixed in 19.32
2. From what you say, nomodeset shouldn't be used anyway with this device.
I guess that's done then. Thanks.

Revision history for this message
Herton R. Krzesinski (herton) wrote :

Thanks for testing, I'm going ahead and setting this to Fix Released.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Ivan Zorin (iaz) wrote :

I may be wrong, but looks like that I have the similar issue - no suspend/hibernate using 'nomodeset'.
Currently I can't booting without 'nomodeset', because looks like that's another issue - bug #991902
And symptoms when system is trying to suspend looks like described in bug #976987

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.