Hello, (Ubuntu Feisty 64 w/i386 chroot)
I've followed the saga that is Firefox taking too much memory when loading graphically intensive pages (with workaround posted at https://help.ubuntu.com/community/UbuntuLTSP/ResolveRamIssues ), and implemented the workaround a couple of weeks ago. This proved to work for the thin-clients I tested on, but low and behold, the only two thin clients in the lab that have different hardware will not boot as long as this workaround is in place. The error, after 21 lines of what looks similar to this: [21] 0 0 0x800003c0 - 0x800803df (0x20) IS[B](OprU) I get the following error: "Fatal server error: xf86MapVidMem: Could not mmap framebuffer (0x4400000,0x400000) (Cannot allocate memory)" (The memory addresses might not be accurate, I took a screenshot with my Treo which has a low quality camera) Does anyone have any information on why this might be happening? The thin-clients this is affecting are older Compaq iPaq workstations which boot fine without the above Firefox workaround. The ones that do work are newer NeoWare e100 thin-clients. Any help would be greatly appreciated. Thanks!! - Jordan -- Jordan Erickson Owner, Logical Networking Solutions http://www.logicalnetworking.net ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
