From owner-freebsd-current Wed Aug 22 23:25: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp010.mail.yahoo.com (smtp010.mail.yahoo.com [216.136.173.30]) by hub.freebsd.org (Postfix) with SMTP id 6932237B40B for ; Wed, 22 Aug 2001 23:25:02 -0700 (PDT) (envelope-from kc5vdj@yahoo.com) Received: from mkc-65-28-47-209.kc.rr.com (HELO yahoo.com) (65.28.47.209) by smtp.mail.vip.sc5.yahoo.com with SMTP; 23 Aug 2001 06:25:02 -0000 X-Apparently-From: Message-ID: <3B84A1BD.7040202@yahoo.com> Date: Thu, 23 Aug 2001 01:25:01 -0500 From: Jim Bryant Reply-To: kc5vdj@yahoo.com User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Kazutaka YOKOTA Cc: freebsd-current@freebsd.org Subject: Re: syscons VTY switch panic... References: <3B820F12.7050209@yahoo.com> <200108220350.MAA03898@zodiac.mech.utsunomiya-u.ac.jp> <3B83384E.1010604@yahoo.com> <200108220520.OAA04225@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This seems to solve the problem. Thank you. How soon before VESA will be stable? I do prefer a 132x60 text-mode console... Kazutaka YOKOTA wrote: > Would you please remove the vesa driver from the kernel and > do not try loading the vesa module either, and see if things work? > > >>Actually, I have tried to get the VESA splash thing going, but never can get a >>nything to display... I can try removing that... I >>believe it is still set up this way... >> >>What are the limitations on image size and color-depth for the boot splash thi >>ng? >> > > The image must have 256 colors. Its size must be 1024x768 or smaller. > If you don't have the vesa support in the kernel, the maximum size is > 320x200. > > Kazu > > >>Kazutaka YOKOTA wrote: >> >> >>>Do you by any chance use a VESA mode in text vtys? >>> >>>The vesa module in -CURRENT has problems now. If you try to >>>set the VESA_800x600 mode in syscons, you will likely to >>>hang your machine. This is a known problem, and is somewhat >>>related to vm86 and context switching. I am afraid there is >>>no immediate fix for it. >>> >>>Kazu >>> >>> >>> >>>>I am getting this with regularity now. >>>> >>>>The one time I was available to see the panic, I forgot to go into the debug >>>> >>ge >> >>>>r and do a traceback, but it had something to do with >>>>a mwrite, and had a line concerning [maybe a buffer is....?]... >>>> >>>>I know this isn't much to go on, but that's what I have. I'll get more info >>>> >>w >> >>>>hen I feel like wasting ten or fifteen minutes for a >>>>double-reboot... [is it necessary to do the `shutdown -r now` to write a ne >>>> >>w >> >>>>entropy, or can we just keep going if it boots without >>>>the proper entropy?]... >>>> >>>>I have pretty much isolated this to VTY switching via syscons. Occasionally >>>> >>, >> >>>>it will leave the system speaker in a constant tone >>>>until it reboots. This is very noticable then X exits. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message