SCIENTIFIC-LINUX-USERS Archives

March 2012

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
William of BHE <[log in to unmask]>
Reply To:
William of BHE <[log in to unmask]>
Date:
Tue, 6 Mar 2012 10:28:42 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
If you think that it's trying to use the Intel 82541PL, blacklisting the 
module will keep it from trying to use the NIC:

Add this to your kernel boot options:
blacklist=e1000

kernel /vmlinuz ramdisk_size=64063 blacklist=e1000 ks=nfs:<IP 
ADDR>:/export/install/kickstart/hostname.ks lang=en_US.UTF-8 keymap=us 
biosdevname=0 ksdevice=link rdblacklist=nouveau nomodeset vnc 
vncpassword=<password> sshd sshpw --username=<loginid>


--W

On 3/6/2012 9:44 AM, Stephen Berg (Contractor) wrote:
> On 03/06/2012 08:06 AM, William of BHE wrote:
>>
>> Can you post your grub.conf lines? And maybe what kind of NICs you're 
>> using? Logs? Why the pxeboot kernel & initrd if you're not using pxe? 

> One nic is a broadcom BCM5703X embedded on the motherboard, that's the 
> active NIC.  There's an add-on card Intel 82541PI, that is not hooked 
> up to anything at this time.
[...snip...]
>
> After talking with a co-worker we had the thought that some of these 
> parameters might need to be on a separate append line in grub.conf 
> which would make it look like a pxeboot file.  Gonna try that next.
>

ATOM RSS1 RSS2