Peter Wemm wrote:
> Try changing the 'device pcm0 at .' to this:
>
> options PNPBIOS
> device pcm0
>
> with *no* 'at isa?'. See what happens. If it shows up in the pnp id tags but
> isn't recognized, show us the 'unknown*' lines from dmesg.
Tried that. The config and dmesg output follows
Frank Mayhar wrote:
> Nick Sayer wrote:
> > Frank Mayhar wrote:
> > > Well, this doesn't help me a whole lot with pcm.
> > I think it does. Try configuring pcm0 at 0x534 (4, not 0), irq 5,
> > dma 0, flags 0x11 (presuming the BIOS says 0x530, irq 5, dma 0 & 1).
> > This did work for me once upon
Nick Sayer wrote:
> Frank Mayhar wrote:
> > Well, this doesn't help me a whole lot with pcm.
> I think it does. Try configuring pcm0 at 0x534 (4, not 0), irq 5,
> dma 0, flags 0x11 (presuming the BIOS says 0x530, irq 5, dma 0 & 1).
> This did work for me once upon a time, modulo bugs in the old p
Cameron Grant wrote:
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> > I did that and it still hangs. Let me see if it's for the same reason.
> > Maybe *sc is getting stepped on somehow?
> very odd. i have no idea what is going on.
> i have committed bits, so try again in a few hours.
Frank Mayhar wrote:
> Well, this doesn't help me a whole lot with pcm.
I think it does. Try configuring pcm0 at 0x534 (4, not 0), irq 5,
dma 0, flags 0x11 (presuming the BIOS says 0x530, irq 5, dma 0 & 1).
This did work for me once upon a time, modulo bugs in the old pcm code.
To Unsubscribe:
Nick Sayer wrote:
> For what it's worth, I believe the Insperion 3500 is an oddity.
>
> When I was dealing with OSS, the correct configuration turned out to be
> a "Generic 256AV" located at 0x530, I5, DMA 0&1 -- that is, you treat
> it just like an ordinary Windows Sound System chip (CS4231). Th
For what it's worth, I believe the Insperion 3500 is an oddity.
When I was dealing with OSS, the correct configuration turned out to be
a "Generic 256AV" located at 0x530, I5, DMA 0&1 -- that is, you treat
it just like an ordinary Windows Sound System chip (CS4231). The PCI
interface, I believe,
Cameron Grant wrote:
> i have just committed a driver for the neomagic chips. please test and post
> results.
Okay. I have a Dell Inspiron 3500, with a NeoMagic 256AV chipset in it.
It hangs on boot, in nm_rd() line 146. Here's the backtrace:
(kgdb) bt
#0 nm_rd (sc=0xc0d83100, regno=1536, si
i have just committed a driver for the neomagic chips. please test and post
results.
- cameron
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
