Mike-97470

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Posted in:
  • 30. Juni 2018 at 17:24 #36419

    Hi Heiner, and as always thanks for your quick response and support!

    1. Which versions of m2p for the RPi have SD Protect as an add-on? The only ones I have found are for ODROID.
    And, by the way, LMS in the HiFiBerry version is optional, so SD Protect should be available in that version, as well.

    Ok, so here’s what I really think: SD Power Protection is a Requirement. (period). Without it the Max2Play RPi is like a car that whenever it’s turned off can’t be started again until a tow truck is called to haul it to a garage where it can be fixed and started again. How acceptable would that be?

    If someone can’t fix LMS then do this: create a simple RPi voltage threshhold detector, a super-cheap little RPi plug in, either generate an interrupt or, better yet, a voltage out-of-tolerance flag so that, when the voltage is too low the M2P Executive can suspend normal operation until the voltage is back in tolerance. It’s that easy.

    2. http://max2play/ Here’s my theory: When a new m2p rpi is ethernet cabled into a system that has another m2p rpi there is a problem using http://max2play/ in a browser, the browser connection can’t be made because the address can’t be resolved even through the existing m2p rpi has had it’s name changed to, eg, „Big Blue“. „Big Blue“ of the existing device is different than the new one’s „max2play“ yet the browser doesn’t think they’re different.

    This is what I’ve observed, yesterday: Firefox goes to http://max2play.com (with Google Search enabled) in the URL field. Chrome keeps max2play/ in the URL field, and displays:
    „This site can’t be reached
    max2play’s server IP address could not be found.
    Did you mean http://max2play.com/?
    Search Google for max2play
    ERR_NAME_NOT_RESOLVED“

    „Big Blue“ is not responding correctly so that it’s address can be differentiated from the „max2play“ address? A little more work to fix.
    I don’t think it’s acceptable to turn off every m2p device on a network just to add a new one, I never have.

    Logging into the router to determine the IP addresses of every connected device including the new cable-connected m2p device, and using that in a browser URL field works always.

    That’s my 0.02Euro,
    Mike

    19. September 2017 at 21:40 #31408

    Here is status after Automatic Setup fails. It’s displayed on the Wifi/LAN tab after the laptop wifi connection is switched back to „max2play“:

    WiFi & Network configuration

    Setup WiFi Started
    2017-09-18 23:12:06|
    Disable Accesspoint
    insserv: Service dnsmasq has to be enabled to start service apache2
    insserv: exiting now!
    update-rc.d: error: insserv rejected the script header
    ifdown: interface wlan0 not configured
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    0
    OK
    OK
    FAIL
    OK
    OK
    OK
    No IP-Address could be received – WiFi NOT working correctly. Please check Network-ID and Passphrase!
    Ignoring unknown interface wlan0=wlan0.
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    FAIL
    OK
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    WiFi detected
    insserv: Service dnsmasq has to be enabled to start service apache2
    insserv: exiting now!
    update-rc.d: error: insserv rejected the script header
    Restarting hostapd (via systemctl): hostapd.service.
    Restarting dnsmasq (via systemctl): dnsmasq.service.
    Finished Please Click here Reload Page!

    Status: WiFi USB adapter status is active. WiFi connection status is not active
    (Only WPA/WPA2-Encryption possible)

    Load WiFi Interface:
    Network SSID:
    Password:

    List of available networks:
    start scan

    • This reply was modified 3 years, 7 months ago by  Mike-97470.
    • This reply was modified 3 years, 7 months ago by  Mike-97470.
    19. September 2017 at 21:27 #31407

    Thanks Heiner,
    I typed this just now without referring to my previous post, so I hope that the story is the same.

    Sorry for the delay. A short vacation and more important projects.
    To review: I installed a new router, the Netgear Nighthawk AC1900,
    then quickly installed dd-WRT which does not do WPS. So the router
    security is WPA2/AES.

    Afterwards, all of my wifi devices automatically connected to the
    new router except that 2 Squeezeboxes needed to do „Network Setup“, and the 2 max2play rpi3’s that were dead-in-the-water.

    I started with the rpi that is the LMS server/squeezeplay. I downloaded the new max2play version 2.44 and installed it on the SD card. After bootup I connected a laptop to wifi „max2play“ and the „Wifi/LAN“ Tab. I checked the „Load Wifi Interface“ box, entered my SSID and password, then clicked „Save all settings“. It didn’t work, I couldn’t get it to work.

    So I connected a monitor and a keyboard to the rpi, and booted to the
    raspbian login prompt. After logging in I edited /etc/wpa_supplicant.conf:

    ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
    update_config=1

    network={
    ssid=“myssid“
    psk=“mypasskey“
    proto=RSN
    key_mgmt=WPA-PSK
    pairwise=CCMP
    auth_alg=OPEN
    }

    It immediately connected and has been working ever since. For weeks now, and before I went on vacation.

    So yesterday I found time to try to get the other max2play rpi3 working. I had tried before, but was unable. So to start fresh, I fomatted the SD card and installed the version 2.44 image. Again I tried to get Autostart to work, but could not. So I again connected a monitor and keyboard to the rpi, but this time it booted through to a „primitive“ max2play desktop GUI. I have no clue why it booted differently than the other one that booted to the raspbian
    login. So I found the Xterm in the desktop, and again edited the /etc/wpa_supplicant.conf file the same way. I then checked the router at 192.168.1.1, and it showed that „max2play“ was connected at 192.168.1.8. I then did a „sudo halt“ shutdown, and took the rpi „downstairs“. After plugging in and waiting for the boot, I looked at „squeezer“ on my phone: max2play did not connect?!? Did max2play really override my wifi settings that worked, well maybe
    they would have worked? Then I used a laptop to check the router connections, max2play was,of course, missing.

    I then switched the laptop to the „max2play“ ssid, and connected via browser to the Wifi/LAN tab.
    I entered the same info as before into the Wifi/LAN tab, and again got the same result, here are some specifics:
    When I clicked the „Save all settings“ I would usually see the same rotating circle, and the screen would become translucent. After a short wait I would check the laptop’s wifi to find that it had
    somehow switched from „max2play“ to my-home-network. That’s unusual!! When I switched back to „max2play“ wifi the Wifi/LAN tab then displayed failure info which I copied, see attachment. (I don’t see a way to attach my photo, so I’m sending this before it gets lost.)

    I hope that I’ve been able to explain everything adequately, don’t be afraid to tell me that I didn’t follow directions.

    29. Juli 2016 at 21:48 #21949

    There are 2 issues:
    1. Although the Raspberry Pi 3 claims it has internal WiFi it has no antenna. There is plenty of space on the circuit board so this is baffling. Yes it has WiFi but it’s range is „short range“.
    -(The RPi’s location is now 3.5M with the use of a long RCA cable, and it’s going to be „perfect“.)
    –RPi’s location ~5.5M from Router = max2play/LMS failed after 3-4 days.
    –Previous location ~8.5M from Router = failed daily.
    –Another location ~15M from Router = totally dead, will not connect.
    Compared to smart phones, tablets, laptops, squeezeboxes, the Raspberry Pi3’s WiFi is disappointing.
    2. The other issue is that max2play’s error recovery, assuming it has some, allows the wifi interface to die. The question is: should max2play automatically reinitialize wifi when it dies?

    20. Juli 2016 at 16:17 #21692

    Thanks Heiner, and you were correct. I tried but had not successfully expanded the Partition. Although the „Instructions“ say to expand the Partition First, max2play does not allow it. But if for example, the Time Zone is set First, then the Partition can be expanded. It’s important to get feedback from max2play indicating that the Partition has been expanded successfully.
    So after taking a couple days to get max2play re-installed, understand the weird 60MB partition that Win32DiskImage creates, discover that Windows can’t format properly except in that 60MB partition, but SDFormatter can format all of an SD card, I got max2play up and running again.
    And it has failed 5 times in those 5-6 days.
    Again I’ve been using SqueezeCommander, and have suspected that the failure is related somehow to SqueezeCommander changes, changing Radio Stations, e.g., between Radio Paradiso and TSF-Jazz, a „Swiss“ one, and others. As I’m typing this it failed again (when it fails it’s WiFi connection is lost), so I’m now switching to Squeezer. [Another thing I noticed this morning is that LMS Favorites can’t be selected using either SqeezeCommander or Squeezer, but they can be using the Squeezebox Classic V3. (They can also be selected via mysqueezebox.com.) But I won’t worry about that for now.] If I continue to get failures with Squeezer my next step will be to replace the Netgear router (WNDR3800) that I’m currently using with an old-faithful LinkSys WRT54 (standard firmware).
    Thanks again Heiner for your help, I wanted to keep you up-to-date,
    Mike

Viewing 5 posts - 1 through 5 (of 5 total)