Sponsored Content
Full Discussion: Hacking in the forums
Contact Us Post Here to Contact Site Administrators and Moderators Hacking in the forums Post 21471 by Neo on Thursday 16th of May 2002 02:17:48 PM
Old 05-16-2002
Boris888:

I don't have any definition wrong and have been in this business before there were hackers and the Internet. This subject is not open for debate.

Also, posting email address in the forums is against the rules. As an admin looking in; it would appear that you register and come to the boards, breaking rules and demand the boards adapt to your wishes.

My friendly suggestion is to go to another board if you are looking for other discussions.

LivinFree:

Thanks for the post. You are exactly right and I appreciate your professional attitude and excellent work.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hacking

I asked my firend about hacking so he told me to come here. I want to know how to get Volumes I, II and III. Does anyone know how to help me and help me become a good hacker? This is what i came here to do!!!!!! (2 Replies)
Discussion started by: nfsu2
2 Replies

2. Linux

Hacking

Im wondering how i can chat to some one (1 Reply)
Discussion started by: Neas
1 Replies

3. UNIX for Dummies Questions & Answers

Hacking in UNIX

Just give link to hacking soft like ipscanners, brutforses, firewalls , etc maybe you know about new projects in this area p.s. thanks for help You might want to read the rules - Note # 11. Thread closed. (0 Replies)
Discussion started by: Ty3
0 Replies

4. Cybersecurity

What kind of hacking is going on here??

Connecting to the Internet with OpenVPN, the connection fails. Rerunning openvpn works second time round but the install is hacked at that point (e.g., a rogue 'java-security' update tries to install itself on 'yum update', yum however spots this and rejects the download, other basic things start... (3 Replies)
Discussion started by: GSO
3 Replies

5. Cybersecurity

hacking

I want to start with hacking and learning it from the scratch! I have googled and found thousands of pages but I would like to know how to start really! It's always good to hear from security experts. please give me some links. the ones which are related to unix hacking. (1 Reply)
Discussion started by: messi777
1 Replies

6. What is on Your Mind?

Hacking buddy

Hi, I am looking for a technical soul willing to play around with technical stuff and exchange the knowledge and experience no matter how skilled would that be either begginer or experienced geek. If anybody interested just ping me in the thread here. Wish you a great day! (9 Replies)
Discussion started by: smoofy
9 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 06:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy