Jump to content

L Jumadi

Members
  • Posts

    59
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Willx Mine not working also 1st, need to open the box and photo the chip.. then seek in forum, Fortunately my wifi chip already known on rockchip forum then ppl here can help to connect it on the build. Bluetooth Im not aware as Im not using it atm
  2. @heiko910 My SBC that I already use for Klipper is RK3318 version (H96 max v11) I bought after my Tanix (that use nearly same chip as transpeed speed). Before posting here Im already give up with Tanix as need to open box set up serial display.. so I tought is easier just buy one again that already can use. While waiting new one or after I success with last one (I forgot already), I have spare time and have CP2102 around also (from my previous hobby building quadcopter with STM chip) but I really dont want solder anything (too small for my old eyes, lol) I just slip the stripped wire to the hole TX RX Ground and use tape to hold it in place and try to see whether it send data to computer.. voila I get data from this little machine, and try to asked here.Then @Nick A help and all worked as I needed :) Right now Im still building (mod/designing) CoreXY from used Ender 5 then may be my Tanix got use :)
  3. @MMorales @dale on Jefflessard openvfd version setting brightness its as easy as write number to /sys/class file, no need other service :)
  4. Ok after long search.. I found that your softdep solution prevent my install option, so I just do it all on install option in /etc/modprobe.d/tm16xx.conf install tm16xx /sbin/modprobe -q ledtrig_timer; \ /sbin/modprobe -q ledtrig_netdev; \ /sbin/modprobe -i tm16xx; \ echo boot > /sys/class/leds/display/value Now it display boot imediately so my eyes cant catch up if 8888 ever show :P
  5. hi @Jean-Francois Lessard Searching further how to early change display, I found using this udev rules can change it quick after your 8888 displayed, better than systemd ACTION=="add", SUBSYSTEM=="module" KERNEL=="tm16xx", RUN+="/bin/sh -c 'echo \"bo ot\" > /sys/class/leds/display/value'" Edit: Should be faster using modprobe install option but dunno why its never executed on armbian tough its correct config Maybe then seaching how to make your driver load earlier
  6. About early LED show seems its on generic LED can be set at u-boot but maybe thats not using any driver just signal one or few individual led :) Maybe Android version using that way also, sure manufacture worker did it and not publish as opensource
  7. Just FYI @Nick A While working further with Jefflessard I found that all modules in your build not included in images created, Tough it compiles as module and already make the .ko file in the /sources/linux-kernel-worktree/devices. I dont know it is by design or not.. while Im afraid to update linux-kernel-image so I just copy (some modules).ko to /lib/modules/6.7.12-edge-sunxi64 run depmod and its ready to modprobe :)
  8. About /lib/modules/$(uname -r)/kernel/drivers/leds/trigger/ I already investigate as Im building the images myself I can check trigger config is modules but seems the image created not include all modules, I will report the creator, thanks
  9. @Jean-Francois Lessard already try your service then try to boot.. it display 8888 longer than a blink boot after followed by time display. So I stick to 8888 only better :) at least have displaying something long before the time. Dunno on Android the led display is faster show when device just like to power on, Its Android base on Linux also with even older kernel, lol. Maybe many unused service or other at kernel loading removed, but after that Android longer loading than armbian
  10. ls /lib/modules/$(uname -r)/kernel/drivers/leds/trigger/ Error: No such file or directory Before I found the trigger with cat /sys/class/leds/display::colon/trigger which result: none usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport disk-activity disk-read disk-write mtd nand-disk [heartbeat] cpu cpu0 cpu1 cpu2 cpu3 activity default-on panic mmc0 mmc1 mmc2 stmmac-0:00:link stmmac-0:00:100Mbps stmmac-0:00:10Mbps thanks for service suggestion, will try and experiment with it.. hope can display early as I am still not so familiar with systemd
  11. @MMorales @Nick A Hi, I already success with Jefflessard version of openVfd with some minor error with my build, can check the forum if you try and have problem: Just in case you interested, I prefer it because it starting to display something when driver initialized so we early know the box starting and not hang up :) then can display timer or whatever you like after.. and setting just via bash scripting than writing other language code :)
  12. Trying it rightaway give error: modprobe: WARNING: Module ledtrig_timer not found in directory /lib/modules/6.7.12-edge-sunxi64 maybe my armbian version or sunxi version not provide it :P
  13. After trial error I change the error line with echo heartbeat > /sys/class/leds/display::colon/trigger then it successfully display time with colon heartbeating :P Sure will be nicer if we can change 1st time appearance than 8888, but I already satisfied with current stage
  14. @Jean-Francois Lessard thanks, with your help now I know which file to check.. dunno maybe because my header using old version. Step I do: kernel header reinstalled cat /lib/modules/$(uname -r)/build/include/config/kernel.release correct -> 6.7.12-edge-sunxi64 I try sudo make install it error like I describe before, then I re-check cat /lib/modules/$(uname -r)/build/include/config/kernel.release wrong -> 6.7.12 reinstalled header again, check kernel.release correct and try make clean then make module --> success then I wrong type make module-install without sudo error permission denied, redo correct sudo make module-install error because build directory gone, recreate it and check kernel.release still correct, so I re-try with correct order make clean, make module ==> success, sudo make modules-install error: Entering directory '/usr/src/linux-headers-6.7.12-edge-sunxi64' make[3]: *** No rule to make target 'modules.order', needed by '//lib/modules/6.7.12-edge-sunxi64/modules.order'. Stop. But accidentally I check /lib/modules/6.7.12-edge-sunxi64/updates seems tm16xx.ko re-created so I try reboot It seems modules loaded correctly as LED power on 8888 awhile then blank .. dmesg said Display initialized successfully trying sudo display-utils -c its correct display 1234 and colon, so I try starting display.service but status is failed I try manually display-service as root it error: /usr/sbin/display-service: line 68: echo: write error: Invalid argument I check its the line number mentioned: echo timer > /sys/class/leds/display::colon/trigger Maybe there is error on my installation before but sure the driver already correct :) .. thanks
  15. Make fdt success as usual but when try reinstall driver got error. I reinstalled header.. trying make success but when make install error permission denied. so sudo make install error: No rule to make target 'arch/arm64/tools/gen-cpucaps.awk', needed by 'arch/arm64/include/generated/asm/cpucap-defs.h'. Stop. then I re-read your read.me no need make just make install, I try make clean and make install same permision denied then sudo make install same as above without creating tm16xx.ko I try to make and move tm16xx.ko manually then reboot, dmesg said: [ 10.187780] tm16xx: version magic '6.7.12 SMP mod_unload aarch64' should be '6.7.12-edge-sunxi64 SMP mod_unload aarch64' I dunno whats wrong, as I try re-make liberman and modules_install still ok
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines