From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000021]: HDSP 9652 not recognized on boot 80-90% of the time
Date: Tue, 1 Feb 2005 21:12:21 +0100 [thread overview]
Message-ID: <2efe1941ef6661bd2b060e9fcf44ff62@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=21>
======================================================================
Reported By: Mark Knecht
Assigned To: charbonnel
======================================================================
Project: ALSA - driver
Issue ID: 21
Category: PCI - RME HDSP
Reproducibility: random
Severity: major
Priority: normal
Status: assigned
Distribution: Gentoo
Kernel Version: 2.4.22-rc2 & others
======================================================================
Date Submitted: 01-31-2004 23:13 CET
Last Modified: 02-01-2005 21:12 CET
======================================================================
Summary: HDSP 9652 not recognized on boot 80-90% of the time
Description:
The HDSP 9652 is not recognized 80-90% of the time on boot. Restarting Alsa
in an xterm produces the same messages. Out of at least 20 boots this
afternoon only one has found the device.
======================================================================
----------------------------------------------------------------------
charbonnel - 05-12-04 11:32
----------------------------------------------------------------------
Hi Aaron,
Are you still overclocking (even 'properly') ?
Things you could try :
* running jack and a few console audio applications (e.g. ecasound)
without X to see if the problem is still here
* running a vanilla kernel (the gentoo kernels are usually heavily
patched)
Thomas
----------------------------------------------------------------------
charbonnel - 02-01-05 21:12
----------------------------------------------------------------------
Hi Mark,
Do you still experience the problem with alsa 1.0.8 ? If so could you
please try alsa-cvs ?
Thanks,
Thomas
Issue History
Date Modified Username Field Change
======================================================================
01-31-04 23:13 Mark Knecht New Issue
01-31-04 23:14 Mark Knecht Note Added: 0000081
01-31-04 23:17 Mark Knecht Note Added: 0000083
02-01-04 08:21 perex Assigned To => charbonnel
02-01-04 08:21 perex Status new => assigned
02-01-04 08:21 perex Category PCI - RME Digi9652/9636
=> PCI - RME HDSP
02-01-04 13:11 charbonnel File Added: hdsp9652.patch
02-01-04 13:12 charbonnel Note Added: 0000089
02-01-04 13:36 Mark Knecht Note Added: 0000090
02-01-04 13:52 Mark Knecht Note Added: 0000091
02-01-04 14:01 charbonnel File Added: hdsp9652_2.patch
02-01-04 14:02 charbonnel Note Added: 0000092
02-01-04 14:15 Mark Knecht Note Added: 0000093
02-01-04 14:16 Mark Knecht Note Edited: 0000093
02-01-04 14:18 Mark Knecht Note Added: 0000094
02-01-04 14:53 charbonnel Note Added: 0000095
02-01-04 15:05 Mark Knecht Note Added: 0000096
02-01-04 15:42 charbonnel File Added: hdsp9652_3.patch
02-01-04 15:43 charbonnel Note Added: 0000097
02-01-04 17:55 Mark Knecht Note Added: 0000099
02-01-04 17:59 Mark Knecht Note Added: 0000100
02-01-04 18:00 Mark Knecht Note Edited: 0000099
02-01-04 18:09 charbonnel Note Added: 0000101
02-02-04 04:01 Mark Knecht Note Added: 0000103
02-02-04 04:01 Mark Knecht File Added: alsa-driver-1.0.2a.ebuild
02-02-04 04:03 Mark Knecht Note Edited: 0000103
02-02-04 04:04 Mark Knecht Note Edited: 0000103
02-08-04 23:04 Mark Knecht Note Added: 0000206
03-09-04 18:48 perex Status assigned => resolved
03-09-04 18:48 perex Resolution open => suspended
03-09-04 18:48 perex Assigned To charbonnel => perex
03-09-04 18:48 perex Note Added: 0000556
03-09-04 21:20 Mark Knecht Status resolved => feedback
03-09-04 21:20 Mark Knecht Resolution suspended => reopened
03-09-04 21:21 Mark Knecht Note Added: 0000558
03-12-04 12:50 perex Assigned To perex => charbonnel
03-15-04 12:14 perex Status feedback => assigned
05-08-04 03:36 charbonnel Note Added: 0001067
05-08-04 06:14 Mark Knecht Note Added: 0001068
05-08-04 06:14 nquit Note Added: 0001069
05-09-04 21:30 charbonnel Note Added: 0001073
05-09-04 23:08 Mark Knecht Note Added: 0001074
05-09-04 23:53 nquit Note Added: 0001075
05-09-04 23:58 nquit Note Added: 0001076
05-12-04 11:32 charbonnel Note Added: 0001091
02-01-05 21:12 charbonnel Note Added: 0003464
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next reply other threads:[~2005-02-01 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 20:12 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-01 20:41 [ALSA - driver 0000021]: HDSP 9652 not recognized on boot 80-90% of the time bugtrack
2005-02-01 21:10 bugtrack
2005-05-31 16:04 bugtrack
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=2efe1941ef6661bd2b060e9fcf44ff62@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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