[SOLVED] Issue installing Wine in Box86 on a raspbian pi2; HowTo?

Hello,
I have installed Box86 on a pi2 with raspbian bullseye on it

uname -a

Linux 5.15.61+ #1579 Fri Aug 26 11:08:59 BST 2022 armv6l GNU/Linux

sudo apt-get update

OK:1 http://archive.raspberrypi.org/debian bullseye InRelease Holen:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15,0 kB] OK:3 https://itai-nelken.github.io/weekly-box86-debs/debian InRelease Holen:4 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages [13,2 MB] Es wurden 13,2 MB in 1 min 38 s geholt (135 kB/s). Paketlisten werden gelesen… Fertig

according this list of command https://docs.google.com/document/d/1...g0Crwq9Eg/edit
I should install the wine Linux32bits binaries from Debian.

Now at the step "wine wineboot" I receive the message "non valid command"

so far I have tried the install of both packages of wine

wget https://dl.winehq.org/wine-builds/de...uster_i386.deb

and

wget https://dl.winehq.org/wine-builds/de...eye-1_i386.deb

with the same error message.

Any hint where it could come from (and to come around) is welcome.

Update 1: according https://ptitseb.github.io/box86/X86WINE.html#examples
Raspberry Pi users: Wine requires a 3G/1G split memory kernel. Raspberry Pi OS for the Pi 4 already has a 3G/1G split kernel and works with Wine, but the Pi 3B+ and earlier models have a 2G/2G kernel and require a custom-compiled 3G/1G kernel to get Wine working.
So now, I am looking how to compile a 3G/1G kernel

The error "non valid command" seems strange. Is that the exact error message?

yes, for me it looks like arm and intel packages are mixed, but I'm not really sure about that. From the other hand rpi2 is not really capable to run wine.

Originally Posted by pan64 yes, for me it looks like arm and intel packages are mixed, but I'm not really sure about that. From the other hand rpi2 is not really capable to run wine.

That was my first thought too, but I think that is what Box64 is all about. There are "tricks" that let you run foreign architecture binaries in a chroot, and I guess Box64 does something like that.

Evo2.

The pi 2 really isn't up to that. Now is this a recent purchase? Because as of version 1.2 Arm have upgraded the Pi 2 from the A7 32bit core to the 64bit A53 core

I don't even think there's a straight Arm32 windows package any more.

All the development has gone to 64bit arm. Even they suck. 28nm Lithography on the BCM2711 in the RazPi 4. That's bad. There's been success using qemu, and I'd look at going that road. You might get there without wine. But I still feel you should start with more horsepower.

Hello,
my small project was running on a pi4.
But I got the question from a person asking if it runs on a pi2. Now I try to compile a new kernel ("custom-compiled 3G/1G kernel to get Wine working" according Box86 advice) for the pi2 since 24h running time. Now I am thinking in starting the kernel in qemu, compiling there, then send it back to the pi2. Then see if the error message is still there. Now I am searching for this possibility.

But I got the question from a person asking if it runs on a pi2.

Is he paying you? If not, then send me your contact details on PM and I'll ask you questions every time I want something difficult done for nothing .

Hello,
In fact that is a PI 1 (guess Pi2 was wrong).

cat /proc/cpuinfo

processor : 0 model name : ARMv6-compatible processor rev 7 (v6l) BogoMIPS : 697.95 Features : half thumb fastmult vfp edsp java tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xb76 CPU revision : 7 Hardware : BCM2835 Revision : 000e Serial : 000000002a35d1af Model : Raspberry Pi Model B Rev 2

I cross compiled a new kernel 3G/1G.

Memory: 112064K/393216K available (9232K kernel code, 1335K rwdata, 2912K rodata, 432K init, 546K bss, 19008K reserved, 262144K cma-reserved)

.. and error still there..

wine wineboot

Ungültiger Maschinenbefehl

wine is there..

ls -l /usr/local/bin/wine

lrwxrwxrwx 1 root root 22 11. Okt 11:33 /usr/local/bin/wine -> /home/pi/wine/bin/wine

ls -l /home/pi/wine/bin/wine

-rwxr-xr-x 1 pi pi 13867 15. Okt 17:32 /home/pi/wine/bin/wine

Take my advice and don't do this to yourself. It would be a good box for building into something, but you're not at the races with that equipment.

Ungültiger Maschinenbefehl
usually means the binary is not executable on the current system, because of incompatibility.
For example you want to run 64bit code on a 32bit system or arm code on intel or something similar.

Originally Posted by business_kid Take my advice and don't do this to yourself. It would be a good box for building into something, but you're not at the races with that equipment.

I know. The working hobby project cost 350Eur (pi4 + etc.).
I was thinking about a low cost version (hobby again).

https://ptitseb.github.io/box86/COMPILE.html

show

"A build for model 2, 3 and 4 can be done. Model 1 and 0 cannot (at least not with Dynarec, as they lack NEON support)"

= I stop here since I have a Model 1 board.

Just as a matter of interest, I managed to compile box64 on my RazPi 4, w/4G of ram. I wanted it for Zoom, but with over 1G of system, and 3-4G of Zoom & emulation, I'm trespassing into swap. That said, the Zoom client works for a basic meeting. The video is good, startup is dead slow, ~1 minute to draw the border for windows, ~2 mins to fill them in. Frankly, you'd want the 8G model. I'm overclocking at 2Ghz and once startup is over I hardly pass 250% cpu.

Edit: I had a Pi 0 once. My son saw it as an sbc, and grabbed it for some low traffic server he needed. He tried with three sbcs, but ended up replacing them all with a smart monitor! Not one of his better efforts.