English thread for unstable images DM8000/DM800/DM500HD

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

  • English thread for unstable images DM8000/DM800/DM500HD

    If you find bugs in our new unstable images you can report them here. Please dont discuss about bugs.
    Tell us your bugfinds that way:

    example:
    dm800hd
    image from 02.03.2010
    bug found:
    what i excactly did.

    Thanks for your valuable help on improving our images.

    http://feed.newnigma2.to/unstable/images/
  • Original von dreamedge
    dm800hd
    image from 01.03.2010 18:45
    Bug found:
    WD HDD in esata modus prevented box from starting, in USB modus no problem
    New installtion


    pls flash image from 02.03.2010 and test again pls.
  • dm800hd
    image newnigma2-snapshot-dm800-20100302050654.nfi
    bug found: bix fährt nicht ganz hoch, geflasht übers webif, beues botlogo kommt, dann kommt schwarzes bild, und rores diode blinkt.
    vortschritsbalken bleibt ca in der mitte des 2ten o stehen beim booting im lcd
  • Original von madmic
    dm800hd
    image newnigma2-snapshot-dm800-20100302050654.nfi
    bug found: bix fährt nicht ganz hoch, geflasht übers webif, beues botlogo kommt, dann kommt schwarzes bild, und rores diode blinkt.
    vortschritsbalken bleibt ca in der mitte des 2ten o stehen beim booting im lcd


    For Bugs im german pls post HERE

    did you flashed again ?
    Why drink & Drive ?

    When you can smoke & fly 8)

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

  • DB 800 HD problem

    My DB800 HD since version 2.5.2 all future upgrades (including 2.8.4) are not working for me... after flashing my DB is hanging for a second each 5 seconds approximately.. and then black screen comes out.. for a second or two... after a minute picture is freezing.. and I need to restart the DB or change the channel so I can see the video
    Thanks in advance!!!!
  • If you reboot once or twice, the Samsung HDD also is detected! This is a known issue with this kind of Samsung HDD.
    "Remember, if it's psychobilly, it's gotta have some rockabilly in it somwhere. It ain't just punk with a double bass." (P.Paul Fenech)
  • No but if hdd no deteckted and USB mount to media/hdd :(

    I reboot once, twince, third....

    Originally posted by LoUiS
    If you reboot once or twice, the Samsung HDD also is detected! This is a known issue with this kind of Samsung HDD.


    But in stable newnigma work good!

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

  • I use this kind of HDD in my own dmm800 and it works fine after rebooting a few times and the heard the same behavior from other user with the same HDD. So it should be the same at your side. As i explained before, this is a known issue, but not sure if it can be fixed!
    "Remember, if it's psychobilly, it's gotta have some rockabilly in it somwhere. It ain't just punk with a double bass." (P.Paul Fenech)
  • You can't compare stable and unstable, because in unstable another OE and another kernel is used.
    Gruß
    Dumbo

    In einer irrsinnigen Welt vernünftig sein zu wollen, ist schon wieder ein Irrsinn für sich.
  • Originally posted by Dumbo
    You can't compare stable and unstable, because in unstable another OE and another kernel is used.


    I know... but hm... I tested experimental with new kernel and hdd samsung and wite effeckts..
  • Original von qestore
    oki, this is bug in kernel because in experimental hdd isn't detect :(
    Mayby it can be fixed...


    we wait from dmm (broadcom) kernel patch i hope fix this problem
    » time to say goodbye «

    Konfuzius sagt:
    Erst wenn eine Mücke auf deinen Hoden landet wirst du lernen Probleme ohne Gewalt zu lösen.
  • @qestore

    i have also that samsung on esata and newnigma 2.8.3 and noticed that sometimes it hangs on boot, so it must be something more that experimental image bug.
    please check smart info, after one of that hangs my smart tells me:

    Brainfuck-Quellcode

    1. SMART Error Log Version: 1
    2. ATA Error Count: 1
    3. CR = Command Register [HEX]
    4. FR = Features Register [HEX]
    5. SC = Sector Count Register [HEX]
    6. SN = Sector Number Register [HEX]
    7. CL = Cylinder Low Register [HEX]
    8. CH = Cylinder High Register [HEX]
    9. DH = Device/Head Register [HEX]
    10. DC = Device Command Register [HEX]
    11. ER = Error register [HEX]
    12. ST = Status register [HEX]
    13. Powered_Up_Time is measured from power on, and printed as
    14. DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    15. SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    16. Error 1 occurred at disk power-on lifetime: 108 hours (4 days + 12 hours)
    17. When the command that caused the error occurred, the device was in an unknown state.
    18. After command completion occurred, registers were:
    19. ER ST SC SN CL CH DH
    20. -- -- -- -- -- -- --
    21. 04 51 01 01 00 00 00
    22. Commands leading to the command that caused the error were:
    23. CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    24. -- -- -- -- -- -- -- -- ---------------- --------------------
    25. ec 00 01 01 00 00 00 00 00:00:54.687 IDENTIFY DEVICE
    26. 00 00 01 01 00 00 a0 00 00:00:54.062 NOP [Abort queued commands]
    27. ff 00 01 01 00 00 a0 00 00:00:53.937 [VENDOR SPECIFIC]
    28. ff 00 01 01 00 00 a0 00 00:00:44.062 [VENDOR SPECIFIC]
    29. 00 00 01 01 00 00 a0 00 00:00:03.937 NOP [Abort queued commands]
    Alles anzeigen


    also UDMA CRC errors growing after every hang

    Quellcode

    1. 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 356


    strange that when same disk is connected inside box that problem doesn't occur

    (it is probably wrong place to post like mine, but i had to point that it is not strictly connected to new openembedded version)

    Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von blt ()