Capeschae

Started to test on Armbian_23.5.1_Orangepizero2_jammy_current_6.1.30.img.xz. Currently running as a SAMBA server. - Reboot OK - Power down OK - LAN OK - USB hard drive OK - HDMI NOT OK (don't know if this can be turned on somehow) Seems to be running stable for now. @Werner: Thank you for providing this with the "ugly EOL-kernel". Seems to run nice as a SAMBA server. I will test some more, like update/upgrade and tightvncserver to see if things keep running smooth. Nice to see the OrangePi zero 2 running on 6.1.30.

LAN working on Minix NEO X7. For now I gave up on trying to find the IO-pin that controls the LAN power on the Minix NEO X7 board. By making a hardware modification, involving removing a voltage controller (because unfortunately 1 pin broke during the modification) and placing a wire to get the LAN power supply from another voltage controller, I got LAN up and running. I will leave it running for a couple of days to see if nothing breaks. I can state that the drivers for the Realtek 8152B USB ethernet adapter are working.

In a dmesg from a Minix Neo X7 running NETBSD that I found here, it says that LAN works. I find following info regarding GPIO: gpio: 0x0000a000 0x00000104 -> 0x0000010c gpio: 0x0000a004 0x00000104 -> 0x0000010c gpio: 0x0003e000 0x00000000 -> 0x80000000 gpio: 0x0003e004 0x00000000 -> 0x80000000 gpio: 0x00080000 0x00000000 -> 0x04000000 gpio: 0x00080004 0x00000000 -> 0x04000000 gpio: 0x0000a000 0x0000010c -> 0x4000010c gpio: 0x0000a004 0x0000010c -> 0x4000010c gpio: 0x00080000 0x04000000 -> 0x04000400 gpio: 0x00080004 0x04000000 -> 0x04000400 Does anybody know how this relates to the GPIO settings in our Armbian DTS? In the DTS there are only gpio0 to gpio3 with different address ranges.

Minix Neo X7 LAN via RTL8152: It seems that the RTL8152 is not powered on after booting. I cannot measure any supply voltages to the chip. When booting from Android NAND the supply voltages are there. I expect that there will be a GPIO that switches the voltage regulator and I'm going to look into this. But it will be a search for the needle in the haystack.

@BOBAH Just FYI. It seems that the dts editor in armbian-config uses the "first" dtb it finds in the /root/dtb folder. Because there were multiple dtb files in my dtb folder a different one was picked than the one I have configured in my extlinux.conf file. Removing all but one dtb files from the /root/dtb folder did the trick. After this I edited the clock rates to try to get LAN working, as you mentioned before. Unfortunately, but as expected, this did not have any results for my Minix NEO X7.

Thanks for pointing me in the right direction! It seems that the dts editor in armbian-config uses the "first" dtb it finds in the /root/dtb folder. Because there were multiple dtb files in my dtb folder a different one was picked than the one I have configured in my extlinux.conf file. Removing all but one dtb files from the /root/dtb folder did the trick.

When using the dts editor in armbian-config, a different dts is shown than the one that I defined in extlinux.conf. For my RK3188 based minix neo X7, I decompiled an existing dtb from boot/dtb into a dts file using dtc on my Linux computer. I edited this into a new dts and compiled it into a dtb. I placed this under the name rk3188-x7.dtb in my boot/dtb folder, referenced to it in extlinux.conf and my system booted using this dtb (checked in dmesg). However, when I try to use armbian-config to edit my dtb/dts, it shows a different dts. Any idea how or where to change this so I can easily work on my dts?

Yes, I understand. That is what I tried to do, but the dts that is shown in the text editor is not the same as the dts that I refer to in /boot/extlinux/extlinux.conf. The dts that I can edit in armbian-config is for "BQ Edison2 Quad-Core" and is different than the one I use. So I was wondering which one will be used when I edit.

@BOBAH I just installed vncserver to have an easier way to edit the dts. However, when I go into the editor I find a different dts that does not reflect my modifications, to be the current dts. It is different than the one I referred to in extlinux.conf (FDT /boot/dtb/X7alpha1.dtb), which is from a dts modified to get my system run stable. Any idea which DTS is used?

This is the output for "lsusb -t" on the ARMBIAN system: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=rt2800usb, 480M |__ Port 4: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M Currently an external Wifi adapter and an external HDD are connected to the USB. It seems like the internal LAN adapter is not recognised or the corresponding drivers are not available.

ifconfig does NOT contain eth0, only "lo" and "wlan0"(external USB-Wifi) In dmesg I find that the USB devices found include the internal USB Hub (USB2514B) and the EXTERNAL WLAN stick (Ralink RT3571). The internal LAN via USB (8152B) is NOT detected during boot. Hardware is OK as it works properly with my original Minix X7 firmware. Also , when using lsmod there is no 8152B.

Whatever I try I get errors like: could not open moddep file '/lib/modules/3.0.36+/modules.dep.bin' Errors always refer to version 3.0.36+. When checking my version I get: root@debian:/lib/modules# uname --kernel-name --kernel-release --machine Linux 3.0.36+ armv7l HOWEVER... In /lib/moddules I found following folders: root@debian:/lib/modules# ls 3.2.0-4-vexpress 3.4.79-r0-s-rm1+ But no 3.0.36+. Might there be files in those folders that could help for a kernel configuration analysis?

So, if it is supported in the build, it actually should work without any entry in the dts file. That makes sense as it is recognised as a USB device. Should any LAN references in the dts be removed? Could the LAN references in the dts somehow interfere?

No succes: root@debian:~# cat /proc/config.gz > config.gz cat: /proc/config.gz: No such file or directory root@debian:~# Might some info from dmesg help?

Here you go: root@debian:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 002 Device 003: ID 0bda:8152 Realtek Semiconductor Corp. root@debian:~#