Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Clark <stephen.clark@earthlink.net>
To: alsa-devel@lists.sourceforge.net
Subject: Re: 2.6.12 sound problem
Date: Thu, 28 Jul 2005 10:11:56 -0400	[thread overview]
Message-ID: <42E8E7AC.1080706@earthlink.net> (raw)
In-Reply-To: <42E6C89C.1060009@earthlink.net>

Stephen Clark wrote:

>Hello List,
>
>
>I recently upgraded my laptop, HP Pavilion N5430, from a 2.4.21 kernel
>to 2.6.12. As a result of
>doing this my sound no longer works correctly. It plays the same thing
>repeatedly some number
>of times - if it plays at all.
>
>Any ideas on how to debug this would be appreciated.
>
>Additional info I don't see any interrupts in /proc/interrupts for the 
>Allegro which is on int 5.
>I just tried the same laptop with knoppix and a 2.4.27 kernel and sound 
>works great and I do
>see interrupts for Allegro on int 5.
>
>
>Thanks,
>Steve
>
>aplay -v and aadebug output follow.
>
>root@joker4 ~]# aplay -v /usr/share/apps/kget/sounds/started.wav
>Playing WAVE '/usr/share/apps/kget/sounds/started.wav' : Unsigned 8 bit,
>Rate 11128 Hz,Mono
>Plug PCM: Hardware PCM card 0 'ESS Allegro PCI' device 0 subdevice 1
>
>Its setup is:
>stream       : PLAYBACK
>access       : RW_INTERLEAVED
>format       : U8
>subformat    : STD
>channels     : 1
>rate         : 11128
>exact rate   : 11128 (11128/1)
>msbits       : 8
>buffer_size  : 5564
>period_size  : 1391
>period_time  : 125000
>tick_time    : 1000
>tstamp_mode  : NONE
>period_step  : 1
>sleep_min    : 0
>avail_min    : 1391
>xfer_align   : 1391
>start_threshold  : 5564
>stop_threshold   : 5564
>silence_threshold: 0
>silence_size : 0
>boundary     : 1458569216
>aplay: pcm_write:1171: write error: Input/output error
>
>aadebug output:
>ALSA Audio Debug v0.0.9 - Mon Jul 25 14:49:10 EDT 2005
>http://alsa.opensrc.org/?page=aadebug
>
>Kernel ----------------------------------------------------
>Linux joker4.seclark.com 2.6.12-prep #1 Sun Jul 24 22:39:46 EDT 2005
>i686 athlon i386 GNU/Linux
>
>Loaded Modules --------------------------------------------
>snd_maestro3           25252  2
>snd_ac97_codec         76408  1 snd_maestro3
>snd_seq_dummy           3972  0
>snd_seq_oss            37760  0
>snd_seq_midi_event      9600  1 snd_seq_oss
>snd_seq                62992  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
>snd_seq_device          9228  3 snd_seq_dummy,snd_seq_oss,snd_seq
>snd_pcm_oss            51760  0
>snd_mixer_oss          18304  1 snd_pcm_oss
>snd_pcm               100744  4 snd_maestro3,snd_ac97_codec,snd_pcm_oss
>snd_timer              33924  2 snd_seq,snd_pcm
>snd_page_alloc         10116  1 snd_pcm
>snd                    57860  12
>snd_maestro3,snd_ac97_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
>
>Modprobe Conf ---------------------------------------------
>alias snd-card-0 snd-maestro3
>options snd-card-0 index=0
>options snd-maestro3 index=0
>remove snd-maestro3 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ;
>}; /sbin/modprobe -r --ignore-remove snd-maestro3
>
>Proc Asound -----------------------------------------------
>Advanced Linux Sound Architecture Driver Version 1.0.9rc2  (Thu Mar 24
>10:33:392005 UTC).
>0 [PCI            ]: Allegro - ESS Allegro PCI
>                       ESS Allegro PCI at 0x1400, irq 5
>    1:       : sequencer
>   16: [0- 0]: digital audio playback
>   24: [0- 0]: digital audio capture
>    0: [0- 0]: ctl
>   33:       : timer
>00-00: Allegro : Allegro : playback 2 : capture 1
>
>Dev Snd ---------------------------------------------------
>controlC0  pcmC0D0c  pcmC0D0p  seq  timer
>
>CPU -------------------------------------------------------
>model name      : mobile AMD Duron(tm) Processor
>cpu MHz         : 299.999
>
>RAM -------------------------------------------------------
>MemTotal:       255652 kB
>SwapTotal:      524280 kB
>
>Hardware --------------------------------------------------
>00:00.0 Host bridge: ALi Corporation M1647 Northbridge [MAGiK 1 /
>MobileMAGiK 1] (rev 04)
>00:08.0 Multimedia audio controller: ESS Technology ES1988 Allegro-1
>(rev 12)
>
>  
>
I've downloaded the latest alsa 1.09rc4a and tried it with no success. 
Is there anything I can do
to further troubleshoot this. I configured the sw --with-debug=full but 
didn't see any additional output.
I am willing to get my hands dirty if someone will give me some 
direction. This laptop is used by my teenage daughter and she has to 
have sound ;).

Steve


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  parent reply	other threads:[~2005-07-28 14:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 23:34 2.6.12 sound problem Stephen Clark
2005-07-27  7:14 ` Jaroslav Kysela
2005-07-28 14:05   ` Stephen Clark
2005-07-28 14:11 ` Stephen Clark [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-01  3:06 Yuan, Hang
2005-07-29 10:21 Yuan, Hang
2005-07-29 12:41 ` Stephen Clark
2005-07-30  3:05   ` Stephen Clark
2005-07-26 17:08 Stephen Clark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42E8E7AC.1080706@earthlink.net \
    --to=stephen.clark@earthlink.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=sclark46@earthlink.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox