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:
Reply To:
Date:
Tue, 6 Mar 2012 07:00:03 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
On Tue, Mar 6, 2012 at 6:36 AM, Stephen Berg (Contractor)
<[log in to unmask]> wrote:
> On 03/05/2012 11:04 AM, Stephan Wiesand wrote:
>>
>> ksdevice=link seems to work for us when reinstalling SL5 systems with SL6.
>> But maybe that's just because we have installed all systems with pci=bfsort
>> since the SL4 times, making device numbering consistent across kernel
>> versions (and we use only eth0 for PXE). Using pci=[no]bfsort, it should
>> always be possible to make the interface in use primary one. But then I'm
>> not sure what Networkmanager or the new parallel udev device discovery may
>> be doing... And since 6.1, some (recent Dell) servers have biosdevname
>> enabled by default. Which makes the first onboard interface "em1", for
>> example :-) The advantage is that this will always match the physical socket
>> labelled "1" on the server.
>
> ksdevice=link works for me when I'm doing an actual pxe boot.  I haven't
> used the pci=bfsort parameter but the sorting of the names isn't the problem
> here.  The kernel/initrd.img combo from the DVD seem to be ignoring
> ksdevice=link and ksdevice=<mac addr>.  Regardless of sorting issues those
> should work if I've only got one NIC with an active link, which is true, or
> if I specify the mac address of the NIC I'm installing over.

What happens if you use a regular DVD, tab out of the menu, and add
your "ks=..." and "ksdevice=..." values to the kernel line?

ATOM RSS1 RSS2