[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems

Mon May 16 11:42:42 UTC 2022

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 wouldn't influence result), alas I didn't use stopwatch then & didn't
note which option I used

> (#92) 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

ie. system operation in ~5 mins (<5 I believe as clock had just flipped
13:22 as it appeared), but I didn't say if persistent OR live was used.

OPTION USED THIS TIME = LIVE only  (not persistent)

BOOT 1: LIVE
started stopwatch as I pressed ENTER at grub
by 2 mins 43 secs the system appeared functional

BOOT2:  LIVE
00:25 secs & screen blanks & messages
00:35 plymouth visible
01:11 message(s) again & plymouth gone
02:23 system fully-operational

BOOT3:  LIVE
00:29 secs & screen blanks & messages
00:35 plymouth visible
01:10 message(s) again & plymouth gone
02:25 system fully-operational

BOOT4:  PERSISTENCE
00:27 secs & screen blanks & messages
00:34 plymount visible
01:41 message(s) again & plymouth gone
03:06 system fully-operational

(boot 4 and there was a longer delay between wallpaper being drawn & the
menu responding to wacom-pen or SUPER key being pressed & menu appearing
which is what I use to detect 'fully-operational)

Boot 2 & 3 are identical; any differences will be me needing to press
the screen on the phone more than once to get it to register 'lap' time.

Re-creating test #101 using Ubuntu Desktop 22.04 LTS (comment #101) 

> - 00:09 enter pressed at GRUB
> - 08:06 screen blacked
> - 08:20 ubuntu plymouth first appeared
> - 09:52 plymouth is gone, system text message appears
> - 10:10 maybe-ubiquity TRY INSTALL prompt
> - 10:37 system fully operational

(I started time at ENTER PRESSED at GRUB, so 9 secs difference expected)

08:01 screen blanked
08:08 ubuntu plymouth first appeared
09:41 plymouth is gone, system text message(s) appear
10:08 maybe-ubiquity; TRY/INSTALL prompt
10:55 system fully operational

Times here start out consistent (9 secs difference expected as I started
time with right hand as I hit enter at grub with left, last time it was
when I saw 'grub' prior to grub.menu appearing), however at MAYBE-
UBIQUITY times differed a bit.. and final-operational differs well
beyond any user/me error(s)

Picking when a system is 'fully operational' is subjective, so a few
secs difference can be just me using wacom-pen touching screen OR
hitting SUPER at the right sec, versus a short delay (as I'm not hitting
key/pen rapidly), but we have ~30 secs difference (10mins37secs-9sec
10m55s?)

> (#102) Are those times stable or do they vary by minutes ?

To me as a user they feel ~stable; but BOOT 1 of Lubuntu LIVE was slower
than BOOTS 2 & 3 (which were consistent; boot 4 was different mode)..
and some some times of Ubuntu Desktop were identical; but by end they
differed beyond I believe could be me.

They don't vary by minutes though in my opinion; secs like this is all
I've generally noted (and some of those secs are likely me/dog; hitting
my phone with the wacom pen for the device instead of my finger as I did
on last test; I can't see that adding 20 secs though! etc)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/1922342

Title:
  Impish live session takes ages to boot on BIOS systems

Status in Release Notes for Ubuntu:
  Fix Committed
Status in casper package in Ubuntu:
  Confirmed
Status in casper source package in Impish:
  Confirmed
Status in casper source package in Kinetic:
  Confirmed

Bug description:
  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 complete. That's why I change the
  description of the bug from live session does not boot to live session
  takes ages to boot. I hope this is the best approach to this.

  I think the problem is the same as described here:
  https://discourse.ubuntubudgie.org/t/20-10-grub-error-can-t-find-
  command-grub-platform/4292. I can see prior to grub menu, briefly, the
  same error: Error can't find grub_platform. After the solution
  described below, this error is not showed and the system is able to
  boot.

  I try making the live usb using startup disk creator and with gnome-
  disks --> Restore disk image and get the same results.

  The live-usb has a gpt partition table instead of mbr like 20.04 live-
  usb has. That implies, I think, that the first one does not boot on
  BIOS systems and the second does.

  I try the same live-usb on an EFI laptop and it boots perfectly
  (perhaps it takes long time, but more less than in this case.

  If I try the solution described here:
  https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1905491/comments/8
  then it works.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: casper 1.461
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 09:55:24 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=gl_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions