Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 51 FirstFirst 123412 ... LastLast
Results 11 to 20 of 508
  1. #11
    Senior Member
    Join Date
    Jan 2006
    Location
    South Coast, NSW, Australia
    Posts
    1,233
    Well done pCP Team.

    Just in-situ upgraded 5 players (had to pre-upgrade one from pCP 3.02 to 3.5 first). All worked fine.
    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

  2. #12
    Senior Member
    Join Date
    Sep 2012
    Posts
    220
    I was on 4.0.0 b4 and just did the in-situ.
    Everything went fine until I had to disable the build in audio in order to be able to set my output settings (for my USB Dac).
    Because after the reboot Squeezelite didn't start again.
    Restart of it or reboot of pCP didn't work either.

    I did another insitu update of 4.0.0. with the same result: at first Squeezelite was running but once another restart was required (disabling the build in audio), it doesn't run anymore.

    I'll try later to download the new version and save it to the SD. Maybe that helps.

  3. #13
    Senior Member Greg Erskine's Avatar
    Join Date
    Sep 2006
    Location
    Sydney, Australia
    Posts
    1,491
    hi marflao,

    If squeezelite is not starting it usually means, "Audio output" and/or "Output setting" are not right.

    Setting "Audio output" to USB audio or disabling built-in audio clears "Output setting". It looks like insitu update may also clear "Output setting".

    Put your "Output setting" to a valid one, check under more> for options. For example, on mine its "sysdefault:CARD=Device".

    regards
    Greg

  4. #14
    Senior Member
    Join Date
    Sep 2012
    Posts
    220
    Hi Greg,

    Thanks for the swift response.

    Maybe I miss something but so far I did the following steps:

    i) insitu to 4.0.0 => successful
    ii) "USB audio" was already chosen hence I didn't need to change the audio output
    iii) disable "built in audio" => save => reboot

    Now Squeezelite is not running anymore.

    iv) set Output settings (and other Squeezelite settings) to the ones I used before (front:CARD=DAC,DEV=0; Alsa: 120:4::1:; Device supports DSD/DoP: 250; Native/DoP DSD Squeezelite binary enabled => save => Squeezelite still not running

    Restart of Squeezelite or reboot of pCP sadly don't work.

    I must admit I'm stuck right now.

    Btw...i downloaded also 4.0.0. (and afterwards 3.5) and burned it to the SD card, followed by the steps ii-iv I described above. Same results as aforementioned.

    Cheers,
    Markus

    Update:
    If i re-enable the built in audio then Squeezelite is running again.
    But the output setting field is empty again which means I don't hear any sound.

    Strange - at least for me - is that I now see other output setting options once I click on "more" (I haven't seen them earlier today).
    More strange - again at least for me - that it works now (I can hear the sound again) although the inbuilt audio is enabled AND the proper output settings have been chosen.

    I'm pretty sure that in the other versions I used (3.5 & 4.0.0b4) the inbuilt audio was disabled.

    Anyway... glad that the sound is back again. :-)
    Last edited by marflao; 2018-09-02 at 02:31.

  5. #15
    Clean install on a Raspberry Pi 3 Model B+ with 7" screen Meridian Explorer 2 DAC and a USB hard drive and everything is working and sounding sweet so big thanks to everyone's hard work in putting together Picoreplayer

  6. #16
    Senior Member Ge Ba's Avatar
    Join Date
    Apr 2017
    Location
    Switzerland
    Posts
    130
    Clean install on a Raspberry Pi 3 Model B+ with 7" screen,

    Issues with WiFi after the fresh install. It works when Pi is near the router, grabbing 5 GHz band. But when located more far, at it’s usual location, it doesn’t connect anymore. Should at least connect to 2.4 GHz band, which is still available there.

    This wasn’t an issue on pCP 3.5. Have your changes affected the selection of 5 vs 2.4 GHz network?
    Server: LMS 7.9.2 - 0011.1527861596 on Synology DS216Play. SOX mansr ARMv7 & C-3PO.
    Players: SB Radio, RPi 3B+, 7’’ Touch, pCP @Marshall Acton. Multiroom HiFi: Denon AVR-X4000, AVM M30 @Nubert NuLine/NuVero 5.1+2

  7. #17
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    1,505
    Quote Originally Posted by Ge Ba View Post
    Clean install on a Raspberry Pi 3 Model B+ with 7" screen,

    Issues with WiFi after the fresh install. It works when Pi is near the router, grabbing 5 GHz band. But when located more far, at it’s usual location, it doesn’t connect anymore. Should at least connect to 2.4 GHz band, which is still available there.

    This wasn’t an issue on pCP 3.5. Have your changes affected the selection of 5 vs 2.4 GHz network?
    Yes, wifi has been completely rewritten, but should not affected channel connections. If I had to guess it is failing at 5G and then before it can switch to 2.4G it is timing out. I have no idea how a RPI functions in an environtment with the same SSID for both bands, because my wifi router doesn't allow it. Running separate SSID's for each band will give you better control of what is going on.

    Any way you can connect over hardware, then run wifi diagnositics and the pastebin the results.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  8. #18
    Senior Member Ge Ba's Avatar
    Join Date
    Apr 2017
    Location
    Switzerland
    Posts
    130
    Quote Originally Posted by paul- View Post
    Yes, wifi has been completely rewritten, but should not affected channel connections. If I had to guess it is failing at 5G and then before it can switch to 2.4G it is timing out. I have no idea how a RPI functions in an environtment with the same SSID for both bands, because my wifi router doesn't allow it. Running separate SSID's for each band will give you better control of what is going on.

    Any way you can connect over hardware, then run wifi diagnositics and the pastebin the results.
    Thanks Paul for the hints, so I took some further attempts, but to no success.
    It seems that Pi/PiCore/PiCorePlayer totally ignore the 2.4 GHz Wi-Fi, although all my other devices (Laptop, mobiles, Squeezeradio, and pCP previously) have no issues with it.

    I wasn't even actually aware before that there was an option to assign separate SSIDs for the two WiFi bands in my router... but now I did it. Most of my devices are an 5 GHz by now, but a few still need 2.4, plus it reaches more far.

    Surprisingly, even after assigning a different SSID (highway69n) to the 2.4 band, that new SSID is not shown in the WiFi Diagnostic page, but only the 5 band (highway69).

    I'm about done here.. last options might be to mess around with IPv6 but before I do that I might rather switch back to pCP 3.5.

    How can I "pastebin" the results of the wifi diagnostics... ok I managed to attach as PDF.
    Attached Images Attached Images
    Server: LMS 7.9.2 - 0011.1527861596 on Synology DS216Play. SOX mansr ARMv7 & C-3PO.
    Players: SB Radio, RPi 3B+, 7’’ Touch, pCP @Marshall Acton. Multiroom HiFi: Denon AVR-X4000, AVM M30 @Nubert NuLine/NuVero 5.1+2

  9. #19
    Senior Member
    Join Date
    May 2017
    Posts
    352
    Are you sure that the 2.4 is on a valid channel? Try for rest ch6
    SqueezeBoxes: 2x SB2 (Living room and study), 1x Radio (Kitchen), 1x Boom (Dining room), 1x piCorePlayer (jacuzzi), 1x piCorePlayer (Garden) 1x OSMC + Squeezelite (Movie room), 1x Touch (Bedroom)
    Server: LMS on Pi3 7.9.1. on PcP 3.21
    Network: AVM Fritzbox, D-Link Smart Switch 24p, 3x Ubiquity

  10. #20
    Senior Member Ge Ba's Avatar
    Join Date
    Apr 2017
    Location
    Switzerland
    Posts
    130
    Quote Originally Posted by edwin2006 View Post
    Are you sure that the 2.4 is on a valid channel? Try for rest ch6
    BINGO!!

    Just found it myself but the channel was exactly the issue. I used to have ch13 - it worked with all other devices but after switching to 1 or 10 the SIID finally appeared!

    Thanks again, Edwin & Paul (going to donate now..).

    Code:
    Wifi diagnostics
    Wifi
    
    on
    
    Wifi MAC:
    
    b8:27:eb:af:00:19
    
    SSID:
    
    highway69n
    
    Wifi IP:
    
    192.168.1.123
    
    Password:
    
    Security:
    
    WPA-PSK
    
    Passphrase:
    
    1c5605a816de08f4565df33d3cb4c84238511a471f059d8c5930da27aef25448
    
    Hidden SSID:
    
    0
    
    Uptime:
    
    0 days 0 hours 2 minutes 23 seconds
    
    ✔  No reboot required.
    
    dmesg:
    
    
    [    9.205059] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
    [    9.205620] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09 18:56:28 
    [    9.971279] brcmfmac: power management disabled
    .
                    
    Loaded modules:
    
    
    Module                  Size  Used by
    joydev                 20480  0
    brcmfmac              307200  0
    brcmutil               16384  1 brcmfmac
    cfg80211              569344  1 brcmfmac
    rfkill                 28672  2 cfg80211
    rpi_backlight          16384  0
    rpi_ft5406             16384  0
                    
    lsusb results:
    
    
                    
    /etc/wpa_supplicant.conf:
    
    
    # Maintained by piCorePlayer
    ctrl_interface=/var/run/wpa_supplicant
    ctrl_interface_group=staff
    country=US
    update_config=1
    
    network={
    	#enc_ssid="highway69n"
    	ssid="highway69n"
    	psk=1c5605a816de08f4565df33d3cb4c84238511a471f059d8c5930da27aef25448
    	key_mgmt=WPA-PSK
    	auth_alg=OPEN
    }
                    
    /etc/sysconfig/tcedir/onboot.lst:
    
    
    pcp.tcz
    pcp-jivelite.tcz
    VU_Meter_Kolossos_Oval.tcz
    firmware-atheros.tcz
    firmware-brcmwifi.tcz
    firmware-ralinkwifi.tcz
    firmware-rtlwifi.tcz
    firmware-rpi3-wireless.tcz
    wireless_tools.tcz
    wpa_supplicant.tcz
                    
    wifi extensions installed:
    
    
    [ OK ] wireless_tools installed.
    [ OK ] wpa_supplicant installed.
    [ OK ] firmware-atheros installed.
    [ OK ] firmware-brcmwifi installed.
    [ OK ] firmware-ralinkwifi installed.
    [ OK ] firmware-rtlwifi installed.
    [ OK ] firmware-rpi3-wireless installed.
                    
    iwconfig results:
    
    
    wlan0     IEEE 802.11  ESSID:"highway69n"  
              Mode:Managed  Frequency:2.412 GHz  Access Point: B4:EE:B4:71:C7:21   
              Bit Rate=72.2 Mb/s   Tx-Power=31 dBm   
              Retry short limit:7   RTS thr:off   Fragment thr:off
              Encryption key:off
              Power Management:on
              Link Quality=47/70  Signal level=-63 dBm  
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:1  Invalid misc:0   Missed beacon:0
    
                    
    ifconfig results:
    
    
    wlan0     Link encap:Ethernet  HWaddr B8:27:EB:AF:00:19  
              inet addr:192.168.1.123  Bcast:192.168.1.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:354 errors:0 dropped:88 overruns:0 frame:0
              TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:111960 (109.3 KiB)  TX bytes:93624 (91.4 KiB)
    
                    
    iwlist results:
    
    
    wlan0     Scan completed :
              Cell 01 - Address: B4:EE:B4:71:C7:21
                        Channel:1
                        Frequency:2.412 GHz (Channel 1)
                        Quality=49/70  Signal level=-61 dBm  
                        Encryption key:on
                        ESSID:"highway69n"
                        Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                                  24 Mb/s; 36 Mb/s; 54 Mb/s
                        Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                        Mode:Master
                        Extra:tsf=0000000000000000
                        Extra: Last beacon: 80ms ago
    ..
                        IE: IEEE 802.11i/WPA2 Version 1
                            Group Cipher : TKIP
                            Pairwise Ciphers (2) : CCMP TKIP
                            Authentication Suites (1) : PSK
    ..
                        IE: WPA Version 1
                            Group Cipher : TKIP
                            Pairwise Ciphers (2) : CCMP TKIP
                            Authentication Suites (1) : PSK
    
     
     Available wifi networks
    
    Scanning.
    -----------------------------------------------------------------------------------------------------
               SSID                     Quality   Level       Channel      Encryption       Address
    -----------------------------------------------------------------------------------------------------
     1. highway69                          80     -54dBm    100   (5.5GHz)   on  WPA    B4:EE:B4:71:C7:32
     2. highway69n                         70     -61dBm     1 (2.412GHz)   on  WPA    B4:EE:B4:71:C7:21
     3. WN-562FE8                          65     -64dBm     1 (2.412GHz)   on  WPA2   D0:05:2A:56:2F:E8
     4. UPC9B6C232                         47     -77dBm    11 (2.462GHz)   on  WPA2   54:67:51:FC:2A:59
     5. WN-562FE8-5G                       44     -79dBm    52  (5.26GHz)   on  WPA2   D0:05:2A:56:2F:F8
     6. UPC Wi-Free                        44     -79dBm    11 (2.462GHz)   on  WPA2   56:67:11:FC:2A:59
     7. UPC7169385                         41     -81dBm     6 (2.437GHz)   on  WPA2   90:5C:44:C3:8F:3B
     8. mNETZ                              40     -82dBm     6 (2.437GHz)   on  WPA    A8:D3:F7:77:9C:B3
     9. Sunrise_2.4GHz_BEA168              40     -82dBm     6 (2.437GHz)   on  WPA    E8:BE:81:BE:A1:6C
    10. UPC Wi-Free                        40     -82dBm     6 (2.437GHz)   on  WPA2   92:5C:14:C3:8F:3B
    11. lon-41104-Starker                  34     -86dBm    60   (5.3GHz)   on  WPA2   E8:D1:1B:09:DD:F9
    12. UPCA648C44                         34     -86dBm    112  (5.56GHz)   on  WPA    54:67:51:FE:6B:EB
    -----------------------------------------------------------------------------------------------------
    Server: LMS 7.9.2 - 0011.1527861596 on Synology DS216Play. SOX mansr ARMv7 & C-3PO.
    Players: SB Radio, RPi 3B+, 7’’ Touch, pCP @Marshall Acton. Multiroom HiFi: Denon AVR-X4000, AVM M30 @Nubert NuLine/NuVero 5.1+2

Posting Permissions

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