Just want to report back: Problem is solved! :D
About two weeks ago I updated to kernel 3.17.4 (openSUSE 13.1 64bit). I
am also using recent versions of ALSA 1.0.28 (from the openSUSE repo
"multimedia:/libs") and pulseaudio 5.0 (from the openSUSE repo
"home:/jejb1:/Tumbleweed") . Since then the is
Today I ran an openSUSE 13.1 KDE live DVD (kernel 3.11.6, 64 bit) in
virtualbox. The warnings I reported for my host system did not occur there.
More importantly, the problem that the sound system does not react
properly to unplugging the Axe-Fx II stays the same. As mentioned before
the Axe-Fx II
After testing a kernel with CONFIG_SOUND_OSS=n I compiled and tried out
another kernel with CONFIG_SOUND_OSS_CORE set to "n". But the known
warnings appeared again.
As the warnings originate from .../fs/sysfs/group.c, could it be a sysfs
problem?
Joachim
Am 12.06.2014 11:44, schrieb Daniel Mack:
I compiled a 3.15 kernel with CONFIG_SOUND=n and tested it right now.
Unfortunately all warnings stayed the same (not only for midi3). Maybe
instead of CONFIG_SOUND the option
CONFIG_SOUND_OSS_CORE (which is set to "y" now) should be set to "n"?
Joachim
Am 12.06.2014 11:44, schrieb Daniel Mack:
>
On 06/12/2014 12:14 AM, je...@web.de wrote:
> I just updated to kernel 3.15.0. Expectedly as with RC8 there is no change.
>
> Daniel, what makes you think, the 'midi3' node causes the warning? The
> warning appears not only for 'midi3' (and 'dmmidi3'), but also
> 'pcmC3D0p', 'pcmC3D0c' and 'contro
I just updated to kernel 3.15.0. Expectedly as with RC8 there is no change.
Daniel, what makes you think, the 'midi3' node causes the warning? The
warning appears not only for 'midi3' (and 'dmmidi3'), but also
'pcmC3D0p', 'pcmC3D0c' and 'control3' nodes.
Joachim
Am 07.06.2014 19:27, schrieb Dani
There is usually only a Roland UM-1G as an additional midi device. The
Edirol UA-5 I mentioned earlier has midi, too, but is typically powered
off/not connected. When I checked with UM-1G and UA-5 disconnected it
made no difference. Unplugging the Axe-Fx II led to the error message again.
The soun
On 06/07/2014 02:40 PM, je...@web.de wrote:
> I chose to try the 3.15RC8 kernel first but unfortunately this did not
> resolve the issue. KMix still did not recognize the
> deisconnect/reconnect. The error messages also did not change
> significantly as far as I can see:
...
> CONFIG_CHR_DEV_OSST
Thanks Daniel and Takashi for your suggestions,
I chose to try the 3.15RC8 kernel first but unfortunately this did not
resolve the issue. KMix still did not recognize the
deisconnect/reconnect. The error messages also did not change
significantly as far as I can see:
2014-06-05T21:34:24.981427+02
At Thu, 05 Jun 2014 09:31:25 +0200,
Daniel Mack wrote:
>
> On 05/18/2014 11:43 PM, je...@web.de wrote:
> > I have a USB audio class 2 device which is an effects processor called
> > Fractal Audio Systems Axe-Fx II. It has the ability to work as a midi
> > and also as an audio interface (capture an
On 05/18/2014 11:43 PM, je...@web.de wrote:
> I have a USB audio class 2 device which is an effects processor called
> Fractal Audio Systems Axe-Fx II. It has the ability to work as a midi
> and also as an audio interface (capture and playback).
>
> The device seems to register well, audio and mid
Meanwhile I have checked with an old Edirol UA-5 and it appears and
disappears in KMix just as expected. Weird.
Does anybody have an idea what causes the disconnect / reconnect issue
with the Axe-Fx II?
Thanks again in advance for any hints and help.
Joachim
---
Hi,
I have a USB audio class 2 device which is an effects processor called
Fractal Audio Systems Axe-Fx II. It has the ability to work as a midi
and also as an audio interface (capture and playback).
The device seems to register well, audio and midi functions work. When
plugged in /var/log/messag
13 matches
Mail list logo
