Search the Community

Hi, guys. I'm using the last Armbian Cubieboard image (Armbian_23.11.1_Cubieboard_bookworm_current_6.1.63.img.xz) on my "Gemei G9" Allwinner A10 tablet. But via serial/UART the boot process stuck forever in "Starting kernel ...". Any tips on how to get the kernel to start? Thanks in advance Here is my boot log: U-Boot SPL 2023.10-armbian (Oct 13 2023 - 22:19:41 +0000) DRAM: 1024 MiB CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2023.10-armbian (Oct 13 2023 - 22:19:41 +0000) Allwinner Technology CPU: Allwinner A10 (SUN4I) Model: Cubietech Cubieboard DRAM: 1 GiB Core: 68 devices, 23 uclasses, devicetree: separate WDT: Not starting watchdog@1c20c90 MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... Unknown monitor Unknown monitor In: serial,usbkbd Out: serial,vidconsole Err: serial,vidconsole Net: Could not get PHY for emac: addr 1 No ethernet found. 230454 bytes read in 12 ms (18.3 MiB/s) Unknown monitor starting USB... Bus usb@1c14000: USB EHCI 1.00 Bus usb@1c14400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 scanning bus usb@1c14000 for devices... 1 USB Device(s) found scanning bus usb@1c14400 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... 2 USB Device(s) found scanning bus usb@1c1c400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 4121 bytes read in 2 ms (2 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 154 bytes read in 2 ms (75.2 KiB/s) 10691398 bytes read in 451 ms (22.6 MiB/s) 8420880 bytes read in 356 ms (22.6 MiB/s) Found mainline kernel configuration 33617 bytes read in 8 ms (4 MiB/s) Working FDT set to 43000000 4832 bytes read in 6 ms (786.1 KiB/s) Applying kernel provided DT fixup script (sun4i-a10-fixup.scr) ## Executing script at 45000000 Kernel image @ 0x42000000 [ 0x000000 - 0x807e10 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 10691334 Bytes = 10.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Working FDT set to 43000000 EHCI failed to shut down host controller. Loading Ramdisk to 495cd000, end 49fff306 ... OK Loading Device Tree to 4955c000, end 495ccfff ... OK Working FDT set to 4955c000 DE is present but not probed Starting kernel ...

Installed Armbian to SD-card-1. Booted Cubietruck from it: works great. Made some changes in system and wanted that changes to another SD card, so I copied entire root ( / ) filesystem from SD-card-1 to my-armbian.tar.gz. There is better ways of doing this: dd or another make-image-software or better remember my changes related to original Armbian and made that changes in new system. But lets consider my stupid way:) Got new SD card: SD-card-2. Created partition table with 1 partition. Made ext4fs on that 1 partition. Unpacked my the filesystem to the partition. Used gparted and set flag BOOT. SD-card-2 didnt booted. I realized that i need U-Boot on it. So used this manual to make my SD card bootable: https://linux-sunxi.org/Bootable_SD_card#Bootloader : Git-cloned the U-Boot. cross-compiled it for default Cubieboard config. dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk-blabla bs=1024 seek=8 to SD-card-2, changed UUID in the /boot/armbianEnv.txt for UUID of newly created ext4 on step (3). Now the SD-card-2 system booted OK! I see it boots by the way LED lamps blinking. Also it resets ethernet interface (it goes down then goes up) and it starts BOOTP/DHCP negotiation. BUT! The weird thing happened. Ethernet works single-directional: Cubietruck do not see any packets coming to it, but everyone else see the packets coming from it. The is no thernet switches between cubieboard and the DHCP-server (my laptop), just one good ethernet cable that worked great with SD-card-1. For example, when SD-card-2 tries to get IP address using DHCP, the DHCP-server see DHCPDISCOVER and respond with DHCPOFFER, but this process has no continuation: DHCP server does not see DHCPREQUEST and following DHCPACK from the Cubieboard. The interesting thing is: when i boot this Cubieboard with the "Original" SD-card-1, everything works great. Also, when i boot some proprietary linux from NAND flash soldered to Cubieboard (i dont know what that linux does, but it talks BOOTP/DHCP after boot) the DHCP-process goes perfect too. So, i've got strange single-directional ethernet connection with my u-booted SD card and have no idea what is happening there:) Please help me understand that.