[Iwanman]

Iwanman

19. Dezember 2021 at 19:36 #51852

Servus zusammen,

das Problem scheint am Pi Zero wieder aufzutreten:
-Pi-Zero,auf M2P ursprünglich V2.50 Buster-Image Update auf Beta211022
– alle Updates inkl. Firmware Updates und Kernal Updates durchgeführt.

Installation dann folgender Text:

RPi-Kamera Addon Installer

Installation gestartet – Diese Meldung zeigt den aktuellen Status der Installation aller 3 Sekunden an. Wenn diese abgeschlossen ist verschwindet die Meldung und der Server läuft.
raspimjpeg: no process found
Reading package lists…
Building dependency tree…
Reading state information…
Package php5 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package php5-cli is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package libapache2-mod-php5 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package ‚php5‘ has no installation candidate
E: Package ‚php5-cli‘ has no installation candidate
E: Package ‚libapache2-mod-php5‘ has no installation candidate
grep: ./config.txt: No such file or directory
chmod: cannot access ‚/var/www/rpicam/raspizip.sh‘: No such file or directory
cp: cannot create regular file ‚/etc/apache2/conf.d/other-vhosts-access-log‘: No such file or directory
chmod: cannot access ‚/etc/apache2/conf.d/other-vhosts-access-log‘: No such file or directory
/var/www/max2play/application/plugins/rpicam/controller/../scripts/install-rpi-cam.sh: line 111: [: ==: unary operator expected
Motion Detection set to internal camera
cp: cannot create regular file ‚/etc/motion/‘: Not a directory
chown: invalid user: ‘motion:www-data’
chmod: cannot access ‚/etc/motion/motion.conf‘: No such file or directory
Reloading apache2 configuration (via systemctl): apache2.service.
finished Please Click here to Reboot Now!

Konfiguration aktualisiert – neuer Eintrag wurde erstellt
Kamera aktiviert
Installation erfolgreich

Status: RPi Cam ist installiert | Status: RPi Cam läuft nicht

raspistill funktioniert und gibt testdatei aus.
Ihr habt da ja bisserl gebastelt habe ich gesehen.

Ich habe noch eine lauffähige M2P Stretch auf V2.47, die ist aber nicht updatefähig; nach update, ist die Kamera nicht mehr erreichbar; das war aber schon im anderen Thread, weshalb ich mit u.A. wegen log4j eine neue Buster-Version aufsetzen wollte.

Gruß
Iwanman

• This reply was modified 2 years, 4 months ago by Iwanman. Reason: Angabe Betaversion korrigiert

[Iwanman]

Iwanman

10. August 2020 at 11:54 #49517

Hi Craig,

reading other topics regarding Pi4 8GB comments (i.e. Nextcoud) it seems there is a adressing issue; i would recomment to set up a pi4 4GB with M2P-Buster, update & upgrade, update Kernel to latest available Version and try to boot that SD-Card on the 8Gig.
Let me know, if that works; perhaps time will heal your 8Gig version…

Greetings
Iwanman

[Iwanman]

Iwanman

31. Mai 2020 at 18:45 #48893

Hi MarioM,

finally I tried the new max2play Beta Version „Beta-200527“ based on the V2.50 M2P-Buster-image and I can confirm my IQaudIO DAC+ is working fine with gmediarender now.
Just for my curiosity what was the clue?

Thank you for your support,
BR
Iwanman

[Iwanman]

Iwanman

11. Mai 2020 at 14:21 #48753

Hi MarioM,

thanks for your reply; but it did Work on IQAudio‘ Buster test image mentioned above (Link) on this Buster-Image, my Pi4 runs without any problems with a fresh compiled gmrender-resurrect version (with all necessary libraries) from github gmrender-resurrect.
I compiled this version exactly in same conditions on latest max2play Pi4-buster version and launched it manually without any connection to the pre-installed version except hardware infrastructure within it’s configurations.
In my opinion there must be a bug in general settings due to the different soundcard and mixer settings, but I cannot find the clue.
If you have a IQAudio DAC+, try my example build and verify please.
Are there any similar bugs known for HifiBerry, etc.?

BR Iwanman

[Iwanman]

Iwanman

29. April 2020 at 18:27 #48666

Hi all,

first of all to change the used Debian „Buster“ build from the current state to „stable“ you have to run „sudo apt update –allow-releaseinfo-change“.
After that upgrade will work again.

So I tried to run my old IQAudIO Pi-DAC+ on my pi4b on the m2p image to use it with gmediarender DLNA. Setting up the soundcard in m2p in the same way as on Pi2’s and Pi3’s, gmediarender started, but cannot stream music. So I checked DTOverlay, alsamixer, aplay -l asound.conf. Everything seems to be ok. But no progress in time counter.
I started a different setup with IQAudio’s „0_quicktest_buster.img“ and a fresh compiled gmediarender.resurrect version. That worked fine, streaming music over the soundcard.
Back in max2play pi4b version I installed that gmediarender.resurrect version in a different directory and started it. It seemmed to be ok until I started streaming.
See the output:

gmediarender 0.0.8 started [ gmediarender 0.0.8_git2020-01-09_26d8f7e (libupnp-1.8.4; glib-2.58.3; gstreamer-0.10.36) ].
Logging switched off. Enable with –logfile=<filename> (or –logfile=stdout for console)
Ready for rendering.

** (gmediarender:8427): WARNING **: 18:24:57.283: cannot set NULL uri
ERROR [2020-04-29 18:24:57.284101 | gstreamer] play: Error: No URI set (Debug: gstplaybin2.c(3824): setup_next_source (): /GstPlayBin2:play)
ERROR [2020-04-29 18:24:57.284342 | gstreamer] setting play state failed (2)
ERROR [2020-04-29 18:24:57.284524 | upnp] upnp_set_error: Playing failed (704)

** (gmediarender:8427): WARNING **: 18:24:59.297: cannot set NULL uri
ERROR [2020-04-29 18:24:59.297855 | gstreamer] setting play state failed (2)
ERROR [2020-04-29 18:24:59.297899 | gstreamer] play: Error: No URI set (Debug: gstplaybin2.c(3824): setup_next_source (): /GstPlayBin2:play)
ERROR [2020-04-29 18:24:59.298036 | upnp] upnp_set_error: Playing failed (704)

** (gmediarender:8427): WARNING **: 18:25:01.308: cannot set NULL uri
ERROR [2020-04-29 18:25:01.308351 | gstreamer] play: Error: No URI set (Debug: gstplaybin2.c(3824): setup_next_source (): /GstPlayBin2:play)
ERROR [2020-04-29 18:25:01.308483 | gstreamer] setting play state failed (2)
ERROR [2020-04-29 18:25:01.308613 | upnp] upnp_set_error: Playing failed (704)

** (gmediarender:8427): WARNING **: 18:25:03.318: cannot set NULL uri
ERROR [2020-04-29 18:25:03.318774 | gstreamer] setting play state failed (2)
ERROR [2020-04-29 18:25:03.318803 | upnp] ERROR [2020-04-29 18:25:03.318799 | gstreamer] upnp_set_error: Playing failed (704)
play: Error: No URI set (Debug: gstplaybin2.c(3824): setup_next_source (): /GstPlayBin2:play)

An idea what can be the difference between the test-image and m2p? both were updated on latest buster resources.

BR
Iwanman

[Iwanman]

Iwanman

29. April 2020 at 17:27 #48665

Hi all,

had same situation with my pi4. I found a passive cooled and slim solution at Amazon:
Geekworm slim passive case

Not the cheapest but smartest solution regarding space, loudness and packaging

BR,
Iwanman

[Iwanman]

Iwanman

31. Dezember 2016 at 16:10 #25333

Hi,

I’m using the 2.34er HiFiBerry image of Max2Play from this site. I’ve the same issues as mentioned above.
The problems are still the same (since Jan. 2016) or has the source changed again?

Bypass to get gmediarenderer: https://klenzel.de/1642
Mention to be root or use sudo in front of commands; source gstreamer0.10-ffmpeg is also not available.

Afterwards M2P will recognise the installed version.

Greetz
Iwan