It's iKVM4.

On 18-02-25 04:23:45, Timothy Pearson wrote:
Actually that's quite odd -- it should not work that way.  There is a
hardware mux that is switched in when the module is installed; only the
BMC can access the DRAM SPD lines without a BMC GPIO being set.

Which module are you using, the iKVM4 or the iKVM5?

On 02/24/2018 11:10 AM, Piotr Kubaj via coreboot wrote:
Strange, I didn't apply any patches. I run D16 with stock coreboot 4.7
and OpenBMC.

Could it be because I have different memory modules (4xKVR16R11D4/16)?

On 18-02-24 12:00:01, [email protected] wrote:
Send coreboot mailing list submissions to
    [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
    https://mail.coreboot.org/mailman/listinfo/coreboot
or, via email, send a message with subject or body 'help' to
    [email protected]

You can reach the person managing the list at
    [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of coreboot digest..."


Today's Topics:

  1. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  2. Re: OpenBMC & KGPE-D16 (Timothy Pearson)
  3. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  4. Re: OpenBMC & KGPE-D16 (Timothy Pearson)
  5. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  6. make gitconfig not working for me with git 1.9.1
     ([email protected])
  7. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)


----------------------------------------------------------------------

Message: 1
Date: Fri, 23 Feb 2018 23:38:42 +0100
From: Elisenda Cuadros <[email protected]>
To: Timothy Pearson <[email protected]>, Coreboot
    <[email protected]>
Subject: Re: [coreboot] OpenBMC & KGPE-D16
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hello,

Thank you for your reply.

I reflashed (same build) the BMC module with a hotplug. Now it works
like a charm, it got an ip, I can log through ssh, reboot, etc..

But now I have a new problem. If I try to boot from a halted system,
with BMC module attached, the system fires up but Coreboot hangs:

Unable to detect valid memory on any nodes.? Halting!
mct_d: fatalexit

If I remove the BMC module the system boots fine.

I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1
orange slots.

I attach both console logs.

Regards,

- Eli



On 22/02/18 22:36, Timothy Pearson wrote:
Actually, for OpenBMC work, hotplugging is often the only way to go.
Just be very careful to align the pins correctly the first time; you
don't have a second chance if you misalign the pins and fry the
module...

On 02/22/2018 03:22 PM, [email protected] wrote:
On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:

Hi,

Now I trying to use your OpenBMC port.

I followed the instructions and everything was fine (compiling,
reading and flashing). I waited several minutes after flashing, but
the module didn 't blinked like in the vendor rom, nor did it receive
an ip.

I halted the system because I thought maybe it needs a cold start.

After this, the system doesn't boot with the module plugged in. The
fans begin to spin for approximately 1/4 second, but nothing else.

My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
(~1000rpm)

In the case I have to reflash the module, is it possible to hotplug
it?
Hotplugging is dangerous and not supported, don't do it.
Thank you very much for your support.
You can use a test clip to externally flash it via a flashing device
(not sure which can do 16 pins though, I would inquire on the flashrom
mailinglist)

Are you using the latest coreboot? AFAIK coreboot was patched to
support
OpenBMC, so you need a new version with the patches.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Console_Without_BMC.log.gz
Type: application/gzip
Size: 24422 bytes
Desc: not available
URL:
<http://mail.coreboot.org/pipermail/coreboot/attachments/20180223/80d225ea/attachment-0002.bin>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Console_With_BMC.log.gz
Type: application/gzip
Size: 2158 bytes
Desc: not available
URL:
<http://mail.coreboot.org/pipermail/coreboot/attachments/20180223/80d225ea/attachment-0003.bin>


------------------------------

Message: 2
Date: Fri, 23 Feb 2018 17:01:13 -0600
From: Timothy Pearson <[email protected]>
To: Elisenda Cuadros <[email protected]>
Cc: Coreboot <[email protected]>
Subject: Re: [coreboot] OpenBMC & KGPE-D16
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8

To subscribe or unsubscribe via the World Wide Web, visit
    https://mail.coreboot.org/mailman/listinfo/coreboot
or, via email, send a message with subject or body 'help' to
    [email protected]

You can reach the person managing the list at
    [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of coreboot digest..."


Today's Topics:

  1. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  2. Re: OpenBMC & KGPE-D16 (Timothy Pearson)
  3. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  4. Re: OpenBMC & KGPE-D16 (Timothy Pearson)
  5. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  6. make gitconfig not working for me with git 1.9.1
     ([email protected])
  7. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)


----------------------------------------------------------------------

Message: 1
Date: Fri, 23 Feb 2018 23:38:42 +0100
From: Elisenda Cuadros <[email protected]>
To: Timothy Pearson <[email protected]>, Coreboot
    <[email protected]>
Subject: Re: [coreboot] OpenBMC & KGPE-D16
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hello,

Thank you for your reply.

I reflashed (same build) the BMC module with a hotplug. Now it works
like a charm, it got an ip, I can log through ssh, reboot, etc..

But now I have a new problem. If I try to boot from a halted system,
with BMC module attached, the system fires up but Coreboot hangs:

Unable to detect valid memory on any nodes.? Halting!
mct_d: fatalexit

If I remove the BMC module the system boots fine.

I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1
orange slots.

I attach both console logs.

Regards,

Eli



On 22/02/18 22:36, Timothy Pearson wrote:
Actually, for OpenBMC work, hotplugging is often the only way to go.
Just be very careful to align the pins correctly the first time; you
don't have a second chance if you misalign the pins and fry the
module...

On 02/22/2018 03:22 PM, [email protected] wrote:
On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:

Hi,

Now I trying to use your OpenBMC port.

I followed the instructions and everything was fine (compiling,
reading and flashing). I waited several minutes after flashing, but
the module didn 't blinked like in the vendor rom, nor did it receive
an ip.

I halted the system because I thought maybe it needs a cold start.

After this, the system doesn't boot with the module plugged in. The
fans begin to spin for approximately 1/4 second, but nothing else.

My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
(~1000rpm)

In the case I have to reflash the module, is it possible to hotplug
it?
Hotplugging is dangerous and not supported, don't do it.
Thank you very much for your support.
You can use a test clip to externally flash it via a flashing device
(not sure which can do 16 pins though, I would inquire on the flashrom
mailinglist)

Are you using the latest coreboot? AFAIK coreboot was patched to
support
OpenBMC, so you need a new version with the patches.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Console_Without_BMC.log.gz
Type: application/gzip
Size: 24422 bytes
Desc: not available
URL:
<http://mail.coreboot.org/pipermail/coreboot/attachments/20180223/80d225ea/attachment-0002.bin>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Console_With_BMC.log.gz
Type: application/gzip
Size: 2158 bytes
Desc: not available
URL:
<http://mail.coreboot.org/pipermail/coreboot/attachments/20180223/80d225ea/attachment-0003.bin>


------------------------------

Message: 2
Date: Fri, 23 Feb 2018 17:01:13 -0600
From: Timothy Pearson <[email protected]>
To: Elisenda Cuadros <[email protected]>
Cc: Coreboot <[email protected]>
Subject: Re: [coreboot] OpenBMC & KGPE-D16
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

You need these patches:

https://review.coreboot.org/#/c/19822/

This one in particular:

https://review.coreboot.org/#/c/coreboot/+/19820/

This is noted on the Raptor status page:

https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php

See the link to "Initial coreboot patches".

If anyone wants to take over upstreaming of the patches in that list
they are welcome to do so!

On 02/23/2018 04:38 PM, Elisenda Cuadros wrote:
Hello,

Thank you for your reply.

I reflashed (same build) the BMC module with a hotplug. Now it works
like a charm, it got an ip, I can log through ssh, reboot, etc..

But now I have a new problem. If I try to boot from a halted system,
with BMC module attached, the system fires up but Coreboot hangs:

Unable to detect valid memory on any nodes.  Halting!
mct_d: fatalexit

If I remove the BMC module the system boots fine.

I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1 orange
slots.

I attach both console logs.

Regards,

- Eli



On 22/02/18 22:36, Timothy Pearson wrote:
Actually, for OpenBMC work, hotplugging is often the only way to go.
Just be very careful to align the pins correctly the first time; you
don't have a second chance if you misalign the pins and fry the
module...

On 02/22/2018 03:22 PM, [email protected] wrote:
On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:

Hi,

Now I trying to use your OpenBMC port.

I followed the instructions and everything was fine (compiling,
reading and flashing). I waited several minutes after flashing, but
the module didn 't blinked like in the vendor rom, nor did it receive
an ip.

I halted the system because I thought maybe it needs a cold start.

After this, the system doesn't boot with the module plugged in. The
fans begin to spin for approximately 1/4 second, but nothing else.

My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
(~1000rpm)

In the case I have to reflash the module, is it possible to
hotplug it?
Hotplugging is dangerous and not supported, don't do it.
Thank you very much for your support.
You can use a test clip to externally flash it via a flashing device
(not sure which can do 16 pins though, I would inquire on the flashrom
mailinglist)

Are you using the latest coreboot? AFAIK coreboot was patched to
support
OpenBMC, so you need a new version with the patches.


--
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com


--
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com

--
________________________________________ / If time heals all wounds, how come the \
\ belly button stays the same?           /
---------------------------------------- \ ^__^
        \  (oo)\_______
           (__)\       )\/\
               ||----w |
               ||     ||

Attachment: signature.asc
Description: PGP signature

-- 
coreboot mailing list: [email protected]
https://mail.coreboot.org/mailman/listinfo/coreboot

Reply via email to