Subject: | |
From: | |
Reply To: | Stephen Berg (Contractor) |
Date: | Tue, 6 Mar 2012 13:41:29 -0600 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On 03/06/2012 01:33 PM, Tom H wrote:
> You're probably right but I just wanted to take out of the equation
> the possibility that you're getting the NIC-choice screen because the
> ksdevice wasn't getting enough info to set itself up. Another idea is
> that you're using the wrong NIC name. There's an app developed by Dell
> (name forgotten sorry) that renames NICs emX or pXpY (depending on
> whether they're embedded or in a PCI slot) and the card that you're
> choosing as your ksdevice might have been renamed.
The biosdevname=0 in my kernel command line disables that NIC renaming.
I get standard eth0 and eth1. That "feature" is nifty, but it breaks a
few things also. MatLab doesn't like to set up a license file for
anything other than a system with eth0.
> Is the box where your procedure fails a Dell or HP because those are
> the two manufacturers, AFAIK, on which the NIC renaming takes place.
>
Nope, it's a MicroWay rack mount box, old-ish Opteron based system.
Trying to squeeze as much work out of it and others like it before they
finally croak on me.
I'm hoping to try to specify the network setup in the kernel line
tomorrow morning, we'll see if it changes the behavior.
--
Stephen Berg
Systems Administrator
NRL Code: 7320
Office: 228-688-5738
[log in to unmask]
|
|
|