Old NV card set to vesa

Asked by gherardo

I have an NV5 Aladdin TNT2 AGP built in processor. The configurator recognized it but in the X config file in the device section it was incorrectly set to "vesa" instead of "nv".
To correct it I had to (with the help of a capable friend):
1) X -configure did not start because no root password was set (this is a general installation bug)
2) had to start in single mode then set password
3) X -configure then could not start because X was active (! I guess so)
4) get back to single
5) look into X config file for the problem and luckly finding the problem, edit it changing the "vesa" to "nv"

So in the end, I've solved my problem but the above are issues that should be cleaned from the code:
1) nv not set correctly
2) root password not set
3) X -configure cannot start

Thanks for your work, Gherardo

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
gherardo (gherardo) said :
#1

forgot to say I've updated ubuntu to the latest fixes.

Revision history for this message
Dean Sas (dsas) said :
#2

Ubuntu doesn't use a root user, instead using sudo, see http://help.ubuntu.com/community/RootSudo

You also don't need to change run levels to reconfigure your X server, just make your changes then use ctrl+alt+backspace to restart it.

Revision history for this message
gherardo (gherardo) said :
#3

Dean,
  thanks.
I was not aware of the locked root user.
What you mean by "make your changes..." to X config, how? what command since X -configure cannot run? Or you mean to run it using sudo and then ctrl+alt+backspace? (I don't have my ubuntu nearby to try ...)

The NV set to vesa problem remain to be corrected in the X installation configurator....

Revision history for this message
Dean Sas (dsas) said :
#4

By editing the x.org config file with a text editor, while X is still running, then while on the X tty (ctrl+alt+f7) hitting ctrl+alt+backspace. If you meant X was refusing to start at all then that doesn't apply.

You can also run sudo dpkg-reconfigure xserver-xorg which *may* fix your problem.

I've never used X -configure myself so don't really know about it.

Revision history for this message
gherardo (gherardo) said :
#5

"sudo dpkg-reconfigure xserver-xorg" worked.
Had to run twice because of few wrong parameters but now all is fine.

I still think there is a wrong setup during the initial ubuntu installation that possibly detects nv card but writes vesa in the config.

Let me know if you need further infos.
Gherardo

Can you help with this problem?

Provide an answer of your own, or ask gherardo for more information if necessary.

To post a message you must log in.