Vitaliy wrote:
Austin English wrote:
With ubuntu updating to the 2.6.24 kernel, a lot more people are running into errors about reserving memory. This patch adds a suggestion to check /etc/sysctl.conf.
You may need to edit /etc/sysctl.conf to give Wine access to this memory.\n",
Can you be more specific what did Ubuntu do to break Wine?
It would have been helpful if Austin had linked to the bug report from his patch. I went and filed a (very well documented :-) bug report http://bugs.winehq.org/show_bug.cgi?id=12548 that turned out to be a dup of the one Austin had been discussing the bug in.
Austin's patch is helpful, but I think we can do better. For instance, we could ship a helper app that pops up a gui and asks whether the user wants us to work around the problem (by doing gksudo sysctl -w vm.mmap_min_addr=0, say) and run it in the preloader if we can't map the lowest page.
On Sun, Apr 13, 2008 at 2:43 PM, Dan Kegel dank@kegel.com wrote:
Vitaliy wrote:
Austin English wrote:
With ubuntu updating to the 2.6.24 kernel, a lot more people are running into errors about reserving memory. This patch adds a suggestion to check /etc/sysctl.conf.
You may need to edit /etc/sysctl.conf to give Wine access to this memory.\n",
Can you be more specific what did Ubuntu do to break Wine?
It would have been helpful if Austin had linked to the bug report from his patch. I went and filed a (very well documented :-) bug report
http://bugs.winehq.org/show_bug.cgi?id=12548 that turned out to be a dup of the one Austin had been discussing the bug in.
Austin's patch is helpful, but I think we can do better. For instance, we could ship a helper app that pops up a gui and asks whether the user wants us to work around the problem (by doing gksudo sysctl -w vm.mmap_min_addr=0, say) and run it in the preloader if we can't map the lowest page.
I had started to notice it whenever ubuntu upgraded the hardy kernel to 2.6.24. A helper app would be good, but in the meantime, I think a link to a wiki page with links to the bug #'s, etc would be helpful. I wrote the patch before your (very detailed :-D) report, however.