04.04.2010 21:55, Chris Brannon пишет:

Dieter Plaetinck wrote:

...

they "should" work. built from the latest archiso, using the latest configs however when i try to boot the i686 image, just after the isolinux menu, i get this: "this kernel requires an x86_64 cpu, but only detected an i686 cpu. Unable to boot - please use a kernel appropriate for your cpu."

It isn't just the kernel. I mounted the root image via a loop device, and I looked at the pacman data for a random package, zlib. It's x86_64 as well.

I built an i686 netinstall here, using the latest archiso and the latest configs/syslinux-iso, and that booted fine under qemu.

I have no idea what happened.

-- Chris

He would put the last 2 iso: In the first does not work GRUB, the second swears that my i686 .. Fun))

On Sun, 04 Apr 2010 21:56:05 -0300 Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> wrote:

On 04/04/2010 01:35 PM, Dieter Plaetinck wrote:

...

So, i built new images. http://build.archlinux.org/isos/

they "should" work. built from the latest archiso, using the latest configs however when i try to boot the i686 image, just after the isolinux menu, i get this: "this kernel requires an x86_64 cpu, but only detected an i686 cpu. Unable to boot - please use a kernel appropriate for your cpu."

any of the archiso hackers know how this can happen? the makefile does just a `uname -m` and obviously i was in the i686 chroot (and it named the isos i686.iso, so the detection should work) and: cat root-image/etc/mkinitcpio.d/kernel26.kver # DO NOT EDIT THIS FILE ALL_kver='2.6.32-ARCH'

Dieter

Do you enter to your 32 bit chroot with linux32 command?

something like: "linux32 mkarchroot -r bash /tmp/somedir"

yes, i login like this: sudo /usr/bin/linux32 /usr/sbin/chroot /var/archroot-releng-i686/ /bin/login then just `make all` could this be caused by installing archiso like this: cd <archiso git dir> && make DESTDIR=/var/archroot-releng-i686/ install? (ie install it from the host system, which is 64bit) maybe that is what i messed up. Dieter