@ Steve Langasek (vorlon),
According to your request I continue the dialogue about the Lenovo V130
issue at
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Please either file a separate bug report for the Lenovo V130 issue, or
follow up on LP: #1886148, rather than commenting on a closed bug.
> This is when using the boot option in the temporary boot menu (F12)
> "Linpus Lite ()"
This suggests to me that this is an EFI boot entry that was manually
... continuing:
This is when using the boot option in the temporary boot menu (F12)
"Linpus Lite ()"
in the picture attached to the previous comment. This is the only
available USB boot option in UEFI mode.
Then I turned off UEFI mode and set teh computer to boot in 'legacy
mode'. Now there wer
@ Steve Langasek (vorlon),
Previously I have not touched the UEFI/BIOS system of the *Lenovo V130*
that I have access to, but now, that you ask about it, I had better do
it in order to help identify what goes wrong, when trying to boot USB
drives cloned from Groovy ISO files.
When testing Groovy
The problem with the Lenovo V130 was reported at this bug
report/comment:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/comments/31
** Attachment added: "mokutil-of-lenovo-v130.txt"
https://bugs.launchpad.net/ubuntu/+source/cd-boot-images-amd64/+bug/1892754/+attachment/5407095/+fi
On Wed, Sep 02, 2020 at 11:15:28AM -, sudodus wrote:
> The old problem that a Lenovo V130 in UEFI mode with secure boot fails
> is still there and independent of the bug reported here.
Do you have a bug reference for this, please? And I would want the same
kind of debugging information from t
Thanks, this bug is squashed :-)
I can confirm that a USB drive cloned from the current daily Lubuntu iso
file boots in UEFI mode with secure boot in my Dell Precision M4800.
(This computer can also boot in UEFI mode without secure boot and in
BIOS mode with the current daily Lubuntu iso file.)
Tested Lubuntu Groovy on 3 machines - ISO downloaded from QA testing
tracker 20200901
http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/219871/downloads
-
All 3 booted successfully in UEFI+secure mode. Results posted on the QA
Testing tracker site.
--
You received this bug notification b
This bug was fixed in the package cd-boot-images-amd64 - 5
---
cd-boot-images-amd64 (5) groovy; urgency=medium
* No-change rebuild against current grub, to pick up a version that
is signed with the current, non-revoked key. LP: #1892754.
-- Steve Langasek Mon, 31 Aug 2020
2
Thanks @vorlon .. will test the new images when available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892754
Title:
Unable to boot in UEFI+secure boot mode
To manage notifications about this bu
Thanks Steve Langasek/@vorlon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892754
Title:
Unable to boot in UEFI+secure boot mode
To manage notifications about this bug go to:
https://bugs.launchp
Ok, a key point here is that your dbx includes Microsoft's recent
revocations of older grub versions; and an examination of the daily
image shows that it's currently using an old grub signed with the old
key instead of the current grub:
$ sudo kpartx -a ~/devel/iso/groovy-desktop-amd64.iso
$ sudo
cd-boot-images-amd64 v 5 has been uploaded, to pull in the new grub.
This will be fixed in daily images as soon as that propagates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892754
Title:
Unabl
The Ubuntu daily image I used in testing
(http://cdimage.ubuntu.com/ubuntu/daily-live/20200826/groovy-desktop-
arm64.iso.zsync) and matches comment #13 still fails to boot with secure
boot enabled
sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
- mokutil --db
https://paste.ubuntu.com/p/g
I am unable to reproduce this issue here using an unmodified, current
groovy image of either Ubuntu (http://cdimage.ubuntu.com/ubuntu/daily-
live/20200826/groovy-desktop-amd64.iso) or Kubuntu
(http://cdimage.ubuntu.com/kubuntu/daily-live/20200831/groovy-desktop-
amd64.iso) in a KVM instance configu
** Tags added: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892754
Title:
Unable to boot in UEFI+secure boot mode
To manage notifications about this bug go to:
https://bugs.launch
Last night I wrote a recent Ubuntu daily image to thumb-drive and tried
to boot it on
sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
which now has secure boot on and it failed with
"ERROR
Verification failed: (0x1A) Security Violation"
Today I've upgrade ISO and now it's 2020-08-28 and
This bug affects the current Ubuntu Desktop Groovy iso file too (not
only Lubuntu).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892754
Title:
Unable to boot in UEFI+secure boot mode
To manage no
I tried again in the Lenovo V130, and this second time the internal UEFI
system is upgraded so that it no longer allows booting (not even when
the current daily Lubuntu Groovy iso file is used to create a persistent
live drive with mkusb (with the setting 'upefi', using 'usb-pack-efi').
So the bugf
Additional test results:
- As before, the Lenovo V130 can boot when the current daily Lubuntu
Groovy iso file is used to create a persistent live drive with mkusb
(with the setting 'upefi', using 'usb-pack-efi'). This indicates that
there is a security problem with grub.
- The Dell Precision M480
yeah me too it turned out
(I finally discovered I can turn secure boot on this thing)
sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
"ERROR - Verfication failed: (0x1A) Security Violation"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Need I say that the old failure mode is still there in a Lenovo V130:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/comments/60
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892754
Title:
This bug affects my Dell Precision M4800 too.
A current daily Lubuntu Groovy iso file cloned to a USB drive works in
BIOS mode and UEFI mode without secure boot, but with secure boot I get
this message:
'Error: security violation'
and the boot process cannot continue.
I double-checked and a Foc
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892754
Title:
Unab
Further test:
1.Dell [ Optiplex] MT 7040 ( i7-6700,16 GB, Intel HD Graphics 530,Intel
i219-LM GB Ethernet, 1 TB hd)boot UFEI + secure boot from media and
install Lubuntu Groovy 20200825 booted successfully
2. Dell [Inspiron] 3521 - failed when attempting to boot UFEI + secure
boot from media and
Further testing on the two boxes that failed:
1. Dell [Inspiron] 3521 - failed when attempting to boot UFEI + secure
boot from media and install Lubuntu Groovy 20200824
2. Acer [Aspire] E3-111-P60S - booted UEFI+secure boot and installed
Lubuntu Groovy 20200824 with no errors.
--
You received t
Just performed a quick test on the Dell [Inspiron] 3521, box this time
running in UEFI without secure boot and the system booted up normally
and the install completed without error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1892754
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
28 matches
Mail list logo
