Bug 22577

Summary: 486SLC2-50MHz won't boot 3.x or 4.x floppies, but does boot 2.2.7
Product: Base System Reporter: opentrax <opentrax>
Component: miscAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description opentrax 2000-11-03 16:50:01 UTC
A korean made Laptop does a register dump instead of booting.
Running:
486SLC2-50MHz 
CHIPS SCATsx/PEAKsx BIOS Version 128

MFG: NAE WAE Semiconductor Co., LTD.
Model: INEX 4150
system has 8 megs of RAM
-------------------------------
I can type the register dump in to the PR, if it will help.
The system does report:
int=0000000d    err=00000000 ....

Fix: 

System does boot from a 2.2.7 diskette.
This seems to suggest something from 3.0 on is causing the problem.
This could caused by a CPU test or some other boot related test/probe.
If someone is willing to work on it, the laptop could be made
available for testing. Currently, it is scheduled to become
the SVBUG "club computer" for club meetings.
How-To-Repeat: Boot with an installation floppies of any of the following version:
3.0, 3.1, 3.2, 3.4, 3.5, 4.0, 4.1

The register dump does vary slightly from version to version.
Comment 1 Sheldon Hearn 2000-11-09 18:30:47 UTC
On Fri, 03 Nov 2000 08:45:54 PST, opentrax@email.com wrote:

> System does boot from a 2.2.7 diskette.
> This seems to suggest something from 3.0 on is causing the problem.

Or that you're not using the correct combination of floppy images.
Which two floppy images did you download and write to disk, and are you
sure they were downloaded with FTP binary mode? :-)

Ciao,
Sheldon.
Comment 2 opentrax 2000-11-10 02:21:21 UTC
On  9 Nov, Sheldon Hearn wrote:
> 
> 
> On Fri, 03 Nov 2000 08:45:54 PST, opentrax@email.com wrote:
> 
>> System does boot from a 2.2.7 diskette.
>> This seems to suggest something from 3.0 on is causing the problem.
> 
> Or that you're not using the correct combination of floppy images.
> Which two floppy images did you download and write to disk, and are you
> sure they were downloaded with FTP binary mode? :-)
> 
I have all the binary images listed in the PR. ALL images work
correctly. I use them all the time to build machines. (I have 20+ 
machines.) All diskettes are labeled and all diskettes were
post-tested on other machines, to verify working diskettes. 

I might have a doubt about one pair of disketes, maybe two (2)
but not six (6) pairs. All on different brand diskettes.
All download at different times. And all verified to be
working after the fact. 

I'd be more than happy to reproduce the test, with
diskettes and the machine, at any of the local BSD User
Group club meetings. If requested, I could have the
entire set available to the team in Walnut Creek.

				best regards,
				Jessem.
Comment 3 opentrax 2000-12-07 10:22:00 UTC
Could you please fill out a PR (Problem Report) at:

http://www.freebsd.org/send-pr.html

I said that I MIGHT work on this, if I get time.
I suspect the problem is in the CPU probe code.
As such I need to build a new set of boot diskettes
to test this. I'm not sure when I'll get time, but
if you fill out a PR there will at least be some
information to check on.

On  6 Dec, alcino@tci.ufal.br wrote:
> 
> I'm having a similar problem with a 486Dx2/66 IBM 
> ValuePoint. I don't test yet with the 2.2.7 diskettes, 
> just with 4.1 and 4.2. The the boot reads the diskettes 
> and start a flashing problably registers show 
> (illegible but I could gues this). I'm a newbie with 
> FreeBSD, but a bit experiencied with computers so jokes 
> like to ask if I'm using the right pair of diskettes 
> are useless.
> 
> Question: I can install FreeBSD after booting with 
> older diskettes?
> 
> PS.: a friend report to me that he have the same 
> problem with a 486, but all work well in a K6, and a hd 
> transplantation back to the 486 works well.
> 
>
Comment 4 unfurl freebsd_committer freebsd_triage 2001-05-31 05:10:07 UTC
State Changed
From-To: open->closed

This problem seems to be isolated to this one machine since no one else 
has made any similar comments. Also, it's almost impossible to duplicate 
since it seems to be this particular piece of hardware.