gerotmf Posted September 22, 2018 Posted September 22, 2018 Hi, Is there a way to fix emmc booting problem from uboot itself, i've updated armbian and now orangepi pc+ doesn't boot, i've connected uart and i see that it reads /boot/boot.scr from mmc 1, but then tries to load stuff from mmc 0, so i guess my boot.scr got overwritten by default one .. or something. boot shows this => boot switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3565 bytes read in 6 ms (580.1 KiB/s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc MMC: no card present ** Bad device mmc 0 ** MMC: no card present ... and then BOOTP load If it's possible to fix from uart console, it would be nice, but i guess i'll have to go search for some sd card or usb key to boot
Igor Posted September 22, 2018 Posted September 22, 2018 You must have some very old installation. Have you changed anything by hand? Try this - make and boot from SD card, mount eMMC and copy /boot/boot.* to your eMMC /boot section.
gerotmf Posted September 22, 2018 Author Posted September 22, 2018 Yep i have very old distribution (Armbian_5.30_Orangepipcplus_Debian_jessie_default_3.4.113), so i've just installed new one on usb and i'm booting from there (needed to print with OctoPrint asap, so i just left it as is), will play with it later, Thanks for reply.
Guidalpi Posted September 24, 2018 Posted September 24, 2018 (edited) Same thing happened here. I have my boot on eMMC and my root is on an external USB HDD. It loads u-boot from eMMC and then I get a lot of "** Bad device mmc 0 **". The only difference from the gerotmf´s logs is that my external USB is being listed as a valid storage device. Even listing my external USB, the kernel is not being loaded (it tries to load it from the ethernet and BOOTP). Finally it shows me the console, but I could not get any command to continue the boot process on the external USB. My system was up to date, as it is automatically updated. It was a 2017 installation (maybe 5.30, and the last update before 5.60 was 5.36). Is there anything I can try, to get my server back? Best regards. Edited September 24, 2018 by Guidalpi Changed SATA to USB
Igor Posted September 24, 2018 Posted September 24, 2018 2 hours ago, Guidalpi said: Is there anything I can try, to get my server back? Did you try the same as it was advised to @gerotmf ?
Guidalpi Posted September 24, 2018 Posted September 24, 2018 10 hours ago, Igor said: Did you try the same as it was advised to @gerotmf ? Unfortunately it didn´t solved for me. I could boot from the SD card, but even copying the boot* files to eMMC (/boot) I´m not able to boot from eMMC. I ´m attaching the image from eMMC boot process.
ATK Posted September 24, 2018 Posted September 24, 2018 21 minutes ago, Guidalpi said: Unfortunately it didn´t solved for me. I could boot from the SD card, but even copying the boot* files to eMMC (/boot) I´m not able to boot from eMMC. I ´m attaching the image from eMMC boot process. Exactly this same issue I am facing since morning , I am on legacy desktop version (5.2x ~ 5.30) + OP+2E ... everything was ok till last night ..I just ran update/upgrade which resulted in a big few MBs of updates.... then carried on my work as usual and later shutdown the board .. but today morning when i fire up the board I start getting the same types of messages as you have posted above ( your screen shot ) .... OS is on emmc ... remedy as suggested by Igor resulted no relief .... seems something got broken in last/recent updates...
Guidalpi Posted September 25, 2018 Posted September 25, 2018 Hello @Igor, @ATK I´ve managed to fix the boot process. I had to to copy all /boot content from eMMC to the external HDD /boot directory. It was empty before this procedure, as the /boot mount point was always coming from eMMC. (my first installation was done on a SD and then I performed a nand-sata-install, selecting boot from eMMC and root from external USB). I really don´t know why, but it is working just fine! Regards and hope it helps.
ATK Posted September 25, 2018 Posted September 25, 2018 @Guidalpi But I am not having any external storage... just the onboard emmc... so for me the issue still remains...
hannibal1986 Posted September 25, 2018 Posted September 25, 2018 I have an opi + 2e, I have armbian (debian) and yesterday with an apt-get update, apt-get upgrade the system and today when I boot up I get the attached image and it does not start, any solution? I'm very noob thnks, internet and dhcp work fine
Igor Posted September 25, 2018 Posted September 25, 2018 I couldn't recreate. My board boots fine after the upgrade: Spoiler U-Boot SPL 2018.05-armbian (Sep 19 2018 - 12:57:55 +0200) DRAM: 1024 MiB Trying to boot from MMC2 U-Boot 2018.05-armbian (Sep 19 2018 - 12:57:55 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi PC Plus DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 Loading Environment from EXT4... MMC: no card present ** Bad device mmc 0 ** Failed (-5) In: serial Out: vidconsole Err: vidconsole Net: phy interface0 eth0: ethernet@1c30000 MMC: no card present ** Bad device mmc 0 ** MMC: no card present ** Bad device mmc 0 ** 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 usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 6 ms (603.5 KiB/s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 203 bytes read in 6 ms (32.2 KiB/s) MMC: no card present ** Bad device mmc 0 ** 5228996 bytes read in 258 ms (19.3 MiB/s) 4654496 bytes read in 235 ms (18.9 MiB/s) Found legacy kernel configuration 36568 bytes read in 5 ms (7 MiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5228932 Bytes = 5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Starting kernel ... [sun8i_fixup]: From boot, get meminfo: Start: 0x40000000 Size: 1024MB ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1 ion_reserve_select: ion chipid [0x2c00081! ion_reserve_common: ion reserve: [0x50000000, 0x60000000]! Loading, please wait... starting version 229 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.27.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: clean, 108980/472352 files, 484602/1888624 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Ubuntu 16.04.5 LTS! Most likely /boot/boot.scr is corrupted. Also, proper rootdev=UUID=xxxxxxxxxxxxxxxxxxxxxx for eMMC must exists in /boot/armbianEnv.txt There is really no any extra magic - u-boot , boot script which loads kernel .. and we are only not getting to the kernel loading commands which are in the script.
hannibal1986 Posted September 25, 2018 Posted September 25, 2018 I used apt-get upgrade yesterday and I have the same problem, I only use the emmc and I can access the emmc files from a system in the SD, could someone solve it? I tried to change the boot.scr by one of the sd that works but Nothing in what file is the boot disk from UBoot? I think that in this update does not find emmc in the boot since I see what happens to those who have emmc
Igor Posted September 25, 2018 Posted September 25, 2018 Please boot from SD card, mount eMMC and provide its content of: boot/armbienEnv.txt boot/boot.cmd boot/boot.scr and type: blkid armbianmonitor -u
hannibal1986 Posted September 25, 2018 Posted September 25, 2018 9 hours ago, Igor said: Please boot from SD card, mount eMMC and provide its content of: boot/armbienEnv.txt boot/boot.cmd boot/boot.scr and type: blkid armbianmonitor -u armbianmonitor -u -> http://ix.io/1nxY blkid is in attached files, marked uuid is the emmc file /boot/armbienEnv.txt not found file /boot/boot.cmd: Spoiler gpio set PL10 gpio set PG11 setenv machid 1029 setenv bootm_boot_mode sec if ext4load mmc 0 0x00000000 /boot/.verbose then setenv verbosity 7 else setenv verbosity 1 fi # nonstandard monitor settings for A10, A20 and A31 based boards # screen is initialized before this script -> saving to u-boot environment is mandatory #setenv video-mode sunxi:1024x768-24@60,monitor=dvi,hpd=0,edid=0,overscan_x=1,overscan_y=2 #saveenv # nonstandard monitor settings setenv bootargs "console=ttyS0,115200 console=tty1 root=UUID=3d0c53d0-0261-461b-8145-852fd0c46920 rootwait rootfstype=ext4 cgroup_enable=memory swapaccount=1 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 panic=10 consoleblank=0 enforcing=0 loglevel=${verbosity}" #-------------------------------------------------------------------------------------------------------------------------------- # Boot loader script to boot with different boot methods for old and new kernel #-------------------------------------------------------------------------------------------------------------------------------- if ext4load mmc 0 0x00000000 /boot/.next || fatload mmc 0 0x00000000 .next || ext4load mmc 0 0x00000000 .next then # sunxi mainline kernel #-------------------------------------------------------------------------------------------------------------------------------- ext4load mmc 0 ${fdt_addr_r} /boot/dtb/${fdtfile} || fatload mmc 0 ${fdt_addr_r} /dtb/${fdtfile} || ext4load mmc 0 ${fdt_addr_r} /dtb/${fdtfile} ext4load mmc 0 ${ramdisk_addr_r} /boot/uInitrd || fatload mmc 0 ${ramdisk_addr_r} uInitrd || ext4load mmc 0 ${ramdisk_addr_r} uInitrd || setenv ramdisk_addr_r "-" ext4load mmc 0 ${kernel_addr_r} /boot/zImage || fatload mmc 0 ${kernel_addr_r} zImage || ext4load mmc 0 ${kernel_addr_r} zImage bootz ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} #-------------------------------------------------------------------------------------------------------------------------------- else # sunxi android kernel #-------------------------------------------------------------------------------------------------------------------------------- ext4load mmc 0 ${fdt_addr_r} /boot/script.bin || fatload mmc 0 ${fdt_addr_r} script.bin || ext4load mmc 0 ${fdt_addr_r} script.bin ext4load mmc 0 ${ramdisk_addr_r} /boot/uInitrd || fatload mmc 0 ${ramdisk_addr_r} uInitrd || ext4load mmc 0 ${ramdisk_addr_r} uInitrd || setenv ramdisk_addr_r "-" ext4load mmc 0 ${kernel_addr_r} /boot/zImage || fatload mmc 0 ${kernel_addr_r} zImage || ext4load mmc 0 ${kernel_addr_r} zImage bootz ${kernel_addr_r} ${ramdisk_addr_r} #-------------------------------------------------------------------------------------------------------------------------------- fi # Recompile with: # mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr and file /boot/boot.scr: Spoiler gpio set PG11 setenv machid 1029 setenv bootm_boot_mode sec if ext4load mmc 0 0x00000000 /boot/.verbose then setenv verbosity 7 else setenv verbosity 1 fi # nonstandard monitor settings for A10, A20 and A31 based boards # screen is initialized before this script -> saving to u-boot environment is mandatory #setenv video-mode sunxi:1024x768-24@60,monitor=dvi,hpd=0,edid=0,overscan_x=1,overscan_y=2 #saveenv # nonstandard monitor settings setenv bootargs "console=ttyS0,115200 console=tty1 root=UUID=3d0c53d0-0261-461b-8145-852fd0c46920 rootwait rootfstype=ext4 cgroup_enable=memory swapaccount=1 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 panic=10 consoleblank=0 enforcing=0 loglevel=${verbosity}" #-------------------------------------------------------------------------------------------------------------------------------- # Boot loader script to boot with different boot methods for old and new kernel #-------------------------------------------------------------------------------------------------------------------------------- if ext4load mmc 0 0x00000000 /boot/.next || fatload mmc 0 0x00000000 .next || ext4load mmc 0 0x00000000 .next then # sunxi mainline kernel #-------------------------------------------------------------------------------------------------------------------------------- ext4load mmc 0 ${fdt_addr_r} /boot/dtb/${fdtfile} || fatload mmc 0 ${fdt_addr_r} /dtb/${fdtfile} || ext4load mmc 0 ${fdt_addr_r} /dtb/${fdtfile} ext4load mmc 0 ${ramdisk_addr_r} /boot/uInitrd || fatload mmc 0 ${ramdisk_addr_r} uInitrd || ext4load mmc 0 ${ramdisk_addr_r} uInitrd || setenv ramdisk_addr_r "-" ext4load mmc 0 ${kernel_addr_r} /boot/zImage || fatload mmc 0 ${kernel_addr_r} zImage || ext4load mmc 0 ${kernel_addr_r} zImage bootz ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} #-------------------------------------------------------------------------------------------------------------------------------- else # sunxi android kernel #-------------------------------------------------------------------------------------------------------------------------------- ext4load mmc 0 ${fdt_addr_r} /boot/script.bin || fatload mmc 0 ${fdt_addr_r} script.bin || ext4load mmc 0 ${fdt_addr_r} script.bin ext4load mmc 0 ${ramdisk_addr_r} /boot/uInitrd || fatload mmc 0 ${ramdisk_addr_r} uInitrd || ext4load mmc 0 ${ramdisk_addr_r} uInitrd || setenv ramdisk_addr_r "-" ext4load mmc 0 ${kernel_addr_r} /boot/zImage || fatload mmc 0 ${kernel_addr_r} zImage || ext4load mmc 0 ${kernel_addr_r} zImage bootz ${kernel_addr_r} ${ramdisk_addr_r} #-------------------------------------------------------------------------------------------------------------------------------- fi # Recompile with: # mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr any idea? thanks
hannibal1986 Posted September 25, 2018 Posted September 25, 2018 Uffffff!!! y copy full boot folder from SD, and change de uuid of root and work now, thanks
Guidalpi Posted September 26, 2018 Posted September 26, 2018 13 hours ago, Igor said: Please boot from SD card, mount eMMC and provide its content of: boot/armbienEnv.txt boot/boot.cmd boot/boot.scr and type: blkid armbianmonitor -u Hope it helps finding what´s going on. #blkid /dev/mmcblk0p1: UUID="3f1bbc6f-5029-43f9-a7d9-1f5bd5b99bf2" TYPE="ext4" PARTUUID="12672447-01" /dev/sdb1: UUID="0644804d-3387-40c4-a733-2f168602fb51" TYPE="ext4" PARTUUID="cf59e41c-01" armbianEnv.txt armbianmonitor.txt boot.cmd boot.scr
Igor Posted September 26, 2018 Posted September 26, 2018 4 hours ago, Guidalpi said: Hope it helps finding what´s going on. The problem is exactly as predicted. You need to update a boot script as described a few posts back: Since this only happens when booting from eMMC, fixing is super easy. Boot from SD card and copy /boot/boot.* to eMMC's /boot/ directory. You only need to mount eMMC before.
Guidalpi Posted September 26, 2018 Posted September 26, 2018 16 hours ago, Igor said: The problem is exactly as predicted. You need to update a boot script as described a few posts back: Since this only happens when booting from eMMC, fixing is super easy. Boot from SD card and copy /boot/boot.* to eMMC's /boot/ directory. You only need to mount eMMC before. Hello @Igor, I´ve tried to copy /boot/boot.* to eMMC, but still no sucess on booting. (as @ATK ) As you explained that there is no magic (" u-boot , boot script which loads kernel") and the boot script seems fine to me (there are no differences between the script and scr file on eMMC, SD and HDD) the only part that could be wrong was the u-boot. So, I decided to downgrade only the u-boot bin. I´ve downloaded the file linux-u-boot-orangepiplus-default_5.39_armhf.deb and extracted its content. Then I ran postinst script setting the device to install u-boot to /dev/mmcblk1 (eMMC, as I had booted from SD card). Rebooting my OPi I noticed that the version of u-boot was really downgraded and the boot process was succesfully executed. My guess is that something between 5.39 and 5.60 has broken the support on my hardware. I´ve made some further investigations and noticed that it seems that in 5.60, the boot script, when running from eMMC, is not being able to read the /boot/armbianEnv.txt as I printed the env variables (env print) and the rootdev was still pointing to the wrong place. I don´t know if it is possible, but I can try to trace the exactly version that breaks my boot support between 5.39 and 5.60. I just need to know where I can access these versions. Best Regards.
Igor Posted September 27, 2018 Posted September 27, 2018 3 hours ago, Guidalpi said: Rebooting my OPi I noticed that the version of u-boot was really downgraded and the boot process was succesfully executed. This is a bit strange but OK. 3 hours ago, Guidalpi said: I just need to know where I can access these versions. You can find old u-boot packages in our repository. http://apt.armbian.com/pool/main/l default=3.4.y next=4.14.y dev=4.18.y ->
Jordi Posted September 28, 2018 Posted September 28, 2018 Hello ! Same problems on my OrangePiPlus2 .. everything worked fine, untill yesterday.. I ran apt-get update && apt-get upgrade, and when I rebooted, it won't turn on.. (nothing happens.. the screen remains turned off) I can boot my OP+2 with a SD card without problems, and once it's running, I can mount the emmc I have an old Armbian running on my OP+2 -> Armbian_5.14_Orangepiplus_Debian_jessie_3.4.112_desktop What have I done? 1) I made a backup of the /boot directory of my emmc before changing anything 2) I boot with an SD with Armbian_5.59_Orangepiplus_Debian_stretch_next_4.14.65 (the last version published I see) 2.1) I've copied all the /boot/boot.* files from SD to EMMC 2.2) Doesn't work -> but something changed.. my monitor turns on, in graphical mode, with a kind of garnet-color-background (but nothing happens) 3) I boot with an SD with Armbian_5.14_Orangepiplus_Debian_jessie_3.4.112_desktop (the one I've installed on my OP+2) 3.1) I've copied all the /boot/boot.* files from SD to EMMC 3.2) Doesn't work At this moment I'm completely lost :( All my hopes are on this thread . Thank you so much for your support ! Jordi (Barcelona)
Guidalpi Posted October 2, 2018 Posted October 2, 2018 On 9/27/2018 at 12:47 AM, Igor said: This is a bit strange but OK. You can find old u-boot packages in our repository. http://apt.armbian.com/pool/main/l default=3.4.y next=4.14.y dev=4.18.y -> Hello Igor, Finally I got your point. I decided to burn my SD again and assured that the right image was being used. And as you said, copying the boot.* from the SD card to the eMMC solved the problem. I have just one last doubt: why the boot.cmd and boot.scr files are not being included/upgraded by any deb package? Best Regards.
Guidalpi Posted October 2, 2018 Posted October 2, 2018 On 9/28/2018 at 6:24 PM, Jordi said: Hello ! Same problems on my OrangePiPlus2 .. everything worked fine, untill yesterday.. I ran apt-get update && apt-get upgrade, and when I rebooted, it won't turn on.. (nothing happens.. the screen remains turned off) I can boot my OP+2 with a SD card without problems, and once it's running, I can mount the emmc I have an old Armbian running on my OP+2 -> Armbian_5.14_Orangepiplus_Debian_jessie_3.4.112_desktop What have I done? 1) I made a backup of the /boot directory of my emmc before changing anything 2) I boot with an SD with Armbian_5.59_Orangepiplus_Debian_stretch_next_4.14.65 (the last version published I see) 2.1) I've copied all the /boot/boot.* files from SD to EMMC 2.2) Doesn't work -> but something changed.. my monitor turns on, in graphical mode, with a kind of garnet-color-background (but nothing happens) 3) I boot with an SD with Armbian_5.14_Orangepiplus_Debian_jessie_3.4.112_desktop (the one I've installed on my OP+2) 3.1) I've copied all the /boot/boot.* files from SD to EMMC 3.2) Doesn't work At this moment I'm completely lost All my hopes are on this thread . Thank you so much for your support ! Jordi (Barcelona) Try the "Other download options" at the end of the page (https://www.armbian.com/orange-pi-plus-2/). It has the legacy kernel (3.4). The torrent link is https://dl.armbian.com/orangepiplus/Ubuntu_xenial_default_desktop.7z.torrent That was the one that finally solved the problem for me. Good luck!
Jordi Posted October 2, 2018 Posted October 2, 2018 15 hours ago, Guidalpi said: Try the "Other download options" at the end of the page (https://www.armbian.com/orange-pi-plus-2/). It has the legacy kernel (3.4). The torrent link is https://dl.armbian.com/orangepiplus/Ubuntu_xenial_default_desktop.7z.torrent That was the one that finally solved the problem for me. Good luck! Thanks a lot Guidalpi ! Unfortunately it did'nt work in my case. I think I've tested every possible combinations of boot files on my system.. and for the moment I've not found the right one.. Fortunately, a friend of mine (a master !) is helping me with this problem. If we (he) find the solution I'll inform here. Is easily reproducible: - I have an OrangePiPlus2 - I use the original installation I installed for my system: Armbian_5.14_Orangepiplus_Debian_jessie_3.4.112_desktop (I have the image) - And then: 1) I burn the image it into a µsd card with Etcher 2) I boot from this µsd on my OPiPlus2 3) I run nand-sata-install to move the installation to the emmc 4) Shutdown, and remove the µsd card 5) Boot from the emmc installation, everything works ok (with kernel 3.4.112 - i see it on /boot) 6) I run apt-get update && apt-get upgrade -> I see the /boot folder and I see kernel has updated to 3.4.113 7) I reboot, and it doesn't work.. the screen remains black and nothing happens Does anybody know if this problem will be solved on a next upgrade ? If it's solved, I can repeat this process, and once I get a system running (based on 5.14 and updated) I'll recover my system Thank you !
hannibal1986 Posted October 2, 2018 Posted October 2, 2018 On 9/28/2018 at 11:24 PM, Jordi said: Hello ! Same problems on my OrangePiPlus2 .. everything worked fine, untill yesterday.. I ran apt-get update && apt-get upgrade, and when I rebooted, it won't turn on.. (nothing happens.. the screen remains turned off) I can boot my OP+2 with a SD card without problems, and once it's running, I can mount the emmc I have an old Armbian running on my OP+2 -> Armbian_5.14_Orangepiplus_Debian_jessie_3.4.112_desktop What have I done? 1) I made a backup of the /boot directory of my emmc before changing anything 2) I boot with an SD with Armbian_5.59_Orangepiplus_Debian_stretch_next_4.14.65 (the last version published I see) 2.1) I've copied all the /boot/boot.* files from SD to EMMC 2.2) Doesn't work -> but something changed.. my monitor turns on, in graphical mode, with a kind of garnet-color-background (but nothing happens) 3) I boot with an SD with Armbian_5.14_Orangepiplus_Debian_jessie_3.4.112_desktop (the one I've installed on my OP+2) 3.1) I've copied all the /boot/boot.* files from SD to EMMC 3.2) Doesn't work At this moment I'm completely lost All my hopes are on this thread . Thank you so much for your support ! Jordi (Barcelona) - Edita el archivo armbianEnv.txt y cambia el UUID de tu SD por el de tu eMMC sino lo modificas es normal que no arranque solo con cambiar la carpeta boot -Edit the file armbianEnv.txt and change the UUID of your SD to that of your eMMC
Guidalpi Posted October 2, 2018 Posted October 2, 2018 2 hours ago, hannibal1986 said: - Edita el archivo armbianEnv.txt y cambia el UUID de tu SD por el de tu eMMC sino lo modificas es normal que no arranque solo con cambiar la carpeta boot -Edit the file armbianEnv.txt and change the UUID of your SD to that of your eMMC Hello @Jordi @hannibal1986 is right! I didn´t need this step as my root resides in an external HDD (same UUID when booting from SD and eMMC) Regards.
Jordi Posted October 4, 2018 Posted October 4, 2018 On 10/2/2018 at 9:40 PM, hannibal1986 said: - Edita el archivo armbianEnv.txt y cambia el UUID de tu SD por el de tu eMMC sino lo modificas es normal que no arranque solo con cambiar la carpeta boot -Edit the file armbianEnv.txt and change the UUID of your SD to that of your eMMC @hannibal1986, @Guidalpi Thanks a lot ! Unfortunately, this file does not exist on my installation ! (brand new installation, but from an older distribution !) My collegue has a plan.. he told me he think he'll be able to solve it, but untill monday we won't meet.. so we'll have to wait I'll keep you updated
martinayotte Posted October 4, 2018 Posted October 4, 2018 1 hour ago, Jordi said: Unfortunately, this file does not exist on my installation ! (brand new installation, but from an older distribution !) The armbianEnv.txt file exist since several years, so which distribution you are talking about ?
freak Posted October 4, 2018 Posted October 4, 2018 Try unplugging your hdmi cable and booting. Wait a bit to make sure it's fully booted then plug in the hdmi cable.
Jordi Posted October 4, 2018 Posted October 4, 2018 1 hour ago, martinayotte said: The armbianEnv.txt file exist since several years, so which distribution you are talking about ? Hello! I'm using the Armbian_5.14_Orangepiplus_Debian_jessie_3.4.112_desktop distribution ( we look for the file on the /boot directory, but it was not there ) I'll wait until monday.. my collegue has a plan, I trust my collegue Thanks a lot
Jordi Posted October 4, 2018 Posted October 4, 2018 1 hour ago, freak said: Try unplugging your hdmi cable and booting. Wait a bit to make sure it's fully booted then plug in the hdmi cable. Wow, have not tried. I'll try next monday. Thanks !!
Recommended Posts