Home of the Squeezebox™ & Transporter® network music players.
Page 13 of 13 FirstFirst ... 3111213
Results 121 to 126 of 126
  1. #121
    Senior Member
    Join Date
    Dec 2015
    Posts
    100
    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 to build a picture of whats out there. percentages etc.
    whatever suits you guys. just a thought.
    rPi 3 + rasPi 7" LCD + HiFiBerry DiGi+ | rPi 2 + IQaudio DAC+ |rPi 2 + HiFiBerry DAC+ | Squeeze Box Touch | LMS + XPenology on HP Gen 8 |


  2. #122
    Senior Member
    Join Date
    Jan 2006
    Location
    South Coast, NSW, Australia
    Posts
    1,097
    Quote Originally Posted by paul- View Post
    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 dongles that work with 3.20 basic and audio, so their options are to provide diag details and wait for a fix, obtain a dongle that is listed as working or revert to a version that worked with their dongle. Net result is it eases pressure on the pCP team.

    In my case, the Ratlink 5370 HiFi Berry dongles that I have had since my first pCPlayer have more than payed for themselves and If I knew which dongle works with 3.20 audio I would buy one of those. In the meantime I can run 3.20 standard or revert to 3.11 Audio as those versions run with the Ratlink 5370 dongle.
    A camel is a racehorse designed by a committee.

    Seen sprayed on the outside wall of the local library -
    Three things I hate in life :
    1. Vandalism
    2. Irony
    3. Lists

  3. #123
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    569
    Wifi drivers are for the most part controlled by the upstream kernel, there are a few exceptions. I've seen many drivers break due to upstream changes. The rtl8192cu driver is one that has been a nightmare. With that driver, we decided to follow what OSMC does and revert to an older 8192cu driver. But between the two versions of the pCP kernel, they both use the same source with the few exceptions on the sound side of the Audiokernel. I have seen wifi issues with more than one chipset on the Audio Kernel. Which is why wifi is not recommended with the AudioVersion

    Which benefit of the audio kernel are you wanting to run on that one system?

  4. #124

    sysdefault:CARD=RPiCirrus

    Quote Originally Posted by paul- View Post
    There does appear to be a timing issue when the drivers are loaded, vs when the modprobe.conf file is updated at boot time. I'm really not sure where to go here without hardware in my hands to work out the bugs.
    Hi Paul, Indeed finding the bug is difficult without direct control for you.

    But , there is a breakthrough, I just got the card drivers to load for the first time .
    And based on that start a second squeezelite manually :
    /usr/local/bin/squeezelite -n piCorePlayer-test2 -o hw:CARD=RPiCirrus
    And that instance works, first song played through that was Breakthough - Queen !

    I suppose there is a timing issue and or wifi module interference.
    I started the pi again to verify configurations and new physical output connections.
    And with that I forgot to put in the wifi dongle in in time.
    Resulting in a remote unreachable system , but with the red led remained dimmed ( off ) !
    Local console confirmed:

    tc@piCorePlayer320B7-1G:~$ aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
    Subdevices: 7/8
    Subdevice #0: subdevice #0
    Subdevice #1: subdevice #1
    Subdevice #2: subdevice #2
    Subdevice #3: subdevice #3
    Subdevice #4: subdevice #4
    Subdevice #5: subdevice #5
    Subdevice #6: subdevice #6
    Subdevice #7: subdevice #7
    card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
    card 1: RPiCirrus [RPi-Cirrus], device 0: WM5102 AiFi wm5102-aif1-0 []
    Subdevices: 0/1
    Subdevice #0: subdevice #0
    tc@piCorePlayer320B7-1G:~$ squeezelite -l
    Output devices:
    null - Discard all samples (playback) or generate zero samples (capture)
    sysdefault:CARD=ALSA - bcm2835 ALSA, bcm2835 ALSA - Default Audio Device
    sysdefault:CARD=RPiCirrus - RPi-Cirrus, - Default Audio Device

    tc@piCorePlayer320B7-1G:~$

    The odd thing , timing I presume, is seen from the dmesg output :
    tc@piCorePlayer320B7-1G:~$ dmesg | egrep 'irrus|rizona'
    [ 27.922830] arizona spi0.1: Failed to get mclk1: -2
    [ 27.922865] arizona spi0.1: Failed to get mclk2: -2
    [ 27.923545] arizona spi0.1: Failed to request DCVDD: -517
    [ 27.973145] arizona spi0.1: Failed to get mclk1: -2
    [ 27.973181] arizona spi0.1: Failed to get mclk2: -2
    [ 27.973837] arizona spi0.1: Failed to request DCVDD: -517
    [ 28.075234] arizona spi0.1: Failed to get mclk1: -2
    [ 28.075265] arizona spi0.1: Failed to get mclk2: -2
    [ 28.075911] arizona spi0.1: Failed to request DCVDD: -517
    [ 28.124213] snd-rpi-cirrus soc:sound: ASoC: CPU DAI (null) not registered - will retry
    [ 28.146586] arizona spi0.1: Failed to get mclk1: -2
    [ 28.146617] arizona spi0.1: Failed to get mclk2: -2
    [ 28.147281] arizona spi0.1: Failed to request DCVDD: -517
    [ 28.148120] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry
    [ 28.163828] arizona spi0.1: Failed to get mclk1: -2
    [ 28.163862] arizona spi0.1: Failed to get mclk2: -2
    [ 28.164474] arizona spi0.1: Failed to request DCVDD: -517
    [ 28.165272] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry
    [ 36.382747] arizona spi0.1: Failed to get mclk1: -2
    [ 36.382779] arizona spi0.1: Failed to get mclk2: -2
    [ 36.383478] arizona spi0.1: Failed to request DCVDD: -517
    [ 36.384509] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry
    [ 36.936465] arizona spi0.1: Failed to get mclk1: -2
    [ 36.936499] arizona spi0.1: Failed to get mclk2: -2
    [ 36.937142] arizona spi0.1: Failed to request DCVDD: -517
    [ 36.938017] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry
    [ 99.623128] arizona spi0.1: Failed to get mclk1: -2
    [ 99.623160] arizona spi0.1: Failed to get mclk2: -2
    [ 99.623757] LDO1: supplied by RPi-Cirrus 1v8
    [ 99.638617] arizona spi0.1: WM5102 revision C
    [ 99.672548] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry
    [ 100.068523] MICVDD: supplied by RPi-Cirrus 1v8
    [ 100.069650] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry
    [ 100.080807] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry
    [ 100.540990] snd-rpi-cirrus soc:sound: wm5102-aif1 <-> 20203000.i2s mapping ok
    [ 2374.853109] arizona spi0.1: ASRC underclocked
    [ 2817.778150] arizona spi0.1: ASRC underclocked

    For timing forensics , I am running this on a pi Bplus, and applied utp after the boot and first checks , and let /sbin/udhcpc do it work later.
    I grabbed the full dmesg output in case it is needed.

    Petar if you are reading this , please see if this helps debuging with your set too.
    Do not forget to run the 'usecase' scripts from hias, see: http://www.horus.com/~hias/cirrus-driver.html.

    I will be posting more on my findings , with the hope Cirrus support can be incorporated in PCP scripts and menu choices.
    Perhaps wise to start a new thread, as pcp320beta has ended too.
    Regards M-H

  5. #125
    Junior Member
    Join Date
    Aug 2008
    Posts
    23

    On install Samba user not created

    Quote Originally Posted by paul- View Post
    Nothing was changed with samba in 3.20 from 3.11. You have always had to set the password from the web interface...... this adds a user and password.

    usr/local/var/lib/samba is already added to the backup set. That takes care of everything recursively below.
    Paul,

    I've tested installing Samba by installing it at the end of a clean install from scratch. I have convinced myself that the Set Samba dialog with Samba running and a new password in the field does NOT create a Samba user. Invoking the command "sudo pdbedit -L" returns nothing, and looking for the password database manually fails as well.

    Following up with "sudo smbpasswd -a tc", and then following up with pdbedit -L shows a user has been created and the Samba Share then works. This is a very minor thing but frustrating for a new user. Thanks for considering looking into this for a fix or next release.
    SB3 / Synology NAS running Logitech Media Server 7.9.0 / Squeeze Lite on Raspberry Pi 2 & 3

  6. #126
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    569
    Quote Originally Posted by dhull View Post
    Paul,

    I've tested installing Samba by installing it at the end of a clean install from scratch. I have convinced myself that the Set Samba dialog with Samba running and a new password in the field does NOT create a Samba user. Invoking the command "sudo pdbedit -L" returns nothing, and looking for the password database manually fails as well.

    Following up with "sudo smbpasswd -a tc", and then following up with pdbedit -L shows a user has been created and the Samba Share then works. This is a very minor thing but frustrating for a new user. Thanks for considering looking into this for a fix or next release.
    Not sure how you are doing this, but here is what I did

    Fresh Image
    - Expand SD Card
    - Install extra file systems
    - Setup USB Mount
    - Install Samba
    - Set Server Name, Workgroup, and Share
    - Set Password

    Samba Works. and if I ssh in
    Code:
    tc@piCorePlayer:~$ sudo pdbedit -L
    tc:1001:Linux User
    tc@piCorePlayer:~$

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •