View previous topic :: View next topic |
Author |
Message |
NotExcessive Apprentice
Joined: 10 May 2005 Posts: 235
|
Posted: Tue Aug 08, 2006 10:30 am Post subject: Proliant 7000 - doubled the RAM - slowed the mouse! [Solved] |
|
|
I've just doubled the RAM on my Proliant 7000 from 512MB to 1GB. I modified the kernel command line from
Code: | memmap=exactmap memmap=640k@0M memmap=511M@1M |
to
Code: | memmap=exactmap memmap=640k@0M memmap=1023M@1M |
as you should, and fired it up.
Everything works fine except for the mouse when I launch X. Whereas it used to follow along just fine, now it updates across the screen only about 4 times a second, and is so sluggish that it takes about 2 seconds to catch up with me. It's like dragging it through treacle. As far as I can tell, the machine runs at normal speed and even the graphics applications like Firefox run fine, once I've taken 2 minutes of delicate nudging to get the stupid mouse pointer over the application icon.
I've tried cutting the kernel invocation back to Code: | memmap=exactmap memmap=640k@0M memmap=511M@1M | but as long as I leave the full 1GB in there, it's fudge. Pull out the extra RAM to take it back to the original 512MB and it's fine. Seems just the presence of the full 1GB with or without the full memmap=1023M argument is enough to bring this on.
I'm lost as to an explanation of what's going on.
Anyone?
Last edited by NotExcessive on Wed Aug 09, 2006 8:03 am; edited 1 time in total |
|
Back to top |
|
|
kerick n00b
Joined: 20 Jan 2003 Posts: 59
|
Posted: Tue Aug 08, 2006 7:58 pm Post subject: |
|
|
You could try compiling the kernel with the 1GB low memory option and see if that speeds things up. Otherwise you have a rough 1/4 to 1/8 ( i forget which ) or your ram stuck in high memory.
...Also, I don't think I've ever had need of that kernel command line option. _________________ -----------------
Thats funny, my post count tells me I'm a n00b... |
|
Back to top |
|
|
NotExcessive Apprentice
Joined: 10 May 2005 Posts: 235
|
Posted: Tue Aug 08, 2006 10:49 pm Post subject: |
|
|
Yes the kernel has been compiled with HIGHMEM off. The mem parameters for the kernel are needed on the Compaq Proliant servers. If you don't add them, the machines run like a dog.
As an aside, I've started up gpm, and noticed that in a text console, the mouse behaviour is exactly the same, so it's not an X issue - more of an issue with the PS/2 side of things. How that ties into the extra memory, I don't know. |
|
Back to top |
|
|
kerick n00b
Joined: 20 Jan 2003 Posts: 59
|
Posted: Wed Aug 09, 2006 4:45 am Post subject: |
|
|
You could check if its the ram thats doing it, which I admit would be odd but not totally surprising.
By that I mean put the new 512 in place of the original. _________________ -----------------
Thats funny, my post count tells me I'm a n00b... |
|
Back to top |
|
|
NotExcessive Apprentice
Joined: 10 May 2005 Posts: 235
|
Posted: Wed Aug 09, 2006 6:54 am Post subject: |
|
|
That's the first thing I did. Run it on the original 512MB, goes like a rocket. Run it on the new 512MB, goes like a rocket. Run it on the total 1024MB, goes like a dog with a dead gerbil up its butt.
This seems to be affecting the IRQ for the PS/2 port the mouse is plugged into. Otherwise the machine runs fine. |
|
Back to top |
|
|
NotExcessive Apprentice
Joined: 10 May 2005 Posts: 235
|
Posted: Wed Aug 09, 2006 8:02 am Post subject: |
|
|
PS: Just solved the issue by removing ACPI support. Don't know why this was forced by simply increasing the RAM, but it runs along like it used to now. |
|
Back to top |
|
|
|