I tested also the current Xubuntu Groovy version dated Okt 17 02:07 from
zsync,
Conclusion: This bug seems squashed with casper version 1.455 :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
The current Ubuntu Desktop (standard Ubuntu) Groovy version dated Okt 17
08:30 from zsync,
- '20201017' in the testing tracker
ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2942062592 okt 17 08:30 groovy-desktop-amd64.iso
$ sha256sum groovy-desktop-amd64.iso
f572ff624215e00b398233b
Although not intentionally so, this now works fine on both the E6400 and
E6510 laptops. Both initial boots, and subsequent boots. Just works
perfect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18993
Ubuntu groovy daily (2020-10-16.4) written (using mkusb/dus)
booted first on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
shutdown, then booted again twice on same dc7700 box
then thumb-drive taken to
- hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)
and it booted
http://iso
http://cdimage.ubuntu.com/ubuntu/daily-live/20201016.4/groovy-desktop-
amd64.iso has now been built with the correct casper.
I am not respinning a lubuntu test image for this issue, since the boot
logic is the same across all flavors. Please test specifically with the
above image, not with other
Worst case scenario on those older Latitude laptops a DVD still works
fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
Title:
failure to boot groovy daily (again)
To manage notification
** Changed in: cd-boot-images-amd64 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
Title:
failure to boot groovy daily (again)
To manage notific
Lubuntu daily (2020-10-16 ISO)
first boot worked on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
but subsequent boots on box failed.
casper is 1.452 still on lubuntu daily :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Sorry, not sure why casper is still out-of-date there. Respinning now.
Note that this only changes the behavior on SECOND boot of the image.
If you have systems that wouldn't boot the previous image at all, this
doesn't do anything to correct that.
--
You received this bug notification because
http://cdimage.ubuntu.com/ubuntu/daily-live/20201016.1/groovy-desktop-
amd64.manifest still shows casper 1.452
Is that correct or is the manifest just not updated? It's still not
working on the Dell latitude E6510 and E6400 previously mentioned. On
the E6510 I tried both legacy and UEFI modes and
The image at http://cdimage.ubuntu.com/ubuntu/daily-live/20201016.1/ has
been built with this new casper.
As time is short before release, please test this asap and let us know
of any problems. This new casper passes its autopkgtests, so it does
successfully modify the partition table of the boot
This bug was fixed in the package casper - 1.455
---
casper (1.455) groovy; urgency=medium
* Use a tmpfs in tests; overlay is not compatible with zfs.
* Make tests work when host kernel does not match that in the test env.
* Properly handle echo -e for dash vs busybox in initram
Ubuntu daily (2020-10-15)
written to thumb-drive using `gnome disks`
First boot works on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
But subsequent reboots, even off & back on fail on same box and another box
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
- hp dc7900 (c2d-e8400, 4g
Also seems to effect Dell Latitude E6400 with C2D CPU's and an E6510
with i7 M620 CPU laptops using 20201015 Ubuntu image created with
Startup Disk Creator in 20.04. The same USB with the same image works OK
in my old Intel Desktop so I'm reasonably certain it's hardware
specific.
Typical behavior
On Thu, Oct 15, 2020 at 05:31:08PM -, Thomas Schmitt wrote:
> > sfdisk --no-reread -q $DEVICE -A 1 -X dos || true
> If this attributes the boot flag to the first partion of type EE, then
> this is a semi-violation of EFI specs and known to be punished by some
> firmwares. UEFI 2.8 says:
>
>
Hi,
Steve Langasek (vorlon) wrote:
> I've manually run through the steps of casper's persistent partition
> creation [...]
> it also "fixes" the protective MBR, removing the empty bootable partition.
That explains why the machines which demand the boot flag boot exactly
once.
sudodus (nio-wiklun
Hi Thomas,
The output of the partition editor commands is in the attached file.
** Attachment added: "p-ed-commands.txt"
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+attachment/5422669/+files/p-ed-commands.txt
--
You received this bug notification because you are a member of Ubun
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-installer/casper/+git/casper/+merge/392318
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
Title:
failure to boot groovy daily
I've manually run through the steps of casper's persistent partition
creation on a local image. The partition creation operation, 'sfdisk
--no-reread -q $DEVICE -a", properly creates the partition on the GPT,
not on the MBR.
However, in the process it also "fixes" the protective MBR, removing the
Hi,
> Please tell me which partition editor commands to run
One might need superuser autority for reading the device file:
device=/dev/sdd
/sbin/fdisk -l "$device"
xorriso -indev stdio:"$device" -report_system_area plain
Have a nice day :)
Thomas
--
You received this bug notification
Hi Thomas,
1. Yes, the software in the ISO fiddles with the USB stick partitioning.
I think this was introduced in Ubuntu 19.10. I think it is used to log
the installer (to help debug failures) and to store crash dumps. (I
would be happy to turn it off.)
Please tell me which partition editor comm
Hi,
sudidus wrote:
> Later on, in the HH series, you can revert back from 'nopersistent' and
> let the system create an ext4 partition again (in a USB drive behind the
> image of the iso file),
So the software in the ISO fiddles with the USB stick partitioning ?
That would be a prime suspect for
@ everybody,
In the light of the lasts findings, questions and suggestions, I did
some more tests, this time with yesterday's Xubuntu Groovy iso file,
that failed booting yesterday.
I think I started testing the cloned USB drive in the Lenovo V130 (which
worked), and continued testing in the HP E
@ Thomas,
1. I know that it can improve things to start from a wiped drive, but I
don't know why. I know that before you got involved and started to
improve the booting, the systems could not create the ext4 partition in
my computers, unless the USB drive was wiped, and I *think* this was
independ
Hi,
Chris Guiver (guiverc) wrote:
> (1) wiped thumb-drive
> (2) `mkusb-plug groovy-desktop-amd64.iso` (option N or non-persistent
> was selected)
Is (2) equivalent to a plain copy by dd or cp ?
> I booted again (still same thumb-drive) without issue on
> - hp dc7700
> and booted successfully on
@ Steve,
Booting 'nopersistent' is a mild tweak, and it seems to improve things a
lot.
Please consider if this should be the default (in other words modify the
iso file accordingly). At least now for Groovy, so that we can release a
set of iso files, that work in the [amd64] computers, that we ha
Further to my comment #46
I booted again (still same thumb-drive) without issue on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
and booted successfully on
hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)
(ubuntu groovy daily 2020-10-14, these are not recorded on iso.qa.ubu as it's
FYI-
I do not have any HP boxes to test on re: bug 1899308 booting prob.
my mixture is dell/lenovo/acer/mac/IntelNuc and InWin - none of these
with boot issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Hi again Jags Desai,
I'm glad that you managed to boot when using mkusb. When you want to
install Ubuntu-MATE, please read the tips at this link:
https://help.ubuntu.com/community/mkusb/persistent#Installing_-
_using_the_Install_icon_on_the_desktop
--
You received this bug notification because
Hi,
i now am boss of my mainboard ASUS ProWS C246-ACE EFI firmware 1401,
at least as long i do not want to disable Secure Boot.
The hardware provider was of not of help with USB sticks, but remembers
to have inserted Debian 10.4.0 netinst on CD-RW when SSD and HDD were
still without bootable syste
Hi Chris,
1. In the meantime I tested the current Lubuntu Groovy iso file in the
HP Elitebook 8560p.
It boots when I made a nopersistent live drive using mkusb-plug, and I
could repeat it.
2. I don't know if the error that you see at shutdown causes failure at
the next boot (when there is an ext
@sudodus
Using mkusb-dus / usb-pack-efi to prepare the live usb, I was able to
boot the "Persistant Live" of Ubuntu MATE Groovy Desktop 20.10 Oct 14,
2020 ISO.
Though the system booted fine, and I got to see the desktop screen, I
have not actually installed the OS yet as I need to free up a parti
@sudodus/Nio
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
thumb-drive was created as requested by @sudodus comment #41
Ubuntu 2020-10-14 groovy daily ISO (same as comment #40)
(1) wiped thumb-drive
(2) `mkusb-plug groovy-desktop-amd64.iso` (option N or non-persistent was
selected)
It's
You need the package 'usb-pack-efi' too.
sudo add-apt-repository ppa:mkusb/ppa # and press Enter
sudo apt update
sudo apt install mkusb usb-pack-efi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899
Hi Jags Desai,
Yes, mkusb-dus (alias dus) is part of the mkusb package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
Title:
failure to boot groovy daily (again)
To manage notifications a
Hi @sudodus
(1) The HP desktop have AMD radeon 290X graphics card.
(2) Ubuntu MATE Focal 20.04 with kernel 5.9.0 and 5.8.14 runs just fine
on the same HP PVILION eLITE DESKTOP.
(3) Yes, as described in my previous post, when I try to boot the system
from Ubuntu MATE Groovy desktop Oct 14, 2020 L
Hi Jags Desai,
It is possible that your problem depends on the graphics, if there is
nvidia graphics. Have you tried to boot in recovery mode or with the
boot option 'nomodeset'?
But if your HP does not even reach grub, you may need a workaround for
the boot process. Please try to install mkusb (
Hi Chris,
There seems to be a difference between the first boot and the subsequent
boots in your
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
It might depend on the creation of the ext4 partition behind the image
of the iso file, which happens only in the first attempt to boot.
Another diff
Ubuntu daily groovy (2020-10-14) written with `dus` (mkusb in 'live')
responds identically to Lubuntu daily.
First attempt on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
worked, but subsequent reboots all failed.
Refer
http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/221721/testc
Lubuntu groovy daily (2020-10-14) is reacting the same as yesterdays
(written with `dus` (mkusb live))
first boot on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
worked, but all subsequent boots made (reboot, or turning off, waiting &
turning back on) have failed.
no tries on
- hp dc790
Ubuntu MATE Groovy Oct 14, 2020 daily does not boot on HP Pavilion Elite
HPE series Desktop PC.
ISO: groovy-desktop-amd64.iso
Downloaded from: http://cdimage.ubuntu.com/ubuntu-mate/daily-
live/current/
sha256sum:
bdf86534a8ef8c353f45a0c82776aaf8b0cc57eac85cc05b9d80b302f9e7cade
I flashed/prepar
Thanks for all the improvements, Thomas and Steve :-)
Although we feel frustrated now, we must remember that the Groovy iso
files have improved a lot and can boot many more computers than when we
started.
-o-
There are workarounds to make also the remaining computers boot: for
example to make a
Hi,
i confirm that
groovy-desktop-amd64.iso1 1 5740827 5740827 2.8G ee GPT
groovy-desktop-amd64.iso2 *0 0 1 512B 0 Empty
is the indication that the --mbr-force-bootable hack is applied.
A nearly non-existend MBR partition not overlapping the partition of
type
Hi Thomas,
> All Ubuntu flavors use the same bootloader logic; there is no
> distinction here.
>
> And I have checked that the latest xubuntu image has the same
> partition setup.
...
> So a failure to boot Xubuntu where Ubuntu works is not explained
> by missing/different xorriso options.
Thank
On Wed, Oct 14, 2020 at 08:04:19AM -, sudodus wrote:
> The current Groovy iso files of Lubuntu and Xubuntu have a later date
> and time (from zsync), yet they fail to boot the HP Elitebook 8560p.
> Is this because the latest tweak suggested by Thomas Schmitt is only
> present in the Ubuntu Gro
The current Ubuntu Desktop (standard Ubuntu) Groovy version dated Okt 14
08.30 from zsync,
- '20201014' in the testing tracker
$ sha256sum groovy-desktop-amd64.iso
20b9b69600470e6641406a6ab975f985903bde4555b552f3155693aa10a862a1
groovy-desktop-amd64.iso
when cloned to USB can boot an old HP El
@ Steve Langasek (vorlon),
The current Ubuntu Desktop (standard Ubuntu) Groovy version dated Okt 13
08:36 from zsync,
- '20201013.1' in the testing tracker
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2894153728 okt 13 08:36 groovy-desktop-amd64.iso
$ sha256sum groovy-desktop-a
Hi Chris,
Please test Ubuntu Desktop (standard Ubuntu) Groovy version dated Okt 13
08:36 from zsync,
- '20201013.1' in the testing tracker
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2894153728 okt 13 08:36 groovy-desktop-amd64.iso
$ sha256sum groovy-desktop-amd64.iso
3b92cb0d
It's been a ~three hours since my last comment (#29)
and the thumb-drive no longer boots on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
I booted it with *live* to test for http://launchpad.net/bugs/1899719
where I quote myself on saying ot occurred on 3 boxes; the purpose of
this boot was
Lubuntu QA-tests using groovy daily 20201013
(iso written with `dus` or mkusb live)
Boots & completed install on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
but FAILS TO BOOT on
- hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)
--
You received this bug notification because
The current Lubuntu Groovy iso file
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 1894162432 okt 13 16:56 groovy-desktop-amd64.iso
$ sha256sum groovy-desktop-amd64.iso
2bc2b6bf2a14a4a293ce5280e754ed9ef4913873a529c99bfe0bcfe222aff2b5
groovy-desktop-amd64.iso
when cloned does *no
I can confirm that my Lenovo V14 IIL boots successfully on todays Ubuntu
Groovy ISO -
http://cdimage.ubuntu.com/daily-live/20201013.1/groovy-desktop-amd64.iso
in UEFI+secure boot and BIOS (legacy) modes. I have not had any problems
with any of my other boxes.
--
You received this bug notificati
Hi Thomas,
> > Please notice that the option -compliance no_emul_toc may cause
problems.
> Do you have any tangible indications for this (beyond the fact that MBR
> table does not work for the Lenovos) ?
I wrote maybe (which includes maybe not). I may have drawn faulty
conclusions when I thought
Hi,
sudodus wrote:
> I also tested the tweak in comment #15 on the current Ubuntu Groovy iso file.
> When cloned the USB drive fails to boot the Lenovo V130,
> ...
> $ sudo gdisk test_mbr.iso
> MBR: MBR only
Obviously the production of "test_mbr.iso" did what the file name says
and made a MBR p
It seems I was too early to test the new current daily Ubuntu Desktop
iso file. Now I found this one:
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2894153728 okt 13 08:36 groovy-desktop-amd64.iso
$ sha256sum groovy-desktop-amd64.iso
3b92cb0d427998b5a7f58377d0204ef56e3f21e8748331b
The current daily Ubuntu Desktop iso file
-rw--- 1 sudodus sudodus 2938152960 okt 13 06:25 groovy-desktop-
amd64.iso
$ sha256sum groovy-desktop-amd64.iso
a1ee702fd38036ac3b22a34657c94a9f1f7cb476bc13b4712ee34dad20499fc2
groovy-desktop-amd64.iso
$ md5sum groovy-desktop-amd64.iso
541b509f09d7
@ Chris,
I was almost sure, that the bug was squashed. But I cannot see anything
wrong with what you describe in comment #19, so it seems there more to
do until we have iso files that can boot all our computers (if at all
possible before the release of 20.10).
Anyway, I look forward to both your
Hi,
> xorriso \
> ...
> -outdev test_mbr.iso \
> ...
> -boot_image any appended_part_as=gpt \
> ...
> HOWEVER it did NOT boot on
> hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
> hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)
The only flaw i see is that the ISO's name "tes
On Mon, Oct 12, 2020 at 09:20:14AM -, Thomas Schmitt wrote:
> That means we should ask Steve Langasek to add option
> --mbr-force-bootable
> to the xorriso -as mkisofs command that is used for ISO production.
> Then the waiting for complaints will begin again.
I have applied this change t
Thank you @Thomas Schmitt (scdbackup) & @sudodus
Using today's Lubuntu groovy ISO 2020.10.12, I ran
(based on @sudodus' comment #15)
--
#!/bin/bash
original=groovy-desktop-amd64.iso
test -f test_mbr.iso && rm test_mbr.iso
xorriso \
-indev "$original" \
-outdev test_mbr.iso \
-boo
Hi,
this is a one-time tangent about the xorriso replay run which i advised
in comment #10.
I found at least the trigger of the xorriso replay flaw about the size
values in ISO 9660 superblock, protective MBR, and GPT header block.
It is the multi-session emulation for overwritable media which is
Hi Steve,
I hope there is still time to improve booting of Groovy iso files, to
make also it work in old HP computers in BIOS mode. Thomas Schmitt
suggested a modification of the iso files, and according to my tests, it
works without destroying anything for other computers.
--
You received this
Hi,
> You are a wizard Thomas,
I lurk at boot loader mailing lists since more than a decade.
But as sysadmin i am lame enough to not knowing how to make ASUS ProWS
C246-ACE EFI firmware 1401 offer me any external storage device for
booting, or how to disable its Secure Boot setting.
I will have
You are a wizard Thomas,
This tweak:
original=groovy-desktop-amd64_20201010_gpt.iso
test -f test_mbr.iso && rm test_mbr.iso
xorriso \
-indev "$original" \
-outdev test_mbr.iso \
-boot_image any replay \
-boot_image any appended_part_as=gpt \
-boot_image any mbr_force_b
Hi,
> So I am sure that we have identified the problem.
There is still the possibility that only a boot flag is missed by the
firmware.
So please test also an ISO made by
...
-boot_image any replay \
-boot_image any appended_part_as=gpt \
-boot_image any mbr_force_bootable=on
If
@guiverc,
> The dc7700 has no booting OS on it; last a failed xubuntu qa-test install but
> I bet
> it'd legacy/BIOS/MBR, and I know the dc7900 has legacy/MBR (no GPT) as my
> boxes are
> mostly 80-160GB disks & I don't bother with GPT
The problem is that the current Groovy *iso files contain a
This morning (CET) I tested a cloned system from a modified iso file
according to Thomas Schmitt;
original=groovy-desktop-amd64_20201010_gpt.iso
test -f test_mbr.iso && rm test_mbr.iso
xorriso \
-indev "$original" \
-outdev test_mbr.iso \
-boot_image any replay \
-boot_imag
** Description changed:
This is either a duplicate or return of
- https://bugs.launchpad.net/ubuntu-cdimage/+bug/1883040
- https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148
Most probably "groovy daily won't boot anymore on some older BIOS boxes"
or the 1883040 bug, as it's impact
Today's daily (Lubuntu 20201011) was written with GNOME-DISKS with same
results.
Failure to boot on
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)
but i can boot it on other dell boxes (& more modern HP)
@sudodus
The dc7700 has no bo
Hi,
so the world might begin to split into incompatible camps.
New Lenovos versus old HPs.
Debian still has the "mac" amd64 ISOs which simply have no EFI equipment
in order to please some old Apple machines:
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/
But this GPT allergy would h
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cd-boot-images-amd64 (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/1899308
I could get a signal to an external screen from the HP Elitebook 8560p.
As I expected, it failed to boot to the current Lubuntu Groovy iso file.
In mkusb's settings menu for a persistent live drive I selected
- MSDOS partition table
- usb-pack-efi
and I could boot to this persistent live system
typo fix in comment #6
this bug needed MSDOS partition table --->
this computer needed MSDOS partition table
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
Title:
failure to boot groovy dail
I have access to one old and slow HP computer, a Probook 6450b with an
Intel i5-M520 CPU. But it seems to be too new to be affected by this
bug. It boots in BIOS mode with this new Groovy iso file.
My son has another and older HP Elitebook, and this bug needed MSDOS
partition table to boot via gru
@ Chris,
This bug might correspond to an observation, that I made years ago with
persistent live drives made by mkusb.
Some old (at that time maybe middle-aged) HP computers refuse to boot
. in BIOS mode
- from a USB drive
- via grub
- in a GUID partition table (GPT).
That made me add an entry
Ubuntu groovy (daily 20201010) desktop won't boot on the same boxes
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)
but boots as expected on other boxes tested (identical results to
Lubuntu & Xubuntu).
--
You received this bug notific
** Tags added: groovy
** Also affects: cd-boot-images-amd64 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
Title:
failure to boot groovy
77 matches
Mail list logo
