Date: Sat, 22 Mar 2003 02:26:24 +0300 From: "Sergey A. Osokin" <osa@freebsd.org.ru> To: "Brian J. Kirk" <kirk@primuul.com> Cc: freebsd-current@freebsd.org Subject: Re: freebsd 5.0 on hp netserver lf Message-ID: <20030321232624.GW49925@freebsd.org.ru> In-Reply-To: <20030321231501.GA38455@primuul.com> References: <20030321224539.GC38273@primuul.com> <000501c2effd$ab6ac220$1200a8c0@gsicomp.on.ca> <20030321231501.GA38455@primuul.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 21, 2003 at 06:15:01PM -0500, Brian J. Kirk wrote: > 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. Try disable ACPI with unset acpi_load at boot prompt. Maybe its help you. > On Fri, Mar 21, 2003 at 06:00:29PM -0500, Matthew Emmerton wrote: > > > > > 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. > > > > > > > Try using hw.eisa_slots = 12. -- Rgdz, /"\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ / AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030321232624.GW49925>