PDA

View Full Version : Yay me!


EZ_Ragwheed
01-10-04, 11:11 AM
Posting this from my second computer which now has Mandrake 9.2 on it.

EZ_Talius
01-10-04, 12:36 PM
Give it two minutes before your graphics freeze in a white noise style way and the system needs to be rebooted

EZ_Gyorg
01-10-04, 12:56 PM
See, linux isn't that bad. My uptime for 9.2 box is 14 days right now. (Downtime was because I moved it to the basement.) I had 90 days on my Debian box before I had to take it down to move to DC.

PsiKoTicK
01-10-04, 04:43 PM
Gyorg is in DC now?

When did this happen? I have an evil linux user near me and I have yet to have my windows-sense tingling? :X Veteran Kakarat Doomstalker
65 Barbarian Assassin
Menagerie

Mithrilhall
01-10-04, 05:50 PM
Congrats...I have yet to try 9.2 but I would like to. I've been screwing with Suse 9.0 and it's pretty nice.

Actually...once I get eMule/LMule up and running in Linux it'll probably be running 24/7. Edited by: Mithrilhall at: 1/10/04 5:51 pm

EZ_Gyorg
01-10-04, 08:44 PM
I moved about dec 10th. Moving into my apartment next thurs.

EZ_Ragwheed
01-11-04, 12:29 AM
Ok, so I managed to hose Linux. I tried to change monitor type to 1024x768@60Hz. Tells me log out.log in to take effect. Next thing I know I'm seeing command line. Linux guru attempts to help me get it fixed to no avail. I end up reinstalling, this time I test the setting I want and make it it will work, which it won;t. The best I can get with my crappy video card is 800x600 @60Hz for some reason.

downloading the bf1942 lunix server stuff now. Damn it's late, I think I'll finish trying to set it up tomorrow.

EZ_nekoken
01-11-04, 04:20 PM
Look at /var/log/XFree86.0.log to see why it fails to use better resolutions.

To manually edit your resolutions, look at /etc/X11/XF86Config. You have to play with the sections for both your videocard and for your monitor.

For your vidcard you'll have a default vga definition:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
Driver "vga"
EndSection

But hopefully you'll have a definition for your real card which specifies an actual driver:
Section "Device"
Identifier "GeForceFX 5800"
Driver "nvidia"
VideoRam 131072
Option "ConnectedMonitor" "DFP"
Option "NvAGP" "1"
EndSection

If you have a flatpanel or are lucky you won't have to do much for the monitor. Example:
Section "Monitor"
Identifier "Viewsonic VX900"
HorizSync 30-82
VertRefresh 75
Gamma 1.0
EndSection

If you are unlucky you'll have to specify modelines for your monitor. Example:
Section "Monitor"
Identifier "ViewSonic P775"
HorizSync 30-95
VertRefresh 50-180
Gamma 1.4
Modeline "1152x864" 145.79 1152 1200 1440 1536 864 866 878 948
Modeline "1280x1024" 157.50 1280 1332 1492 1664 1024 1025 1028 1076 +hsync +vsync
Modeline "1024x768" 133.10 1024 1072 1312 1408 768 770 782 808
Modeline "800x600" 106.08 800 840 1040 1120 600 602 614 640
Modeline "640x480" 83.86 640 672 832 896 480 482 494 520
EndSection

Then you'll have a section called 'Screen' which has both the monitor and vidcard device specified along with the modes you want to use.

Section "Screen"
Identifier "Screen 1"
#Device "GeForce3 ti500"
Device "GeForceFX 5800"
Monitor "ViewSonic VX900"
DefaultDepth 24

Subsection "Display"
Depth 8
Modes "1280x1024" "1152x864" "640x480" "800x600" "1024x768"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1152x864" "640x480" "800x600" "1024x768"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1152x864" "640x480" "800x600" "1024x768"
ViewPort 0 0
EndSubsection
EndSection

EZ_Gyorg
01-12-04, 05:47 AM
what are these 2 options:

Option "ConnectedMonitor" "DFP"
Option "NvAGP" "1"

I run the nvidia drivers and if those are useful I wouldn't mind putting them in.

EZ_nekoken
01-12-04, 04:51 PM
From the nvidia README:

Option "NvAGP" "integer"
Configure AGP support. Integer argument can be one of:
0 : disable agp
1 : use NVIDIA's internal AGP support, if possible
2 : use AGPGART, if possible
3 : use any agp support (try AGPGART, then NVIDIA's AGP)
Please note that NVIDIA's internal AGP support cannot
work if AGPGART is either statically compiled into your
kernel or is built as a module, but loaded into your
kernel (some distributions load AGPGART into the kernel
at boot up). Default: 3 (the default was 1 until after
1.0-1251).


Option "ConnectedMonitor" "string"
Allows you to override what the NVIDIA kernel module
detects is connected to your video card. This may
be useful, for example, if you use a KVM (keyboard,
video, mouse) switch and you are switched away when X is
started. In such a situation, the NVIDIA kernel module
can't detect what display devices are connected, and the
NVIDIA X driver assumes you have a single CRT connected.
If, however, you use a digital flat panel connected
via a DVI port instead of a CRT, use this option to
explicitly tell the NVIDIA X driver what is connected.
Valid values for this option are "CRT" (cathode ray
tube), "DFP" (digital flat panel), or "TV" (television);
if using TwinView, this option may be a comma-separated
list of display devices; e.g.: "CRT, CRT" or "CRT, DFP".
Default: string is NULL.

I personally prefer using AGPGART but it doesn't have AGP 3.0 support so I have to use the nvidia AGP driver with my GeForce 5800.

Specifying DFP prevents the driver from having to scan the outputs to see what kind of device is connected. With a flat panel it used to take a couple or three minutes for the driver to figure out that it was the only display device.

EZ_Gyorg
01-13-04, 05:06 AM
Ok. I've had a bit of trouble with the new nvidia driver (the 5000 series one) in that it isn't detecting the video ram and is using the motherboard ram (which makes 3D unusable) in winex3. Wondered if those might be something to account for problems with the new driver. I'd heard there were some problems with it, but the 4496 doesn't want to compile because apperently my kernel isn't compiled with the gcc version I have and some CC check dies.

EZ_nekoken
01-13-04, 12:23 PM
I'm still using 4349 on my box. The two releases after that one had serious bugs in them that made them unusable. One had something really broken that prevented X from running and another had broken light-mapping in GL.

Those options have been present since at least 3123 I believe.