Ollivier Robert wrote:
> According to Peter Wemm:
> > Have you tried plain "device pcm0"?
>
> Yes, nothing was found.
>
> > (and if it's not detected (ie: it's a
> > motherboard resources rather than a pnp isa device), try adding "options
> > PNPBIOS" to your kernel.)
>
> Here are the results of dmesg with PNPBIOS:
Err.. *both* PNPBIOS and 'device pcm0' - the dmesg you showed below is
with a static ISA sb card configured. I'm particularly interested in
ADS7180, but it's conflicting with something, possibly the ISA pcm0.
case 0x80719304: /* ADS7180 */
s = "Terratec Soundsystem BASE 1";
break;
> [EMAIL PROTECTED]:/src/src/sys/compile/CAERDONN
> [...]
> pcm0: <SoundBlaster Pro 3.2> at irq 5 drq 1 flags 0x15 on isa0
> [...]
> unknown0: <PNP0c02> at port 0x2e-0x2f,0xe0-0xe7,0xe8-0xe9,0x8400-0x8403,0x840
4-0x8407,0x8408-0x8409,0x8410-0x841f,0x80 iomem 0xfffe0000-0xffffffff on is
a0
> unknown1: <PNP0c01> at iomem 0-0x9ffff,0xea000-0xfffff,0x100000-0xfffffff on
isa0
> unknown2: <PNP0200> at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0
> unknown: <PNP0000> can't assign resources
> unknown3: <PNP0100> at port 0x40-0x43 irq 0 on isa0
> unknown4: <PNP0b00> at port 0x70-0x71 irq 8 on isa0
> unknown: <PNP0303> can't assign resources
> unknown5: <PNP0c04> at port 0xf0-0xff irq 13 on isa0
> unknown: <PNP0800> can't assign resources
> unknown6: <PNP0a03> at port 0xcf8-0xcff on isa0
> unknown7: <PNP0c02> at port 0x4d0-0x4d1,0x8000-0x803f,0x2180-0x218f on isa0
> unknown8: <PNP0c02> at iomem 0xfec00000-0xfec0ffff,0xfee00000-0xfee00fff on i
sa0
> unknown: <PNP0f13> can't assign resources
> unknown: <PNP0501> can't assign resources
> unknown: <PNP0501> can't assign resources
> unknown: <PNP0401> can't assign resources
> unknown: <PNP0700> can't assign resources
> unknown: <ADS7180> can't assign resources
> unknown9: <ADS7182> at port 0x200-0x207 on isa0
^^^^^^^^^^^^^^^^^^^^^^^^^^^ These two look like SB + Game port.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
