>>Any chance ROM is mapped somewhere else in your case?
I need to check, this may be a case.
On Fri, Mar 17, 2017 at 7:16 PM, Andrei Borzenkov
wrote:
> On Fri, Mar 17, 2017 at 4:24 PM, Gailu Singh wrote:
> > @Vladimir
> > I do not have serial console (board has memory mapped uart not support in
On Fri, Mar 17, 2017 at 4:24 PM, Gailu Singh wrote:
> @Vladimir
> I do not have serial console (board has memory mapped uart not support in
> grub) to capture memory details. Also on graphics console I can not give
> commands from usb keyboard to dump memory because USB port on board are 3.0
> an
@Vladimir
I do not have serial console (board has memory mapped uart not support in
grub) to capture memory details. Also on graphics console I can not give
commands from usb keyboard to dump memory because USB port on board are
3.0 and USB 3.0 is not supported in Grub. Any other thing I could try
On Thu, Mar 16, 2017, 22:30 Gailu Singh wrote:
> Please find coreboot image attached. Zipped it to reduce size
>
This image is actually fine and is read correctly by fstest. Apparently for
some reason reading image at the end of 4GiB doesn't work. Can you try
dumping last 8M before 4G mark from /
On Fri, Mar 17, 2017, 00:01 Andrei Borzenkov wrote:
> On Fri, Mar 17, 2017 at 9:19 AM, Gailu Singh wrote:
> >>>What address it prints?
> >
> > I followed suggested steps and I see following print
> >
> > fs/cbfs.c:347: head=0x
> >
>
> Then you need to contact coreboot developers and disc
On Fri, Mar 17, 2017 at 9:19 AM, Gailu Singh wrote:
>>>What address it prints?
>
> I followed suggested steps and I see following print
>
> fs/cbfs.c:347: head=0x
>
Then you need to contact coreboot developers and discuss it. GRUB
looks at predefined location at address of cbfs. If this l
