Beiträge von noggie

  • Second stage loader

    Zitat

    Originally posted by tmbinc
    We'll commit soon again, sorry for the delay. We have to sort out some things, and we didn't wanted to make things more complicated than they needed to.


    I think this must qualify as one the longest "soon"s in history. One year and counting...


    Or did I miss the announcement on where to get them from?

  • TV Bild flackert

    Zitat

    Originally posted by Olove
    Es tritt nur bei den Röhren-Panasonics auf. Und auch nicht bei allen, sondern nur bei den TX32PDxx.


    Und mit der Wärme des Netztteils hat DIESER Fehler auch nichts zu tun.


    Olove

    Sorry, should have stated that my answer was to BriBis. There are probably multiple problems that have similar symptoms.


    My TV was also a Sony, by the way, and the power supply problem started with flickering, continued with drop-outs, and ended in complete failure to show a picture.

  • compile public projects as dm7025 plugins

    A quick-and-very-very-dirty method is to just edit the kernel config file (in build/tmp/work/linux-dm7025-2.6.12.6-r6/linux-2.6.12.6/.config), set the options you want, and then re-run the most recent build script (in ../temp/run.do_compile.xxxx).


    A slightly cleaner method (but still pretty dirty) is to edit the kernel config file, and delete some stamps in tmp/stamps/linux-dm7025-2.6.6-r6.do_xxx. Leave the fetch/patch stamps alone, otherwise the changes you made will be overwritten. Then do a new build of dreambox-image. Your changes will stay around until the kernel is next changed by DMM...

  • compile public projects as dm7025 plugins

    a) You don't really have to include them in the image. Just make the ipks and install them on the machine (ipkg install). No need to re-install the entire operating system... And you can de-install them also, if needed (ipkg remove)
    b) The same environment you used to make the image can also be used to create a huge number of extra packages. See package descriptions in your "openembedded/packages" catalog. Build a package (from your build directory!) using "bitbake <package>". Your compiled packages will be stored in the "tmp/deploy/ipk" directory.

  • Experimental: NFI2CF

    Please take the following with a pinch of salt. I don't own a 7020, and the current sources for the bootloader is not public. In other words: I'm guessing...


    As far as I know, there has been certain improvements in the bootloader from the lastest 7020 version to the current 7025 version. One of the improvements concerns the possibility to transfer parameters to the linux kernel that you want to boot. This is possible to do in the 7025 version, but probably not in the 7020 version. When you boot a standard kernel from the CF on a 7020, the kernel will be loaded from the CF, but the hard-wired root file system will still be flash. (On the 7025, you can use a kernel parameter to intruct the linux kernel to use a partition on CF or HDD as the root file system).


    To get around this problem on the 7020, you would need to patch the kernel, to change the hard-wired root file system. More guessing: you can probably do this using a binary editor on a kernel, find the "root=" string, and patch the path to the root file system. Or you could change the kernel configuration and make your own kernel...

  • Routingeintrag dauerhaft speichern

    Zitat

    Originally posted by ralfK
    Kann es beim shutdown probleme geben (längere shutdown Zeit?), wenn ich kein script in /etc/network/if-down.d ablege?


    Don't think so. There might be minor security considerations, but I can't think of anything serious.

    Zitat


    noggie
    ist es ok, wenn ich in deutsch antworte?


    Sure. I understand a little German, but unfortunately it takes me forever when I try to write it myself...

  • Routingeintrag dauerhaft speichern

    I think it should be possible to just add the script that contains the extra commands to the /etc/network/if-up.d directory. Then you could also remove the static route when the interface is brought down again by adding the appropriate script to /etc/network/if-down.d.


    Look at the samba scripts for an example.

  • Error bei rootfs....

    I briefly checked the source of mkfs.jffs2 to see where this error message was produced. Only place I could see was after a call to "scandir". The manual page for scandir suggests that it returns an error if it runs out of memory.


    So maybe you should check to see if you have enough swap enabled on the build machine?

  • gettext für DM 7025 ?

    Sometimes I'm too stubborn for my own good... But I got it to work at the end. Since I have absolutely no prior experience with gettext and friends, there might well be better and simpler ways of making it work.


    First I tested it on my SUSE linux box. I got it to work by changing "LANGUAGE" to "LANG", and "de" to "de_DE".


    To repeat this on the 7025, I also had to install the following packages. Some of them are probably not needed, but I got a little bit frustrated in dependancy-hell and installed all "glibc-localedata-translit-*" packages at one stage.


    And all that just to see

    Code
    root@db7025:~/hello# ./hello.sh
Hallo Welt!
Dieses Programm läuft mit der Prozess-Nummer 1971.

    when the English version was more understandable to me :smiling_face:

  • error compiling 7025

    Hmmm. It works OK at my end. The only thing I can think of that could make a difference, is that I have for a while now been using a slighly more recent version of bitbake. Maybe that actually matters now? Here's the summary of my last build:

    How does that compare to what you get?

  • error compiling 7025

    The error message doesn't make sense, at least not to me. Throwing some pebbles...


    - Could you please confirm if the /home/dm/tuxbox-dev/dm7025/build/tmp/deploy/ipk/Packages exists or not?
    - Anything changed with your python installation lateley?
    - Any chance that the ipkg-build-index command that is used is *not* the one you have in your tmp/staging/i686-linux/bin/ directory?
    - Enough disk space?

  • Are there OE problems at the moment?

    Even though there have been lots of commits by tmbinc lateley, I seem to be stuck at version 5e1272e749d8d72cb03ed0a96616b384591a8572 for the org.openembedded.dreambox branch. Anybody else having this problem?


    P.S. The org.openembedded.dev branch works OK, with several updates every day...