Date: Sun, 29 Mar 1998 22:54:18 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: robert w hall <bobh@n-cantrell.demon.co.uk> Cc: FreeBSD Questions <questions@FreeBSD.ORG> Subject: Re: freebsd 2.2.5 kernel on cyrix 686 M2-MMX cpu Message-ID: <Pine.BSF.3.96.980329225239.23543V-100000@gdi.uoregon.edu> In-Reply-To: <Bh5OwFA8ptF1Ew30@n-cantrell.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 23 Mar 1998, robert w hall wrote: > Doug > Thanks for reply - obscurity of my message is in part due to there being > one previous (to Walnut Creek & questions@freebsd) which obviously > hasn't got to you yet. > > I'm trying to get the new 2.2.5 kernel up on my Cyrix 686 M2-MMX box (VX > Pro motherboard, 40MB DRAM (8Mb fast page, 32Mb EDO), Miro 12PD SVGA > card, NE2000 clone card, titchy 130MB IDE drive) . This is networked to > an AMD 486 server, which has the big disk, CDROM and floppy. Both > systems run Linux Slackware (2.0.30 kernel) under NFS. The 486 has Win > 95, and a small FreeBSD 2.2.5 system, downloaded from the net. The Cyrix > has Win.3.11/Dos 6.2 and just a little spare space (40MB?). okay. 40MB is really, really tight; You have to delete libraries and /usr/include from the EHShell or else you'll run out of space. (As you might guess I did this :) ) > I now have the walnutcreek 4-disk set for 2.2.5 and so moved the > components of the install directory, namely install.bat, fbsdboot.exe > and kernel (2.88meg!) on to the cyrix hard-disk. after some fiddling > with the DOS memory manager (esp enabling EMS), the nearest I've got to > the kernel coming up is:- I don't believe that's correct.... immedately: > Fatal trap 9:general protection fault while in kernel mode > If I bring across the hard disk from the 486, and install the boot > manager (using bootinst.exe) to run the resident system I still end up > with no joy (despite the fact that this system comes up ok on the 486), > and the same (in all detail I think) error message. > > I have NOT tried bringing across the floppy drive and using a boot > floppy (or rather I have but the drive wouldn't come up properly - cable > problem?) - to do the job properly I'll have to start pulling nasty > (=long, lots of mating force needed) VLB cards out of my 486 > motherboard! and I'd rather not bother until I've got some reassurance > that > a) the system comes up cleanly on this cpu/motherboard (686/VX Pro) > combination and that > b) there isn't a work-around. Please try this. fbsdboot may not be happy. If it blows up on the boot floppy then we may have a real bug. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major 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?Pine.BSF.3.96.980329225239.23543V-100000>