From: Giuliano Pochini <pochini@shiny.it>
To: "F. Heitkamp" <heitkamp@ameritech.net>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
linux-audio-user@lists.linuxaudio.org,
Clemens Ladisch <clemens@ladisch.de>,
linux-kernel@vger.kernel.org, alsa-user@lists.sourceforge.net
Subject: Re: [Alsa-user] [alsa-devel] Crash 2.6.32.x, Echo 3G, Alsa, SCSI
Date: Thu, 3 Jun 2010 00:08:28 +0200 [thread overview]
Message-ID: <20100603000828.04af4bdc@Jay> (raw)
In-Reply-To: <4C04FC3F.70905@ameritech.net>
On Tue, 01 Jun 2010 08:25:35 -0400
"F. Heitkamp" <heitkamp@ameritech.net> wrote:
> >> I've tried some newer kernels. Still having problems with the echo 3G.
> >> This is kernel version:
> >> 2.6.32.13. The above patches posted to the linux kernel list seemed to
> >> get rid of the crashes, but evidently did not go into the main kernel tree.
> >>
> > Indeed. I've just checked 2.6.33 and the patch isn't there. It's in 2.6.34.
> >
> > If you need 2.6.32.13 you can apply the above patch to the kernel tree or
> > download ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.23.tar.bz2,
> > otherwise just use the latest kernel.
> >
> I tried 2.6.34. I have jack 1.9..5 installed. I was able to use
> rhythmbox to play mp3s. I could not use the echomixer app. It complained
> about a channels mismatch.
I'm running 2.6.34 now. Both a very old version of echomixer (2005!) and
the latest version I just compiled from alsa-tools-1.0.23 work fine with my
Gina3G. Please quote the error message.
> My goal is to be able to plug in a MIDI keyboard, or USB guitar
> interface and play along with songs etc.
>
> I plugged in a MIDI keyboard, "/proc/asound/cards" showed the keyboard
> was recognized. The keyboard has a USB and MIDI interface.
> I am not sure if they both work at the same time. I had the MIDI cable
> plugged into the Gina3G, but I could not tell if the keyboard was
> recognized.
> I compiled csound5. When I engaged it the system immediately froze and
> started spitting out:
> [...]
Ok, I compiled csound, but I don't know how to use it. How can I reproduce
the problem ?
--
Giuliano.
next prev parent reply other threads:[~2010-06-02 22:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 14:21 Crash 2.6.32.x, Echo 3G, Alsa, SCSI Frederick V Heitkamp
2010-02-02 15:30 ` [alsa-devel] " Clemens Ladisch
2010-02-02 16:02 ` Giuliano Pochini
2010-02-02 22:09 ` Giuliano Pochini
2010-02-03 2:53 ` Frederick V Heitkamp
2010-05-31 19:05 ` F. Heitkamp
2010-05-31 20:59 ` Giuliano Pochini
2010-06-01 5:37 ` Takashi Iwai
2010-06-01 12:25 ` [Alsa-user] " F. Heitkamp
2010-06-02 22:08 ` Giuliano Pochini [this message]
2010-06-17 12:11 ` F. Heitkamp
2010-06-18 11:55 ` Giuliano Pochini
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=20100603000828.04af4bdc@Jay \
--to=pochini@shiny.it \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=heitkamp@ameritech.net \
--cc=linux-audio-user@lists.linuxaudio.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).