Hi everyone,

yes, I know, 32-bit is no more suopporred, but maybe one can answer my questions though.

I have a netbook EEEPC with kali-linux. Everything works fine, but since the change from kernel 5.4 to higher version, I noticed the strange behaviour, that the kernel wil not boot very time.

For me it looks like the kernel itself boots, then the initrd is started to load and then the system hangs. Say: Looks like the load of the initrd hangs.

I have to switch off the device, then start again. This happens so 2 - 3 times,
and then it boots. At this early moments of the boot process I also can not see, what happens. The logs also give no information.

Is this a hardware incompability somehow? The device only has 2GB RAM.

Rhe only unusual I found in the BIOS was the point "CPU-ID" enable/disable, but this shall only effect WindowsXP.

So far so well, my questions:

1. is this issue known?

2. Is there any parameter I can add to the kernel to avoid this hangs? (Itried ecc=off with no succes)

3. Is there any way, to write a log, as soon as the kernel starts? (I suppose not, because at that moment, there are still no partitions mounted. Where shall it write to except to RAM or /boot partition?).

Folks, if no one knows or you think, 32-bit is not worth to think of, no problem! This issue is not a big deal and booting 2 or 3 tries is no big deal, too. I can well live with this issue!

In the other case: Thanks for your help!

Best

Hans

--- PyGate Linux v1.5.12
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2026-02-25, Hans wrote:

2. Is there any parameter I can add to the kernel to avoid this hangs? (Itried
ecc=off with no succes)

remove "quiet" if any and add "debug=vc"

--- PyGate Linux v1.5.12
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 25.02.2026 15:30 Uhr Hans wrote:

yes, I know, 32-bit is no more suopporred, but maybe one can answer
my questions though.

With 13, support for i386 is gone.

I have a netbook EEEPC with kali-linux. Everything works fine, but
since the change from kernel 5.4 to higher version, I noticed the
strange behaviour, that the kernel wil not boot very time.

You have a different OS, but asking in the Debian newsgroup. You will
not find the answers you want here.

If your machine only supports 32 bit, use an OS that supports it. For
example Slackware or NetBSD.

--
kind regards
Marco

Send spam to 1772029802muell@stinkedores.dorfdsl.de

--- PyGate Linux v1.5.12
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Wed, Feb 25, 2026 at 03:10:40PM +0100, Hans wrote:

Hi everyone,

yes, I know, 32-bit is no more suopporred, but maybe one can answer my questions though.

I have a netbook EEEPC with kali-linux. Everything works fine, but since the change from kernel 5.4 to higher version, I noticed the strange behaviour, that the kernel wil not boot very time.

Is this a hardware incompability somehow? The device only has 2GB RAM.

This - 2GB is *very* low memory these days. The eeepc is now VERY old
hardware too. I'm not sure that this will continue to be viable.

So far so well, my questions:

1. is this issue known?

2. Is there any parameter I can add to the kernel to avoid this hangs? (Itried
ecc=off with no succes)

That is probably irrelevant.

3. Is there any way, to write a log, as soon as the kernel starts? (I suppose
not, because at that moment, there are still no partitions mounted. Where shall it write to except to RAM or /boot partition?).

Folks, if no one knows or you think, 32-bit is not worth to think of, no problem! This issue is not a big deal and booting 2 or 3 tries is no big deal,
too. I can well live with this issue!

In the other case: Thanks for your help!

As above, Kali is a Debian derivative and *not* Debian. Strictly, discussion
of non-Debian derivatives is off-topic on this list.

Best

Hans

All the very best to you

Andrew Cater
(amacater@debian.org)

--- PyGate Linux v1.5.12
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

At Fri, 27 Feb 2026 13:06:43 +0100 Marco Moock <mm@dorfdsl.de> wrote:

On 26.02.2026 21:20 Andrew M.A. Cater wrote:

This - 2GB is *very* low memory these days. The eeepc is now VERY old hardware too. I'm not sure that this will continue to be viable.

Certain headless systems run with that.
I run 2 systems with this amount of memory - both are TOR relays and
work fine.

I have a headless Pi 2 with 1G functioning as a Network Print server. I also have a Nano Pi functioning as a [wired] router.

--
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
heller@deepsoft.com -- Webhosting Services


--- PyGate Linux v1.5.12
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Am Freitag, 27. Februar 2026, 13:06:43 Mitteleurop„ische Normalzeit sc
hrieb
Marco Moock:

On 26.02.2026 21:20 Andrew M.A. Cater wrote:

This - 2GB is *very* low memory these days. The eeepc is now VERY old hardware too. I'm not sure that this will continue to be viable.

Certain headless systems run with that.
I run 2 systems with this amount of memory - both are TOR relays and
work fine.

This worked before well, but after kernel upgrade this issue appeared.

For those, who read here: I know, 32-bit is no more supported. You do not
need
to tell me.

I also told, I am running kali linux. But before that, I was running debian/ stable 32-bit on this system and this issue was with the debian system as well.

However, I said, this is not an important issue, although I would like to know, why this happens. I could avoid this issue (if it would be to annoyin
g),
by building a monolithic kernel without the need of an initrd. As the hardw
are
I am using on this computer will not be changed I know, what to compile int
o
the kernel. Or, I leave it as is.

Besides, the advioce "remove the option quiet, and add debug=vc" did not
work,
as the bootimage is not disappearing at tnat moment (but later, whnen the initrd is loaded), so this did not help.

I suggest, if no other ideas are present, then we should just close this discussion. It is really not much important for me to waste your time.

Thank you very much for all your help!

Best regards

Hans

--- PyGate Linux v1.5.12
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Robert Heller <heller@deepsoft.com> writes:

I have a headless Pi 2 with 1G functioning as a Network Print server.

How does that work for you? I tried this once, probably it was a Pi2, to
turn a USB printer into a network printer. Worked well enough to print a
test page but not much more. Often the printer would print nothing but
CUPS had happily logged the job as done. Going to the jobs list in CUPS
and reprinting from there usually worked. Even when it printed it was
super slow even for really simple one page printouts.

Printing was mostly from Windows via Samba so maybe that was an extra complication.

--- PyGate Linux v1.5.12
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2026-02-27, Hans wrote:

Besides, the advioce "remove the option quiet, and add debug=vc" did not work,
as the bootimage is not disappearing at tnat moment (but later, whnen the initrd is loaded), so this did not help.

It is perhaps possible to remove boot screen in the bios to get console
lines. You could also get some informations in /run/initramfs/*

--- PyGate Linux v1.5.12
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 27.02.2026 16:20 Uhr Anssi Saari wrote:

How does that work for you? I tried this once, probably it was a Pi2,
to turn a USB printer into a network printer. Worked well enough to
print a test page but not much more. Often the printer would print
nothing but CUPS had happily logged the job as done. Going to the
jobs list in CUPS and reprinting from there usually worked. Even when
it printed it was super slow even for really simple one page
printouts.

That is an issue of CUPS or the printer itself. I have a Samsung that
does this when it is in standby mode.

--
kind regards
Marco

Send spam to 1772205601muell@stinkedores.dorfdsl.de

--- PyGate Linux v1.5.12
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)