Jump to content

gameseg

Members
  • Posts

    14
  • Joined

  • Last visited

  1. It works!!! I only changed my "uEnv.ini" file in boot_emc to represent "mmcblk0p2" and now I can boot from eMMC. Thank you!
  2. Here are the steps I have taken successfully: 1. Boot into Android 2. Attach USB and perform "update/backup" application 3. Select "aml_autoscript.zip" and perform the update - good! (this is where multiboot is being enabled, correct?) 4. Device s905x reboots automatically into Linux perfectly (Armbian_5.44_S9xxx_Ubuntu_bionic_4.18.0-rc5_mate_20180806) - good! 5. Run "./create-mbr-linux.sh" works perfectly (remember, I edited the "/dev/mmcblk0" name to work correctly here) - good! 6. Run "./install.sh" to install to eMMC works perfectly - good! 7. Shutdown s905x device 8. Unplug USB from s905x device 9. Unplug power cable from s905x device 10. Plug power cable back into the s905x device 11. Boot from eMMC on s905x device - good! 12. Failed boot, error message says "/dev/mmcblk1p2 does not exist" - bad! Evaluate, did step 3 activate multiboot? I've booted into my USB again. Here are the current pictures:
  3. I'm a bit lost, where/what are the steps to activate multi-boot? I would like to help consolidate all of the information and steps for future users.
  4. I'm so sorry, I messed up again! Where are the multi-boot instructions for my s905x? Is there anyway to proceed with my current state - or - do I need to perform a ddbr restore? Do I need to perform a factory reset with the USB Formatting Tool? Are these the correct instructions for multi-boot? Multiboot Selector for Your TV Box 2017
  5. I edited the shell script files and it worked. Step 3 completed successfully. Step 4 copy to eMMC appears to have completed successfully but when I shutdown, remove USB, and afterwards power back on. I then have errors saying "/dev/mmcblk1p2 does not exist" @balbes150 I have no idea how to proceed and need help. Does anyone have any suggestions on what to do next, or know what went wrong? I've attempted to attach the pictures in order of events. Thank you for your help.
  6. I know, but @balbes150 specifically stated that if the ddbr backup works, then installing to eMMC works. Here..."Run the "ddbr" utility, if it can create a full backup of eMMC, then the installation in eMMC will work..." I'll attempt to edit the script and report back as to whether or not I can activate dual boot with step 3 and install to eMMC with step 4. Stay tuned.
  7. Yes, "DDBR" backup completes successfully. I posted pictures and attempted to follow the process outlined by you for steps 1,2,3,4 - step 3 and 4 fail for me. The eMMC installation fails, I cannot activite dual boot. Please see the pictures I attached regarding the error messages. Why does the script incorrectly identify my device? Thank you for your help, sincerely.
  8. Do anyone know if the s905x is supported by the "regular distributions of Armbian" (e.g., Armbian Stretch / Bionic as seen here: https://www.armbian.com/nanopi-k2/)? I'm confused as to whether or not balbes150 is the only one making "supported" firmware for the s905x / a95x device. What is the brand of my s905x / a95x device, who is it made by? My board has printed: "A7_S905X_V2_3" if that helps. This is something that has confused me from the start. I do not mean to specifically ask you the questions - if anyone else has the answer I hope they can chime in. I'm going to perform a speed test on the eMMC and the USB port to determine if it is worthwhile to install on the eMMC... I'll try to do that within a couple days.
  9. I posted images above of my external USB drive gparted partitions, and local mmcblk1 showing one unallocated partition. Would you take a look and confirm whether or not I can install to eMMC? From what I interpreted on your message, it seems that I will be unable to. However, this makes me wonder, why won't it work? I'm using kernel 4.18 I think at least, and just 4.16 kernel is the non-compatible version as outlined by balbes150. I also noted in my above posts that it appears the shell scripts aren't finding the correct name of my eMMC partition (e.g., mmcblk0 vs mmcblk1)
  10. The kernel is 4.18 from what I can tell for image "Armbian_5.44_S9xxx_Ubuntu_bionic_4.18.0-rc5_mate_20180806" - and @balbes150 stated that "kernel 4.16 does not support internal eMMC memory" this first post here: (ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)) Has anyone testing the USB speeds compared to the eMMC speeds on the s905x??? If they are equal or close to it, I'll stick with using my USB 3.0 16GB... I would still like to know why / how to get eth0 to function properly on the latest release using ver 5.72 firmware.
  11. Maybe I'm experiencing a dtb issue - but I do not think so. It appears to me that the issue is related to the disk name "/dev/mmcblk0" vs "/dev/mmcblk1". Why is the shell script not picking up the correct disk? Must I change the disk name in every single shell script file? Also, I bricked my device before the last post when I first attempted to install to the eMMC. I used the USB Burning Tool and it worked fine. I also used the SD Card Tool and it worked fine. I can vouch for both methods working just fine. If you follow the instructions exactly as specified, you will un-brick the device without issue. Just be sure to follow the correct folder hierarchy, for the specific software versions and instructions, and you won't have a problem. HOWEVER, I will add - DO NOT use an AV Receiver when un-bricking. You MUST be directly connected to a monitor via HDMI. The s905x could not detect a monitor when I was connected to an Onkyo receiver (e.g., s905 > hdmi > Onkyo AV Receiver > hdmi > TV = BAD). You must use the following setup I've discovered (s905 > hdmi > monitor = GOOD). I struggled with that for 2 hours...
  12. Yes, I ended up going back a few versions and used a USB instead of SD Card. I selected "Armbian_5.44_S9xxx_Ubuntu_bionic_4.18.0-rc5_mate_20180806" and the eth0 speeds are excellent, as expected right around 75-100Mbps! So this is very good on my s905x A95x device. However, I cannot install to eMMC right now and need help with that. The step: "create-mbr-linux.sh" does not work for me, I get errors "no such file or directory". And if I go right for "nand-sata-install" I also get errors as: "Possibly non-existent device?". I'm attaching screenshots and would like help on how to install to eMMC please :]! Is this the correct process for my s905x? It was not working for me: Install Armbian to eMMC. 1. Be sure to activate multi-boot using the new image. If multiboot previously activated is required to repeat activation using files in a new image. 2. Run Armbian from external media, run "ddbr" and create full backup eMMC. 3. Execute script “/boot/create-mbr-linux.sh” (fails for me) 4. and install Armbian on eMMC execute script “/root/install.sh”. (fails for me) What am I doing incorrectly? Or what do I need to change in order for this to work for me?
  13. @balbes150 did I forget to include anything in my post that would prevent you from helping me resolving my slow eth0 speeds? I know I can't expect to receive help, per-se, but I'm hopeful to receive some help from you.
  14. Incredibly slow eth0 connection: 6.5Mbps down and 14Mbps upload. Cable and equipment work great for all other devices. How do I fix? EDIT 1/25/19: if I have not copied over to eMMC yet, could this keep my download speed so low at 6.5Mbps? My other devices get 125+Mbps. Also: I attempted to backup to sdcard and at roughly 3GB copied, the desktop screen froze saying 16kb speed backup and it no longer updated the progress. So because I wasn't able to backup successfully, I decided not to transfer to eMMC yet. I will try booting up from a USB today to see if a backup becomes successful. I've been using a 32GB Samsung UHC1 class 10 card but maybe that's the issue idk. s905x - installed "Armbian_5.71_Aml-s905_Ubuntu_bionic_default_4.20.2_desktop_20190122" with "...nexbox a95x.dtb" armbianmonitor: http://ix.io/lzas
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines