hi, upgraded kubuntu 9.10 64-bit , works far except wireless connectivity. wep network @ home works, university network uses wpa2 peap. while took me few days figure out how connect while using jaunty, did end connecting network (i had select each ssl cert manually until found right one, /etc/ssl/certs/thawte_premium_server_ca.pem... why can windows , os x auto-select certificate ubuntu can't?), cannot connect @ using same settings before (same ssl cert, same username/password, etc.), not same network manager since rewritten in kubuntu 9.10. thought i'd downgrade knetworkmanager old version back, , did adding official jaunty packages in /etc/apt/sources.list, installed knetworkmanager, while let me set new connections preferences, stores these connection preferences never uses them (ie, never touches network interface). running root didn't help.
thought downgrade backend too, installed old 0.7 network-manager package , tried using knetworkmanager, didn't work either.
removed jaunty packages source, reupgraded karmic version, , i'm square one: wep network works, wpa doesn't. tried installing wicd, couldn't connect home wireless (wep) network @ (dhclient times out), didn't try on wpa network yet. it's weird because can connect home network fine command line (ifconfig eth2 down, iwconfig eth2 essid myneworkname, iwconfig eth2 channel 11, iwconfig eth2 key mywepkey, ifconfig eth2 up, dhclient eth2).
i'm running kubuntu 9.10 64-bit on macbook pro 5,3 restricted broadcom sta drivers enabled. should do?
ifconfig:
iwconfig:code:eth0 link encap:ethernet hwaddr 00:26:b0:df:82:16 inet6 addr: fe80::226:b0ff:fedf:8216/64 scope:link broadcast running multicast mtu:1500 metric:1 rx packets:29846 errors:0 dropped:0 overruns:0 frame:0 tx packets:6503 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 rx bytes:7329261 (7.3 mb) tx bytes:742956 (742.9 kb) interrupt:28 base address:0x6000 eth2 link encap:ethernet hwaddr 00:26:bb:08:85:f2 inet addr:192.168.0.121 bcast:192.168.0.255 mask:255.255.255.0 inet6 addr: fe80::226:bbff:fe08:85f2/64 scope:link broadcast running multicast mtu:1500 metric:1 rx packets:338629 errors:1 dropped:0 overruns:0 frame:44856 tx packets:286534 errors:30 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 rx bytes:105654337 (105.6 mb) tx bytes:30399785 (30.3 mb) interrupt:22 lo link encap:local loopback inet addr:127.0.0.1 mask:255.0.0.0 inet6 addr: ::1/128 scope:host loopback running mtu:16436 metric:1 rx packets:9676 errors:0 dropped:0 overruns:0 frame:0 tx packets:9676 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 rx bytes:601560 (601.5 kb) tx bytes:601560 (601.5 kb)
lspci | grep networkcode:lo no wireless extensions. eth0 no wireless extensions. eth2 ieee 802.11abgn essid:"<my home network's essid>" nickname:"" mode:managed frequency:2.462 ghz access point: 00:15:e9:7b:2f:ba bit rate=54 mb/s tx-power:32 dbm retry min limit:7 rts thr:off fragment thr:off power managementmode:all packets received link quality=5/5 signal level=-51 dbm noise level=-94 dbm rx invalid nwid:0 rx invalid crypt:352 rx invalid frag:0 tx excessive retries:3 invalid misc:1 missed beacon:0 vboxnet0 no wireless extensions. pan0 no wireless extensions.
is there can do?code:00:00.0 host bridge: nvidia corporation mcp79 host bridge (rev b1) 00:00.1 ram memory: nvidia corporation mcp79 memory controller (rev b1) 00:03.0 isa bridge: nvidia corporation mcp79 lpc bridge (rev b3) 00:03.1 ram memory: nvidia corporation mcp79 memory controller (rev b1) 00:03.2 smbus: nvidia corporation mcp79 smbus (rev b1) 00:03.3 ram memory: nvidia corporation mcp79 memory controller (rev b1) 00:03.4 ram memory: nvidia corporation device 0a98 (rev b1) 00:03.5 co-processor: nvidia corporation mcp79 co-processor (rev b1) 00:04.0 usb controller: nvidia corporation mcp79 ohci usb 1.1 controller (rev b1) 00:04.1 usb controller: nvidia corporation mcp79 ehci usb 2.0 controller (rev b1) 00:06.0 usb controller: nvidia corporation mcp79 ohci usb 1.1 controller (rev b1) 00:06.1 usb controller: nvidia corporation mcp79 ehci usb 2.0 controller (rev b1) 00:08.0 audio device: nvidia corporation mcp79 high definition audio (rev b1) 00:09.0 pci bridge: nvidia corporation mcp79 pci bridge (rev b1) 00:0a.0 ethernet controller: nvidia corporation mcp79 ethernet (rev b1) 00:0b.0 ide interface: nvidia corporation mcp79 sata controller (rev b1) 00:0c.0 pci bridge: nvidia corporation mcp79 pci express bridge (rev b1) 00:15.0 pci bridge: nvidia corporation mcp79 pci express bridge (rev b1) 00:16.0 pci bridge: nvidia corporation mcp79 pci express bridge (rev b1) 02:00.0 vga compatible controller: nvidia corporation g96 [geforce 9600m gt] (rev a1) 04:00.0 network controller: broadcom corporation bcm4322 802.11a/b/g/n wireless lan controller (rev 01) 05:00.0 firewire (ieee 1394): agere systems fw643 pci express1394b controller (phy/link) (rev 07)otherwise i'll have downgrade jaunty network connection back. unless there way downgrade networking components? cool.
i added wicd ppa (deb http://apt.wicd.net karmic extras) , wicd working home wireless connection. try connect wpa network tomorrow wicd , report
Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Networking & Wireless [kubuntu] Cannot connect to WPA2 PEAP after Karmic upgrade
Ubuntu
Comments
Post a Comment