IBM 8677 Installation Guide - Page 49

Device, driver, considerations

Get IBM 8677 - BladeCenter Rack-mountable - Power Supply PDF manuals and user guides
UPC - 000435842312
View all IBM 8677 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 49 highlights

4. Log in as root and install the 2.4.18-18.7.x or later kernel errata using RPM Package Manager. 5. Create an entry for the floppy drive in the /etc/fstab file. Note: The floppy resides on the SCSI device after all other devices. 6. Make a directory for the floppy under /mnt 7. Mount the floppy. 8. If you are using the GNOME desktop, remove the magicdev package (to avoid a system hang). The ability of the remote console applet to accurately track the location of the mouse cursor in a Linux X Window System session depends on the configuration of X Windows. Therefore, you must set the mouse handler with the correct resolution information to track the remote mouse cursor properly. In addition, set the mouse acceleration and threshold values to 1 to synchronize the remote and local mouse. SuSE 8.0: Consider the following when installing SuSE on a blade server: v When you start the server and insert the SuSE Linux Version 8.0 CD 1 into the CD-ROM drive, the CD may not start. In this case, use the SuSE Linux Version 8.0 CD 2 to start. v You may encounter problems with mouse synchronization if you are installing remotely using the remote control option of the BladeCenter management module. These problems can be resolved after installation. During installation, you may have to double-click to make selections that normally only require a single click. v When the installer starts, the mouse will not work. To resolve the problem, when the installer starts, use keyboard navigation to ensure that the mouse is listed as a USB mouse. Device driver considerations Some of the options available for the BladeCenter unit have device drivers that you need to install. See the documentation that comes with your option for information about installing any required device drivers. For example, Ethernet controllers are integrated on each blade server system board. The Ethernet controllers provide 1000-Mbps full-duplex capability only, which enables simultaneous transmission and reception of data to the external ports on the Ethernet switches. You do not need to set any jumpers or configure the controller for the blade server operating system. However, you must install a device driver in the blade server to enable the blade server operating system to address the Ethernet controller. For blade server device driver and information about configuring the Ethernet controllers, see the Broadcom NetXtreme Ethernet Software CD that comes with the BladeCenter unit. Chapter 3. Deployment considerations 39

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
4.
Log
in
as
root
and
install
the
2.4.18–18.7.x
or
later
kernel
errata
using
RPM
Package
Manager.
5.
Create
an
entry
for
the
floppy
drive
in
the
/etc/fstab
file.
Note:
The
floppy
resides
on
the
SCSI
device
after
all
other
devices.
6.
Make
a
directory
for
the
floppy
under
/mnt
7.
Mount
the
floppy.
8.
If
you
are
using
the
GNOME
desktop,
remove
the
magicdev
package
(to
avoid
a
system
hang).
The
ability
of
the
remote
console
applet
to
accurately
track
the
location
of
the
mouse
cursor
in
a
Linux
X
Window
System
session
depends
on
the
configuration
of
X
Windows.
Therefore,
you
must
set
the
mouse
handler
with
the
correct
resolution
information
to
track
the
remote
mouse
cursor
properly.
In
addition,
set
the
mouse
acceleration
and
threshold
values
to
1
to
synchronize
the
remote
and
local
mouse.
SuSE
8.0:
Consider
the
following
when
installing
SuSE
on
a
blade
server:
v
When
you
start
the
server
and
insert
the
SuSE
Linux
Version
8.0
CD
1
into
the
CD-ROM
drive,
the
CD
may
not
start.
In
this
case,
use
the
SuSE
Linux
Version
8.0
CD
2
to
start.
v
You
may
encounter
problems
with
mouse
synchronization
if
you
are
installing
remotely
using
the
remote
control
option
of
the
BladeCenter
management
module.
These
problems
can
be
resolved
after
installation.
During
installation,
you
may
have
to
double-click
to
make
selections
that
normally
only
require
a
single
click.
v
When
the
installer
starts,
the
mouse
will
not
work.
To
resolve
the
problem,
when
the
installer
starts,
use
keyboard
navigation
to
ensure
that
the
mouse
is
listed
as
a
USB
mouse.
Device
driver
considerations
Some
of
the
options
available
for
the
BladeCenter
unit
have
device
drivers
that
you
need
to
install.
See
the
documentation
that
comes
with
your
option
for
information
about
installing
any
required
device
drivers.
For
example,
Ethernet
controllers
are
integrated
on
each
blade
server
system
board.
The
Ethernet
controllers
provide
1000-Mbps
full-duplex
capability
only,
which
enables
simultaneous
transmission
and
reception
of
data
to
the
external
ports
on
the
Ethernet
switches.
You
do
not
need
to
set
any
jumpers
or
configure
the
controller
for
the
blade
server
operating
system.
However,
you
must
install
a
device
driver
in
the
blade
server
to
enable
the
blade
server
operating
system
to
address
the
Ethernet
controller.
For
blade
server
device
driver
and
information
about
configuring
the
Ethernet
controllers,
see
the
Broadcom
NetXtreme
Ethernet
Software
CD
that
comes
with
the
BladeCenter
unit.
Chapter
3.
Deployment
considerations
39