Because it's simply not yet supported. Let some time to the Retropie's team to add the Pi4 support. This SBC is a huge update, compared to previous versions, they may have a lot of work. The only other distribution which has support at launch time was LibreElec, and it's still beta.
To be fair, the RPF/RPT has a long history of maintaining backward compatibility. Things have suddenly changed with the introduction of the PI4.fruitoftheloom wrote: ↑Thu Oct 10, 2019 9:55 amThe developers of Retropie have no relationship to RPF / RPT so it is not fair to complain when you have not investigated before buying, caveat emptor....
Not at all. Backwards compatibility means that the new software runs on old hardware. That has been achieved (give or take the odd bug). Getting old software to be compatible with new hardware requires ... no (or severely constrained) new hardware. That is not something RPT has ever tried or claimed. It has always been necessary to update software to run (optimally) on new hardware.
The main change is moving to the the more standard OpenGL 3D - that does break a bit of backwards compatibility, but swaps it for a much better long term option. In most others areas we should be fairly OK.davidcoton wrote: ↑Thu Oct 10, 2019 1:47 pmNot at all. Backwards compatibility means that the new software runs on old hardware. That has been achieved (give or take the odd bug). Getting old software to be compatible with new hardware requires ... no (or severely constrained) new hardware. That is not something RPT has ever tried or claimed. It has always been necessary to update software to run (optimally) on new hardware.
I think you've got that backwards (pun intended.) Backwards compatibility means that old software will run on new hardware or OS.davidcoton wrote: ↑Thu Oct 10, 2019 1:47 pmNot at all. Backwards compatibility means that the new software runs on old hardware.
Yes and no. It depends what is claimed to backward compatible. Is it the software or the hardware?jcyr wrote: ↑Thu Oct 10, 2019 3:04 pmI think you've got that backwards (pun intended.) Backwards compatibility means that old software will run on new hardware or OS.davidcoton wrote: ↑Thu Oct 10, 2019 1:47 pmNot at all. Backwards compatibility means that the new software runs on old hardware.
I didn't have any problem running the old btrfs binary from Stretch on a Pi 4B under Buster. In fact, that old binary worked better than the new one.jcyr wrote: ↑Thu Oct 10, 2019 3:04 pmI think you've got that backwards (pun intended.) Backwards compatibility means that old software will run on new hardware or OS.davidcoton wrote: ↑Thu Oct 10, 2019 1:47 pmNot at all. Backwards compatibility means that the new software runs on old hardware.
can someone elaborate this a bit more?The Pi4B has a dedicated SD card socket which suports 1.8V, DDR50 mode (at a peak bandwidth of 50Megabytes / sec). In addition, a legacy SDIO interface is available on the GPIO pins.
Could it be that Australia is upside down?The Australian version of the Official Pi4 power supply is upside down, why?
It would be easier to turn the house upside down. That way gravity will pull things towards the ceiling the way it is supposed to work down under. Another thought is to hire an electrician to install a new mains socket upside down.DougieLawson wrote: ↑Sat Oct 12, 2019 9:31 amCould you pop the lid off, turn it "widdershins" then glue it back on?
That's probably on purpose.
There are two SD card interfaces on Pi Zero to 3: one is the Broadcom SDHOST interface, the other is the Arasan SDIO. Both are present on the Pi 4 as well, but are not currently used by any official hardware. The Compute Module and Compute Module 3 use the Broadcom SDHOST interface to talk to their eMMC modules. The old Broadcom interface is not normally accessible on the Pi 4, since it uses the same GPIOs that are used for the new DDR SD card interface, and those GPIOs are hardwired to the SD card slot (and not the GPIO header).chwe wrote: ↑Fri Oct 11, 2019 3:01 amFrom https://www.raspberrypi.org/documentati ... minary.pdf
can someone elaborate this a bit more?The Pi4B has a dedicated SD card socket which suports 1.8V, DDR50 mode (at a peak bandwidth of 50Megabytes / sec). In addition, a legacy SDIO interface is available on the GPIO pins.
e.g. with a modified bootloader it should be possible to attach an eMMC module here?
I don't know if this has been answered already, because I can;t find any replies. However, there is a way to get the Pi volume up to about 150% fairly easily. First, you will have to check if you have pulseaudio on your Pi. in a Terminal type pulseaudio and hit Enter. If you get something like "E: [pulseaudio] pid.c: Daemon already running." you have it. If it says something like "pulseausio command not found" you don'e, so just do a sudo apt-get pulseaudioTideMan wrote: ↑Thu Oct 10, 2019 2:39 amI'm running buster on an RPi 4 4GB. The RPi is connected to a Samsung TV by HDMI cable.
In Chromium, when I try to stream, the pictures come through just fine, but I need both RPi and TV at 100% volume to hear sound.
Is there a way to tweak the volume up a bit?
plugwash wrote: ↑Tue Jul 02, 2019 4:39 pmIt looks like it got caught up in the QT opengl es mess.ColonelDare wrote: ↑Tue Jul 02, 2019 7:57 amDoes anyone know what happened to Clementine in the Buster repos?
I use it lots, on several devices, and will miss it if I have to move up from Stretch![]()
Debian builds (and raspbian doesn't change this) QT5 against opengl ES on armel and armhf because more arm boards have (or at least had) drivers for opengl ES than for desktop opengl. Unfortunately this breaks apps that rely on both desktop opengl and QT. The result seems to be that when clementine moved from QT4 to QT5, support for armel and armhf was dropped![]()
I previously assumed it was due to the internal layout of the PSU, indeed I had vague memories of someone from raspberry pi saying it was.
ColonelDare wrote: ↑Tue Nov 26, 2019 5:43 pmBack in June I was all sad because I lost Clementine (and thank you for the helpful explanation anyway).
I have just spotted the Strawberry Music Player currently being developed based on Clementine.
see: https://github.com/jonaski/strawberry
I followed his clues using a spare Pi3B+ that I have [and on a fresh install of Raspbian/Buster - I don't usually side-load code that's not in the repos] it compiled, linked and installed just fine. It took a while to compile and it ran out of memory 1st go as I had left Chromium open using half the 1GB RAM! Doh!Looks like your missing libgnutls28-dev, libprotobuf-dev and protobuf-compiler
You need all the packages listed here:
https://github.com/jonaski/strawberry-b ... Dockerfile
Jonas
You mean almost anything written after about 2009. I know that is when I stopped producing 32 bit versions as being too much hassle.