I have an HP TouchSmart tm2 (model tm2t-1000) which takes around 10
minutes to boot an Ubuntu 21.10 USB disk created using dd.
dmidecode indicates that the BIOS is revision 18.240 and the Firmware
Revision is 71.27.
** Summary changed:
- HIrsute live session takes ages to boot on BIOS systems
+
Lubuntu impish daily boot (2021.10.10) on
- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
start phone-stopwatch at grub menu
~4 mins 40 secs before first boot message appears
~4 mins 47 secs new boot message(s) & switching font (bios generated text? to
graphics?)
~4 mins 51
Hi.
In the next month at least, I will not have much time to dedicate to this so,
if something (tests, etc) is required from me, perhaps I may not be able to do
it quickly so, please be patient. Even so, I send the output of dmidecode in
case it is useful.
Have a nice day
José
** Attachment
Hi,
> I noted Thomas (scdbackup) asked for firmware details
The motivation is to find enough affected hardware so that the delay
can be reproduced by developers. Obviously it did not happen with the
regular testing machines.
So my request/proposal was for the general public:
Tell which machines
Lubuntu impish daily boot on (written with mkusb/dus CLONE mode)
- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
stop watch started at grub/lubuntu
@ 6 mins 34 secs first boot message appeared, only blinking cursor top left
till this point
@ 7 mins 04 secs lubuntu's blue plymouth
Hi,
since the majority of machines seems to work with the current Ubuntu ISOs,
it would be helpful to have manufacturer, model name, and firmware versions
of machines where the ISOs cause long delays or fail.
The problem does not sit in the recognition of boot entry points by the
firmware but
Tested Lubuntu Impish daily ISO 04-06-2021 from QA testing site -
Test machine:
Dell [ Optiplex] MT 7040 ( i7-6700,32 GB, Intel HD Graphics 530,Intel i219-LM
GB Ethernet, M.2 256GB SATA SSD)
Very fast boot in BIOS mode - unable to reproduce the error/problem
** Tags removed: rls-ii-incoming
--
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:
HIrsute live session takes ages to boot on BIOS systems
To manage notifications about this bug go to:
Hi,
José Marinho wrote:
> I can't believe it... it boots fine again but once, twice, three
> times... and there is no MBR partition anywhere.
Let me make up a theory:
> - Burn on stick the iso that was builded with xorriso-1.5.5.
> - Boot it for the first time --> Success.
During this run of
** Also affects: casper (Ubuntu Impish)
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:
HIrsute live session takes ages to boot on BIOS
> What does happen if you zeroize it again ?
> dd if=/dev/zero bs=1 count=16 of=/dev/sdd conv=notrunc seek=462
I can't believe it... it boots fine again but once, twice, three
times... and there is no MBR partition anywhere.
And I repeated the steps again, just in case
- Burn on stick the iso
** Tags added: fr-1415
--
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:
HIrsute live session takes ages to boot on BIOS systems
To manage notifications about this bug go to:
Hi,
it comes to me that while no single ISO can serve all firmwares, it would
be possible that one casper can serve the original ISO and an ISO without
MBR partition 2 alike.
The trick would be to let casper memorize the 16 bytes 462 to 477 before
it runs the partition editor, and to let it
Hi,
the Ubuntu system really manipulates the installation stick's partition
table if i choose to try out Ubuntu.
It looks like i was involved as adviser when the addition of MBR
partition 2 was introduced to "casper's persistent partition creation".
See
@ Thomas Schmitt
Thanks for explaining , it was just a thought as i noticed in the diff
text there was some numbers on there own such as the one at the top so i
wasn't sure if there was something else going on.
>21,22c21
--
You received this bug notification because you are a member of Ubuntu
Hi,
Lucap wrote:
> https://gitlab.gnome.org/GNOME/gnome-disk-utility
> Would the code be worth you looking through for any insight for the
> legacy bios option?
Seems not necessary. Your diff in comment #44 shows the few changes which
gnome disks made for you.
José Marinho's boot1.txt shows
Hi,
José Marinho wrote:
> changes only work at first boot [...]
> This happened today with the new version of xorriso and yesterday with
> "dd if=/dev/zero bs=1 count=16 of="$NEW" conv=notrunc seek=462" command.
> [...]
> the output of two xorriso commands BEFORE trying to boot from
> the stick,
@ José Marinho
>>As I said yesterday, this changes only work at first boot but in the
following boots the >>behaviour is the same again.
If you look at post #16 i had the issue with hirsute where the USB stick
would no longer boot and i had to go to Gnome Disks and untick legacy
bios and then
It seems I only can attach a file per comment. Here you have the second
one file.
** Attachment added: "AfterFirstAttempt"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342/+attachment/5500539/+files/boot2.txt
--
You received this bug notification because you are a member of
Hi Thomas,
As I said yesterday, this changes only work at first boot but in the
following boots the behaviour is the same again.
This happened today with the new version of xorriso and yesterday with
"dd if=/dev/zero bs=1 count=16 of="$NEW" conv=notrunc seek=462" command.
On first boot, after dd
Why not create a BIOS boot partition and install grub on 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:
HIrsute live session takes ages to boot on BIOS systems
To manage
** Tags added: rls-ii-incoming
** Changed in: casper (Ubuntu)
Importance: Undecided => High
--
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:
HIrsute live session takes ages to boot
Hi,
i uploaded a new development snapshot of GNU xorriso which can create a
GPT similar to the result of Lucap's gnome disks run.
cd "$HOME"/xorriso_dir
wget http://www.gnu.org/software/xorriso/xorriso-1.5.5.tar.gz
tar xzf xorriso-1.5.5.tar.gz
cd xorriso-1.5.5
./configure --prefix=/usr
Well, that's strange: the first time I booted from the usb stick it
booted fine, reaching logo on 25 seconds but the second time and the
following it failed again (probably will boot after a long wait but I
did not check)
I'm going to try to reproduce this behavior and send you some logs. The
Hi,
José Marinho wrote:
> GPT PMBR size mismatch (5505347 != 7907327) will be corrected by write.
> ...
> /dev/sdd1 1 7907327 7907327 3,8G ee GPT
> /dev/sdd2 * 0 01 512B 0 Vacía
Looks like fdisk reports to you what would be the result if you let
Hi Thomas.
I corrected the steps I did wrong and I'm going to try to explain the
best I can for letting you know.
<>
I did it and check with xorriso and at least it showed the desired
output:
GPT partition flags: 1 0x0005
But, here begins the problems. When I dd the modified
Hi,
José Marinho wrote:
> 4- [...] I assume that the usb drive shoud have an original ubuntu
> 21.04 ISO burned.
The "$STICK" in the setting of Lucap at comment #44 was additionally
treaded with gnome disks: "edit partition and tick the box that says
Legacy BIOS bootable".
This yielded GPT flags
Bad luck!
It does not work.
I mount the resulting ISO ($NEW) as a loop device and inspect the
partition layout with fdisk. Here is the output:
jose@jose-pc:~/Impish_tests$ sudo fdisk /dev/loop34
Bienvenido a fdisk (util-linux 2.34).
Los cambios solo permanecerán en la memoria, hasta que
Oh wait! I'm just to see this:
In bash there is a special form of quoting:
echo $'\005' | dd bs=1 count=1 conv=notrunc seek=1072 of="$NEW"
And now the output:
.
Media summary: 1 session, 1376337 data blocks, 2688m data, 19.1g free
Volume id: 'Ubuntu 21.04 amd64'
GPT partition
Hi Thomas,
I try the solution from comment #39 erasing the five lines referring to
grub_platform and it did not work.
Now I'm trying to do what you proposed on comment #45 being aware of
comment #46 and, like it happened this morning when I first tried it,
the output of -report_system_area is
Hi,
José Marinho:
> Well, I try the first method (compiling xorriso) and removing the if
> condition from grub.cfg keeping grub_platform command. The usb drive now has
> a GPT partition table but unfortunately, the issue persists so, it seems
> that the grub_platform thing is not the cause.
Well, I try the first method (compiling xorriso) and removing the if condition
from grub.cfg keeping grub_platform command. The usb drive now has a GPT
partition table but unfortunately, the issue persists so, it seems that the
grub_platform thing is not the cause.
If any other test is needed
Hi,
Lucap wrote:
> gnome disks no longer says it's a GPT layout and
> says the first partition is Linux (Bootable)(0x83)
José Marinho wrote:
> in this last experiment I see with Gnome disks that the usb drive with
> the modified iso has a MBR partition table instead the GPT partition table
> of
Thanks José for confirming that and trying Thomas instructions on GPT.
--
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:
HIrsute live session takes ages to boot on BIOS systems
To
@ Lucap
I've just test the iso modified keeping grub_platform command and removing the
part that evaluates the variable and I get the same results as when I removed
both: 32 seconds to togo and 1 minute 22 seconds to language selector.
I wasn't noticed what was changing on partitions layout
>>Thomas Schmitt , Let's try to find out which of the two suspects does
the trick:
Sorry Thomas i tried to read through the instructions but i just simply
don't have any type of command or development skills and i find it
confusing. :(
I'm just a point and click Ubuntu user...
--
You received
I've just built a new ISO with xorriso but this time i never removed
grub_platform and left it all untouched and now the USB stick boots
without any grub_platform error and after 20 to 30 seconds of a black
screen it boots as normal so it's the way the new ISO is being written
to the USB stick as
You might need to hold my hand through this as my technical skills are
limited.
Before i attempt what you ask i've just built a new ISO with
grub_platform removed and it now boots up in the same manner as the
Gnome disk option , after the grub menu it gives a black screen for
about 20 to 30
Hi,
regrettably the display of launchpad's website eats blanks.
This mutilates my proposed grep 'GPT partition flags: 1' by condensing
three blanks before "1" to a single blank.
So i change the inspection proposal to
xorriso -indev stdio:"$NEW" -report_system_area plain | \
grep 'GPT
Hi,
Lucap wrote:
> < MBR partition : 1 0x00 0xee1 5508391
> < MBR partition : 2 0x80 0x0001
> ---
> > MBR partition : 1 0x00 0xee1 15649199
So gnome disks expanded the range of the protective MBR partition to
@Thomas Schmitt
run1.txt = Standard ISO unmodified
run2.txt = Gnome disks - first partition legacy bios enable.
I'll post the difference between the logs , if you want the full logs
posted let me know and i will paste them up.
diff run1.txt run2.txt
21,22c21
< MBR partition : 1 0x00
My bad , I've got it working with /dev/sdc instead of $/dev/sdc.
--
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:
HIrsute live session takes ages to boot on BIOS systems
To manage
@José Marinho
I don't mean to put this on you but as the Gnome disks options also
worked for you i might be better if you run the report_system_area scan
between the normal ISO and the Gnome disk edited version so it gets done
correctly as i'm getting out of my depth here as a point and click
Hi,
José Marinho wrote:
> I made the experiment you proposed modifying grub.cfg file.
> [...]
> So it seems that you find the cause of the problem.
By luck and 14 years of xorriso development. :))
Can i talk you into a second test ?
This time only disable the part in grub.cfg which evaluates
Hi Thomas,
I made the experiment you proposed modifying grub.cfg file. In this case I use
a regular Ubuntu (Main edition with Gnome) Impish iso file.
After Grub I get a blank screen with the cursor blinking and after only 32
seconds I reach Ubuntu logo and after 1 minute and 22 seconds the
Hi,
just in case somebody wants to make experiments with changed grub.cfg,
here are instructions how to create a modified ISO from an Ubuntu amd64
original (but not from a "powerpc" ISO):
Set paths to the original ISO image and for the emerging ISO image:
ORIG=ubuntu-21.04-desktop-amd64.iso
Hi,
Lucap wrote:
> If i look at the USB sticks first partition with gnome disks , edit
> partition and tick the box that says Legacy BIOS bootable then the USB
> stick no longer shows "cannot find grub_platform" and goes straight to
> the grub menu , then it boots to a black screen with a
Amazing how we can all get different results doing the same thing. :)
For me a freshly written ubuntu ISO to a USB regardless if i use Ubuntu
USB creator or DD refuses to boot my old legacy gear that is the last
generation phoenix bios just before EFI was released.
It shows an error just before
Hi,
José Marinho wrote:
> Marking the first partition as bootable legacy BIOS:
> - Plymouth --> 54 seconds.
> - Desktop environment --> 1 minute 45 seconds
Without converting to GPT ?
That would be really strange and surely no solution for the gerneral public.
(It is not allowed by GPT specs to
Well, I'm only came here again firstly to say thanks to Michael and Thomas for
taking into account this problem. Specially, knowing that this bug probably is
quite exceptional and affects at only few cases. Today I was trying on some old
computers on my job and it booted fairly well on all of
Hi,
Chris Guiver wrote:
> Delay occurs regardless of ISO being written using mkusb, dd, or gnome-
> disks..
Hmm. IIRC mkusb offers to unpack the ISO into a filesystem of the USB stick.
If the problem survives that conversion, then it is far inside the GRUB
equipment.
It should be possible to
I'm 'floored' (WOW) by Thomas Schmitt (scdbackup)'s comment 32.
The long delay still exists in impish (on some devices only).
Ubuntu impish - https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1929029
Lubuntu impish - https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1928939
Delay
Hi,
Michael Hudson-Doyle wrote:
> I'm going to
> subscribe Thomas Schmitt, xorriso upstream, who knows enormously more than
> I do about all this stuff.
Well, firmware can always outsmart any preparation in an ISO.
My personal expertise is restricted to ISO 9660 and ends when firmware found
the
Thanks :)
--
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:
HIrsute live session takes ages to boot on BIOS systems
To manage notifications about this bug go to:
On Fri, 21 May 2021 at 02:00, Lucap <1922...@bugs.launchpad.net> wrote:
> Yeah it is complicated , when you look at a freshly written USB stick
> with gnome disks there is a box you can tick that says Legacy BIOS
> bootable , I'm not sure if gnome disks is doing as described below with
> the
Yeah it is complicated , when you look at a freshly written USB stick
with gnome disks there is a box you can tick that says Legacy BIOS
bootable , I'm not sure if gnome disks is doing as described below with
the "bios_grub" flag as the link talks about a hardrive so i'm not sure
if it would apply
If this is it do with the partition table / flags then it needs to be
fixed in debian-cd. You can see the options passed to xorriso here:
https://bazaar.launchpad.net/~ubuntu-cdimage/debian-
cd/ubuntu/view/head:/tools/boot/impish/boot-amd64
As you can see, it's a bit complicated. The name of the
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342/comments/12
Yeah, if you do as post 12 it cuts the black screen boot time of Hirsute
and Impish down to about 20 seconds , not tried it with Lubuntu...
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have confirmed that the bug still exists in Impish and mark your bug report
as it affects me.
@Chris Guiver, as you are more involved in that project and know better than me
the quirks of this processes, tell me if I must close this bug report and if it
is convenient to do something else on
This issue still exists in impish.
Refer https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1928939
Current Lubuntu Focal daily vs Impish daily
plymouth: Focal: ~46 sec Impish: 7 mins 20 secs
scan media start: Focal: ~50 sec
scan media pass: Focal: 3 min 08 sec
black screen & mouse-pointer:
Well i don't hold much confidence if it's not considered important...
I wouldn't be the best person to start a new bug as i don't know what
package this is supposed to be put against , how best to articulate it
or how best to provide any extra information needed as i'm just a point
and click
I'll provide my 2c.
Hirsute (21.04) ISO is already released & development completed. Only
security fixes are now being performed on the now stable 21.04 system,
which does not include this issue (as this issue relates to the ISO
itself, and re-spins are only done for LTS releases, ie. next ISO
Hi @Lucap
I don't kown either at what time is best for reporting that issue and if it is
better continuing here or creating a new bug report.
Perhaps the last option is better because the bug will be reported against next
release and this one is reported against Hirsute Hippo and it's no longer
https://cdimage.ubuntu.com/daily-live/current/
@José Marinho
Don't know if you have tried the latest 21.10 development build but it's
still exactly the same as before as you still have to enable legacy bios
in gnome disks to get it to boot and there's still a long freeze before
it starts.
--
How far into the ‘Impish Indri’ Development should we start reporting
that the live image doesn't boot on legacy computers and do we report it
here or start a new bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Chris Guiver
>>>I dispute that 'they' don't care.
>>>thus bugs with low rating being ignored is to be expected.
Bad choice of words , i should have used i guess it's not considered important.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Well, what they do with this bug report is beyond what you and me can do so
it's their decision. I think that the official iso of Ubuntu (at least if we
talk about a Long Term Support Release) should't have this problem.
Perhaps as they are preparing a new installer that is intended to be used
@lucap
I dispute that 'they' don't care.
Canonical employees are paid to work only a set number of hours a week,
and have responsibilities/tasks they need to complete in their hours, so
have very limited time to fix extra issues.
This bug was reported once during the hirsute cycle in QA-testing
@José Marinho
I've removed the other bug report as i see that you've been trying to
get this resolved for ages with no luck so i'm guessing they just don't
care so it was pointless starting a new one.
I've given up to be honest as there is some really odd stuff going on
with regards to the live
As you like.
I don't know if it's necessary to open a new bug for that, but no problem.
I already marked that the bug you opened as it affects me.
It seems that you have to fill the bug against a package. I don't know which. I
fill that bug against casper, but I think that is not correct.
https://bugs.launchpad.net/ubuntu/+bug/1926260
Thanks Jose, i've opened a bug thread above and the work around , can
you click that This bug affects you too near the top and post in the
thread to confirm the work around?
Thanks
--
You received this bug notification because you are a member of
Well, I just test it with the final ISO downloaded from ubuntu.com and the
problem persists, but with your workaround it boots more quickly.
Perhaps it's a minor issue but I think that it should be avoided because it
gives a bad image to whoever tries Ubuntu for the first time. On a short term
If you look at the freshly written image with Gnome disks , 1st ubuntu
partition , click the cog wheel and choose edit partition you'll notice
that the build team have not enabled the Legacy BIOS bootable option?
If you enable it and click change the drive will now boot , there is
still a really
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: casper (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/1922342
Title:
I just rebooted and timed (phone stopwatch) the boot of
- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
using Ubuntu 21.04 desktop daily (see comment #4;
http://iso.qa.ubuntu.com/qatracker/milestones/419/builds/228934/testcases/1303/results)
which is the device that @jmarinho
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/1922342
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I was doing some new text and I'm going to put some information about
what I have done.
First I create another media with startup disc creator. I think that the
tool is not relevant here and I test with dd, gnome-disk and this tool
and in all I get the same results.
Once created I booted it, but
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342/+attachment/5483802/+files/dmesg.txt
--
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:
Finally, I change the description of the bug for better match the nature
of the problem.
** Description changed:
+ First of all, I change the description of this bug because, thanks to
+ Chris Guiver comments, I could check that the live session effectively
+ works but it takes too long to
79 matches
Mail list logo
