Public bug reported:

Winbook TW802 - Intel Atom Tablet with UEFI Bios
64bit cpu / 32bit bootloader

Related models: TW700, TW800, TW801 & TW100
Recommend do not install V17.10.1 on those machines until issue resolved

Previous Single boot Ubuntu 16.04.1 installation NO Bios issues:
installed via isorespin from USB

New Single boot Ubuntu 17.10.1 installation caused Corrupted Bios:
installed via isorespin from USB
   uname -r = 4.13.0-32-generic
Corruption prevents Bios access to USB, so cannot boot ClonZilla to restore 
prior image
Ubuntu 17 boots to desktop but not fully functional: (issues are unrelated to 
this bug report)

WinBook Bios
Phoenix SecureCore Bios
Version 1.00 IA32
Build   11/24/2014

Can access BIOS with F2 during boot
But Bios hangs accessing "BOOT" tab that controls boot devices
Will not display & cannot select any boot device
Restoring Bios defaults does not fix issue

Attempted Fix:
Tried 17.10 "SPI" fix - bug #1734147
Neither method shown resolves the issue
after fix applied uname -r = 4.15.0-041500rc6-generic

Fix #1734147 creates other issues:
Bug #1734147 fix prevents access to grub during boot
prior to #1734147 fix,"shift" during boot opened grub menu
after fix, cannot open grub with "shift" or "c"

uninstalled the fix via method shown in #1734147
uname -r = 4.13.0-32-generic after #1734148 uninstalled & reboot

Gathering Info for this bug report
ubuntu-bug linux = gathers the information but;
V17 touchpad issues prevent sending the data
version.log & lspci-vnvn.log are attached.

Once USB is accessed, I can restore prior image

Regards.

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


** Tags: artful

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1750491/+attachment/5058643/+files/lspci-vnvn.log

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

Title:
  Ubuntu 17.10.1 UEFI Bios Corruption - WinBook TW802 Tablet

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Winbook TW802 - Intel Atom Tablet with UEFI Bios
  64bit cpu / 32bit bootloader

  Related models: TW700, TW800, TW801 & TW100
  Recommend do not install V17.10.1 on those machines until issue resolved

  Previous Single boot Ubuntu 16.04.1 installation NO Bios issues:
  installed via isorespin from USB

  New Single boot Ubuntu 17.10.1 installation caused Corrupted Bios:
  installed via isorespin from USB
     uname -r = 4.13.0-32-generic
  Corruption prevents Bios access to USB, so cannot boot ClonZilla to restore 
prior image
  Ubuntu 17 boots to desktop but not fully functional: (issues are unrelated to 
this bug report)

  WinBook Bios
  Phoenix SecureCore Bios
  Version       1.00 IA32
  Build 11/24/2014

  Can access BIOS with F2 during boot
  But Bios hangs accessing "BOOT" tab that controls boot devices
  Will not display & cannot select any boot device
  Restoring Bios defaults does not fix issue

  Attempted Fix:
  Tried 17.10 "SPI" fix - bug #1734147
  Neither method shown resolves the issue
  after fix applied uname -r = 4.15.0-041500rc6-generic

  Fix #1734147 creates other issues:
  Bug #1734147 fix prevents access to grub during boot
  prior to #1734147 fix,"shift" during boot opened grub menu
  after fix, cannot open grub with "shift" or "c"

  uninstalled the fix via method shown in #1734147
  uname -r = 4.13.0-32-generic after #1734148 uninstalled & reboot

  Gathering Info for this bug report
  ubuntu-bug linux = gathers the information but;
  V17 touchpad issues prevent sending the data
  version.log & lspci-vnvn.log are attached.

  Once USB is accessed, I can restore prior image

  Regards.

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

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

Reply via email to