Re: problems running 3-d applications

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I used to have 24 bit color depth earlier and 3D applications were running fine....So I dont think the problem is there becuase of color depth....anyways i tried the option but its still not working....

On 1/25/06, Gilboa Davara <gilboad@xxxxxxxxx> wrote:
On Wed, 2006-01-25 at 12:13 +0530, Ankur Nayak wrote:
> Hi,
> I am having problems running 3-d applications on my system. I have fc3
> installed on a p4 2.4ghz intel 865 m/b with 32 mb inbuilt graphics
> memory. Eearlier my 3-d applications were running fine. But, recently
> I installed nvidia drivers to test my friend's new graphics card and
> it was working fine. I had made changes to xorg.conf to enable the
> drivers. Now, I dont have the graphics card anymore and I restored my
> xorg.conf back. But now graphics is not working for me. On starting
> "glxgears", I get the following errors...
> ---
> Xlib:  extension "GLX" missing on display ":0.0".
> glxgears: Error: couldn't get an RGB, Double-buffered visual.
> ---
>
> This is my xorg.conf file
>
> # Xorg configuration created by system-config-display
>
> Section "ServerLayout"
>         Identifier     "single head configuration"
>         Screen      0  "Screen0" 0 0
>         InputDevice    "Mouse0" "CorePointer"
>         InputDevice    "Keyboard0" "CoreKeyboard"
> EndSection
>
> Section "Files"
>
> # RgbPath is the location of the RGB database.  Note, this is the name
> of the
> # file minus the extension (like ".txt" or ".db").  There is normally
> # no need to change the default.
> # Multiple FontPath entries are allowed (they are concatenated
> together)
> # By default, Red Hat 6.0 and later now use a font server independent
> of
> # the X server to render fonts.
>         RgbPath      "/usr/X11R6/lib/X11/rgb"
>         FontPath     "unix/:7100"
> EndSection
>
> Section "Module"
>         Load  "dbe"
>         Load  "extmod"
>         Load  "fbdevhw"
>         Load  "glx"
>         Load  "record"
>         Load  "freetype"
>         Load  "type1"
>         Load  "dri"
> EndSection
>
> Section "InputDevice"
>
> # Specify which keyboard LEDs can be user-controlled (eg, with
> xset(1))
> #       Option  "Xleds"         "1 2 3"
> # To disable the XKEYBOARD extension, uncomment XkbDisable.
> #       Option  "XkbDisable"
> # To customise the XKB settings to suit your keyboard, modify the
> # lines below (which are the defaults).  For example, for a non-U.S.
> # keyboard, you will probably want to use:
> #       Option  "XkbModel"      "pc102"
> # If you have a US Microsoft Natural keyboard, you can use:
> #       Option  "XkbModel"      "microsoft"
> #
> # Then to change the language, change the Layout setting.
> # For example, a german layout can be obtained with:
> #       Option  "XkbLayout"     "de"
> # or:
> #       Option  "XkbLayout"     "de"
> #       Option  "XkbVariant"    "nodeadkeys"
> #
> # If you'd like to switch the positions of your capslock and
> # control keys, use:
> #       Option  "XkbOptions"    "ctrl:swapcaps"
> # Or if you just want both to be control, use:
> #       Option  "XkbOptions"    "ctrl:nocaps"
> #
>         Identifier  "Keyboard0"
>         Driver      "kbd"
>         Option      "XkbModel" "pc105"
>         Option      "XkbLayout" "us"
>         Option      "XkbOptions" "ctrl:swapcaps"
> EndSection
>
> Section "InputDevice"
>         Identifier  "Mouse0"
>         Driver      "mouse"
>         Option      "Protocol" "IMPS/2"
>         Option      "Device" "/dev/input/mice"
>         Option      "ZAxisMapping" "4 5"
>         Option      "Emulate3Buttons" "yes"
> EndSection
>
> Section "Monitor"
>
>         #DisplaySize  310       230
>         Identifier   "Monitor0"
>         VendorName   "Monitor Vendor"
>         ModelName    "SyncMaster"
>         DisplaySize  330        250
>         HorizSync     30.0 - 71.0
>         VertRefresh  50.0 - 160.0
>         Option      "dpms"
> EndSection
>
> Section "Device"
>         Identifier  "Videocard0"
>         Driver      "i810"
>         VendorName  "Videocard vendor"
>         BoardName   "Intel 865"
> EndSection
>
> Section "Screen"
>         Identifier "Screen0"
>         Device     "Videocard0"
>         Monitor    "Monitor0"
>         DefaultDepth     24
>         SubSection "Display"
>                 Viewport   0 0
>                 Depth     16
>                 Modes    "800x600" "640x480"
>         EndSubSection
>         SubSection "Display"
>                 Viewport   0 0
>                 Depth     24
>                 Modes    "1280x1024" "1280x960" "1152x864" "1024x768"
> "800x600" "640x480"
>         EndSubSection
> EndSection
>
> Section "DRI"
>         Group        0
>         Mode         0666
> EndSection
> ----------
>
>
> Any help will be appreciated
>
> Thanks,
> Ankur
> --
> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Try removing the 24bit settings.
"Depth     24
Modes    "1280x1024" "1280x960" "1152x864" "1024x768" "800x600"
"640x480""

At least in my case, 3D DRI is only enabled if color depth <= 16bit.

Gilboa

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux