I can confirm that "removing MBR partition 2" indeed WORKS.
I've tested the "second" step as I've already had booted from the stick a
couple of times (and always had experienced the daunting delay).
Thus I've patched the partition on the stick directly as you've advised.
As expected the
Hi,
i opened a separate bug with my wish for not needing a second zeroizing dd
run when the ISO is already on the USB stick:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1977644
"Please preserve MBR partition entries 2 to 4 when creating persistent
partition"
Have a nice day :)
Hi,
tlk wrote:
> which post details the "removing MBR partition 2"?
#112 by me, confirmed by #114 by Chris Guiver:
If the USB stick with the the slowly booting ISO is overwritten
meanwhile:
# Patch the ISO already as image on hard disk
ISO=ubuntu-22.04-desktop-amd64.iso
dd if=/dev/zero
which post details the "removing MBR partition 2"?
I'll try when I come around to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
Impish live session takes ages to boot on BIOS
Hi,
Chris Guiver wrote:
> This confirms what I believe you wanted.
Yes.
The stick needs the remedy once again after casper created the persistent
partition.
sudodus wrote:
> This is like development of physics ;-)
Like a unification of relativity theory and quantum mechanics ?
My apologies
Congratulations Thomas (for theory) and Chris (for experiments). This is
like development of physics ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
Impish live session takes ages
> If you now apply the remedy to the stick
> dd if=/dev/zero bs=1 count=16 of=/dev/sdb conv=notrunc seek=462
>then i expect it to be permanently booting in reasonable time.
> .. Please confirm.
Inserted thumb-drive(2) [Ubuntu-MATE jammy] into box and
-- start paste
Hi,
Chris Guiver wrote:
> On j3400; pressed ENTER (at grub) at 13:10 (room clock).. I didn't note
> time of plymouth but I had maybe-ubiquity @ 13:13 (room clock) for
> altered version of 2022-04-19 ISO
> [...]
> so I'll now boot twice
> [...]
> alas should have noted clock.. it 'feels' slow...
-- reply to @Thomas #112 (start paste)
So if we want to propose a workaround for the current layout, it would be a
good base if you could confirm that j3400 boots after the plain procedure with
no other experiments inbetween:
# Patch the ISO already as image on hard disk
Hi,
i wrote towards Chris Guiver:
> it would
> be a good base if you could confirm that j3400 boots after the plain
> procedure with no other experiments inbetween
I should have written:
it would be a good base if you could confirm that j3400 boots without
the extra delay of ~6 minutes
Hi,
Chris Guiver wrote:
> libburn : SORRY : Failed to open device (a pseudo-drive) : Permission denied
Oops. No read permission for normal users on USB sticks.
(I should really operate my workstation with a more conventional setup
so that i better anticipate other's adventures.)
> My
My thumb-drive K does not boot on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
- hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)
as it stands now.. (No big news as dc7700 & dc7900 usually react the same; but
confirmed it won't boot on dc7900)
Likely not required; but again
--
Hi,
Chris Guiver wrote:
> └─sdb4 8:20 1 4G 0 part /media/guiverc/writable
So it seems that casper added its persistent partition without creating
a dummy MBR partition with boot flag.
This simplifies the task of making current Ununtu ISOs digestible for
the j3400. One run of
dd
My thumb-drive K (what was used in #107 & #101) which contains Ubuntu
22.04 LTS (20220416) resulted in
PLEASE NOTE: I just noted the ISO date shows it wasn't the released
image.. It'll be the last daily/final/RC i actually used in testing...
I'd expect 20220419 for the released ISO. I don't
Hi,
Chris Guiver wrote:
> I performed the command
> `sudo dd if=/dev/zero bs=1 count=16 of=/dev/sdb conv=notrunc seek=462`
> to Ubuntu Desktop 22.04 LTS thumb-drive (K)
> Booted on j3400
> BOOT1:
> it was fully-operational at 2 min 45 secs
So it looks like the dd run brought about the best
Thomas Schmitt in #104
>...> motion computing j3400
> This one is possibly allowed to be somewhat slow.
From me (comment #76)
> ((or 3 mins 30 secs for `hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)`
The time for lubuntu kinetic actually beat a comparison time of one of
an old hp.dc7700 I
Hi,
i have to correct a statement of mine in #104:
> Last year this worked only once, because casper added the partition again
> during "persistent partition creation". This could be fixed now:
> https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/comments/60
It's probably not fixed.
The
I agree with Thomas about the problems to boot some old computers.
I'm continuing to develop/tweak dus-iso2usb, added an extra (optional)
parameter 'boot-flag' that can be added when mkusb partition table is
selected. It helps HP computers, but may spoil booting some other
computers.
So I think
Hi,
Chris Guiver wrote:
> BOOT2: LIVE
> 00:25 secs & screen blanks & messages
> 00:35 plymouth visible
> 01:11 message(s) again & plymouth gone
> 02:23 system fully-operational
The overall boot time is still very long. But no particular stage stands
out as the big time waster.
>...> motion
I grabbed my phone (stopwatch app) & lubuntu (kinetic; what was used
last time) thumb-drive & timed a boot of Lubuntu kinetic (no new write
of ISO)
Purpose:
> (#102) Are those times stable or do they vary by minutes ?
I hoped it would be a re-creation of #92 (but didn't read was there so
it
Hi,
Chris Guiver wrote:
> lubuntu (jammy) plymouth seen at 7:27 (#90)
> ubuntu (jammy) plymouth seen at 8:20 (#101)
So it is not about the "huge amounts of time" which ubuntu.seed wants
to avoid.
Are those times stable or do they vary by minutes ?
We know that the firmware executes GRUB
Booting the released image of Ubuntu Desktop 22.04 LTS
- 00:00 word 'GRUB' appeared on screen (where I started stopwatch, so
these results will be ~10 secs slower sorry)
- 00:09 enter pressed at GRUB
- 08:06 screen blacked
- 08:20 ubuntu plymouth first appeared
- 09:52 plymouth is gone, system
@ guiverc,
I think you have suitable hardware and the best experience of us to
answer the question in comment # 99.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
Impish live session
Hi,
sudodus wrote:
> http://cdimage.ubuntu.com/lubuntu/releases/22.04/release/
The "Try or Install" menu item of grub.cfg in lubuntu-22.04-desktop-amd64.iso
differs from the one of ubuntu-22.04-desktop-amd64.iso mainly by kernel
parameter file=/cdrom/preseed/lubuntu.seed instead of
At
https://releases.ubuntu.com/22.04/
you find the amd64 iso file and its sha256sum, and at
http://cdimage.ubuntu.com/lubuntu/releases/22.04/release/
you find the corresponding Lubuntu files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi,
sudodus wrote:
> The grub comes from a compressed tarball,
Well, then the hope to find a simple explanation from tweak 3 was an
illusion.
I am staring at the /boot/grub/grub.cfg of ubuntu-22.04-desktop-amd64.iso
and compare it with Chris Guiver's comment #90:
>...> "00:10 secs enter
Hi again Thomas,
The grub comes from a compressed tarball, that is extracted onto the
target drive. This makes it independent of the current operating system
and its version of grub.
So in order to look at it, use dus-iso2usb, or if you want only the
basics, extract only the tarball, in this
Hi,
sudodus wrote:
> # tweak 3: search by UUID
> sed -i '/set isofile/'a" search --set=root --fs-uuid $uid3"
> "$targ1"/boot/grub/grub.cfg
> sed -i 's/(hd0,3)/($root)/' "$targ1"/boot/grub/grub.cfg
Where does the grub.cfg come from, in which you find "set isofile"
and "(hd0,3)" ?
I looked into
Hi Thomas Schmitt,
> I wonder what is meant by "add some tweaks".
1. Made grub use UUID instead of device name to identify partition where
to find the grub files
---
# create grub.cfg to match iso file's name
echo -e "$inversvid tweak grub ...$resetvid"
# tweak 3: search by UUID
sleep 2
Hi,
Chris Guiver wrote:
> The ISO wasn't cloned to thumb-drive; but written using
> `sudo -H dus-iso2usb kinetic-desktop-amd64.iso /dev/sdb msdos grub-2.0.4
> persistent`
Ahum. Congrats to sudodus then. :))
I read in
https://help.ubuntu.com/community/mkusb#Installation
"The main function
I just booted Lubuntu kinetic daily on
- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
I didn't set up stopwatch to time correctly; but room clock said 13:16
at start of boot, and system was fully functional just as it hit 13:22,
which is way faster than comment #90 on same box
Hitting this rn with Ubuntu MATE 22.04 dd'ed onto a USB stick
Spotted the grub_platform thingy, then had to wait (after reading this
bug) like ~20 min after the GRUB menu for it to start booting.
Run of the mill legacy (I guess) platform:
Gigabyte GA-970A-DS3/GA-970A-DS3, BIOS F7a 01/24/2013
AMD
** Also affects: casper (Ubuntu Kinetic)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
Impish live session takes ages to boot on BIOS
Lubuntu 22.04 LTS (jammy) ISO booting on
- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
00:10 secs enter pressed at grub
(I could reduce 10secs from following times, but have opted not to)
BLINKING CURSOR without change until
7:19 (7 mins 19 secs) first boot message
7:27
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Booting Ubuntu Desktop (groovy RC 2020-10-16.4)
- - motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
and plymouth takes ~8 mins to appear on screen
the maybe-ubiquity (try or install) screen took >10 mins
I did mention groovy in comment #17, but I don't believe I filed bugs,
just
I can write a 20.10 ISO to a thumb-drive & re-test it on
- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
to confirm/deny @juliank's #86 comment on that box. That device is not a
common box used for QA by me so it's possible I may not have used it
late in the groovy cycle... I
qemu kvm data, with the iso specified as -hda
- 23s to splash on 20.04 BIOS (isolinux), vs 22s on UEFI
- 30s to splash on 21.04 BIOS, vs 19s on UEFI
I have resized the image using fallocate to be 16G, but that did not
increase boot time.
Optimized VM (kvm, virtio HD):
- 3s to splash on 20.04
Are we sure this issue does not happen on 20.10 as well? It seems to
spend the same time in 20.10, 21.04, 21.10, and jammy daily when booted
in a qemu vm.
I don't know for sure what's going on, I assume it's trying to read the
entire partition into memory to verify it, but not 100% sure.
There was also a much shorter pause in the boot process at:
"commands/verifiers.c:88: file: /casper/vmlinuz type: 3"
The attached picture shows what happens after that.
** Attachment added: "IMG_20220112_115522.jpg"
Reading the grub manual I found a "pager" option which causes the output
to pause after each screenful. By setting that I was able to capture
what happens after "lib/relocator.c:1410:".
** Attachment added: "IMG_20220112_120411.jpg"
I modified the grub arguments, using grub shell, so that "set debug=all"
was used. Having done that and watching the boot process the last
message I saw before a very long pause was:
"lib/relocator.c:1410: chunks = 0xb9fd5c00"
The context before the pause can be found in the attached screenshot.
I just noted Brian's comment so booted a somewhat recent jammy (2021-12-29)
Lubuntu ISO on
- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
with 'quiet splash' removed I had ~similar response to Brian...
" Booting a command list \n\n" & blinking cursor for a long time
If I remove "quiet splash" from the grub command prompt, which I reach
quickly on the above system, I see "Booting a command list" and then
nothing else until the system is booted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
44 matches
Mail list logo
