> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/smartnic-os-installation-guide/initial-server-setup/about-this-guide.md).

# About This Guide

## EnGenius SmartNIC OS Installation Guide

This guide provides a comprehensive walkthrough for installing supported Linux operating systems on the **EnGenius SmartNIC** platform.\
It is structured into three major parts to help you go from initial connection to a fully deployed and operational system.

<figure><img src="https://4096026543-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FS125JIxOdx1KNxKabTMb%2Fuploads%2FfHIvgLb6F7jeQnYLbreY%2F2.png?alt=media&amp;token=4fac5bf9-9570-4c08-862d-29b243f64145" alt=""><figcaption></figcaption></figure>

### Part 1. Operating System Installation

> [**Chapter 1. RHEL (Red Hat Enterprise Linux) Installation**](/smartnic-os-installation-guide/os-installation/rhel-red-hat-enterprise-linux-installation.md)

* Installation via Serial Console&#x20;
  * Prepare Kickstart ISO (mkksiso tool)
  * Create bootable USB drive
  * Perform installation through mini-USB console
* Installation via BMC iKVM&#x20;
  * Launch HTML5 iKVM viewer
  * Mount ISO via virtual media
  * Modify GRUB and enable serial console
  * Verify console output via `obmc-console-client`

> [**Chapter 2. Rocky Linux 9.4**](/smartnic-os-installation-guide/os-installation/rocky-linux-9.4.md)

* Installation Steps
  * Create bootable USB media
  * Temporary GRUB configuration
  * User setup and permanent GRUB updates

> [**Chapter 3. Ubuntu 22.04 LTS** ](/smartnic-os-installation-guide/os-installation/ubuntu-22.04-lts.md)

* Installation Steps
  * Live USB creation and BIOS boot
  * Temporary GRUB edit for console output
  * Updating `/etc/default/grub` and applying permanent settings
  * Enable `serial-getty@ttyS0` service

> [**Chapter 4. CentOS Stream** ](/smartnic-os-installation-guide/os-installation/centos-stream.md)

* Installation Steps
  * Bootable USB creation
  * Text-mode installation
  * Configure serial console and GRUB
  * Validate kernel parameters and console service

> [**Chapter 5. Partition and Storage Configuration**](/smartnic-os-installation-guide/os-installation/partition-and-storage-configuration.md)&#x20;

* Expanding System Partition
  * Remove unused partitions (`mmcblk0p3`)
  * Extend using `growpart` and `resize2fs`
  * Verify results with `df -h`

### Part 2. Appendix

Contains supporting information to help you maintain, troubleshoot, and understand terminology used in this guide.

**Appendix A. Troubleshooting**

* Common installation issues and solutions\
  (e.g., console not responding, USB not detected, GRUB boot failure)

**Appendix B. Glossary**

* Key technical terms: BMC, iKVM, GRUB, ttyS0, LVM, PFR, etc.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.engenius.ai/smartnic-os-installation-guide/initial-server-setup/about-this-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.