From owner-freebsd-current Mon Dec 4 19: 3:45 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 19:03:41 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from cae88-102-101.sc.rr.com (unknown [24.88.102.101]) by hub.freebsd.org (Postfix) with ESMTP id 739CE37B400; Mon, 4 Dec 2000 19:03:40 -0800 (PST) Received: (from dmaddox@localhost) by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eB5345Z00319; Mon, 4 Dec 2000 22:04:05 -0500 (EST) (envelope-from dmaddox) Date: Mon, 4 Dec 2000 22:04:05 -0500 From: "Donald J . Maddox" To: John Baldwin , Andrea Campi , Andrea Campi , freebsd-current@FreeBSD.ORG Subject: Re: [jhb@FreeBSD.org: RE: Panic in -current] Message-ID: <20001204220405.B248@cae88-102-101.sc.rr.com> Reply-To: dmaddox@sc.rr.com Mail-Followup-To: John Baldwin , Andrea Campi , Andrea Campi , freebsd-current@FreeBSD.ORG References: <20001205032713.B2351@webcom.it> <20001204215931.A248@cae88-102-101.sc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001204215931.A248@cae88-102-101.sc.rr.com>; from dmaddox@sc.rr.com on Mon, Dec 04, 2000 at 09:59:31PM -0500 Return-Receipt-To: dmaddox@sc.rr.com Sender: dmaddox@cae88-102-101.sc.rr.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I guess I should specify that this is a desktop with APM enabled in the BIOS, but not being used otherwise... VESA module loaded. #uname -a FreeBSD cae88-102-101.sc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Dec 2 16:07:54 EST 2000 root@cae88-102-101.sc.rr.com:/usr/src/sys/compile/RHIANNON i386 #kldstat Id Refs Address Size Name 1 9 0xc0100000 234878 kernel 2 1 0xc0335000 5540 vesa.ko 3 1 0xc033b000 9eb4 cd9660.ko 4 1 0xc0345000 eb44 msdos.ko 5 1 0xc0354000 7a98 procfs.ko 6 1 0xc035c000 158ec linux.ko 7 1 0xc0372000 b2cc if_dc.ko 8 2 0xc037e000 10004 miibus.ko 9 1 0xc038f000 76e0 linprocfs.ko On Mon, Dec 04, 2000 at 09:59:31PM -0500, Donald J . Maddox wrote: > Just as a data point, I just tried this as well... The daemon saver was ok, > the fire saver was ok, but as soon as I loaded logo_saver and it activated, > I got a 'dc0 timeout'(?) and I was unable to access any of the vtys after > that... I could switch vtys, but could not type anything. > > The fire_saver module is obviously using a VESA mode, but I had no problem > problem with it... > > On Mon, Dec 04, 2000 at 06:41:55PM -0800, John Baldwin wrote: > > > > On 05-Dec-00 Andrea Campi wrote: > > >> > More details: this is an IBM Thinkpad laptop with APM enabled and in the > > >> > kernel. > > >> > As usual, any hint is more than welcome. This used to work... > > >> > > >> Which screen saver? Does it do it with all of them? Just graphical ones, > > >> just > > >> text ones, just green_saver, etc.? > > > > > > Rrrright... I can assure you I would never have thought this could make a > > > difference... > > > > That's ok, it didn't occur to me either at first. However, the green_saver > > calls into APM, and the graphical ones will call into VESA, so it might make a > > difference. > > > > > Ok, I will try each one. At the moment, I'm using logo_saver. > > > I will let you know. > > > > > > Bye, > > > Andrea > > > > > > -- > > > Weird enough for government work. > > > > -- > > > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message