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
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
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
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
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
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:
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
Thank you Clemens for your fast reply.
Sorry for the weird remark regarding /var/log/messages. To clarify: I was *not* able to find related errors.
One thing I have seen while watching the data received by amidi with the -d option as well as with the other tools was, that the data stream
Sorry for the double post, but the first try is barely readly because of html
tags... :(
Thank you Clemens for your fast reply.
Sorry for the weird remark regarding /var/log/messages. To clarify: I was *not*
able to find related errors.
One thing I have seen while watching the data received
Your advice was perfect ... it is pretty much embarrassing, but yeah,
changing to another USB port helped :-)
Did try that before, but just had catched the only other USB port of the
machine that obviously has problems, too. All other USB ports are
working fine - as I know now ... ;-)
So, thanks
Hello,
I am running openSUSE 12.2, 64bit (Kernel 3.4.33-2.24-desktop). ALSA version is
1.0.26 according to YAST, but alsamixer reports 1.0.25.
Recently I encountered a problem with receiving large amounts of sysex data.
The sysex data is sent from an effects processor called Fractal Audio
Received a message of the firmware developer just today. According to
his note a new firmware is currently under development which should
resolve the issue. I consider this as good news, even if a release date
has not been announced,
No, unfortunately not yet.
But I will try to contact the developer again in the coming days and
will report back if I get some positive feedback.
--
Live Security Virtual Conference
Exclusive live event will cover all
Want to give a short feedback for other user waiting for a solution.
Thanks to Daniel the problem is solved now by the following patch:
diff --git a/sound/usb/clock.c b/sound/usb/clock.c
index 379baad..b05111d 100644
--- a/sound/usb/clock.c
+++ b/sound/usb/clock.c
@@ -255,6 +255,13 @@ static int
Hi Daniel,
thanks a lot for your reply.
Sorry for catching up so late. Is this issue solved already?
On 28.02.2012 00:43, Joachim Gahl wrote:
I would like to ask for some help with an USB audio class 2 device.
[...]
I am running openSUSE 11.4, 64bit (Kernel 2.6.37-0.11 desktop). ALSA
17 matches
Mail list logo
