shippy hat geschrieben:Hi All,
Newbie here ...
I was wondering looking at all these great custom builds like openATV or openViX:
1. These builds are all 60-100+ MB.
2. Is there a way to use such builds or reduce the size thereof, on low RAM/flash DVB cheap boxes, by configuring a USB stick as boot device?
3. Above likely means that either the existing bootloader will allow such USB boot, or a bootloader need be flashed first into the generic DVB box?
4. How about configuring such a USB stick with extended RAM and data partitions besides the boot partition?
5. How slow would USB operation be vs the internal memory one, really?
Any guidelines and tutorials are welcome !
I have been searching online but all the configuration scenarios start with flashing OpenATV or openViX to the internal memory (after perhaps updated bootloader flash) via USB and then proceeding to Open Multiboot or plugins or custom updates.
The only current receiver that (as far as I am aware of) has issues with flash memory is the H9 - and if Kodi is the issue usually the images allocate a swap on many of the Emmc receivers.
With the H9, it is really easy to move the root to an SD card as large as you like (OpenViX has built in function to do this), and with the H9 runs anything very well - no need for OpenMultiboot. ....... and Yes it is possible to move the root to a usb, but don‘t see the need when you can use the SD card slot.
In particular, most OE-A image builds (especially OpenATV) use techniques built into the OE-A to configure less such as languages for receivers with small flash Or older receivers - and on the others you can always remove elements such as languages except the one in use.
Gigablue Quad 4K plus Giga UE4k Tuner A (FBC -> Unicable gt-sat lnb 28.2E 4 tuners), Tuner B (FBC -> Gigablue unicable lnb 19.2 4 tuners)
Dreambox dm900
Vu+ Uno4kse
Octagon SF8008
Edision Osmio plus 4K
Zgemma H9, H92S, H9Combo
Multibox