Hi,
i didn't get any response on the user-mailinglist, so i try the devel-list. here's my problem:
since i upgraded my kernel to 2.6.16, wine segfaults immediatly after i start it. When i upgraded to 2.6.16, i also chose to use the 2G/2G vmsplit.
Is wine supposed to work with that config?
Thanks Sven
Sven Köhler skoehler@upb.de writes:
i didn't get any response on the user-mailinglist, so i try the devel-list. here's my problem:
since i upgraded my kernel to 2.6.16, wine segfaults immediatly after i start it. When i upgraded to 2.6.16, i also chose to use the 2G/2G vmsplit.
Is wine supposed to work with that config?
No, it won't work (and other apps will break too). Don't mess with vmsplit.
since i upgraded my kernel to 2.6.16, wine segfaults immediatly after i start it. When i upgraded to 2.6.16, i also chose to use the 2G/2G vmsplit.
Is wine supposed to work with that config?
No, it won't work (and other apps will break too). Don't mess with vmsplit.
That message is understood.
But since kernel 2.6.16, the vmsplit can be chosen via "make menuconfig" - so more and more users of 2G/2G, the new 3G/1G-split or even 1G/3G may appear.