Hi,
I tend to agree with Ben that alternative/roaming usb serial devices
tend to be a common issue for me, especially usb to serial adapters (I
do networks, so usb to serial console ports are a big thing). Problem
for me has always been NOT to have my serial console adapter attached in
older vers
On Wed, Jan 07, 2009 at 09:32:29PM -0500, Chuck Anderson wrote:
> So perhaps we should just NULL out tmp each time before we call
> get_one_ip4_addr. I'll work up a patch.
I built and tested tested this patch against
NetworkManager-0.7.0-1.git20090102.fc10 and it fixes the problem for
me.
The
On Wed, Dec 03, 2008 at 06:45:35PM -0500, Chuck Anderson wrote:
> On Wed, Dec 03, 2008 at 06:10:08PM -0500, Dan Williams wrote:
> > Do you have a gateway in /etc/sysconfig/networking at all?
>
> No. This is the entire /etc/sysconfig/network file:
>
> NETWORKING=yes
> HOSTNAME=dustpuppy.wpi.edu
>
So funny you saw this. I just had this happened myself. It's random
though. Also happens on Ubuntu 8.10. I have a Thinpad T61, e1000,
iwl4965.
Just for some reason after coming out of suspsend Network Manager has
the networking disabled. You just reenable it and all is well. But this
isn't correct
Greetings,
This is my first post on this forum. And obviously, I am pretty novice in
GNOME and related fields.
We are trying to integrate GNOME on OMAP3430 board.
The problem is the NetworkManager (version 0.7) does not recognise the
available network interfaces (while clearly ifconfig command
On Wed, 2009-01-07 at 09:35 +0100, Christoph Höger wrote:
> Hi folks,
>
> something strange happens on my fedora 9 notebook (thinkpad r61, e1000,
> iwl4965, nm-0.7 stable rpm):
>
> randomly (at least I could not figure out how to reproduce it yet), my
> network is set to "disabled" state after a
Hi Dan,
I've noticed that when I successfully connect to a wireless network with a
non-broadcasted SSID that the applet reports:
"You are now connected to the wireless network '(none)'."
Clearly, NetworkManager knows the SSID of the network, since it was able to
look for it, and successfully con
Hi folks,
something strange happens on my fedora 9 notebook (thinkpad r61, e1000,
iwl4965, nm-0.7 stable rpm):
randomly (at least I could not figure out how to reproduce it yet), my
network is set to "disabled" state after a suspend resume cycle. Setting
to "enabled" makes things working again.
