Vu+ and 2.6.28 Kernel - For kernel Engineers

    Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    • Vu+ and 2.6.28 Kernel - For kernel Engineers

      Hallo,

      Does the developers plan to move from 2.6.18 to the 2.6.28 linux kernel? the .18 kernel is so old that moses used it on his stone-tablets many years ago. Porting drivers from new kernels backwards is quite a troublesome task

      tks
      Harry

    • RE: Vu+ and 2.6.28 Kernel - For kernel Engineers

      you might be correct with Moses slabtop :)
      but doesn't your VU+ work properly?

      when you see the trials regarding the kernel version for other receivers it seems a hell of a lot of work + all open plugins and extensions
      (and they aren't to stable 'one can read in them fora)
      2.6.30.2

      it could be an improvement surely, but only when all dependencies work.
      ciao
      :D keine kohle mehr :D

    • RE: Vu+ and 2.6.28 Kernel - For kernel Engineers

      There are so many nice features in the .28 upwards, but there is minimal effort required to make it boot. Only the drivers need to be recompiled - Nothing on E2 will change. (Latest kernels are bad.. thats why use a kernel that is a few releases old)

      a model-T ford WORKS (2.6.18) ... a Ferrari would work better (2.6.28+)

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von Harry ()

    • RE: Vu+ and 2.6.28 Kernel - For kernel Engineers

      previously i was a dreambox user and on ihad there are many threads regarding upgrading the kernel...
      it seems not as easy as you mentioned
      surely with efford one could upgrade...
      thus I stand corrected regarding "it could be done" <> should it be done

      maybe the developers take your request into account.
      ciao
      :D keine kohle mehr :D

    • If its not broken, dont fix it is a bad excuse for not progressing - do the Vu+ team want to be the LEADER or just a cheap hack of a Dreambox? I really hope its the LEADER. On a kernel level, the 2.6.18 is one of the most broken kernels out there, but there is so much glue and patches keeping it working. The new drivers dont work anymore (XFS, DVB-USB etc etc) due to many header changes in the latest. If its not broken, then why not use a 2.4.x kernel, as they also work. (if .18 wasnt broken, Linux would have stopped just there)

    • i agree with you, thats a strange opinion ;)

      but if you really think VU will take a role as leader, i think you will be disappointed.

      there is also not a single sign to see, that vu duo will get oe 1.6 soon (or ever?)

      so this should be more important at the moment, because the development of enigma will be in oe 1.6 in the future.

      afaik vu has not commited a single line of code to enigma yet

    • Originally posted by sinnlos0815
      i agree with you, thats a strange opinion ;)

      but if you really think VU will take a role as leader, i think you will be disappointed.

      there is also not a single sign to see, that vu duo will get oe 1.6 soon (or ever?)

      so this should be more important at the moment, because the development of enigma will be in oe 1.6 in the future.

      afaik vu has not commited a single line of code to enigma yet


      not a true statement :)
      oe is build system which has nothing with enigma2. when you build image with oe1.5 or oe1.6, you still compiling the same enigma2. this applies to kernel as well as dvb drivers.
      oe16 using slightly changed syntax in bb files, rebuild classes and use a newer bitbake. thats all , its just a compiling and packaging system and you could compile nearly anything with both oe1.5 or or1.6.

    • VU+ images are based on OE1.5 until now. Kernel has been backported form 1.6 to 1.5.
      Pustekuchen ist keine Blume.

      Vu+ DUO - 500GB HDD (Samsung EcoGreen F2) - Vu+ DUO - 500GB HDD (Samsung EcoGreen F3)
      Vu+ SOLO - 500GB HDD (WD Mybook Essential 2,5") - Samsung USB DVD Brenner
      DM800 - Abcom IPBox 910 - Opticum HD TS 9600
      Zotac Mag Mini als Medialplayer - Buffalo Drive Station Pro als NAS

    • TBH, if the OE system died and went to hell, I would not cry :D biggest piece of crap this side of the moon. :D

      that is my opinion of it - Sometimes its easier to create your own Canadian cross compiler system from scratch.

    • Originally posted by Harry
      TBH, if the OE system died and went to hell, I would not cry :D biggest piece of crap this side of the moon. :D

      that is my opinion of it - Sometimes its easier to create your own Canadian cross compiler system from scratch.

      and how you`ll fight with dependencies then ? :) i ha no problem with building dm 7020,7025,500hd,800,8000 and vuduo on same machine.

      btw, you don`t need canadian cross, native cross chain work well..

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von xener ()

    • Originally posted by xener
      Originally posted by Harry
      TBH, if the OE system died and went to hell, I would not cry :D biggest piece of crap this side of the moon. :D

      that is my opinion of it - Sometimes its easier to create your own Canadian cross compiler system from scratch.

      and how you`ll fight with dependencies then ? :) i ha no problem with building dm 7020,7025,500hd,800,8000 and vuduo on same machine.


      There are a couple of things there... the Kernel has very little dependency, the root filesystem packages are the things that need to kept in check - but the OE system makes things NEEDLESSLY complicated for small tasks. I have built many systems from scratch, and not once have I had problems managing dependencies. 'Linux from Scratch' is a good start of reading material.

    • Originally posted by xener
      not a problem if you have a plenty of time to find any dependecies for enigma stuff.
      with oe i have complete vuduo image build in ~170 minutes.


      If you know whats going on here - please could you help me out :( I am totally lost on Fault Finding in OE (Works well when there are no problems... almost impossible to fault find in)


      Quellcode

      1. make -f Makefile-vuplus-4.8 mimage
      2. ....
      3. ....
      4. ....
      5. =======
      6. NOTE: package mbox-image-1.0-r0: task do_rootfs: started
      7. ERROR: function do_rootfs failed
      8. ERROR: see log in /mnt/disk/Embedded/VuPlus4.8/bm750/build/tmp/work/mbox-image-1.0-r0/temp/lo
      9. g.do_rootfs.11325
      10. NOTE: Task failed: /mnt/disk/Embedded/VuPlus4.8/bm750/build/tmp/work/mbox-image-1.0-r0/temp/lo
      11. g.do_rootfs.11325
      12. NOTE: package mbox-image-1.0-r0: task do_rootfs: failed
      13. ERROR: TaskFailed event exception, aborting
      14. NOTE: package mbox-image-1.0: failed
      15. ERROR: Build of mbox-image failed
      16. =======
      17. The Logfile shows
      19. ========
      20. Successfully terminated.
      21. Collected errors:
      22. ERROR: Cannot satisfy the following dependencies for mc:
      23. libglib-2.0-0 (>= 2.20.0)
      24. ERROR: Cannot satisfy the following dependencies for enigma2:
      25. libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0) libglib-2.0-0 (>= 2.20.0)
      26. ================
      Alles anzeigen