Wow price wise they are interesting! Just no 1G eth but for a tv box thats ok. Bad luck i wanted it as a poor man's nas
Posts by lumpi
-
-
Hopefully in a few months: Joining Collabora for a summer of Panfrost
Thanks! Hope to turn my 2nd tv box into something useful soon, now that #1 (Allwinner H3) works quite reliably.
-
How far are we from a working panfrost image for s912?
-
Are the nightlies still not working properly? Some are from 6th others from today (10th)
-
...furthest right pin is TX and the pin next to that (4th pin from left or 2nd pin from right...
if you look at the silkscreen of the pcb you can see a little white triangle above the rightmost pin, this and the fact that the solder "eye" has a square shape means* this was considered pin 1 by the engineer who created the board
Not important at all, but i had to scratch my itch as an el. eng...
* = is a very strong indication
-
Right ?
Pin2 (2nd from right) is ground, as its connected to the ground plane. As far as I can judge from ukmark62 's pic
-
Thanks so much for that - I was really confused. All this stuff is greek to me. Big learning curve ahead. So basically, I will still have an empty sd card after the dd command - but the file is there and hidden. I'll give it a go later and let you know how it goes - thx again
You are welcome!
I'll try to answer whatever I can. I'm just kind of an advanced linux user, by no means I'm a developer.
If you are interested in what dd does try man dd in a console window, or well... dd(1) - Linux manual page
Its not perfect, neither specifically for H6, but its an intro to the boot process:http://linux-sunxi.org/boot_process -
ukmark62 that dd command jernej gave you before means that you take the spl file as input (if=) and are writing it to your sdb as an output (of=) with a blocksize of 1024 (bs=) and before you write you skip 8 blocks (seek=)
So all you do is write the raw bits of your spl in the empty space between the MBR of the card and the first partition (sdb1)
So you won't see any files, but the rom bootloader code of the H6 checks at this very location for a magic number of a bootloader and if present loads the spl.
-
You can, but in this case kernel config needs to be tweaked, to enable A10 drivers. You can try it based on my A20 branch here: GitHub - jernejsk/LibreELEC.tv at a20 (check last 3 commits) the
honestly I'm not really interested in getting this beast back to work, as my little daughter used it to learn walking, so the LCD has a couple of nice black spots. But should you be interested in testers shout out loud
that's still not possible, but should be close. I think lima drivers needs to be improved? I don't really know.
oh of course LIMA that I completely forgot about. I didn't actually mean Replicant style, but vendor independant mainline based android. Let's see what will happen on this front. If anything at all
Maybe the pine phone will bring this up to the frontline sometime in the future. -
Oh how I LOVE not seeking a post in over a year. Yeah!!!
F*** Me!
I was dumb enough to get a Beelink GS1 K6.
Now Google Play won't even run.Jernej has images for pineH64 and as your box just got a mainline dtb you might soon get a working LE for your box
-
I have somewhere an inet97f2 tablet based on A10 with some old fedora on it, should i have a look for it?
I know it's pretty OT but such tablets would also be a target for a completely free mainlined android, ok i admit probably rather the A33 variantss than mine (now even more OT
) -
beelink wifi not working
no need to open the box, just enter:
Codecat /sys/bus/mmc/devices/mmc1\:0001/mmc1\:0001\:1/deviceif the reply is:
Code0xf179you are out of luck, as its the realtek version with crappy out of tree driver on GitHub...
-
Driver for your wifi is not hard to find or even to include it, it's just that it's PITA to maintain it and probably doesn't work with iwd, which is planned to replace wpa_supplicant in near future.
replacing wpa_supplicant sounds promising
i can live with my 1m cable its just something to play with
-
even it's late this looks better: GitHub - jwrdegoede/rtl8189ES_linux --> something for sunday
-
edit: deleted as it contained useless info
-
You should make another update with same update file. U-Boot is not updated in such way. BTW, you are bypassing a lot of checks by such update.
well it did the update after the reboot, as the tar file was still in place, I just copied new Kernel to be able to unpack the tar
BTW bad luck:
CodeLibreELEC:~ # cat /sys/bus/mmc/devices/mmc1\:0001/mmc1\:0001\:1/device 0xf179it's definitely a realtek, not yet 100% sure which one...
-
lumpi ah, you are on old image... Actually I mentioned the issue, but yes, that's the one. Copy files manually in that file and repeat update again to update few missing things.
BTW, new images use kodi 18.2-rc1 so some things like addons probably need to be updated
OK thanks!
I just copied new kernel and dtb to /flash after downloading tar and then rebooted no its starting with new system
-
lumpi Current Beelink X2 DT file is broken regarding wifi (missing power connection and one clock for brcm module), so you can't check which module you have. You can update with this file libreelec-h3.arm-9.1-devel-20190513205044-0fffb04-beelink_x2.tar If you have brcm module, you'll have wifi.
The update from 20190324 to this didn't go through.
Is this the compression issue, that chewitt mentioned?
