From owner-freebsd-questions Thu Dec 28 08:07:46 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA12189 for questions-outgoing; Thu, 28 Dec 1995 08:07:46 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA12181 for ; Thu, 28 Dec 1995 08:07:40 -0800 (PST) Received: by Sysiphos id AA02954 (5.67b/IDA-1.5 for questions@freebsd.org); Thu, 28 Dec 1995 17:06:34 +0100 Message-Id: <199512281606.AA02954@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 28 Dec 1995 17:06:33 +0100 In-Reply-To: Alex Kluev "Re: Adaptec 294x problem" (Dec 28, 18:06) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Alex Kluev Subject: Re: Adaptec 294x problem Cc: questions@freebsd.org Sender: owner-questions@freebsd.org Precedence: bulk On Dec 28, 18:06, Alex Kluev wrote: } Subject: Re: Adaptec 294x problem } Hi! } } I'm afraid we found the problem, and it wasn't the Adaptec's fault. } Compaq's PCI controller is residing on the same addresses as the "normal" } one, but differs in the identification code. Here's what we changed in } /sys/i386/isa/pcibus.c : Well, I seem to remember having asked for verbose boot messages. It's wonderful, that you found a way to make the PCI probe work on your system, but there would have been a much simpler way to achieve this, and that would have been to not do the probe, but directly return the specific results for your system ... Compaq PCI chip sets have been broken in similar ways for a long time, and I received a reply from Compaq, that this is taken care of in their PCI BIOS. That's fine, but we don't rely on any PCI BIOS, since there are more broken PCI BIOS versions than broken PCI chip sets. } Of course we had to add "options COMPAQ" to the config file. We wonder if } there could be another way to fix this problem. Could anybody work out a } patch or something, because none of us had any experience with PCI until a } few days ago when the problem arised, and we don't have any documentation. Yes. And this anybody might be me. But if you don't send the information I ask for, there is nothing I can do ... } Another question is : how to make an installation floppy with a modified } kernel? Building the "official" boot floppies is a complex and time consuming process. but it is in fact possible to create a BSD FFS on a floppy, copy /kernel and a few other required files over, and boot from this floppy. Don't ask for details, I didn't try it recently ... Regards, STefan } On Wed, 27 Dec 1995, Stefan Esser wrote: } > Please send VERBOSE boot messages (obtained } > by '-v' entered at the 'Boot: ' prompt), at } > least of the PCI probe: } > } > pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x00000000 } > pcibus_setup(1a): mode1res=0x00000000 (0x80000000) } > pcibus_setup(1b): mode1res=0x00000000 (0xff000001) } > pcibus_setup(2): mode 2 enable port (0x0cf8) is 0x00 } > pcibus_setup(2a): mode2res=0x0e (0x0e) } > pcibus_setup(2a): now trying mechanism 2 } > pcibus_check: device 0 is there (id=04838086) -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se