Announce: piCorePlayer 8.0.0

[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]

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]

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!

[Greg Erskine]

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

Added link to "The Short List" on all wifi pages in the "More information" section.

[paul-]

Sven,

Adding rules to udev that way, udev is already running. You need to reload the udev rules manually during the boot process. You will need to do this every boot.

udevadm control —reload-rules
udevadm trigger

[paul-]

Not sure Jeff. It’s sensing the tv is not using the hdmi…..not sure why it doesn’t come back. I wonder if the fkms driver does the same thing…..just be aware that the fkms doesn’t have the noaudio parameter.

[Jeff07971]

Not sure Jeff. It’s sensing the tv is not using the hdmi…..not sure why it doesn’t come back. I wonder if the fkms driver does the same thing…..just be aware that the fkms doesn’t have the noaudio parameter.

Thanks Paul, I'll have a try again later

Jeff

[Sven_R]

Adding rules to udev that way, udev is already running. You need to reload the udev rules manually during the boot process. You will need to do this every boot.

udevadm control —reload-rules
udevadm trigger

Thanks, Paul, for coming back to this. I forgot to mention that I did this. I tried again to doublecheck - without success. I am out of ideas why the udev rules don't get fired...