From owner-freebsd-current Fri Mar 21 15:18:55 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02AE137B401 for ; Fri, 21 Mar 2003 15:18:53 -0800 (PST) Received: from kirk.sas.upenn.edu (kirk.sas.upenn.edu [130.91.24.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F2A043FAF for ; Fri, 21 Mar 2003 15:18:52 -0800 (PST) (envelope-from kirk@kirk.sas.upenn.edu) Received: from kirk.sas.upenn.edu (localhost [127.0.0.1]) by kirk.sas.upenn.edu (8.12.6/8.12.6) with ESMTP id h2LNF1dY038496 for ; Fri, 21 Mar 2003 18:15:01 -0500 (EST) (envelope-from kirk@kirk.sas.upenn.edu) Received: (from kirk@localhost) by kirk.sas.upenn.edu (8.12.6/8.12.6/Submit) id h2LNF15Z038495 for freebsd-current@freebsd.org; Fri, 21 Mar 2003 18:15:01 -0500 (EST) Date: Fri, 21 Mar 2003 18:15:01 -0500 From: "Brian J. Kirk" To: freebsd-current@freebsd.org Subject: Re: freebsd 5.0 on hp netserver lf Message-ID: <20030321231501.GA38455@primuul.com> References: <20030321224539.GC38273@primuul.com> <000501c2effd$ab6ac220$1200a8c0@gsicomp.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000501c2effd$ab6ac220$1200a8c0@gsicomp.on.ca> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG set hw.eisa_slots=12 works, it recognizes the controller and drives, then panics. I think I'll settle for 4.7 on here fow now. thanks for your help, Brian On Fri, Mar 21, 2003 at 06:00:29PM -0500, Matthew Emmerton wrote: > > ----- Original Message ----- > From: "Brian J. Kirk" > To: > Sent: Friday, March 21, 2003 5:45 PM > Subject: freebsd 5.0 on hp netserver lf > > > > Folks, > > > > I posted a question earlier on freebsd-questions concerning this, and have > since discovered a bit more. Sorry about the cross posting. > > > > I'm trying to get 5.0 running on an old hp netserver lf. quoting some > random website: > > "How come FreeBSD does not detect my HP Netserver's SCSI controller? 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 is no address range clash > :), by bumping the kernel option EISA_SLOTS to a value of 12... > > > > Of course, this does present you with 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. While it is recommended > you compile and install a custom kernel anyway." > > > > The above quoted instructions worked fine when booting with 4.7 floppies, > but 5.0 seems to lack the option to boot into UserConfig with a "boot -c" > command. Looking at the device.hints options, which seem to be replacing > the UserConfig command, I don't see anything listed for eisa slots. With > 5.0's boot loader, I've used > > set EISA_SLOTS=12 > > set EISA=12 > > but the dmesg and installer still don't list the scsi controller, and > hence no drives. > > > > Interestingly, an "lsdev" at the boot prompt correctly lists the floppy > and two drives, including the partition information. > > > > Any suggestions would be greatly appreciated. > > thanks, > > Brian > > > > -- > > Brian Kirk > > primuul.com > > Try using hw.eisa_slots = 12. > > -- > Matt Emmerton > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Brian Kirk primuul.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message