Re: Missing virtio modules for sparc64
On 17 Mar 2017, at 11:36, Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> wrote:
> On 17/03/17 11:33, John Paul Adrian Glaubitz wrote:
>
>> On 03/17/2017 12:22 PM, Mark Cave-Ayland wrote:
>>> There is one issue I've found in that the debian-installer fails to
>>> detect the installation CDROM hardware automatically.
>>>
>>> I was able to workaround this by selecting the option to load an
>>> external driver, let that fail, then manually enter the /dev/vda device
>>> which allowed installation to continue but something is preventing the
>>> virtio-blk device being seen as a CDROM.
>>
>> It's most likely the same issue as the one we have with the vdisk block
>> devices when installing inside a SPARC LDOM [1].
>>
>> Can you post the output of "udevadm info -q env -p /sys/block/vda" if
>> /dev/vda is the virtual block device for your CD-ROM drive? If it
>> doesn't include any indication of a CD device, you know why d-i doesn't
>> detect the CD drive.
>
> Yep, here she is:
>
> ~ # udevadm info -q env -p /sys/block/vda
> DEVLINKS=/dev/disk/by-path/platform-ffe2d650-pci-0000:00:06.0
> /dev/disk/by-label/Debian\x209.0\x20sparc64\x201
> /dev/disk/by-uuid/2017-03-16-23-13-57-00
> DEVNAME=/dev/vda
> DEVPATH=/devices/root/ffe2d650/pci0000:00/0000:00:06.0/virtio0/block/vda
> DEVTYPE=disk
> ID_FS_LABEL=Debian_9.0_sparc64_1
> ID_FS_LABEL_ENC=Debian\x209.0\x20sparc64\x201
> ID_FS_TYPE=iso9660
> ID_FS_USAGE=filesystem
> ID_FS_UUID=2017-03-16-23-13-57-00
> ID_FS_UUID_ENC=2017-03-16-23-13-57-00
> ID_PART_TABLE_TYPE=sun
> ID_PATH=platform-ffe2d650-pci-0000:00:06.0
> ID_PATH_TAG=platform-ffe2d650-pci-0000_00_06_0
> MAJOR=254
> MINOR=0
> SUBSYSTEM=block
> USEC_INITIALIZED=4920671
> ~ #
>
> Presumably the DEVTYPE=disk gives away that the device isn't correctly
> being detected as a CDROM?
Nah, it would still be a disk, but you would have:
> ID_CDROM=1
What does `/lib/udev/cdrom_id /dev/vda` say?
James
Reply to: