From owner-freebsd-mobile Thu Apr 12 12:48:50 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from subtil.dhis.dee.uc.pt (195-23-145-230.nr.ip.pt [195.23.145.230]) by hub.freebsd.org (Postfix) with ESMTP id 80D5D37B422 for ; Thu, 12 Apr 2001 12:48:45 -0700 (PDT) (envelope-from nsubtil@subtil.dhis.dee.uc.pt) Received: (from nsubtil@localhost) by subtil.dhis.dee.uc.pt (8.11.1/8.11.1) id f3CJlpi20971; Thu, 12 Apr 2001 20:47:52 +0100 (WEST) (envelope-from nsubtil) Date: Thu, 12 Apr 2001 20:47:51 +0100 From: Nuno Subtil To: "Richard C." Cc: freebsd-mobile@freebsd.org, mike@argos.org Subject: Re: TOSHIBA, FreeBSD + X Locks up.... :( Message-ID: <20010412204751.A20947@subtil.dhis.dee.uc.pt> References: <004201c0c243$82153840$0100a8c0@bsdaemon.org> <20010411012052.A16561@argos.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010411012052.A16561@argos.org>; from mike@argos.org on Wed, Apr 11, 2001 at 01:20:52AM -0400 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Apr 11, 2001 at 01:20:52AM -0400, Mike Nowlin wrote: > 1) APM + X (on the Savage IX chipset that's in there) is a no-no. APM seems > to work OK when in text mode (I can suspend & resume - everything works OK > except the PCMCIA cards on resume - not sure if that's been fixed since I > last did an update.) Due to some glitches in the Savage handling, APM > events tend to blow up X. I have a 4290 running -CURRENT and X 4.0.3, and APM does work under X. I can suspend/resume with no problems without switching to the console. > > 2) Switching back and forth between X and text mode also causes X to blow > up quite frequently. What is interesting is that telling Gnome to exit > (graceful shutdown of X) almost always blows it up, while doing a > ctrl-alt-bksp to violently kill X usually returns the display to normal. > Haven't look at why this happens, but it does... > I also experience this, but only when I run the console in VESA_800x600 mode. And I get sporadic lockups when switching the console to VESA_800x600. If I run it in plain text mode, X seems to work fine (didn't crash in two hours of use, with plenty of switching to the console and back --- but after that, switching the console to VESA_800x600 instantly wedged the machine...). > 3) (The big one) Is it really locked up, or (like mine when it blows up) > is it just stuck with no keyboard or display? I hooked a serial terminal > up to the back of it and started a login session over that - when X blew up, > the serial terminal was still running fine - could do a proper shutdown and > power-off. (Shutdown & reboot still leaves the display unusable, but the > system does boot up and start running - you just can't see anything.) In my case, it seems to lock up hard. I haven't tried logging in over the network or attaching a serial terminal to it, however if I happen to be playing MP3 when it crashes, the sound stops as well, so my guess is my machine just freezes. Nuno Subtil nsubtil@subtil.dhis.dee.uc.pt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message