Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 Jan 1997 23:28:59 +0100
From:      j@uriah.heep.sax.de (J Wunsch)
To:        belkovic@albert.osu.cz (Josef Belkovics)
Cc:        freebsd-bugs@freebsd.org
Subject:   Re: AIC-7770 (TwinChannel fast SCSI-2 controller (in HP NetServer LC))
Message-ID:  <Mutt.19970108232859.j@uriah.heep.sax.de>
In-Reply-To: <Pine.BSF.3.91.970108220358.290A-100000@albert.osu.cz>; from Josef Belkovics on Jan 8, 1997 22:40:38 %2B0100
References:  <Pine.BSF.3.91.970108220358.290A-100000@albert.osu.cz>

next in thread | previous in thread | raw e-mail | index | archive | help
As Josef Belkovics wrote:

> In 2.1.0R controller ahc1 was in GENERIC kernel and all was ok. In 2.1.5R or
> 2.1.6R ahc1 isn't in GENERIC. I installed 2.1.6R from 2.1.0R boot.flp and 
> copied kernel 2.1.0R from another PC. The build of 2.1.6R kernel is ok, 
> but ahc1 (or ahc0 - I don't know the difference between it) isn't detected.
> 2 questions:

> 1) Exists some release higher 2.1.0 with correct "driver" for ahc1?

Yes, any release.

> 2) Can you put back ahc? in boot.flp?

It's there.  Always.  The bug is different.  Sadly enough, people
don't tend to read FAQs very often (but that's why they are called a
FAQ, they are frequently _asked_ :).  So here's the snippet from the
current FAQ.

Addendum: i noticed after writing that FAQ entry that the changes to
support the `eisa' command in UserConfig didn't make it into the
2.2-BETA.  So if you are unable to upgrade the kernel on that machine
from sources, let us know, and we'll see to put a more recent boot
floppy up for you.  The described hack will be in 2.2-RELEASE.


3.16. FreeBSD does not recognise my on-board AIC-7xxx EISA SCSI in an
HP Netserver

This is basically a known problem. The EISA on-board SCSI controller
in the HP Netserver machines occupies EISA slot number 11, so all the
``true'' EISA slots are in front of it. Alas, the address space for
EISA slots >= 10 collides with the address space assigned to PCI, and
FreeBSD's auto-configuration currently cannot handle this situation
very well.

So now, the best you can do is to pretend there were no address range
clash :), go right ahead and edit the file
/sys/i386/eisa/eisaconf.h. Look for a line defining the macro
EISA_SLOTS, and bump the number it's defining to 12. Configure and
compile a kernel, as described in the Handbook entry on configuring
the kernel.

Of course, this does present you a chicken-and-egg problem when
installing on such a machine. In order to work around this problem, a
special hack is available inside UserConfig. Do not use the ``visual''
interface, but the plain command-line interface there. Simply type

eisa 12
quit

at the prompt, and install your system as usual. Don't forget to
install the kernel source distribution, since you need to build a
custom kernel, or otherwise you would have to repeat the described
procedure at each boot! dset(8) doesn't save this change for you.

Hopefully, future version will have a proper fix for this problem.

-- 
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. ;-)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970108232859.j>