Hi Tom,

I tried adding ksdevice=sdb (my USB ks.cfg key) to the kernel boot line
during installer but it made no difference. Thanks anyway!

regards,
kent

-----Original Message-----
From: [log in to unmask]
[mailto:[log in to unmask]] On Behalf Of Tom
H
Sent: Wednesday, August 10, 2011 3:53 PM
To: [log in to unmask]
Subject: Re: SL6.1 kickstart persistent networkmanager prevents
unattended install

On Wed, Aug 10, 2011 at 4:37 PM, Johnson, Kent A (GE Healthcare)
<[log in to unmask]> wrote:
>>>
>>> Sorry to bother but I've tried to do my homework first, to no
avail...
>>>
>>> I'm kickstarting the standard SL6.1 install DVD from a USB key to
>>> provide an unattended install.
>>>
>>> I've tried everything I can find to try to prevent the
networkmanager
>>> popup to configure the ethernet interface during the install (occurs
>>> immediately after disk partitioning).
>>>
>>> I've tried many different forms of the kickstart network command to
>>> fully configure eth0 or leaving the network line out completely but
the
>>> nm popup persists. The only way that I've been able to stop the nm
popup
>>> during the kickstart install is to disable the ethernet hardware in
the
>>> BIOS! I've read all the RH/SL docs and searched the web far and
wide...
>>>
>>> So, it seems that anaconda starts networkmanager any time that it
finds
>>> an ethernet device (active or not)  whether the kickstart references
>>> network or not. I'm not adding any external repos or anything else
that
>>> would require network. What am I missing?
>>
>> Untested because I use "ks=http://...": how about "ksdevice=" or
"ksdevice=''"?

> I previously tried using --ksdevice when fully specifying the eth0 but
that
> is a pxelinux format that's rejected by anaconda when using media
kickstart.
> I also just removed the kickstart firewall line in case that was
somehow
> causing networkmanager to be invoked but no-go.

> I can pxeboot install fine but we have cases where must do a media
(local)
> install, and unattended, but networkmanager pops up no matter I try...

When you write "--ksdevice" it looks to me like you mean that you're
adding it to the "network..." line in ks.cfg.

What I meant was to try to add "ksdevice=" or "ksdevice=''" as a
kernel argument when you add "ks=hd:...".