From: "Ismail Dönmez" <ismail@pardus.org.tr>
To: "Michael S. Tsirkin" <mst@mellanox.co.il>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-sound@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
PeiSen Hou <pshou@realtek.com.tw>
Subject: Re: No sound in KDE with intel hda since 2.6.20-rc1
Date: Sun, 31 Dec 2006 00:10:14 +0200 [thread overview]
Message-ID: <200612310010.16261.ismail@pardus.org.tr> (raw)
In-Reply-To: <20061230204527.GB4338@mellanox.co.il>
30 Ara 2006 Cts 22:45 tarihinde, Michael S. Tsirkin şunları yazmıştı:
> > > > > > Virtual MIDI Card 1
> > > > >
> > > > > Compile this feature out, I bet things start working again.
> > > >
> > > > Yes, this helped, thanks.
> > > > BTW, is this expected?
> > >
> > > It's a severe "misfeature" in my opinion that caused me problems years
> > > ago. The first soundcard becomes "default", which can probably be
> > > overridden in many different ways.
> > >
> > > However, I really think a hack should be put in to prevent "virtual
> > > MIDI" from ever being in the first slot, it's just a bug asking to
> > > happen.
> >
> > So should we enable Virtual MIDI in kernel config? Since I have it off
> > and aRts have no sound with ALSA backend.
>
> Try updating to latest git - I have
> 7479b1ce5ea41a828002c60739cff37f47b62913 with Virtual MIDI off and ALSA
> seems to work.
>
> BTW, Amarok has an Engine dialog where you can easily switch between
> backends which is good for testing.
Still no sound with latest git. But Amarok with ALSA backend works fine. Maybe
some other problem with aRts. Not sure yet but this is surely a new breakage.
Regards,
ismail
--
2 + 2 = 5 for very large values of 2
next prev parent reply other threads:[~2006-12-30 22:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-29 6:25 No sound in KDE with intel hda since 2.6.20-rc1 Michael S. Tsirkin
2006-12-29 7:18 ` Michael S. Tsirkin
2006-12-29 17:06 ` Benoît Rouits
2006-12-30 17:47 ` Michael S. Tsirkin
2006-12-29 22:23 ` Ismail Dönmez
2006-12-30 18:44 ` Alistair John Strachan
2006-12-30 18:46 ` Michael S. Tsirkin
2006-12-30 19:11 ` Michael S. Tsirkin
2006-12-30 19:19 ` Alistair John Strachan
2006-12-30 20:27 ` Ismail Dönmez
2006-12-30 20:45 ` Michael S. Tsirkin
2006-12-30 22:10 ` Ismail Dönmez [this message]
2007-01-02 22:11 ` Lee Revell
2006-12-30 18:49 ` Michael S. Tsirkin
[not found] <1167501651.14690.10.camel@chimay>
2006-12-30 18:27 ` Michael S. Tsirkin
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=200612310010.16261.ismail@pardus.org.tr \
--to=ismail@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mst@mellanox.co.il \
--cc=pshou@realtek.com.tw \
--cc=s0348365@sms.ed.ac.uk \
--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