Urmas Posted August 28, 2022 Share Posted August 28, 2022 Hi guy's urgent help needed, I have banana pi m2 zero and I need the hdmi Waveshare 7inch LCD settings help. I have tried to change the config file also dts file, none of those worked. Tried to build with hdmi lcd (internet help) - none Could any one point out what is need to be done to get it work? thank you 0 Quote Link to comment Share on other sites More sharing options...
Urmas Posted September 2, 2022 Author Share Posted September 2, 2022 for anyone have same problem 7" display what i did was changing boot script 1. modify file /boot/boot.cmd setenv disp_mode "1024x600p60" mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr but now I have another problem. It's loading long time can anybody help me with that? 1 Quote Link to comment Share on other sites More sharing options...
Igor Posted September 2, 2022 Share Posted September 2, 2022 34 minutes ago, Urmas said: it's loading long time can anybody help me with that? What is loading long time? OS? https://opensource.com/article/20/9/systemd-startup-configuration 0 Quote Link to comment Share on other sites More sharing options...
Urmas Posted September 2, 2022 Author Share Posted September 2, 2022 (edited) sorry for not clarifying. once I have changed the boot.cmd and added to the armbianEnv.txt extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/1024x600.bin video=HDMI-A-1:1024x600@60 OS loading long time about 30s to 1min once it loaded then touchscreen and display works perfectly. Edited September 2, 2022 by Urmas 0 Quote Link to comment Share on other sites More sharing options...
Urmas Posted September 2, 2022 Author Share Posted September 2, 2022 Startup finished in 1min 5.125s (kernel) + 44.582s (userspace) = 1min 49.708s graphical.target reached after 21.382s in userspace 0 Quote Link to comment Share on other sites More sharing options...
Urmas Posted September 2, 2022 Author Share Posted September 2, 2022 15.033s bootsplash-hide-when-booted.service 11.318s logrotate.service 5.116s snapd.service 4.652s armbian-ramlog.service 4.173s networkd-dispatcher.service 3.562s armbian-hardware-optimize.service 2.934s dev-loop5.device 2.921s dev-mmcblk0p1.device 2.409s armbian-zram-config.service 2.329s networking.service 1.999s systemd-random-seed.service 1.827s xrdp.service 1.768s fstrim.service 1.745s dev-loop4.device 1.743s dev-loop3.device 1.740s dev-zram0.device 1.620s apt-daily-upgrade.service 1.556s dev-loop1.device 1.537s snapd.seeded.service 1.464s dev-loop2.device 1.439s dev-loop0.device 1.438s NetworkManager.service 1.186s systemd-resolved.service 1.107s chrony.service 1.004s smartmontools.service 888ms ssh.service 876ms lightdm.service 852ms systemd-logind.service 852ms wpa_supplicant.service 834ms user@0.service 795ms loadcpufreq.service 787ms user@1000.service 769ms nfs-server.service 723ms systemd-udev-trigger.service 683ms proc-fs-nfsd.mount 677ms e2scrub_reap.service 638ms snapd.apparmor.service 626ms keyboard-setup.service 617ms alsa-restore.service 587ms apparmor.service 524ms dev-zram1.device 519ms systemd-udevd.service 477ms rpc-statd.service 475ms openvpn.service 467ms rc-local.service 467ms nfs-mountd.service 462ms hostapd.service 459ms rsyslog.service 448ms systemd-user-sessions.service 445ms sysstat.service 379ms dev-mqueue.mount 361ms sys-kernel-debug.mount 353ms sys-kernel-tracing.mount 352ms xrdp-sesman.service 338ms fake-hwclock.service 325ms kmod-static-nodes.service 309ms systemd-journald.service 309ms modprobe@drm.service 308ms modprobe@configfs.service 302ms modprobe@fuse.service 288ms systemd-rfkill.service 265ms systemd-tmpfiles-clean.service 265ms systemd-modules-load.service 244ms systemd-remount-fs.service 232ms resolvconf-pull-resolved.service 224ms plymouth-quit-wait.service 212ms cpufrequtils.service 202ms nfs-idmapd.service 189ms snap-bare-5.mount 182ms systemd-update-utmp.service 178ms snap-chromium-2058.mount 177ms modprobe@chromeos_pstore.service 164ms snap-core20-1615.mount 160ms armbian-led-state.service 156ms modprobe@mtdpstore.service 149ms snap-gnome\x2d3\x2d38\x2d2004-114.mount 148ms rpc-statd-notify.service 145ms dpkg-db-backup.service 142ms sysfsutils.service 139ms modprobe@efi_pstore.service 137ms snap-gtk\x2dcommon\x2dthemes-1535.mount 122ms dev-loop6.device 122ms polkit.service 121ms systemd-sysctl.service 117ms snap-snapd-16300.mount 115ms modprobe@pstore_blk.service 114ms sys-fs-fuse-connections.mount 111ms systemd-sysusers.service 107ms systemd-tmpfiles-setup.service 106ms run-rpc_pipefs.mount 104ms dev-loop7.device 104ms sys-kernel-config.mount 103ms tmp.mount 98ms rpcbind.service 90ms modprobe@pstore_zone.service 85ms ifupdown-pre.service 79ms console-setup.service 79ms modprobe@ramoops.service 78ms snap-gnome\x2d3\x2d38\x2d2004-117.mount 75ms setvtrgb.service 72ms plymouth-read-write.service 69ms nfs-blkmap.service 68ms user-runtime-dir@1000.service 67ms systemd-update-utmp-runlevel.service 63ms systemd-tmpfiles-setup-dev.service 61ms snap-chromium-2079.mount 60ms user-runtime-dir@0.service 57ms sysstat-collect.service 56ms snapd.socket 55ms armbian-hardware-monitor.service 53ms nfsdcld.service 43ms sysstat-summary.service 37ms systemd-journal-flush.service 16ms e2scrub_all.service 0 Quote Link to comment Share on other sites More sharing options...
Urmas Posted September 2, 2022 Author Share Posted September 2, 2022 I found the problem but I don't know how to get reed of it. booting to the desktop should start and then reboots the OS after that desktop works. 0 Quote Link to comment Share on other sites More sharing options...
Urmas Posted September 3, 2022 Author Share Posted September 3, 2022 found easier display modifying commet out #setenv disp_mode "1024x600p60" mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr then set it armbianConfig.txt disp_mode "1024x600p60" extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/1024x600.bin video=HDMI-A-1:1024x600@60 in this way you be abele to change easily 5" and 7" lcd displays - just change the display resolution however the OS loading is still long time I understand drm_kms_helper generates the 1024x600.bin file but it does not save it or I just can't find it. Does anyone know where is it? 0 Quote Link to comment Share on other sites More sharing options...
Urmas Posted September 8, 2022 Author Share Posted September 8, 2022 Hi there, I have a problem with startup boot loader showing script when I added to the armbianConfig.txt file extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/1024x600.bin video=HDMI-A-1:1024x600@60 I lost boot startup loading script text on display - does not show anything until the desktop loaded. ones is desktop loaded it is very good resolution - want to keep that. but I need startup loading showing something image or startup loading text. Does anybody knowing how to do that? 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.