Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #261895 > unrolled thread

OT: Livesystem - grub is counting up

Started byHans <hans.ullrich@loop.de>
First post2023-09-25 13:10 +0200
Last post2023-09-26 04:40 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.debian.user


Contents

  OT: Livesystem - grub is counting up Hans <hans.ullrich@loop.de> - 2023-09-25 13:10 +0200
    Re: OT: Livesystem - grub is counting up David Wright <deblis@lionunicorn.co.uk> - 2023-09-25 17:10 +0200
      Re: OT: Livesystem - grub is counting up Hans <hans.ullrich@loop.de> - 2023-09-25 18:40 +0200
    Re: OT: Livesystem - grub is counting up Max Nikulin <manikulin@gmail.com> - 2023-09-26 04:40 +0200

#261895 — OT: Livesystem - grub is counting up

FromHans <hans.ullrich@loop.de>
Date2023-09-25 13:10 +0200
SubjectOT: Livesystem - grub is counting up
Message-ID<HhRDr-bqOD-11@gated-at.bofh.it>
Hi list,

maybe someone can answer my question: 

I am building kali linux 32-bit live from time to time, and then, after I get 
the ISO, I install it as usual to an usb-stick using dd in=****** of=****, 
just as usual.

Now since some months booting this stick changed. In ealier times at boot the 
kali menu started, then it boot.

But today there is first a memeory counter "(XXX/528M)" counting up, then, when 
528 is reached, the kali menu appears and I can boot as normal.

So, question: Why is this so? What has changed and can I avoid this somehow in 
the syslinux or grub menu? 

I saw this behaviour also on other livesystems but not at everyones.

If you can tell me some technical background of this, I would appreciate this.

By the way:  Creating a kali live with 64-bit and same packages, this behavior 
does not appear. 

Any hints?


Best regards

Hans

[toc] | [next] | [standalone]


#261903

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2023-09-25 17:10 +0200
Message-ID<HhVnH-bt4V-19@gated-at.bofh.it>
In reply to#261895
On Mon 25 Sep 2023 at 13:01:51 (+0200), Hans wrote:

> I am building kali linux 32-bit live from time to time, and then, after I get 
> the ISO, I install it as usual to an usb-stick using dd in=****** of=****, 
> just as usual.
> 
> Now since some months booting this stick changed. In ealier times at boot the 
> kali menu started, then it boot.
> 
> But today there is first a memeory counter "(XXX/528M)" counting up, then, when 
> 528 is reached, the kali menu appears and I can boot as normal.
> 
> So, question: Why is this so? What has changed and can I avoid this somehow in 
> the syslinux or grub menu? 
> 
> I saw this behaviour also on other livesystems but not at everyones.
> 
> If you can tell me some technical background of this, I would appreciate this.
> 
> By the way:  Creating a kali live with 64-bit and same packages, this behavior 
> does not appear. 
> 
> Any hints?

Some context might help, but that just looks like POST running.
Typically, CMOS screens have options to change this behaviour.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#261907

FromHans <hans.ullrich@loop.de>
Date2023-09-25 18:40 +0200
Message-ID<HhWMN-btMM-7@gated-at.bofh.it>
In reply to#261903
Hi David,

yes, some CMOS shows similar behaviour, but it looks like grub is making first 
some memeory free, then puts its code in it. 

First i thought, it might be, that the kernel needs space granted, but on the 
other hand, this appears not on 64-bit built livesystem. 

And both systems are built in an identically way.

Weired thing......

Hans 

> Some context might help, but that just looks like POST running.
> Typically, CMOS screens have options to change this behaviour.
> 
> Cheers,
> David.

[toc] | [prev] | [next] | [standalone]


#261925

FromMax Nikulin <manikulin@gmail.com>
Date2023-09-26 04:40 +0200
Message-ID<Hi69r-bzRl-1@gated-at.bofh.it>
In reply to#261895
On 25/09/2023 18:01, Hans wrote:
> But today there is first a memeory counter "(XXX/528M)" counting up, then, when
> 528 is reached, the kali menu appears and I can boot as normal.

At certain moment Ubuntu live images started to verify files on the 
media comparing their checksums. Earlier it was just another boot menu 
option, not a step of default boot procedure. There are might be a key 
to cancel the check (Escape?), but it will unlikely interrupt computing 
checksum of a large file, so delay may be significant.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web