i686-linux installation medium on Pentium II fails on boot

  • Open
  • quality assurance status badge
Details
2 participants
  • Skylar "The Cobra" Widulski
  • Josselin Poiret
Owner
unassigned
Submitted by
Skylar "The Cobra" Widulski
Severity
normal
S
S
Skylar "The Cobra" Widulski wrote on 21 Aug 2023 08:29
(address . bug-guix@gnu.org)
841bd669-592d-dfb1-a842-fb7f5807dcac@vern.cc
I've got an old Pentium II machine that I want to install Guix on.
Booting up the i686-linux installation medium, I'm dropped into a guile
REPL with this output visible on the 640x480 rectangle because NeoMagic
framebuffer seems unsupported:
setting up setuid programs in '/run/setuid-programs'...
populating /etc from /gnu/store/lzcvl2y4qsj6fkkq4g42a3zyqj9rsxlr-etc...
creating /etc/machine-id...
/gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/lib/libc.so.6:
CPU ISA level is lower than required
ice-9/boot-9.scm:1685:16: In procedure raise-exception:
ERROR:
1. &invoke-error:
program:
"/gnu/store/j87mrzkw32dc03j9yxf2nxddn8621m1c-dbus-1.12.20/bin/dbus-uuidgen"
arguments: ("--ensure=/etc/machine-id")
exit-status: 127
term-signal: #f
stop-signal: #f
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
GNU Guile 3.0.7
It seems that there is an issue with the P6 (i686) microarchitecture
used in the Pentium II, even though the image is labelled i686. I'm not
sure what problem glibc would have with it.
Explanations? Possible solutions?
-- Cobra
Attachment: OpenPGP_signature
J
J
Josselin Poiret wrote on 22 Aug 2023 12:43
87jztnuzkv.fsf@jpoiret.xyz
Hi Skylar,

"Skylar \"The Cobra\" Widulski" via Bug reports for GNU Guix
<bug-guix@gnu.org> writes:

Toggle quote (29 lines)
> I've got an old Pentium II machine that I want to install Guix on.
> Booting up the i686-linux installation medium, I'm dropped into a guile
> REPL with this output visible on the 640x480 rectangle because NeoMagic
> framebuffer seems unsupported:
>
> setting up setuid programs in '/run/setuid-programs'...
> populating /etc from /gnu/store/lzcvl2y4qsj6fkkq4g42a3zyqj9rsxlr-etc...
> creating /etc/machine-id...
> /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/lib/libc.so.6:
> CPU ISA level is lower than required
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> ERROR:
> 1. &invoke-error:
> program:
> "/gnu/store/j87mrzkw32dc03j9yxf2nxddn8621m1c-dbus-1.12.20/bin/dbus-uuidgen"
> arguments: ("--ensure=/etc/machine-id")
> exit-status: 127
> term-signal: #f
> stop-signal: #f
>
> Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
> GNU Guile 3.0.7
>
>
> It seems that there is an issue with the P6 (i686) microarchitecture
> used in the Pentium II, even though the image is labelled i686. I'm not
> sure what problem glibc would have with it.
> Explanations? Possible solutions?

There apparently was a bug with the ISA stamping that glibc used that
didn't take the -march option into account properly. Since it was
noticed quite quickly after release, I think it should have been fixed
in subsequent versions (although I haven't really looked deep enough
into it). In the meantime, you can try building a new installation
image using an existing Guix (CI doesn't build i686 images for latest).

Best,
--
Josselin Poiret
-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEOSSM2EHGPMM23K8vUF5AuRYXGooFAmTkkWAQHGRldkBqcG9p
cmV0Lnh5egAKCRBQXkC5FhcaipBzDACeEbHEh2qmhnEm+8slPXWs58f7JKTGwFDB
+IHe9NkLJ6khkFqCO/JQl63fLK7jIin+ZpwR5/9AtEb2sNf+bVlX2lPpPbowA0JH
EOEYzP2T2eIiad2Beg5CL5wxsQRHznU2EorT5bY8GKgmeTXG18493zeXwinQtZER
5Js00aQ5xYuWWTcr9lW+PZL3FlWTkSRQt2oRAB78zY8g5MARMkrH2f/7KEGeXlgp
qjpvuuNIXZcKgCxbSHPlU/5hJxOvKySRL/BOWY5OTu4ysCVaOLXCx6nTuaw19oVT
ZPEncTk5kt0rdVpcAhwNROgy+HYyTw+1XYYulX56QNsxQI130sh5BbkmdwxrJBEb
0PHfzfkUD8kE6CyNCJ/ARVO0WQTAkX2spDTHmjDCjfrVQ0HrCoXWMxcxeIdtSLkR
5whMOPY6ULGzEqLwhuZo/qjxf7KpZRx/2Ixcm1VEQvmUsNM6URZN6qk5EUxNnYMP
uASzESCa+zszVWuwDyVaBHkeou3GeHg=
=szGB
-----END PGP SIGNATURE-----

?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 65417@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 65417
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch