Comment 58 for bug 1237519
Revision history for this message
| Brandon Hansen (bhansen-n) wrote Re: [Bug 1237519] Re: Grub2 fails to install to non-standard device path | #58 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Thank you Kent. Unfortunately I was not able to successfully boot after
the grub stage. I am not sure if that is our bug or not, though.
Following is the processed I used, but first I'll mention that I was
unable to use the insmod method of installing our driver during Ubuntu
install in order to have our device recognized. It kept telling me I
had an incorrect module format. I made sure the kernel versions matched
up, but was unsuccessful using this method.
Instead, I used a driver injection disk to have our device recognized
and that worked: the os and grub both installed successfully. Then,
because I don't have an option rom loaded on my card, I loaded our
driver from the uefi shell and invoked grubx64.efi from the shell off of
our device. This brought the grub menu up and I chose to start Ubuntu
Server. I then get few print messages from our device and the OS does
not boot.
The reason I mentioned the insmod method is because I'm not sure if,
even though the driver injection disk files worked, there was still some
sort of conflict that I didn't see. Do you have any thoughts on that?
Is there a different way of testing the fixes you would like me to try?
I apologize I am by no means a Linux expert. Thank you for your time.
Brandon
On 12/10/2013 11:09 AM, Kent Baxley wrote:
> @Brandon,
>
> Thanks for testing that on Precise. I also assume that you were able to
> successfully boot from that point (I think the efi module for the fio
> device has to be loaded by hand)? I just want to confirm so that way I
> won't be testing the same thing twice.
>
> Once the grub2 fixes go out for 14.04 I'll also test it here on my
> server. I just tested 14.04 today not realizing that any fixes have
> gone out for grub2 on Trusty yet. I'll try again as soon as I see the
> status change.
>
> Thanks, again, for testing precise.
>
This e-mail (and any attachments) is confidential and may be privileged. Any unauthorized use, copying, disclosure or dissemination of this communication is prohibited. If you are not the intended recipient, please notify the sender immediately and delete all copies of the message and its attachments.