Open RoodyPooCandyButt opened 7 months ago
NbrTDB
commented
7 months ago Agree about the open source thing... that said, I couldn't get mine working either until I tried the legacy Pi OS (Bullseye). Obviously not ideal but at least could get it working. This was on a Pi 3 though, worth noting.
LaoHu0329
commented
7 months ago I am unable to get any of the drivers to work since kernel version 6.1.21 on a pi 4 running bookworm. The driver for 6.1.0 worked for a while but no longer does. You need to release the driver source and comply with the GPL 2.0 license because you obviously are having too hard of a time releasing functional drivers on your own. I cannot understand why you wouldn't; it would save you time and energy having to release drivers that aren't for even the latest kernel intermittently and unreliably.
If you fail to release the driver source, I will be forced to leave one star reviews and discourage others from purchasing the product, which really is a shame because from a hardware standpoint it is truly excellent.
Enter uname -a, and what is the kernel version you are using?
LaoHu0329
commented
7 months ago Agree about the open source thing... that said, I couldn't get mine working either until I tried the legacy Pi OS (Bullseye). Obviously not ideal but at least could get it working. This was on a Pi 3 though, worth noting.
https://github.com/raspberrypi/linux/blob/rpi-6.1.y/drivers/gpu/drm/panel/panel-waveshare-dsi.c
RoodyPooCandyButt
commented
7 months ago I am unable to get any of the drivers to work since kernel version 6.1.21 on a pi 4 running bookworm. The driver for 6.1.0 worked for a while but no longer does. You need to release the driver source and comply with the GPL 2.0 license because you obviously are having too hard of a time releasing functional drivers on your own. I cannot understand why you wouldn't; it would save you time and energy having to release drivers that aren't for even the latest kernel intermittently and unreliably. If you fail to release the driver source, I will be forced to leave one star reviews and discourage others from purchasing the product, which really is a shame because from a hardware standpoint it is truly excellent.
Enter uname -a, and what is the kernel version you are using?
I am on 6.1.21. I have tried all of the new versions by using rpi-update and rebooting before attempting to install via SSH, but I get a modprobe error every time with every version released since 6.1.21. 6.1.0 worked on bookworm for a while but it stopped after an update, and rolling back does not work either.
talksik
commented
6 months ago Same problem. My device is on 6.1.54 (via Boot2Qt) and I tried this repo's 6.1.20, 6.1.21, and 6.1.58 drivers and all of them produce "exec format error".
Any resolutions? or is this a lost cause?
abieuzent
commented
3 months ago any update ???
talksik
commented
3 months ago @abieuzent I was able to solve this by debugging based on my specific scenario with yocto: https://github.com/agherzan/meta-raspberrypi/issues/1211
The waveshare drivers were added to the linux kernel so it depends on what you are on.
Let me know what your set up is and I can try helping although I am no expert.
I am unable to get any of the drivers to work since kernel version 6.1.21 on a pi 4 running bookworm. The driver for 6.1.0 worked for a while but no longer does. You need to release the driver source and comply with the GPL 2.0 license because you obviously are having too hard of a time releasing functional drivers on your own. I cannot understand why you wouldn't; it would save you time and energy having to release drivers that aren't for even the latest kernel intermittently and unreliably.
If you fail to release the driver source, I will be forced to leave one star reviews and discourage others from purchasing the product, which really is a shame because from a hardware standpoint it is truly excellent.