Closed xdsquared closed 2 years ago
I seemed to have fixed the dependencies in the install.sh script for Bullseye. Had to add the following to replace qt5-default (which was removed because all Debian based distros have qt5 as default now and apparently caused more issues than it solved according to Qt): qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools
Qt-gstreamer will also fail to compile with Bullseye. There is a package you can install though. I do believe that is the package name "qt-gstreamer" and that will take car of it.
Edit the install.sh script to skip the building of it or use the install.sh script to build each leg of the whole project like this "./install.sh --openauto" or "./install.sh --dash".
The four parts the script builds is aasdk, qt-gstreamer, openauto, and dash. If you individually build these, don't forget to create the udev rules for usb. It will be the last part of that script if you need it.
The default firmware version of Bullseye also will cause you a problem when connecting your phone. Connecting phone to Openauto will show a white screen. This has not been resolved as of yet. I have a workaround but it hasn't been extensively tested and will cause high CPU usage.
Oh when I said I "fixed" the install.sh script, I didn't mean in the repo. I only got it working locally. All changes you will have to make yourself locally on your pi.
The short of it is that dash isn't compatible with bullseye yet - among other issues, bullseye has removed openmax support, so it will be especially broken on Pi 3s
has anyone tried on x86 debian buster?
Qt-gstreamer will also fail to compile with Bullseye. There is a package you can install though. I do believe that is the package name "qt-gstreamer" and that will take car of it.
actual package name is libqt5gstreamer-dev
I don't know that anyone has tried on an actual Debian install on x86 hw but I would think you could get it working manually easily depending on versions of packages.
Qt-Gstreamer can be built just as we always do but if using gstreamer 1.16 or 1.18, you have to patch the source of qt-gstreamer before it will compile. I've shared that on Slack in the development channel. Along with that you have to adjust some packages to install on Bullseye. Some of us have worked through some of those adjustments and have gotten it all built. I haven't been able to use it with the white screen issue happening on the OpenAuto tab.
Yes, we should be building qt-gstreamer from source, as the version in the raspbian repos is out of date and has a few bugs that would affect dash (like the red tint issue). I'll try and get the patch incorporated into the install script some time this week.
I really hope this get's fixed,,,i'm also stuck on my PI400 on Bullseye. no chance getting around the white screen bug so far.
There is a way around it but it isn't recommended as it would spike the CPU usage. I've found a way to use it but it isn't zero copy streaming. It relies on passing to the CPU instead of going straight through to the GPU for decoding. We are working on it. Icecube45 actually just put a PR in that I'm testing that provides the debugging function of generating the gstreamer pipeline. Hopefully it can point us in a direction toward fixing it.
Robert Crowley
On Mon, Dec 27, 2021, 5:43 PM Tysonpower @.***> wrote:
I really hope this get's fixed,,,i'm also stuck on my PI400 on Bullseye. no chance getting around the white screen bug so far.
— Reply to this email directly, view it on GitHub https://github.com/openDsh/dash/issues/105#issuecomment-1001787173, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLUDVHKTBLG52B7KNGM6TLUTDTZZANCNFSM5I4MZGEA . You are receiving this because you commented.Message ID: @.***>
I really hope this get's fixed,,,i'm also stuck on my PI400 on Bullseye. no chance getting around the white screen bug so far.
I have a workaround for the white screen issue in my branch of openauto - it adds a new setting in openauto.ini that needs to be set to true, but should work after that. Note that it requires h264bitstream to be installed
Just informing those affected until this is (hopefully) fixed upstream
Should be fixed by #112 and #107
Seem to get this problem on my Pi3
Where does it fail. For you?
Robert Crowley
On Sun, Apr 23, 2023, 9:50 AM MrMad @.***> wrote:
Seem to get this problem on my Pi3
— Reply to this email directly, view it on GitHub https://github.com/openDsh/dash/issues/105#issuecomment-1519072370, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLUDVGEN5P37ITA5F5SX33XCUXQTANCNFSM5I4MZGEA . You are receiving this because you commented.Message ID: @.***>
Seems to keep getting to this point and failing
Tried what I can to fix it but think i am well out my level of knowledge, if anyone knows a fix let me know but for now i cant find anything posted to fix this so ill try another app till i know a fix is out there.
Ok was my error due to intalling from SSH
Yes. It finished but couldn't launch the gui
Robert Crowley
On Sun, Apr 23, 2023, 3:04 PM MrMad @.***> wrote:
Ok was my error due to intalling from SSH
— Reply to this email directly, view it on GitHub https://github.com/openDsh/dash/issues/105#issuecomment-1519134151, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLUDVCORTO3VHG34F42QUTXCV4LTANCNFSM5I4MZGEA . You are receiving this because you commented.Message ID: @.***>
Debian Bullseye won't run install.sh. Says that package qt5-default has no installation candidate. Here's a clip of the terminal