Hi list people,,

I tried a yfm724 sound card, only to find it isn't supported.
Then I switched to an old Opti ISA sound card, only to find it isn't
detected..

(sndconfig tells me that no cards were found. but it works in a winblows
machine.)

any suggestions?


regards

Frank

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tafta Zani
Sent: Monday, 12 February 2001 7:50 AM
To: [EMAIL PROTECTED]
Subject: Re: [newbie] sound card problems with 7.2


hi there,

one of my computers is using SB 16 ISA too.
if you get a device bussy message, try to kill the application
that using the /dev/dsp.
1. login as root (Xwindows or console)
2. type this in console or terminal
    fuser /dev/dsp
    three digit number will appear
3. type this
    kill xxx
    where xxx is the three digit number.

try to configure your SC now.
These work on mine.

good luck!
Tafta

----- Original Message -----
From: Chris Russell <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 06, 2001 1:49 PM
Subject: [newbie] sound card problems with 7.2


>     I have a good install of 7.2 with one exception. I can't get the sound
> card to work. I have tried a dozen different sound cards with no success.
>
> In HardDrake, the sound card shows up but has no IRQ attached to it. If I
> type in IRQ5, I get an error that it is busy or in use. How do I find out
> what device is using IRQ 5? It is not the network card. The SCSI card bios
> says it is at IRQ 9. I baffled. HELP... I also tried ESS cards with the
> same error message.
>
>   Here is my hardware profile:
>
> TMC TD6NF Dual Pentium Pro motherboard w/ 2 ppro 166/512 cpus overclocked
> to 180
> 128 megs RAM - 8 - 16mb 72-pin chips
> Diamond Viper 330 PCI video
> Atech 56k jumpered modem @ com 2 irq 3
> PCI network card
> Buslogic scsi controller PCI
> Soundblaster 16 ISA card
> 2 IBM 68-pin 2.1 gig drives
> Toshiba scsi CD ROM
> 3 1/2 floppy
> ATX case
> PS/2 keyboard and mouse
> both IDE turned off in BIOS
> both COM ports turned off in BIOS
>
> Thanks!
> Chris Russell
>
>



Reply via email to