Announce: piCorePlayer 8.0.0

[paul-]

Are you sure you have the SSID input correctly, in the list of available networks, it is fuzzy, but it looks like capital letters in GHz and lower case in the SSID part?

Anthony

That's a good eye there. I looked it over, but was on my phone the first time, so tiny screen....

[jubm]

Compatible Wifi dongle examples

Hi,
I'm running PiCorePlayer on a Pi 2B with a Netgear WiFi dongle that unfortunately is using one of the incompatible Realtek chips. And I was unsuccessful at compiling the driver unfortunately.
Has any of you a compatible wifi dongle on PCP 8, and which model is it please?

I could replace the Pi with a Pi3B+ or Pi4 with onboard wifi but I'd rather continue using my Pi 2B with an external wifi dongle as it is enclosed in a custom speaker.

Thank you!

[Man in a van]

Hi,
I'm running PiCorePlayer on a Pi 2B with a Netgear WiFi dongle that unfortunately is using one of the incompatible Realtek chips. And I was unsuccessful at compiling the driver unfortunately.
Has any of you a compatible wifi dongle on PCP 8, and which model is it please?

I could replace the Pi with a Pi3B+ or Pi4 with onboard wifi but I'd rather continue using my Pi 2B with an external wifi dongle as it is enclosed in a custom speaker.

Thank you!

I have just fired up a rpi2b

piCorePlayer | piCorePlayer v8.1.0 | www v00017 | linux 5.10.77-pcpCore-v7 (32) | piCore v13.1 | Squeezelite v1.9.9-1391-pCP

Using a dongle :- Edimax EW7811 Un

dmesg

[ 3.870843] usb 1-1.4: New USB device found, idVendor=7392, idProduct=7811, bcdDevice= 2.00
[ 3.870860] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.870873] usb 1-1.4: Product: 802.11n WLAN Adapter
[ 3.870885] usb 1-1.4: Manufacturer: Realtek
[ 3.870897] usb 1-1.4: SerialNumber: 00e04c000001
.
[ 147.814099] usbcore: registered new interface driver rtl8192cu
.
[ 147.499808] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 147.536489] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'

.

Loaded Modules

Module Size Used by
rtl8192cu 86016 0
rtl_usb 20480 1 rtl8192cu
rtl8192c_common 65536 1 rtl8192cu
rtlwifi 114688 3 rtl_usb,rtl8192c_common,rtl8192cu
mac80211 815104 3 rtl_usb,rtlwifi,rtl8192cu
libarc4 16384 1 mac80211
sha256_generic 16384 0
cfg80211 782336 2 mac80211,rtlwifi
rfkill 32768 1 cfg80211
raspberrypi_hwmon 16384 0

Save Option

[ INFO ] Loading wifi firmware extensions...
[ OK ] Atheros firmware loaded.
[ OK ] Broadcom USB firmware loaded.
[ OK ] Ralink firmware loaded.
[ OK ] Realtek firmware loaded.
[ OK ] RPi Broadcom firmware loaded.
[ OK ] Done.
[ INFO ] Loading wifi extensions...
[ OK ] Wireless tools loaded.
[ OK ] WPA supplicant loaded.
[ OK ] Done.
[ INFO ] Generating new passphrase...
[ INFO ] Writing to /usr/local/etc/pcp/wpa_supplicant.conf...
[ INFO ] Reading from /usr/local/etc/pcp/wpa_supplicant.conf...
Stopping WiFi on wlan0...
wlan0 already stopped...
Starting WiFi on wlan0...
deleting routers
adding dns 192.168.1.1
adding dns 0.0.0.0
[ INFO ] Backing up files to /mnt/mmcblk0p2/tce/mydata.tgz /
Done.
[ OK ] Backup successful.

Hope this helps

ronnie

Edit: you could of course, try squeezelite and your dongle on raspberry PI OS Lite (this is a Legacy Buster which might be better for the old rpi, you can look it up on the rpi.com web page

https://downloads.raspberrypi.org/ra...armhf-lite.zip

[jubm]

Thanks Ronnie. Unfortunately, it is a 802.11b/g/n so only 2.4Ghz. But I'll keep it in mind as a workaround.
Anyone using a 5Ghz compatible dongle?

[Man in a van]

Thanks Ronnie. Unfortunately, it is a 802.11b/g/n so only 2.4Ghz. But I'll keep it in mind as a workaround.
Anyone using a 5Ghz compatible dongle?

I have this one that is dual band



I don't remember where I bought it from



dmesg

[ 3.875373] usb 1-1.2: New USB device found, idVendor=148f, idProduct=5572, bcdDevice= 1.01
[ 3.875388] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.875401] usb 1-1.2: Product: 802.11 n WLAN
[ 3.875413] usb 1-1.2: Manufacturer: Ralink
[ 3.875425] usb 1-1.2: SerialNumber: 1.0
.
[ 169.097770] usbcore: registered new interface driver rt2800usb
.
[ 168.667813] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 168.709919] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
.

loaded modules

Module Size Used by
rt2800usb 28672 0
rt2x00usb 24576 1 rt2800usb
rt2800lib 122880 1 rt2800usb
rt2x00lib 61440 3 rt2800lib,rt2800usb,rt2x00usb
mac80211 815104 3 rt2800lib,rt2x00lib,rt2x00usb
libarc4 16384 1 mac80211
sha256_generic 16384 0
cfg80211 782336 2 rt2x00lib,mac80211
rfkill 32768 1 cfg80211
raspberrypi_hwmon 16384 0

save option

[ INFO ] Loading wifi firmware extensions...
[ OK ] Atheros firmware loaded.
[ OK ] Broadcom USB firmware loaded.
[ OK ] Ralink firmware loaded.
[ OK ] Realtek firmware loaded.
[ OK ] RPi Broadcom firmware loaded.
[ OK ] Done.
[ INFO ] Loading wifi extensions...
[ OK ] Wireless tools loaded.
[ OK ] WPA supplicant loaded.
[ OK ] Done.
[ INFO ] Generating new passphrase...
[ INFO ] Writing to /usr/local/etc/pcp/wpa_supplicant.conf...
[ INFO ] Reading from /usr/local/etc/pcp/wpa_supplicant.conf...
Stopping WiFi on wlan0...
wlan0 already stopped...
Starting WiFi on wlan0...
[ INFO ] Backing up files to /mnt/mmcblk0p2/tce/mydata.tgz /
Done.
[ OK ] Backup successful.

The raspberry PI OS tells me

[email protected]:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 148f:5572 Ralink Technology, Corp. RT5572 Wireless Adapter
Bus 001 Device 003: ID 1038:1369 SteelSeries ApS Sensei Raw Gaming Mouse
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[email protected]:~ $ lsusb | grep RT5572
Bus 001 Device 004: ID 148f:5572 Ralink Technology, Corp. RT5572 Wireless Adapter

I hope that is helpful

ronnie

[Narcos]

Everything you would need is on the wifi page. The wireless is working, since you are getting scan data. Try to connect to the SSID on the 2.4ghz channel

Not sure how complicated your wifi password is.....If you are not using standard ascii characters, there could be an issue. You could try this method of setting up wifi too.

https://docs.picoreplayer.org/how-to...hout_ethernet/

It's a simple numerical password, nothing out of the ordinary. I'm unable to "SAVE" SSID changes , I keep getting a pop up message "SSID, Password and Country code MUST be entered!"

As you can see in one of the pics the SSID is erroneously saved (thanks to Anthony for spotting it) as "Bizan_5ghz", now how do I make changes to the wpa_supplicant.conf?

[Narcos]

Are you sure you have the SSID input correctly, in the list of available networks, it is fuzzy, but it looks like capital letters in GHz and lower case in the SSID part?

Anthony

Well spotted Anthony I was hoping this would solve my problem, but .....

[paul-]

I'm unable to "SAVE" SSID changes , I keep getting a pop up message "SSID, Password and Country code MUST be entered!"

The password has to be entered anytime you want to make change.

[jubm]

I think I found the answer to my question: here appears to be the list of the best wifi dongles to use on Linux (with a lot of non-Realtek chips !!)

https://github.com/morrownr/USB-WiFi/blob/main/The_Short_List.md

[paul-]

That's a good find there.

If you want to do driver tinkering, then realtek drivers can work.... but there is a reason I quit trying to maintain them. I have made it so you can build your own drivers without a terrible amount of trouble. https://github.com/piCorePlayer/pCP-Kernels

@Greg_Erskine, perhaps we should link that list somewhere in our documentation.

[jubm]

FYI, I found another one that is not listed in that list : ASUS USB-AC51, also using a 802.11ac Mediatek MT7610U chip. The advantage compared to the other 802.11ac dongles of the list is that it is smaller and cheap (the Linksys AE6000 is small too but old and very hard to find outside of US currently).

[Jeff07971]

HDMI TV Display of Jivelite fails on input change

Hi All,
I use my TV for the display of Jivelite on my Pi2B, I have done this for a good few years now without trouble until now.
Now if I select the input on the TV while the Pi is booting all works fine until I change inputs on the TV.
If I change the input on the TV to another when I come back to the Pi input my TV says "No Signal" "Not connected"

This is a relatively new problem and was working fine until an upgrade (clean install) to pCP 8.0 or 8.1, not sure which TBH

I have uncommented "config_hdmi_boost=4" in config.txt

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
config_hdmi_boost=4

but makes no difference, has anyone any ideas ?


Lounge | piCorePlayer v8.1.0 | www v00017 | linux 5.10.77-pcpCore-v7 (32) | piCore v13.1 | Squeezelite v1.9.9-1391-pCP
On Raspberry Pi 2 Model B v1.1

Jeff

[paul-]

Are you using the vc4-kms-v3d driver on this one?

What happens if you just turn off the tv? Anything odd in dmesg?

[Jeff07971]

Are you using the vc4-kms-v3d driver on this one?

What happens if you just turn off the tv? Anything odd in dmesg?

I am using the vc4-kms-3d driver with noaudio

When I first change input on TV from pCP after booting I get a single "vc4_hdmi 3f902000.hdmi: Unknown register ID 58"

This does not repeat on more input changes or poweroff of the TV

If I boot and then poweroff the TV I get the same "vc4_hdmi 3f902000.hdmi: Unknown register ID 58"

Jeff

[Sven_R]

udev rule not fired

Hi there,

I am using PiCorePlayer 8.1.0 and tried to implement restart of squeezelite when a USB device is added according to https://docs.picoreplayer.org/projec...-from-usb-dac/. I think the manual is not perfectly pCP 8.1.0 compatible, but I think I worked around the main incompatibilities between pCP 7.0.0 and 8.1.0.

So, I created /etc/udev/rules.d/80-local.rules with this content (I doublechecked idVendor and idProduct):

SUBSYSTEM=="usb", ATTRS{idVendor}=="154e", ATTR{idProduct}=="300a", ACTION=="add", RUN+="/home/tc/DAC_start.sh"
SUBSYSTEM=="usb", ATTRS{idVendor}=="154e", ATTR{idProduct}=="300a", ACTION=="remove", RUN+="/home/tc/DAC_stop.sh"

I added the directory to the pCP backup routine using /opt/.filetool.lst.

My problem is that the rules don't get fired by udev once I power up the USB device... Are there any changes in pCP 8.1.0 that would affect udev rules and that I would need to be aware of?

In case you need to know:

This is my DAC_start.sh:

######### DAC_start.sh ######### 
#!/bin/sh
date >> /tmp/udev.log
echo "Starting Squeezelite   ..." >> /tmp/udev.log
sudo /usr/local/etc/init.d/squeezelite restart
###############################

This is my DAC_stop.sh:

######### DAC_stop.sh ######### 
#!/bin/sh
date >> /tmp/udev.log
echo "Stopping Squeezelite   ..." >> /tmp/udev.log
sudo /usr/local/etc/init.d/squeezelite stop
###############################

I made both scripts executable using sudo chmod +x /home/tc/DAC_xxxx.sh. Both scripts work as expected when executed manually.

Thanks!