[gutemine] Flodder - ein Boottool zum Knutschen

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • OK, jetzt lösche mal den Ordner flodder in /media/hdd

      entweder über FTP (DCC E2 etc.) oder über das Terminal - aber bei dem Befehl aufpassen, wenn du nicht sicher bist, besser über FTP

      cd /media/hdd
      rm -rf flodder


      Dann stecke den Stick an die Box (sollte /dev/sdb sein), und mounte ihn manuell

      mkdir /tmp/usb
      mount /dev/sdb1 /tmp/usb


      und dann erstelle den Ordner flodder am Stick und reboote die box

      mkdir /tmp/usb/flodder
      reboot
    • Der Stick ist scheinbar nicht in ext3 Formatiert, also erstmal wie in post 1 beschrieben in ext3 formatieren

      sonst poste mal die Ausgabe von

      fdisk -lu /dev/sd?
      blkid|grep /dev/sd

      aber verwende putty.exe - dann kannst du einfach mit der Maus den gewüschten Teil markieren = gleichzeitig kopiert dann einfach hier als CODE (</> in der Menüleiste) mit Strg+C hier als Text einfügen, das erspart die screenshots ...
    • New

      Source Code

      1. root@dm800:~# mkfs.ext3 -N 30000 /dev/sdb1
      2. mke2fs 1.42.1 (17-Feb-2012)
      3. Filesystem label=
      4. OS type: Linux
      5. Block size=4096 (log=2)
      6. Fragment size=4096 (log=2)
      7. Stride=0 blocks, Stripe width=0 blocks
      8. 30240 inodes, 2041848 blocks
      9. 102092 blocks (5.00%) reserved for the super user
      10. First data block=0
      11. Maximum filesystem blocks=2092957696
      12. 63 block groups
      13. 32768 blocks per group, 32768 fragments per group
      14. 480 inodes per group
      15. Superblock backups stored on blocks:
      16. 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
      17. Allocating group tables: done
      18. Writing inode tables: done
      19. Creating journal (32768 blocks): done
      20. Writing superblocks and filesystem accounting information: done
      Display All

      Source Code

      1. root@dm800:~# opkg update
      2. Downloading http://feed.newnigma2.to/weekly/oe2.0/mips32el-nf/Packages.gz.
      3. Inflating http://feed.newnigma2.to/weekly/oe2.0/mips32el-nf/Packages.gz.
      4. Updated list of available packages in /var/tmp/mips.
      5. Downloading http://feed.newnigma2.to/weekly/oe2.0/dm800/Packages.gz.
      6. Inflating http://feed.newnigma2.to/weekly/oe2.0/dm800/Packages.gz.
      7. Updated list of available packages in /var/tmp/nn2.
      8. Downloading http://feed.newnigma2.to/weekly/oe2.0/emu/Packages.gz.
      9. Inflating http://feed.newnigma2.to/weekly/oe2.0/emu/Packages.gz.
      10. Updated list of available packages in /var/tmp/softcammipsel.
      11. root@dm800:~#
      Display All

      Source Code

      1. dm800 login: root
      2. root@dm800:~# df -h
      3. Filesystem Size Used Available Use% Mounted on
      4. /dev/root 60.0M 51.7M 8.3M 86% /
      5. none 71.0M 1.1M 69.9M 2% /var/volatile
      6. none 71.0M 68.0K 70.9M 0% /dev
      7. none 71.0M 0 71.0M 0% /dev/shm
      8. /dev/mtdblock2 3.8M 2.2M 1.6M 57% /boot
      9. /dev/disk/by-uuid/807232e3-b7a3-4918-b2d1-78c23a46eec4
      10. 298.0G 295.0G 2.9G 99% /media/hdd
      11. root@dm800:~# mkfs.ext3 -N 30000 /dev/sdb1
      12. mke2fs 1.42.1 (17-Feb-2012)
      13. Filesystem label=
      14. OS type: Linux
      15. Block size=4096 (log=2)
      16. Fragment size=4096 (log=2)
      17. Stride=0 blocks, Stripe width=0 blocks
      18. 30240 inodes, 2041848 blocks
      19. 102092 blocks (5.00%) reserved for the super user
      20. First data block=0
      21. Maximum filesystem blocks=2092957696
      22. 63 block groups
      23. 32768 blocks per group, 32768 fragments per group
      24. 480 inodes per group
      25. Superblock backups stored on blocks:
      26. 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
      27. Allocating group tables: done
      28. Writing inode tables: done
      29. Creating journal (32768 blocks): done
      30. Writing superblocks and filesystem accounting information: done
      31. root@dm800:~#
      32. root@dm800:~#
      33. root@dm800:~# opkg update
      34. Downloading http://feed.newnigma2.to/weekly/oe2.0/mips32el-nf/Packages.gz.
      35. Inflating http://feed.newnigma2.to/weekly/oe2.0/mips32el-nf/Packages.gz.
      36. Updated list of available packages in /var/tmp/mips.
      37. Downloading http://feed.newnigma2.to/weekly/oe2.0/dm800/Packages.gz.
      38. Inflating http://feed.newnigma2.to/weekly/oe2.0/dm800/Packages.gz.
      39. Updated list of available packages in /var/tmp/nn2.
      40. Downloading http://feed.newnigma2.to/weekly/oe2.0/emu/Packages.gz.
      41. Inflating http://feed.newnigma2.to/weekly/oe2.0/emu/Packages.gz.
      42. Updated list of available packages in /var/tmp/softcammipsel.
      43. root@dm800:~#
      44. root@dm800:~# opkg install /tmp/*ipk
      45. Unknown package '/tmp/*ipk'.
      46. Collected errors:
      47. * opkg_install_cmd: Cannot install package /tmp/*ipk.
      48. root@dm800:~# opkg install /tmp/*.ipk
      49. Collected errors:
      50. * wfopen: /tmp/*.ipk: No such file or directory.
      51. * pkg_init_from_file: Failed to extract control file from /tmp/*.ipk.
      52. root@dm800:~# opkg install/tmp/*.ipk
      53. opkg: unknown sub-command install/tmp/*.ipk
      54. usage: opkg [options...] sub-command [arguments...]
      55. where sub-command is one of:
      56. Package Manipulation:
      57. update Update list of available packages
      58. upgrade Upgrade installed packages
      59. install <pkgs> Install package(s)
      60. configure <pkgs> Configure unpacked package(s)
      61. remove <pkgs|regexp> Remove package(s)
      62. flag <flag> <pkgs> Flag package(s)
      63. <flag>=hold|noprune|user|ok|installed|unpacked (one per invocation)
      64. Informational Commands:
      65. list List available packages
      66. list-installed List installed packages
      67. list-upgradable List installed and upgradable packages
      68. list-changed-conffiles List user modified configuration files
      69. files <pkg> List files belonging to <pkg>
      70. search <file|regexp> List package providing <file>
      71. info [pkg|regexp] Display all info for <pkg>
      72. status [pkg|regexp] Display all status for <pkg>
      73. download <pkg> Download <pkg> to current directory
      74. compare-versions <v1> <op> <v2>
      75. compare versions using <= < > >= = << >>
      76. print-architecture List installable package architectures
      77. depends [-A] [pkgname|pat]+
      78. whatdepends [-A] [pkgname|pat]+
      79. whatdependsrec [-A] [pkgname|pat]+
      80. whatrecommends[-A] [pkgname|pat]+
      81. whatsuggests[-A] [pkgname|pat]+
      82. whatprovides [-A] [pkgname|pat]+
      83. whatconflicts [-A] [pkgname|pat]+
      84. whatreplaces [-A] [pkgname|pat]+
      85. Options:
      86. -A Query all packages not just those installed
      87. -V[<level>] Set verbosity level to <level>.
      88. --verbosity[=<level>] Verbosity levels:
      89. 0 errors only
      90. 1 normal messages (default)
      91. 2 informative messages
      92. 3 debug
      93. 4 debug level 2
      94. -f <conf_file> Use <conf_file> as the opkg configuration file
      95. --conf <conf_file>
      96. --cache <directory> Use a package cache
      97. -d <dest_name> Use <dest_name> as the the root directory for
      98. --dest <dest_name> package installation, removal, upgrading.
      99. <dest_name> should be a defined dest name from
      100. the configuration file, (but can also be a
      101. directory name in a pinch).
      102. -o <dir> Use <dir> as the root directory for
      103. --offline-root <dir> offline installation of packages.
      104. --add-arch <arch>:<prio> Register architecture with given priorit y
      105. --add-dest <name>:<path> Register destination with given path
      106. Force Options:
      107. --force-depends Install/remove despite failed dependencies
      108. --force-maintainer Overwrite preexisting config files
      109. --force-reinstall Reinstall package(s)
      110. --force-overwrite Overwrite files from other package(s)
      111. --force-downgrade Allow opkg to downgrade packages
      112. --force-space Disable free space checks
      113. --force-postinstall Run postinstall scripts even in offline mode
      114. --force-remove Remove package even if prerm script fails
      115. --noaction No action -- test only
      116. --download-only No action -- download only
      117. --nodeps Do not follow dependencies
      118. --force-removal-of-dependent-packages
      119. Remove package and all dependencies
      120. --autoremove Remove packages that were installed
      121. automatically to satisfy dependencies
      122. -t Specify tmp-dir.
      123. --tmp-dir Specify tmp-dir.
      124. regexp could be something like 'pkgname*' '*file*' or similar
      125. e.g. opkg info 'libstd*' or opkg search '*libop*' or opkg remove 'libncur*'
      126. root@dm800:~#
      Display All
      Box fährt noch hoch...scheinbar dauert es ja beim ersten mal immer sehr lange. Auslesen konnte ich schon dieses:

      Source Code

      1. root@dm800:~# df -h
      2. Filesystem Size Used Available Use% Mounted on
      3. /dev/root 7.8G 779.1M 6.6G 10% /
      4. /dev/sdb1 7.8G 779.1M 6.6G 10% /flodder/root
      5. /dev/sdb1 7.8G 779.1M 6.6G 10% /
      6. none 71.0M 168.0K 70.8M 0% /var/volatile
      7. none 71.0M 68.0K 70.9M 0% /dev
      8. none 71.0M 0 71.0M 0% /dev/shm
      9. /dev/mtdblock2 3.8M 2.2M 1.6M 57% /boot
      10. /dev/disk/by-uuid/807232e3-b7a3-4918-b2d1-78c23a46eec4
      11. 298.0G 295.0G 2.9G 99% /media/hdd
      Display All

      The post was edited 1 time, last by scp06 ().

    • New

      Ich weiß nicht, ob es hier zum flodder passt, aber die Box läuft sehr schlecht. Alle 2 Minuten geht komplett das Bild von unterschiedlichen Kanälen weg (ARD,ZDF). Das war bei dem vorherigen Image (ATV 4.2) nicht der Fall. Auch mit flodder. Soll ich mal ein neues Thema unter Dream 800HD dazu aufmachen?
    • New

      Nee, das liegt nicht am OE2.0. Das Bild setzt nicht aus wenn die Box und Verkabelung in Ordnung sind.... zumindest nicht beim direkten Empfang von live TV. TS auf internen Datenträger geht auch noch. Richtig eng wirds wenn das Netzwerk ins Spiel kommt, da geht der SoC dann wirklich in die Knie.
    • New

      Tja aber irgendwie klappt das Floddern nicht mehr - evtl. liegt da doch der Fehler. So sieht es im Moment aus-kein flodder mehr zu sehen..

      Source Code

      1. root@dm800:~# df -h
      2. Filesystem Size Used Available Use% Mounted on
      3. /dev/root 60.0M 52.5M 7.5M 88% /
      4. none 71.0M 1.2M 69.8M 2% /var/volatile
      5. none 71.0M 68.0K 70.9M 0% /dev
      6. none 71.0M 0 71.0M 0% /dev/shm
      7. /dev/mtdblock2 3.8M 2.2M 1.6M 57% /boot
      8. /dev/disk/by-uuid/807232e3-b7a3-4918-b2d1-78c23a46eec4
      9. 298.0G 295.0G 2.9G 99% /media/hdd