[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread nagato...@hotmail.com
Funcionó para mi, tengo un lenovo G40-80 y desde Junio no podía guardar
cambios en la BIOS, no me reconocio ninguna USB en mo live, de ningún
S.O wifislax, windows 10 con Rufus, Lubuntu etc. pero si podia botear
desde dvd lo que hice fue actualizar el kernel con UkuU y ahora ya pude
volver a botear en modo live. :)

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1728036] Re: Bluetooth does not detect any devices

2017-12-30 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

-- 
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/1728036

Title:
  Bluetooth does not detect any devices

Status in linux package in Ubuntu:
  Expired

Bug description:
  Bluetooth does not detect any devices

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-97-generic 4.4.0-97.120
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johannes   1664 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 27 14:26:40 2017
  HibernationDevice: RESUME=UUID=f750a173-1ffa-48c7-9aaa-faf8785da5eb
  InstallationDate: Installed on 2017-07-23 (96 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b49f Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 174f:1169 Syntek 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MJ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CCCN18WW(V2.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad 1
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 100-15IBY
  dmi.modalias: 
dmi:bvnLENOVO:bvrCCCN18WW(V2.04):bd11/11/2015:svnLENOVO:pn80MJ:pvrLenovoideapad100-15IBY:rvnLENOVO:rnLenovoideapad1:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBY:
  dmi.product.name: 80MJ
  dmi.product.version: Lenovo ideapad 100-15IBY
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728036/+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


[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2017-12-30 Thread Daniel Ruoso
I think I just had a huge breakthrough, after installing a kernel 4.14.0
with all of the patches referenced here, suddenly the touchpad was
working. I went ahead and rebooted and sure enough the touchpad was not
working again. Then I thought, what if I suspend the computer? And sure
enough, the touchpad magically starts working after the computer wakes
up. I think there's some device initialization code that gets called on
wake-up that is missed on boot.

-- 
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/1728244

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1728244/+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


[Kernel-packages] [Bug 1734172] Re: Upgrade ZFS to 0.7.3

2017-12-30 Thread Kim Robertson
Bump the version.

The current version is 0.7.5:

https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.5 .

ZFS 0.7.5 is compatible with 2.6.32 - 4.14 Linux kernels.
ZFS 0.7.3 was compatible with 2.6.32 - 4.13 Linux kernels.
ZFS 0.6.5.11 was compatible with 2.6.32 - 4.12-rc3 Linux kernels.

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

Title:
  Upgrade ZFS to 0.7.3

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  ZFS v0.7 is out, current version is 0.7.3:

  https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.3 .

  
  It is desired to have the latest stable version at least in LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfsutils-linux 0.6.5.11-1ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  Date: Thu Nov 23 19:03:47 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (187 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1734172/+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


[Kernel-packages] [Bug 1740643] [NEW] bcmwl-kernel-source (not installed): bcmwl kernel module failed to build

2017-12-30 Thread michael grosh
Public bug reported:

none of the versions I have used pickup the wireless connection. Just
installed ver 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source (not installed)
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
DKMSKernelVersion: 4.4.0-104-generic
Date: Sat Dec 30 19:06:36 2017
InstallationDate: Installed on 2017-12-30 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageVersion: (not installed)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: bcmwl
Title: bcmwl-kernel-source (not installed): bcmwl kernel module failed to build
UpgradeStatus: Upgraded to xenial on 2017-12-31 (0 days ago)

** Affects: bcmwl (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  bcmwl-kernel-source (not installed): bcmwl kernel module failed to
  build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  none of the versions I have used pickup the wireless connection. Just
  installed ver 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-104-generic
  Date: Sat Dec 30 19:06:36 2017
  InstallationDate: Installed on 2017-12-30 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageVersion: (not installed)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source (not installed): bcmwl kernel module failed to 
build
  UpgradeStatus: Upgraded to xenial on 2017-12-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1740643/+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


[Kernel-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash

2017-12-30 Thread Peter Windridge
Based on skimming https://bugzilla.kernel.org/show_bug.cgi?id=195299 I
think this might be fixed upstream but didn't make it to kernel 4.13.
When will Ubuntu move to 4.14? :)

For now I am trying an older microcode (27.541033.0) but am not
optimistic..


** Bug watch added: Linux Kernel Bug Tracker #195299
   https://bugzilla.kernel.org/show_bug.cgi?id=195299

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

Title:
  System hangs after iwlwifi firmware crash

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Kubuntu 17.10 my HP EliteBook 820 G3 hangs at
  unpredictable times. I have experienced probably 20 hangs. Once the
  system is hung no mouse movement, NumLock toggle, VT switch,
  Ctrl+Alt+Del, SysRq keys, SSH attempts have any effect whatsoever. Any
  audio playing is stuck looping in the hardware buffer. The system is
  really stuck. Only the keyboard backlight is still responsive.

  The only correlation I have noticed is that the system only hangs if
  WiFi is enabled. This morning I experienced two hangs in ten minutes
  necessitating reboots. Having disabled WiFi the system has been stable
  since ~1100 (~5 hours).

  Often, I see a iwlwifi hardware reset in the logs before the system
  dies:

  /var/log/syslog:Oct 30 11:49:30 fry kernel: [ 6529.550751] iwlwifi
  :02:00.0: Microcode SW error detected.  Restarting 0x8200.

  (apport has hopefully uploaded the full log, please lmk if not).
  Sometimes the message doesn't make it into the logs, and ext4
  truncates the file at the next mount.

  There seems to be no correlation with any messages immediately before
  the wifi chip dies. It doesn't seem to matter whether I'm at home or
  at work. I have wired ethernet at work simultaneously with wifi, but
  the wifi provides IPv6 so I would imagine most traffic uses wifi, so
  it's hard to say whether there's any effect of the traffic load on the
  probability of failure.

  Here is a sample of the firmware load:

  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.604743] iwlwifi 
:02:00.0: enabling device ( -> 0002)
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611790] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-33.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611930] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-32.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.620028] iwlwifi 
:02:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.650972] iwlwifi 
:02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208

  02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

  Any help appreciated.

  Thanks,
  Bruce

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Oct 30 16:15:43 2017
  DistUpgraded: 2017-10-15 14:47:25,517 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: kubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:807c]
  InstallationDate: Installed on 2016-09-09 (416 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP EliteBook 820 G3
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-15 (15 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.13
  dmi.board.name: 807C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.74
  dmi.chassis.asset.tag: 5CG6354JW5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.74:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 820 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Kernel-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash

2017-12-30 Thread Peter Windridge
I believe I also have this bug on a HP Envy 13-ab002na.  It is a vanilla
17.10 install.

As with @bwduncan the laptop becomes completely unresponsive to any
inputs and needs hard power off.  The last thing in /var/log/kern.log is
iwlwifi Microcode SW error detected.  It has happened 3 times in the
last 30 min.  It had previously been less frequent and mostly only when
the machine was sleeping.

If I disable WiFi and tether to my phone (via USB) I have not yet
experienced such a lockup.

I installed 17.10 from new with this laptop so cannot say whether it is
17.10 specific (previously had a ThinkPad; seems I had a narrow escape
with the BIOS write bit!).

[...]
Hardware name: HP HP ENVY Notebook 13-ab0XX/82B9, BIOS F.04 09/29/2016
[...]

Dec 30 21:35:56 schramm kernel: [ 1364.091405] iwlwifi :01:00.0: Microcode 
SW error detected.  Restarting 0x8200.
Dec 30 21:35:56 schramm kernel: [ 1364.091570] iwlwifi :01:00.0: Start IWL 
Error Log Dump:
Dec 30 21:35:56 schramm kernel: [ 1364.091577] iwlwifi :01:00.0: Status: 
0x0200, count: 6
Dec 30 21:35:56 schramm kernel: [ 1364.091583] iwlwifi :01:00.0: Loaded 
firmware version: 29.610311.0
Dec 30 21:35:56 schramm kernel: [ 1364.091589] iwlwifi :01:00.0: 0x0038 
| BAD_COMMAND 
Dec 30 21:35:56 schramm kernel: [ 1364.091594] iwlwifi :01:00.0: 0x0220 
| trm_hw_status0
Dec 30 21:35:56 schramm kernel: [ 1364.091599] iwlwifi :01:00.0: 0x 
| trm_hw_status1
Dec 30 21:35:56 schramm kernel: [ 1364.091603] iwlwifi :01:00.0: 0x00043D58 
| branchlink2
Dec 30 21:35:56 schramm kernel: [ 1364.091608] iwlwifi :01:00.0: 0x0004B016 
| interruptlink1
Dec 30 21:35:56 schramm kernel: [ 1364.091612] iwlwifi :01:00.0: 0x 
| interruptlink2
Dec 30 21:35:56 schramm kernel: [ 1364.091617] iwlwifi :01:00.0: 0x0072001C 
| data1
Dec 30 21:35:56 schramm kernel: [ 1364.091621] iwlwifi :01:00.0: 0x0573 
| data2
Dec 30 21:35:56 schramm kernel: [ 1364.091625] iwlwifi :01:00.0: 0x0073 
| data3
Dec 30 21:35:56 schramm kernel: [ 1364.091630] iwlwifi :01:00.0: 0xD4817170 
| beacon time
Dec 30 21:35:56 schramm kernel: [ 1364.091634] iwlwifi :01:00.0: 0x6C4BEE92 
| tsf low
Dec 30 21:35:56 schramm kernel: [ 1364.091638] iwlwifi :01:00.0: 0x0090 
| tsf hi
Dec 30 21:35:56 schramm kernel: [ 1364.091643] iwlwifi :01:00.0: 0x 
| time gp1
Dec 30 21:35:56 schramm kernel: [ 1364.091647] iwlwifi :01:00.0: 0x509414C2 
| time gp2
Dec 30 21:35:56 schramm kernel: [ 1364.091651] iwlwifi :01:00.0: 0x0001 
| uCode revision type
Dec 30 21:35:56 schramm kernel: [ 1364.091656] iwlwifi :01:00.0: 0x001D 
| uCode version major
Dec 30 21:35:56 schramm kernel: [ 1364.091660] iwlwifi :01:00.0: 0x00095007 
| uCode version minor
Dec 30 21:35:56 schramm kernel: [ 1364.091665] iwlwifi :01:00.0: 0x0210 
| hw version
Dec 30 21:35:56 schramm kernel: [ 1364.091669] iwlwifi :01:00.0: 0x00C89200 
| board version
Dec 30 21:35:56 schramm kernel: [ 1364.091674] iwlwifi :01:00.0: 0x0072001C 
| hcmd
Dec 30 21:35:56 schramm kernel: [ 1364.091678] iwlwifi :01:00.0: 0x24022080 
| isr0
Dec 30 21:35:56 schramm kernel: [ 1364.091682] iwlwifi :01:00.0: 0x 
| isr1
Dec 30 21:35:56 schramm kernel: [ 1364.091686] iwlwifi :01:00.0: 0x000A 
| isr2
Dec 30 21:35:56 schramm kernel: [ 1364.091690] iwlwifi :01:00.0: 0x004134C0 
| isr3
Dec 30 21:35:56 schramm kernel: [ 1364.091694] iwlwifi :01:00.0: 0x 
| isr4
Dec 30 21:35:56 schramm kernel: [ 1364.091699] iwlwifi :01:00.0: 0x050B001C 
| last cmd Id
Dec 30 21:35:56 schramm kernel: [ 1364.091703] iwlwifi :01:00.0: 0x 
| wait_event
Dec 30 21:35:56 schramm kernel: [ 1364.091708] iwlwifi :01:00.0: 0x00D4 
| l2p_control
Dec 30 21:35:56 schramm kernel: [ 1364.091712] iwlwifi :01:00.0: 0x00018030 
| l2p_duration
Dec 30 21:35:56 schramm kernel: [ 1364.091717] iwlwifi :01:00.0: 0x0007 
| l2p_mhvalid
Dec 30 21:35:56 schramm kernel: [ 1364.091721] iwlwifi :01:00.0: 0x0081 
| l2p_addr_match
Dec 30 21:35:56 schramm kernel: [ 1364.091725] iwlwifi :01:00.0: 0x0007 
| lmpm_pmg_sel
Dec 30 21:35:56 schramm kernel: [ 1364.091730] iwlwifi :01:00.0: 0x29102230 
| timestamp
Dec 30 21:35:56 schramm kernel: [ 1364.091734] iwlwifi :01:00.0: 0x2030 
| flow_handler
Dec 30 21:35:56 schramm kernel: [ 1364.091744] ieee80211 phy0: Hardware restart 
was requested
Dec 30 21:35:56 schramm kernel: [ 1364.091790] iwlwifi :01:00.0: FW Error 
notification: type 0x cmd_id 0x1C
Dec 30 21:35:56 schramm kernel: [ 1364.091795] iwlwifi :01:00.0: FW Error 
notification: seq 0x0072 service 0x001C
Dec 30 21:35:56 schramm kernel: [ 1364.091800] iwlwifi :01:00.0: FW Error 
notification: timestamp 0x509408DC
Dec 30 21:35:56 schramm kernel: [ 1364.196558] [ cut here 
]

Any help appreciated as Ubuntu is my only OS.

-- 
You received 

[Kernel-packages] [Bug 1531653] Re: Macbook Pro Retina 11, 1 SD Card Reader Doesn't Work

2017-12-30 Thread Randy Syring
FWIW, I recently got a new computer and finally took the MBP into Apple
to run some diagnostics.  The internal hardware diagnostics never found
anything wrong.  However, when I took it to Apple, they had some more
advanced diagnostics that immediately identified a problem with my SD
card reader.  Interesting that the reader still worked with MacOS.

I'm giving the laptop to my son who wants to run MacOS and not Linux, so
I won't be able to contribute to this issue anymore.  Thanks to those
who put effort into it.

-- 
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/1531653

Title:
  Macbook Pro Retina 11,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Macbook Pro (MBP) Retina 11,1 with an SD card reader that
  will not work.

  The SD card reader:

  * has device code 05ac:8406
  * does work in OS X.
  * does not work in SystemRescueCD running kernel 3.14.56-std461-amd64
  - I have a friend with an identical Macbook Pro and his SD card reader 
does work in SystemRescueCD
  * Does not show up in lsusb
  * Does not display any messages in dmesg when an SD card is inserted
  * Device 05ac:8406 does not show up in dmesg
  * Does not work in kernel 4.2.0-22.27~14.04.1.  All issues reported here seem 
to be the same regardless if I use 3.13 or 4.2.
  * Uses the following drivers on my friends MBP: sd, usb-storage, usb, xhci_hcd

  The last point made me look closer at the xhci_hcd logs:

  rsyring@loftex:~$ dmesg | grep xhci_hcd
  [2.681478] xhci_hcd :00:14.0: xHCI Host Controller
  [2.681498] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 1
  [2.681589] xhci_hcd :00:14.0: cache line size of 256 is not supported
  [2.681607] xhci_hcd :00:14.0: irq 63 for MSI/MSI-X
  [2.681755] usb usb1: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [2.682098] xhci_hcd :00:14.0: xHCI Host Controller
  [2.682115] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 2
  [2.682219] usb usb2: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [3.980423] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
  [9.352422] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   14.560476] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   20.549170] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   25.757227] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   26.129482] usb 1-1: new high-speed USB device number 2 using xhci_hcd
  [   26.321707] usb 1-3: new full-speed USB device number 3 using xhci_hcd
  [   26.505802] usb 1-5: new full-speed USB device number 4 using xhci_hcd
  [   26.603224] usb 2-1.1: new SuperSpeed USB device number 6 using xhci_hcd
  [   26.754245] usb 1-1.2: new low-speed USB device number 5 using xhci_hcd
  [   26.954315] usb 1-1.4: new low-speed USB device number 6 using xhci_hcd
  [   27.050323] usb 1-3.1: new full-speed USB device number 7 using xhci_hcd
  [   27.142383] usb 1-3.2: new full-speed USB device number 8 using xhci_hcd
  [   27.234476] usb 1-3.3: new full-speed USB device number 9 using xhci_hcd
  [   81.685139] usb 1-1.4: new low-speed USB device number 10 using xhci_hcd

  The "Timeout while waiting" messages are suspicious to me.  dmesg on
  my friend's MBP  does not show those messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-57-generic 3.13.0-57.95
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rsyring5051 F pulseaudio
   /dev/snd/controlC0:  rsyring5051 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Jan  6 17:57:28 2016
  HibernationDevice: RESUME=UUID=8b8a41c8-2030-4f92-b7d6-1143a081ec85
  InstallationDate: Installed on 2014-02-15 (690 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \vmlinuz-3.13.0-57-generic.efi.signed root=ZFS=/ROOT ro 
libata.force=noncq 
cryptopts=target=cryptdev,source=/dev/disk/by-uuid/6993c5ec-7308-420d-bbe2-1ed18c15e2bc,discard
 boot=zfs initrd=\initrd.img-3.13.0-57-generic
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-57-generic N/A
   linux-backports-modules-3.13.0-57-generic  N/A
   linux-firmware 1.127.19
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-21 (534 days ago)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B16.1509081438
  dmi.board.asset.tag: 

[Kernel-packages] [Bug 1720263] Re: BUG: unable to handle kernel paging request at ffffffffffffffe1

2017-12-30 Thread Joe Farkas
similar. 
constantly getting kernel OOPS 
BUG: unable to handle kernel paging request at 9b9deffdaffc
Oops: 0002 [#1] SMP
Running Ubuntu 17.10 release
Computer:
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
CPU(s):  4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):   1
NUMA node(s):1
Vendor ID:   GenuineIntel
CPU family:  6
Model:   15
Model name:  Intel(R) Core(TM)2 Quad CPUQ6700  @ 2.66GHz
Stepping:11
CPU MHz: 1600.000
CPU max MHz: 2667.
CPU min MHz: 1600.
BogoMIPS:5333.55
Virtualization:  VT-x
L1d cache:   32K
L1i cache:   32K
L2 cache:4096K
NUMA node0 CPU(s):   0-3
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm 
constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi 
flexpriority dtherm

Kernel log, entire session from kernel start to crash:
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] random: get_random_bytes 
called from start_kernel+0x42/0x4e1 with crng_init=0
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] Linux version 
4.13.0-21-generic (buildd@lgw01-amd64-037) (gcc version 7.2.0 (Ubuntu 
7.2.0-8ubuntu3)) #24-Ubuntu SMP Mon Dec 18 17:29:16 UTC 2017 (Ubuntu 
4.13.0-21.24-generic 4.13.13)
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=1973b1e0-e868-4a12-bf92-da56276a6dce ro quiet splash vt.handoff=7
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] KERNEL supported cpus:
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00]   Intel GenuineIntel
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00]   AMD AuthenticAMD
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00]   Centaur CentaurHauls
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] x86/fpu: x87 FPU will 
use FXSAVE
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] e820: BIOS-provided 
physical RAM map:
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] BIOS-e820: [mem 
0x-0x0009f7ff] usable
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] BIOS-e820: [mem 
0x0009f800-0x0009] reserved
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] BIOS-e820: [mem 
0x000f-0x000f] reserved
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] BIOS-e820: [mem 
0x0010-0xbfed] usable
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] BIOS-e820: [mem 
0xbfee-0xbfee1fff] ACPI NVS
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] BIOS-e820: [mem 
0xbfee2000-0xbfee] ACPI data
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] BIOS-e820: [mem 
0xbfef-0xbfef] reserved
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] BIOS-e820: [mem 
0xf400-0xf7ff] reserved
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] BIOS-e820: [mem 
0xfec0-0x] reserved
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] BIOS-e820: [mem 
0x0001-0x00013fff] usable
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] NX (Execute Disable) 
protection: active
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] random: fast init done
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] SMBIOS 2.4 present.
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] DMI: Gigabyte Technology 
Co., Ltd. EP43T-S3L/EP43T-S3L, BIOS F7 07/05/2010
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] tsc: Fast TSC 
calibration using PIT
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] e820: update [mem 
0x-0x0fff] usable ==> reserved
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] e820: remove [mem 
0x000a-0x000f] usable
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] e820: last_pfn = 
0x14 max_arch_pfn = 0x4
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] MTRR default type: 
uncachable
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] MTRR fixed ranges 
enabled:
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00]   0-9 write-back
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00]   A-B uncachable
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00]   C-CCFFF 
write-protect
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00]   CD000-E uncachable
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00]   F-F 
write-through
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00] MTRR variable ranges 
enabled:
Dec 30 10:46:18 horse-EP43T-S3L kernel: [0.00]   0 base 0 

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Davide Prati
#396

I'm connected the laptop with an ethernet cable, but the problem is secure boot.
Did you try it with secure boot enabled?

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Alex Friis
#396

You need a wired connection to the LAN, when doing a PXE-netboot!
For your information, I have succeeded booting another (healthy) PC just for 
testing purposes. For this I used the free win-version of 
https://www.aomeitech.com/pxe/pxe-boot-software.html.
Unfortunately my (sick) Lenovo Z50-70 has PXE-boot disabled in BIOS pr. 
default. So PXE-boot is not my salvator. :-(

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1740614] Re: lost bios

2017-12-30 Thread axt
*** This bug is a duplicate of bug 1734147 ***
https://bugs.launchpad.net/bugs/1734147

** This bug has been marked a duplicate of bug 1734147
   Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

-- 
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/1740614

Title:
  lost bios

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My portable hp pavilion 14 has lost the bios when i have actualized to ubuntu 
17.10. Some solution?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740614/+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


[Kernel-packages] [Bug 1740590] Re: package linux-image-extra-4.4.0-63-generic 4.4.0-63.84 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

2017-12-30 Thread axt
First: You should _not_ use tools like as bleachbit.

"Installed on 2016-10-01 (454 days ago)"...I think, you don't have free
space...and it makes more sense, you come into the german forum
https://forum.ubuntuusers.de/forum/installieren-aktualisieren/.

-- 
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/1740590

Title:
  package linux-image-extra-4.4.0-63-generic 4.4.0-63.84 failed to
  install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It's a message, pop up sen on the re lock in.
  I don't know why the system generated that message.
  I had the root full and cleaned with BleachBit as root.
  After the cleaning other update works proper.
  I'm not the big man on ubuntu and need help, if fixings must be done, 
manually.
  all the best
  Uwe Broeren

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-63-generic 4.4.0-63.84
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uwe1908 F pulseaudio
   /dev/snd/pcmC1D0p:   uwe1908 F...m pulseaudio
   /dev/snd/controlC1:  uwe1908 F pulseaudio
  Date: Sat Dec 30 06:58:00 2017
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  HibernationDevice: RESUME=UUID=c87c90b0-3a7b-4d5d-a476-bcc76ec8abce
  InstallationDate: Installed on 2016-10-01 (454 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Wortmann_AG TERRA_PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-63-generic 4.4.0-63.84 failed to 
install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd06/16/2014:svnWortmann_AG:pnTERRA_PC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: TERRA_PC
  dmi.product.version: System Version
  dmi.sys.vendor: Wortmann_AG

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740590/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Davide Prati
#386
I tried boot into linux via netboot but secure boot forbids me from install 
anything. I can boot into grub but "ls -l" command to get UUID doesn't work for 
the same reason.

Can you tell us how to boot into linux to get UUID with secure boot
enabled? Or do you have an alternative solution?

#395
I think the biggest problem is how to get this UUID if we cannot boot in any 
way..
However i can boot ssd in another pc as first drive so i can use linux to 
change UUID when i'll discover it.


Hope in you guys..

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1740614] Re: lost bios

2017-12-30 Thread axt
You don't have a BIOS, but a UEFI.

→ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147

-- 
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/1740614

Title:
  lost bios

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My portable hp pavilion 14 has lost the bios when i have actualized to ubuntu 
17.10. Some solution?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740614/+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


[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2017-12-30 Thread Dan Streetman
Happy Holidays!

After some more investigation I've changed the patch to what I think is
a more appropriate fix, though it will only fix cases where the
container hang is due to a TCP kernel socket hanging while trying to
close itself (waiting for FIN close sequence, which will never complete
since the container interfaces are shut down).

I also added some kernel-owned socket debug so in case of another
'waiting for lo to become free' hang it will print out all open kernel
sockets along with their family, state, and creating function, which
hopefully will help debug more, assuming my TCP patch doesn't cover all
cases.

The same ppa has been updated with the new patches:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1711407

And if you would like to see the patches they're in my lp git repo:
https://code.launchpad.net/~ddstreet/+git/linux/+ref/lp1711407-tcp-check-xenial

Can those able to reproduce this bug please test with any of the kernels
from that ppa?  There is some debug output to let you track container
net namespace lifetimes; you should see log entries like:

[  229.134701] net_alloc: created netns 8800b99cc980
...
[  438.930538] net_free: freed netns 8800b99cc980

you can track the alloc and free of each container that way, to make
sure none of them are remaining open (i.e. leaking).  Note that netns
addresses may be re-used, so you may see something like:

[  228.797533] net_free: freed netns 8800baab1880
...
[  352.000520] net_alloc: created netns 8800baab1880

that's fine and not a problem.

Also, if you see this line in the logs:

[   22.149194] TCP: our netns is exiting

that indicates the patch to fix this problem detected the problem and
closed the hanging TCP socket.

If you can reproduce the issue with any of those test kernels, please
post one of the socket debug output sections that look like:

[  410.258505] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[  410.261385] netdev_wait_allrefs: waiting on sk 8800b9662800 family 16 
state 7 creator __netlink_kernel_create+0x6d/0x260
[  410.261390] netdev_wait_allrefs: waiting on sk 8800b9662000 family 16 
state 7 creator __netlink_kernel_create+0x6d/0x260
[  410.261408] netdev_wait_allrefs: waiting on sk 8800b9661000 family 16 
state 7 creator __netlink_kernel_create+0x6d/0x260
[  410.261411] netdev_wait_allrefs: waiting on sk 8800baeb4000 family 16 
state 7 creator __netlink_kernel_create+0x6d/0x260
[  410.261416] netdev_wait_allrefs: waiting on sk 8800b9699680 family 2 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261420] netdev_wait_allrefs: waiting on sk 8800bb3743c0 family 2 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261423] netdev_wait_allrefs: waiting on sk 8800bb374780 family 2 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261426] netdev_wait_allrefs: waiting on sk 8800bb374b40 family 2 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261430] netdev_wait_allrefs: waiting on sk 8800bb374f00 family 2 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261433] netdev_wait_allrefs: waiting on sk 8800bb3752c0 family 2 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261436] netdev_wait_allrefs: waiting on sk 8800bb375680 family 2 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261439] netdev_wait_allrefs: waiting on sk 8800bb375a40 family 2 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261442] netdev_wait_allrefs: waiting on sk 8800bb375e00 family 2 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261446] netdev_wait_allrefs: waiting on sk 8800baeb1000 family 16 
state 7 creator __netlink_kernel_create+0x6d/0x260
[  410.261449] netdev_wait_allrefs: waiting on sk 8800baeb2800 family 16 
state 7 creator __netlink_kernel_create+0x6d/0x260
[  410.261452] netdev_wait_allrefs: waiting on sk 8800b9f18000 family 10 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261456] netdev_wait_allrefs: waiting on sk 8800b9f18480 family 10 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261459] netdev_wait_allrefs: waiting on sk 8800b9f18900 family 10 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261462] netdev_wait_allrefs: waiting on sk 8800b9f18d80 family 10 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261465] netdev_wait_allrefs: waiting on sk 8800b9f19200 family 10 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261469] netdev_wait_allrefs: waiting on sk 8800b9f19680 family 10 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261472] netdev_wait_allrefs: waiting on sk 8800b9f19b00 family 10 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261475] netdev_wait_allrefs: waiting on sk 8800b9f19f80 family 10 
state 7 creator inet_ctl_sock_create+0x35/0x80
[  410.261478] netdev_wait_allrefs: waiting on sk 8800baeb7000 family 16 
state 7 creator __netlink_kernel_create+0x6d/0x260
[  410.261510] 

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread edenbar
Hi i connect my ssd back lenovo create pxe server but lenovo boot write
efi nerwork boot failed...i open fdisk on pc when server run and not see
uuid of lenovo..what can i do?

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Alex Friis
ad #386.

Would it be possible to change the UUID of the EFI partition, when having the 
disk in question mounted/connected as an external drive?
Fon instance connecting the disk via a SATA-USB connector and then change the 
UUID with the windows "diskpart" command? Doing something like the following.

DISKPART> list disk 
DISKPART> selectdisk 
DISKPART> uniqueid disk
DISKPART> uniqueid disk ID=[NEW SIGNATURE]

 or is this completely rubbish?

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1740614] Missing required logs.

2017-12-30 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1740614

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => 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/1740614

Title:
  lost bios

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My portable hp pavilion 14 has lost the bios when i have actualized to ubuntu 
17.10. Some solution?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740614/+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


[Kernel-packages] [Bug 1740614] [NEW] lost bios

2017-12-30 Thread Francesc Llopis Malonda
Public bug reported:

My portable hp pavilion 14 has lost the bios when i have actualized to ubuntu 
17.10. Some solution?
Thanks

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1740614

Title:
  lost bios

Status in linux package in Ubuntu:
  New

Bug description:
  My portable hp pavilion 14 has lost the bios when i have actualized to ubuntu 
17.10. Some solution?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740614/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Francesco
I did not understand one thing: you can access the bios but does not
save the settings or you can not log in (like me)?

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread edenbar
Hi ok i install ubuntu 16.04 on external ssd pur kernal 4.14.9 now pls
how i use fdisk to change uuid?

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Andrés Alcarraz
@razimantv Thanks but I wanted a fresh install. Luckly I didn't have the
problem, just installed 17.10 and upgraded kernel ASAP. Maybe lenovo
legion Y520 is not affected by the bug at all, or maybe I just was
lucky.

I took the risk since it sounded that in case something went wrong I
could just recover the BIOS by upgrading the kernel.

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1159306] Re: WARNING: at /build/buildd/linux-3.8.0/net/wireless/sme.c:642 cfg80211_roamed+0x9a/0xa0 [cfg80211]()

2017-12-30 Thread Vidar Braut Haarr
uname -a
Linux plantasjen 4.14.0-041400rc8-generic #201711052313 SMP Sun Nov 5 23:14:08 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

02:00.0 Network controller: Broadcom Limited BCM4360 802.11ac Wireless Network 
Adapter (rev 03)
Subsystem: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f740 (64-bit, non-prefetchable) [size=32K]
Memory at f720 (64-bit, non-prefetchable) [size=2M]
Capabilities: 
Kernel driver in use: wl
Kernel modules: bcma, wl

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

Title:
  WARNING: at /build/buildd/linux-3.8.0/net/wireless/sme.c:642
  cfg80211_roamed+0x9a/0xa0 [cfg80211]()

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  I do not know how long this has been going on, as of now. But I looked
  today at /var/log/syslog, it it was pretty much *only* this warning +
  stacktrace, one after the other, every few seconds. This is the first
  occurence of it, from a saved syslog:

  Mar 22 18:29:32 xango3 kernel: [13498.800669] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm)
  Mar 22 18:29:32 xango3 kernel: [13498.800672] cfg80211:   (517 KHz - 
525 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Mar 22 18:29:32 xango3 kernel: [13498.800675] cfg80211:   (5735000 KHz - 
5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm)
  Mar 22 18:29:32 xango3 NetworkManager[1649]:  (eth1): supplicant 
interface state: disconnected -> scanning
  Mar 22 18:29:35 xango3 kernel: [13501.484571] net_ratelimit: 24 callbacks 
suppressed
  Mar 22 18:29:36 xango3 wpa_supplicant[1777]: eth1: Trying to associate with 
00:7f:28:e9:f9:fb (SSID='beth-el2' freq=2462 MHz)
  Mar 22 18:29:36 xango3 NetworkManager[1649]:  (eth1): supplicant 
interface state: scanning -> associating
  Mar 22 18:29:36 xango3 wpa_supplicant[1777]: eth1: CTRL-EVENT-ASSOC-REJECT 
status_code=16
  Mar 22 18:29:37 xango3 NetworkManager[1649]:  (eth1): roamed from BSSID 
00:7F:28:E9:F9:FB (beth-el2) to (none) ((none))
  Mar 22 18:29:41 xango3 kernel: [13507.164978] [ cut here 
]
  Mar 22 18:29:41 xango3 kernel: [13507.165031] WARNING: at 
/build/buildd/linux-3.8.0/net/wireless/sme.c:642 cfg80211_roamed+0x9a/0xa0 
[cfg80211]()
  Mar 22 18:29:41 xango3 kernel: [13507.165034] Hardware name: Latitude E6410
  Mar 22 18:29:41 xango3 kernel: [13507.165036] Modules linked in: 
usb_storage(F) snd_usb_audio snd_usbmidi_lib hid_generic asix usbnet 
ebtable_nat(F) ebtables(F) xt_CHECKSUM(F) iptable_mangle(F) pci_stub 
vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) ipt_MASQUERADE(F) 
iptable_nat(F) nf_nat_ipv4(F) bridge(F) stp(F) llc(F) dm_crypt(F) 
ip6t_REJECT(F) xt_hl(F) ip6t_rt(F) nf_conntrack_ipv6(F) nf_defrag_ipv6(F) 
ipt_REJECT(F) xt_LOG(F) bnep xt_limit(F) xt_tcpudp(F) xt_addrtype(F) rfcomm 
nf_conntrack_ipv4(F) nf_defrag_ipv4(F) uvcvideo xt_state(F) videobuf2_vmalloc 
videobuf2_memops ip6table_filter(F) ip6_tables(F) videobuf2_core 
snd_hda_codec_hdmi nf_conntrack_netbios_ns(F) videodev 
nf_conntrack_broadcast(F) nf_nat_ftp(F) nf_nat(F) joydev(F) lib80211_crypt_tkip 
nf_conntrack_ftp(F) wl(POF) nf_conntrack(F) snd_hda_codec_idt iptable_filter(F) 
ip_tables(F) snd_hda_intel x_tables(F) snd_hda_codec binfmt_misc(F) 
snd_hwdep(F) snd_pcm(F) coretemp snd_page_alloc(F) snd_seq_midi(F) 
snd_seq_midi_event(F) kvm_intel snd_rawmidi
  Mar 22 18:29:41 xango3 kernel: (F) snd_seq(F) lib80211 kvm snd_seq_device(F) 
snd_timer(F) dell_laptop cfg80211 btusb snd(F) dcdbas bluetooth dell_wmi 
soundcore(F) psmouse(F) ppdev(F) sparse_keymap microcode(F) mac_hid lpc_ich 
tpm_tis intel_ips serio_raw(F) parport_pc(F) lp(F) parport(F) hid_logitech_dj 
usbhid hid nouveau mxm_wmi wmi ghash_clmulni_intel(F) aesni_intel(F) 
aes_x86_64(F) xts(F) lrw(F) gf128mul(F) ablk_helper(F) cryptd(F) video(F) 
i2c_algo_bit ttm drm_kms_helper ahci(F) libahci(F) drm sdhci_pci firewire_ohci 
firewire_core sdhci e1000e(F) crc_itu_t(F)
  Mar 22 18:29:41 xango3 kernel: [13507.165164] Pid: 1073, comm: 
wl_event_handle Tainted: PF  O 3.8.0-13-generic #23-Ubuntu
  Mar 22 18:29:41 xango3 kernel: [13507.165167] Call Trace:
  Mar 22 18:29:41 xango3 kernel: [13507.165177]  [] 
warn_slowpath_common+0x7f/0xc0
  Mar 22 18:29:41 xango3 kernel: [13507.165182]  [] 
warn_slowpath_null+0x1a/0x20
  Mar 22 18:29:41 xango3 kernel: [13507.165207]  [] 
cfg80211_roamed+0x9a/0xa0 [cfg80211]
  Mar 22 18:29:41 xango3 kernel: [13507.165260]  [] 
wl_bss_connect_done.isra.20+0x115/0x1c0 [wl]
  Mar 22 18:29:41 xango3 kernel: [13507.165305]  [] 
wl_notify_connect_status+0x345/0x460 [wl]
  Mar 22 18:29:41 xango3 kernel: [13507.165350]  [] 
wl_event_handler+0x55/0x1f0 [wl]
  Mar 22 18:29:41 xango3 kernel: [13507.165395]  [] ? 
wl_notify_scan_status+0x340/0x340 [wl]
  Mar 22 18:29:41 xango3 kernel: 

[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

2017-12-30 Thread Bug Watch Updater
Launchpad has imported 15 comments from the remote bug at
https://bugzilla.opensuse.org/show_bug.cgi?id=1058870.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-09-15T13:31:31+00:00 Axel Braun wrote:

Created attachment 740759
Screenshot

Did an update on an old ASUS eeePC to the above TW. With Kernel 4.13.1 2/3 of 
the screen is black. Switching back to Kernel 4.12.11 fixes the problem. See 
attached screenshot
Graphics chip is a Intel mobile GM945 GM
Let me know if I can provide further information

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/0


On 2017-09-18T14:28:03+00:00 Ada-lovelace wrote:

I have the same problem with a Lenovo ThinkPad 13 (Ultrabook) with Intel
Come i5. I receive a error message with "Failed to start Setup Virtual
System Console". After that I have a black window.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/1


On 2017-09-18T14:32:45+00:00 Ada-lovelace wrote:

I have the same problem with a Lenovo ThinkPad S2 (Ultrabook) with Intel
Core i5. I receive a error message with "Failed to start Setup Virtual
System Console". After that I have a black window.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/2


On 2017-09-18T16:03:50+00:00 Ada-lovelace wrote:

My graphic card is a Intel(R) Graphics 520.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/3


On 2017-09-19T14:15:32+00:00 Jslaby-h wrote:

Could you attach output of dmesg?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/4


On 2017-09-20T06:09:49+00:00 Axel Braun wrote:

Created attachment 741173
dmesg

It should be noted that the screen distortion appears in runlevel 3 as
well. so it is not an issue of the video driver!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/5


On 2017-09-21T07:27:27+00:00 Jslaby-h wrote:

Hmm...

Can you create a bug at https://bugs.freedesktop.org -- product DRI,
component DRM/Intel?

plane B assertion failure, should be off on pipe B but is still active
[ cut here ]
WARNING: CPU: 1 PID: 259 at ../drivers/gpu/drm/i915/intel_display.c:1252 
assert_planes_disabled+0x128/0x140 [i915]
Modules linked in: ata_piix i915(+) serio_raw i2c_algo_bit uhci_hcd ehci_pci 
drm_kms_helper ehci_hcd syscopyarea sysfillrect sysimgblt usbcore fb_sys_fops 
drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua
CPU: 1 PID: 259 Comm: systemd-udevd Not tainted 4.13.1-1-pae #1
Hardware name: ASUSTeK Computer INC. 901/901, BIOS 190303/17/2009
task: f4ae4700 task.stack: f4b3c000
EIP: assert_planes_disabled+0x128/0x140 [i915]
EFLAGS: 00010286 CPU: 1
EAX: 0046 EBX: f4bbc000 ECX: f71eb340 EDX: f71e486c
ESI: 0001 EDI: 0001 EBP: f4b3dbe4 ESP: f4b3dbc8
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
CR0: 80050033 CR2: b7152000 CR3: 34aeca60 CR4: 06f0
Call Trace:
 ? intel_disable_pipe+0x45/0x220 [i915]
 ? i9xx_crtc_disable+0x5c/0x3a0 [i915]
 ? drm_connector_list_iter_next+0x71/0xa0 [drm]
 ? drm_atomic_add_affected_connectors+0xd0/0xf0 [drm]
 ? intel_crtc_disable_noatomic+0xb5/0x290 [i915]
 ? intel_modeset_setup_hw_state+0xa58/0xc40 [i915]
 ? intel_modeset_setup_hw_state+0xa85/0xc40 [i915]
 ? intel_modeset_init+0x4d1/0xea0 [i915]
 ? intel_setup_gmbus+0x1e1/0x270 [i915]
 ? i915_driver_load+0xa4c/0x1330 [i915]
 ? local_pci_probe+0x35/0x80
 ? pci_device_probe+0x158/0x170
 ? driver_probe_device+0x2b9/0x410
 ? __driver_attach+0x99/0xe0
 ? driver_probe_device+0x410/0x410
 ? bus_for_each_dev+0x4f/0x80
 ? driver_attach+0x19/0x20
 ? driver_probe_device+0x410/0x410
 ? bus_add_driver+0x187/0x230
 ? 0xf8306000
 ? driver_register+0x56/0xd0
 ? 0xf8306000
 ? do_one_initcall+0x46/0x170
 ? do_init_module+0x21/0x1d9
 ? do_init_module+0x50/0x1d9
 ? load_module+0x1435/0x1980
 ? SyS_finit_module+0x79/0xc0
 ? do_fast_syscall_32+0x71/0x150
 ? entry_SYSENTER_32+0x4e/0x7c
Code: ff 83 c4 10 e9 44 ff ff ff 57 68 a0 91 29 f8 e8 cc 8c 2d e0 0f ff 58 5a 
e9 30 ff ff ff ff 75 f0 50 68 d8 91 29 f8 e8 b5 8c 2d e0 <0f> ff 83 c4 0c e9 3e 
ff ff ff 8d b4 26 00 00 00 00 8d bc 27 00
---[ end trace 0e7d08f54709149f ]---

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/comments/6


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Hernán Alvarez
Hi, I have a Baytrail-based Compal ZAW70 (sold under the brand "Kelyx"
in Argentina) which was affected by this bug. I installed using ukuu
both 4.14.9 and 4.14.10 kernels without resolving the issue, the UEFI
settings remain read only.

Just loading the updated SPI driver resolves the issue or there is some
command to be run?

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Davide Prati
Thanks Artur (radium88) #386 for the precious information. I'll try to follow 
your steps and i'll report you as soon as possible.
Hope the bios will let me boot from PXE over network without problems.

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Raziman T V
@alcarraz (#355): You can always install 17.04 and upgrade to 17.10.
This bypasses the problematic kernel versions, that is what I did.

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread edenbar
Michal D did you use win2usb? Install windos on external hdd then put
him internal?

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Michal D.
It destroyed my BIOS on Lenovo Y50-70. Unable to change BIOS settings
nor boot through USB devices. I installed windows through bootable
partition on another SSD luckily.

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Artur
You can't just install system on clean hdd from another pc, UUID of EFI 
partition will be different. UEFI attempts to boot only from partition with 
specific UUID. 
For example:

root #efibootmgr -v

BootCurrent: 0002
Timeout: 3 seconds
BootOrder: 0003,0003,0002,,0004
Boot* CD/DVD Drive  BIOS(3,0,00)
Boot0001* Hard DriveBIOS(2,0,00)
Boot0002* Gentoo
HD(1,800,61800,6d98f360-cb3e-4727-8fed-5ce0c040365d)File(\EFI\boot\bootx64.efi)
Boot0003* Hard DriveBIOS(2,0,00)P0: ST1500DM003-9YN16G

6d98f360-cb3e-4727-8fed-5ce0c040365d - is UUID of EFI partition

After installation on another PC you need manually change UUID of EFI
partition via gdisk('x' command to enable additional options and after
that 'c' command - change UUID)

But you need determine what UUID you must set. I did that by booting my
system via PXE over network

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1740590] Status changed to Confirmed

2017-12-30 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

-- 
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/1740590

Title:
  package linux-image-extra-4.4.0-63-generic 4.4.0-63.84 failed to
  install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It's a message, pop up sen on the re lock in.
  I don't know why the system generated that message.
  I had the root full and cleaned with BleachBit as root.
  After the cleaning other update works proper.
  I'm not the big man on ubuntu and need help, if fixings must be done, 
manually.
  all the best
  Uwe Broeren

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-63-generic 4.4.0-63.84
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uwe1908 F pulseaudio
   /dev/snd/pcmC1D0p:   uwe1908 F...m pulseaudio
   /dev/snd/controlC1:  uwe1908 F pulseaudio
  Date: Sat Dec 30 06:58:00 2017
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  HibernationDevice: RESUME=UUID=c87c90b0-3a7b-4d5d-a476-bcc76ec8abce
  InstallationDate: Installed on 2016-10-01 (454 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Wortmann_AG TERRA_PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-63-generic 4.4.0-63.84 failed to 
install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd06/16/2014:svnWortmann_AG:pnTERRA_PC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: TERRA_PC
  dmi.product.version: System Version
  dmi.sys.vendor: Wortmann_AG

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740590/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread edenbar
Hi davide i have to same screen..when i chose somthing its write ubuntu
fail..and then no os pls insert os..but no boot works no cd no usb no
nothing..

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Dylan Dunn
I think I am affected by this as well. I tried to install 17.10 on my
Lenovo Flex 3 (I have the model number written somewhere) a little
before Thanksgiving, and now it doesn't save bios changes, boot to
anything (USB or otherwise), and it just flashes the Lenovo screen and
restarts itself every second. I have tried replacing the hard drive,
booting to Lenovo's recovery partition which failed, and replacing the
CMOS battery. Whenever I try booting via boot menu, every thing I try
throws up the same "[name of boot device] boot failed." I have no idea
what to do at this point. If anyone has any suggestions, I'm all ears.

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1740590] [NEW] package linux-image-extra-4.4.0-63-generic 4.4.0-63.84 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

2017-12-30 Thread Uwe Broeren
Public bug reported:

It's a message, pop up sen on the re lock in.
I don't know why the system generated that message.
I had the root full and cleaned with BleachBit as root.
After the cleaning other update works proper.
I'm not the big man on ubuntu and need help, if fixings must be done, manually.
all the best
Uwe Broeren

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-63-generic 4.4.0-63.84
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  uwe1908 F pulseaudio
 /dev/snd/pcmC1D0p:   uwe1908 F...m pulseaudio
 /dev/snd/controlC1:  uwe1908 F pulseaudio
Date: Sat Dec 30 06:58:00 2017
ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
HibernationDevice: RESUME=UUID=c87c90b0-3a7b-4d5d-a476-bcc76ec8abce
InstallationDate: Installed on 2016-10-01 (454 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: Wortmann_AG TERRA_PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
RfKill:
 
SourcePackage: linux
Title: package linux-image-extra-4.4.0-63-generic 4.4.0-63.84 failed to 
install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/16/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2001
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd06/16/2014:svnWortmann_AG:pnTERRA_PC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: TERRA_PC
dmi.product.version: System Version
dmi.sys.vendor: Wortmann_AG

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
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/1740590

Title:
  package linux-image-extra-4.4.0-63-generic 4.4.0-63.84 failed to
  install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in linux package in Ubuntu:
  New

Bug description:
  It's a message, pop up sen on the re lock in.
  I don't know why the system generated that message.
  I had the root full and cleaned with BleachBit as root.
  After the cleaning other update works proper.
  I'm not the big man on ubuntu and need help, if fixings must be done, 
manually.
  all the best
  Uwe Broeren

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-63-generic 4.4.0-63.84
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uwe1908 F pulseaudio
   /dev/snd/pcmC1D0p:   uwe1908 F...m pulseaudio
   /dev/snd/controlC1:  uwe1908 F pulseaudio
  Date: Sat Dec 30 06:58:00 2017
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  HibernationDevice: RESUME=UUID=c87c90b0-3a7b-4d5d-a476-bcc76ec8abce
  InstallationDate: Installed on 2016-10-01 (454 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Wortmann_AG TERRA_PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-63-generic 4.4.0-63.84 failed to 
install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Davide Prati
i also tried to upgrade kernel with ukuu, after the reboot on the
working computer ukuu says 4.14.9 is running. Moving ssd back to lenovo
it always show ubuntu boot failed. in attachment a screen of my bios
boot page.

** Attachment added: "bios boot page"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+attachment/5029071/+files/WhatsApp%20Image%202017-12-30%20at%2011.54.05.jpeg

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Alex Friis
380+381
Thx for you feedback. I'll try it myself and return, if it could be of any help!
Feel free to PM me.

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread edenbar
Hi davide...same problem as you... pls notice me if you fix this...i
lost hope...try everything..

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Davide Prati
Hi alexfriis,
i have the same problem of user's post #375. I tried to remove my ssd to 
install ubuntu from another one.
When i move back my sdd to the lenovo laptop it keeps saying: ubuntu boot 
failed. In boot options i have the voice "ubuntu" in first place, so i don't 
know why it doesn't boot.

Other ideas?

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread edenbar
Hi i need the same laptop model? Or just same linux version? Or install
ubuntu 16.04 ? I create it by ubuntu and install in external hdd ? Tnx

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Alex Friis
Hi edenbar2...@gmail.com.

What about moving your HDD temporarily to another PC - one eqvivalent to
your 'corrupted' one - and then install a Ubuntu with Kernel 4.14.9.
Moving the HDD back to the original should 'cure' you - give it a try!

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread Alex Friis
#376
Didn't you read my PM?

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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


[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-30 Thread edenbar
708 people here and even 1 cant help me???
Can someone help just to tell how to fix this problem if i allready format my 
hard disk..?

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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