All,
This issue is now solved. he problem was that the rPac was loaded as a usb
1.0 rather than 2.0 and was crashing.
Thanks to Darrel
Here's from a forum,Ask me if you want to know the forum. hope this is not
against any rules.
Right, I've been puzzling over this problem for the past month, as I tried
to get Raspyfi to recognise my rPAC correctly. Like you, if the device was
connected at boot up, nothing would play - Raspyfi was frozen. If I
connected the device after boot it simply wasn't recognised by alsamixer
(F6 / output device etc).
I now know why. By default the rPAC is a USB audio 1 device - this is make
it a Plug & Play device in Windows - no driver required. Hence the 96/24
limitation. However the rPAC can be forced to boot as a USB audio 2 device.
Simply hold down the volume up & down buttons as you plug in the USB plug
to the RPi (in my case into a powered USB hub connected to the Pi). Then
power up the Pi. Start playing something from the playlist. At first you'll
hear nothing - just press volume up button on the rPAC and
behold..............! So
far I've been listening to 96/24 files - will download some 192/24 & test
those this afternoon.
Hope this resolves your problems. Enjoy!
Thanks to all
2014-02-10 15:44 GMT+00:00 Vince Ur <vince...@gmail.com>:
>
>
>
> >2014-02-08 11:17 GMT+00:00 Jonas Kvinge <linu...@closetothewind.net>:
>
> >What kernel are you using? I got the rDAC working with kernel 3.13.0.
> >3.12.6 did not work for me. Try 3.13 or newer.
>
> Jonas, my device is the rPac not the rDac. Are they equivalent in terms of
> configuration?
>
> To all,
> here is the situation. I got it working with ubuntu 12.10, kernel
> 3.2.0-44. It does not work with a newer 3.2.0, say 3.2.0-52.
> Since I have a working configuration, is there some config files, drivers
> or whatever I could look at that could help me understand what is the
> problem with making the rPac working with linux?
>
> I also tried ubuntu 13.10, don't know the kernel exactly. It did not work.
>
> The error message always says: hardware parameters could not be set.
>
> I also took the hw parameters from the working conf and put them into a
> .asoundrc file, but no joy.
>
> I had a look at dmesg but it doesn't say much what the problem is. are
> there other log files that could help dig deeper into the problem?
>
> Someone suggested to take the module in the working config and install it
> into the one i want to make the device work. Is it reasonable?
>
> Thanks
> V
>
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
