kudzu Posted August 27, 2016 Posted August 27, 2016 U-Boot SPL 2016.05-armbian (Jun 01 2016 - 19:42:08) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2016.05-armbian (Jun 01 2016 - 19:42:08 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi PC I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 (SD), SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB 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 2444 bytes read in 182 ms (12.7 KiB/s) ## Executing script at 43100000 Wrong image format for "source" command SCRIPT FAILED: continuing... switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... USB device 0: unknown device No ethernet found. missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found No ethernet found. => I have tested with two SDs - the same result. But vanilla works perfect! Strange is that after dd command I can't mount SDs with legacy, but vanilla I can. I've downloaded legacy twice.
zador.blood.stained Posted August 27, 2016 Posted August 27, 2016 Jessie server legacy image for PC+ Armbian_5.14_Orangepipcplus_Debian_jessie_3.4.112.raw SHA256: CD5EB351E777651EC4F4DE71E8FD32FDECF40088A467C3C8A8A55916E1A30669 Works fine for me: U-Boot SPL 2016.05-armbian (Jun 01 2016 - 19:42:08) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2016.05-armbian (Jun 01 2016 - 19:42:08 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi PC I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 (SD), SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning bus 3 for devices... 1 USB Device(s) found scanning bus 5 for devices... 2 USB 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 2444 bytes read in 182 ms (12.7 KiB/s) ## Executing script at 43100000 gpio: pin PL10 (gpio 298) value is 1 gpio: pin PG11 (gpio 203) value is 1 0 bytes read in 130 ms (0 Bytes/s) ** File not found /boot/.next ** ** Unrecognized filesystem type ** ** File not found .next ** 37320 bytes read in 489 ms (74.2 KiB/s) 3112435 bytes read in 3349 ms (907.2 KiB/s) 5064616 bytes read in 5410 ms (914.1 KiB/s) Kernel image @ 0x48000000 [ 0x000000 - 0x4d47a8 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3112371 Bytes = 3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Using machid 0x1029 from environment Starting kernel ... 1
kudzu Posted August 27, 2016 Author Posted August 27, 2016 Jessie server legacy image for PC+ Armbian_5.14_Orangepipcplus_Debian_jessie_3.4.112.raw SHA256: CD5EB351E777651EC4F4DE71E8FD32FDECF40088A467C3C8A8A55916E1A30669 SHA256 passed. Strange is that after dd command I can't mount SDs with legacy, but vanilla I can. What about that? I can't mount uSD card with legacy image at my PC. Do you also use dd program to write raw image to SD?
zador.blood.stained Posted August 27, 2016 Posted August 27, 2016 Do you also use dd program to write raw image to SD? I used Rufus this time, but it shouldn't make any difference if you use correct arguments for dd (I mean write to whole device i.e. /dev/sdb and not to partition i.e. /dev/sdb1) Strange is that after dd command I can't mount SDs with legacy, but vanilla I can. Mounts fine for me: ➜ ~ % dmesg | tail [462269.361450] scsi host1: usb-storage 2-1.4:1.0 [462270.359126] scsi 1:0:0:0: Direct-Access Multi Flash Reader 1.00 PQ: 0 ANSI: 0 [462270.369768] sd 1:0:0:0: Attached scsi generic sg1 type 0 [462271.100193] sd 1:0:0:0: [sdb] 30228480 512-byte logical blocks: (15.5 GB/14.4 GiB) [462271.109039] sd 1:0:0:0: [sdb] Write Protect is off [462271.113934] sd 1:0:0:0: [sdb] Mode Sense: 03 00 00 00 [462271.115030] sd 1:0:0:0: [sdb] No Caching mode page found [462271.120498] sd 1:0:0:0: [sdb] Assuming drive cache: write through [462271.138014] sdb: sdb1 [462271.156495] sd 1:0:0:0: [sdb] Attached SCSI removable disk ➜ ~ % mkdir -p /tmp/sdb1 ➜ ~ % _ mount -v /dev/sdb1 /tmp/sdb1 mount: /dev/sdb1 mounted on /tmp/sdb1. ➜ ~ % ls /tmp/sdb1 bin dev home lost+found mnt proc run selinux sys usr boot etc lib media opt root sbin srv tmp var ➜ ~ % dmesg | tail [462270.359126] scsi 1:0:0:0: Direct-Access Multi Flash Reader 1.00 PQ: 0 ANSI: 0 [462270.369768] sd 1:0:0:0: Attached scsi generic sg1 type 0 [462271.100193] sd 1:0:0:0: [sdb] 30228480 512-byte logical blocks: (15.5 GB/14.4 GiB) [462271.109039] sd 1:0:0:0: [sdb] Write Protect is off [462271.113934] sd 1:0:0:0: [sdb] Mode Sense: 03 00 00 00 [462271.115030] sd 1:0:0:0: [sdb] No Caching mode page found [462271.120498] sd 1:0:0:0: [sdb] Assuming drive cache: write through [462271.138014] sdb: sdb1 [462271.156495] sd 1:0:0:0: [sdb] Attached SCSI removable disk [462284.603974] EXT4-fs (sdb1): mounted filesystem with writeback data mode. Opts: (null) ➜ ~ %
kudzu Posted August 27, 2016 Author Posted August 27, 2016 I used Rufus this time, but it shouldn't make any difference if you use correct arguments for dd (I mean write to whole device i.e. /dev/sdb and not to partition i.e. /dev/sdb1) Yes, of course. I'll try again in the morning. Maybe with Windows and other uSD adapter.
arox Posted August 27, 2016 Posted August 27, 2016 Have you make a "sync" after dd ? I see also sometimes recommendations to wipe the cards (dd if=/dev/zero of=/dev/sdX) before copying an image. I never do this, as I never found a justification to do it. But I also sometimes copy images that will not boot ... 1
kudzu Posted August 28, 2016 Author Posted August 28, 2016 Have you make a "sync" after dd ? Yes, but it is also strange, because card with "good" image syncs in 0.5 s when "bad" few minutes. I'll try to make new partition table and maybe wipe it as you suggest.
kudzu Posted August 28, 2016 Author Posted August 28, 2016 Ok, everything works now. It was SD format fault, but I don't know why other images worked fine.
martinayotte Posted August 28, 2016 Posted August 28, 2016 Usually, such issues can happened when doing a "dd" while sd is still mounted with previous partitions. Making sure no partition are mounted before issuing the "dd" command is a good practice. 1
kudzu Posted August 28, 2016 Author Posted August 28, 2016 Usually, such issues can happened when doing a "dd" while sd is still mounted with previous partitions. Making sure no partition are mounted before issuing the "dd" command is a good practice. I think I have checked that every time, but I'm not sure. Thank you everyone for helpful suggestions!
1430 Posted August 30, 2016 Posted August 30, 2016 Hello! Is there any detailed instructions ( step by step ) how to write the image on the card?
Igor Posted August 30, 2016 Posted August 30, 2016 Hello! Is there any detailed instructions ( step by step ) how to write the image on the card? http://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card It's not exactly step by step but it should be clear.
Recommended Posts