Stephen Takacs wrote: > On Sun, Apr 08, 2007 at 12:11:37PM -0400, Nick Holland wrote: >> What you are describing is almost certainly the i386-on-amd64 problem. >> >> Solution is to do one of the following (in my order of preference, your >> criteria may be different than mine, of course!) : >> * run OpenBSD/amd64 (where this problem doesn't exist) >> * wait for 4.1 (where it is fixed) >> * run -current (where it is fixed) > > Unfortunately, my cpu is one of the "lame" Sempron chips which isn't a > true AMD64. It can be pretty hard to tell them apart, given all the > revisions: http://en.wikipedia.org/wiki/Sempron > > I'll definitely give 4.1 a shot and see though... >
In that case, could you provide a full dmesg on the thing? This sounds interesting, I'd really love to know what -current does on it, though I guess we can wait a few weeks for 4.1-release. :) (not like I'm the guy who has the knowledge to troubleshoot what's going on here...) Did you actually try amd64 on it? Nick.
