seeker5528, 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: latest-bios-1.4
** Description changed:
- If I connect my monitor to my computer with a VGA cable, I have to stop
- at the grub menu and add 'nomodeset' to the kernel options with all the
- 4.4.0-* kernels.
-
- If I do not add 'nomodeset' to the kernel options, my monitor goes
+ If I connect my monitor to my computer with a VGA cable my monitor goes
blank, complains of no video signal, then goes to sleep as soon as the
kernel attempts to enable mode setting.
Turning the monitor off and back on does not help, unplugging the VGA
cable and connecting the DVI cable does not help. I have to hit
'Ctrl'+'Alt'+'Del' and wait for the computer to restart or hit the power
button and wait for the computer to shutdown.
- If I connect the monitor to the computer with a DVI cable, I do not have
- to add 'nomodeset' to the kernel options, everything works as expected.
+ If I connect the monitor to the computer with a DVI cable, everything
+ works as expected.
I do not have the option for HDMI on the monitor currently attached.
- Will see if I can get that tested either with another monitor or DVI to
- HDMI adapter.
+
+ WORKAROUND: Add to the grub menu kernel parameter:
+ nomodeset
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
.tmp.unity_support_test.0:
-
+
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
BootLog: /dev/sda6: clean, 615456/10196352 files, 5471760/20831539 blocks
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Sep 7 15:46:17 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
- Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644]
(prog-if 00 [VGA controller])
- Subsystem: Micro-Star International Co., Ltd. [MSI] Sumo [Radeon HD 6410D]
[1462:7786]
+ Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644]
(prog-if 00 [VGA controller])
+ Subsystem: Micro-Star International Co., Ltd. [MSI] Sumo [Radeon HD 6410D]
[1462:7786]
MachineType: MSI MS-7786
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic
root=UUID=dafa5f62-dc35-4803-b094-5062e73974b0 ro quiet splash
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A55M-P25 (MS-7786)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV1.4:bd05/14/2012:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P25(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7786
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Wed Sep 7 15:33:21 2016
xserver.configfile: default
xserver.devices:
- input Power Button KEYBOARD, id 6
- input Power Button KEYBOARD, id 7
- input HID 413c:3010 MOUSE, id 8
- input AT Translated Set 2 keyboard KEYBOARD, id 9
+ input Power Button KEYBOARD, id 6
+ input Power Button KEYBOARD, id 7
+ input HID 413c:3010 MOUSE, id 8
+ input AT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
-
+
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6
xserver.video_driver: radeon
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1621265
Title:
lose monitor during boot up if I don't add 'nomodeset' to kernel
options
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1621265/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
