bigq wrote:
> Hi chill, here are the logs:
> when booted with connected DAC and no sound:
> 33321
>
> when booted with no dac and then plugged, sound is there:
> 33322
Well I'm a numpty at this but both files show
> [ 183.071011] FAT-fs (mmcblk0p1): Volume was not properly unmounted.
>
paul- wrote:
> It should have worked, but I never tested it. I dont have any current
> systems booting from usb. Ill have to set one up.
Ok, I have time. It is not urgent!
pi4 4gb picoreplayer with lms and squeezelite for usb inside an argon
one case
pi3b+ (7\" display, hifiberry
paul- wrote:
> Procedure is the same. Dmesg should show you what is going on.
PiCorePlayer7 32-bit config.txt started with the addition of "dtoverlay
= dwc2, dr_mode = host".
+---+
|Filename: pCP7-32bit-dmesg.txt
Past the procedures in the docs, I cant help much. I dont have any
waveshare devices.
Perhaps post all of your output. from the commands in the help doc.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
paul- wrote:
> This is a different screen, but the procedure should be similar.
>
> https://docs.picoreplayer.org/projects/add-a-display/
I tried that procedure with no luck.
Even when I change the numbers manually in that fila and location there
is no difference in how the touch reacts.
It
Procedure is the same.
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 like the
This is a different screen, but the procedure should be similar.
https://docs.picoreplayer.org/projects/add-a-display/
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
bigq wrote:
> Tried these commands. Didn't help. It seems it has not the same effect
> as re-plugging.
> Re-plugging brings sound and re-powering port doesn't.
> But anyway thanks for the idea!Did you use the right port?
Sent from my Pixel 3a using Tapatalk
slartibartfast wrote:
> One thing you could try is to toggle the power to the USB socket your
> DAC is connected to. Install uhubctl from the extensions list then add a
> couple of commands to run after start up. For my Pi3 with the DAC
> connected to socket 4 I use
>
> uhubctl -l 1-1 -p 4 -a
chill wrote:
> Can you perhaps post a couple of dmesg logs (get to them via 'Main page'
> -> 'Diagnostics' -> 'Logs', or just type dmesg at the command prompt)?
>
>
> For the first one, boot the Pi with the dac connected and powered. I
> understand that in this state you get no sound.
> For
coyrls wrote:
> No, I don't think that's the problem. I think alsactl is a red herring,
> unless you are setting an ALSA level, which you are not, it's not
> needed. The error messages you are seeing are to do with part of a
> script that is only executed when ALSAlevelout is set to "Custom".
rgro wrote:
> Hopefully, my experience will contribute just the tiniest bit for the
> next "code-illiterate" Pi/RME dac user that wants to give this nice
> little mod a try.
Thanks for being a willing guinea pig. Based on your feedback I have
corrected some mistakes in the instructions, and
Did the scanning, which gave me: "wlan0 No scan results"
I guess that's not what I wanted...?
Rothor's Profile: http://forums.slimdevices.com/member.php?userid=71377
View this thread:
Chillas someone with no programming/coding experience, I am in awe
of you, Carsten, Greg, Paul, and the rest of this community. It is
beyond cool that you can do these fixes and modifications in order to
make improvements and solve problems. My gratitude to all involved for
your time,
@jd68
Tx - will give it a go.
mr-b's Profile: http://forums.slimdevices.com/member.php?userid=10044
View this thread: http://forums.slimdevices.com/showthread.php?t=103330
___
Tx, yes I know jivelite is the UI, I was just saying that the player
works as an indication that nothing else was wrong.
Also I was just going on the advice from below which says that the cmd
should restart jivelite.
You probably have not just killed the jivelite process but also the
shell script that controls its startup and spossible restarts.
Code:
~$ ps -eaf | grep jivelite
root 5852 1 0 Feb09 ?00:00:00 /bin/sh
/opt/jivelite/bin/jivelite.sh
root 7751
Calibration of the touch with ts_calibrate will not work.
If I search for pointercal and ts.conf I find 3 different ones of three
fifferent locations.
if I use ts_calibrate only the one in usr/local/etc/ is modified.
The other locations files cannot be modified by hand as the are
Read-only
paul- wrote:
> 1) Run a Patch Update to Pull in new base and web extensions.
> 2) Reboot
> 3) Run the Minor Update to update to pCP 7.0.1
I tried this on my Pi 3B+ installation. There I am booting off an USB
Stick.
I have the version 7.0.1 but when I touch on SDCard image I only get the
normal
Jivelite is the UI not the player (SqueezePlay is the combined player
and UI).
So you appear to have killed the UI but not restarted it.
Playing works because you have not killed the player.
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip
Calibration of the touch with ts_calibrate will not work.
If I search for pointercal and ts.conf I find 3 different ones.
if I use ts_calibrate only the one in usr/local/etc/ is modified.
However it has no effect as I expect that piCoreplayer uses one of the
other files for calibration.
Or
paul- wrote:
> I guess that makes sense, since the default dwc driver is really
> modified for the rpi onboard usb chips. dwc2 is the driver commonly
> used in mainline.
I tried writing "Dtoverlay = dwc2, dr_mode = host" in config.txt of
piCorePlayer 7, but it didn't work.
I wonder if the
I guess that makes sense, since the default dwc driver is really
modified for the rpi onboard usb chips. dwc2 is the driver commonly
used in mainline.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Hi
I'm trying out the clock display freezing issue workaround of a cron job
to restart it nightly.
0 2 * * * /usr/bin/pkill -15 jivelite
However after doing this, I find the display says this in the morning.
Playback is fine though. How do I get the display back (other than a
reboot?)
33315
paul- wrote:
> Couple thoughts. First is the board that is reported. Does not appear
> to be a CM4. Also you are running the 64 bit version of pCP. I would
> try the 32bit version.
>
> >
Code:
> >
> [0.00] Linux version 5.4.83-pcpCore-v8
coyrls wrote:
> I am a bit lost as to how an upgrade vs a fresh install will address the
> problem. I think bigq started with 7.0.0, so it's not as if it was ever
> working under 6.0.1.
> My suggestions would be:
>
> 1) Check what is specified as the output under Squeezelite settings and
> if
Couple thoughts. First is the board that is reported. Does not appear
to be a CM4. Also you are running the 64 bit version of pCP. I would
try the 32bit version.
Code:
[0.00] Linux version 5.4.83-pcpCore-v8 (pCP@SoundStation) (gcc
version 7.4.1
bigq wrote:
> Man in a van and coyrls, thanks for your advises.
> So I tried to save (sudo alsactl store), backup and then reboot.
> The same situation, only replugging helps after boot.
>
> As far as I can see the problem is in initializing 'USB' soundcard on
> boot. For some reason it's not
I also had a problem with the correct display of fonts, I am very glad
that I found this thread that helped me. Thank you ralphy.
DrakeHeyman's Profile: http://forums.slimdevices.com/member.php?userid=71379
View this
Can you perhaps post a couple of dmesg logs (get to them via 'Main page'
-> 'Diagnostics' -> 'Logs', or just type dmesg at the command prompt)?
For the first one, boot the Pi with the dac connected and powered. I
understand that in this state you get no sound.
For the second one, boot the Pi
I am a bit lost as to how an upgrade vs a fresh install will address the
problem. I think bigq started with 7.0.0, so it's not as if it was ever
working under 6.0.1.
My suggestions would be:
1) Check what is specified as the output under Squeezelite settings and
if it's not already
So, I took my own suggestion :)
pCP v6.0.1 Boot log
> Starting piCorePlayer v6.1.0 startup...
> Checking for boot files on mmcblk0p1...
> Trying to mount /dev/mmcblk0p1.
> ssh file found on mmcblk0p1.
> newpcp.cfg not found on mmcblk0p1.
> Setting default piCorePlayer repository...
>
paul- wrote:
> I built that driver/extension, you can install it from the extension
> interface.
>
> rtl8821cu-5.4.83-pcpCore-v7.tcz
>
> source repo is https://github.com/brektrou/rtl8821CU
Thank you very much. Your help and time is appreciated.
rgro wrote:
> Chill, now, the behavior is as I think you'd expect. While Squeezelite
> does not start up upon a reboot with the dac off or in standby mode, as
> soon as the dac is brought up out of standby, Squeezelite is
> automatically started---and it stays on when the dac is put back into
chill wrote:
> I think I'm about there now, with a unified script that handles all the
> tasks necessary for implementing the udev rules, without any need for
> user editing.
Now I found the time to test your script and replace all the old
things.
It is working out of the box! Great work!
carsten_h wrote:
> Now I found the time to test your script and replace all the old
> things.
>
> It is working out of the box! Great work!
>
Great, thanks for confirming that. I also tried it on a separate Pi
with a different DAC (a Dragonfly headphone amp, which identifies itself
as
@BIGQ
Load up pCP v6.0.1 and see how you go :)
ronnie
Man in a van's Profile: http://forums.slimdevices.com/member.php?userid=43627
View this thread: http://forums.slimdevices.com/showthread.php?t=113895
37 matches
Mail list logo
