From owner-freebsd-questions Fri Feb 21 18:22:32 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99E0437B401 for ; Fri, 21 Feb 2003 18:22:31 -0800 (PST) Received: from mail46.fg.online.no (mail46-s.fg.online.no [148.122.161.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id E485343F93 for ; Fri, 21 Feb 2003 18:22:29 -0800 (PST) (envelope-from soppscum@online.no) Received: from spam (ti400720a080-1159.bb.online.no [80.212.164.135]) by mail46.fg.online.no (8.9.3/8.9.3) with SMTP id DAA28619; Sat, 22 Feb 2003 03:22:25 +0100 (MET) Date: Sat, 22 Feb 2003 03:24:29 +0100 From: Michael To: taxman Cc: freebsd-questions@FreeBSD.ORG Subject: Re: 5.0-RELEASE kernel boot problem on acer travelmate 210TEV (laptop) Message-Id: <20030222032429.7d75cffb.soppscum@online.no> In-Reply-To: <200302211846.09122.taxman@acd.net> References: <20030221145033.2f5af08c.soppscum@online.no> <200302211846.09122.taxman@acd.net> Organization: na X-Mailer: Sylpheed version 0.8.9 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 21 Feb 2003 18:46:09 +0100 taxman wrote: > On Friday 21 February 2003 02:50 pm, Michael wrote: (snipped) > > I've been using 4.X for some time with no problems(that I can remember =) > > > > So i'm booting the install 5-RELEASE mini cd : > > Ok this is getting out of hand. 5.0 is a testing release. See: > http://www.freebsd.org/releases/5.0R/early-adopter.html > so of course it is not going to work for everything. Development is > proceeding rapidly on 5.0, so the problem you're seeing may be fixed already. > Installing -current would be the only way to know. if you tried that and got > the same error, then they would love to hear about it on the -current mailing > list so that it can be properly fixed. It's not likely it will ever be fixed > for 5.0 release, which is a static point on an again, rapidly moving, > development track. > If 4.x works well then use that, or if you want to experiment try -current, > perhaps by installing a snapshot. Thanks, didn't realise 5-RELEASE was still current, anyway how should I report something like this to current@ ? I mean is there some sort of "backtrace" I can do after it panics that would be more useful than just this oneline message? :P To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message