Neverwinter Nights "Failed to initialize graphics"

yanta · n00b Joined: 14 Jun 2005 Posts: 12

All right, I've been fighting with this problem for weeks now and I'm admitting defeat. Help...

Neverwinter Nights will not start, glxgears crashes my X server, but direct rendering is enabled and OpenGL screensavers work great.

Chipset is S3 Unichrome. After struggling with both the Gentoo DRI how-to here and the Unichrome one here, as well as untold hours of reading posts in these forums like this one, I finally got direct rendering enabled (using the Unichrome via driver and the masked version of x11-drm that supports via on 2.6 kernels).

When I try to run NWN as a user (which honestly is the point of the entire exercise) I get grumpy silence:

gaminggeek · Posted: Sun Jun 26, 2005 5:17 am Post subject:

you might find it easyer if you go out and find yourself a el-cheepo geforce 2 mx....

yanta · n00b Joined: 14 Jun 2005 Posts: 12

Success!!

After losing my ENTIRE weekend to this silly project I finally got everything working. I wanted to post what I did to assist others who might be fruitlessly Googling, trying to get their S3 Unichrome chipset working with DRI. I just ended up building EVERYTHING using the latest and greatest Mesa CVS version. Being that I've never used cvs before in my life, I'm pretty impressed with myself that it's working

.

First, I ended up disregarding both HOW-TOs I linked to above. They both got me in trouble, and I think my strange results came from cherry-picking info out of both of them.

If you're smarter than me you can just follow the instructions here. I got scared off by the warning on the Gentoo HOWTO, and even when I got brave enough to try it I needed a whole day to fight through what applied to me and what didn't... I'll break everything down shotgun-style below for unichrome on x86 with kernel 2.6.11-gentoo-r11. If you have something different make appropriate substitutions. I'm by no means a gentoo guru -- all standard disclaimers apply.

Remove x11-drm if you've installed it (you don't need it).

pulzed · n00b Joined: 19 May 2005 Posts: 20

Thanks for the howto man!!

Will definatly try this soon,,,

leo.fontenelle · Posted: Wed Jul 06, 2005 2:36 am Post subject: Almost ok...

I did things like above, but not everything is ok. I'm posting this in hope that someone can interpret this data:

From /var/log/Xorg.0.log:

Code:

(--) PCI:*(1:0:0) unknown vendor (0x1106) unknown chipset (0x7205) rev 1, Mem @
0xe4000000/26, 0xe8000000/24

[...]

(II) VIA: driver for VIA chipsets: CLE266, KM400/KN400, K8M800,
PM800/PM880/CN400
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset KM400/KN400 found
(!!) VIA Technologies does not support or endorse this driver in any way.
(!!) For support please contact the driver maintainer or your X vendor.
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xea001000 - 0xea0010f0 (0xf1) MX[B]
[6] -1 0 0xea000000 - 0xea0000f0 (0xf1) MX[B]
[7] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]O
[8] -1 0 0xe8000000 - 0xe8fffff0 (0xfffff1) MX[B](B)
[9] -1 0 0xe4000000 - 0xe8000000 (0x4000001) MX[B](B)
[10] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[11] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[12] -1 0 0x0000e800 - 0x0000e900 (0x101) IX[B]
[13] -1 0 0x0000e000 - 0x0000e100 (0x101) IX[B]
[14] -1 0 0x0000dc00 - 0x0000dc10 (0x11) IX[B]
[15] -1 0 0x0000d800 - 0x0000d820 (0x21) IX[B]
[16] -1 0 0x0000d400 - 0x0000d420 (0x21) IX[B]
[17] -1 0 0x0000d000 - 0x0000d020 (0x21) IX[B]
(WW) ****INVALID MEM ALLOCATION**** b: 0xe4000000 e: 0xe8000000 correcting

The last line is part of the output in the console when I call startx. I can't say much about what I see, since I'm still compiling KDE. But I get no twm, no xterm, just standard mouse cursor with a big black background; when I move the the mouse around, the cursor moves very oddly, and becomes something like an ugly square black&white icon representing a 3-button mouse with the right button pressed.
Could it be the version I grabbed from CVS? The output is version 6.8.99.14.

I guess the kernel part is ok, but "direct rendering" and "glx" are complaining:

Code:

$ dmesg |grep agp
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA KM400/KM400A chipset
agpgart: Maximum main memory to use for agp memory: 380M
agpgart: AGP aperture is 64M @ 0xe0000000

$ dmesg |grep drm
[drm] Initialized drm 1.0.0 20040925
[drm] Initialized via 2.6.3 20050523 on minor 0: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video

$ grep render /var/log/Xorg.0.log
(II) VIA(0): direct rendering disabled

$ glxinfo |grep render
Error: unable to open display (null)

I believe I got bad luck about the specific version from CVS, but I can't suspect what to download later: xc? Mesa? DRM??

leo.fontenelle · Posted: Wed Jul 06, 2005 3:30 pm Post subject: Update

Update Finished emerging KDE. Now I see all KDE, and the mouse cursor is beautifull. But the cursor still moves oddly. I believe my configuration is correct for a three-buttons wheel PS/2 mouse, I'm just
posting just in case:

yanta · n00b Joined: 14 Jun 2005 Posts: 12

Do make sure you're loading DRI and GLX in your xorg.conf and you've got the DRI permissions set.

In the "Modules" section at the top, make sure you've got the following lines uncommented:

leo.fontenelle · Posted: Sat Jul 09, 2005 11:40 pm Post subject: It worked!

Silly me... :roll:

Yes, I forgot to enable glx and dri in xorg.conf! The consoles-changing problem got fixed too. And, by the way, even the mouse was misconfigured, it's an explorer ps/2, not intellimouse.

Just a detail... Until this post I had switched back to regular xorg-x11; then I made the cvs Xorg again, and when I restarted things looked a lot larger, without changing resolution or KDE's configs. KDE's panel is the same size, and konsole's console font too, but KDE's splash, titlebar+menu fonts etc are larger.

yanta · n00b Joined: 14 Jun 2005 Posts: 12

Rebuilding after a crash, I have discovered that the current CVS is a little freaky so the above instructions probably don't work.

When building the 3D Mesa driver, you now need to add THREE lines to the linux-dri-x86 config file:

jgaffney · Apprentice Joined: 22 Dec 2004 Posts: 165

OK, I'm attempting to get his to work, but I'm stuck trying to make the linux-dri-x86 file.

yanta · n00b Joined: 14 Jun 2005 Posts: 12

Sorry, I've been out of town. For anyone else having the same problem:

Your hosts.def has to do with the Xorg build; it looks like you're having problems with the 3D driver.

There should be a file in /usr/src/DRM/Mesa/configs called "linux-dri-x86". You need to add the following three lines to the end of this file:

yanta · n00b Joined: 14 Jun 2005 Posts: 12

Ack! More changes! This is what comes of using the cvs, I guess.

Now, to get the 3D driver to compile, you must first compile libdrm. So, to change (yet again) the instructions above, execute the following commands AFTER you compile Xorg and BEFORE you compile the 3D driver: