[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

help to

Ferney Rodriguez G
Aplicaciones Ltda
Tels:3172867-3172897 ext105
Bogota D.C, Colombia

-----Mensaje original-----
De: anaconda-devel-list-bounces redhat com
[mailto:anaconda-devel-list-bounces redhat com]En nombre de
anaconda-devel-list-request redhat com
Enviado el: Domingo, 09 de Mayo de 2004 11:00 a.m.
Para: anaconda-devel-list redhat com
Asunto: Anaconda-devel-list Digest, Vol 3, Issue 7

Send Anaconda-devel-list mailing list submissions to
	anaconda-devel-list redhat com

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
	anaconda-devel-list-request redhat com

You can reach the person managing the list at
	anaconda-devel-list-owner redhat com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Anaconda-devel-list digest..."

Today's Topics:

   1. Remote Installation of Fedora (Felix Schwarz)
   2. RE: NFS kickstart fails with e1000.ko drivers (Joe Robertson)


Message: 1
Date: Sat, 8 May 2004 19:36:13 +0200
From: Felix Schwarz <felix schwarz-online org>
Subject: Remote Installation of Fedora
To: anaconda-devel-list redhat com
Message-ID: <17115799588 20040508193613 schwarz-online org>
Content-Type: text/plain; charset=us-ascii


(Foreword: If this question is on the wrong list please point me to
the right list. Thanks)

I have a remote server with a high speed internet connection and I
want to install Fedora (Core 1) on this server (currently running
another linux).

What I tried:
I created a grub entry and copied several files from the Fedora cds on
my harddisk so that the system starts the installation process
automatically when I'll reboot.
I wanted to use the VNC install method to install this remote server
but it failed. Before the vnc server starts there are several dialogs
(language, network settings) so the install process hangs.

How can I install Fedora on a remote server? I heard of kickstart but
I don't want to install many servers but only one so using kickstart
seems to be overkill to me.

Btw: VNC over SSH would be nice. Or even better: Starting the
installation manually after login with ssh. Any plans implementing this?

thanks in advance


Message: 2
Date: Sat, 8 May 2004 17:26:38 -0700
From: "Joe Robertson" <jrobertson convera com>
Subject: RE: NFS kickstart fails with e1000.ko drivers
To: <golharam umdnj edu>,	"Discussion list about Kickstart"
	<kickstart-list redhat com>
Cc: anaconda-devel-list redhat com
	<CB104DBE25378C4FAA2B70E0D43C8544033C22FE cbpo convera com>
Content-Type: text/plain;	charset="us-ascii"

Well, I've done quite a bit of testing to characterize 
this  year-old problem when using Gbit ethernet interface 
cards.  I believe the answer is somewhere in anaconda and 
is timing related.

My next step is to load anaconda source and try to 
figure out how to fix this issue (I don't know anaconda 
nor python so that will be a slow process).  This problem 
appears this has been in the discussion world for the past 
year now and is still a problem as evidenced by the number 
of responses I've seen to my first post.  I'm pretty well 
convinced this is simply a timing issue and anaconda is 
declaring a failure too early.

Perhaps someone with anaconda knowledge can point me in a 
direction that might help?

My test effort / results to date:

With considerable help from Richard Black, I've gone through 
modifying the initrd.img file to insert a script that
loads the NIC driver then sleep for awhile before 
anaconda starts.  The changes made to implement this idea
work but they don't help - anaconda loads the 
driver again anyway.

I then tried removing the entry for the e1000 driver for 
my card in the /modules/pcitable file in the initrd.img 
file.  This didn't work since I then got a report that 
there was no network driver and the install terminated.

Based on a suggesion by seph, I have experimented with
connecting the pxe installation client to one of several
different switch models. I found that some switches 
appear to work around the problem (Unfortunately I 
can't use any of the switches that do work around it - 
they are all 10/100). This does let me validate all of 
my setup and I know that the kickstart configuration is 

After finding a switch that allowed a kickstart via 
network, I immediately ran into a bug reported earlier 
by Martin Robb
and I cannot get Fedora Core 2 test 3 to finish a 
kickstart install (error installing at-3.1.8-52).  

Does anyone know of a fix for this yet?

I was  able to get Core 2 test 2 to run kickstart to 
completion. I tested the following switches and found 
some that worked and some that didn't.  I tested with 
the kickstart file via NFS and HTTP and the installation 
files via NFS.

  Switches used when the kickstart install was successful
  (via network):

	Linksys EZXS16W 	16 Port EtherFast 10/100 (Unmanaged)
		(HTTP ks failed once - tried again it worked)
	Intel InBusiness	16 Port 10/100 Switch (Unmanaged)
	Netgear FS108 	8 Port 10/100 Switch (Unmanaged)

  Switches used when the install failed to get the kickstart 
  file (NFS or HTTP):

	No switch		(used crossover cable directly from
				pxe install server and client.  The
				install server and client both use
				the same Gbit ethernet type)
	Netgear GS105 	5 Port Gigabit Switch (Unmanaged)
	Netgear GS524T 	24 Port Gigabit Switch (Unmanaged)
	3COM 3C39036	36 Port 10/100 (Managed)
		Spanning Tree disabled
		Autonegotiate disabled	
		Port set to 100half and 100full (separate tests)

Note:  Interactive installs work in all of these cases 
and I have no problems with the network once the 
installation is done.  The only failure mode here is 
when anaconda loads the drivers and attempts to do an 
NFS or HTTP access for kickstart. I tried loading the 
kickstart file from floppy and the failure was simply 
delayed until it needed to access the NFS for the install 

A suggestion was made by lccha-rhlist naos org to update 
the e1000.ko NIC driver with the latest from Intel. I 
looked at their download site and their latest appears to
be the same version that is in test 3.  The Intel version 
is 5.2.39 and the Fedora Core 2 test 3 version is 
(reported when loaded by insmod) as 5.2.39-k2.

I've been pulling my hair out on this one and really
need to resolve it.  I'm preparing to install a large
number of machines using pxe installs and I don't
want to have to do each one interactively.  It would
be great to get a fix for this in the Core 2 release.

Thanks for any suggestions / help.

> -----Original Message-----
> From: Ryan Golhar [mailto:ryangolhar verizon net] 
> Sent: Friday, May 07, 2004 8:08 PM
> To: 'Discussion list about Kickstart'
> Subject: RE: NFS kickstart fails with e1000.ko drivers
> I observed the same thing with a Cisco switch.  The switch 
> was set at 10 Mbps half-duplex.  The fact that it was 
> obtaining a DHCP IP address threw me off for quite awhile.  
> -----Original Message-----
> From: kickstart-list-bounces redhat com 
> [mailto:kickstart-list-bounces redhat com] On > Behalf Of seph
> Sent: Friday, May 07, 2004 10:12 PM
> To: Discussion list about Kickstart
> Subject: Re: NFS kickstart fails with e1000.ko drivers
> > The switches I'm currently using are unmanaged netgear 24 
> port (or 5 
> > port) cheap switches so there is no way to change this.
> > I've tried using a crossover cable so the switch was eliminated 
> > altogether - same results.  I also tried using a 3COM 3C39036
> > 100 Mbit switch in default mode (I'll learn how - then try 
> > setting the portfast later to see if it helps.)
> I observed the same problem, and mentioned it here at the end 
> of march. unfortunately, I then got buried in work, and 
> didn't get a chance to debug it.
> I'd observed that kickstart failed for my dells with intel 
> gige on the motherboard. But only when hooked up to netgear 
> equipment. Failed on both a netgear gige switch, as well as a 
> netgear 10/100 hub. Worked okay on a cheap linksys switch though.
> I also observed the same failure. Namely, I could manually 
> walk through an install, but kickstart always failed to fetch 
> its config file. Interestingly, it successfully used dhcp to 
> get an ip address.
> I'm certainly interested in whatever results you end up with.
> seph
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list redhat com 
> https://www.redhat.com/mailman/listinfo/kickst> art-list
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list redhat com 
> https://www.redhat.com/mailman/listinfo/kickst> art-list


Anaconda-devel-list mailing list
Anaconda-devel-list redhat com

End of Anaconda-devel-list Digest, Vol 3, Issue 7

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]