Menu

#72 Screen goes black after cloning

open
5
2010-05-19
2010-05-17
No

Hi all,

I did a partition to image today, twice, expert options, gzip regular compression, ntfsclone first, copy to ssh server.

I chose default bootmenu option both times.

Once I did without checksum, the other time with ssha1, both times, clonezilla displayed nice progress screen, and after the cloning it turned my screen to the old, ugly 80x25 screenwith only grey cursor topleft, no info shown, couldnt ctrl-alt-f2 .. ctrl-alt-fN.

It wanst halted or blocked, it just didnt show any info.

First time I did ctrl-alt-del, it seemed to read the cd and then when it stopped reading i hit enter and it restarted.

Second time (when I did checksum) I also chose poweroff after cloning, so when the screen went blank I waited, and after awhile the cd was ejected and after I pressed enter, it did poweroff.

So, obviously, the screen goes berserk after cloning part is done, while the system goes on headless.

I was using clonezilla-live-20100506-lucid.iso.

I'm open for testing if needed.

Viktor

Discussion

  • Viktor Ilijasic

    Viktor Ilijasic - 2010-05-17

    Ah, now I see there's a similar bug already reported. My screen doesn't turn off, it just switches to 80x25 text mode and it blinks white cursor.

    It's an Nvidia 8600 graphic card, regular analog monitor connector.

    Do I go write all this in the other bugreport? It seems this is a duplicate report. :|

     
  • Steven Shiau

    Steven Shiau - 2010-05-19

    Thanks for filing this bug report.
    Where is the similar bug report?
    Thanks.

    Steven.

     
  • Steven Shiau

    Steven Shiau - 2010-05-19
    • assigned_to: nobody --> steven_shiau
     
  • Viktor Ilijasic

    Viktor Ilijasic - 2010-05-22

    Actually, it's not about running it for too long. The progress while cloning is displayed all the while, right up until it is done with cloning. After cloning finishes it switches display mode and goes blank. It doesn't blank screen at all while cloning.

    Unfortunately, I cannot retry this error on that same computer, it is not available to me anymore.

    I could try reproducing the bug on another computer, but it seems to me it might be a bug related to some specific hardware. Perhaps only ATI/Nvidia graphic cards?

     

Log in to post a comment.