*** This bug is a duplicate of bug 83143 ***
https://bugs.launchpad.net/bugs/83143
Wired network is disabled on this system on 7.04, 7.10, and now Hardy
Alpha 8.04.
The "Network Manager" disables the perfectly running wired network card:
Ethernet controller [0200]: Realtek Semiconductor Co.
*** This bug is a duplicate of bug 83143 ***
https://bugs.launchpad.net/bugs/83143
This problem has never been fixed in Ubuntu 7.04 but it's fixed in 7.10.
I hope the fix would be backported into the impacted previous release...
--
Wired network not enabled upon system boot
https://bugs.laun
*** This bug is a duplicate of bug 83143 ***
https://bugs.launchpad.net/bugs/83143
Is there a reason this bug has been closed? I have been searching the
web for an hour or so and I am finding a substantial number of people
that are stuck with this problem.
The symptoms seem to be consistent
*** 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.]
--
Wired network not enabled upon system boot
https://bugs.launchpad.net/bugs/97278
You received this bug notification bec
*** This bug is a duplicate of bug 83143 ***
https://bugs.launchpad.net/bugs/83143
I'll report that I also see nothing in dmesg or /var/log/messages when I
unplug and replug the ethernet cable.
[EMAIL PROTECTED]:~$ dmesg | grep -A5 -B5 link
[ 18.461528] TCP bind hash table entries: 65536 (
*** This bug is a duplicate of bug 83143 ***
https://bugs.launchpad.net/bugs/83143
Aha... that's what I get for skimming. Sounds like it.
--
Wired network not enabled upon system boot
https://bugs.launchpad.net/bugs/97278
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 83143 ***
https://bugs.launchpad.net/bugs/83143
I guess you mean "a duplicate of #83143"?
Well if you read the comment by jerrylamos
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/83143/comments/7
he states that he can connect by clicking t
*** This bug is a duplicate of bug 83143 ***
https://bugs.launchpad.net/bugs/83143
Are we sure this is a duplicate of #97278? I don't see anyone in that
bug saying that they can connect by simply selecting Wired Network from
the network-manager dropdown.
--
Wired network not enabled upon sys
*** This bug is a duplicate of bug 83143 ***
https://bugs.launchpad.net/bugs/83143
I also have this problem. I had the same results as Skou:
$ dmesg | grep link
[ 21.037301] audit: initializing netlink socket (disabled)
but I'd like to note, additionally, that removing and replugging the
e
*** This bug is a duplicate of bug 83143 ***
https://bugs.launchpad.net/bugs/83143
** This bug has been marked a duplicate of bug 83143
does not automatically start the wired connection due to missing link beat
--
Wired network not enabled upon system boot
https://bugs.launchpad.net/bugs/
After pulling out and plugging in the ethernet cable:
$ dmesg | grep link
[ 26.182585] audit: initializing netlink socket (disabled)
--
Wired network not enabled upon system boot
https://bugs.launchpad.net/bugs/97278
You received this bug notification because you are a member of Ubuntu
Bugs, w
For the record, if dmesg does not show link detection, this is a
duplicate of bug 83143.
--
Wired network not enabled upon system boot
https://bugs.launchpad.net/bugs/97278
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
This works well for me and other people, so the reason might be that
your hardware setup does not have a link beat. We need to find a
solution for that.
Just to check this theory, can you please do the following:
- pull out the ethernet cable
- plug it back in
- copy&paste the output of "dm
I can confirm this bug.
I just upgraded to Feisty yesterday (23/4 - 07) and now the network is off per
default.
Steps to reproduce:
1. Boot up computer.
2. Login.
3. Notice that network is off.
** Changed in: network-manager (Ubuntu)
Status: Unconfirmed => Confirmed
--
Wired network not
This problem still occurs with Feisty completely updated, post release.
NM should be smart enough to know that if there are no wireless
connections available, it should automatically try to connect with the
wired connections.
For now I have uninstalled NM and things work just fine (network is
aut
I have a similar problem on my machines (I have 7.04 on two machines).
Upon boot, I run "/etc/init.d/networking restart" from the command line
(Kirk: use --F1 to get a virtual terminal) to get everything
working OR do as Kirk says (but I use NIS, so logging in as a user other
than root is a bit mo
Here's ifconfig output before I use the applet to enable networking, and
after it reports that the network is now enabled (after my manual
intervention):
Before:
eth0 Link encap:Ethernet HWaddr 00:80:C6:FD:2A:ED
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX pack
Is there a way to configure Network Manager to always try the wired
network? Or perhaps a command line utility that allows me to enable the
wired network?
My box doesn't have wireless capabilities at all, but right now I have
to actually log in to Gnome and use the tray icon to get my network up
Thanks for your bug report.
** Changed in: network-manager (Ubuntu)
Sourcepackagename: gnome-network => network-manager
Importance: Undecided => Medium
--
Wired network not enabled upon system boot
https://launchpad.net/bugs/97278
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
19 matches
Mail list logo
