It doesn’t work I have a 480 x 1920 screen and no picture sadly.
Waveshare 7.9in Touchscreen Support?
Can you add “drm.debug=0x02” to your kernel command line, and then after booting, ssh into your machine and run “dmesg | grep drm” and provide the output?
I will try that tomorrow. Also what is a kernel command line I’m new to Linux kernel development.
Ah, well in this case, it should be a matter of just editing or adding “extraargs=drm.debug=0x02
” (without the quotes) in /boot/uEnv.txt
- this just tells the drm subsystem to give us driver debugging outputs. i want to see if it’s actually not seeing things, or if maybe it’s something else. I looked in my code and it definitely should handle 480x1920.
Here is the output:
[ 2.275911] meson-drm ff900000.vpu: Queued 2 outputs on vpu
[ 2.276359] meson-drm ff900000.vpu: CVBS Output connector not available
[ 2.307010] meson-drm ff900000.vpu: bound ff600000.hdmi-tx (ops meson_dw_hdmi_ops)
[ 2.307398] [drm] Initialized meson 1.0.0 20161109 for ff900000.vpu on minor 0
[ 2.360614] meson-drm ff900000.vpu: [drm] Cannot find any crtc or sizes
[ 3.696342] systemd[1]: Starting Load Kernel Module drm…
[ 3.772312] systemd[1]: modprobe@drm.service: Deactivated successfully.
[ 3.773025] systemd[1]: Finished Load Kernel Module drm.
[ 4.771994] [drm] Initialized panfrost 1.1.0 20180908 for ffe40000.gpu on minor 1
Which kernel are you building, and how are you building it? And what does your /boot/uEnv.txt or /boot/extlinux/extlinux.conf file look like? there should be more messages if you have drm.debug=0x02 in the kernel command line.
To be clear, you’re not just trying to use my edid file I linked are you? because that edid file is specifically for the 400x1280 display, not yours which is apparently 400x1920?
I am building your radxa-zero 5.10y kernel and I used the radxa zero kernel building instructions on their website and when I went to edit my /boot/uEnv.txt it created a new file and I haven’t linked any edid file. Also my display is 480x1920.
Can you show me what the contents are in your /boot/uEnv.txt and of the /boot/extlinux/extlinux.conf file please? And also uname -a
please
uEnv.text just has what you said to put in it. extlinux.conf doesn’t exist with the extlinux folder.
uname -a:
Linux radxa-zero 5.10.139-meson64 #22.08.1 SMP PREEMPT Tue Aug 30 07:00:00 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
Is it because I am using armbian?
That doesn’t seem like it’s my kernel; My kernel should be 5.10.145 based.
I’m not sure how Armbian does it for their radxa zero kernels, but it should be possible to apply my patches to their build system as well
What OS are you using?
On mine I use Kali (but disclaimer that I’m a Kali dev), and we don’t put out an image, you have to build it yourself at the present time. Maybe tonight after work, I’ll look into submitting the patches to armbian, but my todo list in my free time is very long
Ok I will try and install the kernel again and see if it works.
UPDATE:
I think I know what the issue is. I think it is because it was still defaulting to the armbian default kernel even though I had a more up to date kernel installed. I tried to uninstall the old kernel and reboot but now the OS is bricked. Tomorrow I will reflash armbian on the emmc and try it again.
The change is merged. Thanks steev.
Thanks for reviewing! I’m definitely not a pro kernel developer, I just wanted to make the wave shares work because a few people were asking about them on the cyberdeck discord as the radxa zero is gaining popularity with rpis being so out of stock. I also happen to love mine too and wanted to see them working. Hopefully this helps people out
Thank you so much for this steev! I spent an insane amount of effort trying to get this working last year and eventually gave up.
Now I’m excited to revisit my project, which has been parked for so long.
@TheMediocritist, at the risk of threadjacking, I wanted to thank you for publishing your experiments with EDID on this board. I’ve got one of those ubiquitous 5" HDMI 800x480 TFT displays (Elecrow brand) and the EDID is broken, causing the image to be shifted “down” by ~10 pixels or so unless you use a non-native resolution. Somehow, your 480x800_c14.bin had the right timings to fix the display, and I was able to use your experiment logs to hack the audio support into it, so now I have perfect sound and picture.
@theophile I found this thread while trying to debug audio issues with my 5" Elecrow display (RC050S model). Do you mind sharing the steps you took to get it working?
hello! quick question, seeing that the changes have already been merged sometime back in September, will the latest OS builds work out of the box with the Waveshare 7.9 touchscreen? or will it still require building and installing the kernel?
referring to builds released in this link by the way: https://github.com/radxa-build/radxa-zero/releases
thank you!
update: i’ve built the kernel, installed it, and it now seems to work fine (though struggling with rotating the screen on kubuntu atm, still looking for a solution)