Re: Sound card problems with -current.
On Fri, 03 Sep 1999 11:27:55 -0400, "Arthur H. Johnson II" wrote: Well, I got rid of the old Voxware drivers and went with the pnp drivers and still nothing. Here is the dmesg: What does "still nothing" mean? I can't see anything in your e-mail message which indicates what you're doing to test the sound and what you see in the way of error messages. I do see this: pcm0: SoundBlaster 16 4.13 at port 0x220-0x22f irq 5 drq 5 flags 0x15 on isa0 That makes it look like your card's available. Are you sure you've created the appropriate devices and symlinks as follows: cd /dev ./MAKEDEV snd0 The pcm(4) manpage says snd1, but if your card's detected as pcm0, then that obviously doesn't apply. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
That didnt work. When I ran mpg123 it said can't access /dev/dsp but the mixer worked. And yes, i did run makedev. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Fri, 3 Sep 1999, Sheldon Hearn wrote: On Fri, 03 Sep 1999 11:27:55 -0400, "Arthur H. Johnson II" wrote: Well, I got rid of the old Voxware drivers and went with the pnp drivers and still nothing. Here is the dmesg: What does "still nothing" mean? I can't see anything in your e-mail message which indicates what you're doing to test the sound and what you see in the way of error messages. I do see this: pcm0: SoundBlaster 16 4.13 at port 0x220-0x22f irq 5 drq 5 flags 0x15 on isa0 That makes it look like your card's available. Are you sure you've created the appropriate devices and symlinks as follows: cd /dev ./MAKEDEV snd0 The pcm(4) manpage says snd1, but if your card's detected as pcm0, then that obviously doesn't apply. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: That didnt work. When I ran mpg123 it said can't access /dev/dsp but the mixer worked. And yes, i did run makedev. What are the permissions on /dev/dsp*? Are other deamons running that are attempting to access /dev/dsp? As an example, I ran E once and enabled 'sounds' from within e-conf only to find that while 'esd' is running, gqmpeg will not run (it reports 'Can't access /dev/dsp'). Good luck, -Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
Well, i recompiled with the Voxware drivers and commented out the pnp0 device, and now it works. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Fri, 3 Sep 1999, Mike Hoskins wrote: On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: That didnt work. When I ran mpg123 it said can't access /dev/dsp but the mixer worked. And yes, i did run makedev. What are the permissions on /dev/dsp*? Are other deamons running that are attempting to access /dev/dsp? As an example, I ran E once and enabled 'sounds' from within e-conf only to find that while 'esd' is running, gqmpeg will not run (it reports 'Can't access /dev/dsp'). Good luck, -Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: Well, I got rid of the old Voxware drivers and went with the pnp drivers and still nothing. Here is the dmesg: -- pcm0: SoundBlaster 16 4.13 at port 0x220-0x22f irq 5 drq 5 flags 0x15 on isa0 unknown0: Game on isa0 unknown1: Audio at port 0x240-0x24f,0x300-0x301,0x388-0x38b irq 9 drq 1,7 on isa0 I'm confused by the unknown1 line. Could you send the output of 'pnpinfo' for this machine. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: Okay. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] Now I'm really confused. It looks like you have an explicit line for the soundcard in your config (e.g. "device pcm0 at isa? port ? ...") but the config file which you posted only had a "device pcm0" line. With the new driver, if it is a pnp card, you mustn't specify resources. What appears to have happened is that the probe hints (which must have matched the bios settings) allowed pcm0 to probe and attach the card. After that, the pnp code allocated resources for the Audio logical device, avoiding the resources already allocated by pcm0. This moved the card settings away from what the driver was expecting, effectively disabling pcm0. Since the Audio device didn't probe as pcm1, you may also have the buggy version of pci.c which was overwriting some of the pnp information. Make sure that you have at least version 1.117 of pci.c. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Fri, 3 Sep 1999, Doug Rabson wrote: On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: Okay. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] Now I'm really confused. It looks like you have an explicit line for the soundcard in your config (e.g. "device pcm0 at isa? port ? ...") but the config file which you posted only had a "device pcm0" line. With the new driver, if it is a pnp card, you mustn't specify resources. Um, I did try that once, but I tried it the correct way and it still didnt work. What appears to have happened is that the probe hints (which must have matched the bios settings) allowed pcm0 to probe and attach the card. After that, the pnp code allocated resources for the Audio logical device, avoiding the resources already allocated by pcm0. This moved the card settings away from what the driver was expecting, effectively disabling pcm0. Since the Audio device didn't probe as pcm1, you may also have the buggy version of pci.c which was overwriting some of the pnp information. Make sure that you have at least version 1.117 of pci.c. BINGO! I had pci.c version 1.116. It is running off pcm0 now thou. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd.Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
