Date: Fri, 6 Apr 2001 12:35:20 -0700 From: Robert Clark <res03db2@gte.net> To: Mark Woodson <mwoodson@wloq.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Vectra XU 6/xxx Message-ID: <20010406123520.B19657@darkstar.gte.net> In-Reply-To: <5.0.2.1.0.20010406095353.020ae4a0@192.168.100.3>; from mwoodson@wloq.com on Fri, Apr 06, 2001 at 10:02:33AM -0400 References: <Mark <XFMail.010404200245.y3k@gti.net> <8766gjdu64.fsf@thanatos.shenton.org> <5.0.2.1.0.20010406095353.020ae4a0@192.168.100.3>
next in thread | previous in thread | raw e-mail | index | archive | help
Not to beat a dead horse, but the link I passed on fro GRUB mentioned a specific problem with the BIOS not finding a bootable partition. (or something like that) It is possible, that the BIOS is just very picky about what it will boot from. In other words, it may not be the boot code that is bad. [RC] On Fri, Apr 06, 2001 at 10:02:33AM -0400, Mark Woodson wrote: > At 03:26 PM 4/5/2001 -0400, Chris Shenton wrote: > >Mark Yeck <y3k@gti.net> writes: > > > > > I used to have a link to an article on dejanews that mentioned boot > > problems > > > with freebsd and vectra's. unfortunately, that link doesnt work anymore > > and i > > > dont remember what the fix was. It had something to do with the bios not > > > working with the bootloader. Wish I could help more. I know others have > > had a > > > similar problem and the answer is out there somewhere. > > > >Mark pointed me to the link a while back. Here's my response to him > >and how I worked around it without resorting to image hacking. > > > Mark> Here's a clue I found on dejanews. Hopefully it will help. > > Mark> > > http://x69.deja.com/getdoc.xp?AN=700810190&CONTEXT=976477108.518324252&hitnum=2 > > As a note for anyone else who has this problem this link doesn't work. > > > Thanks! Seems a big hairy (grabbing boot0 images from FreeBSD-3.x, etc). > > > > As a last attempt before doing the above, I tried telling sysinstall > > to NOT use the normal FreeBSD boot manager, but to install the > > "Standard" boot manager, as it says "no boot manager". [Standard=none > > is a bit confusing, when the next choice is "don't touch the existing > > boot manager on disk"]. > > On a more personal note, I found (for whatever reason) the 3.4 install (CD > I managed to find in the "stack") wouldn't work until I created a small DOS > partition (not sure if this is a geometry problem as mentioned in the > Handbook & Complete) after which it worked. Installing 4.1 on top of that > not letting it touch the MBR (None, not standard) worked for me. It's been > a frustrating install, but glad it's done with. > > Thanks to everyone on the list who gave me pointers and comments. > > -Mark > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010406123520.B19657>