hemispherical1

PLi uses service references for picon names, as described twords the bottom of the The new PLi® PLicons, realtime network update of PLicons - (global) page. IIRC the image automagically scans folder locations such as /usr/share/enigma2/picon, /media/hdd/picon, /media/cf/picon, etc. & displays any "properly named" picons found in skins that support the feature.


--
hemi

menu / setup / system / customize (expert) / disable backgrund scanning


--
hemi

I don't know about 800se, but running "opkg list" on the 800 shows:

kernel-module-tun - 2.6.18-r6+git3+ac6cc9511a5f70eaa584c63fc5c3de33cae1d0e7.1 - tun kernel module; Universal TUN/TAP device driver

... as an available package for install...

--
hemi

Recently I realized I wasn't the only one that wished the DM800 would save shell command history across logins. I tried updating the busybox config (openembedded/recipes/busybox/busybox-1.18.5/openpli/defconfig), updating the options:

CONFIG_FEATURE_EDITING_HISTORY=100
CONFIG_FEATURE_EDITING_SAVEHISTORY=y

The resulting busybox binary seems to work fine & it didn't grow in size at all. Unless someone thinks it's too much wear & tear writing the history to flash (only reason not to add it I could think of), could this be added to the images?


Thanks,
--
hemi

Ps. I just noticed OE E1 image has it included already...

Luckily OpenPLi is open sourced and you're free to branch off your own images with every feature you could possibly want.

Rather than complain about the people who provide you images for free, perhaps your time would be better spent finding an image that actually suits your wants & needs...


--
hemi

I'd humbly suggest that whomever has access to the Frontpage/News section post "important" news there. When PLi updated DMM SSL to 84 & Sept. drivers for example, or perhaps a warning that some users seem have run into trouble after installing the new SSL. I didn't see any mentions of the latter problem in the English section, I just happened to do a lil browsing with google translate and see some posts in the Dutch sub forum. Just a thought...


Thanx,
--
hemi

I think what you want could simply be added to your skin, in the "reception settings" screen section. The required info could be extracted from the satfinder section of the skin_default.xml:

<screen name="Satfinder" position="center,center" size="520,400" title="Satfinder">
<widget name="introduction" position="0,0" size="0,0" font="Regular;23" />
<ePixmap pixmap="skin_default/icons/dish_scan.png" position="5,25" zPosition="0" size="119,110" transparent="1" alphatest="on" />
<widget source="Frontend" render="Label" position="190,10" zPosition="2" size="260,20" font="Regular;19" halign="center" valign="center" tran
sparent="1">
<convert type="FrontendInfo">SNRdB</convert>
</widget>
<eLabel name="snr" text="SNR:" position="120,35" size="60,22" font="Regular;21" halign="right" transparent="1" />
<widget source="Frontend" render="Progress" position="190,35" size="260,20" pixmap="skin_default/bar_snr.png" borderWidth="2" borderColor="#c
ccccc">
<convert type="FrontendInfo">SNR</convert>
</widget>
<widget source="Frontend" render="Label" position="460,35" size="60,22" font="Regular;21">
<convert type="FrontendInfo">SNR</convert>
</widget>
<eLabel name="ber" text="BER:" position="120,60" size="60,22" font="Regular;21" halign="right" transparent="1" />
<widget source="Frontend" render="Progress" position="190,60" size="260,20" pixmap="skin_default/bar_ber.png" borderWidth="2" borderColor="#c
ccccc">
<convert type="FrontendInfo">BER</convert>
</widget>
<widget source="Frontend" render="Label" position="460,60" size="60,22" font="Regular;21">
<convert type="FrontendInfo">BER</convert>
</widget>
<eLabel name="lock" text="Lock:" position="120,115" size="60,22" font="Regular;21" halign="right" />
<widget source="Frontend" render="Pixmap" pixmap="skin_default/icons/lock_on.png" position="190,110" zPosition="1" size="38,31" alphatest="on
">
<convert type="FrontendInfo">LOCK</convert>
<convert type="ConditionalShowHide" />
</widget>
<widget source="Frontend" render="Pixmap" pixmap="skin_default/icons/lock_off.png" position="190,110" zPosition="1" size="38,31" alphatest="o
n">
<convert type="FrontendInfo">LOCK</convert>
<convert type="ConditionalShowHide">Invert</convert>
</widget>
<ePixmap pixmap="skin_default/div-h.png" position="10,152" zPosition="1" size="500,2" />
<widget name="config" position="10,165" size="500,225" scrollbarMode="showOnDemand" />
</screen>

The example above certainly wouldn't look good using the positioning from the satfinder screen in the tuner config section, but it is a starting point to figure out what needs to be placed, you can decide where. Hint: you'll need correct paths pointing to your png (graphic files), skin_default/bar_ber.png would only be valid if your skin.xml resided in /usr/share/enigma2, which is unlikely...

I don't know if anyone would have any interest in doing this for you, but it would be a good project for you as you are the one that wants the feature... ;)


Good luck,
--
hemi

Ps. Many/most learn these type of things through trial & error. It may take you 30 tries to get it laid out how you like, but you'll probably also learn some other cool things along the way...

There are very few updates of E1 boxes as they work well & see little development anymore, but I believe there are still occasional updates. The build server that creates the images for download, builds new images daily, regardless if there have actually been any changes or not.



--
hemi

E1 images stay in PAL until set to NTSC, E2 images cycle through the different options.

If you can't get into the menus, the logical choice would be to flash with DreamUP, no GUI or TV needed. Might as well use that as, if I explain how to do it with telnet, if anything goes wrong (which is easy enough to do, there are no safeguards) the box will be dead until reflashed w/ dreamup & null modem anyways

It seems strange that you cannot connect to the web interface, yet telnet is up and running?

Telnet Flash 500- CDK:
[list=1]
[*]Copy unzipped image to /tmp, name doesn't really matter as long as you know what it is, I'll use root.cramfs for this example.
[*]In telnet run command: eraseall /dev/mtd/3 (if you mistype here you could kill the box, think jtag not dreamup)
[*]In telnet run command: cp /tmp/root.cramfs /dev/mtd/0
[*]Reboot
[/list]
If anything doesn't complete successfully, Dreamup can probably recover the box unless you managed to corrupt the boot loader, that's basically what Gemini's infamous clone kill images did, requiring soldering, jtag, bootloader image, etc...

Again I'd just suggest using dreamup & being done with it, neat & clean...


--
hemi

Hopefully this one works, it has to be years old if there's been any changes...


--
hemi

Unfortunately, with the recent site move, not all of the old information is available yet, or at least I can't find it. If you're going to compile on Ubuntu, make sure DASH isn't the default shell as it has consistently proven to be a problem. Create a directory where you want to keep your OpenPLi build and cd to that directory & run:

wget http://openpli.svn.s...oe/Makefile-2.1

That "should" download the latest makefile to build the images. By default the makefile is set to compile the ET9000, so you shouldn't have to change it, but you might as well check it to make sure:

MACHINE ?= et9000

Then create the build heiarchy by issuing the command, again from within your desired build directory:

make -f Makefile-2.1

Once that completes run the command:

make -f Makefile-2.1 image

If everything goes well it will automagically download & install the build enviornment then proceed to build the image. That said, it rarely (if ever) goes well. Chances are it will stall out, unable to find various software packages. Track down those packages and copy them & their md5sum files to the software directory & try again. Search the forum when you run into trouble for leads on where to find missing software, create md5sums, etc...

To the best of my recollection that is basically the build process, anyone feel free to correct me if I forgot something..


Good luck,
--
hemi

It is fairly rare for DBs to die unless it was running clonekill images on a clone. 90% of people that have trouble with dreamup cause it themselves, using the wrong cable type (straight serial rather than null-modem), wrong com port, disabled com ports in BIOS, USB to Serial adapters without proper drivers installed, etc...

If nothing seems to work, try another PC & verify cable type. I've probably seen 100 people over the years that swear up and down they are using a null-modem cable only to eventually find out they weren't, they were actually using a normal serial DB9 cable...



Good luck,
--
hemi