Gentlefolks. G'day.

PLEASE HELP. My resolution I cannot get to change. Here is my xorg:
And note that my nvidia-drivers are installed, but antix"monitor Settings" basic util, does not change the res to the listed 1280x1024_60.00 mode.

I am quite flustered. Havent used Antix in over a month. Followed several guides but cant get my resolution to the native 1280x1024.
I am very dissapointed in myself, for reaching this point of frustration - in correcting this (simple) fault.
Along with these, there is something that might be adjust in GRUB, what and where was it again?

what else could I be missing?

plz guys - its been long enough __{{emoticon}}__ .
Adding a custom res in this xorg, does nothing

I see that you have the nvidia-xconfig app, do you not have the nvidia settings app? Or is it not available? Or does it not work? I usually can use sgfxi to install nvidia drivers and use the nvidia - settings app to modify the configuration / save the configuration. There have been a few cases where the driver did not play nice and the settings app would not work (Example my multi seat system)

Hw u doing Dave? Thanks for replying.

Presently, you're on my wave-length/page.

I do have the nvidia-xconfig app. I will likely edit this post after confirming if I have the nvidia-settings app.
I can say however that nvidia-xconfig, though it will launch, and display most Tabs - will:
1. Only show me a max res of 640 x 480 & hang if I try that option"Advanced", to possibly edit that.
2. Freeze if I play around with it too much (try clicking each section).

Thus, I've been rendered to this present situation, which you graciously took the time to analyze. (lengthy OP! so thanks).

Nvidia Xconfig (think) also did-up my xorg.conf. Clearly it was not successful.

I tried for a manual mode line using xrandr - no success there either. Namely it spits that"gamma" error I mentioned Above.

So - thats whats up Dave.

Same error was here with Radeon 9200 SE. I have installed the vesa driver, and set up resolution in grub. See vga=ask option. In case of errors X will pick up resolution used by grub.

I got sgfxi to work. Adding custom resolutions hopefully wont be such a pain.

To provide some background/recap, sgfxi broke my display, rather than helping me change from default linux nouveau. The problem in essence/summary was this:

sgfxi - the tool recommended by antixheroes DEFAULTS to installing version 173.14.39 of the legacy nvidia driver (for cards such as my FX5200). This is the latest driver - I was not able to alter which.

HOWEVER. The nvidia driver, works with a kernel module AND with xorg.
debian def:"a binary-only Xorg driver requiring a Linux kernel module for its use"

So afaik, xorg determines which card is available, and which driver to use. A kernel module is also going to be made by the respective nvidia driver package you install. Whether it be the more current 304.xxx.xxx series, or the legacy 173.xxx.xxx

The problem with sgfxi is that it doesnt touch the xorg requirement! Which is that the nvidia-xserver/xorg package be version 173.14.39 TO MATCH the version of the latest legacy driver (ie. one sgfxi installs).

The solution was:

1. Update Xorg : xserver-xorg-video-nvidia-legacy-173xx (this is version 173.14.39
2. Run sgfxi script as root. (it will install NVIDIA DRIVER 173.14.39 by default).

Tada: no more"API mismatch" error.

If this is not done, the xorg-nvidia...binaries, which in Antix are 173.14.35 will not match, and your display will BREAK. (no screens found) being the likely result.

NO OTHER PACKAGE/METHOD helped me, incl installing the 173.xx legacy source OR dkms versions.
Nor was editing a xorg.conf.d file of any kind necessary in this case.

Not that hard, for a couple weeks (months if I count on/off attempts) at trying to fix a legacy nvidia installation.


Hope this helps some poor wandering soul through search-engine hit Someday.
Cheers

Wow glad to see you have figured out the issue, and even happier to see that you posted the solution __{{emoticon}}__
It seems that I must have forgot to reply to your post before (getting good at that lately).... but to be honest, from the solution you have posted I highly doubt that any suggestions on how to fix the problem would have stirred up that solution. In fact I would guess that it would have taken even more time listening to my suggestions than that which it took to figure this out!

I must say kudos to you Grim0x.

It is great when you can figure a solution to the problem and let everyone else know what you did. __{{emoticon}}__

I am thankful to the Lord I got it resolved. What a pain it was - as there was nothing from the log files truly enlightening.
Consequently, as my xorg installation was perfectly fine, I wouldnt have suspected it.

Thank you for chiming in and sharing the sucesss. Eperbab, Dave, jdmeaux