Comment 20 for bug 26294

Revision history for this message
ttoine (ttoine) wrote : Re: [Bug 26294] Re: Ubuntu is missing the alsa-firmware package

Endolith,

I don't want ot go into a troll, this not the place for.

First point, if you have broken packages when adding medibuntu
repository, it is up to you and not the case at all for everyone (yes,
it appends...) If you do that from a fresh Ubuntu 8.04 install, you
won't have this kind of problem.

Second point, for licence purpose, it is not possible for Canonical and
Ubuntu to host some packages like alsa-firmware on their own
repositories. The case has been discussed a lot, there is nothing to do
at this point. That is why Medibuntu was created by a third party team.

Third point, and not the least, Medibuntu is nowadays a well known
project. If you want to read dvds with libdvdcss and libdvdread3, to
have w32codecs (or w64 or ppc), alsa-firmware, and other non
distributable stuff like that, without compiling from sources...
Medibuntu is the project created and maintained for this purpose. For
exemple, you will find in Medibuntu another version of Mplayer, with
full codecs support. It is not the case with the standard Ubuntu package.

Sorry that we can't propose a better solution. It is not possible at
this time, and it is more because of the licence of the firmware
proposed by the manufacturers, than because of the Ubuntu teams.

For myself I use the alsa-firmware package provided by the Ubuntu Studio
Team for more than one year now, and I am glad to have the possibility
out of the box to use my Echo Indigo I/O and my RME hdsp Multiface II
sound cards, with Jack and Ardour2, at low latency with the -rt kernel.
Medibuntu is the first thing I add to Synaptic when installing a
workstation, and second is WineHQ. So I can do every Multimedia work
with Ubuntu and free softwares.

Toine

Endolith a écrit :
> 1. I plug in my Echo Indigo sound card, which works fine in Windows and Mac. Nothing happens.
> 2. Being a somewhat technically-minded user, I check in the System Log to see if there are any errors so I can figure out why it isn't recognized.
> 3. I copy and paste the errors into Google.
> 4. I find a bug report, which includes a link to a third-party repository named Medibuntu, which I have never heard of in several years of using Linux.
> 5. I open a terminal and copy and paste commands to install the Medibuntu repositories.
> 6. After updating my package manager, I have to manually fix broken packages and inconsistent dependencies.
> 7. After fixing my package manager, I install the firmware package and my hardware finally works.
>
> If that's what you call "supported by Ubuntu", you might as well mark
> Bug #1 as Won't Fix.
>
>