-
This may occur if the MXT driver is holding non-swapable memory to keep the compression above 2X. Kswapd works in
vain to swap out memory (usually from the lower 16MB) but
cannot find any pages to swap out.
1. Determine if the MXT driver is holding memory: Run the
mxtdump2 script. If MemHeld variable is non-zero and steady
then the MXT driver might be responsible.
2. If 1 is true...
2005-02-18 00:46:23 UTC by abali
-
++++++++++++++++++++++++
Works OK in Redhat 7.1. No need for sw_cursor flag.
2005-02-18 00:46:23 UTC by abali
-
The XF86Config option "sw_cursor" is needed.
sw_cursor stands for software cursor.
2005-02-18 00:46:23 UTC by abali
-
If X desktop gets scrambled, it might be because of the problems
with the graphics acceleration. Try adding the lines marked
with "+"
to your XF86Config file, found in /etc/X11/ on Redhat
distributions.
--- XF86Config.orig Sun Apr 22 13:50:22 2001
+++ XF86Config Wed Apr 18 16:01:19 2001
@@ -338,12 +338,14 @@
Section "Device"
Identifier "Matrox|MGA...
2005-02-18 00:46:23 UTC by abali
-
This hang does not have anything to do with mxt.
You are being misled by the "mxt_scan_bios enter" which
happens to be the last message printed before your hang occurs.
This is about the time kernel is initializing all the
modules; a module called after mxt is hanging your system
and not the mxt module.
2005-02-18 00:46:22 UTC by nobody
-
This is a known bios bug.
Linux 2.4.3 MXT support patch 2.4.3-md16 or higher
has a workaround for this.
Bios will be fixed as soon as possible.
2005-02-18 00:46:22 UTC by abali
-
You should have built or booted with 64GB highmem supported
kernel. From LILO: prompt select the right kernel to
boot it with. If you are building your own kernel.
when you do make xconfig, select "Processor Type"
and then select 64GB under High Memory Support.
Rebuild your kernel.
2005-02-18 00:46:22 UTC by abali
-
Address space has a memory hole right below the 4GB limit. This hole is needed for PCI adapters and such. Currently
size of this hole is about 0.5 GB. This is the reason
for seeing less than expected amount of memory. We are
aware of this issue. Size of the PCI hole may get smaller
in the future.
2005-02-18 00:46:22 UTC by abali
-
xosview 1.7.1 is not setup to handle more than 4GB memory size.
As a result some of the memory values may be shown incorrectly,
and the screen may overflow to the left due to negative values.
This is due to the 32-bit internal representation used in
xosview.
We modified xosview 1.7.1 to deal with this problem. Our fix
divides
memory values by 1024 before displaying them. The memory bar...
2005-02-18 00:46:22 UTC by abali
-
That disables the executable bit. Does magicdev
start on next reboot if you do that?.
2005-02-18 00:46:22 UTC by nobody
