Re: [Alsa-user] alsaconf: setup of soundchip VIA 8237 fails - SuSE-Linux 9.2

2006-11-16 Thread Clemens Ladisch
Heinz Knoche wrote: Without success I tried to set up my soundchip. ... 4. Is it at all possible that the soundchip's silence is related to the sharing of an interrupt? No. What are the contents of /proc/asound/cards? Regards, Clemens

Re: [Alsa-user] alsaconf: setup of soundchip VIA 8237 fails - SuSE-Linux 9.2

2006-11-16 Thread Heinz Knoche
Sorry for getting the same mail a second time Clemens, I just forgot including the alsa-user list ! Clemens Ladisch schrieb: Heinz Knoche wrote: Without success I tried to set up my soundchip. ... 4. Is it at all possible that the soundchip's silence is related to the sharing of an

Re: [Alsa-user] alsaconf: setup of soundchip VIA 8237 fails - SuSE-Linux 9.2

2006-11-16 Thread Clemens Ladisch
Heinz Knoche wrote: Clemens Ladisch schrieb: What are the contents of /proc/asound/cards? cat /proc/asound/cards 0 [rev60 ]: VIA8233 - VIA 823x rev60 VIA 823x rev60 with CMI9761 at 0xd000, irq 3 This codec should be supported even by your old ALSA version.

Re: [Alsa-user] alsaconf: setup of soundchip VIA 8237 fails - SuSE-Linux 9.2

2006-11-16 Thread Heinz Knoche
Clemens Ladisch schrieb: Heinz Knoche wrote: Clemens Ladisch schrieb: What are the contents of /proc/asound/cards? cat /proc/asound/cards 0 [rev60 ]: VIA8233 - VIA 823x rev60 VIA 823x rev60 with CMI9761 at 0xd000, irq 3 This codec should be supported

Re: [Alsa-user] alsaconf: setup of soundchip VIA 8237 fails - SuSE-Linux 9.2

2006-11-16 Thread Lee Revell
On Fri, 2006-11-17 at 02:21 +0100, Heinz Knoche wrote: Clemens Ladisch schrieb: Heinz Knoche wrote: Clemens Ladisch schrieb: What are the contents of /proc/asound/cards? cat /proc/asound/cards 0 [rev60 ]: VIA8233 - VIA 823x rev60 VIA 823x rev60 with

[Alsa-user] alsaconf: setup of soundchip VIA 8237 fails - SuSE-Linux 9.2

2006-11-15 Thread Heinz Knoche
Dear people! Without success I tried to set up my soundchip. I noted: 1. The alsa-driver via82xx is sharing IRQ 3 with ehci_hcd (related to the usb-system ??). 2. How could I prevent the usb-drivers from being loaded at boot? 3. How could I asign interrupts differently? 4. Is it at all possible