That doesn't seem to be a problem here... when I kill the xterm I just get dumped back to a (working) text console. I tried both with and without DRI enabled, after booting with the default (80x25) text mode.
On Sun, Dec 02, 2001 at 01:55:47PM -0600, Carl Wilhelm Soderstrom wrote: > I've got a similar situation with an identical card and linux distro. > I can repeatably freeze the console with the following procedure: > > startx from the console, with no window manager, only launching an xterm. > log in to another virtual console as the same user you started X as, 'export > DISPLAY=:0.0'; and start a window manager (actually, any X client, I think). > switch back to the graphical console (should now be displaying a window > manager), and kill the xterm (ctrl-d). > switch to the virtual console where I started the window manager, and kill > the window manager. > > at this point the console hangs; displaying a blank (tho not dark) screen. > attempting to switch to any virtual console results in the rendering of a > series of short, vertical (mostly red & green) lines at the top of the > screen. machine is still active, and I can SSH in > > Greg, can you try doing this, and see if it happens on your machine as well? > It doesn't happen to me if I don't load the DRI stuff. I've tested this with > kernel 2.4.9-ac3, 2.4.14, and 2.4.16. > I don't have framebuffer support in my kernel; as someone on #dri suggested > removing it to see if it fixes another DRI lockup problem (after playing > Half-Life [under wine] or Rune [from loki] for some time, the screen will > hang). > I actually never got console framebuffer working with my G450... hung every > time, with the early 2.4 kernels I tried. > > I submitted a lengthy and detailed bug report to [EMAIL PROTECTED]; is it > appropriate to repost it here? (I'm new to this list). _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
