Strona 1 z 1
[solved] polaczenia z AP dopiero po kilku nieudanych probach
: 01 lip 2009, 14:14
autor: kraken
problem z polaczeniem do wifi.
witam
mam dosc dziwny problem.
ubuntu laczy mi sie z wifi dopiero po kilku probach. kompletnie nic w tym czasie nie zmienaim w ustawieniach, poprostu klikam na ikone polaczen i klikam ponownie na swoja siec. czasasmi laczy sie po 5 probach, nieraz za pierwszym. przewaznie jednak sa problemy.
da sie wyczuc RANDOMA.
mam takze zasintalawana viste[dualboot], na ktorej ten problem nigdy nei istnial, zawsze sie laczyl za pierwszym razem.
karta oparna na broadcomie, router dlink 524
jakies sugestie?
Odp: polaczenia z AP dopiero po kilku nieudanych probach
: 01 lip 2009, 20:48
autor: Semerchet
Ja tylko zgaduje. Może stery do luftu. Wrzuć na wszelki wypadek:
może ktoś coś sobie przypomni, albo coś w google znajdziemy.
Odp: polaczenia z AP dopiero po kilku nieudanych probach
: 01 lip 2009, 21:26
autor: kraken
00:0c.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2)
00:0d.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2)
00:12.0 VGA compatible controller: nVidia Corporation GeForce 7150M (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
02:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
02:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
02:05.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
02:05.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
02:05.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)
03:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 02)
domyslam sie ze chodzilo ci o: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 02)
szukalem duzo na necie o tej karcie, okazuje sie ze bardziej gownianej nie moglem dostac ale coz.....zyc trzeba dalej.
zeby ja zainstalowac musialem sciagac jakies paczki oraz bawic sie fwcutterem. ale pozatym laczeniem sie .....dziala calkiem ok.
jeszcze mala wskazowka: mialem kiedys inny network manager, zdaje sie wicd [chodzilo poprawnie] ale z roznych wzgledow potrzebuje tego z gnoma.
Odp: polaczenia z AP dopiero po kilku nieudanych probach
: 01 lip 2009, 21:38
autor: Semerchet
okazuje sie ze bardziej gownianej nie moglem dostac
Racja. Ale jest nadzieja. Podam ci dwa link:
http://djkaos.wordpress.com/2008/10/25/ ... ta-driver/
http://www.esdebian.org/wiki/driver-ofi ... 21-bcm4322
Przeanalizuj je.
Te stery z repo chyba wogóle nie działają. b43 będziesz musiał wysłać na emeryturę. To też - ndiswrapper ssb bcm43xx b43legacy.
PS.
http://www.broadcom.com/support/802.11/linux_sta.php
W paczkach znajdziesz instrukcję.
Odp: polaczenia z AP dopiero po kilku nieudanych probach
: 01 lip 2009, 23:24
autor: kraken
zrobilem to wszystko od A do Z z wielkim sukcesem i taki oto efekt:
po pierwszym restarcie wifi polaczyla sie automatycznie, cud miod. po czym razlaczylem siec. zeby ponownie sie zalaczyc musialem 3 razy laczyc z wifi.
zrobilem drugi restart. tym razem juz nie polaczyla sie automatycznie. ale za to wskoczyla juz za pierwszym razem z palucha.
[jezeli laczy sie to wskakuje bardzo szybko, jezeli sie ma nie polaczyc to te kropki sie ruszaja dluzszy czas 20-sek po czym wyskakuje komunikat o rozlaczeniu]
czyli ciezko powiedziec czy cos lepiej chodzi....
moze cos w logach bedzie ciekawego? tylko ktore to moga byc?
Odp: polaczenia z AP dopiero po kilku nieudanych probach
: 02 lip 2009, 00:05
autor: Semerchet
mialem kiedys inny network manager, zdaje sie wicd [chodzilo poprawnie] ale z roznych wzgledow potrzebuje tego z gnoma
Może tu powinniśmy szukać błędu??
Odp: polaczenia z AP dopiero po kilku nieudanych probach
: 02 lip 2009, 18:17
autor: kraken
bledu jak bledu
swiadczy to o tym ze problem tkwi w gnome network manager, a stery jako tako dzialaja.
logi ponizej zawieraja 2 logowania network managera. jedno nieudane podczas startu systemu. i drugie poprawne ktore puscilem z palucha.
moja wifi to []eth1[]
mi one nic nie daly:) moze ktos bardziej swiatly cos wynajdzie
Kod: Zaznacz cały
Jul 2 05:58:48 mac-laptop acpid: client connected from 3080[111:122]
Jul 2 05:58:48 mac-laptop bluetoothd[3103]: Bluetooth daemon 4.39
Jul 2 05:58:48 mac-laptop bluetoothd[3103]: Starting SDP server
Jul 2 05:58:48 mac-laptop bluetoothd[3103]: bridge pan0 created
Jul 2 05:58:48 mac-laptop bluetoothd[3103]: Starting experimental netlink support
Jul 2 05:58:48 mac-laptop bluetoothd[3103]: Failed to find Bluetooth netlink family
Jul 2 05:58:49 mac-laptop NetworkManager: <info> starting...
Jul 2 05:58:49 mac-laptop NetworkManager: <info> (eth0): new Ethernet device (driver: 'forcedeth')
Jul 2 05:58:49 mac-laptop NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_1b_24_86_f0_42
Jul 2 05:58:49 mac-laptop NetworkManager: <info> (eth1): driver does not support SSID scans (scan_capa 0x00).
Jul 2 05:58:49 mac-laptop NetworkManager: <info> (eth1): new 802.11 WiFi device (driver: 'wl')
Jul 2 05:58:49 mac-laptop NetworkManager: <info> (eth1): exported as /org/freedesktop/Hal/devices/net_00_1a_73_a8_2b_b4
Jul 2 05:58:49 mac-laptop NetworkManager: <info> Trying to start the supplicant...
Jul 2 05:58:49 mac-laptop avahi-daemon[3170]: Found user 'avahi' (UID 110) and group 'avahi' (GID 121).
Jul 2 05:58:49 mac-laptop avahi-daemon[3170]: Successfully dropped root privileges.
Jul 2 05:58:49 mac-laptop avahi-daemon[3170]: avahi-daemon 0.6.23 starting up.
Jul 2 05:58:49 mac-laptop NetworkManager: <info> Trying to start the system settings daemon...
Jul 2 05:58:49 mac-laptop avahi-daemon[3170]: Successfully called chroot().
Jul 2 05:58:49 mac-laptop avahi-daemon[3170]: Successfully dropped remaining capabilities.
Jul 2 05:58:49 mac-laptop NetworkManager: <info> (eth1): supplicant manager state: down -> idle
Jul 2 05:58:49 mac-laptop nm-system-settings: SCPlugin-Ifupdown: init!
Jul 2 05:58:49 mac-laptop nm-system-settings: SCPlugin-Ifupdown: update_system_hostname
Jul 2 05:58:49 mac-laptop nm-system-settings: SCPluginIfupdown: management mode: unmanaged
Jul 2 05:58:49 mac-laptop nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/net_00_1b_24_86_f0_42, iface: eth0): not well known
Jul 2 05:58:49 mac-laptop nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/net_00_1a_73_a8_2b_b4, iface: eth1): not well known
Jul 2 05:58:49 mac-laptop nm-system-settings: SCPlugin-Ifupdown: end _init.
Jul 2 05:58:49 mac-laptop nm-system-settings: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list.
Jul 2 05:58:49 mac-laptop nm-system-settings: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Jul 2 05:58:49 mac-laptop nm-system-settings: SCPlugin-Ifupdown: (142214968) ... get_connections.
Jul 2 05:58:49 mac-laptop nm-system-settings: SCPlugin-Ifupdown: (142214968) ... get_connections (managed=false): return empty list.
Jul 2 05:58:49 mac-laptop avahi-daemon[3170]: No service file found in /etc/avahi/services.
Jul 2 05:58:49 mac-laptop avahi-daemon[3170]: Network interface enumeration completed.
Jul 2 05:58:49 mac-laptop avahi-daemon[3170]: Registering new address record for fe80::21a:73ff:fea8:2bb4 on eth1.*.
Jul 2 05:58:49 mac-laptop avahi-daemon[3170]: Server startup complete. Host name is mac-laptop.local. Local service cookie is 2381438656.
Jul 2 05:58:49 mac-laptop avahi-daemon[3170]: Registering HINFO record with values 'I686'/'LINUX'.
Jul 2 05:58:49 mac-laptop nm-system-settings: Ifupdown: get unmanaged devices count: 0
Jul 2 05:58:49 mac-laptop acpid: client connected from 3156[0:0]
Jul 2 05:58:53 mac-laptop NetworkManager: <info> (eth0): device state change: 1 -> 2
Jul 2 05:58:53 mac-laptop NetworkManager: <info> (eth0): bringing up device.
Jul 2 05:58:53 mac-laptop NetworkManager: <info> (eth0): preparing device.
Jul 2 05:58:53 mac-laptop NetworkManager: <info> (eth0): deactivating device (reason: 2).
Jul 2 05:58:53 mac-laptop NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Jul 2 05:58:53 mac-laptop NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Jul 2 05:58:53 mac-laptop NetworkManager: <info> (eth1): device state change: 1 -> 2
Jul 2 05:58:53 mac-laptop NetworkManager: <info> (eth1): preparing device.
Jul 2 05:58:53 mac-laptop NetworkManager: <info> (eth1): deactivating device (reason: 2).
Jul 2 05:58:53 mac-laptop NetworkManager: <WARN> nm_device_wifi_disable_encryption(): error setting key for device eth1: Invalid argument
Jul 2 05:58:53 mac-laptop NetworkManager: <info> (eth1): device state change: 2 -> 3
Jul 2 05:58:53 mac-laptop NetworkManager: <info> (eth1): supplicant interface state: starting -> ready
Jul 2 05:58:53 mac-laptop acpid: client connected from 3156[0:0]
Jul 2 05:58:57 mac-laptop console-kit-daemon[2942]: WARNING: Couldn't read /proc/2941/environ: Failed to open file '/proc/2941/environ': No such file or directory
Jul 2 05:59:02 mac-laptop x-session-manager[3566]: WARNING: Could not parse desktop file /home/mac/.config/autostart/cgmailservice.desktop: Plik klucza nie zawiera klucza "Type"
Jul 2 05:59:02 mac-laptop x-session-manager[3566]: WARNING: could not read /home/mac/.config/autostart/cgmailservice.desktop
Jul 2 05:59:10 mac-laptop x-session-manager[3566]: WARNING: Could not launch application 'bluetooth-applet.desktop': Unable to start application: Nie można wykonać procesu potomnego "bluetooth-applet" (No such file or directory)
Jul 2 05:59:12 mac-laptop x-session-manager[3566]: WARNING: Could not launch application 'gnome-volume-manager.desktop': Unable to start application: Nie można wykonać procesu potomnego "/usr/lib/gnome-volume-manager/gnome-volume-manager" (No such file or directory)
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) starting connection 'Auto wifek'
Jul 2 05:59:18 mac-laptop NetworkManager: <info> (eth1): device state change: 3 -> 4
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jul 2 05:59:18 mac-laptop NetworkManager: <info> (eth1): device state change: 4 -> 5
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1/wireless): access point 'Auto wifek' has security, but secrets are required.
Jul 2 05:59:18 mac-laptop NetworkManager: <info> (eth1): device state change: 5 -> 6
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jul 2 05:59:18 mac-laptop NetworkManager: <info> (eth1): device state change: 6 -> 4
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jul 2 05:59:18 mac-laptop NetworkManager: <info> (eth1): device state change: 4 -> 5
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1/wireless): connection 'Auto wifek' has security, and secrets exist. No new secrets needed.
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Config: added 'ssid' value 'wifek'
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Config: added 'scan_ssid' value '1'
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Config: added 'psk' value '<omitted>'
Jul 2 05:59:18 mac-laptop NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Jul 2 05:59:18 mac-laptop NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jul 2 05:59:18 mac-laptop NetworkManager: <info> Config: set interface ap_scan to 1
Jul 2 05:59:18 mac-laptop NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
Jul 2 05:59:28 mac-laptop NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
Jul 2 05:59:30 mac-laptop NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating
Jul 2 05:59:30 mac-laptop NetworkManager: <info> (eth1): supplicant connection state: associating -> associated
Jul 2 05:59:30 mac-laptop NetworkManager: <info> (eth1): supplicant connection state: associated -> 4-way handshake
Jul 2 05:59:30 mac-laptop NetworkManager: <info> (eth1): supplicant connection state: 4-way handshake -> group handshake
Jul 2 05:59:30 mac-laptop NetworkManager: <info> (eth1): supplicant connection state: group handshake -> completed
Jul 2 05:59:30 mac-laptop NetworkManager: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'wifek'.
Jul 2 05:59:30 mac-laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 2 05:59:30 mac-laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Jul 2 05:59:30 mac-laptop NetworkManager: <info> (eth1): device state change: 5 -> 7
Jul 2 05:59:30 mac-laptop NetworkManager: <info> Activation (eth1) Beginning DHCP transaction.
Jul 2 05:59:30 mac-laptop NetworkManager: <info> dhclient started with pid 3917
Jul 2 05:59:30 mac-laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Jul 2 05:59:30 mac-laptop dhclient: Internet Systems Consortium DHCP Client V3.1.1
Jul 2 05:59:30 mac-laptop dhclient: Copyright 2004-2008 Internet Systems Consortium.
Jul 2 05:59:30 mac-laptop dhclient: All rights reserved.
Jul 2 05:59:30 mac-laptop dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 2 05:59:30 mac-laptop dhclient:
Jul 2 05:59:31 mac-laptop NetworkManager: <info> DHCP: device eth1 state changed (null) -> preinit
Jul 2 05:59:31 mac-laptop dhclient: Listening on LPF/eth1/00:1a:73:a8:2b:b4
Jul 2 05:59:31 mac-laptop dhclient: Sending on LPF/eth1/00:1a:73:a8:2b:b4
Jul 2 05:59:31 mac-laptop dhclient: Sending on Socket/fallback
Jul 2 05:59:34 mac-laptop dhclient: DHCPREQUEST of 192.168.0.170 on eth1 to 255.255.255.255 port 67
Jul 2 05:59:43 mac-laptop last message repeated 2 times
Jul 2 05:59:43 mac-laptop dhclient: DHCPACK of 192.168.0.170 from 192.168.0.1
Jul 2 05:59:43 mac-laptop dhclient: bound to 192.168.0.170 -- renewal in 67270 seconds.
Jul 2 05:59:43 mac-laptop NetworkManager: <info> DHCP: device eth1 state changed preinit -> reboot
Jul 2 05:59:43 mac-laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled...
Jul 2 05:59:43 mac-laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) started...
Jul 2 05:59:43 mac-laptop NetworkManager: <info> address 192.168.0.170
Jul 2 05:59:43 mac-laptop NetworkManager: <info> prefix 24 (255.255.255.0)
Jul 2 05:59:43 mac-laptop NetworkManager: <info> gateway 192.168.0.1
Jul 2 05:59:43 mac-laptop NetworkManager: <info> nameserver '89.174.12.254'
Jul 2 05:59:43 mac-laptop NetworkManager: <info> nameserver '192.168.0.1'
Jul 2 05:59:43 mac-laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
Jul 2 05:59:43 mac-laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) complete.
Jul 2 05:59:43 mac-laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
Jul 2 05:59:43 mac-laptop avahi-daemon[3170]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.0.170.
Jul 2 05:59:43 mac-laptop avahi-daemon[3170]: New relevant interface eth1.IPv4 for mDNS.
Jul 2 05:59:43 mac-laptop avahi-daemon[3170]: Registering new address record for 192.168.0.170 on eth1.IPv4.
Jul 2 05:59:44 mac-laptop NetworkManager: <info> (eth1): device state change: 7 -> 8
Jul 2 05:59:44 mac-laptop NetworkManager: <info> Policy set 'Auto wifek' (eth1) as default for routing and DNS.
Jul 2 05:59:44 mac-laptop NetworkManager: <info> Activation (eth1) successful, device activated.
Jul 2 05:59:44 mac-laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
jeszcze jedno:
jak wylacze wszelkie zabezpieczenia.....czyli dam siec otwarta jest dobrze. problemy robia wtedy go away
Odp: polaczenia z AP dopiero po kilku nieudanych probach
: 02 lip 2009, 20:37
autor: Semerchet
Odp: polaczenia z AP dopiero po kilku nieudanych probach
: 03 lip 2009, 16:09
autor: kraken
rozwiazanie tego dziwnego problemu znalazlem o dziwo w swoim routerze.
[nie kupujcie dlinka - tani ale pozniej ssie krew litrami]
mialem zabezpienie 'wpa2-psk(aes)', zmienilem na wpa-psk/wpa2-psk i od tamtej pory jest pieknie. laczy sie za kazdym razem do sieci, za przy kazdym restarcie kompa.
suma sumarow w ubuntu nic nie zmienialem, prawdopodobnie system mial problem ze wsparciem '(aes)'.
dzieki za pomoc