You are not logged in.

#1 2010-02-23 15:19:38

TioDuke
Member
Registered: 2009-08-06
Posts: 24

Cannot Ctrl+Alt+F1 after nvidia-173xx update

I have recently discovered that I cannot switch into "terminal mode" with the latest nvidia-173xx drivers (nvidia-173xx-173.14.25-1 and nvidia-173-xx-utils-173.14.25-1). Whenever I do Ctrl+Alt+Fn, the screen goes black with no terminal prompt. Then the only thing to do is Ctrl+Alt+F8 (F8 instead of F7, as it used to be) to go back to the X11 session.

This happens also if I logout from KDE and select "Console login" from within the KDM menu: the screen just goes black (after flickering a bit): in this case the only solution is to wait for KDM to kick in and display the (GUI) login screen.

An other thing I discovered is that, when I shutdown/restart the computer and the X11 session is terminated, the screen goes back to terminal mode but the display (and all those messages about services going down) is dimmed down.

The temporary solution for me is to go back to the previous version: nvidia-173xx-173.14.22-4 and nvidia-173-xx-utils-173.14.22-4. Here everything is fine (going to console mode, screen during shutdown, etc.)

Here it is my xorg.conf:

Section "ServerLayout"
    Identifier     "Layout0"
    Screen         "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Clone" "off"
    Option         "Xinerama" "off"
EndSection

Section "Files"
EndSection

Section "ServerFlags"
    Option         "AllowMouseOpenFail" "on"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
    Option         "Protocol" "Standard"
    Option         "XkbLayout" "ca"
    Option         "XkbModel" "microsoftpro"
    Option         "XkbOptions" "compose:rwin,terminate:ctrl_alt_bksp"
    Option         "XkbRules" "xfree86"
    Option         "XkbVariant" "multi"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Acer"
    ModelName      "X183H"
    HorizSync       31.0 - 80.0
    VertRefresh     55.0 - 76.0
    Modeline       "1360x768@60" 84.50 1360 1392 1712 1744 768 783 791 807 -HSync +Vsync
    Option         "DPMS"
    Option         "DPI" "96x96"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce FX 5200"
    Option         "RenderAccel" "True"
    Option         "TripleBuffer" "True"
    Option         "PixmapCacheSize" "300000"
    Option         "OnDemandVBlankinterrupts" "True"
    Option         "IgnoreEDID" "True"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "ConnectToAcpid" "False"
    SubSection     "Display"
        Depth       24
        Modes      "1360x768@60"
    EndSubSection
EndSection

And here you have my kdmrc (in case it is of any help):

[General]
ConfigVersion=2.4
ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6
PidFile=/var/run/kdm.pid
ReserveServers=:1,:2,:3
ServerVTs=-7
StaticServers=:0

[Shutdown]
BootManager=None
HaltCmd=/sbin/halt
RebootCmd=/sbin/reboot

[X-*-Core]
AllowNullPasswd=false
AllowRootLogin=false
AllowShutdown=Root
AutoReLogin=false
ClientLogFile=.xsession-errors-%d
Reset=/usr/share/config/kdm/Xreset
Session=/usr/share/config/kdm/Xsession
SessionsDirs=/usr/share/config/kdm/sessions,/usr/share/apps/kdm/sessions
Setup=/usr/share/config/kdm/Xsetup
Startup=/usr/share/config/kdm/Xstartup

[X-*-Greeter]
AntiAliasing=false
ColorScheme=Oxygen
FaceSource=AdminOnly
FailFont=Sans Serif,10,-1,5,75,0,0,0,0,0
ForgingSeed=1250611569
GUIStyle=Oxygen
GreetFont=Serif,20,-1,5,50,0,0,0,0,0
GreetString=Welcome to %s at %n
GreeterPos=50,50
HiddenUsers=
Language=en_US
LogoArea=Logo
LogoPixmap=/usr/share/apps/kdm/pics/kdelogo.png
MaxShowUID=65000
MinShowUID=500
Preloader=/usr/bin/preloadkde
SelectedUsers=
ShowUsers=NotHidden
SortUsers=true
StdFont=Sans Serif,10,-1,5,50,0,0,0,0,0
Theme=/usr/share/apps/kdm/themes/oxygen-air
UseBackground=true
UseTheme=true
UserCompletion=false
UserList=true

[X-:*-Core]
AllowNullPasswd=true
AllowShutdown=All
NoPassEnable=false
NoPassUsers=
ServerArgsLocal=-nolisten tcp
ServerCmd=/usr/bin/X -br -novtswitch -quiet
TerminateServer=true

[X-:*-Greeter]
AllowClose=false
DefaultUser=sergio
FocusPasswd=true
LoginMode=DefaultLocal
PreselectUser=Previous

[X-:0-Core]
AutoLoginEnable=true
AutoLoginLocked=false
AutoLoginUser=sergio
ClientLogFile=.xsession-errors

[Xdmcp]
Enable=false
Willing=/usr/share/config/kdm/Xwilling

I wasn't able to find any relevant messages in Xorg.log.  Another piece of information that may be relevant: the framebuffer resolution is set to "vga=773" in GRUB (which, I think, automatically disables KMS).

I'd rather be able to upgrade my nvidia driver in the future. Have anyone experienced the same problem? Is there any workaround it?

Thank you very much.

[Edit] I forgot: I am on i686, the monitor is an LCD widescreen and the nvidia card is an old one: FX 5200 [/Edit]

Last edited by TioDuke (2010-02-23 15:22:46)


[img]http://boincstats.com/signature/-1/user/2670943/sig.png[/img]

Offline

#2 2010-03-01 20:05:33

TioDuke
Member
Registered: 2009-08-06
Posts: 24

Re: Cannot Ctrl+Alt+F1 after nvidia-173xx update

Bump.

It also happens when setting the framebuffer resolution to "vga=normal" in GRUB.


[img]http://boincstats.com/signature/-1/user/2670943/sig.png[/img]

Offline

#3 2010-03-04 12:46:41

totsilence
Member
Registered: 2010-02-01
Posts: 21

Re: Cannot Ctrl+Alt+F1 after nvidia-173xx update

Hey, I can confirm this, albeit with a different driver.

I have upgraded nvidia drivers from 190.56 to 195.36 and I can't switch back into console once X is started. The boot output is printed correctly though.
There is also another issue: If I don't set vga= in the boot options, my boot output hangs at "Waiting for udev uevents to be processed [busy]" (see: http://bbs.archlinux.org/viewtopic.php?id=92189).
.After a while X will start, even without vga= parameter.

The problem definitely doesn't exist with 190.56...
Maybe time for a bug report to NVIDIA?

Problem also stayed even if I exchanged vesafb for uvesafb.

Cheers
Bastian

Offline

Board footer

Powered by FluxBB