Angepinnt OE2.0: feed update from stable to weekly

Wo wird dieser gespeichert, wenn ich extern keine Speichermöglichkeit angegeben habe?

/media/hdd

Vermutlich ist der Flash voll. Darüber würde die Ausgabe von df -h Aufschluss bringen.

Ich habe die Box nun mit einem Weekly neu geflasht. Läuft alles prima. Besten Dank.

Danke, hat wunderbar geklappt!

Hi All,

DM800HD with following, after installing board.newnigma2.to/wbb4/index.…ekly-1-0-mips32el-nf-ipk/, and correcting entries manually, as per this thread:

version=1-000-20160618
comment=opendreambox
target=9
creator=newnigma2 Team <team@newnigma2.to>
url=http://www.newnigma2.to
catalog=http://feed.newnigma2.to/weekly/oe2.0

(tried also with feed.newnigma2.to/weekly/oe2.0/ipk/)

result: firmware update does not work; plugins catalogues - empty, although initial notification pops upon reboot, that there is software update available - all attempts end with info, that network access is badly configured, but it's not.

Any help would be much appreciated. Many thanks in advance.

P.S. image-version.ori:

version=0-4.0.18-20160618
comment=opendreambox
target=9
creator=newnigma2 Team <team@newnigma2.to>
url=http://www.newnigma2.to
catalog=http://feed.newnigma2.to/stable/4.0

Why don't you use the automatic update/upgrade from the first post?

Edit: The file you edited is an information file only; changes there are useless.
As described in the thread, the configuration files are in /etc/opkg. But if you follow the instructions in the first post, there is nothing to adjust manually.

I have initially already applied newnigma2-feedupdate2weekly_1.0_mips32el-nf.ipk - nothing has changed (please see my image-version.ori content). Then, I subsequently applied manual corrections as per post #25 - still the same. I presume there must be something with the update paths: feed.newnigma2.to/weekly/oe2.0 links to empy folders, with exception of images. feed.newnigma2.to/weekly/oe2.0/ipk/ seems to be OK (from the perspective of the content of sub-catalogues), but it still does not work. I have checked entries in etc/opkg/ and they follow initial change in etc/image-version.

Did you see my Edit? The information file will not change!!!

Did you everything what is described in the first post:
1. grep stable /etc/opkg/*feed.conf (to get the information out of the config files)
2. reboot the box
3. copy ipk to /tmp
4. opkg install /tmp/newnigma2-feedupdate2weekly* (any error messages?)

5. opkg update && opkg upgrade (any error messages?)

OK, I will chceck and edit again the content of etc/opkg manually, to follow feed.newnigma2.to/weekly/oe2.0/ipk/. I will share the result. Thank you.

All updated via instructions from @AlfredENeumann - but result is the same as installing the latest image manually: no chance to install any additional plugin from remote control. Of course I can do everything by telnet, but it's not convenient. Any ideas, please?

Why dont you just flash the weekly image?

That would definitely be the easiest solution.
If you are not willing to do that, you should at least:
- make sure that you have a valit internet connection (with DNS Server)
. post the complete telnet output of "opkg update && opkg upgrade"

Yes, you were absolutely right - part of my problems was my router firewall, after all. Thanks for the help.

My mistake was one firewall rule inside the router for blocking ICMP traffic in forward chain - once disabled I have almost everything available from remote control level. Almost, because feed for picons is just empty. Are picons supported in your OE2.0 image for DM800HD? From where can I download them and install manually?

Many thanks in advance for great support!

EDIT_1: I have tried picon loader (included in the feed of Newnigma2 for 800HD); I have tried picon manager for OE2.0 (not included in the feed), and both do not work. I have tried copying latest picons from my DM8000ssst (still running perfect dreamboxupdate.com image compilation from 2013, upgraded to latest E2.0 from 2016-06-16, with updated Gemini plugin) to /picons/piconHD - every third channel showed the picon correctly with ValiHD-extended skin in my DM800HD. After reboot, box went into reboot-loop, resolved with deleting /picons/piconHD folder via ftp. I have tried both options in expert settings as picon location: "flash" (I guess this means /usr/share/enigma2/picons, but again - e.g. Gemini plugin creates its own subfolders there) or "/picons" created in root - no luck. Any ideas please?

EDIT_2: Of course I use flash expander on poor DM800HD.

I hope I am not littering this thread, as my original question was on lack of picon feed in current Newnigma2 update channel for the oldest DM800HD.

Hallo Zusammen,

wollte seit Langem mal wieder meine DM800 updaten. Habe jetzt die obige Mehode versucht. Bekomme immer die Ausgabe 'architecture incompatible'

Mein Image ist wohl ein wenig älter (hüstl)

catalog=http://feed.newnigma2.to/stable/3.1.6

/etc/opkg/official-feed.conf:src/gz official feed.newnigma2.to/stable/dm
00/3.1
/etc/opkg/softcammipsel-feed.conf:src/gz softcammipsel feed.newnigma2.to
stable/emu

Kann mir mal jmd. helfen, wie ich was Neues auf die Kiste bekomme?


Vielen Dank vorab!

Du kannst nicht von einem OE1.6 Image auf OE2.0 updaten. Du musst dazu neu flashen.

- aktuellen SSL flashen
- Image flashen


Sollte das Flashen des SSLs mit einem aktuellen Browser nicht funktionieren, dann einen alten Firefox portable verwenden.

Nicht nur das Image, vor allem die Box (hüstl) ....
Eine 900 gibt es für unter 300€ .....

Hab ich per Browser versucht. Bekomme aber immer den Fehler 'invalid image (or old version)'.

goliath schrieb:

Nicht nur das Image, vor allem die Box (hüstl) ....
Eine 900 gibt es für unter 300€ .....

Naja, die alte tuts ja noch...