Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.Hawaii.Edu!news.uoregon.edu!hammer.uoregon.edu!news-peer.gsl.net!news.gsl.net!howland.erols.net!newsfeed.internetmci.com!news.bctel.net!news.axionet.com!amd40.wecs.org!amd40.wecs.org!duane From: duane@amd40.wecs.org (Duane Eddingfield) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: IBM P166+ (CYRIX) an i486_MACHINE ? Date: 26 Oct 1996 05:44:51 GMT Organization: A FreeBSD box. Lines: 29 Message-ID: <54s8gj$481@amd40.wecs.org> References: <32634E20.2CD7@usoft.nl> NNTP-Posting-Host: ma199.axionet.com X-Newsreader: TIN [version 1.2 PL2] Willem Wals (walsw@usoft.nl) wrote: : Hi All, : Last week a bought a new motherboard and a IBM P166+ chip. : Reinstalled my FreeBSD 2.1.5-Release on it and started building my own : kernel. Under the impression I had a Pentium-clone-chip I choose : I586_MACHINE and removed I386_MACHINE, I486_MACHINE entries from my : kernel configuration file. After reboot I got a kernel-panic stating I : was unable to start due to unrecognized cpu. Rebooted from old kernel : (GENERIC) and changed I586 to I486, recompile, reboot and had a flying : system (real fast compared to my old 66Mhz pentium). : Now for the question: Is it normal to detect IBM P166+ as an I486? I had exactly the same experience with an AMD 5x586 chip. Had to set it back to i486 and it worked fine. Also, in the CONFIG file I put 'controller pci0' and then the kernel recoginized the motherboard EIDE controller but then said '[no driver assigned]'. But if I say 'controller wdc0 at pci?' I get unresolved references at kernel link time. Do I have the wrong syntax or is 2.1.5R not quite ready for this sort of thing? Thanks to anyone with an explanation. Duane E...