Bug 861

Summary: sb16 support in 2.1 is erratic and has cosmetic defect
Product: Base System Reporter: Donald Burr <d_burr>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 2.1.0-RELEASE   
Hardware: Any   
OS: Any   

Description Donald Burr 1995-12-03 12:40:02 UTC 
	I upgraded to the 2.1.0-RELEASE kernel.  I started with my 2.0.5
	kernel config file, and merged in any differences I found with the
	new 2.1 files (none to speak of, really).  Built a new kernel,
	and rebooted.  My sbmidi0 device no longer was found.  Yes, I had
	the address set correctly, both in the kernel config file, and the
	sound_config.h file.  Didn't really irk me, since I don't use midi.
	But, "a while" later (not really sure... and a computer reboot or
	two may have taken place during this time), suddenly my kernel
	recognized the sbmidi0 device.  But it printed the kernel message
	oddly:

sbmidi0 at 0x300 on isa
 <SoundBlaster MPU-401>

	My 2.0.5 kernel, aside from *always* succesfully detecting sbmidi0,
	printed:

sbmidi0 at 0x300 on isa
sbmidi0: <SoundBlaster MPU-401>

	(note the "sbmidi0:" before the "<SoundBlaster..."

Fix: 

I dunno.  Use the system a bit, maybe reboot a couple times, and
	*boom!* it reappears, just like magic.
How-To-Repeat: 
	Build a new kernel, reboot, and watch the fun.
Comment 1 scrappy freebsd_committer freebsd_triage 1996-10-22 07:31:10 UTC 
State Changed
From-To: open->feedback


Dust off the cobwebs - Confirm Status
Comment 2 mpp freebsd_committer freebsd_triage 1997-03-09 06:57:03 UTC 
State Changed
From-To: feedback->Closed
Comment 3 mpp freebsd_committer freebsd_triage 1997-03-09 06:57:27 UTC 
State Changed
From-To: Closed->closed

I used to have the hardware in question and had no problems getting 
it configured.  All mail to the orignator bounces.