paul- wrote:
> What good does referring someone to a wifi list, when they are trying
> to make something work? I don't think there is any such thing as
> "proved to work" when it comes to wifi and linux.
The point is that if someone really wants to make a pCPlayer wifi then
there is a list of
is it possible to implement a "phone home" in the beta, and have it dump
pCP version
Pi type
dac/audio out
wifi type/model
wifi sig strength
etc
etc
user may be prompted to add a few comments. 100 char max or something
eg. slow to boot. playing everything except BBC iplayer
it might be a way
Wirrunna wrote:
> pCP Team, WiFi dongle issues are a recurring theme with new releases,
> probably because of the vast number of dongles available.
> Listing a "preferred " hardware set is probably not a good call as other
> projects found out in the past, but there is already a very handy table
paul- wrote:
> Works fine here, If I had to guess, there is a channel conflict on your
> router. Try changing your channel.
pCP Team, WiFi dongle issues are a recurring theme with new releases,
probably because of the vast number of dongles available.
Listing a "preferred " hardware set is prob
In a previous message, he mentioned he is using the 4" spi version.
I'm assuming that you are trying to get jivelite working. First install
jivelite, this will also install the Touchscreen kernel modules. In pCP
3.20, I've started to include the ads7846.ko module that waveshare uses
as a touch
efthk23 wrote:
> Hi all. After a lot of time of searching, I decided to make a thread
> asking for help. As you have read from the title, I want to make my
> waveshare touchscreen work with the picore player. I've read a lot of
> posts asking the same thing but they haven't found any solution. Co
Hi all. After a lot of time of searching, I decided to make a thread
asking for help. As you have read from the title, I want to make my
waveshare touchscreen work with the picore player. I've read a lot of
posts asking the same thing but they haven't found any solution. Could
please, anyone that
I updated my 4 players and my LMS now to 3.20 with no problems after
running the hotfix - all seems to have gone fine. One very minor thing
- the output settings for the USB cards seem to get lost in the upgrade
- in the UI at least. Just needed to go into the UI and reselect the
correct output
Eyerex wrote:
> For some strange reason i can never get the WiFi working on the 3.20
> beta's or final using the Pi3 WiFi all i get is
> Scanning..
>
> No wifi devices found!
>
> Possible error:
>
> 1. USB wifi adapter missing - insert adapter.
> 2. wifi drivers and firmware missing - rebo
I tried replacing the framework call with the os shutdown but couldn't
make it work.
The command is not executed, you just get the screen bump.
"sudo: shutdown: command not found" :-)
Use "halt" instead and it works as expected.
--
Michael
___
unix
For some strange reason i can never get the WiFi working on the 3.20
beta's or final using the Pi3 WiFi all i get is
Scanning..
No wifi devices found!
Possible error:
1. USB wifi adapter missing - insert adapter.
2. wifi drivers and firmware missing - reboot required.
Setup
Pi3
piCorePlay
mherger wrote:
> > Not without recompiling the jivelite binary.
> >
> > The Quit applet registers a Quit event which resides in the C code to
> > handle an orderly shutdown of all the resources jivelite opens.
>
> But you could replace that call with aforementioned instruction in the
> lua appl
I just did in-situ updates to all 3 of my pCp players. I tried updating
to the "audio" on one and while it updated, the Ratlink wifi wouldn't
work, so I connected an ethernet cable and updated again - but this time
to standard pCp. Working now.
RPi 2B, Kali reclocker, I2S generic DAC on 2 pCps an
13 matches
Mail list logo
