ljones0

Members
  • Content Count

    21
  • Joined

  • Last visited

About ljones0

  • Rank
    Member

Recent Profile Visitors

588 profile views
  1. Hello all! Noticing a problem with the latest versions of armbian (I'm using the files avaliable here. In particular I was using the "bullseye_current" image however I also tried some of the files in the archive. Unfortunatly wifi dosen't seem to be quite 100% in these images -- I'm unable to connect to the internet via wifi and I'm also finding the m2 zero can barely find any wifi devices at all. I did notice these errors though; [ 8.565750] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 8.588984] brcmfmac mm
  2. So after looking at this website am I correct in thinking that there's no xorg accel/drivers for the R69 until the 5.2 kernel? ljones
  3. Ok I gave that image a go for the rk3288 device on several different microsd cards, but it failed to boot from any of them. However I managed to find some old bits 'n' pieces here and here it consitsts of downloading a script which writes some boot files to a micro sd card and also someone's ancient pre-rolled version of ubuntu. That worked although I am not sure quite how everything ties up -- that's the first time it has worked. If anyone wants it I could always put up an image of the micro sd I created with those old files and scripts for the rk3288/mk902ii. It worked on my old
  4. How would I go about getting the relevent files from my R69 though? Or do they have to be done manually (presumably android uses some other method for booting?). All this reminds me of a problem I had years back with a similar (in form factor) device, I believe it was an RK3288 based device, "MK902II". Closest thing to it I think was a device called a 'firefly' but my device was just too different (it did not boot, like the R69). Might eventually be worth retrying what with the situation with dtb files and microsd cards. ljones
  5. One more thing -- I managed to even get xorg and xfce to start on mine(!). But X dosen't seem to have any acceleration however. After looking around online I see (if this is correct btw as I'm still not 100% on what the CPU is on my device without pulling the heatsink off x.x ) the H2+ CPU and H3 CPU are very similar - it's just that the H2+ is a cheapo version of the H3 with no 4K output and gigabit ethernet. At a guess they both use the same video chipset (Mali400) but there dosen't seem to be any x accel for mali 400 in armbian? I did try to install xserver-xorg-video-armsoc-su
  6. I'll give it a go again but I did try both etcher and dd and they both gave me the same results. I've not tried it recently but even using a different PC resulted in the same thing happening. One guess - maybe not every micro sd is created equally? I'm really not sure but from memory don't some of these arm-based devices require some sort of boot code to be written at a very specific place on a microsd? Maybe that's the problem or prehaps the data "ends up in the wrong place" so to speak as (for example) one 16gb card and another might be just very slightly different capacities. Th
  7. Intresting that one worked for me on the integral micro sd - I managed to boot to a login prompt (though I've not tried it beyond that). I did try also that image on the new samsung 16gb, but it didn't work on that one. ljones
  8. I tried the branad new samsung 16gb btw. It failed to boot like many of the others. BTW Here is a picture of the sd cards. ljones
  9. Well I decided to give it another go, and this time I seem to have gotten slightly further. I managed to find the one-and-only local copy of the image that I used originally (I'd remembered to copy it onto a *very* old and painfully slow kingston 1gb usb memory stick). As a precaution however I also decided to buy a new sd card writer (and a new micro sd card) just in case the one I have was playing up for some reason; I'm now using it. I've been trying it and my device (R69) seems to really *hate* some of my micro sd cards. I tried a sandisk ultra 8gb to start with an
  10. If my device is a wechip one then one thing I thought about doing is trying to see if there was a copy of the original android firmware about for it, download it and then write it to a micro sd card. Since I installed a terminal program on my device in android if it boots from microsd to android then it would be clear to see as the terminal program wouldn't be there. I did find wechips' support website but they don't seem to support their own device; no mention of an R69 device on the support page, and although that sticker on my device says "MXQ-4K" and there's a MXQ-4K device on
  11. I managed to get the top off the device as it appears to only be clipped on. Here's one side of the board; ljones
  12. :-( I don't know. I'm not even getting that far. Any attempt to boot from the SD just results in an empty screen - about the only thing I do see if I try to go off the microsd card is from the display itself, "No signal". I'm starting to think my box is faulty, it would not suprise me as a lot of these boxes are cheapo chinese devices. Only other thing I can think of is maybe the way this device boots gets locked down or corrupted in some way? ljones
  13. Still no joy with booting. Here's what android has to say about the CPU btw; $ cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 1 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revi
  14. Intresting but how do I go about getting the dtb file from the device? I'm also going to try a different computer and see if it is something there which is causing a problem.
  15. Hello all! I have one of these (possibly!) a sunvell R69 tv- box (it says R69 on top and has a green line going around it). I did try to check on its built-in android to see what CPU is in this box; I couldn't really find a 100% answer but it is either an H2+ or H3. I did download and manage to get to work one of the armbian images (but I cannot remember which one it was) but then later used the micro sd for other purposes. I then tried downloading the armbian image for the orange pi one (I can't remember if that was the one I chose earlier; I've seen others use this im