Menu
▾
▴
[coLinux-devel] [ colinux-Feature Requests-3133824 ] Blue screen with PAE forceenabled with more as 4GB RAM
|
From: SourceForge.net <no...@so...> - 2010-12-09 23:32:00
|
Feature Requests item #3133824, was opened at 2010-12-09 22:30 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=3133824&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Priority: 5 Private: No Submitted By: KRavEN () Assigned to: Nobody/Anonymous (nobody) Summary: Blue screen with PAE forceenabled with more as 4GB RAM Initial Comment: I'm having a problem with the latest colinux snapshot and a kernel that is PAE forceenable and patched to remove the license restrictions preventing more than 4gb of ram. Here's the article with a ton of information about the licensing restrictions and using more than 4gb ram with 32bit Windows. http://www.geoffchappell.com/viewer.htm?doc=notes/windows/license/memory.htm When I try to start colinux while running this patched kernel and PAE forceenabled I get a bluescreen. System is Windows Vista Enterprise Edition, 32-bit SP1 ntkrnlpa 6.0.6001.18488 with 4gb ram. colinux runs perfectly under unpatched kernel without PAE forceenabled boot option. I've attached the app I used to patch my kernel and run the necessary bcdedit commands to create a new boot entry. It would be terrific if colinux could be made work in this scenario. I have a Lenovo T400 laptop and normally I only have 2517MB total memory shown under task manger -> performance. With PAE and the patched kernel I have 3989MB. This makes a huge difference in performance and if colinux worked too I would upgrade to 8gb of ram. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2010-12-10 00:32 Message: This is a double from tracker ID 3001398 "Start coLinux with bluescreen on Win7 with 4GB+ RAM" See https://sourceforge.net/tracker/?func=detail&aid=3001398&group_id=98788&atid=622063 ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2010-12-10 00:25 Message: Your article link was interesting. Current coLinux can't run on machines where operating system uses 4GB RAM or more. Problem is not only the PAE. PAE is supported. But we can't handle 64 bit for physical memory access. The limit ist not only the Windows driver. Inside Linux part of coLinux we have a second memory mapper. This is inside Linux kernel, and the code there does only work up to 32 bit physical memory. If Windows give coLinux a memory page that exist above the 4GB, then this memory page can't access from inside Linux. An other problem is AWE (Address_Windowing_Extensions) can't handle by coLinux. See also forum entry "How to let coLinux run in large RAM" https://sourceforge.net/projects/colinux/forums/forum/342354/topic/3467832 Only what we can do, is to disallow the start. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=3133824&group_id=98788 |
