Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Aug 1999 12:08:02 -0000
From:      Lofthouse Andrew 2Lt WRALC/TIECT <Andrew.Lofthouse@robins.af.mil>
To:        Doug <Doug@gorean.org>, Frank Mayhar <frank@tinker.exit.com>, stable@FreeBSD.ORG
Cc:        John Polstra <jdp@polstra.com>
Subject:   RE: Problem reporting build failure (rebuilding bootstrap, crtbeg in.c:33)
Message-ID:  <3F69A3D5863ED211B31F0000F809353502D1E0FF@FSUHHZ33>

next in thread | raw e-mail | index | archive | help

	On Fri, 13 Aug 1999, Frank Mayhar wrote:

	> "Make upgrade" doesn't exist in 3.0-release.  There's just world,
aout-to-elf,
	> aout-to-elf-build, aout-to-elf-install and move-aout-libs.

		I think I sent you this already, but if I didn't take a look
at
	http://home.san.rr.com/freebsd/make-upgrade.html.



Just for the record, the procedures listed on the above website work.  I
followed them this weekend and successfully updated my 2.2.8-RELEASE to
3.2-STABLE. It takes a bit of time (three make world builds, basically), but
it works.

HOWEVER, I'm still asking for some help. It seems that even with the upgrade
to 3.2-STABLE, I'm still running into the same problem I had when I tried
installing the 3.2-RELEASE (I thought the problem would be fixed in
-STABLE). The problem is that the hardware probe does not detect my primary
IDE controller, wdc0 (most of the time). I did find a workaround, which
entails going into my BIOS setup, setting the "auto-detect" option on the
harddrive settings and saving the new settings. Note that this works only
one time. Each time I reboot, I have to go back into my BIOS setup and save
the settings (even without changing anything). This is a little annoying to
do each time I boot up. Now, I realize that IDE drives may not be the first
choice for this type of OS (it seems, looking at the e-mail traffic, that
SCSI is the way to go), but that's all I've got. As I mentioned, I thought
the problem was resolved in -STABLE, but I guess not. I'll submit a bug
report. But in the meantime, I'd appreciate any ideas on why the new
bootstrap would not detect my primary IDE controller, while 2.2.8 worked
just fine.

FYI I've got a Pentium MMX cpu with Intel 430TX chipset, Award BIOS version
4.51 PGM, PnP BIOS 1.0A on an AOpen AP5TC RC1.10 motherboard. Both
harddrives are on my primary controller (1.27 GB Samsung as master, 6.54 GB
Seagate as slave) and my ATAPI CD-ROM drive is master on the secondary
controller. By the way, the probe always detects my secondary controller
(wdc1) just fine. I'd prefer not to mess with the physical configuration of
the machine (i.e. move drives to different controllers, etc). I've got 4 OSs
on the machine and I rather not mess up their drive configurations.

And I do appreciate the tips I've received so far.

Andrew J. Lofthouse


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




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