[Bug 94095] Re: Ethernet interface not configured at boot time
*** This bug is a duplicate of bug 83143 *** https://bugs.launchpad.net/bugs/83143 Gutsy Tribe 5 is also working fine for me. My wired ethernet interface is up when I'm logged in the GUI. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
*** This bug is a duplicate of bug 83143 *** https://bugs.launchpad.net/bugs/83143 Oops, I spoke too soon, after yesterdays MASSIVE Ubuntu Tribe 5 (6?) upgrade, Network Mangler does not configure the network on one of my computers. I have to manually click on the Network Mangler icon. If Network Mangler can connect fine when I click on the icon, why can't the programmers get it to connect during boot?? I can (have in times past) supplied /var/log/syslog, dmesg, anything anyone working on this bug wants to see. Jerry -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
*** This bug is a duplicate of bug 83143 *** https://bugs.launchpad.net/bugs/83143 Jerry, you are commenting on a duplicate bug report of a bug which is marked as Invalid. Please submit a new bug report about network-manager and include the output of 'dmesg' and '/var/log/daemon.log' after booting your system. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
*** This bug is a duplicate of bug 83143 *** https://bugs.launchpad.net/bugs/83143 Gutsy Tribe 5 (6) configures my network interfaces properly. Feisty and earlier Gutsy Tribes did not. Jerry -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
*** This bug is a duplicate of bug 83143 *** https://bugs.launchpad.net/bugs/83143 [Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
*** This bug is a duplicate of bug 83143 *** https://bugs.launchpad.net/bugs/83143 folkoy, thanks for the dmesg output. So the problem is the missing carrier detect (link beat), duplicating to bug 83143. ** This bug has been marked a duplicate of bug 83143 does not automatically start the wired connection due to missing link beat -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
*** This bug is a duplicate of bug 83143 *** https://bugs.launchpad.net/bugs/83143 Thanks, BTW after a fresh install of latest Debian Etch 4.0, it also show the exact same problem. I assume the fix will also be pushed to Debian. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
It seems to me that my Dell D620 has similar problems. I typically use it wireless at home, suspend, dock it at work, and resumes. The network icon will then show up as if the wired network is working, but eth0 will not have an IP address. Clicking the 'wired network' item in the menu (twice?) fixes the problem. I wonder if it is just the DHCP server that is slow to respond, and/or that the icon displays as connected to avahi being up and running? (I.e. eth0:avah is up). -k -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
Nice, thanks for checking this again. So this seems to be fixed in the latest version. ** Changed in: network-manager (Ubuntu) Status: Unconfirmed = Fix Released -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
sorry, this bug is NOT fixed. Please re open the bug -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
Is there someone with enough privilege to re-open the bug status to confirmed? The problem is NOT fixed. Do I need to re-open a new bug with same description? ** Changed in: network-manager (Ubuntu) Status: Fix Released = Unconfirmed -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
bug is NOT fixed. Changing the bug status to unconfirmed. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
Folkoy, maybe your network card does not support link beat detection. Can you please attach the output of dmesg | grep link ? ** Changed in: network-manager (Ubuntu) Status: Unconfirmed = Needs Info -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
Hi Martin, That network card has been working without problem with Ubuntu 6.06 without a glitch and with many different Linux distro. It's only in Feisty that this problem occurs. Here is the output; $ dmesg | grep link [ 23.772183] audit: initializing netlink socket (disabled) Did you compare the last 4 files sent in my replies above aemon.log, daemon_after.log messages messages_after ? These logs are capture immediately after bootup and then re-capture after pressing on the networking applet then wired Network. What else would be usefull for you? thanks -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
Mark, can you please attach your /etc/network/interfaces and /var/log/daemon.log (after a fresh boot) here? -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 94095] Re: Ethernet interface not configured at boot time
I will be happy to, but I won't be able to until tonight when I get home to that computer. To get that info for you, I guess I need to type those commands in the terminal, right? On 4/16/07, Martin Pitt [EMAIL PROTECTED] wrote: Mark, can you please attach your /etc/network/interfaces and /var/log/daemon.log (after a fresh boot) here? -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a direct subscriber of the bug. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 94095] Re: Ethernet interface not configured at boot time
No commands needed. Just attach the 2 files that Martin requested. =Robert On 4/16/07, Mark Anton [EMAIL PROTECTED] wrote: I will be happy to, but I won't be able to until tonight when I get home to that computer. To get that info for you, I guess I need to type those commands in the terminal, right? On 4/16/07, Martin Pitt [EMAIL PROTECTED] wrote: Mark, can you please attach your /etc/network/interfaces and /var/log/daemon.log (after a fresh boot) here? -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a direct subscriber of the bug. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a direct subscriber of the bug. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
In attachement are 4 files. deamon.log (/var/log/daemon.log) and messages (/var/log/messages) take after a clean bootup. I recapture the same file after clicking on the networking applet and on the wired connection so that Feisty connect to the network. If you do a diff of the two logs files you'll see intersting things that occured. There was some dhcdbd error messages in the /var/log/messages that appears after clicking the network applet. Before booting the PC, the content of both /var/log/messages and daemon.log was erased to eliminate previous boot noise... $ diff daemon.log daemon_after.log Two lines were a bit scary; 1) eth0: Driver 'dmfe' does not support carrier detection. ^IYou must switch to it manually 2) Deactivating device eth0. Then doing ; $ diff messages messages_after What's that redhat in the path? 1) Apr 16 18:20:58 ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason The 4 files are in attachement. The interface file is already attached in a previous comment above. ** Attachment added: daemon.log http://librarian.launchpad.net/7338121/daemon.log -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
** Attachment added: daemon_after.log http://librarian.launchpad.net/7338122/daemon_after.log -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
** Attachment added: messages http://librarian.launchpad.net/7338123/messages -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
** Attachment added: messages_after http://librarian.launchpad.net/7338137/messages_after -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 94095] Re: Ethernet interface not configured at boot time
Lo and behold, I have rebooted twice-- and it is now accessing the internet by itself. Amazing. If you need any more information from me, please ask. I want to help. I really appreciate what you guys are doing there. Mark Anton Stockton, Ca On 4/16/07, Mark Anton [EMAIL PROTECTED] wrote: Here are the attatched files. Hope this helps. Thanks, Mark Anton Stockton On 4/16/07, Martin Pitt [EMAIL PROTECTED] wrote: Mark, can you please attach your /etc/network/interfaces and /var/log/daemon.log (after a fresh boot) here? -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a direct subscriber of the bug. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
forgot to mention in my reply above that the system got many package updated today and the networking problem is still there. What other information might be usefull to you for debugging? thanks -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 94095] Re: Ethernet interface not configured at boot time
Hi, Today, my computer logged on to the internet by itself. It happened after I changed the setting manually. I noticed suddenly that it was now giving me the option to do that when I move the mouse cursor over the double-monitor icon. I kept it on the dchp setting. I rebooted a couple of times, and there internet was there on its own. Mark Anton On 4/16/07, folkoy [EMAIL PROTECTED] wrote: forgot to mention in my reply above that the system got many package updated today and the networking problem is still there. What other information might be usefull to you for debugging? thanks -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a direct subscriber of the bug. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
My previous comments stating that this bug was fixed, were premature. Apparently a recent update has caused the issue to return. I have the latest updates, and the original problem has re-appeared. Additional information, which may require separate bug reports: 1) my Gigabit PCMCIA card, a Trendnet TEG-PCBUSR, now comes up in 10MB mode. This previously worked reliably in feisty at 100MB and 1000MB. It always woked at 100MB and 1000MB in Edgy. 2) my 802.11g Netgear PCMCIA wireless card no longer comes up properly at boot time. Rebooting sometimes allows the card/network to come up. This also worked reliably in Edgy. I will provide more details on issues 1 and 2 above, when I can do more testing. Robert -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 94095] Re: Ethernet interface not configured at boot time
Thanks for the information. My internet problem has never gone away. I still have to manually click on the wired network at the double-monitor icon. This problem still needs to be addressed, and we can only hope they do so. Other aspects of Feisty Fawn are very good. Mark Anton Stockton, Ca On 4/11/07, Robert Clark [EMAIL PROTECTED] wrote: My previous comments stating that this bug was fixed, were premature. Apparently a recent update has caused the issue to return. I have the latest updates, and the original problem has re-appeared. Additional information, which may require separate bug reports: 1) my Gigabit PCMCIA card, a Trendnet TEG-PCBUSR, now comes up in 10MB mode. This previously worked reliably in feisty at 100MB and 1000MB. It always woked at 100MB and 1000MB in Edgy. 2) my 802.11g Netgear PCMCIA wireless card no longer comes up properly at boot time. Rebooting sometimes allows the card/network to come up. This also worked reliably in Edgy. I will provide more details on issues 1 and 2 above, when I can do more testing. Robert -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a direct subscriber of the bug. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
This issue was apparently fixed through one of the feisty updates. I have not had any Ethernet configuration at startup up issues for over a week now. I consider this bug Fixed. Thanks Ubuntu Team! -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 94095] Re: Ethernet interface not configured at boot time
Hi Robert, My Feisty just got update few minutes ago (april 10). I rebooted and the ethernet connection was not setup after reboot. I had to click again on the small network applet in toolbar and select Wired Connection. I tried to change the config of the network interface in Network Settings to enable Roaming mode. I rebooted and still the network interface is not enabled after I logged in. So I disabled the Roaming mode, rebooted and did the following commands; Immediately after reboot here is the state of my eth0; $ sudo ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:50:2C:08:B9:02 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:46 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13852 (13.5 KiB) TX bytes:1216 (1.1 KiB) Interrupt:19 Base address:0x9800 Then I tried to bringup and got the following message; $ sudo ifup eth0 ifup: interface eth0 already configured Then I tried to bring down and bring back up and it worked; $ sudo ifdown eth0 There is already a pid file /var/run/dhclient.eth0.pid with pid 4078 killed old client process, removed PID file Internet Systems Consortium DHCP Client V3.0.4 ... $ sudo ifup eth0 There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:50:2c:08:b9:02 Sending on LPF/eth0/00:50:2c:08:b9:02 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20 DHCPOFFER from 192.168.0.175 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.0.175 bound to 192.168.0.100 -- renewal in 65270 seconds. At that point the inerface is fine and up although the applet still beleive the network interface is still off (this was expected). Here is my interface file; ~$ sudo cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface iface eth0 inet dhcp auto eth0 This bug is still not fixed. Are you ok to re-open the bug? Is there any test I can do on my machine or any files I need to check? What should I do to re-open the bug, can we transition the bug from fixed to non fixed. I guess the priority is at least medium if not high. thanks Steve On Tue, 2007-10-04 at 15:28 +, Robert Clark wrote: This issue was apparently fixed through one of the feisty updates. I have not had any Ethernet configuration at startup up issues for over a week now. I consider this bug Fixed. Thanks Ubuntu Team! -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 94095] Re: Ethernet interface not configured at boot time
Hi Ubuntu Team, I have the April 10 updates. Unfortunately, I still need to manually click on the double-monitor icon and select wired network every time I boot up my Ubuntu 7.04. Older versions didn't do this. Is it going to be fixed in an update? Mark Anton On 4/10/07, folkoy [EMAIL PROTECTED] wrote: Hi Robert, My Feisty just got update few minutes ago (april 10). I rebooted and the ethernet connection was not setup after reboot. I had to click again on the small network applet in toolbar and select Wired Connection. I tried to change the config of the network interface in Network Settings to enable Roaming mode. I rebooted and still the network interface is not enabled after I logged in. So I disabled the Roaming mode, rebooted and did the following commands; Immediately after reboot here is the state of my eth0; $ sudo ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:50:2C:08:B9:02 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:46 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13852 (13.5 KiB) TX bytes:1216 (1.1 KiB) Interrupt:19 Base address:0x9800 Then I tried to bringup and got the following message; $ sudo ifup eth0 ifup: interface eth0 already configured Then I tried to bring down and bring back up and it worked; $ sudo ifdown eth0 There is already a pid file /var/run/dhclient.eth0.pid with pid 4078 killed old client process, removed PID file Internet Systems Consortium DHCP Client V3.0.4 ... $ sudo ifup eth0 There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:50:2c:08:b9:02 Sending on LPF/eth0/00:50:2c:08:b9:02 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20 DHCPOFFER from 192.168.0.175 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.0.175 bound to 192.168.0.100 -- renewal in 65270 seconds. At that point the inerface is fine and up although the applet still beleive the network interface is still off (this was expected). Here is my interface file; ~$ sudo cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface iface eth0 inet dhcp auto eth0 This bug is still not fixed. Are you ok to re-open the bug? Is there any test I can do on my machine or any files I need to check? What should I do to re-open the bug, can we transition the bug from fixed to non fixed. I guess the priority is at least medium if not high. thanks Steve On Tue, 2007-10-04 at 15:28 +, Robert Clark wrote: This issue was apparently fixed through one of the feisty updates. I have not had any Ethernet configuration at startup up issues for over a week now. I consider this bug Fixed. Thanks Ubuntu Team! -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a direct subscriber of the bug. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
Today's update seems to have fixed this for me. However, altho now ifconfig show all the interfaces as UP, the network icon says it's disabled. And if I enable it, network goes down. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
I'm having a similar problem. I have to manually click on the wired network option on the networking applet (double-monitor icon) to get my ATT DSL internet to get recognized. This was not a problem with the previous release of Ubuntu, only Feisty. I hope this gets fixed soon! My wired connection is set for dhcp. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
Using Feisty Beta I have same problem. The PC has a single Ethernet card eth0 using DHCP. When Feisty boots, the eth0 interface is not enabled. The first time I log on after each reboot, I have to click on the small networking applet and click on wired connection. Then the eth0 is braught up and work fine. The problem is that it should have been enabled by default during the boot of Ubuntu Feisty instead of requiring human intervention after each reboot. I checked in the networking configuration tool under GNOME and KDE don't see any misconfiguration for the networking and interfaces. This was not a problem under dapper. This will confuse new Ubuntu users if their interface is not ON by default. any suggestions? thanks -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
I have a similar issue that might confirm this bug: After upgrading from dapper to feisty beta, my network interfaces with static IP assigned will come up but no IP will be configured. Currently, I have 3 ethernet interfaces, 2 static IP and 1 DHCP. Starting in recovery (single) mode, all interfaces come up fine. Starting normally, only the dhcp interface will have an IP assigned until I manually restart networking with /etc/init.d/networking restart, then all interfaces come up as they should. Booting without splash shows no obvious errors, nor do the dmesg logs. I don't see anything wrong in the init scripts: [EMAIL PROTECTED]:/etc# find /etc/ -lname *networking* /etc/rcS.d/S40networking /etc/network/interfaces hasn't changed: auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.32.1 netmask 255.255.255.0 auto eth1 iface eth1 inet static address 192.168.45.254 netmask 255.255.255.0 auto eth2 iface eth2 inet dhcp I tried disabling (and even removing completely) the firewall (shorewall) and disabling avahi with no success. My test hardware is also pretty old (Dell Optiplex GX150) -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
I do not see this problem if fsck runs at boot time. This leads me to believe that this is a timing problem at boot time. I'm aware that changes were made to improve boot times in feisty. Since I never saw this problem in edgy, suspect the boot optimization(s) in feisty is causing the problem. I think the automatic fsck after 30 boots, gives the ethernet setup enough time to complete before other network steps are done. Others feisty users may not see this, because they are running on newer/faster hardware. Portion of /proc/cpuinfo cpu MHz : 746.793 cache size : 256 KB bogomips: 1494.79 -- Ethernet interface not configured at boot time https://launchpad.net/bugs/94095 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
** Changed in: Ubuntu Sourcepackagename: None = network-manager -- Ethernet interface not configured at boot time https://launchpad.net/bugs/94095 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
