max2headroom

Forum Replies Created

Viewing 10 posts - 1 through 10 (of 10 total)
  • 3. Juni 2020 at 0:24 #48936

    Hi Geoffrey,

    Don’t waste your time with Max2Play. If you look through the responses given (something which MarioM couldn’t be bothered to do), it’s obvious there’s no real interest in fixing this. Switch to OpenELEC and don’t look back (which is what I did). All the best.

    25. Dezember 2019 at 20:33 #47831

    With an ethernet cable connected, I still get the same results.

    But to my surprise, when I install Max2Play on an old 8GB Hama 4x MicroSD it boots without problems (albeight slowly). No luck, however, with a brand new 32GB Samsung EVO Plus.

    Dunno. Maybe some weird timing glitch, where one process is supposed to wait for another, but when the card loads too quickly, those ends never meet?

    9. Dezember 2019 at 13:06 #47715

    I’m currently running LibreELEC without any issues, so I guess that rules out any hardware problem.

    PS: Starting tomorrow, I will be traveling until the day before X-mas, so I won’t be able to do any additional testing on my hardware.

    6. Dezember 2019 at 13:23 #47698

    „Do you have 5V power supply to test this out?“

    Nope I’m afraid I haven’t – if I did, I would have tested and reported. (I’m *assuming* it will be fine then, but of course assumptions aren’t perfect for troubleshooting.)

    PS: Power supply for the AMP2 is 19V/3.42A

    6. Dezember 2019 at 10:41 #47684

    Just to give some details on my boot process…

    I get:

    [ OK ] Starting Network Time Synchronization…
    [FAILED] Failed to start Network Time Synchronization
    [ OK ] Stopped Network Time Synchronization

    So far, so good. System wants to sync, notices it can’t (no network available in my case) and stops. But then I get:

    Starting Network Time Synchronization…
    A start job is running for Network Time Synchronization (27s / 30s)

    It starts to count from 1s to 30s, but at 27s it hangs.

    Looks similar to Stephane’s protocol, doesn’t it. The problem for us, of course, is that the boot process hangs, but maybe the actual question to ask is, why does the boot process try to synch network time AGAIN after it already found out that it won’t work?!

    4. Dezember 2019 at 15:38 #47679

    Hello Heiner,

    Thanks for the effort. It’s a bit unfortunate that Stephane doesn’t chime in – that would make it a lot easier to figure out what his setup and mine have in common (at least it looks like its not only my Pi having this problem – of three known setups with Amp2+Pi4+max2play, it seems like two had problems). Did you try to email him?

    You haven’t responded to my statement that my installation is out of the box, and the pi isn’t connected to the internet. In my book, that 100% rules out any issues with the home network or my router, as the pi4 doesn’t even know I have internet. If I’m missing something, please let me know.

    As for the rest, I have followed the instructions on this site and used the recommended Win32Disk-Imager. If I should use a different SD card and different burning software or change other parameters, let me know and I will try that. For obvious reasons, the only thing I can’t provide is a second Pi.

    Last but not least: In your test setup, was your Pi connected to the internet? Just to point out the obvious: The error sounds like max2play is trying to do something over internet, but can’t. So maybe the problem isn’t with the home network, but with the fact that there is no network to begin with. Thanks!

    29. November 2019 at 13:11 #47644

    Heiner, with all respect, but you are not being helpful. Either commit yourself to solving this problem, or let it be known that it’s not on your priority list (fair enough) and save the time (please).

    The setup with the screen is what I reported over two weeks ago (it’s in the word „screenshot“). I mailed you the screenshot last Wednesday. I can’t see any access point initiation, although I would assume the boot sequence has a fixed order – if Network Time Sync comes before access point initiation, or as an alternative to it, and the boot is stuck at time synchro, it is probably logical that the initiation never happens.

    27. November 2019 at 15:07 #47617

    Hm. I am happy to try out anything to solve the problem, but please bear in mind that my setup is 100% new: I already burnt a fresh image onto SD card and ran into these problems. Burning the very same image (it’s still m2p_buster_rpi-v250.img.zip) onto SD card will most certainly lead to the very same problems. Or is there something I’m missing?

    Since I can’t attach an image here, I will be mailing you a screenshot to you can see what’s going on. Possibly there’s some enhanced logging function I can use to provide further details?

    24. November 2019 at 13:40 #47592

    Hello Heiner,

    My max2play install is fresh out of the box, so there shouldn’t be conflicting entries (none by default, I guess, and I didn’t add any).

    I did have a Pi1 in my network previously, but since the problem also occurs with the router turned off, and my new Pi4 was never connected to the internet (no cable and no Wifi configured) I can’t see how that thread (which I had already digested before replying to Stephane’s post) could be related.

    (And sorry for the late reply, to me the problem is urgent, but as it turns out I wasn’t subscribed to this thread – now I am.)

    13. November 2019 at 16:05 #47528

    Sounds like just my problem. However, my Amp2 is mounted on a Pi4. Max2Play version is the latest 2.50 beta for the Pi4.

    I have a screenshot, but it seems like I can’t upload images.

    Unfortunately I can’t report what happens after removing the Amp2 board, since I don’t have a fitting AC adapter (whole device is powered via Amp2 like it should be).

    For me, I’m 100% new to Max2Play so everything is still at the default settings. There’s no physical LAN cable attached, and I never configured any kind of Wifi connection.

    Thanks!

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