Arch linux driver sr needs updating
found SMP MP-table at [c00ff780] 000ff780 Entering add_active_range(0, 0, 245680) 0 entries of 256 used Zone PFN ranges: DMA 0 - 245680 On node 0 totalpages: 245680 DMA zone: 32 pages used for memmap DMA zone: 0 pages reserved DMA zone: 4064 pages, LIFO batch:0 Normal zone: 1760 pages used for memmap Normal zone: 223520 pages, LIFO batch:31 High Mem zone: 127 pages used for memmap High Mem zone: 16177 pages, LIFO batch:3 Movable zone: 0 pages used for memmap DMI present. SMP alternatives: switching to UP code Freeing SMP alternatives: 9k freed ACPI: Core revision 20070126 ACPI: Checking initramfs for custom DSDT ACPI: setting ELCR to 0200 (from 0c20) CPU0: AMD Athlon(tm) Processor LE-1640 stepping 03 Total of 1 processors activated (5229.64 Bogo MIPS).
Total pages: 243761 Kernel command line: root=/dev/disk/by-uuid/706d610a-837f-4c03-9241-62000e029f52 ro noapic mapped APIC to ffffb000 (fee00000) mapped IOAPIC to ffffa000 (fec00000) Enabling fast FPU save and restore... ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7 10 11 14) *0, disabled.
The Arch team does not support ARM devices, but the Arch Linux ARM project does.
Now when I power it on it I get a rapidly flashing green center LED, it seeks the usb flash drive once and then keeps blinking.
Does not get on the network as I don't see it in my router's device list.
I had successfully rebooted it multiple times after installation by using the reboot command. but while frustrated with the non-booting situation, I pressed the reset button, and to my surprise, it booted off of the USB flash drive and I could ssh into archlinux installation, and subsequent reboots work. I have to use the reset button again for it to boot from USB flash drive. Is there a way to force GFN to boot from USB with or without Sata drive hookup. it probably isn't initialised in time so try a different one.
Why does it refuse to boot archlinux and what can I do to resolve this problem? I wanted to use USB Flash drive as boot drive so I can swap out Sata drives as needed. Sata drive has to be hooked up after boot is completed. There was a post about one trick in the forum, but you would have to modify a u-boot variable to start stop and start usb subsystem.