I saw the same Segmentation fault appear a few times in the voluminous output when executing: sudo apt-get install wine
and every time I invoke "wine" regardless of parameters. (although I don't believe I saw any Timeout messages)
I too am using a pi5, with 8Gb of Ram.
Graham
vide@pentomino:~ $ which wine
/usr/bin/wine
vide@pentomino:~ $ ls -la /usr/bin/wine
lrwxrwxrwx 1 root root 22 Feb 18 2023 /usr/bin/wine -> /etc/alternatives/wine
vide@pentomino:~ $ ls -la /etc/alternatives/wine
lrwxrwxrwx 1 root root 20 Feb 18 2023 /etc/alternatives/wine -> /usr/bin/wine-stable
vide@pentomino:~ $ ls -la /usr/bin/wine-stable
-rwxr-xr-x 1 root root 1029 Feb 18 2023 /usr/bin/wine-stable
vide@pentomino:~ $ /usr/bin/wine-stable -h
Segmentation fault
vide@pentomino:~ $ head -5 /usr/bin/wine-stable
#!/bin/sh -e
wine32=/usr/lib/wine/wine
wine64=/usr/lib/wine/wine64
vide@pentomino:~ $ /usr/lib/wine/wine64 -h
Segmentation fault
vide@pentomino:~ $ strace /usr/lib/wine/wine64 -h
execve("/usr/lib/wine/wine64", ["/usr/lib/wine/wine64", "-h"], 0x7fffc2f66218 /* 23 vars */) = -1 EINVAL (Invalid argument)
+++ killed by SIGSEGV +++
Segmentation fault
vide@pentomino:~ $ strace /usr/lib/wine/wine64 ./gcc6809.exe
execve("/usr/lib/wine/wine64", ["/usr/lib/wine/wine64", "./gcc6809.exe"], 0x7ffffa451878 /* 23 vars */) = -1 EINVAL (Invalid argument)
+++ killed by SIGSEGV +++
Segmentation fault
I remember from using wine on a pi3 that there was a problem with the memory configuration, but there I got a helpful error message and was able to correct it:
pi@fake09:~/src/max6809 $ wine max6809.exe
Warning: memory above 0x80000000 doesn't seem to be accessible.
Wine requires a 3G/1G user/kernel memory split to work properly.
wine: failed to map the shared user data: c0000018
Could something similar be happening here except it fails before it can issue the warning? Has wine been tested on a pi5 in 64-bit mode?
(without making this post even longer I will just add that I have also tried a lot of options with amd64 and i386 installations of wine running under binfmt multiarch...)
Oh wait... this is the 4K vs 16K page thing again, isn't it? Maybe needs kernel=kernel8.img in config.txt ...
YES! That fixed it.
and every time I invoke "wine" regardless of parameters. (although I don't believe I saw any Timeout messages)
I too am using a pi5, with 8Gb of Ram.
Graham
vide@pentomino:~ $ which wine
/usr/bin/wine
vide@pentomino:~ $ ls -la /usr/bin/wine
lrwxrwxrwx 1 root root 22 Feb 18 2023 /usr/bin/wine -> /etc/alternatives/wine
vide@pentomino:~ $ ls -la /etc/alternatives/wine
lrwxrwxrwx 1 root root 20 Feb 18 2023 /etc/alternatives/wine -> /usr/bin/wine-stable
vide@pentomino:~ $ ls -la /usr/bin/wine-stable
-rwxr-xr-x 1 root root 1029 Feb 18 2023 /usr/bin/wine-stable
vide@pentomino:~ $ /usr/bin/wine-stable -h
Segmentation fault
vide@pentomino:~ $ head -5 /usr/bin/wine-stable
#!/bin/sh -e
wine32=/usr/lib/wine/wine
wine64=/usr/lib/wine/wine64
vide@pentomino:~ $ /usr/lib/wine/wine64 -h
Segmentation fault
vide@pentomino:~ $ strace /usr/lib/wine/wine64 -h
execve("/usr/lib/wine/wine64", ["/usr/lib/wine/wine64", "-h"], 0x7fffc2f66218 /* 23 vars */) = -1 EINVAL (Invalid argument)
+++ killed by SIGSEGV +++
Segmentation fault
vide@pentomino:~ $ strace /usr/lib/wine/wine64 ./gcc6809.exe
execve("/usr/lib/wine/wine64", ["/usr/lib/wine/wine64", "./gcc6809.exe"], 0x7ffffa451878 /* 23 vars */) = -1 EINVAL (Invalid argument)
+++ killed by SIGSEGV +++
Segmentation fault
I remember from using wine on a pi3 that there was a problem with the memory configuration, but there I got a helpful error message and was able to correct it:
pi@fake09:~/src/max6809 $ wine max6809.exe
Warning: memory above 0x80000000 doesn't seem to be accessible.
Wine requires a 3G/1G user/kernel memory split to work properly.
wine: failed to map the shared user data: c0000018
Could something similar be happening here except it fails before it can issue the warning? Has wine been tested on a pi5 in 64-bit mode?
(without making this post even longer I will just add that I have also tried a lot of options with amd64 and i386 installations of wine running under binfmt multiarch...)
Oh wait... this is the 4K vs 16K page thing again, isn't it? Maybe needs kernel=kernel8.img in config.txt ...
YES! That fixed it.
Statistics: Posted by gtoal — Sat Jun 21, 2025 8:55 pm