@Colin, So I've been running maverick with the 'fix' (copying the wubildr out of winboot) and made a few changes (not the least of which is moving to Natty). I noticed the "invalid mode" command flashing by since then, but still worked. But then I removed the old maverick kernel, regenerating grub.cfg in the process, and this morning the computer failed to boot again, dropping at the grub prompt.
So long story. Basically I've seen other users on the forums whose maverick has been working and then suddenly: grub prompt. Which points to lupin destroying wubildr, even on 10.10 installs. So I change grub-mkimage in lupin to revert back to the last version (just removed those 3 additional modules), ran 'grub-install /dev/sdaY' and... it works again. So, my point is - it's been 3 weeks since release. There have been many affected users on the forums. Is it possible to just revert the lupin change and prevent this problem from reoccurring? Thanks PS clearly my tests are not comprehensive, if you need some additional testing to confirm this on, say, a fresh 10.10 install, let me know. I just think the change is fairly minor and, it's pretty clear the new lupin is breaking wubildr, so... it makes sense to me ;) -- Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10 https://bugs.launchpad.net/bugs/653134 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
