# Lambda Quad: Network Failure after reboot

**URL:** <https://deeptalk.lambda.ai/t/lambda-quad-network-failure-after-reboot/3018>\
**Category:** Technical Help\
**Created:** [June 3, 2022, 9:54pm UTC](https://deeptalk.lambda.ai/t/lambda-quad-network-failure-after-reboot/3018 "2022-06-03T21:54:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![markd](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@markd](https://deeptalk.lambda.ai/u/markd)\
**Post date:** [June 8, 2022, 3:33am UTC](https://deeptalk.lambda.ai/t/lambda-quad-network-failure-after-reboot/3018/2 "2022-06-08T03:33:16Z")

</div>

Geshi,

It would be best to send a email to: [support@lambdal.com](mailto:support@lambdal.com)

Most workstation mothers have the Qcode lights on the motherboard, a few have IPMI/iKVM instead.

On the motherboard there would likely be lights on the board with a ‘88’ which are used to spell out different motherboard codes (Qcode or Postcode) A0,c2, etc… that can be looked up in the motherboard manual. We would need to figure out which order/machine and motherboard.

It sounds like it is not booted. It may be best to shutdown, unplug and clear the CMOS. Then power up again. (The clear CMOS varies on the motherboard also).

But emailing [support@lambdal.com](mailto:support@lambdal.com) would be best.

Mark

---

_[View the full topic](https://deeptalk.lambda.ai/t/lambda-quad-network-failure-after-reboot/3018)._
