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
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
*** 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
Grr...sry about my handling mistakes. ;)
--
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/1740229
Title:
Ubuntu 17.10 killed my notebook
Status in linux package in Ubuntu:
Incomplete
You confuse a bug tracker with a support forum, for example https://ubuntuforums.org/;>ubuntuforums.org. There better help
for the individual user is possible, if you give useful information.
But...maybe you have https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147;>this
issue. You should
You confuse a bug tracker with a support forum, for example
https://ubuntuforums.org/. There better help for the individual user is
possible, if you give useful information.
But...maybe you have this issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147. You should
check your UEFI.
@Joseph Salisbury
No. That alone can _not_ solve the problem.
When starting the stick or the DVD, the option must be set before _and_
after the double dash:
" forcepae -- forcepae"
@Wesley Keener, execute this commands:
sudo sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="forcepae"/g'
What a cruel editor. The 1st is 1 line:
sudo sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="forcepae"/g'
/etc/default/grub
--
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/1740906
#482
http://kernel.ubuntu.com/sru/versions.html
4.13.0-17.20 → dangerous, a corrupt (!) version.
--
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:
corrupted BIOS due to
> What can I do with Lenovo Y50-70 with Windows 10 Only? Ubuntu is
removed.
olekcz, hm, do you have _this_ UEFI issue? I suppose, (re-)flashing of
the last UEFI version (https://tinyurl.com/ycq52ba5) could solve the
problem, it's a Windows executable.
--
You received this bug notification
@Ahmed Ibrahim (n0krashy), I wrote "suppose" and "could". I don't have
this notebook.
--
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
Plz post the output of:
cat /etc/default/grub | grep GRUB_CMDLINE_LINUX
--
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/1740906
Title:
package linux-image-4.13.0-21-generic (not
If it's the kernel bug, Bionic will not help. Additionally the
corrupting Artful kernel is still integrated in the image.
--
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/1740229
Title:
I mean Win 1803 of course, "1804" doesn't exist.
--
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:
corrupted BIOS due to Intel SPI bug in kernel
Status in Linux:
Unknown
I mean Win 1803 of course.
--
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:
corrupted BIOS due to Intel SPI bug in kernel
Status in Linux:
Unknown
Status in linux
#592, #602
@Robert R (roremich)
17.10 w/o .1 is *toxic* (and anyway EoS, with .1 also). Already the
first boot up changes the value. The UEFI is destroyed, so to speak.
Btw., that would not have happened in CSM mode instead UEFI mode.
Hard cheese, inform in advance.
Installing a clean kernel in
> dmi.bios.version: F4
> (...)
> dmi.board.name: B150M-D3H-CF
> dmi.board.vendor: Gigabyte Technology Co., Ltd.
At the first you should flash the current UEFI version F24g (!).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
> dmi.bios.date: 06/06/2008
> dmi.bios.vendor: LENOVO
> dmi.bios.version: 7LETB9WW (2.19 )
> (...)
> dmi.product.version: ThinkPad T61
At the first you should flash the current BIOS version 2.30-1.08 (!).
The Core 2 Duo has implemented the Intel64 extension. You should install
Bionic 64 bit
> Linux Mint 18.3 (Ubuntu 16.04.3)
At the first: Mint is *not* Ubuntu, it is only based on it with several
changes, additions and withheld packages.
As a basis I would always have flashed the last available BIOS/UEFI. But
216 is already on your Asus X451MA.
"r8169 can't disable aspm" (your
You use nouveau, but have set the boot option nomodeset. So it is your
fault.
Bionic with kernel 5.3.0-26 and nouveau work fine.
--
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/1860196
Btw., Vicky, if Win8 is already running, the first thing I would do
would be to flash the last available UEFI, unfortunately also almost 5
years old.
https://pcsupport.lenovo.com/de/en/products/laptops-and-
netbooks/lenovo-z-series-laptops/lenovo-z50-70/downloads/DS100528
--
You received this
> My default first boot device is Ubuntu and then windows and then USB
and network.. etc..
(...)
> I tried to run pratation magic.
How did you boot Partition Magic?
If this is on a DVD, the ODD must be before the HDD in the boot
sequence.
Then you could also just boot Focal64 for fixing.
--
Before you have to scrap the notebook...http://archive.ubuntu.com/ubuntu/dists/xenial-
updates/main/uefi/grub2-amd64/current/grubx64.efi.signed">http://archive.ubuntu.com/ubuntu/dists
/xenial-updates/main/uefi/grub2-amd64/current/grubx64.efi.signed is
much newer, but should also work.
--
You
Before you have to scrap the notebook:
http://archive.ubuntu.com/ubuntu/dists/xenial-
updates/main/uefi/grub2-amd64/current/grubx64.efi.signed is much newer,
but should also work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Vicky, your current issue has nothing to do with the UEFI issue in this
thread.
> I then select windows 8 and use windows 8.
Technically you only had to do an in-place upgrade to Win10.
This reliably ;-) overwrites Grub.
Officially, this has been possible free of charge for up to 1 year after
25 matches
Mail list logo
