Jump to content


hemispherical1

Member Since 9 Jan 2007
Offline Last Active 26 Jan 2020 17:11
-----

#493125 How to create swapfile in pli?

Posted by hemispherical1 on 31 May 2015 - 04:48

It's nice for a user to have the option to actually learn something. This terribly "complicated" method would allow a user to create a swapfile on any Linux based box, ranging from $ routers to  $$$$ computers & anything inbetween... No crutches required. ;)

 

--

hemi




#337757 usb stick

Posted by hemispherical1 on 4 March 2013 - 04:49

The easiest way is probably to plug the stick into a Windows machine. If you want to do it on the Dreambox I think you need to install the dosfstools package then run mkfs.vfat /dev/actual-device (/dev/sda, /dev/sda1, /dev/sdb3, etc...) in telnet/ssh...


--
hemi


#325097 dm800 openpli2.1 endless reboot loop

Posted by hemispherical1 on 2 January 2013 - 21:11

I' not an expert, but I think it would be quite unusual for a skin to be causing a complete reboot. Usually it's just Enigma2 respawning continually. When trying to connect over the wired LAN, make sure that dhcp is running on the router, and hopefully DHCP was activated on the box. Scan your network or look into the router webif to see what address the DB picked up. If you didn't have dhcp activated or the ethernet port configured statically, sorry...

--
hemi

Ps. Putting the box into stop mode like you were going to flash should show you the IP the DB is pulling, if it is pulling...

PPs. If the files on the DB are desperately needed (besides learning to make backups), it might be worthwhile to learn how to boot the DB from either USB or the network. That would allow you to start up the DB, mount the flash and remove the problem skin and/or retrieve your files...


#322222 unpack openpli image on linux

Posted by hemispherical1 on 22 December 2012 - 17:13

Look, now you are blaming me of missleading and trying to brick your box,...

Nobody blamed you for anything. I said that "I'd rather have a bricked DB in the closet, useless for anything, rather than possibly provide you with any form of satisfaction.". Let me try to say it another way that you might be able understand...

Hypothetically, if I had the choice of a broken DB, or listening to your condescending attitude to fix it, I would strongly prefer throwing my DB in the trash. No my DB is not broken, nor in the trash, it never was in the trash and I don't believe you tried to damage anything.

--
hemi


#322045 unpack openpli image on linux

Posted by hemispherical1 on 22 December 2012 - 00:49

I didn't follow your "suggested/proper/clever procedure" RedX suggestions for the simple reason that your condescending attitude throughout this thread assured I'd rather have a bricked DB in the closet, useless for anything, rather than possibly provide you with any form of satisfaction.

Some of us are actually able to use what we refer to as... "common sense". Please don't attempt to take the solution as something you actually contributed to. From what I read, you'd still have folks mixing & matching binaries & architectures, rather than solving the problem. I missed the part where you suggested using the root account... But then again, I'm an ass, as stated earlier...

--
hemi


#320981 unpack openpli image on linux

Posted by hemispherical1 on 18 December 2012 - 07:38

Steal the required binaries (buildimage & mkfs.jffs2) & info from build-nfi-image.sh from nfibackup... Then Happysat can write a script to automate it... ;)

Something like:

mkfs.jffs2 --root=/path/to/boot --faketime --output=/path/where/I/want/boot.jffs2 --eraseblock=0x4000 -n -l
mkfs.jffs2 --root=/path/to/root-of-filesystem --faketime --output=/path/where/I/want/root.jffs2 --eraseblock=0x4000 -n -l

buildimage --brcmnand --arch dm800 -e 0x4000 -f 0x4000000 -s 512 -b 0x40000:/path/to/SSL.bin.gz -d 0x3C0000:$/path/to/boot.jffs2 -d 0x3C00000:/path/to/root.jffs2 > NewImage.nfi

--
hemi

Ps. IIRC recent versions of nfidump can extract the SSL also from orig image, making 1 less thing to track down...


#314513 Reconfigure buttons on remote controller

Posted by hemispherical1 on 18 November 2012 - 20:35

I never had a 7000, but I'd guess... Copy /share/tuxbox/enigma/resources/rcdm5xxx.xml (or if one sounds better suited for 7000...) to /var/tuxbox/config/enigma/resources/ & edit there, enigma restarts required for changes to take effect...

--
hemi


#303053 Cutlist Editor + Execute Cuts

Posted by hemispherical1 on 30 September 2012 - 18:40

Something like....

Open the DVR/Recording selector
Select the recording you want to edit
Press menu
Choose cutlist editor
Press OK
ffwd, rewind, etc to the location you want to cut
Press OK again & select what you want to do (remove before that point, start cut there, end cut there, remove after... etc...
When done with your cuts, just exit cutlist editor

With the desired recording still selected (or select again)
Menu
Execute cuts
Choose whether to replace existing file with the edited one, or keep the original copy also
Press OK

--
hemi


#299373 Newer kernel for "make_cdk_image" openpli

Posted by hemispherical1 on 16 September 2012 - 22:30

DMM never released the source for the drivers required to run the DB, that's the main reason why all the boxes were using ancient (6+ year old) kernels up until fairly recently. (If not somebody would've updated the kernels themselves.) Finally DMM updated the kernels on most of the newer boxes, but all the E1 boxes and even the 800 are still tied to ancient kernels.

Unfortunately that means when a needed feature finally appeared in a new kernel, the only real option is to attempt to backport it to the ancient kernels, with varying degrees of success.

--
hemi


#295185 Custom Cam?

Posted by hemispherical1 on 28 August 2012 - 06:47

I believe custom cam is an example/framework, illustrating installation of your own customcam, or allowing you to just rename your "non-pli" cam to customcam and running like that. Attaching the version from dm800 2.1 PLi feed...

--
hemi

Attached Files




#289294 lamedb

Posted by hemispherical1 on 23 July 2012 - 21:03

Transponder & services entries both contain a namespace (to identify sat) & TransponderID (to specify TP). If your example contained a service from the example tp you'd probably have seen it yourself... ;)

--
hemi


#284774 telnet

Posted by hemispherical1 on 25 June 2012 - 00:52

does the file actually exist, /usr/bin/root_to_cf.sh ?
is it executable?

--
hemi


#282892 CF on dm7025

Posted by hemispherical1 on 12 June 2012 - 23:46

http://www.google.co...q=how to telnet

Once you figure out how to telnet into the DB (hint. I believe DCC has a telnet client/tab)... enter the command:

/usr/bin/root_to_cf.sh (and hit the enter key)

--
hemi


#282823 CF on dm7025

Posted by hemispherical1 on 12 June 2012 - 17:46

Did you try running /usr/bin/root_to_cf.sh from telnet to see whether the problem is in the script itself or whatever calls the script?

--
hemi


#282665 install plugin

Posted by hemispherical1 on 11 June 2012 - 21:23

I'm guessing the easiest way would be to install one of PLi's oscam packages, then extract the oscam binary from your tar.gz & overwrite the binary that PLi installed, probably under /usr/bin. If you also need specific config files from your tar.gz, overwrite the ones that PLi installed also.

The best way to actually learn what goes where is probably to download an existing package for your image & extract the files within. From there you can poke around the data.tar.gz file, etc. and see what goes where...

--
hemi