From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - tools 0001831]: envy24control does not work with Hercules Fortissimo IV
Date: Sat, 11 Feb 2006 13:48:41 +0100 [thread overview]
Message-ID: <d248d6bf673fb45b28f0a26293ed253e@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1831>
======================================================================
Reported By: liiwi
Assigned To:
======================================================================
Project: ALSA - tools
Issue ID: 1831
Category: envy24control
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 02-08-2006 20:03 CET
Last Modified: 02-11-2006 13:48 CET
======================================================================
Summary: envy24control does not work with Hercules Fortissimo
IV
Description:
Previously I did not have any pressing need to try envy24control. However
recently
for some odd reason left channel got just about muted. So, I tried
envy24control:
>No ICE1712 cards found
So, now I'm without left channel.
>From dmesg:
ice1724: No matching model found for ID 0x81160100
ice1724: Invalid EEPROM version 1
Hrm, this might be an driver issue if envy24control asks from driver about
the card and it does not know what model...
This happens with all the way to 1.0.11-rc3.
lspci says about the card:
>Multimedia audio controller: VIA Technologies Inc. VT1720/24
[Envy24PT/HT] PCI >Multi-Channel Audio Controller (rev 01)
======================================================================
----------------------------------------------------------------------
liiwi - 02-11-06 13:17
----------------------------------------------------------------------
Hrm, after playing with envy24control sources, mainly replacing "ICE1712"
with "ICE1724", it looks like reading from card eeprom does not give
what's expected.
Just a guess, though. So, this might be driver issue.
As ICE1712 requirement is hardcoded into envy24control, are there any
plans to add real ICE1724 support?
----------------------------------------------------------------------
liiwi - 02-11-06 13:48
----------------------------------------------------------------------
Ok, one problem solved: left channel was missing, because I had screwed up
bindings in .asoundrc.Color of face today is RED.
However, the thing about envy24control still is there. I'd also like to
record something, but so far I've only been able to get silence from
capture channels.
I'm just guessing that either the driver is not supporting this card
properly
or I just need to adjust levels with envy24control.
Issue History
Date Modified Username Field Change
======================================================================
02-08-06 20:03 liiwi New Issue
02-11-06 13:17 liiwi Note Added: 0008015
02-11-06 13:48 liiwi Note Added: 0008016
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next reply other threads:[~2006-02-11 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 12:48 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-22 20:58 [ALSA - tools 0001831]: envy24control does not work with Hercules Fortissimo IV bugtrack
2006-07-22 20:57 bugtrack
2006-07-22 20:56 bugtrack
2006-07-22 0:56 bugtrack
2006-02-11 12:17 bugtrack
2006-02-08 19:03 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=d248d6bf673fb45b28f0a26293ed253e@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