On Monday 08 March 2004 20:55, Andreas Mohr wrote:
> Hi,
>
> On Mon, Mar 08, 2004 at 09:40:01AM -0800,
[EMAIL PROTECTED] wrote:
> > Message: 11
> > From: Casey Heshler <[EMAIL PROTECTED]>
> > Reply-To: [EMAIL PROTECTED]
> > To: [EMAIL PROTECTED]
> > Date: Mon, 8 Mar 2004 09:26:55 +0100
> > Subject: [Alsa-user] ALSA is dreamware on my system...
> >
> > Anyone who has been following the "saga" of ALSA, and me, and my posts,
> > will KNOW - I finally got ALSA running on my system, but, at a serious
> > cost. I now have "introduced" noise/static with any sound recording I do
> > - of which - this was not the issue with my "default" previous sound
> > within a hdd installed Knoppix.
> >
> > ALSA Subscriber E-Mail Group has been useless in getting any resolve for
> > the noise - and all I know is that I can't record without getting this
> > static/noise in my audio recordings now - which IS NOT a valid option.
> >
> > Upon posting a querry on how to yank out ALSA - the suggestion to rip
> > "alsa" from firing off in init.d - has turned into a system that has a
> > 1.7GHz processor, that now runs sluggish, and extremely slow, mouse
> > movement has become jumpy, instead of smooth moving, and if I wanted to
> > put ALSA back into the init.d, it refuses to be added because it doesn't
> > have a proper sort order ID.
>
> Whoops, sounds quite bad indeed.
> Well, at least the sluggishness should be able to get resolved quite easily
> by running top and watching what stuff slows the system down by e.g.
> hogging the CPU.
> Then run "ps fax|less" and look for the parent process of the CPU hogging
> process. Then look at the ALSA files in init.d and think about how this
> could have happened. Maybe you actually have module load/fail looping
> problem? (some modules might especially stall the system during init phase)
>
> Oh, and reinstalling ALSA init files in a working way should be possible
> using update-rc.d -f alsa remove
> update-rc.d -f alsa defaults
> That should fix the problem.
>
> But PLEASE - before finally removing ALSA, record the type of static/noise
> you get and place it somewhere for others to download/diagnose.
> Otherwise you would have filed irate complaint after irate complaint
> without anyone being able to diagnose the issue with some helpful data. ;-)
I would love for "someone" to hear what I am hearing - I can post a 10 second
WAV file, but my concern is - how, and where, do I do this? Can I place the
file in a "common" local location, and then post the target area???
> Also report
> lspci -v -v; cat /proc/interrupts
Ask, and you shall receive: (this is after getting alsa back to booting in the
init.d)
[EMAIL PROTECTED]:/installs# lspci -v -v;cat /proc/interrupts
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 81)
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
Region 0: Memory at d8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans-
64bit- FW+ AGP3- Rate=x1,x2
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW-
Rate=<none>
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:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
(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
Memory behind bridge: dc000000-ddffffff
Prefetchable memory behind bridge: d0000000-d7ffffff
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:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev
40)
Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA 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
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:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
(prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc.
VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
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
Region 4: I/O ports at d000 [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:07.2 USB Controller: VIA Technologies, Inc. USB (rev 1a) (prog-if 00
[UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
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: 0x08 (32 bytes)
Interrupt: pin D routed to IRQ 5
Region 4: I/O ports at d400 [size=32]
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:07.3 USB Controller: VIA Technologies, Inc. USB (rev 1a) (prog-if 00
[UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
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: 0x08 (32 bytes)
Interrupt: pin D routed to IRQ 5
Region 4: I/O ports at d800 [size=32]
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:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
Subsystem: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
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-
Capabilities: [68] 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:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97
Audio Controller (rev 50)
Subsystem: VIA Technologies, Inc. VT82C686 AC97 Audio Controller
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-
Interrupt: pin C routed to IRQ 10
Region 0: I/O ports at dc00 [size=256]
Region 1: I/O ports at e000 [size=4]
Region 2: I/O ports at e400 [size=4]
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-
01:00.0 VGA compatible controller: S3 Inc. ProSavage KM133 (rev 03) (prog-if
00 [VGA])
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 (1000ns min, 63750ns max), Cache Line Size: 0x08 (32
bytes)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at dd000000 (32-bit, non-prefetchable) [size=512K]
Region 1: Memory at d0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [dc] 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: [80] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans-
64bit- FW- AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW-
Rate=x4
CPU0
0: 7339660 XT-PIC timer
1: 21559 XT-PIC keyboard
2: 0 XT-PIC cascade
4: 290488 XT-PIC serial
5: 1024 XT-PIC usb-uhci, usb-uhci
8: 1 XT-PIC rtc
10: 191718 XT-PIC VIA686A
12: 232860 XT-PIC PS/2 Mouse
14: 108740 XT-PIC ide0
15: 1580 XT-PIC ide1
NMI: 0
LOC: 7339526
ERR: 1070
MIS: 0
[EMAIL PROTECTED]:/installs#
Thank You for the Init.d stuff -=- IT WORKED -=- ALSA is back in Sys-V now,
>
> > Someone tell me, without having to re-install Knoppix, how I can take
> > ALSA COMPLETELY OFF my system, and return to using arTs, since IT
> > ACTUALLY WORKED without the noise/static problem. When my business deals
> > with recording sound for my customers, a sound system like ALSA is NOT
> > going to work if all it does is throw noise and static into a clean
> > recording. Arts at least could do that, whereas, ALSA appears it can
> > not...
>
> dpkg -r alsa-base alsa-headers alsa-utils alsaplayer alsaplayer-alsa
> alsaplayer-common alsaplayer-gtk libasound2 libasound2-dev should do the
> job.
> But a simple
> dpkg -r alsa-base
> would be more elegant, since it would simply remove ALSA init elements
> and would leave the remaining ALSA infrastructure in place for eventual
> later use.
>
> > I need to get my business back running, right now, I'm stuck with crummy
> > ALSA, and noise, static recordings - of which - I never had this problem
> > with the original sound that Knoppix had running before.
> >
> > Thank you for any assistance, I thank you, my business thanks you, and my
> > customers thank you,
> > Casey
>
> I can imagine that :)
>
> Anyway, ALSA has TONS of different soundcards to support, and problems
> with some soundcards can be very nasty to debug, I imagine:
> I've written my own ALSA driver (azf3328) too, which incidentally also
> still is quite buggy due to major amounts of work that I had to do since
> the soundcard is completely undocumented/unsupported. But please note that
> this card isn't supported in Windows XP/2000 at all!
> All in all that's why it's relatively easily possible for some soundcard
> driver to not support its soundcard properly/fully. And yes, I'm also
> inclined to believe that deciding ALSA to be the preferred sound system in
> early 2.6.x versions is a bit problematic (especially since you can read
> about misc. problems with OSS emulation every third day or so ;-) That's
> not to say that ALSA is crap - as far as I'm concerned it's quite some cool
> feat. It's just that its time hasn't quite come yet, it seems (when it
> comes to configurability and hardware compatibility).
>
> Andreas Mohr
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
