Accidently switched from X to console and x had to create a default config to start

dr_zayus69 · 11-15-2005, 12:57 PM

Hi. Lately i've been practicing using keyboard shortcuts to use the mouse less/not at all. (why? Cuz im nerdy and curious) I went to hit alt + f2 to bring up the run application dialog box in gnome and accidenlty hit f1 and pretty sure i unknownly had ctrl depressed as well. This brought me to the console and i forget the key combo to get back to the gui was (I thought it would have just been pressing ctl+alt+f1) again. So i rebooted figuring i'd get back into the login screen and everything would be fine. The console login came up and flashed a few times then it said X couldn't be started. It gave me the option to view a few outputs related to the error (I viewed them but don't know much about x so it was pointless) Eventually it said it had to create a new config file to be able to restart x. I have the Nvidia driver for my card installed so now i am not postive as to whether or not it is enabled now - i have a feeling it is not. The way i would know is TUXRacer would run sluggish without the driver but if i had it enabled properly it worked perfectly. For some reason TUXRacer won't start. I have a few questions that arise from the situation.

1. what is the key combo to get to the console so i know for sure so im more careful next time?
2. what is the key combo to get back to the gui so if it does happen again i can get back?
3. What could i have done to mess up x by switching to the console?

I forgot if it said it saved my original config file as xorg.conf~ or xorg.conf.backup but here is diff of xorg.conf against both.

Code:

[root@localhost X11]# diff xorg.conf xorg.conf~
1c1,2
< # Xorg configuration created by system-config-display
---
>
> # XFree86 4 configuration created by pyxf86config
4c5
<       Identifier     "single head configuration"
---
>       Identifier     "Default Layout"
10a12
>
14d15
<
18d18
<
34a35
>
37d37
<
40d39
<
97c96
<       DefaultDepth     16
---
>       DefaultDepth     24
102a102,106
>       SubSection "Display"
>               Viewport   0 0
>               Depth     24
>               Modes    "800x600" "640x480"
>       EndSubSection

Code:

[root@localhost X11]# diff xorg.conf xorg.conf.backup
1c1,2
< # Xorg configuration created by system-config-display
---
>
> # XFree86 4 configuration created by pyxf86config
4c5
<       Identifier     "single head configuration"
---
>       Identifier     "Default Layout"
10a12
>
14d15
<
18d18
<
31c31
<       Load  "dri"
---
> #     Load  "dri"
34a35
>
37d37
<
40d39
<
88c87
<       Driver      "nv"
---
>       Driver      "nvidia"
97c96
<       DefaultDepth     16
---
>       DefaultDepth     24
102a102,106
>       SubSection "Display"
>               Viewport   0 0
>               Depth     24
>               Modes    "800x600" "640x480"
>       EndSubSection

thanks for any replies in advance.

rhennig · 11-15-2005, 02:47 PM

1. Ctrl+Alt+F[1-6] - you can have up to 6 consoles (by default).
2. Ctrl+Alt+F7 - default X Windows screen is started on 7 but it is possible to have it on 8 through 12.
3. Replace the xorg.conf file with the xorg.conf.backup file - it has the nvidia required configuration. When the nvidia drivers are loaded, if the xorg.conf file does not have the nvidia parameters set up, it usually won't start X because the nvidia drivers won't load without the correct parameters in the conf file.
Hope that helps!

dr_zayus69 · 11-26-2005, 05:26 AM

Quote:

Originally posted by rhennig
1. Ctrl+Alt+F[1-6] - you can have up to 6 consoles (by default).
2. Ctrl+Alt+F7 - default X Windows screen is started on 7 but it is possible to have it on 8 through 12.
3. Replace the xorg.conf file with the xorg.conf.backup file - it has the nvidia required configuration. When the nvidia drivers are loaded, if the xorg.conf file does not have the nvidia parameters set up, it usually won't start X because the nvidia drivers won't load without the correct parameters in the conf file.
Hope that helps!

when i switched with the .backup one the same scenario repeats. I think the issue is it isn't finding the driver. As far i know i didn't move it at all so i don't know why it stopped working all the sudden.

dr_zayus69 · 12-02-2005, 11:33 PM

i tried to open blender today but i get the same results as tux racer (no response) I know blender uses OpenGL and im assuming tux racer does as well. Maybe this is related to an OpenGL problem? This is really frustrating.

dr_zayus69 · 12-03-2005, 02:22 AM

i found this in /var/log/Xorg.0.log

Code:

(EE) Failed to initialize GLX extension (NVIDIA X driver not found)

i did a search for Nvidia:

Code:

[jeff@localhost ~]$ find / -name [Nn][Vv][Ii][Dd][Ii][Aa] 2> /dev/null
/lib/modules/2.6.12-1.1378_FC3/build/drivers/video/nvidia
/lib/modules/2.6.12-1.1381_FC3/build/drivers/video/nvidia
/lib/modules/2.6.12-1.1376_FC3/build/drivers/video/nvidia
/var/lib/nvidia

and i still have the installer for the driver on my computer so i know i installed it. What do i need to do to make it so the driver is found? Should i just re install it with the installer?

edit: I just ran glxgears for shits. Here is the output.

Code:

glxgears
Xlib:  extension "GLX" missing on display ":0.0".
glxgears: Error: couldn't get an RGB, Double-buffered visual.

thanks for any help in advance.