Looking at the code for alsa-tools 1.0.25, it looks like the hdsp
firmware is now checked for in /lib/firmware (as per patch in comment
#23). I'm marking this as fix released, if it is in fact not working,
please reopen this bug. Thanks!
** Changed in: alsa-tools (Ubuntu)
Status: Confirmed
I just uploaded alsa-firmware 1.0.20 without the patch to Medibuntu
lucid. Now it's up to Luke. But if I were you, I wouldn't hold my breath
for that, as he hasn't even replied...
** Changed in: medibuntu
Status: In Progress => Fix Released
--
rme hdsp firmware is not loaded at system sta
** Branch linked: lp:~medibuntu-maintainers/medibuntu/alsa-
firmware.lucid
--
rme hdsp firmware is not loaded at system startup
https://bugs.launchpad.net/bugs/222663
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Changed in: medibuntu
Status: Confirmed => In Progress
** Changed in: medibuntu
Assignee: (unassigned) => Lionel Le Folgoc (mrpouit)
** Changed in: alsa-tools (Ubuntu)
Assignee: Toby Smithe (tsmithe) => (unassigned)
--
rme hdsp firmware is not loaded at system startup
https:
** Changed in: medibuntu
Status: Invalid => Confirmed
** Changed in: medibuntu
Importance: Undecided => Medium
--
rme hdsp firmware is not loaded at system startup
https://bugs.launchpad.net/bugs/222663
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Attachment added: "Patch against current universe alsa-tools source package
providing alsa-firmware-loaders binary package, to tell hdsploader to seek for
its firmwares in the place expected by the kernel"
http://launchpadlibrarian.net/35008363/alsa-tools_correct-hdsp-firmware-path.patch
** Attachment added: "Patch against current medibuntu alsa-firmware package to
drop the patch moving the hdsp firmwares in an unexpected place, notably for
the kernel."
http://launchpadlibrarian.net/35008275/alsa-firmware_drop-hdsp-patch.patch
--
rme hdsp firmware is not loaded at system st
Raphael,
I don't think so, because hdsploader works if my external box is not
connected at startup. The patch in -loaders is only for hdsploader: it
allow the hdsploader to find where is the firmware to load, for auto or
command line launch.
Let's make a trial: release the version of alsa-firmwar
ttoine,
I understand and know that. I also use a custom alsa-firmware package with my
multiface.
What I just say here is that the solution is incomplete and that's why I insist
on this change!
There's a few scenarios where people might want to load the firmware manually
through hdsploader.
i.e.
Raphael,
We don't need to change anything to alsa-tools: I can confirm that the
packaging of alsa-firmware I suggest work, I own and use every day the
RME hdsp Multiface II with this solution... The sound card driver and
firmware are auto loaded.
Toine
--
rme hdsp firmware is not loaded at syst
ttoine,
This packaging is just what I proposed : drop the 02_move_hdsploader.patch!
The problem here is that hdsploader may now not be able to find the firmware in
this location because it's actually patched to seek in the hdsploader
subdirectory. Can you test & confirm that?
That's why I think
To everyone,
In Hardy, Jaunty and Karmic, the best way to fix the problem is to install this
package:
http://apt.64studio.com/backports/pool/main/a/alsa-firmware/alsa-firmware_1.0.15-2.64studio1~jaunty1_i386.deb
No other package from Ubuntu has to be tweaked.
Can Medibuntu hosts this package, o
Hi there,
2009/10/8 ttoine :
> Thanks for your time. I don't know if Toby is still available for
> packaging.
Sorry ttoine, I'd love to have the time to learn about simple udev
etc, but it would be wrong to say I do. Consequently, I'll have to say
I'm not available to give much help on this, and
Hi,
You should probably contact the previous uploader
(https://launchpad.net/~themuso) for alsa-firmware-loaders. When it's
done, I can remove 02_move_hdsploader.patch from alsa-firmwares, and
maybe update the package to a newer version (1.0.20). I would be more
confident if someone with such hard
Raphaël,
Thanks for your time. I don't know if Toby is still available for
packaging. If you don't have any answer from the Medibuntu guys in a
couple of days, I will try to package it from vanilla sources, add it in
my PPA and report youif it works or not. I may take a bit of time to do
that, it
OK so after some research, it seems it was patched as a transition from the
firmware storage policy.
I assume we can safely drop the two patches quoted two comments above. Keep
debian maintainers tuned and we will be safe using the upstream vanilla way of
storing firmwares. Kernel will find the
Dug a bit on the debian side and changelog says it was an ubuntu merge at
version 1.0.17 so we did it wrong in the first place.
Now that ubuntu synced with debian, the changelog says the same! (Recursive
changelog is something I didn't hit before, seems fun ... or not)
Will try to know more and p
Actually the best way would be to unpatch our packages and follow the
upstream way of installing this particular firmware.
Or
Keep our current patches against ubuntu's alsa-tools
(firmware_locations.patch) and medibuntu's alsa-firmware
(02_move_hdsploader.patch) in place and use the previously pr
So were are we at this time ?
The best way to solve the problem is currently to install the .15
version of alsa-firmware of 64Studio. I do that either on Hardy LTS,
Jaunty or Karmic Beta.
Since launching hdsploader in a terminal works, the problem imho is that
the kernell module don't look for hd
I think the problem lies between the kernel (module or not) that seeks
the firmware in the /lib/firmware directory and hdsploader that is
actually patched to seek in /lib/firmware/hdsploader.
We have two ways to fix it. Either patch hdsploader for it to seek in
/lib/firmware and install hdsp firmw
** Changed in: alsa-tools (Ubuntu)
Importance: Undecided => Medium
--
rme hdsp firmware is not loaded at system startup
https://bugs.launchpad.net/bugs/222663
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
OK,
The place where the firmware helper is looking for the firmware is the
old place. It has been corrected by Toby, creating the "hdsploader"
folder. So it means that hdsploader is updated, since the command line
works well.
So where could be the problem ? Perhaps could Crimsun have any idea
abo
On hardy, creating a simple symlink from
/lib/firmware/hdsploader/multiface_firmware_rev11.bin to
/lib/firmware/multiface_firmware_rev11.bin loads the firmware
automagically every time the module is loaded.
I think firmware helper don't seek in subdirectories.
Maybe this bug should be against ude
Toby,
It doesn't work too. But don't spend too much time on this at the
moment, think about your studies first. I am not in a hurry with this
bug. Just, some people will not understand what to do because of a lack
of documentation about this sound card. Any one can create a menu
shortcut of config
Better as an alsa-firmware-loaders task, really.
** Also affects: alsa-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: alsa-tools (Ubuntu)
Assignee: (unassigned) => Toby Smithe (tsmithe)
Status: New => Confirmed
** Changed in: medibuntu
Status: Confir
Please try this updated rule. If it works, I'll prepare a debdiff for
Intrepid for alsa-tools.
** Attachment added: "85-hdsploader.rules"
http://launchpadlibrarian.net/13990197/85-hdsploader.rules
--
rme hdsp firmware is not loaded at system startup
https://bugs.launchpad.net/bugs/222663
You
26 matches
Mail list logo
