Raylynn Knight

Members
  • Content Count

    5
  • Joined

  • Last visited

About Raylynn Knight

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Perhaps the documentation should be update to prevent hours of frustration for those of us trying to use Vagrant on MacOS! This all used to work just fine on MacOS until recently.
  2. I currently have installed "linux-u-boot-beelinkx2-next 5.34.171121" which boots and runs correctly. apt upgrade is offering "linux-u-boot-beelinkx2-next/stretch 5.37.180119 armhf [upgradable from: 5.34.171121]" which I know from experience will result in an un-bootable situtation.
  3. I've been using a Beelink X2 with Armbian for some time now booting from eMMC. I ran an "apt update; apt upgrade" on the box early on 01/14/2018 and a reboot was suggested at the end. The system did not successfully reboot after this update and it appears that it doesn't recognize uboot on the eMMC. At the time I had other pressing matters so I set it aside to work on today. Today I downloaded the latest image Armbian_5.34.171121_BeelinkX2_Debian_stretch_next_4.13.14_desktop.img, verified it and successfully wrote the image to a 16GB microSD card. This successfully booted the X2, I then did an "apt update; apt upgrade" on the microSD card and rebooted. This then resulted in an un-bootable SD card! Something in the latest update is causing an issue with uboot on the X2. I'm now rewriting the original image to the microSD and will attempt to determine what update is causing the issue!
  4. I recently acquired an A64+ 2GB model with the optional WiFi. I created an SD card with the latest nightly image. Logging in I get the following: Welcome to ARMBIAN 5.27.170410 nightly Ubuntu 16.04.2 LTS 4.10.0-pine64 So far it appears to be functioning well except it doesn't appear to recognize the wifi. ifconfig shows only eth0 and lo interfaces. iwconfig also shows only eth0 and lo. lsmod shows no modules loaded. Running dmesg I noticed the following WARNINGs: <cut> [ 0.000000] psci: Trusted OS migration not required [ 0.000000] WARNING: x1-x3 nonzero in violation of boot protocol: x1: 0000000000000000 x2: 0000000000000000 x3: 0000000040080000 This indicates a broken bootloader or old kernel [ 0.000000] percpu: Embedded 23 pages/cpu @ffff80007e794000 s56216 r8192 d29800 u94208 <cut> [ 1.666020] ------------[ cut here ]------------ [ 1.666039] WARNING: CPU: 1 PID: 36 at drivers/base/dd.c:349 driver_probe_device+0x258/0x2c0 [ 1.666041] Modules linked in: [ 1.666054] CPU: 1 PID: 36 Comm: kworker/1:1 Not tainted 4.10.0-pine64 #42 [ 1.666057] Hardware name: Pine64+ (DT) [ 1.666066] Workqueue: events deferred_probe_work_func [ 1.666072] task: ffff80007c1e3200 task.stack: ffff80007c1d4000 [ 1.666076] PC is at driver_probe_device+0x258/0x2c0 [ 1.666081] LR is at driver_probe_device+0x60/0x2c0 [ 1.666085] pc : [<ffff00000857c6b8>] lr : [<ffff00000857c4c0>] pstate: 20000145 [ 1.666087] sp : ffff80007c1d7c60 [ 1.666090] x29: ffff80007c1d7c60 x28: 0000000000000000 [ 1.666096] x27: ffff80007c0d7d20 x26: ffff80007c1df3b8 [ 1.666102] x25: ffff000008b37cbb x24: 0000000000000003 [ 1.666108] x23: ffff000008b5cc40 x22: 0000000000000001 [ 1.666114] x21: 0000000000000000 x20: ffff000008bd6000 [ 1.666120] x19: ffff80007c216c10 x18: 0000000000000000 [ 1.666126] x17: 00000000fd541423 x16: 00000000768beda0 [ 1.666132] x15: ffffffffffffffff x14: ffff80007af1b91c [ 1.666139] x13: ffff80007af1b1e8 x12: 0000000000000020 [ 1.666145] x11: 0000000000000020 x10: 0101010101010101 [ 1.666151] x9 : 0000000000000008 x8 : 0000000000000008 [ 1.666157] x7 : ffff000008864a80 x6 : 0000000000000020 [ 1.666163] x5 : ffff80007c216da0 x4 : 0000000000000000 [ 1.666168] x3 : ffff80007c1e3200 x2 : ffff000008bd6200 [ 1.666174] x1 : ffff80007c216e80 x0 : ffff80007ad7e980 [ 1.666183] ---[ end trace 7854786610e49d0e ]--- [ 1.666186] Call trace: [ 1.666192] Exception stack(0xffff80007c1d7a90 to 0xffff80007c1d7bc0) [ 1.666197] 7a80: ffff80007c216c10 0001000000000000 [ 1.666203] 7aa0: ffff80007c1d7c60 ffff00000857c6b8 ffff80007af2a010 ffff80007af2a000 [ 1.666209] 7ac0: ffff80007ad5a068 ffff80007af2a000 ffff80007c1d7b40 ffff0000084f0a04 [ 1.666215] 7ae0: ffff80007af2a000 0000000000000001 ffff80007c1d7b10 ffff0000086b6274 [ 1.666220] 7b00: ffff80007e7f53e8 ffff0000084f0cf0 ffff80007c1d7b30 ffff0000084f0c8c [ 1.666226] 7b20: ffff80007c3cd680 ffff80007e7f53e8 ffff80007ad7e980 ffff80007c216e80 [ 1.666232] 7b40: ffff000008bd6200 ffff80007c1e3200 0000000000000000 ffff80007c216da0 [ 1.666237] 7b60: 0000000000000020 ffff000008864a80 0000000000000008 0000000000000008 [ 1.666242] 7b80: 0101010101010101 0000000000000020 0000000000000020 ffff80007af1b1e8 [ 1.666248] 7ba0: ffff80007af1b91c ffffffffffffffff 00000000768beda0 00000000fd541423 [ 1.666248] 7ba0: ffff80007af1b91c ffffffffffffffff 00000000768beda0 00000000fd541423 [ 1.666253] [<ffff00000857c6b8>] driver_probe_device+0x258/0x2c0 [ 1.666259] [<ffff00000857c86c>] __device_attach_driver+0x9c/0xf8 [ 1.666268] [<ffff00000857a8b4>] bus_for_each_drv+0x5c/0x98 [ 1.666273] [<ffff00000857c33c>] __device_attach+0xc4/0x138 [ 1.666278] [<ffff00000857c928>] device_initial_probe+0x10/0x18 [ 1.666282] [<ffff00000857b8ac>] bus_probe_device+0x94/0xa0 [ 1.666287] [<ffff00000857bd2c>] deferred_probe_work_func+0x74/0xa8 [ 1.666296] [<ffff0000080bf8f4>] process_one_work+0x1c4/0x378 [ 1.666301] [<ffff0000080bfcec>] worker_thread+0x244/0x498 [ 1.666309] [<ffff0000080c5968>] kthread+0xf0/0x120 [ 1.666316] [<ffff0000080826c0>] ret_from_fork+0x10/0x50 [ 1.669020] sun50i-a64-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver I didn't notice anything else in that would indicate the recognition or initialization of any WiFi. Thanks for any assistance.
  5. I ran into this issue after downloading ARMBIAN 5.27 mainline Ubuntu Xenial image. I created an image on a SD card, booted the SD card and then ran the nand-sata-install script to install to the eMMC card on my XU4. After this finished the device didn't appear to boot any longer. I have the USB-UART cable so I connected that and was able to determine that the old uboot was still trying to load the kernel image from a non-existant FAT partition. My forum search turned up this thread. I first tried the "run copy_uboot_sd2emmc" command, but this didn't work because the new uboot no longer contains the script. So reading further I saw the message above from Voiter and solved the issue by rebooting from the SD card, halting the boot script and at the uboot prompt running the following command: mmc dev 0; mmc read 0x50000000 0x1 0xa3e; mmc dev 1 1; mmc write 0x50000000 0x0 0xa3e; mmc dev 1 0 I was then able to switch the boot mode back to eMMC and successfully boot. So adding a copy_uboot_sd2emmc script with the above command should suffice in helping to resolve this issue.