No, its the kernels handling of hdmi. What I outlined works fine for
standard hdmi monitors/TVs
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&business=U7JHY5WYHCNRU&lc=GB
Not sure, you might try doing some reading on the rpi forums. Im a
bit too busy to hunt right now.
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&business=U7JHY5WYHCNRU&lc
noaudio with the dtoverlay shows the older hdmi and headphones driver
but no sound.
I took a look at the dtoverlays - couldn't see any issues maybe the
bcm2835 config gets confused with the overlay?
Not sure where to look next, Any suggestions?
I will try other choice but it works fine with sysdefault:CARD=FXD502BT
I'm happy !!!
Yvanq's Profile: http://forums.slimdevices.com/member.php?userid=71808
View this thread: http://forums.slimdevices.com/showthread.php?t=
paul- wrote:
> I'm guessing here, but there are lots of problems with HDMI screens that
> report incorrect EDID information. I thought that was mostly related
> to the pi4, but not sure. I think you mentioned that you were
> overriding the screen size. Make sure the resolutions you have se
I'm guessing here, but there are lots of problems with HDMI screens that
report incorrect EDID information. I thought that was mostly related
to the pi4, but not sure. I think you mentioned that you were
overriding the screen size. Make sure the resolutions you have set in
the config.txt ar
Paul Webster wrote:
> Hopefully that is the same error that it is getting when being run by
> pCP.
> Challenge is to work out why.
>
> how about
> sudo ls -lrt /dev/fb*
>
> Edit:
> Unfortunately I do not have a spare system to set this up myself at the
> moment.
>
> Question:
> Which Raspberr
Hopefully that is the same error that it is getting when being run by
pCP.
Challenge is to work out why.
how about
sudo ls -lrt /dev/fb*
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc),
planetradio (bauer - kiss, absolute, scala, jazzf
Paul Webster wrote:
> OK ... try this
> cat /var/log/jivelite.log
> (no "s")
>
> and
> sudo /bin/sh /opt/jivelite/bin/jivelite.sh
cat /var/log/jivelite.log
Gives can't open no such file or directory
sudo /bin/sh /opt/jivelite/bin/jivelite.sh
Gives
fbset: FBIOPUT_VSCREENINFO: Invalid argu
OK ... try this
cat /var/log/jivelite.log
(no "s")
and
sudo /bin/sh /opt/jivelite/bin/jivelite.sh
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc),
planetradio (bauer - kiss, absolute, scala, jazzfm etc), kcrw, supla
finland, abc austra
Paul Webster wrote:
> #347 where I also said where the log file is
/bin/sh /opt/jivelite/bin/jivelite.sh
Gives can't open.. no such file or directory
/bin/sh /opt/jivelite/bin/jivelite.sh
Gives access denied
diode84's
#347 where I also said where the log file is
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc),
planetradio (bauer - kiss, absolute, scala, jazzfm etc), kcrw, supla
finland, abc australia, cbc/radio-canada and rte ireland
Paul Webster wrote:
> Did you reboot after making the gpu_mem change?
>
> Try setting Jivelite to not autostart in pCP and then run it by hand
> from the command line (see one of my earlier messages)
Paul I have searched for your earlier message. No luck.
I can access pCP8 in terminal but star
Did you reboot after making the gpu_mem change?
Try setting Jivelite to not autostart in pCP and then run it by hand
from the command line (see one of my earlier messages)
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc),
planetradio (b
Paul Webster wrote:
> Try increasing gpu_mem to 128 (or 256 or 512) (and remove the #).
>
> What I suspect is happening is that Jivelite is exiting because there is
> not enough GPU memory and then the launch script is relaunching it.
I increased mem to 512 and removed # but no difference, sti
Try increasing gpu_mem to 128 (or 256 or 512) (and remove the #).
What I suspect is happening is that Jivelite is exiting because there is
not enough GPU memory and then the launch script is relaunching it.
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering rad
Paul Webster wrote:
> The gpu_mem line(s) should be commented out (a # at the start of the
> line).
Yes it has the # at the beginning of line.
but no # before dtoverlay=vc4-kms-v3d,noaudio
diode84's Profile: http://forum
Howard Passman wrote:
> I suspect not. Raspberry pi only certifies a few if not only one screen
> officially. Plus pCP and Jivelite aren't your run of the mill software.
> There is no routine to 'calibrate' the touch screen in piCorePlayer.
>
> Of course all of this is to the best of my knowled
The gpu_mem line(s) should be commented out (a # at the start of the
line).
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc),
planetradio (bauer - kiss, absolute, scala, jazzfm etc), kcrw, supla
finland, abc australia, cbc/radio-canada a
paul- wrote:
> Your docker run command is wrong. You should post in the LMS docker
> thread.
Will do, thanks for the pointer.
sutty81's Profile: http://forums.slimdevices.com/member.php?userid=58392
View this thread: ht
Paul Webster wrote:
> I should have remembered from my CEC experiments.
I have added dtoverlay=vc4-kms-v3d,noaudio and gpu_mem=16 to
config.txt.
I now get screen alternating between the Jivelite pCP start screen and :
a large offset between 1970 and is normat looping.
What log would I need
21 matches
Mail list logo
