-
-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to run HamClock on /dev/fb0 #7029
Comments
Since you enabled the KMS driver, isn't it possible to use KMS/DRM with HamClock instead of the framebuffer device? I actually was not aware that Also, did you check whether the mode/depth is reported as supported? cat /sys/class/drm/HDMI-A-1/modes
tvservice -m DMT
tvservice -m CAE
And another thing: sudo usermod -a -G render "$USER" The |
I am checking several things and will reply with more output/findings. Thank you for a quick reply. I am also installing the rPI 5 with the latest image and will test it as well. |
card0 card1 card1-HDMI-A-1 renderD128 version
1920x1080
1920x1080
1920x1080i
1920x1080i
1680x1050
1280x1024
1440x900
1280x960
1280x800
1280x720
1280x720
1280x720
1280x720
1280x720
1024x768
800x600
720x480
720x480
720x480
720x480
720x480
mode "1920x1080"
geometry 1920 1080 1920 1080 16
timings 0 0 0 0 0 0 0
rgba 5/11,6/5,5/0,0/0
endmode
Frame buffer device information:
Name : vc4drmfb
Address : 0
Size : 4147200
Type : PACKED PIXELS
Visual : TRUECOLOR
XPanStep : 1
YPanStep : 1
YWrapStep : 0
LineLength : 3840
Accelerator : No
|
Forgot to add gpu_mem_256=76
gpu_mem_512=76
gpu_mem_1024=76 |
I changed the color depth from default 16 to 32 by adding a kernel parameter. $ cat /boot/cmdline.txt
root=PARTUUID=f0cf2e93-02 rootfstype=ext4 rootwait net.ifnames=0 logo.nologo console=tty1 video=HDMI-A-1:1920x1080M-32@60 After reboot, I see the following $ fbset -i
mode "1920x1080"
geometry 1920 1080 1920 1080 32
timings 0 0 0 0 0 0 0
accel true
rgba 8/16,8/8,8/0,0/0
endmode
Frame buffer device information:
Name : vc4drmfb
Address : 0
Size : 8294400
Type : PACKED PIXELS
Visual : TRUECOLOR
XPanStep : 1
YPanStep : 1
YWrapStep : 0
LineLength : 7680
Accelerator : No Which is great. It is in 32. Would 24 work as well?
Is there a way to enable it to get hardware acceleration? At least 2D operations, line lines, and bitmaps. Perhaps I should open a separate request for this? |
Creating a bug report/issue
Required Information
cat /boot/dietpi/.version
echo $G_DISTRO_NAME $G_RASPBIAN
uname -a
Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
echo $G_HW_MODEL_NAME
or (EG: RPi3)RPi 3 Model B (aarch64)
200W USB 4 port charger
SanDisk 32G
Additional Information (if applicable)
Git HamClock, Web HamClock
Build by me. Compiles fine. Fails to run.
Yes. I just setup fresh unit
echo $G_HW_UUID
Steps to reproduce
Running level 3. No desktop installed
$ sudo apt install fbset
$ git clone --depth 1 https://github.com/kj7rrv/hamclock.git
$ cd hamclock/ ESPHamClock
$ make help
$ make hamclock-fb0-1600x960
$ ./hamclock-fb0-800x480
Expected behaviour
Actual behaviour
~/.hamclock/
shows: fails setting 32 bit color modesudo fbset -i
sudo fbset -depth 32
/boot/config.txt
sudo reboot
Extra details
$ dmesg | grep fb0
[ 1.047981] simple-framebuffer 3e812000.framebuffer: fb0: simplefb registered! [ 8.209655] vc4-drm soc:gpu: [drm] fb0: vc4drmfb frame buffer device
$ dmesg | grep vc4
[ 8.077290] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4]) [ 8.083042] rc rc0: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0 [ 8.083233] input: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0/input3 [ 8.090506] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4]) [ 8.090972] vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops [vc4]) [ 8.091281] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 8.091547] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 8.091846] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 8.092099] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4]) [ 8.103570] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0 [ 8.209655] vc4-drm soc:gpu: [drm] fb0: vc4drmfb frame buffer device
The text was updated successfully, but these errors were encountered: