Hi Ronnie. I apologize I did not get notified that anyone had answered
my question.
I am trying to use the USB input on the DAC. I have tried both inputs
USB A and USB B. I also tried my RPI3.
>From what I've read in the manual the Windows Driver is the only one I
see. Although on their site
Give me a chance to run through it.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=U7JHY5WYHCNRU=GB_code=USD=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted)
if you
Hi Ronnie. Well, I don't know what happened, but it's working. I'm
assuming it's the third USB cable I tried.
Thanks again for taking the time. I do appreciate it very much.
Howard
Man in a van wrote:
> Can you try
>
> a) using the usb 2 sockets
>
> b) using a different rpi (3b+ or 3B)
>
paul- wrote:
> I'm concerned about the error. It seems part of the install script from
> the source package did not pickup the new kernel name, and used the
> running kernel name. The extension may have no contents. However the
> compiled driver should still be sitting on the persistent
And if it isn't obvious, THANK YOU for all the work you have put into
pCP, and dealing with all this stuff. Probably time for another project
contribution...
Braklet's Profile:
Hi Ronnie. Results from lsmod
/home/tc$ lsmod
Module Size Used by
fuse 114688 3
spidev 20480 0
snd_soc_bcm2835_i2s16384 0
snd_soc_core 200704 1 snd_soc_bcm2835_i2s
snd_compress 20480 1 snd_soc_core
snd_pcm_dmaengine
paul- wrote:
> Rebooting is fine, since you are on 7.0.1. The new kernel drivers
> would not be used anyway. I'm concerned about the error. It seems part
> of the install script from the source package did not pickup the new
> kernel name, and used the running kernel name. The extension
Hello
I have set up a pCP with a Raspberry PI and a touch display (original 7
"), in addition I have installed a remote PI board
(https://www.msldigital.com/) in order to be able to remotely control
the pCP via an IR. Is it possible to display jivelite on the touch
display as well to display on
Hi,
Trying to set up the Pimoroni Line Out Mini Hat with a Pi 4B running PcP
8.0
I've followed the steps in post #348.
The Pirate audio card plays fine thru squeezekite, but with jivelite,
the splash screen "Picoreplayer - red white and black" flashes briefly
before going back to the console
I would like to use an AudioLab M-DAC+ with my RPI 4 running
piCorePlayer 7.0, Squeezelite v1.9.9-1386-pCP. I've tried all of the
suggested output setting with no luck. Has anyone here been successful
with this DAC? Any help would be appreciated.
Thanks,
Howard
I have dealt with the vagaries of Ralink and Realtek chipsets for many
years now, so I endorse the decision to remove problematic drivers from
the piCorePlayer distribution.
However, this puts me in a quandry. I'm happily running pCP 7.0.1 on a
RPi B+ with a Realtek-based USB dongle using the
Single core chips also have limited memory available, there is a chance
you are running low of ram. Swap files are disabled by default.
Perhaps remove nozswap from the command line. As for what's in the
kernel, lists of drivers to chipsets to commercial products are not well
maintained.
If you have an x86_64 ubuntu system, you could also cross compile the
driver. I use a x86_64 system to compile all of the pCP kernels.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Editing the quote...
paul- wrote:
> there is a chance you are running low of ram.
> You can look at the drivers in the extension wireless-KERNEL.tcz and see
> the list of drivers.
> What are your wifi specs? I don't have a good feel of the AC and AX
> chipsets that work. (Since I use the
paul- wrote:
> If you have an x86_64 ubuntu system, you could also cross compile the
> driver. I use a x86_64 system to compile all of the pCP kernels.
I have set up cross-compile environments for OpenWrt and work with Yocto
and buildroot occasionally, so I'm not completely clueless there.
Howard Passman wrote:
> I would like to use an AudioLab M-DAC+ with my RPI 4 running
> piCorePlayer 7.0, Squeezelite v1.9.9-1386-pCP. I've tried all of the
> suggested output setting with no luck. Has anyone here been successful
> with this DAC? Any help would be appreciated.
>
> Thanks,
>
>
Can you try
a) using the usb 2 sockets
b) using a different rpi (3b+ or 3B)
ronnie
Man in a van's Profile: http://forums.slimdevices.com/member.php?userid=43627
View this thread:
I rebooted back into 7.0.1 with my new driver in onboot.lst, and
wireless came back up. (This is a headless system, wifi only.)
I will probably shut it down, take a SD card image, and then attempt a
8.0.0 in-situ upgrade.
But I am still very interested in swapping to in-tree USB WLAN
Rebooting is fine, since you are on 7.0.1. The new kernel drivers
would not be used anyway. I'm concerned about the error. It seems part
of the install script from the source package did not pickup the new
kernel name, and used the running kernel name. The extension may have
no contents.
Braklet wrote:
> I have set up cross-compile environments for OpenWrt and work with Yocto
> and buildroot occasionally, so I'm not completely clueless there. But I
> have never worked with TinyCoreLinux or tried to build PiCorePlayer.
> What's involved in your driver build environment?
RPI
20 matches
Mail list logo
