erew

Members
  • Content Count

    18
  • Joined

  • Last visited

About erew

  • Rank
    Member

Recent Profile Visitors

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

  1. Hi, not sure.... Ive just opened a fresh install of Armbian on a USB stick and the Extlinux.conf there shows the # in the place I originally indicated (copy/paste below) LABEL Armbian LINUX /zImage INITRD /uInitrd FDTDIR /dtb # FDT /dtb/meson-gxl-s905x-khadas-vim.dtb APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 The # may get changed/removed if/when you install to EMMC/NAND as the Extlinux.conf file is used for booting from EMMC/NAND storage and not off a USB card/SD/TF card.... so that file is only used in that instance of booting from internal storage. The # is typically used to say "dont use this line in the code" ..... so its possible something has been changed on the boot process too. Its not something Ive seen yet, but ill take a look sometime.
  2. Noticed this post with the question above... emmc to SD.... I wrote instructions on doing this+videos showing how to do it. Thought you might find them helpful if you wanted to do this for backups etc. Making a Backup of your emmc via the GUI https://www.ondroid.net/armbian-os-backing-up-emmc-nand-via-gui/ - What you will need - All the commands/screens to perform this - Includes 1 x video showing the whole process Making a Backup of your emmc via Command line https://www.ondroid.net/armbian-os-backing-up-emmc-nand-via-cli/ - What you will need - All the commands/screens to perform this - Includes 1 x video showing the whole process Thanks erew
  3. @Janaboy My rough (dont quote me) understanding of this is that its a mix of your DTB (Device Tree Blob) file and also actual driver files, hence trying different DTB files, with different results. The DTB file is basically telling the system which drivers to load at startup. I believe the Beelink Mini MXIII box has an Aigale AW-CM273SM and Qualcomm Atheros QCA9377 for WiFi/Bluetooth.... And I have no idea if anyone has ever written a driver or if one of the DTB files activates the driver, though I can seem some references around the internet to people trying. So, if you can find a driver or if one exists, you can write your own DTB file, which might work OR obviously test other DTB files.... (this is why Im thinking to create a database so that we can find the best combinations for which DTB to use with which box). The other alternative is to use an external usb dongle. Im not 100% confident which one would or wouldnt work, but have seen the CSR bluetooth dongles referenced before in ubuntu/armbian forums.... and they are cheap as $2 kind of thing.... Maybe someone else on here has experience with them. (If I had one to hand Id give it a go for you, but sadly dont) Search google for csr bluetooth dongle if you want to try this route. Im not yet at a stage to start writing about loading other drivers/editing DTB files etc.... as Ive still got my own research/experiments to do on that.
  4. @Janaboy Thanks, and glad it helped!! Im working on a slightly updated guide... and potentially going to collate a list/database of DTB files/boxes and what works/doesnt work (HDMI, WiFi etc) so its a bit easier to figure which DTB file to use... So Ill post something on that in the future!
  5. @imikei Youve not mentioned which box you have.... However I think you may end up needing to reset it back to factory (if its not even booting to the internal Android OS anymore), so Booting Problems section of this post. Once thats done, if youre sure your using the correct DTB for your box, Id suggest trying an earlier build of Armbian or one with a different kernel version to see if that gets you working. Im guessing you mean username/password at the initial text screen where you log in as root and change the passwords etc.
  6. @baku1413 My suggestion is this.... If as you say, you can get it to boot from an SD card, load that up and get into Armbian, load a terminal window up and run lsblk -o NAME,FSTYPE,LABEL,SIZE,MOUNTPOINT From the section of my original post Backing up if you are using SD card/USB stick for booting/running Armbian OS in step 7 and "Reveal hidden content" .... there is an image that shows what you should be seeing for mmcblk0 and mmcblk1 and the (one being an internal and an external drive).... and the partitions under them e.g. mmcblk0p1 (drive 0 partition 1) mmcblk0p2 (drive 0 partition 2) mmcblk1p1 (drive 1 partition 1) mmcblk1p2 (drive 1 partition 2) The ones with ROOTFS and BOOT on them are your SD card.... Any others are either the Android OS or ROOT_EMMC and BOOT_EMMC (the copied/installed Armbian OS). So maybe from that, you can figure IF it can see multiple drives? If its already copied once because ROOT_EMMC and BOOT_EMMC exist? If it cant see anything other than your SD card etc. Its not really something I can diagnose for you as I dont exactly know the install routine inside out, but perhaps this might lead you in the direction to figure what is occurring.
  7. @anonymox Are you trying to run this from a USB stick??? You need to run it from an SD card I believe.... because a USB stick will be called /dev/sda1 and SD card will be /dev/mmcblk1 and I think the script only works with /dev/mmcblk0 and 1 (one being the SD and the other emmc/nand) Either way, from what the log says, it cant see the SD card or the emmc. (Also check you only perhaps have the 1 SD card plugged in and no other external media .. usb stick/hard drive etc).
  8. @baku1413 I know that some TV boxes just wont boot off the emmc.... you are better asking on the specific TV Box forum e.g. "Armbian for Amlogic S9xxx kernel 4.1x (>= ver 5.55)" etc... and see if anyone else has experience or knowledge of your specific box. Beyond that, I cannot think of any reason why the script that copies your SD card over to the emmc would wipe your SD card..... though that script tries to guess which is your SD card and which is your emmc memory before it starts to make its changes, deletes/creates partitions, copies files over etc. So perhaps the script is detecting your SD card/emmc memory incorrectly..... I really dont know. What you can do, is a least when you have re-created and booted from your SD card, is to open Gparted and see if you can find a drive that has BOOT_EMMC and ROOT_EMMC on your TV box, that has data on it.... that would at least suggest that the install script did copy over your files to emmc, which might mean your box is one of those that doesnt boot. Also, did you check out the section called "LOST.DIR, System Volume Information and Android folders cause problems booting off eMMC/NAND." to ensure that if you have a BOOT_EMMC partition, that it doesnt have those folders on it!!! As they can cause this problem of not booting from emmc as well.
  9. Manual process to setup the partition at the command line - Backing up if you are using emmc/NAND for booting/running Armbian OS THIS HAS BEEN INCORPORATED INTO THE SPOILER/Reveal Hidden Contents on the main document.
  10. Ive written/posted it..... so see if that works for you! You need the section "Backing up if you are using emmc/NAND for booting/running Armbian OS" Its easier than it looks, but I wanted to make it very clear for people to use, so hopefully it is. Thanks!
  11. Ive updated the guide I wrote to cover these additional topics: Example of setting up a system Example Setup on a MeCool M8S PRO w (Change your DTB file in uEnv.ini and extlinux.conf for other boxes). - Hardware you need - Software/Downloads Setting it up - Steps to image your SD Card/USB stick from a Windows PC - Installing onto the MeCool M8S PRO w (Or any other box assuming youve changed the DTB) Congratulations - If you reach here you will have a working Armbian server. Booting Problems and getting your system to boot Booting off SD/USB problems. uEnv.ini and extlinux.conf (Required for booting Armbian) - Editing the files and picking the right DTB. - What do these 2 files do and why cant I boot off emmc internal ram? - What should the files look like? Installing onto emmc/NAND - The internal hard drive of the TV box. LOST.DIR, System Volume Information and Android folders cause problems booting off eMMC/NAND. What to do if you brick your device. Ive done something and now my box wont boot/stuck on a splash screen/is a brick what do I do? - Getting the system recovered - notes - Doing the recovery Bootable Backups (can be used to migrate to another TV Box too) Backing up if you are using SD card/USB stick for booting/running Armbian OS - You will need the following to do this - How to get things setup and do it (create/restore your image) Backing up if you are using emmc/NAND for booting/running Armbian OS - You will need the following to do this - Option A and Option B - How can I tell Ive booted from my Backup SD card? - What have we actually just done? - What can I do with my imaged SD card?
  12. I am about to write an article on doing this. are you on eMMC/NAND or an SD Card? I will be writing some answers in here, over the next few hours
  13. Yes, sorry I dont know of any way to get it working on that box. Id like it working too. I tried all the different DTB files just over 1 year ago and none of them got the WiFi working. If you do find any solution (either an updated DTB file on the latest Armbian, or a manual driver install somehow) please let me know! Thanks!
  14. I think there are 2 versions/revisions of the Mecool M8S Pro w box from what I picked up elsewhere on the internet. Mine wont install to emmc (well it copies, but wont boot off it, no matter what I try). My experience with it, is in the above article. Which does cover recovery of them (if you ever need it).
  15. For anyone getting stuck with their box, Ive written a guide, that covers the following: Example of setting up a system Example Setup on a MeCool M8S PRO w (Change your DTB file in uEnv.ini and extlinux.conf for other boxes). - Hardware you need - Software/Downloads Setting it up - Steps to image your SD Card/USB stick from a Windows PC - Installing onto the MeCool M8S PRO w (Or any other box assuming youve changed the DTB) Congratulations - If you reach here you will have a working Armbian server. Booting Problems and getting your system to boot Booting off SD/USB problems. uEnv.ini and extlinux.conf (Required for booting Armbian) - Editing the files and picking the right DTB. - What do these 2 files do and why cant I boot off emmc internal ram? - What should the files look like? Installing onto emmc/NAND - The internal hard drive of the TV box. LOST.DIR, System Volume Information and Android folders cause problems booting off eMMC/NAND. What to do if you brick your device. Ive done something and now my box wont boot/stuck on a splash screen/is a brick what do I do? - Getting the system recovered - notes - Doing the recovery Bootable Backups (can be used to migrate to another TV Box too) Backing up if you are using SD card/USB stick for booting/running Armbian OS - You will need the following to do this - How to get things setup and do it (create/restore your image) Backing up if you are using emmc/NAND for booting/running Armbian OS - You will need the following to do this - Option A and Option B - How can I tell Ive booted from my Backup SD card? - What have we actually just done? - What can I do with my imaged SD card? I dont expect to answer every question/solve every problem, but it perhaps centralizes a lot of questions/answers people seem to keep asking on the forum.