rosea grammostola wrote:
> Ok, I did manage to build a kernel. But I had to force install it cause
> it shared some drivers with the alsa packages.
>
> Do you normally build the alsa packages with or against the kernel or
> something?

"Usual" I don't care of such things, but when I compiled my latest
kernel, I had this issue too. This is also for a kernel-rt package from
Quentin's private repository. IIRC there were one or two ALSA firmware
files for a Yamaha product and one or two ALSA firmware files for
another product, thus I had to force the install too, but the kernels
were fine.
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Ralf Mardorf wrote:
> rosea grammostola wrote:
>
>> Ok, I did manage to build a kernel. But I had to force install it cause
>> it shared some drivers with the alsa packages.
>>
>> Do you normally build the alsa packages with or against the kernel or
>> something?
>>
>
> "Usual" I don't care of such things, but when I compiled my latest
> kernel, I had this issue too. This is also for a kernel-rt package from
> Quentin's private repository. IIRC there were one or two ALSA firmware
> files for a Yamaha product and one or two ALSA firmware files for
> another product, thus I had to force the install too, but the kernels
> were fine.
But will the drivers for the Yamaha products also be fine? e.g. are the
yahama products still working likely after the force?



_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

rosea grammostola wrote:
> But will the drivers for the Yamaha products also be fine? e.g. are the
> yahama products still working likely after the force?

I don't know. My read is, that the ALSA firmware will be replaced by the
force option. I don't know if the ALSA drivers will have some additional
dependencies, that then might be broken for those replaced drivers.

It's very hard to learn about those issues . Usual no user needs to
patch and compile a kernel, real-time audio sometimes is an exceptional
case. Maybe we should lurk (not post) to some kernel developers lists or
so. Is there a ALSA users list ... ? ...
http://www.alsa-project.org/main/index.php/Mailing-lists ... I suppose
that a postmaster account is needed and that a lot of spam will be sent
by this list :S.
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

On Wednesday 04 November 2009 13:57, rosea grammostola wrote:
> But will the drivers for the Yamaha products also be fine? e.g. are the
> yahama products still working likely after the force?

Call me a scaredy-cat, but I would be very dubious about force-installing a
kernel. If your main aim is to get your wireless working, would it not be
possible to buy a USB one and use that in preference to the one on your PC?
I suspect the time you save in faffing about with all sorts of brokenness
will pay for it a couple of times over.

--
Pob hwyl / Best wishes

Kevin Donnelly

www.cymraeg.org.uk - Welsh-English autotranslator
www.eurfa.org.uk - Geiriadur rhydd i'r Gymraeg
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Kevin Donnelly wrote:
> On Wednesday 04 November 2009 13:57, rosea grammostola wrote:
>
>> But will the drivers for the Yamaha products also be fine? e.g. are the
>> yahama products still working likely after the force?
>>
>
> Call me a scaredy-cat, but I would be very dubious about force-installing a
> kernel. If your main aim is to get your wireless working, would it not be
> possible to buy a USB one and use that in preference to the one on your PC?
> I suspect the time you save in faffing about with all sorts of brokenness
> will pay for it a couple of times over.
>

Yesno

instead of buying new hardware, it seems to be better to get as most as
possible hardware configurations working for linux real-time audio. OTOH
it will safe time for the user just to buy another hardware. I don't
know what is consequentially.

In his case, if I remember correctly, the device is fine with some
distros or distro versions and that's a reason (after doing a backup) to
do some experiments, before buying another hardware.

... yes, I found this earlier reply:

rosea grammostola wrote:
> Ralf Mardorf wrote:
>
>> rosea grammostola wrote:
>>
>>
>>> Or is it possible to backport the 64studio jaunty-backport kernel to hardy?
>>>
>>>
>>>
>>>
>> I guess you are asking for including the jaunty kernel to hardy
>> backports, because of your wireless device.
>>
> Indeed, but not only for my wireless. I could add the jaunty kernel to
> hardy, but that doesn't seems to be a good practise afaik.
>

If I understand correctly his device is fine with Jaunty.

Ralf


_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kevin Donnelly wrote:
> On Wednesday 04 November 2009 13:57, rosea grammostola wrote:
>> But will the drivers for the Yamaha products also be fine? e.g. are the
>> yahama products still working likely after the force?
>
> Call me a scaredy-cat, but I would be very dubious about force-installing a
> kernel. If your main aim is to get your wireless working, would it not be
> possible to buy a USB one and use that in preference to the one on your PC?
> I suspect the time you save in faffing about with all sorts of brokenness
> will pay for it a couple of times over.
>
The firmware does not change all that often and I have not heard of any
problems using the firmware that shipped with a different kernel (99% of
time there is no difference). For your audio devices there is next to
no chance that the firmware has changed. The firmware is provided by
the vendor, and usually most vendors don't change it unless they have to
(If you really care about this then hash all the files in /lib/firmware
before and after and see what changed).

In this particular case whomever built the kernel package used an older
version of make-kpkg that does not put firmware into
/lib/firmware/<kernel version> directories.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFK8dT6wRXgH3rKGfMRAqb9AJ9T0zCC1NzpL67rkcP4K1 IZ+ARJAQCbBJSO
QfIC40UYgHQ3y+9WuYPNA3o=
=ohhL
-----END PGP SIGNATURE-----
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

package make-kpkg?

Is that an part of another package? Can't find it...




On 11/4/09, Gustin Johnson <gustin@echostar.ca> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Kevin Donnelly wrote:
>> On Wednesday 04 November 2009 13:57, rosea grammostola wrote:
>>> But will the drivers for the Yamaha products also be fine? e.g. are the
>>> yahama products still working likely after the force?
>>
>> Call me a scaredy-cat, but I would be very dubious about force-installing
>> a
>> kernel. If your main aim is to get your wireless working, would it not be
>>
>> possible to buy a USB one and use that in preference to the one on your
>> PC?
>> I suspect the time you save in faffing about with all sorts of brokenness
>> will pay for it a couple of times over.
>>
> The firmware does not change all that often and I have not heard of any
> problems using the firmware that shipped with a different kernel (99% of
> time there is no difference). For your audio devices there is next to
> no chance that the firmware has changed. The firmware is provided by
> the vendor, and usually most vendors don't change it unless they have to
> (If you really care about this then hash all the files in /lib/firmware
> before and after and see what changed).
>
> In this particular case whomever built the kernel package used an older
> version of make-kpkg that does not put firmware into
> /lib/firmware/<kernel version> directories.
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iD8DBQFK8dT6wRXgH3rKGfMRAqb9AJ9T0zCC1NzpL67rkcP4K1 IZ+ARJAQCbBJSO
> QfIC40UYgHQ3y+9WuYPNA3o=
> =ohhL
> -----END PGP SIGNATURE-----
> _______________________________________________
> 64studio-users mailing list
> 64studio-users@lists.64studio.com
> http://lists.64studio.com/mailman/listinfo/64studio-users
>
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

rosea grammostola wrote:
> package make-kpkg?
>
> Is that an part of another package? Can't find it...
>
It is not installed by default since it's purpose is to build kernel
packages. Not likely something everyone is going to do. If you want it
you have to install the "kernel-package" package. "build-essential" is
also a good idea to install.

Again, if you are not actually building kernels you do not need this
package.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFK8zJ7wRXgH3rKGfMRApg5AJ98YtdZGjp4cbpHd5kRrz JQEJ0NJwCePZm4
XRiEw7TPwL7dL8qhc+C+Q5I=
=Rxiq
-----END PGP SIGNATURE-----
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users