• Content Count

  • Joined

  • Last visited

About ethDreamer

  • Rank

Recent Profile Visitors

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

  1. @Igor After a bunch of experiments I WAS able to get the LCD to work with Armbian!..... using lubuntu's bootloader. The problem has been narrowed down to uboot then. If you could give me any ideas on getting it to work with Armbian's bootloader that'd be great. Here's what I did for anyone who wants to follow: Edit Armbian buildscripts to add kernel.img to the kernel build targets (could also just set KERNEL_IMAGE_TYPE="Image kernel.img") and have it copy the resulting kernel.img file to output/images. Once the desktop sd image is built, run: # this will setup the ima
  2. I should mention that the display backlight does seem to turn on with the legacy kernel, but it's a black screen and X doesn't detect it. I've even tried copying /etc/X11 from the lubuntu build but that didn't do anything either :/
  3. Sorry should've mentioned. I'm using the legacy kernel. Though it doesn't detect the display with either one :/
  4. FriendlyELEC sells an 11.6inch eDP FHD LCD Display with Capacitive Touch for the nanoPC-T4. I'm trying my hardest to get it working with Armbian. Unfortunately, Armbian doesn't seem to detect the display: root@nanopct4:~# xrandr --listmonitors Monitors: 0 It works in the stock lubuntu image they provide so I'm trying to gather as much configuration information as I can from lubuntu to see what I need to do to get it working. I want to try a few different experiments.. I have a kernel.img file from lubuntu that I'd like to try booting with Armbian but I don't understand uboot very w
  5. I can understand why you're frustrated doing all this for (essentially) free. Let me see what I can do to help. Can you answer some questions for me? I do know C and I am a software engineer, but I've never worked with the kernel before and my low level/device driver knowledge isn't so good. Is the learning curve for this type of work too steep to have this be my first project? > It's expensive work If it is too difficult to learn, do you have any idea how expensive this would be? I do appreciate you keeping the lights on man. I know this project wouldn't exist withou
  6. Yup that did it. It boots fine with the latest commit 716bd3b9dc.. as long as HDMI is unplugged. If HDMI is plugged in, it will enter that boot loop. I can plug in HDMI after the boot loader gets to this point: I feel like I'm not going to be the last person to run into this issue so I hope they find this post.. Side note: is there any way to have the kernel redirect output to the serial console after this point? Because otherwise I don't see anything until the system reaches the login prompts. I'm more than happy to be a tester for this.
  7. So I noticed my NanoPC-T4's will not boot an image made with the latest armbian build script. I did a binary search on the commits and tracked down the breaking change: commit 75d0f64e3d75e7c34466871b9723ef1a238609d8 <- THIS COMMIT AND ANYTHING AFTER IS BROKEN Author: Piotr Szczepanik <> Date: Fri Apr 17 21:30:37 2020 +0200 Switch rk3399 to u-boot v2020.04 (#1873) * Switched rk3399 to u-boot 2020.04-rc4 * Switched rk3399 u-boot to v2020.04, synchronized configs * Updated to u-boot v2020.04 final * Fixed OrangePi 4 device tree reference
  8. I've built everything into the kernel that I can think of: Device Drivers ---> [*] USB support --> [*] USB Type-C Support --> ** built everything other than alternative mode / display port drivers [*] PHY Subsystem ---> ... [*] Rockchip TYPEC PHY Driver Nothing seems to get it working (other than using the legacy kernel). If I plug in a USB type-c ethernet adapter, the light stays on solid but nothing shows up under lsusb.. I'm not sure what else to try. Any help would be appreciated.
  9. I've been working on a project to boot a custom kernel on my NanoPC-T4. I haven't gotten too far though because as soon as I make the smallest change to the source, everything goes to hell (see below). I've built 3 images following EXACTLY the same process. All I did was change the KERNELBRANCH variable in userpatches/lib.config to point to different branches in the same repository. For completeness, here's my lib.config (which simply points to my fork of ayufan-rock64/linux-mainline-kernel): KERNELSOURCE='' KERNELBRANCH='branch:BRAN
  10. Okay so if I understand you right (and for anyone who might read this in the future) I just need to create the file userpatches/lib.config containing: KERNELSOURCE=[github url of kernel source] KERNELBRANCH=[existing branch] LINUXCONFIG=[existing config file] assuming that repository hosts a bootable kernel on that branch that can be successfully compiled with that config - then this is all I need to do to have the build system continue as usual and create the image for me? Thanks for your help I'll try this when I get home.
  11. I was actually able to successfully do the opposite (merge commits from ayufan-rock64/linux-mainline-kernel into anthraxx/linux-hardened). I thought this might be easier since there wasn't a whole lot of commits to aufan's branch after forking from torvalds/linux. Either way I can't test either kernel until I know how to integrate a new kernel source into the Armbian build system.
  12. I hope you can understand my question just from the title but here's more information in case you need it. BACKGROUND ON MY END GOAL IN CASE YOU HAVE ADVICE: I'm attempting to create a hardened linux image for running on my nanoPC-t4. I gotta give you guys props because Armbian appears to be wayyyyy ahead of the alternative distributions I checked out (gentoo/arch/lubuntu) in terms of support/customizability/documentation for ARM development. As a first step, I'm trying to build & boot a hardened Linux kernel. After some googling, I settled on this repo as my best option for free &