Subject: Re: Kernel hangs during npx0 initialization.
To: =?EUC-KR?B?DQq52r/rwdg=?= <nytereider@teramail.com>
From: Brian Buhrow <buhrow@lothlorien.nfbcal.org>
List: port-i386
Date: 01/10/2005 08:46:07
	Hello.  You don't say which version of NetBSD, but I assume you're
using NetBSD-2.0 or later?  If so, perhaps you need to uncomment the line
which says:

npx*		at acpi?		# Math coprocessor

Then, if that doesn't work, try again and comment out the line which says:
npx0	at isa? port 0xf0 irq 13	# x86 math coprocessor

	I suspect your new board doesn't properly support the legacy
co-processor configuration, and only presents a co-processor via the ACPI
tables.  Or, worse, it claims to support the legacy mechanism, but doesn't
work, which is why I suggest you comment out the legacy support in the
configuration file as a second try if the first custom kernel doesn't work.
Good luck.

-Brian
On Jan 10,  5:40pm, =?EUC-KR?B?DQq52r/rwdg=?= wrote:
} Subject: Kernel hangs during npx0 initialization.
} I upgraded my machine's CPU from old AMD Athlon 1.0GHz (Thunderbird core)
} to Duron 1.8GHz. (Applebred core) And now *BSD
} (NetBSD/FreeBSD/OpenBSD/DragonflyBSD...) refuses to boot!
} 
} As long as I can see from the kernel's message, the problem is npx0. The
} kernel freezes anytime it tries to initialize/detect npx0 in my machine.
} OF COURSE, THE CPU HAS FPU.
} 
} I tried to solve problem by configuring kernel differently, but as long as
} I enable npx, the kernel refuses to boot.
} 
} So much frustrated, I tried Windoze XP and ran some cpu test apps there,
} but there seems to be no problem.
} 
} Then, I tried Linux. With early versions of linux kernel (I think
} something like 2.4.10 or so), the same problem occurs: the kernel fails to
} detect FPU correctly and freezes. However, when I tried again using newer
} 2.6.x (any version) linux kernels, no problem at all!!!
} 
} I think the reason for this is the NPX initialization code...As long as I
} can see, all flavors of *BSD faces same problem. Linux once had same
} problem, but it seems they fixed it. (2.4.x couldn't boot, but 2.6.x can)
} 
} So, does anyone had similar experiences? Flawed FPU detection/initialization?
>-- End of excerpt from =?EUC-KR?B?DQq52r/rwdg=?=