Yes, I expect this is a lack of support in grub-probe for this device.
Is the source code for your driver available, in which case I can
probably work out the answer to the following questions by myself?
Failing that, I need to know a few things:
* What are the characteristics of your device naming? Ideally I'd like
to have something in the format of Documentation/devices.txt from the
kernel, for example:
"""
8 block SCSI disk devices (0-15)
0 = /dev/sda First SCSI disk whole disk
16 = /dev/sdb Second SCSI disk whole disk
32 = /dev/sdc Third SCSI disk whole disk
...
240 = /dev/sdp Sixteenth SCSI disk whole disk
Partitions are handled in the same way as for IDE
disks (see major number 3) except that the limit on
partitions is 15.
"""
* Can the firmware access your device directly by way of the usual UEFI
block device methods, or is anything special needed?
It would also be helpful if you would be able to test our current
development release. I don't expect it to work right now, so don't
spend time testing just yet as you'll no doubt just run into much the
same bug, but our standard operating procedure is to fix bugs first in
the development release and then backport as necessary, so it would be
good to ensure that you would be able to confirm fixes in our
development release.
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237519
Title:
Grub2 fails to install to non-standard device path
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1237519/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
