Getting in contact with the i386 porters
Hi, I have a problem with sudo, Bug #1004894. sudo from unstable seems to not work on an AMD Geode LX processor. Unfortunately, I don't have any i386 systems left, there don't seem to be any public i386 porterboxes other than 64bit boxes running 32bit chroots, and the i386 port traditionally doesn't have a port-specific mailing list. i386@buildd.d.o was Cced two weeks ago without any reaction. How would I proceed from here? I suspect this to be a toolchain / buildd essue and feel myself being at a loss regarding this issue. Is the Geode LX supported by the i386 port in the first place? I see Kernel taint flags: TAINT_CPU_OUT_OF_SPEC in the logs, but also CONFIG_MGEODE_LX=y in Debian's i386 kernel. Please advise, thanks. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Re: Getting in contact with the i386 porters
On Tue, 2022-02-15 at 12:28 +0100, Marc Haber wrote: > Unfortunately, I don't have any i386 systems left, there don't seem > to > be any public i386 porterboxes other than 64bit boxes running 32bit > chroots, and the i386 port traditionally doesn't have a port-specific > mailing list. i386@buildd.d.o was Cced two weeks ago without any > reaction. The architecture requalification page for bookworm currently lists a single porter for i386[1]. Maybe contact him directly? It might also be a good idea for people interested in the i386 port to setup a port-specific mailing list. Or for such people to decide what the goal of the i386 port is: run current software on ancient hardware or support running old software (e.g., games) on current hardware. The former would not allow baseline changes, while the latter would allow, for example, using SSE without fallback (which as far as I understand some software already does on i386 or would like to do) or dropping support for AMD Geode processors. Ansgar [1]: https://salsa.debian.org/release-team/release.debian.org/-/blob/bb0660c80401eeacbe7063044a9a1b711dcc2303/www/bookworm/arch_spec.yaml#L108
Re: Getting in contact with the i386 porters
On 2022-02-15 12:28, Marc Haber wrote: > Unfortunately, I don't have any i386 systems left, there don't seem to > be any public i386 porterboxes other than 64bit boxes running 32bit > chroots, and the i386 port traditionally doesn't have a port-specific > mailing list Package sbuild-qemu could help you here: # Build image $ sudo sbuild-qemu-create --arch i386 -o i386.img unstable http://deb.debian.org/debian $ sudo chown : i386.img # Boot QEMU VM to console $ sbuild-qemu-boot --arch i386 i386.img Since this seems to be tied to a particular CPU, you might need to hack the sbuild-qemu-boot script to include a '-cpu' option for qemu-system-i386 with a model that is somewhat similar to the Geode LX. Best, Christian
