Comment 43 for bug 27833

Revision history for this message
carrasclin (fontanet9) wrote :

The message "can't modify CPUCS: Broken pipe" means that the device you intend to load the firmware does not accept it because it is incompatible.
I can reproduce it on my system:
When I issue lsusb with a USB sound card connetcted I get the following:
"remy@d4700:~$ su
Password:
d4700:/home/remy# lsusb
Bus 005 Device 003: ID 067b:2506 Prolific Technology, Inc.
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 004: ID 0d8c:0006 C-Media Electronics, Inc.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000"

so a C-Media's chip USB sound card is connected to Bus 002 Device 004

and then if I issue a stupid command attempting to load some MidiSport firmware to it:

"d4700:/home/remy# fxload -I /usr/share/usb/maudio/MidiSport8x8-2.10.ihx -D /dev/bus/usb/002/004"
then I get exactly:
"can't modify CPUCS: Broken pipe
d4700:/home/remy#"

After having taken a look at M-Audio's home page I see that the new versions of Oxygen keyborards such as 'Oxygen 8 v2 - 25-Key USB MIDI Controller' it says that are 'USB class-compliant'. That means that actually it does not need any driver at all. USB class-compliant devices are supposed --at least in theory-- that are supported with a generic set of drivers incorporated on the operating system. In my case I have a 'generic-no-brand' USB MIDI interface which it seems a replica of M-Audio Midi-Uno and it is automaticaly recognized on qjack control, same happens with the forementioned USB sound card which uses a CM106-L C-Media chip.

So my suggestion is to try to use it without trying to load any firmware and start qjack control and wait a minute or so and look out on the pop-up box after clicking on button 'Connect', tab MIDI, and click on 'Refresh'.

If the Oxygen is the original version 8 in principle the MidiSportKS.ihx firmware should work. But the "can't modify CPUCS: Broken pipe" message what in fact tells us is that inside the keyboard there is something which is not the original interface of first versions of that keyboard series. With the 'USB class-compliant" Oxygen 8 v2 the firmware loading with fxload certainly shall not work, and then the only hope is that it will be automatically recognized by the generic 'class-compliant' drivers provided with ALSA and the kernel.