K wi-fi sieti sa treba pripajat na 2-krat

Sekcia: Hardware a Drivery 04.04.2008 | 01:20
Avatar zemkooo openSUSE, PC-BSD  Používateľ
Mam takyto problem:

mam doma wireless router obvykle sa musim k nemu pripajat na dvakrat, co ma dost stve. Vyzera to nalsedovne.

1. nastartujem linux a v system trayi svieti ikonka - nepripojene k sieti (pouzivam Gnome netmanagera alebo ako sa vola...)
2. kliknem na ikonku - vypise mi dostupne siete
3. zvolim tu svoju a cakam na pripajanie
4. kedze siet aj s heslom je uz ulozena - vyskoci vyzva na pristup ku keyring manageru,aby si odtial vytiahol heslo k wi-fi sieti, zadam heslo do keyring manazera
5. chvilu pripaja, potom nachvilu nabehne connected a asi za sekundu opat disconnectne
6. takze to opakujem, na druhykrat uz vacsinou pripoji a spojenie drzi...

problem je, ze:

A. musim sa pripajat na 2krat
B. niekedy nepripoji ani na 2.krat a vyskoci okno s nazvom siete a musim rucne vypisat heslo
C. stalo sa uz, ze k sieti ma pripojilo automaticky po prihlaseni - toto je ale velmi zriedkave

este par info o hardware/software:

- pouzivam openSUSE 10.3, GNOME
- wi-fi karta je Intel PRO/Wireless 3945ABG, Router MSI RG60G
- vo WinXP ani Vista nikdy takyto problem nie je - k sieti sa pripoji zakazdym automaticky, cize siet aj router by mali byt nastavene dobre

neskor este pozriem do logov, ci tam nieco nenajdem a pripadne pripojim...

Nevie niekto pomoct ?
    • Re: K wi-fi sieti sa treba pripajat na 2-krat 04.04.2008 | 01:31
      Avatar Marián Sova Ubuntu 10.10  Administrátor
      Mňa sa tiež opýta na heslo do keyring ale paradoxne musím zadať prihlasovacie. Ak zadám to do keyring, tak ma nepripojí vôbec. Skús to tak, aj keď to v tvojom prípade neviem, či pomôže.
      Čo ťa nezabije, to ťa posilní | Leták na propagáciu jabbera v pdf | www.mikroprocesory.sk
    • Re: K wi-fi sieti sa treba pripajat na 2-krat 04.04.2008 | 02:39
      Avatar zemkooo openSUSE, PC-BSD  Používateľ
      Tu je vycuc z logu:

      Apr 3 23:35:43 linux NetworkManager: <info> Activation (eth1) Beginning DHCP transaction.
      Apr 3 23:35:43 linux NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
      Apr 3 23:35:43 linux NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth1
      Apr 3 23:35:43 linux NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth1
      Apr 3 23:35:49 linux NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface eth1
      Apr 3 23:35:49 linux NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled...
      Apr 3 23:35:49 linux NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) started...
      Apr 3 23:35:49 linux NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon:
      Apr 3 23:35:49 linux NetworkManager: <info> address x.x.x.x
      Apr 3 23:35:49 linux NetworkManager: <info> netmask x.x.x.x
      Apr 3 23:35:49 linux NetworkManager: <info> broadcast x.x.x.x
      Apr 3 23:35:49 linux NetworkManager: <info> gateway x.x.x.x
      Apr 3 23:35:49 linux NetworkManager: <info> nameserver x.x.x.x
      Apr 3 23:35:49 linux NetworkManager: <info> nameserver x.x.x.x
      Apr 3 23:35:49 linux NetworkManager: <info> domain name 'domena'
      Apr 3 23:35:49 linux NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
      Apr 3 23:35:49 linux NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) complete.
      Apr 3 23:35:49 linux NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
      Apr 3 23:35:50 linux NetworkManager: <info> Clearing nscd hosts cache.
      Apr 3 23:35:50 linux NetworkManager: <info> Activation (eth1) successful, device activated.
      Apr 3 23:35:50 linux NetworkManager: <info> Activation (eth1) Finish handler scheduled.
      Apr 3 23:35:50 linux NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
      Apr 3 23:35:50 linux NetworkManager: <debug> [1207258550.227130] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'meno'
      Apr 3 23:35:50 linux NetworkManager: <info> SWITCH: terminating current connection 'eth1' because it's no longer valid.
      Apr 3 23:35:50 linux NetworkManager: <info> Deactivating device eth1.
      Apr 3 23:35:51 linux NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed
      Apr 3 23:35:51 linux NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed
      Apr 3 23:35:58 linux NetworkManager: <debug> [1207258558.710809] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'meno'
      Apr 3 23:35:58 linux NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / meno
      Apr 3 23:35:58 linux NetworkManager: <info> Deactivating device eth1.
      Apr 3 23:35:58 linux NetworkManager: <info> Device eth1 activation scheduled...
      • Re: K wi-fi sieti sa treba pripajat na 2-krat 04.04.2008 | 02:50
        Avatar zemkooo openSUSE, PC-BSD  Používateľ
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) started...
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1/wireless): access point 'meno' is encrypted, but NO valid key exists. New key needed.
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) New wireless user key requested for network 'meno'.
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) New wireless user key for network 'meno' received.
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
        Apr 3 23:35:58 linux NetworkManager: <info> Activation (eth1/wireless): access point 'meno' is encrypted, and a key exists. No new key needed.
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: sending command 'INTERFACE_ADD eth1 wext /var/run/wpa_supplicant '
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: response was 'OK'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: response was 'OK'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: response was '0'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 7065746f'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: response was 'OK'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 scan_ssid 1'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: response was 'OK'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: response was 'OK'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: response was 'OK'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 psk <key>'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: response was 'OK'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
        Apr 3 23:35:59 linux NetworkManager: <info> SUP: response was 'OK'
        Apr 3 23:35:59 linux NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
        Apr 3 23:36:00 linux NetworkManager: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'meno'.
        Apr 3 23:36:00 linux NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
        Apr 3 23:36:00 linux NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
        Apr 3 23:36:01 linux NetworkManager: <info> Activation (eth1) Beginning DHCP transaction.
        Apr 3 23:36:01 linux NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
        Apr 3 23:36:01 linux NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth1
        Apr 3 23:36:01 linux NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth1
        Apr 3 23:36:04 linux NetworkManager: <info> Old device 'eth1' activating, won't change.
        Apr 3 23:36:10 linux NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface eth1
        Apr 3 23:36:10 linux NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled...
        Apr 3 23:36:10 linux NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) started...

        • Re: K wi-fi sieti sa treba pripajat na 2-krat 04.04.2008 | 02:55
          Avatar zemkooo openSUSE, PC-BSD  Používateľ
          Apr 3 23:36:10 linux NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon:
          Apr 3 23:36:10 linux NetworkManager: <info> address x.x.x.x
          Apr 3 23:36:10 linux NetworkManager: <info> netmask x.x.x.x
          Apr 3 23:36:10 linux NetworkManager: <info> broadcast x.x.x.x
          Apr 3 23:36:10 linux NetworkManager: <info> gateway x.x.x.x
          Apr 3 23:36:10 linux NetworkManager: <info> nameserver x.x.x.x
          Apr 3 23:36:10 linux NetworkManager: <info> nameserver x.x.x.x
          Apr 3 23:36:10 linux NetworkManager: <info> domain name 'domena'
          Apr 3 23:36:10 linux NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
          Apr 3 23:36:10 linux NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) complete.
          Apr 3 23:36:10 linux NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
          Apr 3 23:36:11 linux NetworkManager: <info> Clearing nscd hosts cache.
          Apr 3 23:36:11 linux NetworkManager: <info> Activation (eth1) Finish handler scheduled.
          Apr 3 23:36:11 linux NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
          Apr 3 23:36:11 linux NetworkManager: <info> Activation (eth1) successful, device activated.


          - namiesto x.x.x.x su samozrejme spravne IP adresy a maska