Date: Tue, 06 Jul 2004 19:37:40 -0600 From: Brad Waite <freebsd@wcubed.net> To: Doug White <dwhite@gumbysoft.com> Cc: freebsd-stable@freebsd.org Subject: Re: 4.10-STABLE boot issues Message-ID: <40EB53E4.6030103@wcubed.net> In-Reply-To: <20040706160346.O24627@carver.gumbysoft.com> References: <2398.24.9.172.8.1087316143.squirrel@webmail.wcubed.net> <20040616144028.W16072@carver.gumbysoft.com> <2045.24.9.172.8.1087445008.squirrel@webmail.wcubed.net> <20040619113634.T48022@carver.gumbysoft.com> <40EA1066.8030709@wcubed.net> <20040706160346.O24627@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug White wrote: > On Mon, 5 Jul 2004, Brad Waite wrote: > > >>>It obviously works for the rest of the world, and it doesn't look like a >>>BIOS access problem since it can read the file fine if its on /. >> >>Well /boot is *not* on /dev/da0s1a. It's on /dev/amrd0s1a, but boot2 >>doesn't know how to get at the amr device. At least not as far as I've >>tested. I'm leery of messing around in >>/usr/src/sys/boot/i386/boot2/boot2.c, but if someone wants to give me >>some pointers, I'll try it. > > > This is new information ... the BIOS Int13 calls for the AMR may be doing > something evil. Is there updated firmware for that device available? I'm running the latest firmware available. The NetRAID's a pretty common card, and I haven't heard of anyone having similar problems under FreeBSD. Does boot2 treat /dev/da and /dev/ad different, or are they both accessed through INT13?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40EB53E4.6030103>