✨ Directly blacklist the vc4 module everywhere

[Itxaka]

This makes us drop the especific config files for rpi

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1407

[Itxaka]

cant build images locally, the script fails :/

[mauromorales]

LGTM

[mauromorales]

@Itxaka what issue do you get? seems to finish on my side, will copy to SD and test

[Itxaka]

@Itxaka what issue do you get? seems to finish on my side, will copy to SD and test

the losetup and the vg stuff seems to fail in my system and leaves around lv groups and loop devices mounted ¬_¬

[mauromorales]

ah yes, that happens all the time, just get rid of them every time before running the build

$ sudo dmsetup remove <device_name>

[Itxaka]

ah yes, that happens all the time, just get rid of them every time before running the build

$ sudo dmsetup remove <device_name>

did several times... still fails

even with a clean system. Looks like my system doesnt like something that the script is doing...

[mauromorales]

strange, worked well for me with ubuntu and opensuse

[jimmykarily]

ah yes, that happens all the time, just get rid of them every time before running the build

$ sudo dmsetup remove <device_name>

did several times... still fails

even with a clean system. Looks like my system doesnt like something that the script is doing...

I have issues like that too. I do things like this (among other things) to make it work:

sudo dmsetup remove $(lsblk | grep -o -E 'loop.p.')