luminx that is benign message,nothing dramatic. It will be removed.
Posts by tromo
-
-
tbe vuduo4k? That is work in progress, but, anyway, what you do describe should and could not (ah well, crap happens all the time, but...) happen. Need a bit more info.
-
Bene, grazie a parole gentili, stiamo cercando di ottenere una soluzione con l'aiuto di alcune persone molto simpatiche su questo forum. Work in progress, but...
-
Thx m8, will PM you.
-
Each one is a separate dedicated system
One is DDR RAM 128MB to the Spark system
One is DDR RAM 128MB to linux system
Each one is 128MB
Not really important, and not nitpicking, but technically the above is a bit incorrect. Bunch of memory is used by kernel, drivers, Frame Buffers, video processing, etc.
-
vuduo4k dropped, waste of time and nerves without the box for both users and devs.
-
If I recall correctly, there are at least two possible reasons for this kind of error:
- corrupt u-boot environment
- bad capacitors (the ones under the card reader seem the 1st to go, but changing other big ones cannot hurt)
- less likely: bad security chip, bad NOR chip
In a case you can access the box via ttl/rs232 here is 8900 bootloader.
-
Uhh mate, help:) This is really non issue on most E2 boxes, especially on osmio4k (being quite capable box and able to spoof MAC).
- Kodi: stalker plugin or simple itpv (EPG/no EPG and similar drama)
- E2: dedicated lists from, hmm, 'provider' (EPG/no EPG and similar drama) but less fuss than starting Kodi etc...
- Newer Smart TVs. Funny stuff, I see that Zamzung has at least 3 apps in on-line store for such needs, makes one wonder about the attitude of big corps and legalase stuff :)Of course not every 'provider' does offer all the options, although all the possibilities are in the middleware. Probably a case of 'manuals are for lesser beings' :)
-
I've just wanted to try this on osmio4k pure2, but after a very light and short inspection, it just does not make any sense:) This seems to be some HiSilicon version ,as it NEEDS some libs that are not available on a non-hisil box.
NEEDED libhi_common.so
NEEDED libhi_msp.so
NEEDED libQt5WebKitWidgets.so.5
NEEDED libQt5Widgets.so.5
NEEDED libQt5WebKit.so.5
NEEDED libQt5Gui.so.5
NEEDED libQt5Test.so.5
NEEDED libQt5Network.so.5
NEEDED libQt5Core.so.5
NEEDED libpthread.so.0
NEEDED libstdc++.so.6
NEEDED libgcc_s.so.1
NEEDED libc.so.6
If this works elsewhere than on a dedicated HiSil model/box, I'm sorry on unjustified suspicion and would be very happy about it.
-
Pls check the TEST directory....
-
Great, thx, and congrats on a nice work then!
-
Not really my battle, nor war, alas I would recommend to use latest 6.2 pure2 image as a base. But ok :) If this works, everybody happy. I guess :)
-
Well, a year or two later compared to others.... but there it goes. Patience is a strange game :)
-
Great, it makes sense, including code wise:)
-
This sounds like a wrong image (for clone?). But, regardless, I would stay clear from 6.3beta images, especially for older boxes. YMMV. 6.2 are still a safer choice in many cases.
-
Well, H7 is a really good box that can open a lot of stuff (and it did all that before many others could), but yes, for C band and blindscan it *might* be lacking at the moment. The problems are not BRCM related, but Front End/Tuner HW and SW , which are from another company. Sadly, at this moment, I'm not able to check C band stuff.
-
It is a kinda snafu stuff, for a proper (whatever the definition is) one ***might*** need hw support, but than again in most cases a simple ('simple' is a wrong word, let us say that standards are respected) is enough.
Sadly, it is PIA (or $$) to have it properly implemented, and we have this strange fun ---> and blame it on another guy game.
Than again, as very few users need this.... -
Strange, I cannot see any drama (except all the standard AML stuff) on HD stuff.
-
Ah well, the meaning of 'blindscan' is a bit elusive/shady among manufacturers/users, especially in C band. A proper one (in a true sense of the def) should not care about predefined satellites.xml or other stuff, but do a 2 pass scan; 1st spectral analysis (get something strong and probably reasonable) and then do all the possible DVB parameters checks to see if it makes any sense. There are at least two more approaches to this problem, with less or more happy results (time vs quality).
-
Uhh, in all the OEA based images you'll be able to use one of these chipsets:
enigma2-plugin-drivers-network-usb-ath9k-htc \
enigma2-plugin-drivers-network-usb-carl9170 \
enigma2-plugin-drivers-network-usb-rt2500 \
enigma2-plugin-drivers-network-usb-rt2800 \
enigma2-plugin-drivers-network-usb-rtl8187 \
enigma2-plugin-drivers-network-usb-smsc75xx \
enigma2-plugin-drivers-network-usb-zd1211rw \
enigma2-plugin-drivers-network-usb-rtl8812au \
enigma2-plugin-drivers-network-usb-r8723a \
enigma2-plugin-drivers-network-usb-rt8723bs \
enigma2-plugin-drivers-network-usb-mt7601u \
enigma2-plugin-drivers-network-usb-mt7610u \
enigma2-plugin-drivers-network-usb-rtl8192eu \
enigma2-plugin-drivers-network-usb-ax88179-178a \
enigma2-plugin-drivers-network-usb-rt73 \
enigma2-plugin-drivers-network-usb-rt3070 \
enigma2-plugin-drivers-network-usb-rt3573 \
enigma2-plugin-drivers-network-usb-rt5572 \
enigma2-plugin-drivers-network-usb-r8712u \
enigma2-plugin-drivers-network-usb-rtl8192cu \
enigma2-plugin-drivers-network-usb-rtl8192cu-rev2 \
enigma2-plugin-drivers-network-usb-rtl8192ce \
enigma2-plugin-drivers-network-usb-r8188eu \
+ some subvariants as some drivers cover more models.
But, alas, there **could** be some problems:
- Vendor ID/Product ID might not be supported
- Without a dedicated antenna on the stick, in a more demanding layouts, send/receive might be poor
- Older sticks/chipsets might put unhappy strain to your power supply and shorten it's lifespan
- Overheating and resulting dropouts could happen, especially in 24/7 workload
In short, if you do need a reliable network link, it might be better to try an old router that can work in AP mode, 2nd hand AP/Bridge (the terms are sometimes very strange and do not map 1:1 between manufacturers), check whether PowerLine pair can meet $$/make sense ratio (and no disturbance from bad house/flat installations), or still the best, try to use good old plain wire.
In a low bandwidth, low/short usage, some luck, USB wifi stick could be ok:)