Sponsored Content
Operating Systems Linux Need assistance to enable more that 4GB RAM on Linux 32Bit OS. Post 302429743 by Corona688 on Tuesday 15th of June 2010 11:18:34 AM
Old 06-15-2010
First and foremost is the question, does your system board actually support >4GB of RAM? Even many 64-bit boards don't, and if your system hardware doesn't you're out of luck no matter what kernel you use.

If your board does, and your processor supports PAE, go ahead and use the PAE kernel. There shouldn't be a performance hit so far as I can tell. PAE kernels won't boot on non-PAE processors, which is why it's packaged separately.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Athlon XP + Linux/Unix? and RAM Question

Has anyone had any experience with this new processor and its compatability with Linux/Unix? How did it preform comared to regular Athlons and P4's? I also have one other question. I plan on buying a new dell and fiddling left and right with it. Which type of RAM is better, RDRAM or... (3 Replies)
Discussion started by: KyPeN
3 Replies

2. UNIX for Dummies Questions & Answers

How much RAM does RH Linux need?

I wish to install Red Hat linux 7.1 on a machine with 16mb of EDO Ram. When I enter the instalation process I am told 'You do not have enough memory'. Is there a way to install RHL with only the 16? Or will I have to upgrade and buy some very expensive EDO. ~ Paul (3 Replies)
Discussion started by: KrazyGuyPaul
3 Replies

3. Debian

what is the best linux ver for p100 16 ram

Hello all i own p100 16ram laptop , i would like to run linux on it i need it for gcc compilation and shell scripting , no gui. what version of linux should i install , i dont mind to install old one . tnx allot (5 Replies)
Discussion started by: umen
5 Replies

4. Shell Programming and Scripting

To find the RAM size for an Linux server.

Hi Gurus, Can someone let me know how to find the RAM size,ROM size and Number of processors for a linux server. Version :Linux 2.4.9-e.57smp Also what does "e.57smp" stands for? Thanks in advance gurus..... cheers. (3 Replies)
Discussion started by: navojit dutta
3 Replies

5. Linux

Linux 32bit or 64bit

Hi, I want to know what is command to know which will tell wheather linux is 32 or 64 bit (5 Replies)
Discussion started by: manoj.solaris
5 Replies

6. Linux

Linux version v.s. 32bit/64bit

Where can I get a list that maps the each Linux version to corresponding 32/64 bits model? e.g. OS -> Model (ILP32, LP64, ...) RHLE3 -> ? RHLE4 -> ? RHLE5 -> ? ... It would be better if there is such a list that contains most of current UNIX OS versions. ... (1 Reply)
Discussion started by: princelinux
1 Replies

7. Debian

How to enable and use ACL's in Linux

Hi, How to enable and use ACL's in linux. Thx, siva. (2 Replies)
Discussion started by: Sivaswami
2 Replies

8. Red Hat

red hat Linux 5.0 is detecting 3gb ram but physical ram is 16gb

Hi, On server 64bit Hw Arch , Linux 5.0(32bit) is installed it is showing only 3gb of ram though physical is 16gb can u give me idea why? (4 Replies)
Discussion started by: manoj.solaris
4 Replies

9. Red Hat

32bit Linux vs 64 bit Linux

Friends , Would u plz tell me what is the difference between 32-bit Linux o/s and the 64 bit Linux o/s . Is there any RAM limitation in this two types of o/s . Waiting for kind reply ... ... (7 Replies)
Discussion started by: shipon_97
7 Replies

10. Cybersecurity

root cannot write to Linux RAM

void main() { long ((long)(&array)); int x; for (;;) { (array) =+ 1023; printf("%c", array); } } What is wrong with this code to print Linux RAM? (13 Replies)
Discussion started by: Alux
13 Replies
GLIDE(4)						     Kernel Interfaces Manual							  GLIDE(4)

NAME
glide - Glide video driver SYNOPSIS
Section "Device" Identifier "devname" Driver "glide" ... EndSection DESCRIPTION
glide is an Xorg driver for Glide capable video boards (such as 3Dfx Voodoo boards). This driver is mainly for Voodoo 1 and Voodoo 2 boards, later boards from 3Dfx have 2D built-in and you should preferably use a driver separate for those boards or the fbdev(4) driver. This driver is a bit special because Voodoo 1 and 2 boards are very much NOT made for running 2D graphics. Therefore, this driver uses no hardware acceleration (since there is no acceleration for 2D, only 3D). Instead it is implemented with the help of a "shadow" framebuffer that resides entirely in RAM. Selected portions of this shadow framebuffer are then copied out to the Voodoo board at the right time. Because of this, the speed of the driver is very dependent on the CPU. But since the CPU is nowadays actually rather fast at moving data, we get very good speed anyway, especially since the whole shadow framebuffer is in cached RAM. This driver supports 16 and 24 bit color modes. The 24 bit color mode uses a 32 bit framebuffer (it has no support for 24 bit packed-pixel framebuffers). Notice that the Voodoo boards can only display 16 bit color, but the shadow framebuffer can be run in 24 bit color. The point of supporting 24 bit mode is that this enables you to run in a multihead configuration with Xinerama together with another board that runs in real 24 bit color mode. (All boards must run the same color depth when you use Xinerama). Resolutions supported are: 640x480, 800x600, 960x720, 1024x768, 1280x1024 and 1600x1200. Note that not all modes will work on all Voodoo boards. It seems that Voodoo 2 boards support no higher than 1024x768 and Voodoo 1 boards can go to 800x600. If you see a message like this in the output from the server: (EE) GLIDE(0): grSstWinOpen returned ... Then you are probably trying to use a resolution that is supported by the driver but not supported by the hardware. Refresh rates supported are: 60Hz, 75Hz and 85Hz. The refresh rate used is derived from the normal mode line according to the following ta- ble: Mode-line refresh rate Used refresh rate 0-74 Hz 60 Hz 74-84 Hz 75 Hz 84- Hz 85 Hz Thus, if you use a modeline that for example has a 70Hz refresh rate you will only get a 60Hz refresh rate in actuality. Selecting which Voodoo board to use with the driver is done by using an option called "GlideDevice" in the "Device" section. (If you don't have this option present then the first board found will be selected for that Device section). For example: To use the first Voodoo board, use a "Device" section like this, for example: Section "Device" Identifier "Voodoo" Driver "glide" Option "dpms" "on" Option "GlideDevice" "0" EndSection And if you have more than one Voodoo board, add another "Device" section with a GlideDevice option with value 1, and so on. (You can use more than one Voodoo board, but SLI configured boards will be treated as a single board.) Multihead and Xinerama configurations are supported. Limited support for DPMS screen saving is available. The "standby" and "suspend" modes are just painting the screen black. The "off" mode turns the Voodoo board off and thus works correctly. This driver does not support a virtual screen size different from the display size. SUPPORTED HARDWARE
The glide driver supports any board that can be used with Glide (such as 3Dfx Voodoo boards) CONFIGURATION DETAILS
Please refer to xorg.conf(5) for general configuration details. This section only covers configuration details specific to this driver. The following driver Options are supported: Option "OnAtExit" "boolean" If true, will leave the Voodoo board on when the server exits. Useful in a multihead setup when only the Voodoo board is connected to a second monitor and you don't want that monitor to lose signal when you quit the server. Put this option in the Device section. Default: off. Option "GlideDevice" "integer" Selects which Voodoo board to use. (Or boards, in an SLI configuration). The value should be 0 for the first board, 1 for the sec- ond and so on. If it is not present, the first Voodoo board found will be selected. Put this option in the Device section. EXAMPLE
Here is an example of a part of an xorg.conf file that uses a multihead configuration with two monitors. The first monitor is driven by the fbdev video driver and the second monitor is driven by the glide driver. Section "Monitor" Identifier "Monitor 1" VendorName "Unknown" ModelName "Unknown" HorizSync 30-70 VertRefresh 50-80 # 1024x768 @ 76 Hz, 62.5 kHz hsync Modeline "1024x768" 85 1024 1032 1152 1360 768 784 787 823 EndSection Section "Monitor" Identifier "Monitor 2" VendorName "Unknown" ModelName "Unknown" HorizSync 30-70 VertRefresh 50-80 # 1024x768 @ 76 Hz, 62.5 kHz hsync Modeline "1024x768" 85 1024 1032 1152 1360 768 784 787 823 EndSection Section "Device" Identifier "fb" Driver "fbdev" Option "shadowfb" Option "dpms" "on" # My video card is on the AGP bus which is usually # located as PCI bus 1, device 0, function 0. BusID "PCI:1:0:0" EndSection Section "Device" # I have a Voodoo 2 board Identifier "Voodoo" Driver "glide" Option "dpms" "on" # The next line says I want to use the first board. Option "GlideDevice" "0" EndSection Section "Screen" Identifier "Screen 1" Device "fb" Monitor "Monitor 1" DefaultDepth 16 Subsection "Display" Depth 16 Modes "1024x768" EndSubSection EndSection Section "Screen" Identifier "Screen 2" Device "Voodoo" Monitor "Monitor 2" DefaultDepth 16 Subsection "Display" Depth 16 Modes "1024x768" EndSubSection EndSection Section "ServerLayout" Identifier "Main Layout" # Screen 1 is to the right and screen 2 is to the left Screen "Screen 2" Screen "Screen 1" "" "" "Screen 2" "" EndSection If you use this configuration file and start the server with the +xinerama command line option, the two monitors will be showing a single large area where windows can be moved between monitors and overlap from one monitor to the other. Starting the X server with the Xinerama extension can be done for example like this: $ xinit -- +xinerama FILES
glide_drv.o SEE ALSO
Xorg(1), xorg.conf(5), Xserver(1), X(7) AUTHORS
Author: Henrik Harmsen. X Version 11 xf86-video-glide 1.2.0 GLIDE(4)
All times are GMT -4. The time now is 11:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy