Hi,
I'm tracking -CURRENT and build a kernel yesterday with the following
options (edited):
device sbc # Soundblaster Bridge-Code to pcm
device pcm # PnP/PCI Sound Cards
#device midi # Midi interfaces
#device seq # Sequencer
The corresponding hints are: <none>
Without midi device, this is the relevant dmesg part:
[...]
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sbc0: <Creative SB AWE64> at port 0x220-0x22f,0x330-0x331,0x388-0x38b \
irq 5 drq 1,5 on isa0
pcm1: <SB16 DSP 4.16> on sbc0
unknown: <PNP0401> can't assign resources
unknown: <PNP0501> can't assign resources
unknown: <PNP0501> can't assign resources
unknown: <PNP0700> can't assign resources
unknown: <PNP0303> can't assign resources
ed0 XXX: driver didn't initialize queue mtx
lp0 XXX: driver didn't initialize queue mtx
lo0 XXX: driver didn't initialize queue mtx
ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable
[...]
and the kernel happily boots. Sound is usable as before.
Now, adding midi (either alone or together with seq) produces the
following messages:
sbc0: <Creative SB AWE64> at port 0x220-0x22f,0x330-0x331,0x388-0x38b \
irq 5 drq 1,5 on isa0
pcm1: <SB16 DSP 4.16> on sbc0
midi0: <SB Midi Interface> on sbc0
midi1: <SB OPL FM Synthesizer> on sbc0
midi2: <CTL0022 WaveTable Synthesizer> at port 0x620-0x623 on isa0
exactly here, the system hangs completely.
What I'm I missing?
Thanks,
-Farid.
--
Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555
Broicherdorfstr. 83, D-41564 Kaarst, Germany | [EMAIL PROTECTED]
- - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - -
Murphy's Law fails only when you try to demonstrate it, and thus succeeds.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
