Date: Thu, 27 Feb 2003 13:34:13 +0200 From: Ruslan Ermilov <ru@freebsd.org> To: Geoffrey <geoffrey@reptiles.org> Cc: Juli Mallett <jmallett@freebsd.org>, Poul-Henning Kamp <phk@critter.freebsd.dk>, current@freebsd.org Subject: Re: Any ideas why we can't even boot a i386 ? Message-ID: <20030227113413.GD39346@sunbay.com> In-Reply-To: <20030227112755.GC39346@sunbay.com> References: <20030227042706.A67762@FreeBSD.org> <20030227052926.G28626-100000@iguana.reptiles.org> <20030227112755.GC39346@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--vni90+aGYgRvsTuO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 27, 2003 at 01:27:55PM +0200, Ruslan Ermilov wrote: > On Thu, Feb 27, 2003 at 05:35:13AM -0500, Geoffrey wrote: > > On Thu, 27 Feb 2003, Juli Mallett wrote: > >=20 > > > * De: Poul-Henning Kamp <phk@critter.freebsd.dk> [ Data: 2003-02-27 ] > > > [ Subjecte: Any ideas why we can't even boot a i386 ? ] > > > > Yup. 386dx - 33Mhz. Results below: > > > > > > > > Loaded kern.flp, mfsroot.flp, prompted for boot, then core dumped > > > > as follows: > > > > > > Was this normal release? I thought I recalled a convo resulting in > > > the decision that 386 would require special release bits? > >=20 > > Yes, it was from release floppies written a couple of weeks ago. > > In fairness, it might not like my scsi host adapter (Adaptec 1542CF). = Or > > there may be an issue with the size of the drive (HP C2490 - 2 GB). The > > bios only supports one controller so fitting enough IDE drives for src, > > obj, usr and swap wasn't an option. > >=20 > : RCS file: /home/ncvs/src/sys/i386/conf/GENERIC,v > : Working file: GENERIC > : head: 1.376 > : branch: > : locks: strict > : access list: > : keyword substitution: kv > : total revisions: 508; selected revisions: 1 > : description: > : ---------------------------- > : revision 1.296 > : date: 2001/01/14 10:11:10; author: jhb; state: Exp; lines: +2 -2 > : Remove I386_CPU from GENERIC. Support for the 386 seriously pessimizes > : performance on other x86 processors. Custom kernels can still be built > : that will run on the 386. > : =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >=20 Also in src/UPDATING: : 20010116: : The kernel option I386_CPU is now mutually exclusive with the : other cpu types. If you have an i386 system, be sure that it : only had this line. Remove it for all other configurations. Also in FreeBSD/i386 5.0-RELEASE Release Notes: : 2.1.1 Processor/Motherboard Support :=20 [...] : Support for the 80386 processor has been removed from the GENERIC : kernel, as this code seriously pessimizes performance on other : IA32 processors. The I386_CPU kernel option to support the 80386 : processor is now mutually exclusive with support for other IA32 : processors; this should slightly improve performance on the 80386 : due to the elimination of runtime processor type checks. Custom : kernels that will run on the 80386 can still be built by changing : the CPU options in the kernel configuration file to only include : I386_CPU. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --vni90+aGYgRvsTuO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD4DBQE+Xfe0Ukv4P6juNwoRAumIAJi30xo36K+N8QF3yy5ESIct7K4OAJ4mN0PK HiE1y3f6PUH9I8z11/uXcQ== =IzAD -----END PGP SIGNATURE----- --vni90+aGYgRvsTuO-- 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?20030227113413.GD39346>