DevShanky

Members
  • Content Count

    85
  • Joined

  • Last visited

About DevShanky

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. I am wondering if this script would break nand-sata-install since the base Armbian images are single partition while the new encrypted image on SD card is having a separate Boot and Root partition. If this is the case then how can we move the image to eMMC from SD? -R
  2. This is a very good tutorial. Thank you for posting this here. Armbian build has an option CRYPTROOT_ENABLE=yes that can enable encrypted root system via custom build. See here. Is there some overlap here? -R
  3. Hi, I am unable to see boot splash logo on device startup with recent builds (5.9.rc#) which was working earlier. The build shows option to include boot splash which is related to frame buffer settings. However including this option does not show boot logo. Are there any signification changes in this area? -R
  4. A corrupt or faulty SD card can also cause problems. You can get a good quality SD card and try again. -R
  5. Did you Copy u-boot-s905x2-s922 to u-boot.ext? Just checking... -R
  6. Pirated? I am sure I am missing some thing here. It would be kind of good to be enlightened or informed here so this is not repeated unknowingly. Thought Linux was in spirit based on GPL or MIT license. Was not aware the dtb definitions could be proprietary. I see most of them in https://github.com/torvalds/linux/tree/master/arch/arm64/boot/dts/amlogic May be I am truly missing something! -R
  7. It was a normal technical discussion on dtb support for a S905X3 device. What can I say!
  8. I can see response to my post but not the original posted text.
  9. Strangely I am unable to view my message on this forum now.
  10. I am not working for on any commercial or for profit project. Looks like you have some very good thing going on here so this is just a feedback. Please ignore if you think it is not important. There are no expectations that this will be fixed. I tried buster desktop. I am not able to see the boot logo. Verified the config file you have listed and they are as expected. Plymouth also does not work. May be it just one of those orange pi thing. It is just that looking at a blank screen for 20-30 seconds when device comes up is odd. I believe kernel enabled bootsplash h
  11. Has anybody here had success with running Single Armbian Image on RK3399 Orange Pi 4? I tried using the latest image with revised procedure using extlinux. There are two dtb available in rockchip folder. 1. rk3399-orangepi-4.dtb. No HDMI with this image. 2. rk3399-orangepi.dtb. HDMI works only on 1024x728 resolution and no sound. The startup screen and u-boot messages with both screen were hazy and jumbled. If anybody here had got this working, let me know if these are the correct dtb files? Thanks -R
  12. @Igor Kernel enabled Bootsplash works great on the recent 20.08 on Orange Pi 4. However there is a delay of around 20 - 30 seconds before this Bootsplash comes up. Is is possible to enable bootsplash on u-boot also on this image? I built a custom image 20.08-trunk with option "Kernel enabled bootsplash' disabled however could not see u-boot bootspalsh on this image. -Rajesh
  13. The latest build fails if this driver is selected to be build with the kernel. Realtek 8192E USB WiFi (RTL8192EU) [N/m/y/?] (NEW) y --> fails / m --> succeeds If 'm' or module is selected then the build succeeds. -R
  14. Build on Windows 10 WSL2. I was able to build the image from source code on Build-Armbian on Windows 10 (WSL2) Ubuntu 18.04. Used NO_APT_CACHER=yes and cloned the folder in ~/. Had multiple build failures without these settings. Thought I would share, just in case if someone is interested to use this environment to build images. -R
  15. Would you by any change have set of instructions to do a build on Win 10 / WSL2? Microsoft has finally rolled out Wind 10 2004 with WSL2 enabled by default. I tried the build on Windows 10 after upgrade. The scripts exits with not supported build environment not supported. I also have docker running on Windows 10 but looks like WSL2 os more convenient and better option. -R