resume hang ubuntu 14.10 kernel 3.16

[James Cobban]

Since upgrading to 14.10 every time I open the laptop lid the system hangs after enabling the keyboard but before turning on the display. That is the backlight on the LED screen is not turned on. This issue has occurred occasionally since 12.4, but is now completely consistent.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-24-generic 3.16.0-24.32
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jcobban 3455 F.... pulseaudio
 /dev/snd/controlC0: jcobban 3455 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Nov 13 14:51:39 2014
HibernationDevice: RESUME=UUID=e1d460c4-e29e-470e-a302-7891166d98f7
MachineType: Dell Inc. Vostro 3555
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=5850bfca-8269-4a92-8fda-798e6557b0bd ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-24-generic N/A
 linux-backports-modules-3.16.0-24-generic N/A
 linux-firmware 1.138
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-11-12 (1 days ago)
WifiSyslog: Nov 13 14:34:15 jcobban-laptop kernel: [ 1205.903943] systemd-hostnamed[4497]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
dmi.bios.date: 10/24/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0K89MF
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd10/24/2011:svnDellInc.:pnVostro3555:pvrNotSpecified:rvnDellInc.:rn0K89MF:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Vostro 3555
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[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.18 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.18-rc4-vivid/

[James Cobban (7-webmaster)]

On 2014-11-14 04:35 PM, Christopher M. Penalver wrote:
> hangs after enabling the keyboard but before turning on the display.

** Tags added: bios-outdated-a06

I agree that the BIOS on my laptop has problems. Linux complains about them regularly. However I have been to the Dell site and there is no more recent BIOS that I can install. And since Dell does not support running Linux on this laptop I have no ability to raise this issue with the OEM.

--

Jim Cobban <email address hidden>
<mailto:<email address hidden>?subject=Email%20Message>
Web-site: www.jamescobban.net <http://www.jamescobban.net/>
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
[phone]

[James Cobban (7-webmaster)]

On 2014-11-14 11:02 PM, Christopher M. Penalver wrote:
> James Cobban, the A06 BIOS may be found at
> http://www.dell.com/support/home/bs/en/bsdhs1/Drivers/DriversDetails?driverId=905PX
> .
>
Thank you. That was not there the last time I went looking for
microcode. How am I supposed to install that when it comes packaged as
a .EXE? Will it run under Wine?

--

Jim Cobban <email address hidden>
<mailto:<email address hidden>?subject=Email%20Message>
Web-site: www.jamescobban.net <http://www.jamescobban.net/>
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
[phone]

[James Cobban (7-webmaster)]

On 2014-11-13 03:02 PM, Joseph Salisbury wrote:
> Would it be possible for you to test the latest upstream kernel? Refer
> tohttps://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v3.18 kernel[0].
I downloaded the following files:
linux-headers-3.18.0-031800rc2_3.18.0-031800rc2.201410262035_all.deb
linux-headers-3.18.0-031800rc2-generic_3.18.0-031800rc2.201410262035_amd64.deb
linux-image-3.18.0-031800rc2-generic_3.18.0-031800rc2.201410262035_amd64.deb

and installed. It would not boot, complaining that it could not find
the root drive by UUID. Perhaps the instructions for installing a
kernel are inadequate.

I have now purged that kernel, and upgraded the bios to the A06 level.
As far as I can tell everything is going fine during the resume EXCEPT
that the backlight is not turned on. Every time I open the lid the disk
light flickers in a consistent pattern, the mouse turns on, and the
keyboard works. But without the display all I can do is Alt-PrtSc-RSEIUB!

--

Jim Cobban <email address hidden>
<mailto:<email address hidden>?subject=Email%20Message>
Web-site: www.jamescobban.net <http://www.jamescobban.net/>
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
[phone]

[James Cobban (7-webmaster)]

I have tried to upgrade the microcode. I rebooted into Windoze and ran the .exe. I see no difference in the value of microcode in /proc/cpuinfo, so I don't know that it took, but I did run the upgrade command, and sat there while it displayed its progress indicator.

I tried installing the 3.18 kernel but it failed, as I reported, and nobody has got back to me to suggest what I did wrong in the installation.

I have tried using the proprietary ATI driver. If I manually suspend the system and restart it does recover correctly with the proprietary driver. However with the proprietary driver if I close the lid and then reopen it the system does not resume at all. That is the only result is that I hear a "clunk" after the lid is opened, so obviously the BIOS recognized that the lid had opened, but there is no disk activity, and the keyboard is not enabled so the only recover is holding down the power button. With the open source driver the system reliably recovers on Ubuntu 14.10 kernel 3.16 (which it did not do on 14.4 with kernel 3.13) However the backlight is not turned on so I cannot do anything. I have been having that problem with the Xorg driver for several years now and when I ask their development group how to give the driver a kick to turn on the backlight their response is "the driver should do that for you." So I ask them again and every time the response is "the driver should do that for you". Why they cannot just add a command to turn the gd light on I do not understand. I guess they are purists.

I have even tried reformatting the partition and reinstalling 4.10 from scratch.

I really want to help you out by testing the problem but you have to tell me what to do, because I have tried to do everything you asked when I opened the problem and I have not heard from anyone since. I am really tired of having to leave my laptop open!

I cannot see any option for adding tags in the Launchpad user interface.

[James Cobban (7-webmaster)]

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

A06
05/28/2014

[penalvch (penalvch)]

James Cobban, could you please test the latest mainline kernel (3.18-rc5) and advise to the results? 3.18-rc2 has been problematic for many.

[James Cobban (7-webmaster)]

On 2014-11-20 07:25 PM, Christopher M. Penalver wrote:
> James Cobban, could you please test the latest mainline kernel
> (3.18-rc5) and advise to the results? 3.18-rc2 has been problematic for
> many.
>
> ** Tags removed: bios-outdated-a06
> ** Tags added: latest-bios-a06
>
I attempted to install kernel 3.18-rc5 but the compile of the fglrx-core
failed, see bug 1395222.

--

Jim Cobban <email address hidden>
<mailto:<email address hidden>?subject=Email%20Message>
Web-site: www.jamescobban.net <http://www.jamescobban.net/>
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
[phone]

[penalvch (penalvch)]

James Cobban, as the mainline article advises, the mainline kernel won't work with proprietary drivers (ex. fglrx). Hence, you would need to first uninstall it, and then do the test.

[James Cobban (7-webmaster)]

On 2014-11-20 07:25 PM, Christopher M. Penalver wrote:
> James Cobban, could you please test the latest mainline kernel
> (3.18-rc5) and advise to the results? 3.18-rc2 has been problematic for
> many.
>
> ** Tags removed: bios-outdated-a06
> ** Tags added: latest-bios-a06
>
I rebooted with 3.18-rc5. The graphics driver is now broken. The
system has reverted to a lower resolution. Even when I try booting the
previously working 3.16-24 and 3.16-23 I cannot get proper resolution.
On 3.18-rc5 I cannot resume from suspend whether the suspend was
performed manually or by closing and opening the lid. Remember in 14.10
the system actually resumes. The ONLY problem is that it does not turn
the backlight on. All I want is for someone to tell me what I have to
do to turn the backlight on. Otherwise 14.10 is resuming from suspend fine.

Meanwhile: How do I fix the graphics that were broken when I installed
3.18-rc5?

--

Jim Cobban <email address hidden>
<mailto:<email address hidden>?subject=Email%20Message>
Web-site: www.jamescobban.net <http://www.jamescobban.net/>
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
[phone]

[James Cobban (7-webmaster)]

On 2014-11-21 06:19 PM, Christopher M. Penalver wrote:
> James Cobban, as the mainline article advises, the mainline kernel won't
> work with proprietary drivers (ex. fglrx). Hence, you would need to
> first uninstall it, and then do the test.
>
I am not running fglrx. I did not ask for fglrx to be installed, and
when I check the drivers the system declares that I am running with the
X.org wrapper. It is the install for 3.18-rc5 that is broken, and now
my graphics are f....d up!

--

Jim Cobban <email address hidden>
<mailto:<email address hidden>?subject=Email%20Message>
Web-site: www.jamescobban.net <http://www.jamescobban.net/>
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
[phone]

[James Cobban (7-webmaster)]

I took me a day to recover from the damage done to my system by trying to install 3.18-rc5. I need more advice before I will risk losing my system by trying another kernel. Is there no way to debug this problem on 3.16?

[James Cobban (7-webmaster)]

I have created a separate partition on my HD, installed Ubuntu 4.10 from the DVD, upgraded to the latest kernel 3.16.25 from the repository, and then installed kernel 3.18-rc5 according to the instructions on the web. The installation reports a known bug. I then reboot. I have no idea how to copy the page of output that results, including a kernel panic to some place where I can post it. The output includes:

request_module: runaway loop modprobe binfmt-464C [5 copies]
Failed to execute /init (error -8)
Starting init: /sbin/init exists but couldn't execute it (error -8)
Starting init: /bin/sh exists but couldn't execute it (error -8)
Kernel panic - not syncing: no working init found. Try passing init= option to kernel ...
CPU: PID: 1 Comm: swapper/0 Not tainted 3.18.0-031800rc5-generic #201411162035
Hardware name: Dell Inc. Vostro 3555/0K8MF, BIOS A06 05/28/2014
...

[James Cobban (7-webmaster)]

On 11/24/2014 10:55 PM, Christopher M. Penalver wrote:
> James Cobban, could you please test the latest mainline kernel 3.18-rc6
> and advise to the results?
>
I installed 3.18-rc6. I get the same known installation bug, and the
same kernel panic for a missing init that I got with rc5.

--

Jim Cobban <email address hidden>
<mailto:<email address hidden>?subject=Email%20Message>
Web-site: www.jamescobban.net <http://www.jamescobban.net/>
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
[phone]

[penalvch (penalvch)]

James Cobban, if the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please continue to test the next most recent kernel version until you can test to the issue with a mainline kernel.

[James Cobban (7-webmaster)]

On 11/25/2014 11:13 PM, Christopher M. Penalver wrote:
> James Cobban, if the test did not allow you to test to the issue (ex.
> you couldn't boot into the OS) please continue to test the next most
> recent kernel version until you can test to the issue with a mainline
> kernel.
>
I have already tried 3.18-rc2, rc5, and rc6. I cannot boot any of
them. Since neither rc5 nor rc6 actually install properly, perhaps if
someone would address the known installation bug, so that I get an init
file built and avoid the kernel panic I could actually test the latest
kernels. I have now added myself to the list of affected users for that
bug. Note that the published instructions for removing 3.18 do not
work. I had to individually remove each individual component to get rid
of rc5 before I installed rc6. I will try rc4 and rc3 to see if they
will boot during the next 24h, but I do have other things I need this
system for.

I am up to 3.16.0-25 on 14.10 and the system still will not resume from
suspend.

--

Jim Cobban <email address hidden>
<mailto:<email address hidden>?subject=Email%20Message>
Web-site: www.jamescobban.net <http://www.jamescobban.net/>
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
[phone]

[James Cobban (7-webmaster)]

I am trying to follow the instructions for installing these kernels, but there is clearly something wrong.

Firstly the installs all fail with the following known bug:

bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1: bcmwl kernel module failed to build [error: macro "alloc_netdev" requires 4 arguments, but only 3 given] Edit

    Ubuntu
    “bcmwl” package
    Bugs
    Bug #1358966

This is obviously a simple error which could be fixed in a minute. I suspect it is the failed installation that causes the resulting system boot kernel panic because of a missing init.

Secondly when I issue the specified command in the web page to remove the 3.18 headers and kernel the following happens:

sudo apt-get remove linux-headers-3.18* linux-image-3.18*

Reading package lists...
Building dependency tree...
Reading state information...
Package 'linux-headers-3.16.0-23' is not installed, so not removed
Package 'linux-headers-3.16.0-23-generic' is not installed, so not removed
Package 'linux-headers-3.16.0-23-lowlatency' is not installed, so not removed
Package 'linux-image-3.16.0-23-generic' is not installed, so not removed
Package 'linux-image-3.16.0-23-lowlatency' is not installed, so not removed
Package 'linux-headers-3.16.0-24' is not installed, so not removed
Package 'linux-headers-3.16.0-24-generic' is not installed, so not removed
Package 'linux-headers-3.16.0-24-lowlatency' is not installed, so not removed
Package 'linux-headers-3.16.0-25-lowlatency' is not installed, so not removed
Package 'linux-image-3.16.0-24-generic' is not installed, so not removed
Package 'linux-image-3.16.0-24-lowlatency' is not installed, so not removed
Package 'linux-image-3.16.0-25-lowlatency' is not installed, so not removed
The following package was automatically installed and is no longer required:
  thermald
Use 'apt-get autoremove' to remove it.
The following packages will be REMOVED:
  linux-generic linux-headers-3.16.0-25 linux-headers-3.16.0-25-generic
  linux-headers-3.18.0-031800rc5 linux-headers-3.18.0-031800rc6
  linux-headers-3.18.0-031800rc6-generic:i386 linux-headers-generic
  linux-image-3.16.0-25-generic linux-image-extra-3.16.0-25-generic
  linux-image-generic
0 upgraded, 0 newly installed, 10 to remove and 0 not upgraded.
After this operation, 425 MB disk space will be freed.
Do you want to continue? [Y/n] (Reading database ... 215753 files and directories currently installed.)
Removing linux-generic (3.16.0.25.26) ...
Removing linux-headers-generic (3.16.0.25.26) ...
Removing linux-headers-3.16.0-25-generic (3.16.0-25.33) ...
Removing linux-headers-3.16.0-25 (3.16.0-25.33) ...
Removing linux-headers-3.18.0-031800rc5 (3.18.0-031800rc5.201411162035) ...
Removing linux-headers-3.18.0-031800rc6-generic (3.18.0-031800rc6.201411231935) ...
Removing linux-headers-3.18.0-031800rc6 (3.18.0-031800rc6.201411231935) ...
Removing linux-image-generic (3.16.0.25.26) ...
Removing linux-image-extra-3.16.0-25-generic (3.16.0-25.33) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-25-generic /boot/vmlinuz-3.16.0-25-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-25-generic /boot/vmlinuz-3.16.0-25-generic
run-parts: executing /etc...

[penalvch (penalvch)]

James Cobban, as the article now more specifically advises, one would have to uninstall bcmwl first before installing the mainline kernel.

As well, the article does not advise to run linux-headers-3.18* to uninstall a package. It advises to do the exact package name on a per package basis.

[James Cobban (7-webmaster)]

Then we are looking at different articles. I am looking at : http://linuxg.net/how-to-install-kernel-3-18-rc6-on-ubuntu-14-10-ubuntu-14-04-and-derivatives/ which does not say anything about bcmwl and explicit uses * on the remove.

[penalvch (penalvch)]

James Cobban, please review https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392460/comments/3 for the official documentation previously provided to you.

The URL you linked is some "Bob's homemade website", YMMV.

[James Cobban (7-webmaster)]

On 11/28/2014 06:54 PM, Christopher M. Penalver wrote:
> James Cobban, please review
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392460/comments/3
> for the official documentation previously provided to you.
>
> The URL you linked is some "Bob's homemade website", YMMV.
>
The procedure described there is too vague and confusing and incomplete
for an amateur to follow. I tried. There are too many examples of "if
<confusing piece of gibberish requiring knowledge I do not have> then
you should <confusing and vague procedure>. I tried it but could get
nowhere. Which is presumably why "Bob" wrote his site. I am trying to
help you to help me but you are not making it easy by assuming that I am
intimate with kernel issues, or even that I am familiar with exactly
which bits of software are already installed. I have tried to be as
clean as possible by installing a complete fresh system from the 14.10
DVD, but I haven't the foggiest notion what "bcmwl" is or does or why
there would be one on my system! I assume that if the 14.10 DVD
installed it there is a damn good reason why it is there.

--

Jim Cobban <email address hidden>
<mailto:<email address hidden>?subject=Email%20Message>
Web-site: www.jamescobban.net <http://www.jamescobban.net/>
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
[phone]

[penalvch (penalvch)]

James Cobban, thousands of people, from newbies to IT professionals, were able to successfully follow the same instructions verbatim in order to install and test the mainline kernel. This is because it was written assuming the reader has no prior knowledge of linux at all.

For more on bcmwl, please see https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx .

[James Cobban (7-webmaster)]

On 11/28/2014 12:32 AM, Christopher M. Penalver wrote:
> James Cobban, as the article now more specifically advises, one would
> have to uninstall bcmwl first before installing the mainline kernel.
>
> As well, the article does not advise to run linux-headers-3.18* to
> uninstall a package. It advises to do the exact package name on a per
> package basis.
>
OK. I removed the bcmwl proprietary driver. I downloaded the 3 .deb
files for amd64. You provide no procedure for performing that download
in any obvious way. For example how am I supposed to obtain the proper
names for a wget command or to download them by ftp to a specific
directory. In Firefox double clicking on each entry downloads it into
the Downloads directory, not into the recommended separate directory.
This is part of what I mean when I say your documentation is vague. I
installed, and booted. The system now boots on kernel 3.18-rc6. There
is no observable change in behavior from kernel 3.16. The system
displays disk activity consistent with normal resume processing, but the
back-light on my display is not turned on, so I have no choice but to
manually reboot even though the system is completely operational in all
other respects. For example I can ssh, ftp, even http to the system.

Kernel 3.16 seems to have resolved all of the actual suspend/resume
problems I had on previous releases. But at least most of the time the
earlier kernels and drivers would turn on the back-light when they felt
like resuming at all.

I would stop bothering the kernel group and the X.org team if someone
would just give me a manual command to turn on the damn light! I can
ssh into the system to issue the command.

--

Jim Cobban <email address hidden>
<mailto:<email address hidden>?subject=Email%20Message>
Web-site: www.jamescobban.net <http://www.jamescobban.net/>
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
[phone]

[James Cobban (7-webmaster)]

I have tested the issue against 3.18-rc2, 3.18-rc5, and 3.18-rc6 and it still is not fixed. I have been raising this issue for TWO years, since Ubuntu 12.4 with no resolution in sight. What else do you want me to do to reactivate this problem? I want to be able to close my laptop. As it is my laptop is effectively a desktop with an inconveniently small screen and mediocre keyboard because I cannot close the lid and take it anywhere. I have to leave my mouse sitting on top of the keyboard so the laptop will not accidentally close! You may think that I am being unreasonable, but two years is a long time to have a broken system with nobody giving me any hope that it will ever work.

Tell me what to do!

[penalvch (penalvch)]

James Cobban, the latest mainline kernel is 3.18.

[James Cobban (7-webmaster)]

On 12/10/2014 01:32 AM, Christopher M. Penalver wrote:
> James Cobban, the latest mainline kernel is 3.18.
>
I know. The behavior is unchanged at 3.18-rc6.

--

Jim Cobban <email address hidden>
<mailto:<email address hidden>?subject=Email%20Message>
Web-site: www.jamescobban.net <http://www.jamescobban.net/>
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
[phone]

[penalvch (penalvch)]

James Cobban, 3.18-rc6 is not 3.18.

[James Cobban (7-webmaster)]

On 12/10/2014 06:47 PM, Christopher M. Penalver wrote:
> James Cobban, 3.18-rc6 is not 3.18.
>
I was explicitly told to try out 3.18-rc6. Prior to that I was told to
try 3.18-rc5, and before that to try 3.16 which I did by migrating to
14.10, which I did not want to do because it is not an LTS release. I
was NEVER told to try out 3.18 in any other version. As far as I am
concerned the kernel team are desperately trying to find any excuse to
not actually look at the problem. I have explained that I do not
understand the instructions on exactly what to do to test out a kernel,
and all you seem to have the time for is to criticize my stupidity,
rather than explain exactly what it is that I have to do. My laptop has
been marginally useful for over TWO years because resume doesn't turn on
the backlight! Kernel 3.16 in Ubuntu 14.10 seems to have addressed
every other suspend/resume issue I had, but the backlight is STILL not
being turned on, and that means suspend/resume is unusable on my laptop.
I am sick and tired of reporting this problem again every time I change
releases, with no results. I appreciate that you are all volunteers but
how hard can it be to turn on the backlight? I have begged the X-org
team for a command to turn on the backlight, and the only response I get
is "The driver should turn on the backlight." Well it doesn't.

Please tell me PRECISELY what I have to do. The lack of precision in
your instructions so far have wasted your time and mine.

--

Jim Cobban <email address hidden>
<mailto:<email address hidden>?subject=Email%20Message>
Web-site: www.jamescobban.net <http://www.jamescobban.net/>
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
[phone]

[James Cobban (7-webmaster)]

Since no one will tell me what I need to do to reactivate this problem report, and since the original description of the problem is not specific enough, I have created a new problem report 1401672 with a more specific description and additional documentation.

[James Cobban (7-webmaster)]

I am really desperate to resolve this problem. I installed xbacklight, closed my laptop, reopened the laptop, saw the disk activity that indicated the system had resumed from suspend. I entered Ctrl-Alt-T blindly, entered "xbacklight -set 100". Nothing happened. Entered "vbetool dpms on". Nothing happened. I previously tried both commands while the system was running normally and saw nothing to indicate that they didn't work. However both tools are dependent upon the driver working to implement the standard interfaces that the tools use. All I want is a command that I can issue to turn on the bloody light bulb! If I had such a command I could add it to the script that runs when the lid is opened and I could get off everybody's back.

[James Cobban (7-webmaster)]

On a reboot the backlight is turned on very early in the process, before the driver is loaded, probably by the bios. This is obvious because grub is able to display, so on a reboot the driver does not have to turn on the backlight, it is already on, whereas on a resume the backlight needs to be explicitly turned on by the operating system since the bios is only involved to the extent of signalling the ACPI state. However even if there is a bug in the bios with respect to supporting whatever mechanism the driver is attempting to use to manage the hardware display state, on Ubuntu 13 and earlier the display was occasionally turned on by resume, whereas now it is never turned on.

Please tell me what I have to do to resolve the "incomplete" status of this problem.

[James Cobban (7-webmaster)]

I have tried to reproduce the problem with the latest daily build of Ubuntu 15.04. The system does not load the driver properly and the system does not resume when the lid is opened, so it does not get far enough to see whether the problem still exists at that level.

[Launchpad Janitor (janitor)]

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

[James Cobban (7-webmaster)]

How can I keep this unresolved problem open? I have had this problem for over two years now and I still do not have a solution or even a workaround.

[penalvch (penalvch)]

James Cobban, could you please test the latest mainline kernel (now 4.0-rc2) and advise to the results?

[James Cobban (7-webmaster)]

I have tested this against Ubuntu 15.04 and the problem is solved.