Jump to content

piknew

Members
  • Posts

    113
  • Joined

  • Last visited

Recent Profile Visitors

5184 profile views
  1. I had to reapply u-boot image. So, I did it by armbian-config and later by "dd" command. In both situations this is failing (please see u-boot messages printed by serial). I was restoring the image (I have backup images of my SD card) and trying again. What may be the problem? I had linux-u-boot-orangepi*-current 22.08.6 installed. As below - please note Verifying Checksum ... Bad Data CRC BTW. I tried the same on Orange Pi PC and Orange Pi Zero - the same result (fail to boot). => version U-Boot 2022.07-armbian (Oct 18 2022 - 07:35:20 +0000) Allwinner Technology arm-none-linux-gnueabihf-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 20191025 GNU ld (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 2.33.1.20191209 => reset resetting ... U-Boot SPL 2022.07-armbian (Oct 18 2022 - 07:35:20 +0000) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2022.07-armbian (Oct 18 2022 - 07:35:20 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi PC DRAM: 1 GiB Core: 65 devices, 18 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@1c28000 Out: serial@1c28000 Err: serial@1c28000 Net: phy interface1 eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... 1 USB Device(s) found scanning bus usb@1c1c400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 5 ms (723.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 212 bytes read in 4 ms (51.8 KiB/s) 13021622 bytes read in 549 ms (22.6 MiB/s) 8387760 bytes read in 356 ms (22.5 MiB/s) Found mainline kernel configuration 32077 bytes read in 13 ms (2.4 MiB/s) 374 bytes read in 10 ms (36.1 KiB/s) Applying kernel provided DT overlay sun8i-h3-i2c0.dtbo 393 bytes read in 5 ms (76.2 KiB/s) Applying user provided DT overlay ds1307.dtbo 4185 bytes read in 9 ms (454.1 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 44000000 Kernel image @ 0x42000000 [ 0x000000 - 0x7ffcb0 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 13021558 Bytes = 12.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image Device 0: unknown device ethernet@1c30000 Waiting for PHY auto negotiation to complete. done BOOTP broadcast 1 DHCP client bound to address 192.168.10.136 (3 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-81-a9-fc-f7-d9 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A80A88 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A80A8 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A80A *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A80 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A8 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default-arm-sunxi *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default-arm *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default *** ERROR: `serverip' not set Config file not found BOOTP broadcast 1 DHCP client bound to address 192.168.10.136 (3 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET BOOTP broadcast 1 DHCP client bound to address 192.168.10.136 (2 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET =>
  2. Solution: 1. Create file in /etc/systemd/network with name eg. "01-xradio_wlan.link". Please refer to systemd documentation. Content of file: [Match] OriginalName=* Driver=xradio_wlan [Link] NamePolicy= Name=wlx0042c49ede90 MACAddressPolicy=none MACAddress=00:42:c4:9e:de:90 For reference, this is content for 2nd file "99-default.link" (which is applied as default policy): [Match] OriginalName=* [Link] NamePolicy=mac MACAddressPolicy=none 2. Result:
  3. I believe this patch is causing, for kernels >= 5.13 - section of setting up mac address is skipped: https://github.com/armbian/build/blob/master/patch/misc/wireless-xradio-5.13.patch I do not have the knowledge - what was stated behind of this patch... For me the problem is that generally I have a policy to name network interface with mac. And currently on OPI Zero - this is making my wlan interface "random".
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines