Bug 36536

Summary: Apparent mother board incompatability
Product: Base System Reporter: Almon C. Turner <n4okg>
Component: miscAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Almon C. Turner 2002-03-30 16:20:00 UTC
   I have two machines, one with an ASUS P3B-F motherboard with the Intel 440BX AGP chipset with Pentium III 500Mhz processor, and the other the ASUS A7M266 Socket A motherboard with the AMD 761 Chipset and AMD Athlon 1.4 processor. Since installing both FreeBSD 4.2-Release and FreeBSD 4.4-Relaese on the newer system I have had numerous weird problems, most of which were reported as bugs.  It seems now that they are more likely motherboard problems, since they disappear when I install on the older system.  The problems that disappear are as follows:
1.  Install must be done with "PNP OS = YES" to avoid system lock-up    when device probe is invoked.
2.  Kernel recognizing the FreeBSD install disk (after system has booted from that disk and the install has progressed to the point of selecting packages) as a music disk on one CDROM drive, a Creative 52X, but not on another CDROM drive, also a Creative 52X.
3.  Problems starting X Server - DCOP_Server failed self-test. Repeated tries could get the server going with KDE.  I re-installed with Gnome and the problem wasn't there.

Fix: 

Install either release on the machine with the P3B-F motherboard and Pentium II 500Mhz processor.
How-To-Repeat:    Install either FreeBSD 4.2-Release or FreeBSD 4.4-Release on the Machine with the A7M266 motherboard, AMD Athlon 1.4 processor and 266 DDR RAM.
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2003-07-13 02:55:12 UTC
State Changed
From-To: open->feedback

Does this problem persist in newer versions?
Comment 2 Almon C. Turner 2003-07-13 15:23:31 UTC
I discovered that, when I removed the internal modem and replaced it 
with an external version of essentially the same modem, the problem 
disappeared.  For some reason the presense of the PNP (NOT Winmodem) 
modem caused the glitch.  Once the PCI modem was removed all went well.

Al Turner
n4okg@mobis.com


---
[This E-mail scanned for viruses by Mobile Internet Services]
Comment 3 Kris Kennaway freebsd_committer freebsd_triage 2003-08-16 06:38:51 UTC
State Changed
From-To: feedback->closed

Submitter reports problem was due to a HW incompatibility.