• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map





Everything posted by jock

  1. Hello @nokirunner, glad to see you! Are you using a recent image or it is an older installation? I ask because recent images with legacy kernel get all the multimedia features enabled, including hardware 3D acceleration, using an autoinstalling media script that can be downloaded on first page. Mainline kernel images instead should already get 3D acceleration out of the box, despite having slow X11 experience for now.
  2. Hello, very glad to hear about a real rk322x board ReSpeaker board was actually what gave most of the traction in the initial phase thanks to their documentation, studied mostly by @fabiobassa Anyway let's get on the tracks. I don't have a board like yours but will try to help. First of all to make life easier, always provide u-boot and dmesg logs. Now the Respeaker board is somewhat different from a regular tvbox and for this reason rk322x-config is useless for you. If you applied the respeaker patches, you should have a file rk3229-respeaker-v2.dtb in /boot/dtb. If so, change the line fdfile=rk322x-box.dtb to fdtfile=rk3229-respeaker-v2.dtb in /boot/armbianEnv.txt and reboot the machine. This is essential to let the kernel know what is the hardware of the respeaker board. Without this, it will be much harder getting farther. Looking at the snippet you provided, the mmc2 device is not the internal eMMC, but the SDIO Wifi chip. It looks to me also that it does not get configured right in your current setup. Using the respeaker device tree may definitely help here! The ap6212 firmware is already there in /lib/firmware/brcm/ap6212, and the kernel module able to drive the wifi chip is brcmfmac. brcmfmac is a bit "stupid" about firmware directory, because it won't look in ap6212 directory, but will just look in /lib/firmware/brcm, so probably you may want to copy the content of ap6212 into its brcm parent and then try with modprobe brcmfmac to see what happens. But all of this can work only when the SDIO bus is working correctly, ie: you need the proper device tree in place.
  3. Hello, your box will probably work fine, just follow the instructions on first page. About the best image, it is up to what you want to do with the box. If you want to set up a server, prefer the Debian Minimal. If you want a desktop experience Ubuntu Focal already provides X11. Legacy 4.4 kernel has most features and is most stable, mainline kernel is for experimentation
  4. It is much better to go with Lima driver (eg: mainline kernel) nowadays, which should provide everything you need already packed and working, including opengl and opengl es via mesa. However if you want to test Mali driver, read carefully this thread and compile glmark2 to test it.
  5. Ok, for start the gpu@ff300000 node is clearly missing the status = "okay" property. It looks like it is missing some other things, for example I don't see an operating points table for the GPU. You may try to compile the dts back to dtb and see what happens, but honestly I think you may have more luck trying a nightly armbian image with latest kernel and updates or even compile Armbian yourself.
  6. Hmm, it seems like you did not link the dts file. Yes, the vendor kernel is only 4.4, and actually you're on 5.4 which is mainline. Here, on my rk322x targets, I managed to get lima working fine with mali 400, which is fundamentally the same as Mali 450 but much slower. desktop is really slow with Lima enabled, and some games I tried also did not render perfectly, but Kodi instead was plenty usable. Wasn't able though to get hardware video acceleration yet, but I guess it's just a matter of consolidation from Kodi, ffmpeg and kernel developers, in fact LibreElec already has Mainline Kernel + Lima + hardware video acceleration in Kodi for h.264.
  7. Can't see anything about lima in the kernel dmesg log you posted. Are you sure you got the right device node in the device tree? It is essential, otherwise the hardware will never be detected by the kernel. Note that when the node is present and enabled (look for status="okay") in the device tree, the lima module is automatically loaded by the kernel. As a side note, you don't need armsoc driver, everything should be handled by default modesetting driver. You should also not blacklist any other module. configuration bits instead are important: I get black screen if I miss things there. Little note: my experience is based upon rockchip rk322x and amlogic s905, but it should be the same on rk3328.
  8. You need a minimum of strategy then. The easier way I could think of is burn the pristine image to an sdcard, boot the system and made the necessary changes you are comfortable with, read back the sdcard and you get your already setup image which can be distributed back. But this is a very very rough solution and I would not recommend it. At last you get an image which is set up with the partitions sized for the particular sdcard (armbian resizes itself during first boot to fill the entire media) and also requires manual steps to replicate the same behaviour when you want to create a new image. A nicer solution would be using the armbian user patches and user scripts to create a systemd service which automatically starts at boot. Probably you want it to run in MultiUser target, which is the last step of system initialization. The systemd service in turn runs your script/application. You need to master systemd a bit, but creating a basic systemd service/module is quite easy. Debugging can require some challenge though (systemctl status, journalctl are good friends here). This chapter of the armbian documentation may be useful to you, once you write your scripts and patches and put them in the right directories, you can use the armbian build system to produce auto-setupping images. Rockchip (not rockwell) has some command line and GUI tools to write images from a PC directly to eMMC of tvboxes via USB cable, but this is not always straightforward. Other vendors probably have tools too, but I'm not aware of.
  9. In my opinion, your choice is not a great solution, either because putting a script in /etc/init.d does not automatically triggers it and also because you would end up cloning a system which is half-started. If you can boot from sdcard - and guessing from your question, you can - just boot from sdcard and put the .img file on the sdcard itself. Once booted, use dd to write the .img file on the internal emmc device. Otherwise you may be able to use some other tools and external USB to PC cables, but this depends on the platform and chip vendor. For example, Rockchip has the tools to do this.
  10. Well, many things changed, the installation process is much easier than ever and hardware support if far superior thanks to device tree overlays. I think you may safely remove them
  11. Officially built images on Armbian servers have been updated and now are working perfectly.
  12. Analog sound is not yet in mainline kernel, it works only on 4.4. Hardware acceleration also is still partial on mainline kernel and it is in heavy work in progress by LibreELEC and kernel teams. For multimedia features I suggest to stay on kernel 4.4 for now
  13. I guess it will never see mainline kernel again. The company developing the chip went bankrupt and left this horrible driver that is so messy and confused no one wants to lose time with. The lack of documentation makes things even worse and since it is a low performance device is another disincentive to bring it back to life.
  14. Ok, images on the first page are updated and working, they're safe to use and install in flash. Images from download page are still broken, server will decide when they will be refreshed
  15. The rk322x-config script will tell you the name (if known) and the vendor/device ids. From the vendor and device id, you may also google around if rk322x-config does not autodetect it. If you got 3030:3030, you have the ssv6051p or 6256p chip. The first one is only supported in legacy 4.4 kernel, the second one is not supported at all. The manufacturer of the chip, aside from providing a crappy driver, was also so dumb to give the very same device ID to two different chips, so to be sure what you got you need to read the signature on the chip itself.
  16. Ok situation is clear now... turned out that while cleaning up things for mainline inclusion I made a separate branch (rk3229-squash) and by mistake removed the OPTEE binary blob from that Stupid u-boot, during compilation, did not say anything about the missing file... You instead most probably cloned the rk3229 branch which was perfectly fine. If you are testing the image from sdcard it works fine because the good bootloader that is getting engaged in the eMMC. But don't burn the new image in the eMMC, or the safe bootloader will vanish! I'm recompiling things right now, so the balance to the force will be restored soon
  17. Those seems broken too! U-boot seems to be broken, but the last change there is one month old
  18. Hello guys, good news! RK322x now is mainlined into armbian! This is the download page: From now on your board will get all the benefits of being part of Armbian ecosystem, including kernel updates! Support and developing images will still be provided in this forum thread as usual, so for the thread followers nothing will change edit: I'm in the middle of testing the images and it seems there's something wrong with the bootloader, so don't download them yet!
  19. We realized that product names and board signatures are totally unreliable for hardware mapping, so I moved to device tree overlays. All hardware combinations are covered simply by a bunch of device tree overlays. rk322x-config script has been adapted accordingly so, from now on, it should be simpler and much less error prone!
  20. Well, NAND are strange beasts. I was talking some days ago with @fabiobassa and he has a box with NAND flash which is rebooting fine, while most of them don't. Device tree should not influence ssv6051 driver, which is so crappy it always loads even if there is no sign of it in the device tree. To handle that rk322x-config script blacklists/unblacklists the module if necessary. You can still do modprobe ssv6051 and see what dmesg log says, but beware: crappy driver = crappy logging. I don't handle that, but seems strange to me. It hangs just after running the script or during a specific operation? If doing echo timer > /sys/class/leds/auxiliary/trigger makes the red led blinking, then led-conf1 is the led wiring configuration for your box. Otherwise you have a different wiring that I have not yet encountered. It is just clock speed at the moment. Thanks for the detailed report of what works and what not, I have submitted all the patches to mainline Armbian for review so I hope it will be merged soon!
  21. Please follow the instructions on first page, armbian images are not designed to boot from sdcard as-is.
  22. Uhm, sounds very strange, the "inconsistency" is right to be there, that's just because the image is smaller than the whole NAND and later armbian will resize the partition to the full size, but other than that the filesystem should be clean. I suspect something went wrong during the burn process, but this is puzzling as long as you reinstalled the legacy image correctly. I will double check the image and maybe ask you to do another test if you don't bother Thanks in the meantime! edit: the image seems ok, could you please download a fresh copy of the multitool and try again? You can also try the Armbian Ubuntu Focal Minimal 4.4 on first page image in alternative, but a newer copy of the multitool is essential because I changed the step-nand process to bring an overlay-capable u-boot.
  23. I need a hand from people who has a NAND board and could sacrifice the system on it for a test (you can either do a backup using multitool first ) I changed the way the device tree and rk322x-config works to be more effective, simpler and less prone to errors. If you could download this test image (Debian minimal, console only), burn it on NAND, configure using rk322x-config, shutdown the board, unplug and replug power and confirm everything works ok, I would be really glad for any report. This will speed up moving to mainline armbian, which could really happen this week! Thanks!
  24. Indeed, no big deal at all. Old chip and old crappy driver, I could not do more than 10Mbit/s TX even if the box is close to the AP. The box I got here is picky about the interface: wlan0 always crashes the driver, I must use p2p0 to be able to use it. I have a question for you: do your board has one or two leds? Are they working well with the devicetree/board profile you selected?
  25. I resume the thread, because had the chance to verify the same condition. Panfrost with GPU @600Mhz is having issues on my setup too on recent 5.6 kernel. I don't think it is due to low voltage, since the voltage in the opp table is the official one and also I extensively checked in the past against proprietary mali stack and never had any issue. Turning 600 Mhz OPP entry into 500 Mhz results in a good behaviour by Panfrost. 500 Mhz was removed some time ago due to clock rework by @Myy, but currently seems to work pretty fine. Maybe it could be reintroduced?