For the Wine 'too much RAM' issue, I found two possible fixes:
1)add the mem=3072 (for 3GB) or mem=2048 (For 2GB) flag to your kernel
boot parameters (from
http://appdb.winehq.org/objectManager.p ... &iId=14154 )
2)set up wine-get and apply a patch (from
http://bugs.winehq.org/show_bug.cgi?id=10778 )
Which is the better choice for a user who needs a stable system?
Over 4GB RAM issue
Over 4GB RAM issue
On Wed, 2009-02-25 at 10:17 -0600, Austin English wrote:
is the problem yet.
In grub.conf I have two lines that start with kernel, one in this:
title Fedora (2.6.27.15-170.2.24.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.15-170.2.24.fc10.x86_64 ro
root=/dev/VolGroup00/LogVol00 rhgb quiet
and one in this:
title Fedora (2.6.27.12-170.2.5.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.12-170.2.5.fc10.x86_64 ro
root=UUID=1d89eae5-278b-4fed-b1b5-08ffa039ffd8 rhgb quiet
Do I add mem=3072 to the end of both?
Okay, I'm going to go with easy/quick since I'm not completely sure thisOn Wed, Feb 25, 2009 at 10:11 AM, tparker <[email protected]> wrote:Easier/quicker.For the Wine 'too much RAM' issue, I found two possible fixes:
1)add the mem=3072 (for 3GB) or mem=2048 (For 2GB) flag to your kernel
boot parameters (from
http://appdb.winehq.org/objectManager.p ... &iId=14154 )
is the problem yet.
In grub.conf I have two lines that start with kernel, one in this:
title Fedora (2.6.27.15-170.2.24.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.15-170.2.24.fc10.x86_64 ro
root=/dev/VolGroup00/LogVol00 rhgb quiet
and one in this:
title Fedora (2.6.27.12-170.2.5.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.12-170.2.5.fc10.x86_64 ro
root=UUID=1d89eae5-278b-4fed-b1b5-08ffa039ffd8 rhgb quiet
Do I add mem=3072 to the end of both?
Over 4GB RAM issue
On Wed, Feb 25, 2009 at 12:34 PM, tparker <[email protected]> wrote:
--
-Austin
Whichever one you boot from (likely 2.6.27.15).On Wed, 2009-02-25 at 10:17 -0600, Austin English wrote:Okay, I'm going to go with easy/quick since I'm not completely sure thisOn Wed, Feb 25, 2009 at 10:11 AM, tparker <[email protected]> wrote:Easier/quicker.For the Wine 'too much RAM' issue, I found two possible fixes:
1)add the mem=3072 (for 3GB) or mem=2048 (For 2GB) flag to your kernel
boot parameters (from
http://appdb.winehq.org/objectManager.p ... &iId=14154 )
is the problem yet.
In grub.conf I have two lines that start with kernel, one in this:
title Fedora (2.6.27.15-170.2.24.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.15-170.2.24.fc10.x86_64 ro
root=/dev/VolGroup00/LogVol00 rhgb quiet
and one in this:
title Fedora (2.6.27.12-170.2.5.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.12-170.2.5.fc10.x86_64 ro
root=UUID=1d89eae5-278b-4fed-b1b5-08ffa039ffd8 rhgb quiet
Do I add mem=3072 to the end of both?
--
-Austin
So I added mem=3072 to the end of the line:
kernel /vmlinuz-2.6.27.15-170.2.24.fc10.x86_64 ro
root=/dev/VolGroup00/LogVol00 rhgb quiet
in grub.conf and rebooted.
I get a post beep and then:
PANIC: early exception 0e rip 10:ffffffff81025977 error 0 cr2 ffffffffff5fc0f0
So I obviously did something wrong but do not know what or how to fix it.
kernel /vmlinuz-2.6.27.15-170.2.24.fc10.x86_64 ro
root=/dev/VolGroup00/LogVol00 rhgb quiet
in grub.conf and rebooted.
I get a post beep and then:
PANIC: early exception 0e rip 10:ffffffff81025977 error 0 cr2 ffffffffff5fc0f0
So I obviously did something wrong but do not know what or how to fix it.
Thanks I will try mem=3G when I can. Does anyone know how I get past the kernel panic to re-edit grub.conf?
The system does have another kernel listed when I try the system recovery option (F11) just before the panic, but when that loads all I have is a blinking line cursor to type at, no log in options and no idea what to do.
The system does have another kernel listed when I try the system recovery option (F11) just before the panic, but when that loads all I have is a blinking line cursor to type at, no log in options and no idea what to do.
Over 4GB RAM issue
On Wed, Feb 25, 2009 at 3:22 PM, tparker <[email protected]> wrote:
you need to fix, then press 'e' to edit it. Remove that line, then use
'b' to boot.
--
-Austin
Hit escape when grub comes up to disable timeout, select the kernelThanks I will try mem=3G when I can. Does anyone know how I get past the kernel panic to re-edit grub.conf?
The system does have another kernel listed when I try the system recovery option (F11) just before the panic, but when that loads all I have is a blinking line cursor to type at, no log in options and no idea what to do.
you need to fix, then press 'e' to edit it. Remove that line, then use
'b' to boot.
--
-Austin
You could edit the line right before the start in grub. Simply press a key to stop booting the default kernel and then press 'e' to edit the entry. And 'e' to edit the line. Change the mem parameter and press 'b' to boot the kernel. (I don't know if these are the correct keys but there is an explanation on the screen, after you hit a key to interrupt grub not to start the default kernel.)tparker wrote:Thanks I will try mem=3G when I can. Does anyone know how I get past the kernel panic to re-edit grub.conf?
Thank you very much Austin and Rico. I was able to follow your instructions and changed the '3072' to '3G' and the kernel booted.
Is there a way to have a note added about that to the section of the how to at http://appdb.winehq.org/objectManager.p ... &iId=14154 since the format it says is "mem=3072 (for 3GB) or mem=2048 (For 2GB)"? Just in case some other newb runs into this problem as well.
After the system boot I checked the 'about this computer' and it says I have 3GB RAM, not 5GB, so it looks like that worked. Now I'm off to load WoW and Vent and see if they still use too much memory and crash.
Thank you again for your time and patience.
Is there a way to have a note added about that to the section of the how to at http://appdb.winehq.org/objectManager.p ... &iId=14154 since the format it says is "mem=3072 (for 3GB) or mem=2048 (For 2GB)"? Just in case some other newb runs into this problem as well.
After the system boot I checked the 'about this computer' and it says I have 3GB RAM, not 5GB, so it looks like that worked. Now I'm off to load WoW and Vent and see if they still use too much memory and crash.
Thank you again for your time and patience.
Over 4GB RAM issue
On Wed, Feb 25, 2009 at 3:59 PM, tparker <[email protected]> wrote:
--
-Austin
Done.Thank you very much Austin and Rico. I was able to follow your instructions and changed the '3072' to '3G' and the kernel booted.
Is there a way to have a note added about that to the section of the how to at http://appdb.winehq.org/objectManager.p ... &iId=14154 since the format it says is "mem=3072 (for 3GB) or mem=2048 (For 2GB)"? Just in case some other newb runs into this problem as well.
No problem.Thank you again for your time and patience.
--
-Austin
Over 4GB RAM issue
On Wed, 2009-02-25 at 11:11 -0500, tparker wrote:
graphics on the lowest possible settings I can buy 45 minutes to an hour
between game crashes as long as I'm careful where I go.
Which, unless someone has a better idea, leaves me with:
before in Linux and I don't really understand what the patch does
so before jumping into it want to ask-
Does this patch do anything different than just limiting the memory did?
Since that already failed I don't want to do something I'm likely to
mess up a few times if there's no real chance of it fixing the
problem.
I tried this (at 3G) and it did not fix the problem, if I put theFor the Wine 'too much RAM' issue, I found two possible fixes:
1)add the mem=3072 (for 3GB) or mem=2048 (For 2GB) flag to your kernel
boot parameters (from
http://appdb.winehq.org/objectManager.p ... &iId=14154 )
graphics on the lowest possible settings I can buy 45 minutes to an hour
between game crashes as long as I'm careful where I go.
Which, unless someone has a better idea, leaves me with:
The couple of how-tos I found for this go beyond anything I have done2)set up wine-git and apply a patch (from
http://bugs.winehq.org/show_bug.cgi?id=10778 )
before in Linux and I don't really understand what the patch does
so before jumping into it want to ask-
Does this patch do anything different than just limiting the memory did?
Since that already failed I don't want to do something I'm likely to
mess up a few times if there's no real chance of it fixing the
problem.
The fix in that bug will work better than without, but games will still crash occasionally.
BTW the bug will still occur no matter how much physical RAM you have, it only applies to virtual memory.There was a mmap patch posted a month or so back that is supposed to fix the issue.But games slow down to a crawl on 64-bit systems with 4GB ram or greater, and the patch simply doesn't work otherwise.Not even on a 32bit system with 2GB ram.
Also some are suggesting that this may be a nvidia driver bug here: http://www.nvnews.net/vbulletin/showthread.php?t=127984
Although this may be an unrelated issue.
BTW the bug will still occur no matter how much physical RAM you have, it only applies to virtual memory.There was a mmap patch posted a month or so back that is supposed to fix the issue.But games slow down to a crawl on 64-bit systems with 4GB ram or greater, and the patch simply doesn't work otherwise.Not even on a 32bit system with 2GB ram.
Also some are suggesting that this may be a nvidia driver bug here: http://www.nvnews.net/vbulletin/showthread.php?t=127984
Although this may be an unrelated issue.
