From owner-freebsd-hackers Thu Jun 8 20:30:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 58EDC37BC72 for ; Thu, 8 Jun 2000 20:30:43 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:AJ+PgEiokm15bA0Qn4LQ3PIj6Rb7GlMX@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id MAA16733; Fri, 9 Jun 2000 12:30:40 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:2lhpsUZeVIlaqkGG6KxCEAnByCKCV44X@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id MAA01398; Fri, 9 Jun 2000 12:37:28 +0900 (JST) Message-Id: <200006090337.MAA01398@zodiac.mech.utsunomiya-u.ac.jp> To: Graham Wheeler Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: 4.0-Stable/XFree86-4.0/syscons switching crash In-reply-to: Your message of "Thu, 08 Jun 2000 12:21:08 +0200." <93676b3af19b0fcbd3f667ba55a116cc@cequrux.com> References: <93676b3af19b0fcbd3f667ba55a116cc@cequrux.com> Date: Fri, 09 Jun 2000 12:37:27 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I am running 4.0-S on a Compaq Presario laptop with a Trident Cyberblade >VGA. I couldn't get this to work in anything other than 640x480 with >XFree86-3.3.6, so I moved to XFree86-4.0 (and no, I'm not interested in >mail from people who say that the Trident Cyberblade works for them in >3.3.6; believe me, mine doesn't - I spent a week jumping through hoops >with it before I gave up. If you were lucky enough to have xf86config or >XF86Setup work for you with this chipset, I'm happy for you - but I had >to hand-customise the XF86Config file extensively even to get 640x480 to >work). > >Anyway, XFree86 4.0 works for me, except for a couple of glitches. The >first one, which occurs sufficiently infrequently that I can live with >it, is that sometimes when I kill X and return to text mode my Enter key >gets remapped to Scroll Lock. Irritating in the extreme, but it doesn't >happen consistently, just occasionally. The cause of this is most likely that the X server failed to restore the keyboard mode (K_RAW to K_XLATE) when it's got killed. Try using the kbd_mode program that comes with XFree86. Run vidcontrol -s N-1 < /dev/ttyv0; kbd_mode -a < /dev/ttyvN (where N is the vty from which you started X) as root. For example, if you run `startx' in /dev/ttyv3, you should type: vidcontrol -s 4 < /dev/ttyv0; kbd_mode -a < /dev/ttyv3 >Much more distressing: if I switch out of X to a text mode console with >Ctrl-Alt-Fn, and then switch back to X, the machine freezes up >completely and has to be power-cycled. Does the machine respond to ping from another machine on the network? >It does first switch back into >graphics mode, and I can see the top part of the screen is messed up, so >it hasn't restored the low memory. Um, this sounds more like a bug in the X server. syscons does nothing to set up the graphics mode for the X server. It is entirely up to the X server to properly initialize the video chip set. The only thing syscons does when you switching back X is to tell the X server that the X server may now have the full access to the video card... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message