• Status Unconfirmed
  • Percent Complete
  • Task Type Bug Report
  • Category Packages
  • Assigned To No-one
  • Operating System pentium4
  • Severity Medium
  • Priority Very Low
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Arch Linux 32
Opened by Enrique Dominguez - 13.10.2021

FS#210 - keymap don't gets fixed on login as set in /etc/vconsole.conf

gzip comes with asm code, if enabled, built a TEXTREL which gets bloqued on boot, so systemd don’t set keymap
A lot of tricks in forums, old thread more complete here $506 An old problem. Work around while asm gets fixed is call configure with DEFS=”NO_ASM” like this:

export DEFS="NO_ASM"
./configure ....


./configure DEFS="NO_ASM" ....

I have not tested it, but gentoo on x32 have gzip like this and no TEXTRELS here.
No matter i486, i686 or pentium.

Hope it helps.

Best regards.

Andreas Baumann commented on 20.10.2021 04:51

IMHO we should not disable assembly in gzip in general just because there is a bug in
the resource restrictions in early systemd booting. Also, why does this happen only
on 32-bit and not on 64-bit?

Then I would rather opt to drop the compression of keymap and character set files

..or to find this ancient bug in (possibly) systemd. :-)

Enrique Dominguez commented on 18.11.2021 13:21

Hi, I don't get notified about your response, sorry for the delay. As far I know, it's not a bug in systemd, but gzip asm itself. On 32bits results on TEXTREL aka security flaw because you get a stack WX. Disabling asm for x32 is a temporary workaround much better than having a vulnerable binary. More here (you don't have to ship 'the big book about elf' ;) )
It's not a systemd bug this time; systemd keeps us from running a broken binary.


Available keyboard shortcuts


Task Details

Task Editing