I disagree to move this to invalid (Not only still I have that bug as
well), as it was already on triaged, hence a problem to be looked in.
Would it make sense, that I check with the latest kernel?
Regards
Chris
--
You received this bug notification because you are a member of Kernel
Packages
Hi Christopher,
not sure if I understand. Do you have a definition page of the different kinds
of kernels you mentioned?
With repository kernel I would understand an available kernel via repository
sources. However would Linux Mint be considered as a 3rd party?
Next question would be which versi
@ Joseph (Or anyone who knows), can you help me our here.
As I am not developer, I am not getting on how Ubuntu versioning and Kernel
updates work.
Why is there an artful-proposed needed? Is the 4.13 Kernel versioned under
artful, but still used in Xenial?
Then I would need to add the artful-pro
*NOT WORKING*
So checked to install from artful-proposed the following packages:
linux-image-4.13.0-37-generic/artful-proposed
linux-image-extra-4.13.0-37-generic/artful-proposed
Following sequence:
1. Install fix kernel from bug #1734147
2. Reboot with fix kernel
3. Reboot into BIOS, doing some
*WORKING*
Ok, was on -36 hence thought -37 would be the next one.
Tested with
linux-image-4.13.0-38-generic/artful-proposed
linux-image-extra-4.13.0-38-generic/artful-proposed
and fix worked. BIOS is writable after applying fix kernel. Stays
writable after returning to 4.13.0-38.
** Tags remove
@Mika
After seeing the logs in your post I checked the logs on my Lenovo Yoga (20C0)
for similar entries as yours:
[ 19.724288] intel-spi intel-spi: wrote SSFSTS_CTL=0x0045020c
[ 19.724301] intel-spi intel-spi: wrote FDATA(0)=00 00
[ 19.724304] intel-spi intel-spi: wrote SSFSTS_CTL=0x0041360c
[ 1
#509
At least my BIOS is read only. I can't change a single setting without it
reverting on next boot.
It just says "Configuration changed - restarting system." and I have the old
settings again. :-(
When using the patched kernel, that message is gone and I can edit and
save BIOS changes over r
#511, 512, 513
I switched to 4.13.0-21, which was stated to have fixed the problem and should
be safe as in multiple posts above (e.g. #350, #484, ...).
I cannot say, if mint need to do something as well, but it comes right off the
ubuntu repos (see below).
linux-image-4.13.0-21-generic:
Inst
#516, #517
no change in 4.13.0-26. as soon as I booted once, BIOS is back to ro.
If the commit d9018976cdb6 is missing, what to 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
#519
no, I did not compile the kernel yet. So far only used the one provided in the
fix description.
As for repairing -like with the fix kernel- this won't help, right? It
would just be an option to go away from the repository kernels and
compile my own one until the commit is included in the rep
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742696/+attachment/5035110/+files/lspci-vnvn.log
** Summary changed:
- Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of
Intel SPI bug
+ Commit d9018976cdb6 missing in Kernels <
Public bug reported:
New bug forked out of Bug #1734147 "corrupted BIOS due to Intel SPI bug
in kernel Edit"
When trying to apply the proposed fix in Bug #1734147 to a Lenovo Yoga
with Serial Flash s25fl064k, the actual fix works, however reverting
back to original available Kernel <4.14.x again
#524, #525
Created Bug #1742696
"Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel
SPI bug"
Let's continue discussion over there
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
So how are we going on with this?
As it seems I am the only one so far in this unique combination. Hence it might
be too much asked to cherry pick the 4.13 kernels just for me?
I could try to build by current kernel (4.13.0-26) with patches and then stay
on that one until 4.14 gets available? (n
#5
Using the test kernel I can confirm, that the BIOS is writable, keeps settings
over reboot and the bios changed message has disappeared.
Thanks a lot!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Hi there,
so it feels I am a special case of this. I am running Linux Mint 18.3 as my
main distro. However to check a problem with standby based on Ubuntu I tried to
run Ubuntu 17.10 from USB. Since then I have the same trouble to save my BIOS,
etc.
However Linux Mint is starting from hard disk
NOT WORKING
I tried it on my Lenovo Yoga Thinkpad (20C0) with Linux Mint 18.3 (The
one I managed to use the 17.10 USB on to mess up the BIOS).
When installing the Kernels provided above, I can again do changes in
BIOS and they stay over reboot.
However as soon as I revert back to 4.13.0-21 Kerne
Hi there,
I have the same behaviour on a Lenovo Thinkpad Yoga, running
- Linux Mint 18.2 (hence Ubuntu 16.04)
- 4.10.0-38-generic
- Lenovo BIOS Version: GQET52WW (1.32), Release Date: 05/04/2017
- intel-microcode 3.20170707.1~ubuntu16.04.0
Only difference is, that standby randomly works (maybe 4
18 matches
Mail list logo
