BETA: piCorePlayer6.0.0 - PI4 support

[chill]

Getting there. I've discovered the modprobe commands to install the framebuffer:

modprobe flexfb setaddrwin=0 width=240 height=240 init=-1,0x11,-2,120,-1,0x36,0x00,-1,0x3A,0x05,-1,0xB2,0x0C,0x0C,0x00,0x33,0x33,-1,0xB7,0x35,-1,0xBB,0x1A,-1,0xC0,0x2C,-1,0xC2,0x01,-1,0xC3,0x0B,-1,0xC4,0x20,-1,0xC6,0x0F,-1,0xD0,0xA4,0xA1,-1,0x21,-1,0xE0,0x00,0x19,0x1E,0x0A,0x09,0x15,0x3D,0x44,0x51,0x12,0x03,0x00,0x3F,0x3F,-1,0xE1,0x00,0x18,0x1E,0x0A,0x09,0x25,0x3F,0x43,0x52,0x33,0x03,0x00,0x3F,0x3F,-1,0x29,-3
modprobe fbtft_device name=flexfb speed=32000000 cs=1 gpios=dc:9

Do you have any clues as to how to use these under pCP? These modules don't seem to be available, and I don't know whether I can add them myself or whether they have to be built into pCP.

modprobe flexfb setaddrwin=0 width=240 height=240 init=-1,0x1
1,-2,120,-1,0x36,0x00,-1,0x3A,0x05,-1,0xB2,0x0C,0x0C,0x00,0x33,0x33,-1,0xB7,0x35
,-1,0xBB,0x1A,-1,0xC0,0x2C,-1,0xC2,0x01,-1,0xC3,0x0B,-1,0xC4,0x20,-1,0xC6,0x0F,-
1,0xD0,0xA4,0xA1,-1,0x21,-1,0xE0,0x00,0x19,0x1E,0x0A,0x09,0x15,0x3D,0x44,0x51,0x
12,0x03,0x00,0x3F,0x3F,-1,0xE1,0x00,0x18,0x1E,0x0A,0x09,0x25,0x3F,0x43,0x52,0x33
,0x03,0x00,0x3F,0x3F,-1,0x29,-3
modprobe: FATAL: Module flexfb not found in directory /lib/modules/4.19.80-pcpCore
modprobe fbtft_device name=flexfb speed=32000000 cs=1 gpios=d
c:9
modprobe: FATAL: Module fbtft_device not found in directory /lib/modules/4.19.80-pcpCore

[JQW]

Those modules are there if you install Jivelite.

[chill]

Those modules are there if you install Jivelite.

So they are! Thank you - that's a start.

[Gerhardc]

Sounds like something is not getting backed up, When you pair your headphones, you should see

[ INFO ] Pairing Successful

Followed by some messages about a backup being done.

I can add a screen shot this evening.

This is my screenshot after pairing:

[coyrls]

It's because running headless, the linux kernel doesn't have the many sources for entropy, so it takes time. If you are really bothered by it, you can install a rng daemon, that will use the rpi processor hardware entropy generator to fill the random pool. Personally, I wouldn't worry about it for a Music server.

Thanks, I just wanted to check that it wouldn't cause a problem. I'm happy to leave it.

[paul-]

Gearhardc,

That all looks perfectly normal and correct. So if you do a reboot at this point, then the paired device disappears?

The only thing that I can think is that something got messed up during the install. Perhaps try to remove the bluetooth stuff, reboot, then re-add it. Is anything else installed on the system?

[Gerhardc]

Gearhardc,

That all looks perfectly normal and correct. So if you do a reboot at this point, then the paired device disappears?

The only thing that I can think is that something got messed up during the install. Perhaps try to remove the bluetooth stuff, reboot, then re-add it. Is anything else installed on the system?

I have only Squeezelite and Jivelite installed on this system. I removed the Bluetooth and reinstalled it again with the same result. The same problem exists with Bose Soundlink II speaker. After successfully paired the Headphone, i switched the Headphone off and reboot PCP. After reboot i switched the Headphone on. The Headphone speaks to me trying to connect to pi-Wohnzimmer without success. This is the pairing page after reboot:

[paul-]

I wonder if Jivelite is doing something. Do you have a spare SD card that you can start from a fresh image and just install Bluetooth. Otherwise, I'll have to work through to see what might be going on with the installation.

Does everything work if you don't reboot?

[Gerhardc]

I wonder if Jivelite is doing something. Do you have a spare SD card that you can start from a fresh image and just install Bluetooth. Otherwise, I'll have to work through to see what might be going on with the installation.

Does everything work if you don't reboot?

I have just created a fresh system only with squeezelite. Nothing has been changed. If my hadphone is switch off and then switched on again, it is reconnected and is playing music again.

[paul-]

That part is perfectly normal. Most headphones/speakers will only try to connect on when you power them on. The part that Is unusual is that you have to repair after a reboot.