Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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: 1106:7204 00:01.0 Class 0604: 1106:b188 00:0a.0 Class 0200: 10ec:8139 (rev 10) 00:0f.0 Class 0101: 1106:0571 (rev 06) 00:10.0 Class 0c03: 1106:3038 (rev 81) 00:10.1 Class 0c03: 1106:3038 (rev 81) 00:10.2 Class 0c03: 1106:3038 (rev 81) 00:10.3 Class 0c03: 1106:3038 (rev 81) 00:10.4 Class 0c03: 1106:3104 (rev 86) 00:11.0 Class 0601: 1106:3227 00:11.5 Class 0401: 1106:3059 (rev 60) 00:18.0 Class 0600: 1022:1100 00:18.1 Class 0600: 1022:1101 00:18.2 Class 0600: 1022:1102 00:18.3 Class 0600: 1022:1103 01:00.0 Class 0300: 1002:4151 01:00.1 Class 0380: 1002:4171 Lee, Since I don't have access to the LKML, hopefully you won't mind too much by forwarding this message to the kernel (Linux) mailing list. Although, the original audio stutter is better, it's still a major problem (not usuable). In fact, I'm thinking of dumping Linux for the first time in a decade. I have a VIA K8M system and it's been a mess for more than 6 months. I just tried the 2.6.20-rc4 kernel as I'm near my wits end, but there's no improvement over 2.6.18 which is included in Slackware 11.0. The audio stutter is still here. sigh I'll hope for the best for awhile longer. TIA for forwarding this message. I'm using ALSA 1.0.14rc1 which is included in the 2.6.20-rc4 kernel. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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 changed from the 2.6.16.1 kernel which works fine with ALSA to the 2.6.17 kernel which works terribly with ALSA and the Via VT8237 chipset. You ought to hear this sucker sing! The echo is horrendous. What does lspci -n say? ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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: 10ec:8139 (rev 10) 00:0f.0 Class 0101: 1106:0571 (rev 06) 00:10.0 Class 0c03: 1106:3038 (rev 81) 00:10.1 Class 0c03: 1106:3038 (rev 81) 00:10.2 Class 0c03: 1106:3038 (rev 81) 00:10.3 Class 0c03: 1106:3038 (rev 81) 00:10.4 Class 0c03: 1106:3104 (rev 86) 00:11.0 Class 0601: 1106:3227 00:11.5 Class 0401: 1106:3059 (rev 60) 00:18.0 Class 0600: 1022:1100 00:18.1 Class 0600: 1022:1101 00:18.2 Class 0600: 1022:1102 00:18.3 Class 0600: 1022:1103 01:00.0 Class 0300: 1002:4151 01:00.1 Class 0380: 1002:4171 ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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 the 2.6.17 kernel which works terribly with ALSA and the Via VT8237 chipset. You ought to hear this sucker sing! The echo is horrendous. ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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- MAbort+ SERR- PERR- Latency: 8 Region 0: Memory at e000 (32-bit, prefetchable) [size=128M] Capabilities: [80] AGP version 3.0 Status: RQ=32 Iso- ArqSz=0 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3+ Rate=x4,x8 Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x8 Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [60] #08 [0060] Capabilities: [58] #08 [8001] 00:00.1 Host bridge: 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- MAbort- SERR- PERR- Latency: 0 00:00.2 Host bridge: 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- MAbort- SERR- PERR- Latency: 0 00:00.3 Host bridge: 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- MAbort- SERR- PERR- Latency: 0 00:00.4 Host bridge: 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- MAbort- SERR- PERR- Latency: 0 00:00.7 Host bridge: 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- MAbort- SERR- PERR- Latency: 0 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: c000-cfff Memory behind bridge: e800-e80f Prefetchable memory behind bridge: c000-dfff BridgeCtl: Parity- SERR+ NoISA+ VGA+ MAbort- Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: FIRST INTERNATIONAL Computer Inc: Unknown device 6001 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (8000ns min, 16000ns max) Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at d000 [size=256] Region 1: Memory at e811 (32-bit, non-prefetchable) [size=256] Expansion ROM at 2000 [disabled] [size=64K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:0f.0 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Subsystem: FIRST INTERNATIONAL Computer Inc: Unknown device 6001 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 Interrupt: pin A routed to IRQ 10 Region 4: I/O ports at d400 [size=16] Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI]) Subsystem: FIRST INTERNATIONAL Computer Inc: Unknown device 6001 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32, cache line size 08 Interrupt: pin A routed to IRQ 10 Region 4: I/O ports at d800 [size=32]
Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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 changed from the 2.6.16.1 kernel which works fine with ALSA to the 2.6.17 kernel which works terribly with ALSA and the Via VT8237 chipset. You ought to hear this sucker sing! The echo is horrendous. This bug report is too vague. What exactly are you doing, and what exactly are the symptoms? Lee ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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 segment of audio in this manner. The result is just a continuous jumble of echoes. Other users of similar hardware must be experiencing the same problem. I haven't done ANYTHING other than upgrade from the 2.6.16.1 kernel to the 2.6.17 kernel with a slightly newer (Hg) version of ALSA. Remember, this problem has been worsening throughout the life cyle of the 2.6.16.x kernels. HTH ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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 conflicting interrupts. If I play a brief tone ( 1 sec.), the tone will just echo for several seconds. Imagine listening to a longer segment of audio in this manner. The result is just a continuous jumble of echoes. Other users of similar hardware must be experiencing the same problem. I haven't done ANYTHING other than upgrade from the 2.6.16.1 kernel to the 2.6.17 kernel with a slightly newer (Hg) version of ALSA. Remember, this problem has been worsening throughout the life cyle of the 2.6.16.x kernels. HTH I think you are hitting a known bug that's caused not by ALSA but by a buggy PCI quirk for VIA chipsets. It's a regression introduced during the 2.6.16.x series. It has been discussed on LKML and should be fixed in the first 2.6.17 stable release. Lee ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user 2.6.17 is out according to http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.17 . ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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 ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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. The bug was not found in time for 2.6.17. Lee ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user Is there any automagical formula allowing to know which non-rc kernel is stable ? ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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. Visit http://win.mail.ru/cgi-bin/support_bl?ip=216.158.38.3 Giving up on 194.67.23.20. On Sun, 2006-06-18 at 22:37 +0300, Sergei Steshenko wrote: 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 conflicting interrupts. If I play a brief tone ( 1 sec.), the tone will just echo for several seconds. Imagine listening to a longer segment of audio in this manner. The result is just a continuous jumble of echoes. Other users of similar hardware must be experiencing the same problem. I haven't done ANYTHING other than upgrade from the 2.6.16.1 kernel to the 2.6.17 kernel with a slightly newer (Hg) version of ALSA. Remember, this problem has been worsening throughout the life cyle of the 2.6.16.x kernels. HTH I think you are hitting a known bug that's caused not by ALSA but by a buggy PCI quirk for VIA chipsets. It's a regression introduced during the 2.6.16.x series. It has been discussed on LKML and should be fixed in the first 2.6.17 stable release. Lee ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user 2.6.17 is out according to http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.17 . ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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 last kernel release. Lee ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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 recipient. Remote host said: 550 Access from ip address 216.158.38.3 blocked. Visit http://win.mail.ru/cgi-bin/support_bl?ip=216.158.38.3 Giving up on 194.67.23.20. On Sun, 2006-06-18 at 22:37 +0300, Sergei Steshenko wrote: 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 conflicting interrupts. If I play a brief tone ( 1 sec.), the tone will just echo for several seconds. Imagine listening to a longer segment of audio in this manner. The result is just a continuous jumble of echoes. Other users of similar hardware must be experiencing the same problem. I haven't done ANYTHING other than upgrade from the 2.6.16.1 kernel to the 2.6.17 kernel with a slightly newer (Hg) version of ALSA. Remember, this problem has been worsening throughout the life cyle of the 2.6.16.x kernels. HTH I think you are hitting a known bug that's caused not by ALSA but by a buggy PCI quirk for VIA chipsets. It's a regression introduced during the 2.6.16.x series. It has been discussed on LKML and should be fixed in the first 2.6.17 stable release. Lee ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user 2.6.17 is out according to http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.17 . ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user I myself have been having trouble accessing my the host in the last hour or so - service unavailable, authentication errors along with service. 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 version in the lower half of the page. I once filled the form to have work IP address removed, they did it. ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Terrible Echo With Via VT8237 Chipset, CVS (Recent) ALSA 2.6.17 Kernel
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 version in the lower half of the page. I once filled the form to have work IP address removed, they did it. Not this time. I've filled out that f**king form 10 times over the past week and nothing changes. Lee ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
