Date: Wed, 12 Jun 1996 19:19:09 -0700 From: Scott MacFiggen <smurf@csua.berkeley.edu> To: David Kelly <dkelly@hiwaay.net> Cc: Scott MacFiggen <smurf@csua.berkeley.edu>, Matthew Stein <matt@bdd.net>, freebsd-questions@freebsd.org Subject: Re: NExGen chip Nx586-100 Message-ID: <199606130219.TAA11702@soda.CSUA.Berkeley.EDU> In-Reply-To: Your message of "Wed, 12 Jun 1996 20:22:18 CDT." <v03006f00ade51a645747@[206.104.22.180]>
next in thread | previous in thread | raw e-mail | index | archive | help
>Any chance you left kernel.GENERIC or kernel.old or such laying around from >the original release? You could boot to it from the boot manager and all >would be well again. Else boot the boot floppy, and maybe the root floppy, >then take the fixit floppy option, and you might be able to move one of >those kernels to your hd root to get the system running again. I wish I could remember, I set up my system when 2.1 was released and haven't touched a thing since. >I looked at the Linux patch for NexGen and didn't find any similar code in >the FreeBSD kernel. To optimize an Nx586 to 100% of its potential for >FreeBSD one would need proper documentation from NexGen as to exactly what >they offer. I think I'll head over to the freebsd-hackers list and see if there is any interest. I am currently on contract at Nexgen as a sysadmin so I might be able to get some support from within. >The Linux NexGen patch can be found at http://www.cantrip.org/ncm.html I glanced at the patch and it doesn't seem to complicated, but then again I am not a kernel hacker by any measure. Thanks for the help, I'll go see what the freebsd hackers have to say. >David Kelly N4HHE, n4hhe@amsat.org, dkelly@hiwaay.net -Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606130219.TAA11702>