I did get network manager work, but do have to restart network-manager every time I reboot.
Code:sudo /etc/init.d/NetworkManager restart
I did get network manager work, but do have to restart network-manager every time I reboot.
Code:sudo /etc/init.d/NetworkManager restart
Mike: "The hardest questions in life are the ones worth answering"
Also, the menu entry Edit Connections does nothing for me.
Mike
Mike: "The hardest questions in life are the ones worth answering"
After all upgrades and nm 0.7 installation I am writing this post from my wireless card AR5418 using wpa-2 on MacBook 2.1 amd64 2.6.24-4 R7.
1. Using nm-0.7 I choose wpa-2 and typed my passwphrase.
2. I checked /etc/networh/interfaces and everything was ok
3. Re-open nm-0.7 and all settings was still there registered. On nm-0.6 all settings didn't get registered after closing it.
4. Testing with dinamically dhcp could not connect to the network.
5. Change to static dhcp typing my IP address, netmask and gateway could finally be connected to the wireless network.
Note.: No crashes noticeable with nm-0.7 on my system.
Last edited by mabovo; February 13th, 2008 at 06:18 PM.
I don't see this behaviour (iwl3945). After a reboot, nm-applet found my card, then segfaulted. After restarting nm-applet it asked for my WPA2 passphrase, and from then on has worked exactly as NM 0.65.
lshw output:
Code:*-network description: Wireless interface product: PRO/Wireless 3945ABG Network Connection vendor: Intel Corporation physical id: 0 bus info: pci@0000:03:00.0 logical name: eth2 version: 02 serial: <snip> width: 32 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless configuration: broadcast=yes driver=iwl3945 ip=192.168.0.150 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
Last edited by 23meg; January 25th, 2008 at 11:30 AM. Reason: edited out serial
Remember: if your problem is not described on a Launchpad bug, it can only be fixed by accident!
I have the same problems that Mike mentioned.
Think carefully before executing commands containing "rm", especially "sudo rm -rf ", if you require more information concerning this matter, read this.
I am an experimenter, give me the most stable OS and I can make it unstable in a few hours.
C == seriously fast == FTW!
Working without problems with atheros AR5212/AR5213 chipset (D-Link AirPlus DWL-G520)
"Let's nobody be dead today----Looks very bad on my report" One of my favourite lines from AVATAR
Linux User#395230
Ubuntu User# 13498
Working fine with WPA2 on IPW2200; no crashes or drops so far. lshw output:
Code:description: Wireless interface product: PRO/Wireless 2200BG Network Connection vendor: Intel Corporation physical id: 5 bus info: pci@0000:03:05.0 logical name: eth1 version: 05 serial: <snip> width: 32 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ipw2200 driverversion=1.2.2kmprq firmware=ABG:9.0.2.6 (Mar 22 2005) ip=192.168.10.3 latency=64 maxlatency=24 mingnt=3 module=ipw2200 multicast=yes wireless=IEEE 802.11g
Last edited by 23meg; January 25th, 2008 at 11:26 AM.
Working fine here too. Network manager showed up after I did "/etc/init.d/NetworkManager restart".
I use WPA. lshw output:
Code:*-network:0 description: Wireless interface product: RT2500 802.11g Cardbus/mini-PCI vendor: RaLink physical id: 4 bus info: pci@0000:05:04.0 logical name: wmaster0 version: 01 serial: <snip> width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list logical ethernet physical wireless configuration: broadcast=yes driver=rt2500pci ip=192.168.1.101 latency=64 module=rt2500pci multicast=yes wireless=IEEE 802.11g
Last edited by 23meg; January 25th, 2008 at 11:27 AM. Reason: edited out serial
Bookmarks