Yep, whoever coded that part of Network Manager decided some cards
didn't support carrier detect therefore disabled the card. Even though
the cards work just fine.
Once booted, with Gutsy Ubuntu and Gutsy Xubuntu, clicking on the
network manager icon and clicking the wired network line and
I just spent a lot of time testing the nm applet on an updated (as of
20071017) Ubuntu Gutsy RC1 using a whole bunch of different network
adapters. I found that the applet won't connect automatically with a
few cards only. Big report follows and syslog is attached. I also
moved the drive to an
I performed a new install from scratch and retested starting with #3
#4. I got the same result with #1 #2 failing. Based on the logs, it
looks like it is the carrier detect issue and it affects both the tulip
and ne2k-pci drivers.
--
[feisty fawn] NetworkManager reports incorrect online
** Description changed:
--
[feisty fawn] NetworkManager reports incorrect online status
https://bugs.launchpad.net/bugs/82927
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Now indicates correctly with three computers here: Gutsy Tribe 5 on IBM
Thinkpad R31, IBM NetVista 2gHz P4, 1.2 gHz Celeron motherboard.
Cheers, Jerry Amos
--
[feisty fawn] NetworkManager reports incorrect online status
https://bugs.launchpad.net/bugs/82927
You received this bug notification
** Tags added: iso-testing
--
[feisty fawn] NetworkManager reports incorrect online status
https://bugs.launchpad.net/bugs/82927
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Solved for me with version 0.6.5-0ubuntu7
--
[feisty fawn] NetworkManager reports incorrect online status
https://bugs.launchpad.net/bugs/82927
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Mathias Hasselmann said on 2007-06-18:
Possible work arround for me: Provide some DBus interface for letting
ip-up/ip-down scripts report the online status of manually configured devices.
Would be some kind of hack, but that short term solution would drop alot of
announces NM currently cause.
The only progress I've seen is backwards. On my IBM Net Vista which
came up with Network Manager O.K. on Feisty, now on Gutsy daily builds
up through yesterday during boot Network Manager fills /var/log/syslog
with hundreds and thousands of loops of enabling and disabling either
eth2 (which I
Same for me on gutsy, NM 0.6.5
--
[feisty fawn] NetworkManager reports incorrect online status
https://bugs.launchpad.net/bugs/82927
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Isn't there a manual configuration mode, and wouldn't this mode be the
thing to choose when one uses a manually configured PPP link?
Or do I entirely misunderstand the situation?
--
[feisty fawn] NetworkManager reports incorrect online status
https://bugs.launchpad.net/bugs/82927
You received
Isn't there a manual configuration mode, and wouldn't this mode be the
thing to choose when one uses a manually configured PPP link?
Or do I entirely misunderstand the situation?
Well, yes: There is this sub-menu with ppp providers, but - at least in
my setup - NetworkManager doesn't realize
o.O
My NetworkManager (as of Feisty, current to today) has no sub-menu
dealing with PPP at all. What sub-menu are you looking at?
--
[feisty fawn] NetworkManager reports incorrect online status
https://bugs.launchpad.net/bugs/82927
You received this bug notification because you are a member of
Gutsy as of 20070618 has network manager problem with same symptoms as Feisty.
1. Network manager disables Realtek ethernet card during boot. No reason to
do that since it works fine.
2. After boot, the applet shows a red mark and passing the cursor over it says
no network connection.
3.
Can people confirm that this is still happening? I haven't had this
for a while.
Is still have the problem with manually configured PPP links. NM doesn't
detect when this link is online and has created a default route. This
causes important applications like Epiphany, Evolution, GAIM^W Pidgin,
Can people confirm that this is still happening? I haven't had this for
a while.
--
[feisty fawn] NetworkManager reports incorrect online status
https://bugs.launchpad.net/bugs/82927
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Exact same problem as Jerry Lamos since Feisty. I'm now on Gutsy, hoping
that it would solve my problem... but not yet.
Applet NetworkManager 0.6.4
/var/log/syslog
Jun 3 12:18:39 oli NetworkManager: information^Istarting...
Jun 3 12:18:39 oli NetworkManager: information^Ieth1: Driver
I have the same problem with my wireless. I am using the ndiswrapper
with my wireless adapter. More often than not when I try to connect to
my wireless network it does not get an IP address. It worked fine in
Edgy and it works fine in Windows. When I sudo dchpclient I can surf but
the network
Same problem.
I solved it by editing /etc/network/interfaces
I deleted all lines except for:
auto lo
iface lo inet loopback
Now the NetworkManager applet works correctly.
--
[feisty fawn] NetworkManager reports incorrect online status
https://bugs.launchpad.net/bugs/82927
You received this
After 7.04 full synaptic upgrade April 13,
Network Manager 0.6.4-ubuntu7
- has some harmless, extraneous entries in /etc/network/interfaces
- does dhcp and dns duties ok
- allows review of manual configuration
- does *not* report status info via bars ico; it's missing.
--
[feisty fawn]
This should have been fixed in
network-manager (0.6.4-6ubuntu7) feisty; urgency=low
* 21_manual_means_always_online.diff:
The previous version of this patch (ubuntu5) made a change to nm-applet
that would assume the state was disconnected if the device list was empty.
This didn't
Sorry, that's Bug 103258.
--
[feisty fawn] NetworkManager reports incorrect online status
https://bugs.launchpad.net/bugs/82927
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
April 13 synaptic update network-manager (0.6.4-6ubuntu7) feisty
*does not* provide connection status information as it did April 10.
See Bug 103528 for some history.
Network functions are ok, but I expect there are more gui products that
are not coming thru on my install of 7.04 with all the
Last night/this morning (two different computers, both on wired network,
both with NM reporting no connection when there was one):
Did a sudo aptitude update sudo aptitude dist-upgrade. Received
(among other things) network-manager (0.6.4-6ubuntu7) feisty. Restarted
the machines.
NM properly
NM failed for me on Apr 12th feisty update. After dist-upgrade my
network was down. /etc/init.d/network restart got the network back up
but NM now reports 'No network connection'. The network connection is a
static wired connection which NM noticed was connected yesterday, but
not today.
Current
Add another confirmation here.
Upon reboot (network-manager 0.6.4-6ubuntu6), I have full network access
that actually appears to be _managed_ fine by NM, but the NM applet
_reports_ that I'm offline.
Selecting Wired Network makes the applet disconnect/reconnect, and
then it reports fine. Even
Same here, subscribing.
--
[feisty fawn] NetworkManager reports incorrect online status
https://bugs.launchpad.net/bugs/82927
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
I can confirm that the udpates I did on April 11th, 2007 contained a
network manager update (to 0.6.4). I connect via ethernet. When booting
up Ubuntu Feisty the network manager icon has the disconnected. I have
an IP address and everything works. To resolve this I just click on the
icon and click
Latest today's build 20070411, CD Live:
1. During boot scripts network comes up O.K., finds gateway, finds remote DNS.
2. Still during boot scripts Network Manager disables the network. Dapper and
Edgy don't do that. They Just Work.
3. After boot completes, Network Manager says No connection.
My network connection works, and I had no errors in feisty beta, but
after downloading new updates through update manger today, network
manger .6.4 displays no connection icon, says no connection when mouse
is over it, and will not display any network information. However, the
network connection
The same problem here, after updating on 10/04/2007 at 19:30 (aprox.),
using Fiesty beta Network manager displays no conection manager.
Although i have two machines running Fiesty, one desktop pc and a IBM
t40 laptop, the wire connections are not recognized anymore, wireless
connection seems to
Same here. Afer today's update (10/04/2007). I have been using feisty
for a few weeks and never had this problem. I have internet access by
ethernet tough, with out having to to any configuration. After
deactivating network in nm and reactivating, the no connection sign
goes away.
--
[feisty
On my Edgy box, NM doesn't take control of any adapter interface
**unless** that interface has the auto in front of it in
/etc/networking/interfaces. I've statically configured the wifi card in
my Edgy box, and NM ignores the entire interface as a result. Does
removing the
auto eth0
from
Like Olivier Bornet I found the same kernel-related nm-applet bug.
(Gnome nm-applet 0.6.3)
When running 2.6.20-6 on edgy, network-manager works perfectly on my IBM T43p
(with atheros), including WPA.
When running 2.6.20-12/13 on edgy, network-manager stops working at all - but I
can get an
I'm getting the exact same feedback as bytesmythe. However networking
works on my home WEP encrypted network with NM. At my school, it does
not connect as said--dhclient works. I'm not an expert on this, but for
some reason I think it's a bug with multiple APs of the same SSID. I
don't know.
Wicd
NM works perfectly with:
Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
Connections fail when the signal is weaker than about 40%. As long as it's
~50+% though, it's perfect. It has worked perfectly since Dapper.
Now if only the wired Marvell card had better drivers
I'm having the same type of problem with NM. When I click on the icon,
it correctly displays a list of available wireless networks, but when I
select one of them, it attempts to connect but fails.
If, while it is attempting to connect, I pop open a terminal and run
dhclient (which will connect
I googled feisty fawn network manager and it brought me here. Reading the
dialog above, I think my comments might be relevant. I too am totally
frustrated with Network Manager. It converts a static IP to the zero configure
IP of 169.x.x.x the instant the NIC patch cable is disconnected.
I have the same kind of problem on a MacBook Pro.
With edgy, all is ok. Network Manager handle perfectly the wired and
wireless connections, even with WPA. :)
Now, because I have some problems to do recording with the microphone,
I'm trying to use the feisty kernel with the edgy installation.
On 20070322 builds, Ubuntu and Kubuntu boot up with No network
connection. Left click on the icon, click to activate, and it does.
Since it comes right up, there was no technical reason to de-activate
the network during boot as shown in the syslogs above.
Xubuntu Feisty, Dapper, Simply Mepis,
Sorry, Jerry. Would you mind updating the bug report's description, to
be a bit more accurate? I was just hoping to make this report easier
for others to find, but I guess I didn't entirely understand the
problems at hand. Thanks. :)
--
[feisty fawn] NetworkManager reports incorrect online
** Description changed:
- feisty fawn herd 3 download 1 February 2007
- After bootup there was a message about a crash, apparently add/remove
program?
- Going on:
+ Description edited 3/17/07 by Jerry Amos, originator:
- Network manager icon on top line, right side just before speaker volume
** Changed in: network-manager (upstream)
Status: Unknown = Unconfirmed
--
[feisty fawn] NetworkManager reports incorrect online status
https://launchpad.net/bugs/82927
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Summary changed:
- feisty fawn no network connection
+ [feisty fawn] NetworkManager reports incorrect online status
--
[feisty fawn] NetworkManager reports incorrect online status
https://launchpad.net/bugs/82927
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I see the title of the bug has changed.
** Not only does Network Manager report incorrect status, during boot
Network Manager itself disabled a perfectly running eth0, complaining
something about no carrier detect?
Network Manager should not disable perfectly functioning hardware, a
ordinary
45 matches
Mail list logo
