usual user

  • Content Count

    142
  • Joined

  • Last visited

About usual user

  • Rank
    Elite member

Recent Profile Visitors

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

  1. Restudy your referenced spec. The default serial console is located at "Debug UART".
  2. You probably have a misunderstanding about what this thread is about. It is about to verify if my DT overlay is working in Armbian environment so it can be integrated in Armbian for out of the box operation of Armbian users. It is sufficient to aprove it is working in a similar manner as for me. If a special USB-C device does not work, this is possible to discuss with the patch autor. PD functionality is for NanoPC-T4 out of scope because it has no PD features desined in hardware. The NanoPC-T4 can e.g. operate an additional display via a cost-effective USB-C DP alternative mode adapter.
  3. IIUC the PINE64 and Firefly image use legacy kernel and don't use this particular kernel patch. Now that the only difference in our setups is the USB DP adapter, IMHO the only sensible way forward is to swap the dock for another DP alternate mode adapter. Swapping the board will not eliminate an incompatibility between the kernel patch and the dock. The USB-C hardware (DTB) seems to be set up correctly otherwise the USB functionality would not work. The DP alternate mode uses the same hardware lanes but only protocolly differently. Off topic: Out of curiosity does the offered u-boot influenc
  4. Okay, I can only imagine two reasons for this still not working. Either the DP kernel patch doesn't support your DP hardware or u-boot doesn't set up the NanoPC-T4 as needed. To rule out u-boot, apply the extracted u-boot, which can be found here. E.g: dd bs=512 seek=64 conv=notrunc if=u-boot-rockchip.bin of=${DEVICE} ; sync and test. Replace "${DEVICE}" by your micro-SD device.
  5. IIUC the extlinux.conf is working with the current kernel for you. The USB keyboard is not expected to work, because mainline uboot does not yet have the necessary support enabled. Boot option selection is only available via serial console for now. Extract the tar-gz kernel archive, which can be found here, in your /usr/lib/modules/ directory. E.g.: tar -C /usr/lib/modules/ -xzf 5.10.0-98.fc34.aarch64.tgz and reboot. Extlinux.conf will pick it up by the default option. To fall back to original kernel without boot option selection, rename the symlink /usr/lib/modules/linux-default,
  6. The image was provided to identify a boot.scr magic deficiency. Also Fedora 31 is EOL, so image RIP. Since there seems to be more shortage there, as long as no one who cares for Armbian shows up and maintain the boot.scr magic, you are on your own.
  7. It is a hardware flaw due to a missing pull resistor and a software quirk. A fix is discussed here but as long as noone with an affected device confirms it, probably nothing will happen.
  8. IMHO I think from version 5.10.0 the path won't change again because generic node names have been around since then. Therefore, the same DTBO can always be applied. But as long as the hardware setup doesn't change, there's no reason to ever change the DTB. Therefore, after an update, restoring the DTB from a persistent location would also be an option. But I guess you will have more fun to keep having the boot.scr magic in place. And tinkering with boot.scr magic opens even the option to load the DTB from the persistent location direct or choose a different DTB file name that wouldn't be
  9. OK, here is the preperation for our experiment: - create an extlinux directory in your root, e.g. mkdir /extlinux - copy the attached extlinux.conf into it - reboot and check if the device is now booting with distro-boot method The auto boot timeout is set to 10 seconds, so be patient. If this is working I will upload my kernel and you can put it in for the test. extlinux.conf
  10. Applies for me flawless. fdtoverlay -V Version: DTC 1.6.0 fdtoverlay -v -i imx6q-hummingboard.dtb.orig -o imx6q-hummingboard.dtb imx6q-hummingboard-gpio.dtbo input = imx6q-hummingboard.dtb.orig output = imx6q-hummingboard.dtb overlay[0] = imx6q-hummingboard-gpio.dtbo The overlay is written for DTS comming with 5.10.0 kernel. Over time, some node names have been renamed to improve homogeneity. Attempting to apply it to an older release may fail.
  11. Maybe somthing like imx6q-hummingboard-gpio.dts. Compile it with DTC and apply it as follows: mv imx6q-hummingboard.dtb imx6q-hummingboard.dtb.orig fdtoverlay -i imx6q-hummingboard.dtb.orig -o imx6q-hummingboard.dtb imx6q-hummingboard-gpio.dtbo But since I don't know your PAD configuration requirements, I only chose one random one. You have to look up your needs yourself. imx6q-hummingboard-gpio.dts
  12. Just switched to 5.10.0. I noticed that the DTB has changed multiple node names. As a result, my user space could no longer apply all configuration quirks due to the changed paths in sysfs. Useing a DTB before 5.7.x resolved all observed regressions for me. Perhaps it is also worth trying in your case to run the current kernel with a pre 5.7.x DTB as a test.
  13. Unfortunately my config and the armbian config diverge quite a lot and it is not easy to identify the relevant differences. The only help I could offer further is to run your environment with my kernel to identify whether the kernel is the culprit or something else. If you want to try this, you have to post the output of the following commands: cat /proc/cmdline ls -hal /boot lsblk -o +PARTUUID so I can prepare the experiment.
  14. Either fix the boot.scr magic or switch to distro-boot by inserting an extlinux.conf. For background maybe start reading here and here. I usually write DT-overlays for my board extensions and apply them to the base DTB.
  15. Useing imx6q-cubox-i.dtb for hummingboard carrier won't work. You need imx6q-hummingboard.dtb. In my environment I use mainline uboot build with mx6cuboxi target and distro-boot method. This way uboot identifies at which SolidRun imx6 device it is running and selects the appropriate DTB. IIRC Armbian uses also mainline uboot but boot.scr magic to select the DTB.