Posts by buzzmarshall

    Is there a particular reason to change the MAC address? Normally each device should be manufactured with a unique address anyway.

    One would think that you'd be right about that but that is not always the case.


    Every time i bring in a bunch of OEM boxes from the factory for some reason they are usually always all on the same mac address.


    I have always used a autostart script similar to what Iridium posted for years when i try and run them on my internal LAN otherwise they conflict even tho they all have different static ip's and a properly populated host file for my LAN.

    Seems kinda pushy and bold for some normal user to decide how important someone else's community is and make demands like that. Its their house and their rules so i would suggest you find a better way if its important for you to be here.


    Just my 2 cents and sorry for my blunt reply but you may want to rethink how you present yourself as this is a helpful and usually friendly environment the team try and create for everyone.

    i could be wrong but was under the impression that is the same as the xaomi unit and had some weird app that you could fish the bindings out to get working but under android the app controlled it... I looked at a couple of them for a local dealer last year as they came with some millet tv box he got off bangbad but wanted to work on a bunch of oem boxes he bought from ENY. It seemed to be some kinda propriatary link that i never bothered wasting that much time on...


    try googling Openhab Xiaomi Mi IO Binding as i seemed to recall someone mentioning something about being able to pull the bindings from the Android app that it ran thru.


    i maybe wrong but it sure looks like one of the the xamomi remotes tho...

    Ya that is true for sure. Under the circumstances tho i think its good that the python3 push is happened concurrently with LE and the others efforts in moving up to mainstream tho rather then having them consecutively and to be honest am glad to see the move, I quess now it will up to the add-on devs to start looking into moving forward in their respective projects as well as things move forward.


    but your right it may be bloody for a bit.

    For the sake of cheapness there is nothing wrong with the S912's other then the typical lack of support for some of the boxes hardware features when running under Linux (LE). It just means more things need to be done in software. I have good 4k tv's in the house and typically stream most incoming stuff in 1080 without any issues, as well i have a huge storage network which everyone in the house streams local content from and even some of the 4k stuff still works good enough for our use. I would suggest tho whatever you buy try and get at least 2g of ddr.


    Some of the newer x3 boxes like the A95x3-f3 because of the newer mt7668 chipset have no wifi-bluetooth in LE or any of the other current forks at this time. The other ones you mention you might need to do a bit of checking to see if they are in the same boat as i seem to remember some of the Tanix boxes were using a old no longer support wifi chipset. I quess you would need to figure which exact box your looking at and then just check and see if theres anyone bulding for them and what issues if any people were having with them.

    clarkss12...


    I did mess with one that one of our group guys got back in Dec and eventually got a modded LE 9.2 build using the generic project mostly working, but to be honest it was a big waste of time as the guy that owned it had nothing but trouble with the device pretty much right outta the box... Windows 10 kept crashing and the box ran hot which i suspect was at least partly to blame why Winblows was really buggy and locked up and crashed a lot.


    He got the unit because we've been looking around for awhile for a SoC without the typical Arm GPU and the Intel was appealing and we figured we'd loose winblows anyways as really we were just looking for a better board for Linux and LE.


    After some tinkering I got LE working by 1st making a full linux distro run on a modded kernel on the box, we used the kernel tweak learned from that to tweak LE's kernel and got it working...


    Thru all of this tho the box still had heat issues and kept crashing so we stopped and he tried returning or getting it swapped out but ran up against a wall with Customer Service as they didn't like the idea of messing it with.


    In my normal job I do a lot of mb repairs on Macbooks and a variety of other low level boards as i do reworking and repair as well as design and consult on custom boards and I've seen a lot of poorly made crap over the years and the board in his box was manufactured poorly with things not down and poorly oriented before going thru the oven. The sad part is its not the 1st time i have seen that kinda poor quality come out from Beelink before. Its just disappointing to see a supposed Premium maker as they claim produce bad boards in the same manner you would expect from some knock off clone shop charging half the price, I did consider pulling the chip and reballing it but for the time investment it was not worth it, but i am sure that will be the last Beelink product he buys.

    Anyway...To your point.. If your up to building LE git sources you should be able to build the Generic project and work out from there as i am not sure if anyone else has really gone down this rabbit hole yet...


    Tigro... Sorry don't mean to hijack your thread so i will shut now... Chewitt and Da Flex i think have probably helped so i need no say anymore.

    Not that its really any of my business but still i will throw it out there as a lot of people looking for the easy way end up with things that they may not understand what its capable of doing or being used for..


    Indigo is something you may want to rethink as it can cause issues...


    Not looking to open a discussion on the topic as its probably taboo here (for good reasons). just thought i would advise caution in regards to it... as there are safer methods to accomplish what it does...


    Sorry if i am out of bounds saying so...

    Most of the various distro's work the same way which is, if there is something bootable in the sd-slot it will try and run that and if you take the card out it will then revert back to running the resident Android version that is on the internal storage.

    LE is kinda in a transitioning mode while they work towards getting things up on the mainstream sources so there is a bit of slim pickings in most the amlogic stuff right now while their guys are busy...


    There are a few around tho that have their own forks of LE so they can maintain some of the Amlogic boxes, just not sure who's got what so you need to do a bit of checking around.


    I know that box is able to run the newest because i have matrix and the 18.5 running on it and it works fine, the issue is just things are kinda quite here in the Amlogic area which will probably change someplace down the road.


    Trying to update the kodi version on your existing software is more work then its worth as you might as well just do your own build if your going to mess with that.

    Don't get me wrong as i am not saying it won't run.


    Hell i have matrix 19 running on older S812 and up.


    I am just saying that if your not self sufficient in developing and are like most that rely on other developers for firmware then even a free box without current software really is not worth anything other then a parts board to be played with or thrown on to your pile of old devices.


    Out of all the different developers out there to a large extent they all are based on OE and LE and as such pretty much make use of the same build system that each fork has altered for their own purposes and the amount of support for the older boxes is getting smaller all the time.


    Currently with LE focused on moving linux to mainstream and off the old proprietary BSP's and help push Kodi thru the python 3 upgrade they have chosen to support a smaller pool of devices while transistioning... So most of the other Distributions are trying to support some of the older devices while still supporting the older propriatary BSP's for the devices they have chosen to support.


    All I was saying was that unless your willing to learn or already have the ability that you will probably have to either rely on someone else's firmware and if you can't find any then you will be at least at a minimal level have to take some existing build and hope to mod it enough to get it to work. Maybe just a dtb change maybe more...


    So as much as $15 bucks is a good deal you may not have much of a choice other then running Android and then Kodi as a app, which to me is something not worth the effort.


    I have been running Linux on these devices going all the way back to the Dream devices as the idea of running Kodi on a OS that is basically a touch screen OS is just dumb in my opinion if your trying to get the best performance out of Kodi. but hey to each their own...


    But just to be clear i never said it can't or won't run.

    Sounds like a deal... But... there is always a but ...


    Storage space is not as big a concern depending on how much crap you keep on the box...


    Personally i would never buy a box these days with less then 2g sram as more Sram is always good and besides pretty much the only place you see 1g devices these days is in New Old Stock that the crappy dealers will try and dump just to get their costs back.


    Its not that it Can't run LE or any of the LE clones/forks like CE/EE/AE or others but its already getting hard to find developers releasing for older devices so no matter what the deal maybe it could still end up as a waste of money if your not into taking things into your own hands development wise.


    Kodi has already moved to 18 and in the near future will be going to 19 and unless you want to just settle to keep it going on 17 and python 2 or maybe if your lucky enough to find a version with Kodi 18 your choices will keep getting smaller.


    But if that is all you expect out of the device then it may serve your purposes...

    No Probs...


    No misunderstanding on my part as i understand the term but kinda ignored it for context as i am assuming his reference is to the current open source developers trying to create a reverse-engineered open source solution or possibly from some other platform using the Mali's which maybe hacked to make useful...


    Sorry, i made the assumption by your interest in them that you were maybe of the type wanting to go down the development rabbit hole and was just trying to point out that blobs and info can be found if one wants to look and that finding the DDK even a older one is a good source of info for anyone trying to create blobs for their own non public use to test on..


    Blobs are a pain in the butt but doable, but they are ok for the big factories that can absorb their costs whenever they need them created but the small Linux developers can't absorb those costs every time they want to upgrade their device leaving open source solutions as the only real answer which is why i make it a point to follow the open source development to see how things are going...


    I have watched a lot of start/quit linux open source attempts over the years but this last year with the current group of developers has really kicked the ball closer to the net , its impressive and this time round appears to show the key dev's involved are in for the long haul which is great.


    sorry for the confusion...

    Assuming he's referring to private stuff given to them but still if you want to put the time in you should be able to locate alternate Mali uses OTHER then Amlogic, Rockchip and the rest we typically see here...


    If your good with ftp search engines and figure out the search string to look with, you will find there is more sources of information on the Mali's then just the ones here everyone typically associates the Mali's with...


    The news feeds (uucp) is another place to look for info...


    Blobs are floating around tied to various DDK's and linux revisions, and if your resourceful enough you may even come across a DDK and work towards creating your own blobs... just understand doing so has some legal implications that you may not want to step into... (hence why most of this is private and will stay so)...


    Thing is tho if that stuff is used for informational purposes there is nothing that says you can't use it and other info to create your own without using the DDK which technically is arguably without the same legal implications of using a unlicensed copy of the DDK... you will probably need some rudimentary Assembly skills on Arm as well...

    Motherboards can be funny animals as they all pretty much work in general but then in a lot of the cheaper designs there is usually a few little quirks that can pop up that maybe for general use go mostly unnoticed by users... sometimes just moving things around inside the case and where cables are crossing things can introduce things into systems... some of the cheaper boards can be picky that way...or then again it could just be a bad board to begin with...


    Things like bad caps on a board which is not all that uncommon can cause weird noise issues and intermittent things like booting issues... I recap boards all the time and have seen even some more expensive boards with caps that are drying out that lead to all kinds of issues...


    Hopefully its just something simple like moving some cables around...


    One other thing i would make a comment about is that i am assuming you swapped out the boards yourself and if so make sure the grounding posts are not touching on anything other then the ground landing pads on the board... its the grounding ring (pad) around the mounting hole on the board where the mounting screw holds the MB into the case... Some boards that solder ring built up around the hole is heaped up with more solder then needed and then when tightening the screw down it gets squeezed and widens out till it touches some board trace that laid real close... Sometimes when things like that happen its not bad enough to stop the board from booting but causes a bunch of intermittent issues...

    Can you boot any thing via USB on that workstation or is it just the LE stick that wont be found...


    In the bios make sure to Disable the Secure Boot for Legacy otherwise you may not see the usb option...


    If your actually able to boot stuff from USB then as Klojum suggested try a different writing app... You may want to check and make sure that the machine has the last released bios for it installed as there were a few fixes in the last release that fixed a few things, some of which seemed to help booting from a wider variety of sources...


    In general tho those machines are not the greatest things to play with things like Kodi as the machine is more designed and suited as a workstation for something like CAD... Last time i ran kodi on one of them was back around the days of Jarvis-Krypton and even then they were kinda buggy and i had to swap out the video card for something more mainstream and then found it didnt play nice with the ECC memory till i swapped it for a different brand...


    Not to put a damper on your idea and i am sure with enough playing around you will eventually get it to work but depending on what options are on the machine you may end up playing around with a bunch of things trying to get it to work right... Their were great machines for what they were meant to do but can be touchy trying to get them to run what you want and being a HP makes things a bit worse as like IBM they like to do things their way...


    I still have a couple of them here with maxed out cpu's and memory and was using them to run Unity and some PCB Cad software but finally gave up trying to keep up to date versions of software on them as they are just to much work to run newer software on them...