Jason C. McDonald, thank you for reporting this and helping make Ubuntu
better.

In order to allow additional upstream developers to examine the issue, at your 
earliest convenience, could you please test the latest upstream kernel 
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please 
keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest upstream kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Tags added: bios-outdated-1.20

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652354

Title:
  Internal laptop display stops working in 4.4.0-57-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Toshiba Satellite P745D w/ AMD graphics, and I'm running the
  open source Radeon driver. I can use the internal and/or an external
  VGA monitor just fine in 4.4.0.53-generic and prior. However, upon
  updating to 4.4.0-57-generic, the internal monitor shuts off after
  GRUB and will not display anything. Setting NOMODESET in GRUB does not
  resolve the issue - I had to reboot into 4.4.0-53 to see anything on
  the internal laptop monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   jason      3081 F...m pulseaudio
   /dev/snd/controlC1:  jason      3081 F.... pulseaudio
   /dev/snd/controlC0:  jason      3081 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 23 09:30:44 2016
  HibernationDevice: RESUME=UUID=6428aefe-2277-446d-9209-a012d120611b
  MachineType: TOSHIBA Satellite P745D
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=7e97fb33-4ee2-499c-a3c4-69f37f16c4f4 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware                            1.157.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (236 days ago)
  dmi.bios.date: 05/26/2011
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.10
  dmi.board.asset.tag: NULL
  dmi.board.name: QOQAE
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.10:bd05/26/2011:svnTOSHIBA:pnSatelliteP745D:pvrPSMR1U-004001:rvnTOSHIBA:rnQOQAE:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite P745D
  dmi.product.version: PSMR1U-004001
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to