Re: boot parameter interface=auto can't adaptation the correct NIC

[Floris Bos <info@je-eigen-domein.nl>]

Hi,

On Monday, December 13, 2010 04:15:46 am Qin Bo wrote:
> 2010/12/10 Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
> 
> > Is this another case of a driver/NIC taking longer to get link up after
> > being enabled than the installer is willing to wait?  I seem to recall
> > a bnx2 user a few days ago reporting a similar problem.
> 
> How can i find the bnx2 problem? I had set  netcfg/dhcp_timeout=60 as boot
> parameter, the problem still reproduce.
> But I still think the netcfg didn't got the correct interface, then
> couldn't get the IP address from dhcp server.
> Because I had read the netcfg source:netcfg.c netcfg-common.c, i can't find
> where the program deal with interface=auto.

You need "netcfg/choose_interface=auto"


As far as the detection goes, it is this part in netcfg.c:

==
                    interface_up(*ifaces);

                    usleep(250);

                    if (ethtool_lite (*ifaces) == 1) /* CONNECTED */ {
                        di_info("found link on interface %s, making it the 
default.", *ifaces);
                        defiface = strdup(*ifaces);
                        interface_down(*ifaces);
                        break;
                    } else {
#ifdef WIRELESS
                        struct wireless_config wc;
#endif /* WIRELESS */
                        di_info("found no link on interface %s.", *ifaces);
==


A 250 us delay is kinda short.

It takes 3 seconds for the link of my test box to get up.
(on-board Intel 82574L NIC, connected to a HP 1810G gigabit switch).


-- 
Yours sincerely,

Floris Bos