Pi 4 with Raspbian Stretch?

[ioscanner]

I have a project I am trying to use a Pi 4 on and it seems Buster is still new and doesn't have the support needed of a few close source projects. I have tried to install Stretch on the Pi 4 but it seems it doesn't work. Is there a way to install Stretch on the Pi 4?

Thanks in advance.

[lpsw]

No. The Pi4 requires Buster.

[Imperf3kt]

No. The Pi4 requires Buster.

To be more accurate, the Pi4 needs the bootcode compatible with it to work.
This bootcode is not present in anything except Raspbian Buster and select 3rd party operating systems.

[DougieLawson]

I have a project I am trying to use a Pi 4 on and it seems Buster is still new and doesn't have the support needed of a few close source projects. I have tried to install Stretch on the Pi 4 but it seems it doesn't work. Is there a way to install Stretch on the Pi 4?

Thanks in advance.

You need to tell us what you're trying to install & run. There may be a way to get the missing stuff on Buster.

[fruitoftheloom]

I have a project I am trying to use a Pi 4 on and it seems Buster is still new and doesn't have the support needed of a few close source projects. I have tried to install Stretch on the Pi 4 but it seems it doesn't work. Is there a way to install Stretch on the Pi 4?

Thanks in advance.

You need to tell us what you're trying to install & run. There may be a way to get the missing stuff on Buster.

The OP is trying to use a Auvudea B101 HDMI Capture Device:

https://www.raspberrypi.org/forums/view ... &p=1523299

[timg236]

No. The Pi4 requires Buster.

To be more accurate, the Pi4 needs the bootcode compatible with it to work.
This bootcode is not present in anything except Raspbian Buster and select 3rd party operating systems.

For reference, Raspberry Pi4 needs the following files to boot to Linux

• start4.elf and fixup4.dat (or _cd _x variants)

• kernel7l.img

• *.dtb and overlays from bootfs

• /lib/modules from Linux

• Userland code from https://github.com/raspberrypi/userland

So if you take a Stretch image for Pi3 and copy the following files from Buster then it should boot if you disable FKMS in config.txt by commenting out "dtoverlay=vc4-fkms-v3d". The Mesa drivers for V3D will NOT run on Stretch and there is no chance of anyone at RPi spending time on that.

Disclaimer: I've not tried this since some months before launch i.e. when we switched to Buster. This should at least get a Kernel + Linux console running but I wouldn't be surprised if you hit issues with userland.

i.e. If you really really really want to run stretch then the above is a good starting point but unless you are happy debugging via serial console and hacking userland stuff then I wouldn't bother

[Imperf3kt]

disable FKMS in config.txt by commenting out "dtoverlay=vc4-fkms-v3d". The Mesa drivers for V3D will NOT run on Stretch

Are you sure? I've been using that config setting since Raspbian Jessie for one specific program that will not run without it.

Been working (mostly) fine since 2016

[ShiftPlusOne]

disable FKMS in config.txt by commenting out "dtoverlay=vc4-fkms-v3d". The Mesa drivers for V3D will NOT run on Stretch

Are you sure? I've been using that config setting since Raspbian Jessie for one specific program that will not run without it.

Been working (mostly) fine since 2016

There's a distinction between V3D and VC4, in Mesa terms. VC4 is the gallium driver for pi =<3 and V3D is the driver for pi 4. I don't think there's a V3D driver in the stretch version of Mesa.

[andrum99]

disable FKMS in config.txt by commenting out "dtoverlay=vc4-fkms-v3d". The Mesa drivers for V3D will NOT run on Stretch

Are you sure? I've been using that config setting since Raspbian Jessie for one specific program that will not run without it.

Been working (mostly) fine since 2016

There's a distinction between V3D and VC4, in Mesa terms. VC4 is the gallium driver for pi =<3 and V3D is the driver for pi 4. I don't think there's a V3D driver in the stretch version of Mesa.

It would have been nice if they had used a different dtoverlay for Pi 4 to avoid this confusion.

[fanoush]

I am running the old stretch I used before in a chroot on pi4. With schroot it even shares home directory and other configs so it is relatively painless. I currently use it to launch pyhoca-gui (remote access to x2go servers) which seems to be broken in Buster for me. So that is another solution to run old stuff on pi4.