*** 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 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
*** 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
*** 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
*** 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
*** 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
*** 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
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
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
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
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
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
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
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
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
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
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
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
** 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
** 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.
--
** 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.
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
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
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,
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
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
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
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
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
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
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
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
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
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
** 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
35 matches
Mail list logo
