[Bug 27833] Re: Add support for MidiSport USB midi interfaces
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/usbusbfsdefaults0 0|sudo tee -a /etc/fstab echo argument _needs_ quotes and pay attention at spaces. or edit it with Alt+F2 gksudo gedit Open /etc/fstab and add a line with /dev/bus/usb//proc/bus/usbusbfsdefaults00 without quotes and paying attention at spaces. It needs reboot or sudo mount dev/bus/usb. This is because the udev rules script uses device nodes mounted under /proc/bus/usb to upload firmware and Hardy only mounts the device nodes under /dev/bus/usb. Former versions of Ubuntu and Debian mounted it on both. -- Add support for MidiSport USB midi interfaces https://bugs.launchpad.net/bugs/27833 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211604] Re: trash icon disappears in panel
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 SystemPreferencesSessions and on Startup Programs tab add an entry like Name: Trash applet starter; Command: /usr/lib/gnome- applets/trashapplet. Now without Alex's fix also the trash bin applet becomes visible after next session login. -- trash icon disappears in panel https://bugs.launchpad.net/bugs/211604 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 27833] Re: Add support for MidiSport USB midi interfaces
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 the Oxygen device, even if it is namend with an other name. In that case probably it will be recognaized and work with usual MIDI software such as Rosegarden and soft synths like ZynAddSubFX. If it is not recognized in any way on qjack control, then the only hope is to wait for newer versions of ALSA that will incorporate generic 'class-compliant' driver support for the Oxygen 8 v.2. Since it is a popular brand there is hope that this could happen. That is the usual way that goes with Linux. The most recent hardware --and the new version 2 of that particular keyboard it is a rather new-- have to wait some time untill is fully supported. Of course there is a workaround to make the keyboard work in the meanwhile: since it has a standard MIDI out port you could use a generic USB MIDI interface of that sort that is usually found on eBay and the like and to interface the Oxygen with the computer through that. -- Add support for MidiSport USB midi interfaces https://bugs.launchpad.net/bugs/27833 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 27833] Re: Add support for MidiSport USB midi interfaces
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:/home/remy# lsusb Bus 005 Device 003: ID 067b:2506 Prolific Technology, Inc. Bus 005 Device 001: ID : Bus 004 Device 001: ID : Bus 003 Device 001: ID : Bus 002 Device 004: ID 0d8c:0006 C-Media Electronics, Inc. Bus 002 Device 001: ID : Bus 001 Device 001: ID : 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. -- Add support for MidiSport USB midi interfaces https://bugs.launchpad.net/bugs/27833 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88923] Re: Package 'midisport-firmware': firmware is not loaded automatically
*** 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 typographic sets such as Arial their appearance is the same it is important to distinguish it. _All_scripts_and_commands_must_be_issued_as_super-user, ie: sudo. So it seems that now the manual setting of the firmware should be done with sudo fxload -I /usr/share/usb/maudio/MidiSport2x2.ihx -D /dev/bus/usb/001/008 setting apropriatly /dev/bus/usb/###/### according with what shows 'lsusb' where the midi device it is pluged in. Take a look also here https://bugs.launchpad.net/ubuntu/+source /midisport-firmware/+bug/27833 since this bug report it is a duplicate of that. -- Package 'midisport-firmware': firmware is not loaded automatically https://bugs.launchpad.net/bugs/88923 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 27833] Re: Add support for MidiSport USB midi interfaces
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 properly set. On the Live CD it is not. So you
have to isuue 'sudo mount usbfs -t usbfs /proc/bus/usb/'. And on a hard drive
installation you have to open '/etc/fstab' and lookout for an entry 'proc
/proc procdefaults0 0'. If it is not pressent edit it and
save. You con do it with 'sudo gedit /etc/fstab'
And next comes the firmware issue part:
Actually you have three ways to workaround the problem:
First of all and independent of the installation procedure 'apt-get
install fxload'
1- Download the Debian 'precompiled' version from any Debian repo like
http://ftp.us.debian.org/debian/pool/non-free/m/midisport-firmware/ and
install it with GDebi clicking on it with the secondary mouse button.
2- Download the 'source' package from any Debian repo or from soruceforge.net
http://sourceforge.net/project/showfiles.php?group_id=8 . Actually since
the package consists of binary firmware blob files there is no real 'source'
package. The difference lies on that the 'source' one is installed with the
make utility independently from the package management system.
So you unpack the tarball, enter to the unpacked directory and type the usual
'./configure make sudo make install'
3- Install the one from the Ubuntu repo but 'sudo nautilus' and go to
'/etc/udev/rules.d' find a file '85-midisport-firmware.rules' , delete it and
with a text editor copy and paste :
-cut
here-
# midisport-firmware.rules - udev rules for loading firmware into MidiSport
devices
# DEVPATH==/*.0 selects interface 0 only
# (some udev versions don't work with SYSFS{bInterfaceNumber})
# MidiSport 2x2
ACTION==add, SUBSYSTEM==usb, DEVPATH==/*.0, ENV{PRODUCT}==763/1001/*,
RUN+=/sbin/fxload -s /lib/firmware/maudio/MidiSportLoader.ihx -I
/lib/firmware/maudio/MidiSport2x2.ihx
# MidiSport 1x1
ACTION==add, SUBSYSTEM==usb, DEVPATH==/*.0, ENV{PRODUCT}==763/1010/*,
RUN+=/sbin/fxload -s /lib/firmware/maudio/MidiSportLoader.ihx -I
/lib/firmware/maudio/MidiSport1x1.ihx
# KeyStation
ACTION==add, SUBSYSTEM==usb, DEVPATH==/*.0, ENV{PRODUCT}==763/1014/*,
RUN+=/sbin/fxload -s /lib/firmware/maudio/MidiSportLoader.ihx -I
/lib/firmware/maudio/MidiSportKS.ihx
# MidiSport 4x4
ACTION==add, SUBSYSTEM==usb, DEVPATH==/*.0, ENV{PRODUCT}==763/1020/*,
RUN+=/sbin/fxload -s /lib/firmware/maudio/MidiSportLoader.ihx -I
/lib/firmware/maudio/MidiSport4x4.ihx
# MidiSport 8x8
ACTION==add, SUBSYSTEM==usb, DEVPATH==/*.0, ENV{PRODUCT}==763/1031/110,
RUN+=/sbin/fxload -s /lib/firmware/maudio/MidiSportLoader.ihx -I
/lib/firmware/maudio/MidiSport8x8-2.10.ihx
ACTION==add, SUBSYSTEM==usb, DEVPATH==/*.0, ENV{PRODUCT}==763/1031/121,
RUN+=/sbin/fxload -s /lib/firmware/maudio/MidiSportLoader.ihx -I
/lib/firmware/maudio/MidiSport8x8-2.21.ihx
# vim: ft=conf
cut
here
and save it as '85-midisport-firmware.rules' on '/etc/udev/rules.d'.
You have got to chose any of the three options and then when you plug
your Midisport/M-Audio device should be automatically recognized. I have
tested the three ways plus the manual way pointed out on an earlier post
with a Keystation keyboard and I've managed to fix the problem.
So far for the Ubuntu maintainer of this package I think that the most
straightforward solution is to simply rip out the deb package from
Debian's repo and upload to the Ubuntu Multiverse, since it appears
that this one just work 'out of the box' with the newly introduced
changes on the udev rules on Ubuntu.
** Attachment added: 85-midisport-firmware.rules replacement to the one
installed by Ubuntu deb package. Place it on /etc/udev/rules.d/
http://launchpadlibrarian.net/13158474/85-midisport-firmware.rules
--
Add support for MidiSport USB midi interfaces
https://bugs.launchpad.net/bugs/27833
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 27833] Re: Add support for MidiSport USB midi interfaces
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 the duplicate of this bug report here https://bugs.launchpad.net/ubuntu/+source/midisport- firmware/+bug/88923/comments/19 -- Add support for MidiSport USB midi interfaces https://bugs.launchpad.net/bugs/27833 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88923] Re: Package 'midisport-firmware': firmware is not loaded automatically
*** 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 which I am using now is for real work). With the March 18th beta and the live daily build of March 28 what I've seen is that the usb devices that normaly appeared both mounted at /proc/bus/usb/###/### and at /dev/bus/usb/###/###, now only appear at /dev/bus/usb/ In my case the workaround is issue an lsusb to identify the bus and device numbers of the Midiman device and then load manualy the firmware with something like: /sbin/fxload -s /lib/firmware/maudio/MidiSportLoader.ihx -I /lib/firmware/maudio/MidiSportKS.ihx -D /dev/bus/usb/##1/##2 being ##1 and ##2 the numbers showed with the lsusb command and substituing MidiSportKS.ihx with that appropriate to your m-audio device. A script to automaticaly do the workaround could be: #!/bin/bash #your firmware ... taken from usbmidi. You must substitute '.ihx' for the corresponding to your device fw=/lib/firmware/maudio/.ihx #perhaps you need an additional second stage firmware blob loader. Then you could set the following #fw2=/lib/firmware/maudio/MidiSportLoader.ihx #and change 'fxload -I $fw -D $dev' line to 'fxload -s $fw2 -I $fw -D $dev #get proc address. Perhaps you must change 'Midisport' for 'Midiman' bd=$( lsusb | grep Midisport | cut -d ' ' -f 2,4 | sed -e 's/ /\//' -e 's/://' ) # normally it should be 'dev=/proc/bus/usb/$bd' dev=/dev/bus/usb/$bd #load firmware echo fxload -I $fw -D $dev fxload -I $fw -D $dev -- Package 'midisport-firmware': firmware is not loaded automatically https://bugs.launchpad.net/bugs/88923 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 45563] Re: Build of fglrx module fails
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 get into this dabate but I am seriously putting into question the kind of developping model Ubuntu is implementing. For me it resembles quite near to that of a succesful (unfurtunately in my opinion) company located in the nice city of Redmond. Is it making a visualy cosmeticised distro out of Debian Sid which crashes on loging or salutes you with a stalled black screen while booting, does not allow you to enable some modules for some hardware --though this is a featured suposedly supported-- the way to attract new people to open and free software? And all this after having done a big deal of propaganda saying GNU/Linux is more stable, don't crashes, and solves all problems people have with Windows, and so on... I fear some new attracted users after having such bad experiences with this distribution and others which are a big deal worst will return to their Windows, payed or pirated, loughing on Linux geeks and thinking that this kind of issues Ubuntu have also affect Debian damaging its reputation. I think Ubuntu developers should be a rather more cautious with the releases not trying to go too fast making fast food for average stupid consumer as other non free closed source companies have done for a long time. Disclaimer: This comment should not be interpreted as derogatory, offensive, or threatenning in any way and it is made on a bonna fide basis trying to encourage people to improve this distribution and all free and open source software in general. And to the extentent allowed by the law it comes absolutly without any guarantee to serve for any purpose or fitness to any use. Greetings. -- Build of fglrx module fails https://bugs.launchpad.net/bugs/45563 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178789] Module Assistant refuses to build anything on Gutsy.
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 in case if the Internet link fails) when I
do a sudo m-a and follow all module-assistant's instructions to attempt
to build and install some module (i.e.: zd1211, sl-modem or cdfs) just
before building, when on the menu I choose LIST I get:
cdfs-src (source) installed (V: 2.4.20.a+2.6.18-1):│
│ -- Binary package(s) for kernel(s): │
│+ (2.6.22-14-generic): not found│
│ Some packages could not be found. The search command can search in the │
│ package pool for precompiled packages.
though I've installed all dependencies and previously I've used the GET
command.
If then I hit on the BUILD option then a messege box telling Build of
the package cdfs-src (or any other module) failed! How do you wish to
proceed?
│
│ VIEW Examine the build log file │
│ CONTINUE Skip and continue with the next operation │
│ STOP Stop processing the build commands
It's no matter if I use the console menu or directly I issue something
like sudo m-a clean,get,build zd1211 the result allways ends the
same.
Here are some log files from m-a
For sl-modem:
dh_testdir
dh_testroot
rm -f build-arch-stamp build-indep-stamp configure-stamp
# Add here commands to clean up after the build process.
/usr/bin/make clean SUPPORT_ALSA=1
make[1]: Entering directory `/usr/src/modules/sl-modem'
make[1]: Leaving directory `/usr/src/modules/sl-modem'
cd modem; /usr/bin/make clean SUPPORT_ALSA=1
make[1]: Entering directory `/usr/src/modules/sl-modem/modem'
make[1]: Leaving directory `/usr/src/modules/sl-modem/modem'
dh_clean
/usr/bin/make -C drivers clean
make[1]: Entering directory `/usr/src/modules/sl-modem/drivers'
rm -f kernel-ver slamr.o slusb.o slamr.ko slusb.ko *st7554.o amrmo_init.o
sysdep_amr.o *.mod.* .*.cmd *~
rm -f -r .tmp_versions
make[1]: Leaving directory `/usr/src/modules/sl-modem/drivers'
/usr/bin/make -f debian/rules kdist_clean kdist_config binary-modules
make[1]: Entering directory `/usr/src/modules/sl-modem'
dh_testdir
dh_testroot
rm -f build-arch-stamp build-indep-stamp configure-stamp
# Add here commands to clean up after the build process.
/usr/bin/make clean SUPPORT_ALSA=1
make[2]: Entering directory `/usr/src/modules/sl-modem'
make[2]: *** No rule to make target `clean'. Stop.
make[2]: Leaving directory `/usr/src/modules/sl-modem'
make[1]: [clean] Error 2 (ignored)
cd modem; /usr/bin/make clean SUPPORT_ALSA=1
make[2]: Entering directory `/usr/src/modules/sl-modem/modem'
make[2]: *** No rule to make target `clean'. Stop.
make[2]: Leaving directory `/usr/src/modules/sl-modem/modem'
make[1]: [clean] Error 2 (ignored)
dh_clean
/usr/bin/make -C drivers clean
make[2]: Entering directory `/usr/src/modules/sl-modem/drivers'
rm -f kernel-ver slamr.o slusb.o slamr.ko slusb.ko *st7554.o amrmo_init.o
sysdep_amr.o *.mod.* .*.cmd *~
rm -f -r .tmp_versions
make[2]: Leaving directory `/usr/src/modules/sl-modem/drivers'
for templ in /usr/src/modules/sl-modem/debian/sl-modem-modules-_KVERS_.postinst
/usr/src/modules/sl-modem/debian/sl-modem-modules-_KVERS_.postinst.backup
/usr/src/modules/sl-modem/debian/sl-modem-modules-_KVERS_.postinst.modules.in;
do \
cp $templ `echo $templ | sed -e 's/_KVERS_/2.6.22-14-generic/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in}
${templ%.modules.in}.backup 2/dev/null || true; \
sed -e 's/##KVERS##/2.6.22-14-generic/g ;s/#KVERS#/2.6.22-14-generic/g ;
s/_KVERS_/2.6.22-14-generic/g ; s/##KDREV##/2.6.22-14.46/g ;
s/#KDREV#/2.6.22-14.46/g ; s/_KDREV_/2.6.22-14.46/g ' $templ
${templ%.modules.in}; \
done
dh_clean -k
dh_installdirs lib/modules/2.6.22-14-generic/misc usr/lib/sl-modem
if ! test -e drivers/Makefile ; then echo Please update the package, extract
the tarball!; exit 1 ; fi
/usr/bin/make -C drivers KERNEL_DIR=/usr/src/linux KVERS=2.6.22-14-generic
make[2]: Entering directory `/usr/src/modules/sl-modem/drivers'
gcc -I/usr/src/linux/include -o kernel-ver kernel-ver.c
kernel-ver.c: In function ‘main’:
kernel-ver.c:11: error: ‘UTS_RELEASE’ undeclared (first use in this function)
kernel-ver.c:11: error: (Each undeclared identifier is reported only once
kernel-ver.c:11: error: for each function it appears in.)
make[2]: *** [kernel-ver] Error 1
make[2]: Leaving directory `/usr/src/modules/sl-modem/drivers'
make[1]: *** [binary-modules] Error 2
make[1]: Leaving directory `/usr/src/modules/sl-modem'
make: *** [kdist_build] Error 2
For
[Bug 27833] Re: Add support for MidiSport USB midi interfaces
To Forest Bond.
I see in your attached debdiff something like...
code
# 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_device, ATTRS{idVendor}==0763,
ATTRS{idProduct}==1001, RUN+=@fxload@ -s @firmwaredir@/MidiSportLoader.ihx
-I @firmwaredir@/MidiSport2x2.ihx -d $env{DEVNAME}
/code
PLEASE, PLEASE, it is not correct!!!
the '-d $env{DEVNAME}' MUST be inside the quote commas. And the '-d'
should be an upper case.
Like this...
code
ACTION==add, SUBSYSTEM==usb_device, ATTRS{idVendor}==0763,
ATTRS{idProduct}==1001, RUN+=@fxload@ -s @firmwaredir@/MidiSportLoader.ihx
-I @firmwaredir@/MidiSport2x2.ihx -D $env{DEVNAME}
/code
If not this way, would not work.
I've also tried the '-D $tempnode' as pointed out by other colegue and
also works OK.
It is interesting to know also that I have compiled from the source available
on the sourceforge.net on an official Debian Etch and the original
'42-midisport-firmware.rules.in' as ALSO the proposed modified one both work.
But on Ubuntu (both Feisty and Gutsy) the only way to make it work is with the
above code, whether with -D $env{DEVNAME} or -D $tempnode.
Greetings.
--
Add support for MidiSport USB midi interfaces
https://bugs.launchpad.net/bugs/27833
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88923] Re: Package 'midisport-firmware': firmware is not loaded automatically
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 perhaps it was
an ALSA issue and perhaps I should recompile it... perhaps a kernel
issue... really I was becoming mad.
And now a petition for the package maintainer/ers:
I see that the latest package available on the Gutsy repo still is not fixed.
So please fix it as soon as you can since this kind of bugs are what make many
people who by first time aproache to Ubuntu and other GNU/Linux dists think
that Linux is bad or do not works or that has no hardware support and so on...
So please fix it! Actually the fix it is really simple.
Thanks a lot especially to the one person that found the fix and for all
the Launchpad folks.
--
Package 'midisport-firmware': firmware is not loaded automatically
https://bugs.launchpad.net/bugs/88923
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
