new kernals wont boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
High
|
Unassigned |
Bug Description
system wont boot unless i use an older kernal at time of booting. even after today i got a new kernal ending in .44 I think but it and .42do Not work I have to select .40 to get the thing going.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSign
Uname: Linux 4.8.0-40-generic i686
NonfreeKernelMo
.tmp.unity_
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: i386
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
CompositorUnred
CompositorUnred
Date: Tue Mar 28 11:09:59 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingI
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660G] [1002:9900] (prog-if 00 [VGA controller])
Subsystem: Lenovo Trinity [Radeon HD 7660G] [17aa:3970]
InstallationDate: Installed on 2017-01-25 (62 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
MachineType: LENOVO IdeaPad Z585
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/03/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 60CN95WW
dmi.board.
dmi.board.name: Lenovo
dmi.board.vendor: LENOVO
dmi.board.version: 31900006FRU WIN8 STD
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: IdeaPad Z585
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.
version.libdrm2: libdrm2 2.4.70-1
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Tue Mar 28 10:29:38 2017
xserver.configfile: default
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.
affects: | xorg (Ubuntu) → linux (Ubuntu) |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.