steph6
January 11th, 2016, 09:45 AM
Hi everybody, glad to join the community.
I got an HP proliant G4 350 ML. I've installed last ubuntu desktop TLS release, the 14.04.3 from a live usb.
Installation is OK, but when I restart the server, I got the message error: file '/grub/i386-pc/normal.mod' not found
So I've done some searches on the net and I've decided to use boot-repair.
But when I start the server on boot-repair usb, I got a terminal menu asking for starting boot-repair or boot-repair (fail safe). No matter of which option I choose, my screen start flashing. It displays the boot-repair screen (with somebody jumping) but :
- it's allmost green
- there is too a blank square in the center of the screen, I supposed that it's the boot-repair GUI box
- it display during only about 1 second
and then the screen turn again black about 1 second and it displays again the green picture about 1 second, and it still go round as this severals minutes before staying definitely black
I don't have founded any information about this kind of bug. Does somebody got an idea ? Thanks a lot for your help.
I got an HP proliant G4 350 ML. I've installed last ubuntu desktop TLS release, the 14.04.3 from a live usb.
Installation is OK, but when I restart the server, I got the message error: file '/grub/i386-pc/normal.mod' not found
So I've done some searches on the net and I've decided to use boot-repair.
But when I start the server on boot-repair usb, I got a terminal menu asking for starting boot-repair or boot-repair (fail safe). No matter of which option I choose, my screen start flashing. It displays the boot-repair screen (with somebody jumping) but :
- it's allmost green
- there is too a blank square in the center of the screen, I supposed that it's the boot-repair GUI box
- it display during only about 1 second
and then the screen turn again black about 1 second and it displays again the green picture about 1 second, and it still go round as this severals minutes before staying definitely black
I don't have founded any information about this kind of bug. Does somebody got an idea ? Thanks a lot for your help.