NeumoTeam 2.9a Image für 200s, 400s

Anzeige

NeumoTeam 2.9a Image für 200s, 400s

200s image needs some further testing, will be released soon.

Many thanks to deeptho, who has been working almost his entire summer
vacation on this image!

Download at the NeumoTeam fileserver:
http://files.myopera.com/NeumoTeam/files/download.html


New features
*network update via http. In the network update menu, choose "add server".
Add the server as usual. You will have to enter something (e.g. the letter "r")
for the username and password even if the website does not require one.
After adding the server, you can use "modifify server" to change the protocol
to http. You can also edit /var/update_server_list, which has a new format.
*menu-X runs /var/script/menuX.sh
*improved layout of epg-display.
*new standby-mode "DGS original"
*wider channel list to allow more room for program titles and icons; improved
icon layout: icons are placed as far right as possible instead of being
aligned in columns.
*internet epg icon in channel: icon looks like two computers with or without
a red cross. The first variant means "internet epg is available on this
channel and has been activated by user". The second variant means "internet
epg is available on this channel but has not been activated by user".
Press the "check" button on the remote (the one that looks like a "v" and
is below the left arrow button) to toggle the status. Icons appear only
after you install internet epg software
*auto start time can now be set in "Neumo team options" (used to be fixed
at 03:00 hours)
*ext3 support: ext3 is a journaled filesystem. After an unclean shutdown,
it detects and corrects any meta-data corruption on your hard disk in a very
short time. This way a time-consuming full file system check is avoided,
and you will no longer have to wait 15 minutes before relook reboots after
a panic. Note that even with the ext3 file system a corruption can occur, for
instance if your hard disk is dying. To detect such cases, once in a while
(by default: every 20 mounts, every 20th time you activate the relook) a full
filesystem check will be run even if it is not needed.
ext3 support is NOT automatically activated. For each filesystem you have to
decide whether or not to activate it. The filesystem that needs it most is
/var/media. Make sure it is unmounted and then run the following command
tune2fs -O has_journal /dev/ide/host0/bus0/target0/lun0/part4
Use
tune2fs -i 4w -c 100 /dev/ide/host0/bus0/target0/lun0/part4
to schedule a full fsck every 4 weeks or every 100 mounts (whichever comes
first) instead of after the default number of days and mounts
Once you have activated ext3, you can deactivate it using the command
tune2fs -O ^has_journal /dev/ide/host0/bus0/target0/lun0/part4
You can even move your hard disk to a system that does not support ext3
BUT ONLY if all ext3 partitions are CLEANLY unmounted first.

*sqlite3 command line client now has command line recall. Press up arrow
to view and edit the last type command. Backspace and delete work.
*passwd command: use "passwd relook" to alter the password
*syslogd, klogd: use "syslogd -O /tmp/syslog; klogd" to log console
messages to /tmp/syslogd
*strace: use "strace -f -o /tmp/log command" to find out what command is doing
*ntpclient: use "ntpclient -s -h $NTPHOST" to set system time from
ntpserver $NTPHOST. You can also synchronize continuously with ntp server
but that does not seem to work (ntpclient -l -h $NTPHOST&).
*adjtimex: use adjtimex -t $TICKS -f $FREQ to slow down or speed up your
system clock if it is running ahead or behind. Needs to be run on each boot
*additional options for "find": -exec and -print0
*less: "less" is a better version of "more"
*dropbear ssh server and client: only works after you have created some keys.
Run the following commands to create the keys:
cd /etc/dropbear
dropbearkey -t dss -f dropbear_dss_host_key
dropbearkey -t rsa -f dropbear_rsa_host_key
*sftp-server: this allows you to connect to relook using sftp.
*tar: tar now has the -T option
*ldd, strace, fuser (useful for debugging)
*/etc/fstab to facilitate mounting. Could this not be used instead of
the mountmanager config file? We could move fstab to /var/etc and then
link to it.

Other changes
*New database schema (1.15.1). Database is automatically upgraded
from 1.15 (and perhaps earlier versions).
*improved /bin/init: works without changes on hard disk and nfs installation;
handles ext3; simplified code.
Support for internet epg: shutdown is delayed if internet epg is running.
RF-part of relook is shutdown. Shutdown continues after internet software
finishes, when the user presses the powerbutton once more, or when
a scheduled recording is going to start.
*busybox has been upgraded to 1.2.1
*telnet has been removed: you can still telnet TO relook but not FROM
(does anyone use telnet FROM relook?)
*upgraded sqlite3 to version 3.3.6.
*added "universal tun/tap" support as a module to the kernel.
This can be used in openvpn. Added sound support to the kernel
(simplifies using sandali's dvb api support)

Solved bugs
*improved robustness against erroneous NULL values in database.
*channel epg now displays the channel being watched, not some other
channel
*rev 529: log.smb and log.nmb now stored in /tmp/ instead of in flash
*rev 346: if current channel has no epg, info banner showed program from
last channel.
*fixed DiSEqC 1.1
*fixed subtitle bug
*crash in channel epg when database is locked
*crash when pressing epgbutton twice
*long program names extend over icons in the live banner.

Known (unsolved) bugs
*many transponders are missing in newly created db.dat files. This
is a bug from official 2.9a. You will only be affected if you erase
your db.dat and then recreate it. You can add missing transponders
using a manual scan.
*some part of the epg gathering code makes relook crash. The problem
happened continuously during some weeks, but is now gone. The most
likely explanation is that the bug is still there but that it only
causes problems when certain epg-data is transmitted and that currently
no such data is transmitted.
*geckow web interface only works partly. The reason is that the sqlite3
file format has changed. Geckow should be relinked to support both old
and new format.
*if your channels are ordered non-consecutively then a satellite scan
will use existing channel numbers for the newly found channels. The new
channel cannot be reached by pressing the channel number.
*daylight savings time: relook does not switch automatically to and
from dst. In the user interface, timezone CET should be added. The option
for dst should be removed (or at least disabled for CET) because switching
is automatic.
*channel epg is not updated when new data arrives: press "right" a couple
of times until you reach a channel with no data. Now press "check".
the current channel is activated and epg-data (usually for the next 2
programs) arrives on the transport stream. However, it does not appear
on screen (as it does in the regular epg display). I you zap to another
channel and then back, the data will appear, proving that it is indeed there.
*network update: it should be possible to input a blank username or password.
Now this aborts the process of adding a new server. This is annoying because
for http update usually there is no need for a username and password.
The problem is that the virtual keyboard handles empty input quite
differently from everything else.
*network update: user should be asked to select a protocol (now it is set
to ftp; the user has to press "modify server" later if he wants to change it)
*When watching a program already in progress, the progressbar starts at start
time of the program. It should start at "begin time of watching" so that
users know what he will record with "include time shift".
*when inserting new harddisk
-fdisk produces errors. It seems to work anyway, but the errors
should not appear.
-some partitions should be formatted as ext3 by default instead of ext2 so
that user does not have to activate ext3 manually.
-var/data is not mounted initially. If the user proceeds with channel search
db.dat will be created in /var filesystem instead of in /var/data. At the
next boot /var/data/db.dat will appear to be missing and the user has to
do the channel search again. Also, db.dat is now stored twice in flash:
once in /var/db.dat (backup copy) and once in /var/data/db.dat. The second
copy is useless because /var/data is overmounted with a hard disk partition.
It occupies valuable space on the flash chip.
*various parts of the gui display time based on different underlying code.
In some cases different times (by one hour) can appear in various parts
of the gui. The time reported by the command "date" does not take into
account the current timezone and may be inconsistent with the gui-time.
*some parts of the code user sql insert queries of the following type:
insert into ... values (v1,v2)
This should be replaced with
insert into ... (c1,c2) values (v1,v2)
The second form lists the names of the columns to be inserted and continues
to work when columns are added to the database, whereas the first form fails.
*The code should more gracefully handle NULL values in database tables.
Null values are never entered by relook itself but can occur as the result
of bugs in external software of the pc-editor type. Many parts of the code
crash in this case. The crash can often be avoided by treating NULL as 0.
Zero is also an illegal value in many cases (e.g. as a channel number)
but does not cause a direct crash.
*on off-the-air channels, title of next program is displayed, even if the
next program is hours away.
*sound is out of sync during playback of recording if another program
is simultaneously recorded.
_________
relooker

 

Relook PCEditor 1.2.38

PCEditor 1.2.38: Unterstützung für neue Datenbank Revision 1.16 vom Neumo 2.9a.

• New: Support for Neumo 2.9a (database revision 1.16)
• New: Create empty Neumo database revision 1.16
• New: Remove characters for defining short/long channel names
• Updated: Export/Import for database revision 1.16
• Fixed: When creating a new database, overwriting an existing file did not work

Thanks to JonDoe
_________
relooker

 

AW: NeumoTeam 2.9a Image für 200s, 400s

Ein wehleidiges lechtzen eines 300s Besitzers .....

 

AW: NeumoTeam 2.9a Image für 200s, 400s

Hallo Josef,

Ich kann keine Versprechungen machen, ich denke aber dass die Chance ziemlich groß ist dass es bald (diese Monat?) ein neues DGS Images gibt,
wo auch der 300s zusammen mit der 200s, 400s in integriert ist. (es gibt das bereits ungefähr ein halbes Jahr für der 200s, 400s)

Wenn es so weit ist dann wird es wieder regelmässig neue Images geben für deinen 300s.

MfG
_________
relooker

 

AW: NeumoTeam 2.9a Image für 200s, 400s

Und ich habe nun drei 300s. Es waren vier, aber einen hab ich verkauft. Eigentlich nur noch zwei, denn einer kennt keine Module mehr, der kleine Kerl!
Hab versucht zu reparieren, geht aber auch nach meinen mühseligen Versuchen (bild) trotzdem nicht. Werd wohl doch noch einen 400s holen bald einmal!

 

AW: NeumoTeam 2.9a Image für 200s, 400s

Na klar, mit diese Zange wird's nie gehen!

Was du brauchst ist einen schweren Hammer, und der Freddy Krüger Anzug. Damit kannst du sicherlich deinen 300s wieder am leben bringen!


_________
relooker

 

AW: NeumoTeam 2.9a Image für 200s, 400s

Hallo Relooker!
Hab falsches Bild gesandt. Das war die Bestrafung. Hab ihm einige Elkos zusammengedrückt, weil er keine Module mehr kennt. Die Module werden zwar warm, also Strom hängt noch dran, aber keine Kennung. Sonst geht alles. Hoffe, das wird er sich merken und keine weiteren Schwierigkeiten machen!

Aber ganz im Ernst: Hatte 2 Module drin, das dürften die Receiver nicht derpacken, scheint es. Trotz zusätzlichem Kühler. Ein Kollege hat grad berichtet, Topf 6000 gleiches Problem. Im 2. Modul Viaccess-Karte abgebrutzelt. Denke, die werden einfach zu heiß und sollten zusätzliche Kühlung haben.

 

AW: NeumoTeam 2.9a Image für 200s, 400s

Moin,

wie sind die Erfahrungen mit dem 2.9 a, gibts da Probleme?

Wie sieht das mit dem Telnet und FTP - Zugang aus ? Gibts da neuere Erkenntnisse? ich hatte bisher immer nur Neumo Images drauf, gibts dann auch die Probleme?
Gruß
Siggi

 

AW: NeumoTeam 2.9a Image für 200s, 400s

@meergeist

habe zur Zeit fantacy2.82 und darüber neumo 2.9a kopiert. Komme über Netzwerk in die Box und habe keine Probleme. Möchte mich aber als Normaluser bezeichnen, der keine grossen Ansprüche stellt, ausser:
stabiler Lauf, EPG oK und Aufnahmen fünktionieren und Neumo-Funktionen sind vorhanden. O*R*F und Premiere kommt rein und das alles ohne Pixelprobleme (was will man mehr mit nur ASTRA). Das man nur mit einem Kanal zur gleichen Zeit entschlüsseln kann, damit kann ich leben.

Ich bin rundum zufrieden.
Wenn ich da noch an die Zeiten mit der 300er denke...

Gruss bmuser

 

AW: NeumoTeam 2.9a Image für 200s, 400s

Moin,
trotzdem ich bisher nur Neumo Images drauf hatte komme ich mit dem 2.9a nicht mehr über FTP auf die Box.

Wie kann ich das möglichst einfach wieder hinbekommen?

Gruß Siggi