• Content Count

  • Joined

  • Last visited

About TheLinuxBug

  • Rank
    Advanced Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    United States of America

Recent Profile Visitors

1048 profile views
  1. My friend, I think I can propose what is your issue here, please do let me know how close I get: #1. When a sdcard is not booting and you boot from the onboard 8GB eMMc on the Sunvell R69 you will get the error you are seeing above, this is because the u-boot on the eMMc from factory is not made to boot from sdcard #2. While you downloaded the h3droid_installer.img.xz file, you did not decompress the image file with the program 'xz' or similar decompression program for your operating system #3. If you will try again and first decompress the file, then write it to the Sdcard with etcher and place it into the Sunvell R69 I think you will see a different outcome at boot time #4. My guess is also when using other images you may have also failed to decompress them as well. You may want to revisit Armbian images and make sure you have decompressed them with '7zip' or '7z' on Linux before you write them to the card. To clarify, if you fail to decompress the image and write it to the card there will be no u-boot and the data on the card unusable, so it will not boot from the card. If you have written the sdcard correctly, the uboot (bios) will be there and should start when you plug the power in for the board. It is understandable for someone new at this to miss this step, so don't feel too much shame if I hit the nail on the head. My hope is you will at least be able to get something booted. Good Luck! Cheers!
  2. Unfortunately this not the right place to discuss these issues. However, I would suggest you actually read the website instead of just randomly doing things. If you would have read, you would have use the H3ii image and used etcher or similar to write it to an SDcard instead of using the full installation package. If you read the site we have documentation for H3ii and H3resc on the site which you can use for a better understanding of those tools Cheers!
  3. Use H3Droid ( and install Armbian from H3resc menu. We provide the correct fex/uboot for the old h2+ 1Gb ram version in the H3resc uboot/fex selector. Cheers!
  4. Before I got a headache and quit the other night I was dealing with a similar issue. It looks like in the DTBs I was reviewing that the analog codec seems to want to use similar pins as the ethernet adapter. I am not well versed enough in how the DTB is to be formatted and how to map this differently as needed. I had one DTB hacked together which seemed to provide most things except USB and analog audio, but not confident enough in it to really give it out till I know its right. My hope is next time I get a chance to bug a few devs I know and get it working as expected. When I get there, I will share that with you as well. RE: @martinayotte this is actually the info I was looking for, thanks for that! At least got me pointed in the right direction of what to look at. @guidol if you want to mess with it your self, what @martinayotte said should get you started. Cheers!
  5. Yes, most of the devices are controlled by the DTB file, in fact, I compiled the 'staging' wifi driver and played around with enabling WIFi in the new DTB. I actually added the wrong DTB to that tar.gz after all was said and done, like you noticed, sorry about that. I was kinda rushed when I put that up. I did compile a few more kernels and was talking to some devs about trying to get some help with getting devices enabled correctly in the DTB. I actually have a DTB that works for enabling vga framebuffer, ethernet and wifi however ends up breaking USB (assuming your powering through pins, you can actually connect a USB device) and the staging driver in 4.12.y is trash and the kernel panics when you inset the WiFi driver. Glad to hear you found a working dtb for your needs, supposedly there were a few in the packages as you noticed with different things enabled. As I get time I will probably compile a few more kernels and work on the DTB and will post back here if I come up with something better. Though glad to hear what I provided gave you a good start! Cheers!
  6. @guidol Good news and medium good news. Here is u-boot, kernel and dtb needed to enable eth0 and have it work: The uboot has vga and eth0 enabled, however, the current versions of the WiFi module that are around do not work with this kernel and while VGA is in the uboot, it isn't active in the kernel in this. If your goal is to boot up and have eth0 up and access, this should work for you. I am going to test building 4.14.y and 4.13.y branch to see if the WiFi driver is incorporated at any point, the github repos are not very specific about whats been updated and my attempts to build the driver seperately have so far failed for the 4.12.y repo I used to generate this. This should at least be enough to get you started. Once i test a bit more I will upload my .config and provide a link as well. Cheers!
  7. Yeah, having a serial UART is pretty important for working with this board unless you have one of the VGA breakouts or something where you can see whats going on. Cause I don't think these images are setup in any way to otherwise be default accessible. I doubt you will get any feedback on the USB port with the image, however, it may bring up ethernet... can't recall though and if it does, it is likely with a predefined static IP. You can probably mount the image using a loop device on your local Linux machine and take a look at things inside to get a better idea. Maybe a little later today I can pull it out and play with it and see if I can come up with something better for you. If you really want to motivate me to test it, you are best to come to IRC and bug me about it, lol. Otherwise I do have a huge list of 'other things' I will probably start working on first. Cheers!
  8. @guidol You will need to use Google translate but the document you want for ethernet is: It may take compiling your own kernel with the driver built in. To be honest I think I got around this at the time I was testing by using an image produced by Zeepan for my use with Cameras which I believe had ethernet already enabled. Don't quote me as saying this should work, but you could test this image: You should be able to unzip and then DD that to an SDcard and boot it. It should provide, I believe, ethernet, VGA and camera interfaces already in the kernel if I recall correctly. (I have a VGA adapter board and a few other items I still need to add to the site for reference when I have time). P.S. If you don't have an irc client installed but wish to join the irc room briefly there are now web based clients you can use, you can follow this link: to and it will tell you what to do. Maybe this will help you? Cheers!
  9. Hey Guys, I spent time over the past two days updating and if you visit the site and use the navigation at the top right I have added some simple how-tos for certain things as well as have included better links to the resources you need. This includes the dock.dtb file your looking for, if you look through the wifi setup page, I believe it is linked at the bottom: As some of the Chinese resources have been slowly going down, I am trying to replicate the how-tos into English and add pages so that they will not be lost. If you guys come up with anything that would be good to keep on there that I am missing, please PM me here or send me info using the Feedback form on the page. Also if you get stuck on something, I will try to keep checking back here and offer suggestions as I can. @guidol if you get stuck and your familiar with IRC you can come on Freenode irc network and join #H3Droid and I will be happy to try and help you some with getting things working, as I know just how frustrating the thing can be. Have a great weekend! Cheers!
  10. Assuming you are not talking about the OLD Sunvell R69 model with 1gb ram, 8gb eMMc and you are talking about the newest version with 2GB of ram: You must have gotten lucky, mine won't boot normal images with regular settings, seems I got one with shitty ram modules that are way under-clocked like some others have. Additionally, the board has NAND not eMMc, this is why you can't see it and you won't be able to. There is no support for NAND in Linux, there is only a proprietary FTL driver implementation that is licensed which Android manufacturers use, such as in this case. So while you can boot other Linux images and such off SDcard you won't be able to use the NAND except with their specific image, sadly. Cheers!
  11. To note, if you check that Youtube video there seem to be a lot of people in the comments there observing the same issue. They state they also have this exact same board and it won't boot at all either. I am guessing bad quality memory, like in the last box, except in the last box it simply prevented any good use of 1080p cause the DRAM wasn't fast enough. In this version is seems it causes the need to likely set DRAM super low for it to boot. Will probably take using uboot/fex for OPi Zero +2 and trying to figure out something usable from that. I really wanted to get H3Droid working with this board for our next release but at this point with the mix of quality / revisions that are possible this may be in vain, because even if I get it working, may not work for others. No going back now though... will just have to keep at it! Cheers!
  12. Super odd! They must have made revisions of this board and some are different. I promise you mine will not even boot that Beelink X2 image mention in the video. The ONLY think I have gotten to boot was OPi Zero +2 image and its severely crippled. I will post images of mine below, maybe there is some subtle difference I am missing? So far my link seems limited so I am guessing they made some change mid-run of these, like using sub-standard memory that needs an extremely low DRAM setting to operate. Only thing that seems to make sense as to why all other images won't boot. Will continue to update if I make any progress here. Cheers!
  13. @Jani-Matti Thanks for the video, I now understand what you were saying better, the Armbian image for Beelink X2 should supposedly work. I am actually going to test that one now and will report back if I am successful or not. Thanks!
  14. Okay, it seems I missed something; supposedly the Orange Pi 0 +2 H3 image does boot on the NEW Sunvell (R69) H3 2Gb Ram, 16GB Rom image (NAND will not work obviously). However, it boots without USB, ethernet, wifi... basically anything but HDMI and UART. So obviously need to get fex figured out but I guess I at least got it booting. Still looking for any suggestions from anyone that has it running well already. Will update as I make more progress... @Matthew Hodgson Please realize there is 2 different R69's now, the old one, yes you could run almost any image and the Beelink X2 image worked, so did H3Droid out of the box. Problem here is, this new box is not the same. It uses NAND storage and it seems has some very specific configurations needed in the fex which are custom (thinking possibly very low DRAM settings or some specific setting in the fex that is only available in the OPi Zero +2 image). It is either you are thinking of that box or you got a different revision as I spent hours trying to get different images booting and the only success I had was the OPi Zero +2 H3 Armbian image and that only works somewhat with most of the peripherals missing. Since I am still working to make it work with H3Droid, at least that is my goal, I welcome any feedback which may help and will be sure to update here as I make progress. Cheers!
  15. You must have some weird SDcards, cause on the old R69 I had no problem booting at anytime from and SDcard. And I did a lot of booting while I was testing H3Droid. So it seems maybe you need to stay away from those no-name brand SDcards. This however has no effect on the new box. I have been testing and am yet to get anything to actually boot. I did notice in the other thread someone mentioned the OPi0+2 uboot seemed to partially load, so may test that later. Cheers!