Jaton 3D Force G-32 Support?

[Sephiroth]

Is the Jaton 3D Force G-32, AGP4X video card supported in Lenny? If so does it have full 3D support? I am building a demo system and this of the Jaton 3D Force B-32 Plus are the best two junk cards I have laying around. No, I do not intend on playing Oblivion with this system, but some basic 3D support would be nice.

[smallchange]

It works with the nv xserver but no acceleration. It is too old for the current legacy drivers from Nvidia. You can get the archived version of the legacy drivers and install them. I don't remember exactly which version contains support but I think it is around 65.

[Sephiroth]

Oh this is an nVidia chipset? I read that it was something like "Triton T-64". If it's nVidia can't I simply use the official nVidia driver on their site?

*EDIT*

This is not an nVidia chipset, but a "Trident Microsystems" chipset.

*EDIT*

The B-32 Plus uses the Riva TNT2 chip, so maybe the official nVidia driver will work with it?

[smallchange]

I have one of those (B-32) and I used it about 6 months ago. It has been removed from the supported models in the Nvidia legacy drivers. You need to get an older version of the legacy driver. You can try the new legacy of course, but I think you will see a logged message about not finding a supported display adapter.

[Sephiroth]

Uh, you sure?

http://www.nvidia.com/object/linux_display_ia32_71.86.11.html
This claims that the Riva TNT and TNT2 are supported.

[smallchange]

Not entirely, although I thought I was. Did this one work?

[llivv]

Not entirely, although I thought I was. Did this one work?

I have one of them too
I bet I could get 3ddesktop in etch to show a cube with it.
I wonder if Sephiroth wants to know if he can run compiz in squeeze with it?
General rule of thumb (as far as I have been able to figure out is) you need at least 128MB of vram
to run most modern 3D apps on a pc.
32MBs doesn't give direct remdering at all
64MB's gives minimal 3D functionality iirc

let us know what you get with the new Version: 71.86.11 driver for the older nvidia chipsets

[Sephiroth]

Sorry was out for the weekend. I am about to install it and will tell you my results.

*EDIT*

Alright I built it, but this thing doesn't have an installer to modify the X config file. I manually added the line "Driver "nvidia"" to the display device section, but now it just blacks out when KDE tries to display the login screen. Not sure if this is a driver issue or something I'm not doing properly in the configuration file. Upon running 'lspci' the last thing listed is "nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15)", which is listed as supported by said driver. Ideas?

*EDIT*

I just went back to using the stock "nv" driver and all is good. I also went in and configured X manually and will be trying the "nvidia" driver again soon, now that the monitor is forced into its native resolution.

*EDIT*

Alright I recompiled the nVidia driver and chose it in place of nv. The system rebooted and I have the login screen, but it took a solid minute to render the five head-like images for each username, and I still can't see anything else. It's like it wants to run on an 8086 or something. I'll figure it out though.

[smallchange]

I would say that the driver is working and you just need to get the configuration right. If so, what you need to do will depend on which version of X you are running, which probably depends on which version of Debian you are running. The later X is better able to auto detect hardware, but if your monitor is also old you may need to give some info about it. The earlier X will require a more extensive xorg.conf file. Look in /var/log/Xorg.0.log to see what is happening.

If X thinks that it failed to load you should be dropped to a text terminal rather than having a blank black screen. It is quite likely that you will find no errors in the log and the X server is running. This is an indication of a problem with something like GDM or KDM.

[Sephiroth]

Bumping for some help. Upon reviewing the Xorg.0.log.old file, I discovered why it runs so slow. My log is spammed with the following.

Code: Select all

tossed event which came in late
mieqEnequeue: out-of-order valuator event; dropping.


I also get about eight warnings scattered through the file like this:

Code: Select all

(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00000548, 0x00005818, 1)


And finally, I got an error listed when it tried loading GLX, which I believe is my problem.

Code: Select all

(EE) GLX is not supported with the Composite extension


I have no modules listed in my device section or in my X configuration, for that matter.

[Sephiroth]

Alright, if I disable the composite extension and use the official driver I get a solid white screen with no visible cursor for the mouse, and my Xorg.0.log shows a bunch of those "WAIT" lines in it, but not the other two error lines. Still looking to get this working.

[smallchange]

My best guess is that this is a mismatch between the nvidia GLX and something in your display manager or what ever is trying to display. I have no idea what you are trying to run, but I would say "simplify".

[Sephiroth]

I can't simplify it any further. I simply want hardware support on this card. I can disable the composite extension and get a white screen with the official driver or I can leave it enabled and have GLX fail to load and have the screen freeze up.

[smallchange]

I doubt that is true but if you provide no information no one can help you.

[Sephiroth]

What more do you need? I have detailed the information as best I can. There is no "extra" information that I am hiding from you. Stock xorg.conf, if I use the nVidia driver with the composite extension on, GLX won't load and video operations freeze, though the machine does not. If I disable the composite extension I get a solid white screen. It's really THAT SIMPLE. The card and LCD monitor are being detected properly according to xorg.0.log. The simple fact is that something odd is happening and I can't figure it out. There is no simplifying this, it has just been described to you in 100% crystal-clear detail. If you can't comprehend an extension causing a problem when loaded and then something else not working when it isn't loaded, I don't know what to tell you.