[SLOF] Loading file from disk image
Thomas Huth
thuth at redhat.com
Wed Jan 3 01:25:34 AEDT 2018
On 02.01.2018 15:17, Jd Lyons wrote:
>
>
>> On Jan 2, 2018, at 8:43 AM, Jd Lyons <lyons_dj at yahoo.com> wrote:
>>
>> Joy!peffpwpc……
>>
>> 14677: [ a5] 0 0 0 2 1 5e77ef40 5e7d1078 4 0
>> 14679: [111] encode-int 0 0 2 1 5e77ef40 5e7d1078 4 5e7d107c 4
>> 1467b: [112] encode+ 0 0 2 1 5e77ef40 5e7d1078 8
>> 1467c: [ 12] b(") 0 0 2 1 5e77ef40 5e7d1078 8 1467e e
>> 1468d: [110] property 0 0 2 1 5e77ef40
>> 1468f: [127] finish-device 0 0 2 1 5e77ef40
>> 14691: [127] finish-device 0 0 2 1 5e77ef40
>> 14693: [de0] xde0 0 0 2 1 5e77ef40
>> 14694: [ 0] end0 0 0 2 1 5e77ef40
>> restored fcode@ 5e77ef40
>> restored fcode-spread 1
>> restored fcode-offset 2
>> restored fcode-end 0
>> restored ip 0
>> ok
>> 0 > dev /pci ls
>> 5e72ad60 : /pci at 800000020000000
>> 5e72d2e8 : |-- ethernet at 0
>> 5e72d9d8 : +-- NVDA,Parent at 1
>> 5e7cfab0 : |--
>>
>
> Seems to be having trouble populating the children,
>
> I should see:
>
>> 5e72d9d8 : +-- NVDA,Parent at 1
>> 5e7cfab0 : |-- NVDA,Display-A
Indeed, sounds like there is something wrong here. Does SLOF hang during
the "ls" or do you get back to the firmware prompt? Could you please
paste the whole log, right from the start of booting the VM?
Not sure, but in case you've manually started the FCODE from the
firmware prompt, maybe you've also got to open the node for "extension"
instead. So instead of doing select-dev or open-dev, could you please
try this instead:
dev /pci/vga
get-node extend-device
Thomas
More information about the SLOF
mailing list