Solarflare
Server
Adapter
User
Guide
Solarflare
Adapters
on
Linux
Issue
20
©
Solarflare
Communications
2017
69
2
Identify
the
driver
dependencies
using
the
modinfo
command:
modinfo
./sfc.ko
|
grep
depends
depends:
i2c
‐
core,mii,hwmon,hwmon
‐
vid,i2c
‐
algo
‐
bit
mtdcore
mtdpart
All
modules
listed
as
depends
must
be
present
in
the
initrd
file
image.
In
addition
the
user
should
be
aware
of
further
dependencies
which
can
be
resolved
by
adding
the
following
lines
to
the
modules.dep
file:
sfc:
i2c
‐
core
mii
hwmon
hwmon
‐
vid
i2c
‐
algo
‐
bit
mtdcore
mtdpart
1
i2c
‐
algo
‐
bit:
i2c
‐
core
mtdpart:
mtdcore
3
A
configured
kickstart
file
with
the
Solarflare
Driver
RPM
manually
added
to
the
%Post
section.
For
example:
%post
/bin/mount
‐
o
ro
<IP
Address
of
Installation
server>:/<path
to
location
directory
containing
Solarflare
RPM>
/mnt
/bin/rpm
‐
Uvh
/mnt/<filename
of
Solarflare
RPM>
/bin/umount
/mnt
3.10
Unattended
Installation
‐
SUSE
Linux
Enterprise
Server
Unattended
SUSE
Linux
Enterprise
Server
installations
are
configured
with
AutoYaST.
The
documentation
for
AutoYaST
can
be
found
at:
https://www.suse.com/documentation/sles11/book_autoyast/data/
book_autoyast.html
https://www.suse.com/documentation/sles
The
prerequisites
for
a
Network
AutoYaST
installation
are:
•
SUSE
Linux
Enterprise
installation
media.
•
A
DHCP
server
for
IP
address
assignments
and
to
launch
PXE
Boot.
•
A
NFS
or
FTP
server
to
provide
the
installation
source.
•
A
TFTP
server
for
the
download
of
the
kernel
boot
images
needed
to
PXE
Boot.
•
A
boot
server
on
the
same
Ethernet
segment.
•
An
install
server
with
the
SUSE
Linux
Enterprise
Server
OS.
•
An
AutoYaST
configuration
server
that
defines
rules
and
profiles.
•
A
configured
AutoYaST
Profile
(control
file).
1.
For
Red
Hat
Enterprise
Linux
from
version
5.5
add
mdio
to
this
line.