With the latest firmware from the Hardy (8.04) repo it works OK without
modifications on the scripts or any need in using the manual uploading
script but the "/etc/fstab" configuration file needs to be fixed.
To do this you can type on a terminal:
echo "/dev/bus/usb//proc/bus/usbusbfs
I've experienced the same issue and also Alexander Jones' fix works for
me too.
A workaround based on savagex post wrote on 2008-06-05 consisits on
openning "System>Preferences>Sessions" and on "Startup Programs" tab add
an entry like "Name: Trash applet starter; Command: /usr/lib/gnome-
applets/t
To Forest Bond.
I see in your attached debdiff something like...
# MidiSport 2x2
-ACTION=="add", SUBSYSTEM=="usb_device", ATTRS{idVendor}=="0763",
ATTRS{idProduct}=="1001", RUN+="@fxload@ -s @firmwaredir@/MidiSportLoader.ihx
-I @firmwaredir@/MidiSport2x2.ihx"
+ACTION=="add", SUBSYSTEM=="usb_d
Just to say I had the same problem and the same solution pointed before.
In my case it is a Keystation.
Adding "$env{DEVNAME}" as stated before...
...and the keyboard starts nice and is fully accessible with qjackd control and
Rosegarden.
I've been for about two weeks crazy about. I conjectured
*** This bug is a duplicate of bug 27833 ***
https://bugs.launchpad.net/bugs/27833
On the last days it seems that the new midisport firmware package now installs
under /usr/share/usb/maudio/...
The "-I" switch of fxload it is an upper case letter 'ei' _not_ a lower case
'L', since with some
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:
"[EMAIL PROTECTED]:~$ su
Password:
d4700:/hom
I'am affraid it is so.
But in the previous post I've sayed to look at the qjack control tab marked as
MIDI, instead you should look also at the tab marked ALSA and see after
clicking on 'refresh' button if it shows some MIDI device appart from 'Midi
Through'. If the answer is yes probably it is
Public bug reported:
Binary package hint: module-assistant
On Gutsy after a succesfull and clean install and after installing all
build dependencies, appropriate kernel headers and all repositories
enabled (in fact I have a local mirrored repo with main, restricted,
universe and multiverse just i
I'am wondering if this issue has something to do with this other bug
report I've posted recently https://bugs.launchpad.net/ubuntu/+source
/module-assistant/+bug/178789
By the way I've returned to Official Debian Etch and all this sorts of
problems have gone away. I know this is no the place to ge
*** This bug is a duplicate of bug 27833 ***
https://bugs.launchpad.net/bugs/27833
I've only tested with a live CD and I am not sure if this is an
idiosincrasy of the live CD and with a regular hard drive install things
work different. (I am intending to test it with other computer since
that
The problem seems due to that the usbfs is not mounted on /proc/bus/usb/
but only on /dev/bus/usb. So the udev scripts that use the /proc/bus/usb
to upload the firmwares to the attached devices fail to do so since it
do not found the respective nodes.
I have found a workaround that I've posted on
It seem that the way as the udev rules are managed in Ubuntu have been
chaged, interestengly making it more compatible with the original
Midisport firmware package and with Debian itself. And thats the reason
of the latest problems.
The fix consists of two steps.
First of all the usbfs must be pro
12 matches
Mail list logo
