From owner-freebsd-hardware Wed Apr 3 17:49:32 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA13102 for hardware-outgoing; Wed, 3 Apr 1996 17:49:32 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA13097 for ; Wed, 3 Apr 1996 17:49:29 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id SAA15500; Wed, 3 Apr 1996 18:49:10 -0700 Date: Wed, 3 Apr 1996 18:49:10 -0700 From: Nate Williams Message-Id: <199604040149.SAA15500@rocky.sri.MT.net> To: Michael Smith Cc: nate@sri.MT.net (Nate Williams), freebsd-hardware@freebsd.org Subject: Re: It isn't easy being "green"... In-Reply-To: <199604040205.LAA23103@genesis.atrad.adelaide.edu.au> References: <199604032123.OAA15011@rocky.sri.MT.net> <199604040205.LAA23103@genesis.atrad.adelaide.edu.au> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > APM suspend/resume works on some machines in both -stable and -current. > > However, folks are having a difficult time getting updated to -stable > > and -current because of instabilities and other problems, so it's > > difficult to know which machines work and which don't. > > I find the comment about upgrading totally bizarre. I've bootstrapped > machines to both -stable and -current over the last couple of weeks, > and never had anything that couldn't directly be tracked to a bad sup. But you have some expertise that others don't have. Also, they are experiencing instabilities of 2.1R, and 2.1R + PCCARD patches that are affecting the upgrade to -stable. I suspect some of the instabilities are due to the PC-CARD patches, but unfortunately they are unable/unwilling to give up that functionality in order to test out the APM code -stable/-current. Nate