Re: boot parameter interface=auto can't adaptation the correct NIC
2010/12/13 Jon Ander Ortiz jonba...@gmail.com I've suffered the same issue in some netcards (nexcom and portwell HW). The usleep of netcfg.c is not enought to up the interface and detect the link up in auto mode (buggy driver or buggy hardware?? :-/). In my case the sleep goes to some seconds (4-5 secs.). Hi all, I had modified the usleep to 3 secs in netcfg.c, then I can get IP address from dhcp server. From this we seems need to usleep configurable is better, not only hard code 250, we can let it have a default value 250, if not configure by user. -- Best Regards, Qin Bo
Re: boot parameter interface=auto can't adaptation the correct NIC
I've suffered the same issue in some netcards (nexcom and portwell HW).
The usleep of netcfg.c is not enought to up the interface and detect the
link up in auto mode (buggy driver or buggy hardware?? :-/).
In my case the sleep goes to some seconds (4-5 secs.).
BR
2010/12/13 Floris Bos i...@je-eigen-domein.nl
Hi,
On Monday, December 13, 2010 04:15:46 am Qin Bo wrote:
2010/12/10 Lennart Sorensen lsore...@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
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org
Archive:
http://lists.debian.org/201012130441.46315.i...@je-eigen-domein.nl
Re: boot parameter interface=auto can't adaptation the correct NIC
On Mon, Dec 13, 2010 at 11:15:46AM +0800, Qin Bo wrote: 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. It might have been the tg3 mentioned here: http://lists.debian.org/debian-boot/2010/12/msg00230.html hard to keep track of all the network types. If the logs were correct, it certainly looks like the interface was brought up and udhcpc tried it, but didn't wait long enough for link to come up first, and gave up and went to the next interface. Maybe gigabit interfaces are slow to come up, and the delay in udhcpc or the installer needs to be longer. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101213172503.gw12...@caffeine.csclub.uwaterloo.ca
Re: boot parameter interface=auto can't adaptation the correct NIC
2010/12/10 Lennart Sorensen lsore...@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.
Re: boot parameter interface=auto can't adaptation the correct NIC
Hi,
On Monday, December 13, 2010 04:15:46 am Qin Bo wrote:
2010/12/10 Lennart Sorensen lsore...@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
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201012130441.46315.i...@je-eigen-domein.nl
Re: boot parameter interface=auto can't adaptation the correct NIC
Quoting Qin Bo (kinbos...@gmail.com): hi all: I use squeeze Nov 6 build iso to install, i had three network interface card, a onboard NIC and two stand alone NIC is intel e1000, and e1000 1st(eth1) is plug a cable, e1000 2nd(eth2) and onboard(eth0) is not, i want to auto configure the NIC which plug cable (at this is e1000 1st, eth1), so i write interface=auto as boot parameter, but when get ip from dhcp server, the installation can't get ip. when i configure network manually, found the ip configure onboard NIC, that is say the ip is configure on eth0 not eth1. any idea? Or may be is a bug? If i want to auto configure the NIC which plug cable, how to? It would be interesting to get the installer logs. Could you try processing manually (but boot with interface=auto), complete the installation and then send the /var/log/installer files which you'll find on the installed system? To avoid a lengthy install, just do an install without any task selected (not even standard system). signature.asc Description: Digital signature
Re: boot parameter interface=auto can't adaptation the correct NIC
2010/12/10 Christian PERRIER bubu...@debian.org Quoting Qin Bo (kinbos...@gmail.com): hi all: I use squeeze Nov 6 build iso to install, i had three network interface card, a onboard NIC and two stand alone NIC is intel e1000, and e1000 1st(eth1) is plug a cable, e1000 2nd(eth2) and onboard(eth0) is not, i want to auto configure the NIC which plug cable (at this is e1000 1st, eth1), so i write interface=auto as boot parameter, but when get ip from dhcp server, the installation can't get ip. when i configure network manually, found the ip configure onboard NIC, that is say the ip is configure on eth0 not eth1. any idea? Or may be is a bug? If i want to auto configure the NIC which plug cable, how to? It would be interesting to get the installer logs. Could you try processing manually (but boot with interface=auto), when i disable the onboard card, then it can get ip from dhcp, if i manually select eth1, it also can work, in other words the NIC e1000 1st (eth1) is OK. but, i couldn't try it manually beacause i want to install the system with automatic netinstall finally, so i must use interface=auto as boot parameter, let installer can't auto adapt the NIC which have plug a cable. complete the installation and then send the /var/log/installer files which you'll find on the installed system? here is the relative log: Dec 10 10:48:06 main-menu[358]: INFO: Menu item 'ethdetect' selected Dec 10 10:48:06 kernel: [ 25.607101] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded Dec 10 10:48:06 kernel: [ 25.607125] r8169 :02:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 Dec 10 10:48:06 kernel: [ 25.607167] r8169 :02:00.0: setting latency timer to 64 Dec 10 10:48:06 kernel: [ 25.607210] alloc irq_desc for 26 on node -1 Dec 10 10:48:06 kernel: [ 25.607212] alloc kstat_irqs on node -1 Dec 10 10:48:06 kernel: [ 25.607228] r8169 :02:00.0: irq 26 for MSI/MSI-X Dec 10 10:48:06 kernel: [ 25.607831] eth0: RTL8168c/8111c at 0xc934e000, 00:21:85:01:ff:5c, XID 1c2000c0 IRQ 26 Dec 10 10:48:06 kernel: [ 25.615707] Intel(R) PRO/1000 Network Driver - version 7.3.21-k5-NAPI Dec 10 10:48:06 kernel: [ 25.615710] Copyright (c) 1999-2006 Intel Corporation. Dec 10 10:48:06 kernel: [ 25.615748] e1000 :03:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 Dec 10 10:48:06 net/hw-detect.hotplug: Detected hotpluggable network interface lo Dec 10 10:48:06 net/hw-detect.hotplug: Detected hotpluggable network interface eth0 Dec 10 10:48:07 kernel: [ 25.867589] e1000: :03:00.0: e1000_probe: (PCI:33MHz:32-bit) 00:07:e9:10:79:e1 Dec 10 10:48:07 kernel: [ 25.902177] e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection Dec 10 10:48:07 kernel: [ 25.902208] e1000 :03:01.0: PCI INT A - GSI 17 (level, low) - IRQ 17 Dec 10 10:48:07 kernel: [ 26.154391] e1000: :03:01.0: e1000_probe: (PCI:33MHz:32-bit) 00:07:e9:10:79:de Dec 10 10:48:07 kernel: [ 26.193637] e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection Dec 10 10:48:07 net/hw-detect.hotplug: Detected hotpluggable network interface eth2 Dec 10 10:48:07 net/hw-detect.hotplug: Detected hotpluggable network interface eth1 Dec 10 10:48:07 hw-detect: Loading PCMCIA bridge driver module: i82365 Dec 10 10:48:07 hw-detect: FATAL: Module i82365 not found. Dec 10 10:48:08 check-missing-firmware: no missing firmware in /dev/.udev/firmware-missing Dec 10 10:48:08 kernel: [ 27.596162] r8169: eth0: link down Dec 10 10:48:08 kernel: [ 27.596495] ADDRCONF(NETDEV_UP): eth0: link is not ready Dec 10 10:48:08 kernel: [ 27.626452] ADDRCONF(NETDEV_UP): eth1: link is not ready Dec 10 10:48:08 kernel: [ 27.683856] ADDRCONF(NETDEV_UP): eth2: link is not ready Dec 10 10:48:09 init: starting pid 339, tty '/dev/tty2': '-/bin/sh' Dec 10 10:48:09 check-missing-firmware: no missing firmware in /dev/.udev/firmware-missing Dec 10 10:48:10 main-menu[358]: INFO: Menu item 'netcfg' selected Dec 10 10:48:10 netcfg[3916]: INFO: eth0 is disconnected. (MII) Dec 10 10:48:10 netcfg[3916]: INFO: eth0 is not a wireless interface. Continuing. Dec 10 10:48:10 kernel: [ 29.266430] r8169: eth0: link down Dec 10 10:48:10 kernel: [ 29.266760] ADDRCONF(NETDEV_UP): eth0: link is not ready Dec 10 10:48:10 netcfg[3916]: INFO: eth1 is disconnected. (MII) Dec 10 10:48:10 netcfg[3916]: INFO: eth1 is not a wireless interface. Continuing. Dec 10 10:48:10 kernel: [ 29.289684] ADDRCONF(NETDEV_UP): eth1: link is not ready Dec 10 10:48:10 netcfg[3916]: INFO: eth2 is disconnected. (MII) Dec 10 10:48:10 netcfg[3916]: INFO: eth2 is not a wireless interface. Continuing. Dec 10 10:48:10 kernel: [ 29.347050] ADDRCONF(NETDEV_UP): eth2: link is not ready Dec 10 10:48:10 kernel: [ 29.437364] r8169: eth0: link down Dec 10 10:48:10 kernel: [ 29.437695] ADDRCONF(NETDEV_UP): eth0: link is not ready Dec 10 10:48:45 kernel: [ 63.884359] lo: Disabled Privacy Extensions Dec 10 10:48:45 kernel: [
Re: boot parameter interface=auto can't adaptation the correct NIC
On Fri, Dec 10, 2010 at 05:45:30PM +0800, Qin Bo wrote: Dec 10 10:49:14 netcfg[3916]: INFO: eth0 is disconnected. (MII) Dec 10 10:49:14 netcfg[3916]: INFO: eth0 is not a wireless interface. Continuing. Dec 10 10:49:14 netcfg[3916]: INFO: eth1 is disconnected. (MII) Dec 10 10:49:14 netcfg[3916]: INFO: eth1 is not a wireless interface. Continuing. Dec 10 10:49:14 kernel: [ 93.801715] ADDRCONF(NETDEV_UP): eth1: link is not ready Dec 10 10:49:14 kernel: [ 93.804385] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Dec 10 10:49:15 netcfg[3916]: INFO: eth2 is disconnected. (MII) Dec 10 10:49:15 netcfg[3916]: INFO: eth2 is not a wireless interface. Continuing. Dec 10 10:49:15 kernel: [ 93.867068] ADDRCONF(NETDEV_UP): eth2: link is not ready Dec 10 10:49:15 main-menu[358]: (process:3915): udhcpc (v1.17.1) started Dec 10 10:49:15 main-menu[358]: (process:3915): Sending discover... Dec 10 10:49:15 main-menu[358]: (process:3915): Sending discover... Dec 10 10:49:15 main-menu[358]: (process:3915): Sending discover... Dec 10 10:49:15 main-menu[358]: (process:3915): udhcpc: has been called with an unknown param: leasefail Dec 10 10:49:15 main-menu[358]: (process:3915): Received SIGTERM Dec 10 10:49:15 main-menu[358]: INFO: Menu item 'netcfg' succeeded but 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. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101210154825.gr12...@caffeine.csclub.uwaterloo.ca
Re: boot parameter interface=auto can't adaptation the correct NIC
lsore...@csclub.uwaterloo.ca (Lennart Sorensen) writes: On Fri, Dec 10, 2010 at 05:45:30PM +0800, Qin Bo wrote: Dec 10 10:49:14 netcfg[3916]: INFO: eth0 is disconnected. (MII) Dec 10 10:49:14 netcfg[3916]: INFO: eth0 is not a wireless interface. Continuing. Dec 10 10:49:14 netcfg[3916]: INFO: eth1 is disconnected. (MII) Dec 10 10:49:14 netcfg[3916]: INFO: eth1 is not a wireless interface. Continuing. Dec 10 10:49:14 kernel: [ 93.801715] ADDRCONF(NETDEV_UP): eth1: link is not ready Dec 10 10:49:14 kernel: [ 93.804385] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Dec 10 10:49:15 netcfg[3916]: INFO: eth2 is disconnected. (MII) Dec 10 10:49:15 netcfg[3916]: INFO: eth2 is not a wireless interface. Continuing. Dec 10 10:49:15 kernel: [ 93.867068] ADDRCONF(NETDEV_UP): eth2: link is not ready Dec 10 10:49:15 main-menu[358]: (process:3915): udhcpc (v1.17.1) started Dec 10 10:49:15 main-menu[358]: (process:3915): Sending discover... Dec 10 10:49:15 main-menu[358]: (process:3915): Sending discover... Dec 10 10:49:15 main-menu[358]: (process:3915): Sending discover... Dec 10 10:49:15 main-menu[358]: (process:3915): udhcpc: has been called with an unknown param: leasefail Dec 10 10:49:15 main-menu[358]: (process:3915): Received SIGTERM Dec 10 10:49:15 main-menu[358]: INFO: Menu item 'netcfg' succeeded but 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. Intersting timing above: udhcpc lives less than a second? I've also got a problem with link states, but that's more an unfortunate interleaving of events, see 'udhcpc timeout with tg3' from Dec. 6. Or maybe these timestamps are wrong for some reason? -- Regards, Feri. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8762v1jxh7@tac.ki.iif.hu
boot parameter interface=auto can't adaptation the correct NIC
hi all: I use squeeze Nov 6 build iso to install, i had three network interface card, a onboard NIC and two stand alone NIC is intel e1000, and e1000 1st(eth1) is plug a cable, e1000 2nd(eth2) and onboard(eth0) is not, i want to auto configure the NIC which plug cable (at this is e1000 1st, eth1), so i write interface=auto as boot parameter, but when get ip from dhcp server, the installation can't get ip. when i configure network manually, found the ip configure onboard NIC, that is say the ip is configure on eth0 not eth1. any idea? Or may be is a bug? If i want to auto configure the NIC which plug cable, how to? best regards Qin Bo
