From owner-freebsd-hackers Mon Nov 13 00:01:44 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA20671 for hackers-outgoing; Mon, 13 Nov 1995 00:01:44 -0800 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA20661 for ; Mon, 13 Nov 1995 00:01:42 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id AAA04624 for ; Mon, 13 Nov 1995 00:00:37 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA00101; Mon, 13 Nov 1995 08:54:31 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA13417; Mon, 13 Nov 1995 08:54:31 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id IAA24961; Mon, 13 Nov 1995 08:41:27 +0100 From: J Wunsch Message-Id: <199511130741.IAA24961@uriah.heep.sax.de> Subject: Re: getting close - 1104-snap ed0 not working To: archive@cps.cmich.edu (Mail Archive) Date: Mon, 13 Nov 1995 08:41:26 +0100 (MET) Cc: freebsd-hackers@freebsd.org (FreeBSD hackers) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Mail Archive" at Nov 12, 95 05:44:09 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 929 Sender: owner-hackers@freebsd.org Precedence: bulk As Mail Archive wrote: > > > You sure it matches your hardware? You've booted with -c and made > > positively sure it matches what the SMC is set to? > > > Just to say this I have an Ultra in a 486/66 that works fine for > WinNT/Win95/LinSux BUT won't run fer shit in the current snapshop I have That's not sufficient. FreeBSD refuses to tweak the configuration of the card, since (that's how i understand it) there's no way to tell the difference between a soft configuration and a hard jumper setting, at least on some cards. > spent three hours of reconfigging the whole system to make sure the card > was even where freebsd wanted to find it by default.. You shouldn't have done this! Simply boot with -c and adjust _FreeBSD_'s idea, not the hardware. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)