On Thu, Apr 11, 2013 at 12:20:39 -0700, chris hermansen wrote:
> First time: I plugged the Schiit USB into the laptop before booting
> the laptop (only one altset for output, two for input for stream0)
>
> Second time: I hot-plugged the Schiit USB into the already running
> laptop (two altsets for
Torstein, list;
On Thu, Apr 11, 2013 at 2:02 AM, Torstein Hegge wrote:
[...]
>> ie no S32_LE altset on either playback or capture. Switching the
>> Schiit back to USB does not change this.
>
> The USB or S/PDIF input setting on the Schiit shouldn't affect the
> behavior of the USB interface, it
On Wed, Apr 10, 2013 at 08:46:04 -0700, chris hermansen wrote:
> Torstein and list:
>
> Wait! this is still weird. Please see at bottom...
>
> On Wed, Apr 10, 2013 at 8:31 AM, chris hermansen
> wrote:
> > Torstein, list:
> >
> > On Wed, Apr 10, 2013 at 2:32 AM, Torstein Hegge wrote:
> >> Wha
Torstein and list:
Wait! this is still weird. Please see at bottom...
On Wed, Apr 10, 2013 at 8:31 AM, chris hermansen wrote:
> Torstein, list:
>
> On Wed, Apr 10, 2013 at 2:32 AM, Torstein Hegge wrote:
> [...]
>> What does dmesg / /var/log/kern.log say when you plug in the device with
>> the
Torstein, list:
On Wed, Apr 10, 2013 at 2:32 AM, Torstein Hegge wrote:
[...]
> What does dmesg / /var/log/kern.log say when you plug in the device with
> the v3.9-rc6 kernel?
Hmm things are getting interesting. Yesterday, when I had the problem
with missing altset 2, as far as I can remember, I
On Tue, Apr 09, 2013 at 15:25:15 -0700, chris hermansen wrote:
> Torstein, list;
>
> On Tue, Apr 9, 2013 at 12:34 AM, Torstein Hegge wrote:
> > On Mon, Apr 08, 2013 at 18:28:30 -0700, chris hermansen wrote:
> [..]
> >> Hmm that was a bit of a slip of the brain. Anyway, I'm actually back
> >> in
Torstein, list;
On Tue, Apr 9, 2013 at 12:34 AM, Torstein Hegge wrote:
> On Mon, Apr 08, 2013 at 18:28:30 -0700, chris hermansen wrote:
[..]
>> Hmm that was a bit of a slip of the brain. Anyway, I'm actually back
>> in the same general vicinity as the Bifrost and can do some more
>> testing.
>>
On Mon, Apr 08, 2013 at 18:28:30 -0700, chris hermansen wrote:
> Torstein and list;
>
> On Mon, Mar 18, 2013 at 12:56 PM, chris hermansen
> wrote:
> > Torstein and list;
> >
> > On Mar 18, 2013 12:52 PM, "Torstein Hegge" wrote:
> >>
> >> On Sun, Mar 17, 2013 at 07:36:01PM -0700, chris hermansen
Torstein and list;
On Mon, Mar 18, 2013 at 12:56 PM, chris hermansen wrote:
> Torstein and list;
>
> On Mar 18, 2013 12:52 PM, "Torstein Hegge" wrote:
>>
>> On Sun, Mar 17, 2013 at 07:36:01PM -0700, chris hermansen wrote:
>> > The kernel's compiled and I'm testing. Cutting to the chase, I can't
Torstein and list;
On Mar 18, 2013 12:52 PM, "Torstein Hegge" wrote:
>
> On Sun, Mar 17, 2013 at 07:36:01PM -0700, chris hermansen wrote:
> > The kernel's compiled and I'm testing. Cutting to the chase, I can't
> > seem to get it to misbehave any more.
>
> I'm a bit worried that you didn't get a
On Sun, Mar 17, 2013 at 07:36:01PM -0700, chris hermansen wrote:
> The kernel's compiled and I'm testing. Cutting to the chase, I can't
> seem to get it to misbehave any more.
I'm a bit worried that you didn't get a single warning about runtime
rate being different from current rate, if this last
Torstein and list;
On Sun, Mar 17, 2013 at 5:31 AM, Torstein Hegge wrote:
> On Thu, Mar 14, 2013 at 10:13:17AM +0100, Torstein Hegge wrote:
>> If we can find some other explanation for the 'cannot get freq' and the
>> large negative rate you saw earlier, it might help to replace the
>> if (cur_
On Thu, Mar 14, 2013 at 10:13:17AM +0100, Torstein Hegge wrote:
> If we can find some other explanation for the 'cannot get freq' and the
> large negative rate you saw earlier, it might help to replace the
> if (cur_rate != prev_rate) {
> with
> if (rate != prev_rate) {
> so that we do the rese
On Wed, Mar 13, 2013 at 09:00:29PM -0700, chris hermansen wrote:
> Looking at the messages, I find it odd that the reset doesn't happen
> cf. we just jump to the complaint about the rates not matching.
>
> Mar 13 20:33:51 temuko kernel: [ 372.014273] current rate 96000 is
> different from the run
Torstein and list;
On Tue, Mar 12, 2013 at 1:48 PM, Torstein Hegge wrote:
> On Tue, Mar 12, 2013 at 07:59:52AM -0700, chris hermansen wrote:
>> Mar 12 07:13:34 temuko kernel: [ 1221.640038] usb 1-3: new high-speed
>> USB device number 2 using ehci-pci
>> Mar 12 07:13:34 temuko kernel: [ 1221.7979
On Tue, Mar 12, 2013 at 07:59:52AM -0700, chris hermansen wrote:
> Mar 12 07:13:34 temuko kernel: [ 1221.640038] usb 1-3: new high-speed
> USB device number 2 using ehci-pci
> Mar 12 07:13:34 temuko kernel: [ 1221.797930] usb 1-3: config 1
> interface 8 altsetting 0 bulk endpoint 0x1 has invalid ma
Torstein and list;
Sorry about the delay with this, life and the garden and what-not kind
of caught up with me over the last few days...
On Sat, Mar 9, 2013 at 12:35 PM, Torstein Hegge wrote:
[last experiment's evidence deleted]
>
> According to lsusb -v from
> https://gist.github.com/storrgie
On Sat, Mar 09, 2013 at 09:01:48AM -0800, chris hermansen wrote:
> I plugged in the Schiit, then with 'sudo aplay -vD
> plughw:CARD=Interface,DEV=0' I played:
>
> 1. a 44.1/16 for ~ 10 seconds - it sounded fine - so I interrupted it
> 2. a 96/24 - it was staticky / noisy, even though the plughw sl
Torstein and list;
On Sat, Mar 9, 2013 at 12:00 AM, Torstein Hegge wrote:
> On Fri, Mar 08, 2013 at 08:23:54AM -0800, chris hermansen wrote:
>> As to the outcome, I have two.
(blush) (blush) (blush)
What an idiot I am! A new kernel snuck into the updates while I
wasn't paying attention and so
On Fri, Mar 08, 2013 at 08:23:54AM -0800, chris hermansen wrote:
> As to the outcome, I have two.
>
> The first is that the problem seems worse now - I get more songs going
> into staticky noisy mode.
>
> The second is the attached excerpt of the kernel log file.
>
> Mar 8 08:04:39 temuko kerne
Torstein and list;
On Fri, Mar 8, 2013 at 8:43 AM, Torstein Hegge wrote:
> On Fri, Mar 08, 2013 at 08:23:54AM -0800, chris hermansen wrote:
>> As to the outcome, I have two.
>>
>> The first is that the problem seems worse now - I get more songs going
>> into staticky noisy mode.
>>
>> The second
On Fri, Mar 08, 2013 at 08:23:54AM -0800, chris hermansen wrote:
> As to the outcome, I have two.
>
> The first is that the problem seems worse now - I get more songs going
> into staticky noisy mode.
>
> The second is the attached excerpt of the kernel log file.
That looks like the log from plu
Hello Torstein and list;
On Thu, Mar 7, 2013 at 12:30 PM, Torstein Hegge wrote:
> On Wed, Mar 06, 2013 at 01:15:06PM -0800, chris hermansen wrote:
>> Does this help?
>
> Kind of, but it doesn't bring me much closer to understanding why this
> happens.
> It would be nice if I could reproduce this
On Wed, Mar 06, 2013 at 01:15:06PM -0800, chris hermansen wrote:
> Does this help?
Kind of, but it doesn't bring me much closer to understanding why this happens.
It would be nice if I could reproduce this.
This might not be relevant at all, but could you try to do this change on top
of v3 of the
Torstein and list;
On Wed, Mar 6, 2013 at 12:23 PM, Torstein Hegge wrote:
> On Wed, Mar 06, 2013 at 09:41:02AM -0800, chris hermansen wrote:
>> So I have now tried the v2 patch.
>>
>> It seems to work mostly. I can't create a problem with aplay using a
>> device of plughw:CARD=Interface,DEV=0 sw
On Wed, Mar 06, 2013 at 09:41:02AM -0800, chris hermansen wrote:
> So I have now tried the v2 patch.
>
> It seems to work mostly. I can't create a problem with aplay using a
> device of plughw:CARD=Interface,DEV=0 switching between 44.1/16 and
> 96/24 tracks.
Good.
> Using gmusicbrowser with a
Torstein, list:
On Tue, Mar 5, 2013 at 11:18 PM, Torstein Hegge wrote:
> On Tue, Mar 05, 2013 at 03:44:04PM -0800, chris hermansen wrote:
>> On Tue, Mar 5, 2013 at 3:03 PM, chris hermansen
>> wrote:
>> > On Mon, Mar 4, 2013 at 6:44 PM, chris hermansen
>> > wrote:
>> >> On Mon, Mar 4, 2013 at
On Tue, Mar 05, 2013 at 03:44:04PM -0800, chris hermansen wrote:
> On Tue, Mar 5, 2013 at 3:03 PM, chris hermansen wrote:
> > On Mon, Mar 4, 2013 at 6:44 PM, chris hermansen
> > wrote:
> >> On Mon, Mar 4, 2013 at 2:44 PM, Torstein Hegge wrote:
> >>> On Mon, Mar 04, 2013 at 11:30:03AM -0800, chr
Torstein and list;
On Tue, Mar 5, 2013 at 3:03 PM, chris hermansen wrote:
>
> Torsten and list;
>
>
> On Mon, Mar 4, 2013 at 6:44 PM, chris hermansen wrote:
>>
>> Torstein and list;
>>
>>
>> On Mon, Mar 4, 2013 at 2:44 PM, Torstein Hegge wrote:
>>>
>>> On Mon, Mar 04, 2013 at 11:30:03AM -0800,
Torsten and list;
On Mon, Mar 4, 2013 at 6:44 PM, chris hermansen wrote:
> Torstein and list;
>
>
> On Mon, Mar 4, 2013 at 2:44 PM, Torstein Hegge wrote:
>
>> On Mon, Mar 04, 2013 at 11:30:03AM -0800, chris hermansen wrote:
>> > I would be happy to test this on my Schiit Bifrost as well. I'm
>
Torstein and list;
On Mon, Mar 4, 2013 at 2:44 PM, Torstein Hegge wrote:
> On Mon, Mar 04, 2013 at 11:30:03AM -0800, chris hermansen wrote:
> > I would be happy to test this on my Schiit Bifrost as well. I'm
> currently
> > using the TOSLINK connection but it would be easy peasy to hook up a
>
On Mon, Mar 04, 2013 at 11:30:03AM -0800, chris hermansen wrote:
> I would be happy to test this on my Schiit Bifrost as well. I'm currently
> using the TOSLINK connection but it would be easy peasy to hook up a laptop
> via the USB.
If you could test the patch i just posted to alsa-devel [1], th
Gentlemen;
On Sat, Mar 2, 2013 at 4:21 AM, Daniel Mack wrote:
> Hi Torstein,
>
> (+ alsa-devel)
>
> On 02.03.2013 12:09, Torstein Hegge wrote:
> > Daniel Mack gmail.com> writes:
> This is a known bug, also most probably flaw in the CMEDIA chip,
> and not yet properly worked around in
Hi Torstein,
(+ alsa-devel)
On 02.03.2013 12:09, Torstein Hegge wrote:
> Daniel Mack gmail.com> writes:
This is a known bug, also most probably flaw in the CMEDIA chip,
and not yet properly worked around in the snd-usb driver. If you
want to investigate, have a look at the feedb
Daniel Mack gmail.com> writes:
> >> This is a known bug, also most probably flaw in the CMEDIA chip,
> >> and not yet properly worked around in the snd-usb driver. If you
> >> want to investigate, have a look at the feedback format
> >> autodetection code in sound/usb/endpoint.c.
> >
> > Thank
> > * each
> > time playback format changes (16/44 to 24/96 and back) the sound is
> > totally scrambled, but /proc/asound/card2/pcm0p/sub0/hw_params shows
> > the correct playback format. Stop/start playback solves the problem.
>
> This is a known bug, also most probably flaw in the CMEDIA chip,
> I've read a quite long discussion here about this USB Audio 2.0 chip.
> Apparently there have been problems when switching sample rates.
> Now I have bought a cheap USB to S/PDIF interface with this chip (search for
> "CM6631 USB" at www.aliexpress.com) and I wonder if it is better supported
>
On 12.12.2012 22:20, Thorsten Mühlfelder wrote:
>>> Problems left: * There is a blob at the beginning of playback
>>
>> This is most probably a bug in the hardware chain somewhere. Can
>> you exclude the possibilty that this plop is produced by the
>> receiving side and occurs every time the lin
> > Problems left:
> > * There is a blob at the beginning of playback
>
> This is most probably a bug in the hardware chain somewhere. Can you
> exclude the possibilty that this plop is produced by the receiving side
> and occurs every time the link was lost? You can try that by re-plugging
> the
On 12.12.2012 00:42, Thorsten Mühlfelder wrote:
>>> The system is running Slackware 14.0 with kernel 3.2.29 (Alsa
>>> 1.0.24).
>>
>> This kernel is *way* too old. Please try a 3.7 which has just been
>> released.
>
> OK, I've updated to 3.7.0.
>
> Now lsusb.py shows the device in high speed: 3-3
> > The system is running Slackware 14.0 with
> > kernel 3.2.29 (Alsa 1.0.24).
>
> This kernel is *way* too old. Please try a 3.7 which has just been released.
OK, I've updated to 3.7.0.
Now lsusb.py shows the device in high speed:
3-30d8c:0309 ef 2.00 480MBit/s 100mA 3IFs (CMEDIA
> Try to work with "aplay -v" and you should get immediate feedback
> without having to check files etc. If I recall "aplay -v -D hw:2,0"
> with a 96/24 file should tell you that 24 bits is not supported and
> suggest some others that are.
Yes, aplay tells me:
Available formats:
- S16_LE
- S32_LE
Daniel, Thorsten, list:
On Tue, Dec 11, 2012 at 4:51 PM, Daniel Mack wrote:
> On 11.12.2012 20:40, Thorsten Mühlfelder wrote:
>> depth 32 bit as suggested). The system is running Slackware 14.0 with
>> kernel 3.2.29 (Alsa 1.0.24).
>
> This kernel is *way* too old. Please try a 3.7 which has just
Thorsten, list:
On Tue, Dec 11, 2012 at 4:40 PM, Thorsten Mühlfelder
wrote:
>> Yes, the discussion has ended without real solution. So this is why I've
>> asked here again.
>> As soon as the China device arrives I can test if it has the same issues
>> like your Schiit.
>
> OK, device has arrive
On 11.12.2012 20:40, Thorsten Mühlfelder wrote:
>> Yes, the discussion has ended without real solution. So this is why I've
>> asked here again.
>> As soon as the China device arrives I can test if it has the same issues
>> like your Schiit.
>
> OK, device has arrived:
> lsusb:
> Bus 007 Device
> Yes, the discussion has ended without real solution. So this is why I've
> asked here again.
> As soon as the China device arrives I can test if it has the same issues like
> your Schiit.
OK, device has arrived:
lsusb:
Bus 007 Device 003: ID 0d8c:0309 C-Media Electronics, Inc.
lsusb.py:
7-3
Thorsten and list;
>> The second is that "hw" does not handle the 24 bit word length, at
>> least in this context, necessitating the use of "plughw" to get to 32
>> bits.
>
> Thanks for the information. So I need something like this?
> pcm.usbplug {
> type plug
> slave {
>
> I guess I was the last person discussing the use of this chip, in the
> Schiit Bifrost
> http://schiit.com/cart/index.php?main_page=product_info&cPath=0&products_id=7
Yes, it was your discussion about the Schiit.
> The second is that "hw" does not handle the 24 bit word length, at
> least in t
Thorsten and list;
On Wed, Nov 28, 2012 at 7:06 AM, Thorsten Mühlfelder
wrote:
> Hi,
>
> I've read a quite long discussion here about this USB Audio 2.0 chip.
> Apparently there have been problems when switching sample rates.
> Now I have bought a cheap USB to S/PDIF interface with this chip (se
Hi,
I've read a quite long discussion here about this USB Audio 2.0 chip.
Apparently there have been problems when switching sample rates.
Now I have bought a cheap USB to S/PDIF interface with this chip (search for
"CM6631 USB" at www.aliexpress.com) and I wonder if it is better supported now.
SZÉKELYI Szabolcs wrote:
>> I didn't try actually using surround sound, so don't know about that.
>> Although 5-channel output does work.
>
> What's the difference between 5-channel and surround (apart from 5 vs. 6
> channels)?
Maybe there's none :)
I just think there were some problems mentioned
Thanks for following up on this.
HoverHell gmail.com> writes:
> Well, I get sound of it, pretty nice stereo quality. But for
> everything else...
> I had to use alsa's softvol since alsa driver gets no mixers from it.
> No luck as of yet getting volume handle or IR remote working (see
> thread in
SZÉKELYI Szabolcs wrote:
> any news on this? I'm planning to buy one, but still don't know if it will
> work
> or not. It's a pity that the original poster provided no info either on the
> results of the test, I mean if he managed to get any sound out of it, stereo
> or
> surround. I guess yes si
Hi,
HoverHell gmail.com> writes:
>
> Well, I have the device now...
>
> HoverHell wrote:
> > At alsa-project in by-vendor matrix I don't see any appropriate entry
> > for this device.
>
> That's the question 1, still unanswered.
> E.g. is there something for this device or it should be added?
Yet another related question: does absence of mixer controls in this
(snd-usb-audio) device means it has none at all or it might be the
driver's problem?
--
--HoverHell (jabber/GTalk here, PGP ... available).
--
Cry
Well, I have the device now...
HoverHell wrote:
> At alsa-project in by-vendor matrix I don't see any appropriate entry
> for this device.
That's the question 1, still unanswered.
E.g. is there something for this device or it should be added?
In lsusb it is '041e:3042 Creative Technology, Ltd'
Q
Sergei Steshenko wrote:
> On Mon, 13 Apr 2009 17:18:28 +0500
> HoverHell wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hello.
>>
>> The primary question is: how much this (subj.) device is supported in ALSA?
>> I have some information that it should work, but I don't know wha
On Mon, 13 Apr 2009 17:18:28 +0500
HoverHell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello.
>
> The primary question is: how much this (subj.) device is supported in ALSA?
> I have some information that it should work, but I don't know what
> exactly will work, e.g. will it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
The primary question is: how much this (subj.) device is supported in ALSA?
I have some information that it should work, but I don't know what
exactly will work, e.g. will it support 24bit/96khz, and will volume
control handle work or not (I ha
J W wrote:
> I am wondering what is the development state of the emu 1212 (1820)
> drivers for alsa - I know there was some work done a while ago but the
> driver is incomplete. I have stereo playback but no capture
This was my experience as well. I tried (off and on) for six months to
get the
I am wondering what is the development state of the emu 1212 (1820) drivers for
alsa - I know there was some work done a while ago but the driver is
incomplete. I have stereo playback but no capture and I would dearly like to
get ADAT working. Has development been abandoned or if not what is the
I've been trying to fix the audio on my Lenovo n100, model 768 for a while.
I've seen a many suggestions such as patching the ACPI DSDT, adding module
parameters, etc, but so far nothing has worked, except turning off ACPI, which
also disables cpu scaling. I'm using kernel 2.6.20.3 with the 1.0
Hi,
I have got hold of a couple of old Korg 1212 I/O sound cards I would
like to use. I have not been able to run jack reliably so far; I only
got more or less random crashes after anything from a few seconds to
acouple of hours. I tried with various releases of Fedora Core (1, 5
and 6 so far), wi
On Tuesday 27 January 2004 08:25, Ulrich Staudinger wrote:
>i am just one of the readers, but in the last weeks i see more and
> more of these messages:
>
>[EMAIL PROTECTED] wrote:
>>The message cannot be represented in 7-bit ASCII encoding and has
>> been sent as a binary attachment.
>
Listen up f
On Tue, 27 Jan 2004, Ulrich Staudinger wrote:
> i am just one of the readers, but in the last weeks i see more and more
> of these messages:
> [EMAIL PROTECTED] wrote:
>
> >The message cannot be represented in 7-bit ASCII encoding and has been sent as a
> >binary attachment.
Ignore them. It's
i am just one of the readers, but in the last weeks i see more and more
of these messages:
[EMAIL PROTECTED] wrote:
The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.
---
The SF.Net email
The message cannot be represented in 7-bit ASCII encoding and has been sent as a
binary attachment.
message.zip
Description: Binary data
At Wed, 3 Sep 2003 13:34:38 +0200,
Steffen Hein wrote:
>
> > Jack
>
> Nice thing but not (yet) widely supported.
>
> > > > The ALSA driver at least has the dmix plugin, that supports
> > > > multi-playback on any cards, but I think only in stereo.
> > > Channels count is not restricted.
> > Ah,
> Jack
Nice thing but not (yet) widely supported.
> > > The ALSA driver at least has the dmix plugin, that supports
> > > multi-playback on any cards, but I think only in stereo.
> > Channels count is not restricted.
> Ah, good to know.
Wouldn't be an issue anyway since the card is only stereo.
Hallo,
Jaroslav Kysela hat gesagt: // Jaroslav Kysela wrote:
> On Wed, 3 Sep 2003, Frank Barknecht wrote:
>
> > The ALSA driver at least has the dmix plugin, that supports
> > multi-playback on any cards, but I think only in stereo.
>
> Channels count is not restricted.
Ah, good to know.
ciao
On Wed, 3 Sep 2003, Frank Barknecht wrote:
> The ALSA driver at least has the dmix plugin, that supports
> multi-playback on any cards, but I think only in stereo.
Channels count is not restricted.
Jaroslav
-
Jaroslav Kysela <[EMAIL PROTECTED]
Hallo,
Steffen Hein hat gesagt: // Steffen Hein wrote:
> > > Damn. I really need this feature since esd and especially arts are much
> > > to unrelieable and have much too high latency. I've read that the card
> > > does hardware mixing internally with 36bit precision so it would be
> > > really n
> > Damn. I really need this feature since esd and especially arts are much
> > to unrelieable and have much too high latency. I've read that the card
> > does hardware mixing internally with 36bit precision so it would be
> > really nice if the driver would support it.
>
> in this sense, yes, but
At Tue, 2 Sep 2003 14:19:25 +0200,
Steffen Hein wrote:
>
> Am Dienstag, 2. September 2003 09:06 schrieb Jaroslav Kysela:
> > Yes, all I/Os are supported.
>
> Nice to hear :-)
>
> > > hardware-mixing (multiple streams played at once)?
> > Nope.
>
> Damn. I really need this feature since esd and
Am Dienstag, 2. September 2003 09:06 schrieb Jaroslav Kysela:
> Yes, all I/Os are supported.
Nice to hear :-)
> > hardware-mixing (multiple streams played at once)?
> Nope.
Damn. I really need this feature since esd and especially arts are much to
unrelieable and have much too high latency. I'v
I consider buying a Terratec EWX 24/96 soundcard.
It just features chinch connectors for line-in and line-out as well as optical
i/o connectors. It uses the envy24 driver. Does anyone here use this card?
Are both IO-Types (analog and optical) supported? Does the driver do
hardware-mixing (multi
On Tue, 2 Sep 2003, Steffen Hein wrote:
> I consider buying a Terratec EWX 24/96 soundcard.
> It just features chinch connectors for line-in and line-out as well as optical
> i/o connectors. It uses the envy24 driver. Does anyone here use this card?
>
> Are both IO-Types (analog and optical) suppo
Haha! ...
I took a look at that file and it's just and older version of
alsa-driver.
Here is what I was missing in my modules.conf (i.e. module options):
options snd-via82xx index=0 id="VIA"
After I put that in an reloaded the modules everything worked like a
charm with the latest alsa release.
Sorry, you're right. The driver is not on the CD, it's on the Realtek site.
See
http://www.realtek.com.tw/downloads/downloads1-3.aspx?series=8&Software=True.
On Wednesday 08 January 2003 11:39 am, Edward Muller wrote:
> I can't seem to locate that driver on the CD. The only driver I've found
>
I've got both going for me. Perhaps I should try and play with how irqs
are assigned on this machine, which is loaded with add-in pci cards as
well as all the onboard stuff.
On Wed, 2003-01-08 at 16:03, Joachim Blaabjerg wrote:
> On Wednesday 08 January 2003 17:49, Edward Muller wrote:
> > I was j
On Wednesday 08 January 2003 17:49, Edward Muller wrote:
> I was just wondering if anyone is working on getting the sound (a
> via8233/35 chip ... listed as a Realtek AL650 in the manual) on an Asus
> A7V8X Mobo working.
>
> I haven't been able to get it working and CVS (from last night) doesn't
>
I can't seem to locate that driver on the CD. The only driver I've found
for linux on the CD was for the Broadcomm nic.
On Wed, 2003-01-08 at 12:59, Mike Payson wrote:
> On Wednesday 08 January 2003 08:49 am, Edward Muller wrote:
> > I was just wondering if anyone is working on getting the sound (
On Wednesday 08 January 2003 08:49 am, Edward Muller wrote:
> I was just wondering if anyone is working on getting the sound (a
> via8233/35 chip ... listed as a Realtek AL650 in the manual) on an Asus
> A7V8X Mobo working.
>
> I haven't been able to get it working and CVS (from last night) doesn't
I was just wondering if anyone is working on getting the sound (a
via8233/35 chip ... listed as a Realtek AL650 in the manual) on an Asus
A7V8X Mobo working.
I haven't been able to get it working and CVS (from last night) doesn't
work either.
--
Edward Muller
Interlix - President
Web Hosting -
Hi Martin,
At Mon, 4 Nov 2002 10:58:53 +0100,
Martin Fiedler wrote:
>
> Hello,
>
> Am Montag, 4. November 2002 09:37 schrieb Takashi Iwai:
> > the spdif on this chip is not supported (perhaps) yet.
> > it wouldn't be too difficult to support it, but so far, we had no
> > experimental environment
Hello,
Am Montag, 4. November 2002 09:37 schrieb Takashi Iwai:
> the spdif on this chip is not supported (perhaps) yet.
> it wouldn't be too difficult to support it, but so far, we had no
> experimental environment.
> otherwise via8235 should be almost identical with via8233.
I think I'll buy thi
At Sun, 3 Nov 2002 23:30:27 +0100,
Martin Fiedler wrote:
>
> Hello there,
>
> i'm going to buy a board with onboard via8235 sound. Anyone got experience
> with this chipset and ALSA? I couldn't find this one in the soundcard matrix,
> the latest via chipset thats supported seems to be via8233a
Hello there,
i'm going to buy a board with onboard via8235 sound. Anyone got experience
with this chipset and ALSA? I couldn't find this one in the soundcard matrix,
the latest via chipset thats supported seems to be via8233a (which is found
on KT333 boards). Will I run into trouble with ALSA b
Joachim Backhaus hat gesagt: // Joachim Backhaus wrote:
> I'm asking that because I want to buy
> a Midiman Midisport 8x8 Interface in
> addition to my Midiman Winman 2x2 and
> sell my Portman 2x4.
>
> Can anybody recommend that?
>
> I have also subscribed to the Linux Audio Dev
> and the Linu
Hi,
I'm new to this list and I'm currently in the
process of changing from Windows 98 SE
to Linux.
I'm a bit confused as the ALSA soundcard
matrix says that the ALSA drivers for
the Midiman MIDI Interfaces (Midisport & Portman)
are "undetermined".
Does that mean they are under development or
tha
90 matches
Mail list logo
