© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Colin, thanks for the pointer to the info that could you help with a work-around. Using grub2 in chained boot mode still had a similar problem, so I've reverted back to legacy grub for now. I've got 4 files attached here for you. The fdisk output, the "good" mbr now with legacy grub installed, and two different "bad" mbr dumps. One produces the "module not found" described in this bug" while the other is a different symptom, probably caused by the same problem. Ignore that one if you wish. Looks like I can only add one attachment per post, so next three files in next posts.
After operating with grub2 in chained mode fro a while, wife booted into windows again and next time, the grub bootloader was just gone, and the system booted straight into windows. No idea what's up with that, but figured I'd attach that capture as well.
Also, if you haven't seen it, there was a thread specifically about HP/Compaq laptops having various bits of software that caused this problem. Given that we have Compaq laptops, it might give you some more info to work with. That thread is here: http://
Thanks for looking in to this.