You are not logged in.
I'm using XOrg CVS, Mesa CVS, and DRM CVS, trying to get hardware acceleration to work for my onboard Prosavage 8 VPU. My problem is my xorg.conf file, which I can't seem to get right... I either have DRI and totally fubar graphics (think TV tuned to a really distorted, weak signal), or perfectly good graphics but no DRI.
So, here's the data on my monitor, a Sony Trinitron: HWD says that it's 28-96 KHz hsync (believable), and 50-75 Hz vsync (I think it's actually more like 50-100, but under normal circumstances I don't use vsync above 75 Hz). My normal setting for XOrg is 1280x1024 pixels; the monitor runs this at 79.9 KHz hsync and 75 Hz vsync.
Here's the xorg.conf file I set up for DRI:
# Auto-generated by Archie mkxcfg
# Auto-generated by Archie mkxcfg
Section "ServerLayout"
# Serial Mouse not detected
# USB Mouse not detected
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "PS/2 Mouse" "CorePointer"
EndSection
Section "Files"
# Additional fonts: Locale, Gimp, TTF...
# FontPath "/usr/X11R6/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/X11R6/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi"
FontPath "/usr/X11R6/lib/X11/fonts/PEX"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/X11R6/lib/X11/fonts/defoma/CID"
FontPath "/usr/X11R6/lib/X11/fonts/defoma/TrueType"
FontPath "/usr/X11R6/lib/X11/fonts/artwiz-fonts"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "GLcore"
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "type1"
Load "freetype"
Load "record"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
Option "XkbVariant" "nodeadkeys"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "Auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "Monitor"
# Warning: This may fry old Monitors
# Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
### Uncomment if you don't want to default to DDC:
### Uncomment if you don't want to default to DDC:
Identifier "Monitor0"
### Uncomment if you don't want to default to DDC:
HorizSync 28.0 - 96.0
VertRefresh 50.0 - 75.0
ModeLine "1280x1024" 79.9 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
EndSection
Section "Device"
Identifier "Card0"
Driver "savage"
VendorName "All"
BoardName "All"
ChipSet "Savage4"
Card "savage Savage4"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
Does that "Modeline" line need editing or something? If so, what do I change? Is there something else wrong with my xorg.conf?
Offline
huh? modeline look strange to me...
[paul@night ~]$ gtf 1280 1024 75
# 1280x1024 @ 75.00 Hz (GTF) hsync: 80.17 kHz; pclk: 138.54 MHz
Modeline "1280x1024_75.00" 138.54 1280 1368 1504 1728 1024 1025 1028 1069 -HSync +Vsync
(remember to remove the "_75.00" bit when inserting into xorg)
If you're getting 1280x1024 then the prosavage driver is ignoring the default color depth
Offline
... Huh? I think you messed up with your copying and pasting...
ModeLine "1280x1024" 79.9 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
Offline
My normal setting for XOrg is 1280x1024 pixels; the monitor runs this at 79.9 KHz hsync and 75 Hz vsync
The "79.9" in the modeline is the pixel clock rate, not hsync. What modeline does "gtf" produce for you if you want 1280 x 1024 @75Hz?
Offline
[proteus@localhost ~]$ gtf 1280 1025 75
# 1280x1025 @ 75.00 Hz (GTF) hsync: 80.25 kHz; pclk: 138.67 MHz
Modeline "1280x1025_75.00" 138.67 1280 1368 1504 1728 1025 1026 1029 1070 -HSync +Vsync
Thanks.
Offline
Oh... Forgot to mention: there was another problem. It was impossible to load the savage module for some bizarre reason... Even when the drm module was loaded. Any reason for this? It didn't seem to affect XOrg with regard to DRM (no errors at all in the log, DRI on), but is there any particular reason that this was the case? Could it have had some effect on X, without producing any error messages?
Offline
I haven't played with the savage driver since I built my daughter a PC with onboard video over 18 months ago. I had trouble getting direct rendering working at that time. I got it working by installing the latest "common" and "savage" tarballs from freedesktop snapshots which is probably the best place to find help. I think there may have been some extra stuff to do - like specifying the full path to the modules in the (Xfree86) config file.
Sorry I can't remember more.
Offline
Thanks... I suppose I'll try again at some point.
Offline
Okay, tried again using the latest common and savage snapshots, plus the Xorg binary, from dri.freedesktop.org/snapshots. It's no go: the install script gave me the same error that I got with the CVS when modprobing savage, that the module couldn't be inserted because it contained an unknown symbol. Methinks the driver is currently broken... I'll wait until the next snapshot comes out.
Also, using X with those drivers installed and without DRI enabled does not work, giving me the old fuzzy screen... Damned if I know what's going on there.
And finally, this:
# 1280x1024 @ 75.00 Hz (GTF) hsync: 80.17 kHz; pclk: 138.54 MHz
Modeline "1280x1024_75.00" 138.54 1280 1368 1504 1728 1024 1025 1028 1069 -HSync +Vsync
is wrong. Why? Notice the hsync: 80.17 kHz. At 1280x1024@75, my monitor's hsync (according to its own menu/info display) is 79.9 kHz. Something fishy is going on here.
Offline
# 1280x1024 @ 75.00 Hz (GTF) hsync: 80.17 kHz; pclk: 138.54 MHz Modeline "1280x1024_75.00" 138.54 1280 1368 1504 1728 1024 1025 1028 1069 -HSync +Vsync
is wrong. Why? Notice the hsync: 80.17 kHz. At 1280x1024@75, my monitor's hsync (according to its own menu/info display) is 79.9 kHz. Something fishy is going on here.
I wouldn't worry too much about it. My guess is there might be an allowed tolerance in the vesa specifications or due to rounding errors. The manual for my AG Neovo F-417 for instance specifies VESA 1280x1024@75Hz as using 80Khz and a pixel clock rate of 135 - no decimal places or anything.
Offline
Ah... Alright.
Now I think I understand the business with the modprobe failing... That's probably a bug, as it didn't happen the previous times I've tried to get DRI working.
What I don't get is the utterly screwed up graphics I get when using the "DRIed" XOrg without any 3D acceleration. I'm talking "screwed up" as in "nought but thick black columns with thin white lines in between, lots of staticky grey fuzz, and a perfectly ordinary cursor."
Offline