Bug 51615
| Summary: | (Nvidia Geforce2) VC switch away from X doesn't restore console | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Public Beta | Reporter: | Warren Togami <wtogami> | ||||||
| Component: | XFree86 | Assignee: | Mike A. Harris <mharris> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | David Lawrence <dkl> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | roswell | CC: | bugs.michael | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2001-08-24 20:09:33 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Warren Togami
2001-08-13 02:38:34 UTC
Created attachment 27473 [details]
XFree86.0.log
Created attachment 27474 [details]
XF86Config-4
Related to Bug 50930 "Keyboard doesn't work in Failsafe mode" We (Red Hat) should really try to fix this before next release. This note is with regards to the change of summary name to "(Geforce2 MX) VC switch while server starts, crashes X". I am quite sure that this is not an X crash, because if you hit ALT-F7 it will flicker and go back to X, with everything working like it should. Before switching back to the X terminal, you are in a text virtual terminal, but the X server is still displaying the framebuffer and controlling the mouse. FWIW, I'm able to reproduce this on Seawolf with Roswell's kernel 2.4.7-2 and XFree86 4.0.3-5. I get either what is described here, https://listman.redhat.com/pipermail/roswell-list/2001-August/000965.html or I'm back in X (e.g. at the kdm prompt) and cannot type in anything. Additionally, the Red Hat kdm logo disappears quite often. Fortunately, restarting the X server via mouse click on kdm's button restores the keyboard. mschwendt what video controller do you have? Please note that ALT-F7 should also bring you back into X when this bug occurs, with keyboard and mouse fully working. Is this the case? Yes, ALT+F4 at my end due to only three virtual consoles I have configured.
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04)
(prog-if 00 [VGA])
Subsystem: Matrox Graphics, Inc. Millennium G400 16Mb SGRAM
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at dc000000 (32-bit, prefetchable) [size=32M]
Memory at dfefc000 (32-bit, non-prefetchable) [size=16K]
Memory at df000000 (32-bit, non-prefetchable) [size=8M]
Expansion ROM at dfee0000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Capabilities: [f0] AGP version 2.0
I think I see the same. When X11 starts, I often press C-A-F1 to login on the
console. The end result is that the display is in graphics mode, but mouse
and keyboard is grabbed by tty1. When I press enter the graphics mode is
distorted by a newline (it looks weird). Changing back to Alt-F7 works fine
(but the RedHat Logo usually disappear when this happens).
This is on a Dell Latitude LSt laptop, with the NeoMagic MagicMedia card:
Bus 1, device 0, function 0:
VGA compatible controller: Neomagic Corporation [MagicMedia 256AV] (rev
32).
IRQ 10.
Master Capable. Latency=128. Min Gnt=16.Max Lat=255.
Prefetchable 32 bit memory at 0xf6000000 [0xf6ffffff].
Non-prefetchable 32 bit memory at 0xfe400000 [0xfe7fffff].
Non-prefetchable 32 bit memory at 0xfeb00000 [0xfebfffff].
I forgot: I'm using RedHat Linux 7.1, fully updated. Not rosweel. This bug was reported against Geforce2. Each video driver is responsible for saving and restoring the hardware specific registers, therefore, this bug report is specific to this hardware. If other hardware has the same bug, then they should be reported in other bug reports per hardware since any fixes are not going to fix more than one hardware driver. In the case of the Nvidia card. I do not have hardware nor video specifications to debug or troubleshoot this. If you are using the supplied "nv" driver, please report this bug upstream to the XFree86 team by sending a detailed bug report via email to: xfree86 If you are using the Nvidia binary only drivers supplied elsewhere by Nvidia, please contact Nvidia technical support. I'm afraid, I cannot submit my comments on this one as a separate bug (for MGA400) because my configuration is considered unsupported most likely. It is a fully updated Seawolf with Roswell's 2.4.7-2 kernel (2.4.7-2.9 since yesterday) and a couple of irrelevant package upgrades to get ext3 fs. Any important role the kernel version plays here? If appreciated, I could go back to 2.4.3-12 kernel, try to reproduce what has been covered here (especially the lost keyboard), and only then submit a separate bug. For Seawolf, though, not Roswell. |