NM_Main 1.320 report

IBM T42, Intel Pro 2200BG FC4 kernel-2.6.11-1.1177 dbus-0.31-4 hal-0.5.0.cvs20050322b-1 hal-gnome-0.5.0.cvs20050322b-1 With our without a wire plugged in, NM connects to my home and office wireless networks on boot. The office network is hidden. The context menu item Stop All Wireless

Re: NM_Main 1.320 report

On Tue, 2005-03-29 at 08:58 -0500, Bill Moss wrote: NM does not seem to be able to bring up the wired network on its own. If I do 'ifconfig eth0 up' then NM takes over and configures the wired network. Found and fixed on both HEAD and STABLE_0_3. Please test. Thanks! Dan

NM problems on fedora core 3

Greetings to the list! First of all i want to say that NM is really a great piece of software, that IMHO, does the right thing in getting linux closer to the average user. I searched for a decent way of managing connections to the ever growing number of APs that i might user with my laptop, and

Re: NM problems on fedora core 3

Ivan Blagdan wrote: Currently i use neat to connect to my home AP trough a configured eth1 interface, using wep... no problems connecting. Using NetworkManager to get a connection doesn't work, connection dosn't go past the 'connectiong to wireless network' part. Having looked trough logs it

NM_MAIN 1.321 report

Fixed. NM is now able to bring up the wired and wireless devices at boot and to freely switch between the two. Bug. NM does not seem to be able to determine the active device. My wireless device is not marked as active but it is working fine. An artifact of this bug is that hovering over the

Re: NM problems on fedora core 3

Your scan shows two AP's, yours with a signal level of -72 dBm and another one with signal level of -77 dBm. These are both weak signals and I expect if you 'watch -n2 iwlist eth1 scan' you will see these levels fluctuate a good deal. Both AP's are set to the same channel 11. This will cause

Re: NM_MAIN 1.321 report

On Tue, 2005-03-29 at 14:02 -0500, Bill Moss wrote: ipw2200-1.0.2 report. The main issue for the ipw2200 driver continues to be failures to load firmware at boot or firmware restarts. These failures do not always occur which makes them hard to trace. I saw this frequently with the 2.6.9

Re: NM problems on fedora core 3

Bill Moss wrote: Your scan shows two AP's, yours with a signal level of -72 dBm and another one with signal level of -77 dBm. These are both weak signals and I expect if you 'watch -n2 iwlist eth1 scan' you will see these levels fluctuate a good deal. Both AP's are set to the same channel 11.

NM_MAIN 1.325

I previously wrote Bug. NM does not seem to be able to determine the active device. My wireless device is not marked as active but it is working fine. An artifact of this bug is that hovering over the panel icon always shows 100% link quality. 'iwconfig eth1' shows the correct link quality.

Re: NM_MAIN 1.325

I sent Dan a patch for the 'link quality stuck at 100%' bug. -- Bill Moss Professor, Mathematical Sciences Clemson University ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list