It didn't work.

My question is: why is NetworkManager trying to configure the interface if the install method is not network based?

Any other ideas?

On Wed, Jul 13, 2011 at 4:58 PM, j.e.aneiros <jesus.aneiros@gmail.com> wrote:
So, it would be something like:

linux ks=hd:sdb1:/ks.cfg.ip=192.168.0.1

I'll try it and let you know. This kludge is gonna be interesting.

Thanks Terry.


On Wed, Jul 13, 2011 at 4:50 PM, Terry Polzin <foxec208@wowway.com> wrote:
On Wed, 2011-07-13 at 16:41 -0400, j.e.aneiros wrote:
> No, it is not necessary 'cause I'm giving the entry hd:sdb1, and
> that's working, but thanks anyways.
>
> On Wed, Jul 13, 2011 at 4:34 PM, Terry Polzin <foxec208@wowway.com>
> wrote:
>
>         On Wed, 2011-07-13 at 16:23 -0400, j.e.aneiros wrote:
>         > Hi,
>         >
>         >
>         > I hope this is the right place for posting this question.
>         >
>         >
>         > I'm trying to perform an installation using kickstart and I
>         having a
>         > hard time trying to disable NetworkManager during the time
>         previous to
>         > the real installation, it says it is trying to configure
>         eth0.
>         >
>         >
>         > I'm using a CDROM based installation with a kickstart file
>         on a USB
>         > memory. The line I'm typing for the kernel is as follows:
>         >
>         >
>         > linux ks=hd:sdb1:/ks.cfg
>         >
>         >
>         > I also tried
>         >
>         >
>         > linux ks=hd:sdb1:/ks.cfg nonet noipv6
>         >
>         >
>         > But still getting the timeout popup message.
>         >
>         >
>         > I don't want any human intervention during the install,
>         besides
>         > putting the CD in and taking it out.
>         >
>         >
>         > I need to have the network configured to access the machine
>         via ssh
>         > after the reboot. All this is intended for remote install
>         purposes in
>         > several machines.
>         >
>         >
>         > Any suggestion will be of help.
>         >
>         >
>         > Thanks in advance.
>         >
>         > --
>         > J. E. Aneiros
>         > GNU/Linux User #190716 en http://counter.li.org
>         > perl -e
>         >
>         '$_=pack(c5,0105,0107,0123,0132,(1<<3)+2);y[A-Z][N-ZA-M];print;'
>         > PK fingerprint: 5179 917E 5B34 F073 E11A  AFB3 4CB3 5301
>         4A80 F674
>         >
>         >
>
>
>         I think you need to specify that your ks file is
>         on /dev/sdb1/ks.cfg  /ks.cfg may be leading the installer to
>         believe
>         that the ks file is on /dev/sda someplace/
>
>         --
>         users mailing list
>         users@lists.fedoraproject.org
>         To unsubscribe or change subscription options:
>         https://admin.fedoraproject.org/mailman/listinfo/users
>         Guidelines:
>         http://fedoraproject.org/wiki/Mailing_list_guidelines
>
>
>
> --
> J. E. Aneiros
> GNU/Linux User #190716 en http://counter.li.org
> perl -e
> '$_=pack(c5,0105,0107,0123,0132,(1<<3)+2);y[A-Z][N-ZA-M];print;'
> PK fingerprint: 5179 917E 5B34 F073 E11A  AFB3 4CB3 5301 4A80 F674
>

OK have you tried putting a fixed IP address on the port? NM is probably
sending out a DHCP request that is not being responded to, regardless of
it's use during the install process you may want to
address it.

--



--
J. E. Aneiros
GNU/Linux User #190716 en http://counter.li.org
perl -e '$_=pack(c5,0105,0107,0123,0132,(1<<3)+2);y[A-Z][N-ZA-M];print;'
PK fingerprint: 5179 917E 5B34 F073 E11A  AFB3 4CB3 5301 4A80 F674




--
J. E. Aneiros
GNU/Linux User #190716 en http://counter.li.org
perl -e '$_=pack(c5,0105,0107,0123,0132,(1<<3)+2);y[A-Z][N-ZA-M];print;'
PK fingerprint: 5179 917E 5B34 F073 E11A  AFB3 4CB3 5301 4A80 F674