Network Booting MiniMyth Configuration

Covers how to configure an environment to network boot MiniMyth with an NFS root using a Fedora Core 6 backend with an IPCop router.

[CURRENTLY UNDER DEVELOPMENT]’, ‘

Assumptions

Preparation

To start, there are several pieces of information that is required to configure a system for MiniMyth. The easiest thing

to do is to boot the system with a live CD to determine the information.

First, determine the mac address of the ethernet adapter.

ifconfig eth0

eth0      Link encap:Ethernet  HWaddr 00:50:2c:a7:81:26
          inet addr:10.10.8.24  Bcast:10.10.8.255  Mask:255.255.255.0
          inet6 addr: fe80::216:e6ff:fe8d:7e8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:208096 errors:0 dropped:0 overruns:0 frame:0
          TX packets:214489 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:42024483 (40.0 MiB)  TX bytes:108963963 (103.9 MiB)
          Interrupt:22

My MAC address (HWaddr) is 00:50:2c:a7:81:26

Next, the PCI Manufacturer ID and Device ID for the network card is required:

lspci | grep Ethernet

00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2)

lspci -n | grep 00.07.0
00:07.0 0680: 10de:03ef (rev a2)

So in the example above, the manufacturer id is 10de and the device id is 03ef. For my actual motherboard, I fould

1106:3065.

At this point, it may be worth while to verify that the video card that you have is supported by MiniMyth.

lspci | grep VGA

00:0d.0 VGA compatible controller: nVidia Corporation GeForce 6100 nForce 430 (rev a2)

lspci | grep Audio

00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2)

Before spending more time, take a look at the supported hardware for MiniMyth to make sure that your devices are

supported.

http://www.linpvr.org/minimyth/document-

hardware.shtml

[future plans, include steps to add support for ourselves for unsupported hardware.]

Supporting RPL Booting

My motherboard does not support booting via PXE. It only supports Novell NetWare RPL booting. However, I have found

that using etherboot, that it is possible to boot an Etherboot ROM using RPL which can then start the PXE Boot process.

If your motherboard supports booting via PXE directly, skip this section.

Previously, we found that my manufacturer and device IDs for my ethernet card were 1106 and 3065.

So, I then go to http://rom-o-matic.net/ and click the latest production release of

Etherboot.

  • There, using the IDs, choose the correct NIC/ROM type. For the above, it is “via-rhine:via6105m —

    [0x1106,0x3053]”

  • Next, correct the ROM output format to “Binary ROM Image(.zrom)”
  • I glanced through the customizable ROM configuration settings, and found that I didn\’t care to make any changes.
  • I just clicked on “Get ROM” and saved the file to to [pci-manuf]_[pci-devid].zrom, or 1106_3065.zrom in this

    example.

/netboot/
/netboot/rpld.conf <-- The configuration file.
/netboot/[pci-manuf]_[pci-devid].zrom <-- The etherboot rom for the given nic. Configure rpld.conf start rpld

Supporting PXE Booting

In IPCop, configure fixed lease:
Mac address: 00:50:2c:a7:81:26
IP Address: 10.10.8.24
Remark: Diskless Mythfrontend
Hostname: mythfe2
Next Server: 10.10.8.23 <-- Your tftp boot server, my mythtv backend.
Filename: /pxelinux.0 <-- The pxelinux boot image.

Configuring MiniMyth

My Hardware

  • Motherboard — SY-KT600 Dragon v2.0
  • Videocard — GeForce 4400

Leave a Reply