Date: Sat, 10 Jan 1998 16:54:19 +0200 (EET) From: Sergey Shkonda <serg@bcs.zp.ua> To: "Richard M. Neswold" <rneswold@mcs.net> Cc: hackers@FreeBSD.ORG Subject: Re: K6 Problems... Message-ID: <199801101454.QAA02481@bcs3.bcs.zaporizhzhe.ua> In-Reply-To: <Pine.BSF.3.95.980109135237.20728A-100000@Jupiter.Mcs.Net>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <Pine.BSF.3.95.980109135237.20728A-100000@Jupiter.Mcs.Net> you wrote: > Hello, > I recently upgraded my system to a K6/166. I booted with /kernel.GENERIC > so that I could recompile my kernel with "i586_CPU" defined. The newly > compiled kernel only booted as far as the probe messages. No error > messages or panics occurred; the system just sat there after probing the > hardware. > I rebooted to GENERIC again and tried a debugging kernel. It stopped at > the same point in the booting process. Hitting the hot key brought me into > the debugger. Since I'm a complete novice at using the kernel debugger, > this route wasn't too enlightening. > I also tried recompiling a new GENERIC kernel (the one I was using was > from last October.) The new GENERIC kernel stopped at the same point, too. > I've tried compiling kernels with various drivers removed. I've disabled > drivers from the visual config editor. Nothing lets a 2.2.5 kernel boot > (my working GENERIC kernel is 2.2.2-ish -- maybe even 2.2.1-ish!) > Windows95 works an this hardware, as does the old GENERIC kernel. > I have a K6 (stepping 9741 (?)), 64MB of SDRAM, Intel-TX chipset. options AUTO_EOI_1 and AUTO_EOI_2 will be disabled. > Any help or suggestions would be appreciated! > Rich > ======================================================================== > Richard Neswold | rneswold@mcs.net > Home Page 'http://www.mcs.net/~rneswold/' | > PGP Key 'finger rneswold@mcs.net' | -- Sergey Shkonda (serg@bcs.zaporizhzhe.ua)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801101454.QAA02481>