Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2007-01-08 Thread T . P . Reitzel
T.P. Reitzel tpreitzel at hotmail.com writes: Lee, In a more compact form, here's the output of lspci -n : 00:00.0 Class 0600: 1106:0204 00:00.1 Class 0600: 1106:1204 00:00.2 Class 0600: 1106:2204 00:00.3 Class 0600: 1106:3204 00:00.4 Class 0600: 1106:4204 00:00.7 Class 0600:

Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-19 Thread Lee Revell
On Sun, 2006-06-18 at 09:05 -0700, T.P. Reitzel wrote: I first mentioned this echo problem while experimenting with the 2.6.16.18 kernel. The problem is even worse now. Audio is totally unusable. Although my PC hasn't hardlocked yet, it just might at some point in the future. I simply

[Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-19 Thread T.P. Reitzel
Lee, In a more compact form, here's the output of lspci -n : 00:00.0 Class 0600: 1106:0204 00:00.1 Class 0600: 1106:1204 00:00.2 Class 0600: 1106:2204 00:00.3 Class 0600: 1106:3204 00:00.4 Class 0600: 1106:4204 00:00.7 Class 0600: 1106:7204 00:01.0 Class 0604: 1106:b188 00:0a.0 Class 0200:

[Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-18 Thread T.P. Reitzel
I first mentioned this echo problem while experimenting with the 2.6.16.18 kernel. The problem is even worse now. Audio is totally unusable. Although my PC hasn't hardlocked yet, it just might at some point in the future. I simply changed from the 2.6.16.1 kernel which works fine with ALSA to

[Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-18 Thread T.P. Reitzel
00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge Subsystem: VIA Technologies, Inc. K8M800 Host Bridge Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort-

Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-18 Thread Lee Revell
On Sun, 2006-06-18 at 09:05 -0700, T.P. Reitzel wrote: I first mentioned this echo problem while experimenting with the 2.6.16.18 kernel. The problem is even worse now. Audio is totally unusable. Although my PC hasn't hardlocked yet, it just might at some point in the future. I simply

[Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-18 Thread T.P. Reitzel
Lee - I don't know if I can explain it much better, but here's another attempt. ANY sound just echoes for several seconds almost like the problem is due to conflicting interrupts. If I play a brief tone ( 1 sec.), the tone will just echo for several seconds. Imagine listening to a longer

Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-18 Thread Sergei Steshenko
On Sun, 18 Jun 2006 13:54:48 -0400 Lee Revell [EMAIL PROTECTED] wrote: On Sun, 2006-06-18 at 11:39 -0700, T.P. Reitzel wrote: Lee - I don't know if I can explain it much better, but here's another attempt. ANY sound just echoes for several seconds almost like the problem is due to

Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-18 Thread Lee Revell
On Sun, 2006-06-18 at 22:37 +0300, Sergei Steshenko wrote: 2.6.17 is out according to http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.17 . I said the first 2.6.17 -stable release meaning 2.6.17.1. The bug was not found in time for 2.6.17. Lee

Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-18 Thread Sergei Steshenko
On Sun, 18 Jun 2006 15:42:55 -0400 Lee Revell [EMAIL PROTECTED] wrote: On Sun, 2006-06-18 at 22:37 +0300, Sergei Steshenko wrote: 2.6.17 is out according to http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.17 . I said the first 2.6.17 -stable release meaning 2.6.17.1.

Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-18 Thread Lee Revell
I am STILL getting this message from your ISP even though I have repeatedly filled out the form. Please do not mail me again until it's fixed or you have changed ISPs. [EMAIL PROTECTED]: 194.67.23.20 does not like recipient. Remote host said: 550 Access from ip address 216.158.38.3 blocked.

Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-18 Thread Lee Revell
On Sun, 2006-06-18 at 22:48 +0300, Sergei Steshenko wrote: Is there any automagical formula allowing to know which non-rc kernel is stable ? I am not referring to stable in the conventional sense. -stable in kernel development has a specific meaning - it refers to the bugfixes applied to the

Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-18 Thread Sergei Steshenko
On Sun, 18 Jun 2006 15:50:44 -0400 Lee Revell [EMAIL PROTECTED] wrote: I am STILL getting this message from your ISP even though I have repeatedly filled out the form. Please do not mail me again until it's fixed or you have changed ISPs. [EMAIL PROTECTED]: 194.67.23.20 does not like

Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel

2006-06-18 Thread Lee Revell
On Mon, 2006-06-19 at 00:28 +0300, Sergei Steshenko wrote: This problem goes away by itself. Anyway, they are asking to fill a form from your, not somebody else's, IP address, and the http://win.mail.ru/cgi-bin/support_bl?ip=216.158.38.3 page has an English form to be filled - see English