ACER Aspire 5100 laptop Suspend/Resume Failure

[Aaron Sosnick]

On this old laptop, Ubunutu 14.04 works fine on boot (after making sure fgrlx drivers are removed).

However after a Suspend/Resume the screen flickers/tears so badly as to make the system unusable.
Note that the problem does not occur with Hibernate/Resume. In fact if I can get the focus into a terminal while the
screen is flickering and do a $ sudo pm_hibernate, the screen will be okay on Resume.

Separately the wifi (b43) vanishes after a Resume, but I'll file a separate report on that later.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.47
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: aaron 1959 F.... pulseaudio
Date: Tue Jun 24 09:15:25 2014
HibernationDevice: RESUME=UUID=2e389861-74ff-4ad0-a5cc-272eef21f8d6
InstallationDate: Installed on 2014-06-21 (3 days ago)
InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530
Lsusb:
 Bus 001 Device 002: ID 5986:0100 Acer, Inc Orbicam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 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
MachineType: Acer Aspire 5100
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=6990d211-9cd7-4c22-9263-2e3c11e9010a ro radeon.runpm=1 splash quiet
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/22/2008
dmi.bios.vendor: Acer
dmi.bios.version: V3.13
dmi.board.name: Navarro
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5100:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5100
dmi.product.version: V3.13
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Aaron Sosnick (longlegged-guy)]

Note that this bug was reported back in 2011
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/894308 so it is not new.
The graphics card is not recognized at all and the system boots in an innapropriate, unchangeable resolution if
nomodeset is added to the boot options

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 kernel[0].

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.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc2-utopic/

[Aaron Sosnick (longlegged-guy)]

Attached is the output from

$ sudo dpkg -i linux-headers-3.16.0-031600rc2_3.16.0-031600rc2.201406220135_all.deb linux-headers-3.16.0-031600rc2-generic_3.16.0-031600rc2.201406220135_amd64.deb linux-image-3.16.0-031600rc2-generic_3.16.0-031600rc2.201406220135_amd64.deb

The output contains errors and while the machine still boots it comes up in an inappropriate/unchangeable 1024x768 resolution and no wifi. The radeon driver doesn't appear to be working at all. It's worse than an unusable screen after suspend.

I'm not sure whether I should tag kernel-unable-to-test-upstream or kernel-bug-exists-upstream. I will mark the bug back to confirmed.

I see similar errors and behavior when I try 3.14 and 3.15 kernels.

Thanks.

[Aaron Sosnick (longlegged-guy)]

Oh. Am I not supposed to mark as confirmed since I first reported? Apologies if I should not have marked. At any rate, unless I am making a mistake in installing, newer kernels make things worse not better. I'm happy to provide additional diagnostics or information if someone can be so kind as to let me know what would be useful.

Thanks.

[Aaron Sosnick (longlegged-guy)]

Since virtualbox seemed to the source of at least some of the errors coming from installing the 3.16rc2 kernel I uninstalled virtualbox and reinstalled the 3.16rc2 kernel. Output from sudo dpkg -i is attached. The install error messages are gone, but the behavior is is the same, graphics card and wifi not recognized at all.

[Aaron Sosnick (longlegged-guy)]

Umm.. I did as you asked. Is there anything else I should try or any additional information I can provide? Do we have any idea why the newer kernels don't work at all with the graphics card? Should I assume from silence that this isn't going to be a priority for anyone to work on?

[penalvch (penalvch)]

Aaron Sosnick, thank you for taking the time to report this bug and trying to help make Ubuntu better. However, Linux Mint, is not a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories.

[Aaron Sosnick (longlegged-guy)]

This problem happens with or without Mint packages.

It is an Ubuntu problem and you are not nice for suggesting otherwise.

Please mark "won't fix" not invalid if that's your attitude.

I'll give some more recent Ubuntu versions a chance when I can and reopen
if it hasn't been fixed.

[penalvch (penalvch)]

Aaron Sosnick, in order to eliminate confusion, it will help immensely if you filed a new report (not reopen this one) with Ubuntu (not Mint) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Aaron Sosnick (longlegged-guy)]

Okay fair enough. I have a recollection of trying a few different installs
back then in 2014, no idea why I submitted the bug report from a
non-vanilla Ubuntu install. That said, this looks pretty far upstream from
all the Mint stuff to me. I'm away from the machine in question until the
10th. I'll try to find some time once I'm back around it.

It's an old machine that I can't say I even really use now (although maybe
I would if the screen worked!), so I'm not going to have a ton of time to
bisect around a bunch of stuff,
but some vanilla 14.04 LTS install shouldn't be hard to try as long as I
can get it to boot into
a light enough desktop environment for the rusty hardware.

Thanks for taking the time to reply. I realize I'm not paying anybody
anything, though I do try
to be helpful in the community.

Regards,
A.

On Tue, Mar 1, 2016 at 9:15 AM, Christopher M. Penalver <
<email address hidden>> wrote:

> Aaron Sosnick, in order to eliminate confusion, it will help immensely if
> you filed a new report (not reopen this one) with Ubuntu (not Mint) via a
> terminal:
> ubuntu-bug linux
>
> Please feel free to subscribe me to it.
>
> For more on why this is helpful, please see
> https://wiki.ubuntu.com/ReportingBugs.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1333697
>
> Title:
> ACER Aspire 5100 laptop Suspend/Resume Failure
>
> Status in linux package in Ubuntu:
> Invalid
>
> Bug description:
> On this old laptop, Ubunutu 14.04 works fine on boot (after making
> sure fgrlx drivers are removed).
>
> However after a Suspend/Resume the screen flickers/tears so badly as to
> make the system unusable.
> Note that the problem does not occur with Hibernate/Resume. In fact if I
> can get the focus into a terminal while the
> screen is flickering and do a $ sudo pm_hibernate, the screen will be
> okay on Resume.
>
> Separately the wifi (b43) vanishes after a Resume, but I'll file a
> separate report on that later.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: linux-image-3.13.0-24-generic 3.13.0-24.47
> ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
> Uname: Linux 3.13.0-24-generic x86_64
> ApportVersion: 2.14.1-0ubuntu3.2
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: aaron 1959 F.... pulseaudio
> Date: Tue Jun 24 09:15:25 2014
> HibernationDevice: RESUME=UUID=2e389861-74ff-4ad0-a5cc-272eef21f8d6
> InstallationDate: Installed on 2014-06-21 (3 days ago)
> InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530
> Lsusb:
> Bus 001 Device 002: ID 5986:0100 Acer, Inc Orbicam
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 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
> MachineType: Acer Aspire 5100
> PccardctlIdent:
> Socket 0:
> no product info available
> PccardctlStatus:
> Socket 0:
> no card
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=...