Автор Тема: wifi проблемы авторизации(решено)  (Прочитано 4629 раз)

Оффлайн myshbesh

  • Участник
  • *
  • Сообщений: 62
Установил altlinux-5.0.0-kdesktop-i586-ru на ноут Toshiba Satellite P200-RT7 все хорошо, только wifi  после установки ОС первый раз соединяется и все работает прекрасно, но после рассоединения(принудительного) или после перезагрузки компа соединение можно ждать сколько угодно, подтверждая пароль.Соединение  может произоити чере 5, через 10 минут или не произоти вообще.
Настраивал wifi  с помощью KNetworkManadger, wifi -карту он определяет как Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection.
 Подскажите, пожалуйста, с чем это может быть связано.
« Последнее редактирование: 09.04.2014 15:37:32 от myshbesh »

Оффлайн myshbesh

  • Участник
  • *
  • Сообщений: 62
Re: wifi проблемы авторизации
« Ответ #1 : 31.08.2010 12:47:28 »
Забыл, wifi маршрутизатор D-linr-824.

Оффлайн ruslandh

  • Поспешай не торопясь !
  • Модератор глобальный
  • *****
  • Сообщений: 32 361
  • Учиться .... Телепатами не рождаются, ими ....
Re: wifi проблемы авторизации
« Ответ #2 : 31.08.2010 17:32:01 »
Смотрите логи на 12-м экране и в /var/log/messages

Оффлайн myshbesh

  • Участник
  • *
  • Сообщений: 62
Re: wifi проблемы авторизации
« Ответ #3 : 31.08.2010 20:56:36 »
К сожалению, мне эта информация мало, что говорит.
А как её перенести на форум я не знаю.
Если несложно подскажите, пожалуйста.

Оффлайн Карлсон

  • Участник
  • *
  • Сообщений: 1 699
Re: wifi проблемы авторизации
« Ответ #4 : 31.08.2010 21:15:05 »
А как её перенести на форум я не знаю.

От рута
tail -100 /var/log/messages > /tmp/log.txt

и потом log.txt сюда, на форум. Вместо числа 100 подставьте нужное количество строк, которое будет сохранено в файл (чтоб влезло все нужное, и не влезло все ненужное).

Оффлайн ruslandh

  • Поспешай не торопясь !
  • Модератор глобальный
  • *****
  • Сообщений: 32 361
  • Учиться .... Телепатами не рождаются, ими ....
Re: wifi проблемы авторизации
« Ответ #5 : 31.08.2010 21:18:42 »
Двенадцатый экран = Ctrl+ALt+F12 (обратно Alt+F7)

Оффлайн myshbesh

  • Участник
  • *
  • Сообщений: 62
Re: wifi проблемы авторизации
« Ответ #6 : 31.08.2010 21:49:40 »
Спасибо
Aug 31 21:36:25 VMESTONAME NetworkManager: <WARN>  update_one_setting(): Failed to update connection secrets: 1 802-1x
Aug 31 21:36:25 VMESTONAME NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.
Aug 31 21:36:25 VMESTONAME NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 6 -> 4 (reason 0)
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  Activation (wlan0/wireless): connection 'default' has security, and secrets exist.  No new secrets needed.
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  Config: added 'ssid' value 'default'
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  Config: set interface ap_scan to 1
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> 4-way handshake
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> associated
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> associating
Aug 31 21:36:25 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Aug 31 21:36:35 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug 31 21:36:38 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug 31 21:36:38 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> 4-way handshake
Aug 31 21:36:38 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> associated
Aug 31 21:36:41 VMESTONAME NetworkManager: <info>  wlan0: link timed out.
Aug 31 21:36:41 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> disconnected
Aug 31 21:36:42 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug 31 21:36:43 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> disconnected
Aug 31 21:36:48 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug 31 21:36:50 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug 31 21:36:50 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> 4-way handshake
Aug 31 21:36:50 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> associated
Aug 31 21:36:50 VMESTONAME NetworkManager: <info>  Activation (wlan0/wireless): association took too long.
Aug 31 21:36:50 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 5 -> 6 (reason 0)
Aug 31 21:36:51 VMESTONAME NetworkManager: <info>  Activation (wlan0/wireless): asking for new secrets
Aug 31 21:36:51 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> disconnected
Aug 31 21:36:58 VMESTONAME NetworkManager: <WARN>  get_secrets_cb(): Couldn't get connection secrets: User refused to supply secrets.
Aug 31 21:36:58 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 6 -> 9 (reason 7)
Aug 31 21:36:58 VMESTONAME NetworkManager: <info>  Activation (wlan0) failed for access point (default)
Aug 31 21:36:58 VMESTONAME NetworkManager: <info>  Marking connection 'default' invalid.
Aug 31 21:36:58 VMESTONAME NetworkManager: <info>  Activation (wlan0) failed.
Aug 31 21:36:58 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 9 -> 3 (reason 0)
Aug 31 21:36:58 VMESTONAME NetworkManager: <info>  (wlan0): deactivating device (reason: 0).
Aug 31 21:36:58 VMESTONAME NetworkManager: <info>  Hostname is not changed because Xorg server is active
Aug 31 21:36:58 VMESTONAME NetworkManager: <info>  Hostname is not changed because Xorg server is active
Aug 31 21:37:01 VMESTONAME kernel: [ 4012.584249] [drm] Resetting GPU
« Последнее редактирование: 21.09.2010 14:26:32 от Mario_z »

Оффлайн ruslandh

  • Поспешай не торопясь !
  • Модератор глобальный
  • *****
  • Сообщений: 32 361
  • Учиться .... Телепатами не рождаются, ими ....
Re: wifi проблемы авторизации
« Ответ #7 : 01.09.2010 08:24:55 »
Цитировать
....
Aug 31 21:36:41 VMESTONAME NetworkManager: <info>  wlan0: link timed out.
....
Activation (wlan0/wireless): association took too long.
...
Aug 31 21:36:58 VMESTONAME NetworkManager: <WARN>  get_secrets_cb(): Couldn't get connection secrets: User refused to supply secrets.
.....
Aug 31 21:36:58 VMESTONAME NetworkManager: <info>  Activation (wlan0) failed for access point (default)
Дословно :
...
Таймаут.
.....
Слишком долгая установка соединения
....

Не удалось получить секрет соединения, Пользователь отказался предоставить секрет.
....
Активация точки доступа не удалась, нет доступа.
.....

Оффлайн myshbesh

  • Участник
  • *
  • Сообщений: 62
Re: wifi проблемы авторизации
« Ответ #8 : 01.09.2010 10:56:34 »
Так в чем проблема?
Иногда ведь соединяется и тогда не разрывается.
А с виндой соединялось моментально.

Оффлайн myshbesh

  • Участник
  • *
  • Сообщений: 62
Re: wifi проблемы авторизации
« Ответ #9 : 05.09.2010 14:39:58 »
 В  /var/log/messages   не вся информация.
На 12 экране ее больше.
Кто-нибудь знает, как найти файл, где вся инфа с 12 экрана?
Заранен благодарен.

Оффлайн ruslandh

  • Поспешай не торопясь !
  • Модератор глобальный
  • *****
  • Сообщений: 32 361
  • Учиться .... Телепатами не рождаются, ими ....
Re: wifi проблемы авторизации
« Ответ #10 : 05.09.2010 15:30:32 »
Такого файла может и не быть. Настройка осуществляется через /etc/syslog.conf

Оффлайн myshbesh

  • Участник
  • *
  • Сообщений: 62
Re: wifi проблемы авторизации
« Ответ #11 : 21.09.2010 13:46:38 »
Спасибо всем за советы.Как записывать логи разобрался. Но проблемы остались.
привожу логи
1. Успешное подключение:

Sep  5 17:54:23 VMESTONAME NetworkManager: <WARN>  update_one_setting(): Failed to update connection secrets: 1 802-1x
Sep  5 17:54:23 VMESTONAME NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.
Sep  5 17:54:23 VMESTONAME NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 6 -> 4 (reason 0)
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  Activation (wlan0/wireless): connection 'default' has security, and secrets exist.  No new secrets needed.
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  Config: added 'ssid' value 'default'
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> disconnected
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  Config: set interface ap_scan to 1
Sep  5 17:54:23 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Sep  5 17:54:35 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Sep  5 17:54:35 VMESTONAME kernel: [ 1985.145990] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep  5 17:54:35 VMESTONAME kernel: [ 1985.147815] wlan0: authenticated
Sep  5 17:54:35 VMESTONAME kernel: [ 1985.147818] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep  5 17:54:35 VMESTONAME kernel: [ 1985.150299] wlan0: RX AssocResp from 00:19:5b:be:a3:c1 (capab=0x431 status=0 aid=1)
Sep  5 17:54:35 VMESTONAME kernel: [ 1985.150303] wlan0: associated
Sep  5 17:54:35 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> 4-way handshake
Sep  5 17:54:35 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> associated
Sep  5 17:54:39 VMESTONAME NetworkManager: <info>  wlan0: link timed out.
Sep  5 17:54:39 VMESTONAME kernel: [ 1988.885117] wlan0: disassociated (Reason: 3)
Sep  5 17:54:39 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> disconnected
Sep  5 17:54:39 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Sep  5 17:54:40 VMESTONAME kernel: [ 1989.884127] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep  5 17:54:40 VMESTONAME kernel: [ 1990.084126] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep  5 17:54:40 VMESTONAME kernel: [ 1990.284108] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep  5 17:54:40 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> disconnected
Sep  5 17:54:40 VMESTONAME kernel: [ 1990.484128] wlan0: association with AP 00:19:5b:be:a3:c1 timed out
Sep  5 17:54:45 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Sep  5 17:54:47 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Sep  5 17:54:47 VMESTONAME kernel: [ 1997.649459] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep  5 17:54:47 VMESTONAME kernel: [ 1997.670493] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep  5 17:54:47 VMESTONAME kernel: [ 1997.672319] wlan0: authenticated
Sep  5 17:54:47 VMESTONAME kernel: [ 1997.672323] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep  5 17:54:47 VMESTONAME kernel: [ 1997.674720] wlan0: RX ReassocResp from 00:19:5b:be:a3:c1 (capab=0x431 status=0 aid=1)
Sep  5 17:54:47 VMESTONAME kernel: [ 1997.674723] wlan0: associated
Sep  5 17:54:47 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Sep  5 17:54:47 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Sep  5 17:54:48 VMESTONAME kernel: [ 1997.763177] padlock: VIA PadLock not detected.
Sep  5 17:54:48 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> group handshake
Sep  5 17:54:48 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed
Sep  5 17:54:48 VMESTONAME NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'default'.
Sep  5 17:54:48 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep  5 17:54:48 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Sep  5 17:54:48 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 5 -> 7 (reason 0)
Sep  5 17:54:48 VMESTONAME NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction.
Sep  5 17:54:48 VMESTONAME NetworkManager: <info>  dhcpcd started with pid 9431
Sep  5 17:54:48 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Sep  5 17:54:48 VMESTONAME dhcpcd[9431]: wlan0: dhcpcd 4.0.15 starting
Sep  5 17:54:48 VMESTONAME NetworkManager: <info>  DHCP: device wlan0 state changed (null) -> preinit
Sep  5 17:54:48 VMESTONAME dhcpcd[9431]: wlan0: broadcasting for a lease
Sep  5 17:54:49 VMESTONAME dhcpcd[9431]: wlan0: offered 192.168.0.3 from 192.168.0.1 `My Host'
Sep  5 17:54:49 VMESTONAME dhcpcd[9431]: wlan0: acknowledged 192.168.0.3 from 192.168.0.1 `My Host'
Sep  5 17:54:49 VMESTONAME dhcpcd[9431]: wlan0: leased 192.168.0.3 for 604800 seconds
Sep  5 17:54:49 VMESTONAME avahi-daemon[6912]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.3.
Sep  5 17:54:49 VMESTONAME avahi-daemon[6912]: New relevant interface wlan0.IPv4 for mDNS.
Sep  5 17:54:49 VMESTONAME avahi-daemon[6912]: Registering new address record for 192.168.0.3 on wlan0.IPv4.
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>  DHCP: device wlan0 state changed preinit -> bound
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>    address 192.168.0.3
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>    prefix 24 (255.255.255.0)
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>    gateway 192.168.0.1
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>    nameserver '213.234.192.7'
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>    nameserver '85.21.192.5'
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>    nameserver '192.168.0.1'
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>    domain name 'MSHOME'
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Sep  5 17:54:49 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Sep  5 17:54:49 VMESTONAME avahi-daemon[6912]: Withdrawing address record for 192.168.0.3 on wlan0.
Sep  5 17:54:49 VMESTONAME avahi-daemon[6912]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.3.
Sep  5 17:54:49 VMESTONAME avahi-daemon[6912]: Interface wlan0.IPv4 no longer relevant for mDNS.
Sep  5 17:54:49 VMESTONAME avahi-daemon[6912]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.3.
Sep  5 17:54:49 VMESTONAME avahi-daemon[6912]: New relevant interface wlan0.IPv4 for mDNS.
Sep  5 17:54:49 VMESTONAME avahi-daemon[6912]: Registering new address record for 192.168.0.3 on wlan0.IPv4.
Sep  5 17:54:50 VMESTONAME NetworkManager: <info>  (wlan0): writing resolv.conf to /sbin/resolvconf
Sep  5 17:54:51 VMESTONAME named[6046]: loading configuration from '/etc/named.conf'
Sep  5 17:54:51 VMESTONAME named[6046]: using default UDP/IPv4 port range: [1024, 65535]
Sep  5 17:54:51 VMESTONAME bind: sending signal 1 to named succeeded
Sep  5 17:54:51 VMESTONAME named[6046]: using default UDP/IPv6 port range: [1024, 65535]
Sep  5 17:54:51 VMESTONAME named[6046]: listening on IPv4 interface wlan0, 192.168.0.3#53
Sep  5 17:54:51 VMESTONAME named[6046]: could not listen on UDP socket: permission denied
Sep  5 17:54:51 VMESTONAME named[6046]: creating IPv4 interface wlan0 failed; interface ignored
Sep  5 17:54:51 VMESTONAME NetworkManager: <info>  Hostname is not changed because Xorg server is active
Sep  5 17:54:51 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 7 -> 8 (reason 0)
Sep  5 17:54:51 VMESTONAME NetworkManager: <info>  (wlan0): writing resolv.conf to /sbin/resolvconf
Sep  5 17:54:51 VMESTONAME NetworkManager: <info>  Policy set 'default' (wlan0) as default for routing and DNS.
Sep  5 17:54:51 VMESTONAME NetworkManager: <info>  Hostname is not changed because Xorg server is active
Sep  5 17:54:51 VMESTONAME NetworkManager: <info>  Activation (wlan0) successful, device activated.
Sep  5 17:54:51 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Sep  5 17:55:09 VMESTONAME kernel: [ 2018.912239] [drm] Resetting GPU


« Последнее редактирование: 21.09.2010 14:26:18 от Mario_z »

Оффлайн myshbesh

  • Участник
  • *
  • Сообщений: 62
Re: wifi проблемы авторизации
« Ответ #12 : 21.09.2010 13:50:15 »
Прошу прошения не умею вставлять с полосой прокрутки, поэтому придется использовать несколлько сообщений.

2.Неудачное соединение.

Sep  5 17:33:45 VMESTONAME kernel: [  735.152599] [drm] Resetting GPU
Sep  5 17:35:10 VMESTONAME kernel: [  820.669244] [drm] Resetting GPU
Sep  5 17:41:02 VMESTONAME kernel: [ 1172.066804] [drm] Loading RV610 CP Microcode
Sep  5 17:41:02 VMESTONAME kernel: [ 1172.067196] [drm] Loading RV610 PFP Microcode
Sep  5 17:41:02 VMESTONAME kernel: [ 1172.082150] [drm] Resetting GPU
Sep  5 17:41:16 VMESTONAME NetworkManager: <WARN>  update_one_setting(): Failed to update connection secrets: 1 802-1x
Sep  5 17:41:16 VMESTONAME NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.
Sep  5 17:41:16 VMESTONAME NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 6 -> 4 (reason 0)
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  Activation (wlan0/wireless): connection 'default' has security, and secrets exist.  No new secrets needed.
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  Config: added 'ssid' value 'default'
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  Config: set interface ap_scan to 1
Sep  5 17:41:16 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Sep  5 17:41:19 VMESTONAME kernel: [ 1188.896231] [drm] Resetting GPU
Sep  5 17:41:28 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Sep  5 17:41:28 VMESTONAME kernel: [ 1197.830196] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep  5 17:41:28 VMESTONAME kernel: [ 1197.831967] wlan0: authenticated
Sep  5 17:41:28 VMESTONAME kernel: [ 1197.831971] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep  5 17:41:28 VMESTONAME kernel: [ 1197.834315] wlan0: RX AssocResp from 00:19:5b:be:a3:c1 (capab=0x431 status=0 aid=1)
Sep  5 17:41:28 VMESTONAME kernel: [ 1197.834319] wlan0: associated
Sep  5 17:41:28 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> 4-way handshake
Sep  5 17:41:28 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> associated
Sep  5 17:41:31 VMESTONAME kernel: [ 1200.855619] wlan0: disassociated (Reason: 3)
Sep  5 17:41:31 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> disconnected
Sep  5 17:41:31 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Sep  5 17:41:32 VMESTONAME kernel: [ 1201.852132] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep  5 17:41:32 VMESTONAME kernel: [ 1202.052111] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep  5 17:41:32 VMESTONAME kernel: [ 1202.252134] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep  5 17:41:32 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> disconnected
Sep  5 17:41:32 VMESTONAME kernel: [ 1202.452113] wlan0: association with AP 00:19:5b:be:a3:c1 timed out
Sep  5 17:41:37 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Sep  5 17:41:38 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> disconnected
Sep  5 17:41:38 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Sep  5 17:41:39 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Sep  5 17:41:39 VMESTONAME kernel: [ 1209.642812] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep  5 17:41:39 VMESTONAME kernel: [ 1209.660369] wlan0: authenticate with AP 00:19:5b:be:a3:c1
Sep  5 17:41:39 VMESTONAME kernel: [ 1209.660391] wlan0: authenticated
Sep  5 17:41:39 VMESTONAME kernel: [ 1209.660393] wlan0: associate with AP 00:19:5b:be:a3:c1
Sep  5 17:41:39 VMESTONAME kernel: [ 1209.664729] wlan0: RX ReassocResp from 00:19:5b:be:a3:c1 (capab=0x431 status=0 aid=1)
Sep  5 17:41:39 VMESTONAME kernel: [ 1209.664732] wlan0: associated
Sep  5 17:41:39 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> 4-way handshake
Sep  5 17:41:39 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> associated
Sep  5 17:41:42 VMESTONAME NetworkManager: <info>  Activation (wlan0/wireless): association took too long.
Sep  5 17:41:42 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 5 -> 9 (reason 7)
Sep  5 17:41:42 VMESTONAME NetworkManager: <info>  Activation (wlan0) failed for access point (default)
Sep  5 17:41:42 VMESTONAME kernel: [ 1211.715066] wlan0: disassociating by local choice (reason=3)
Sep  5 17:41:42 VMESTONAME NetworkManager: <info>  Marking connection 'default' invalid.
Sep  5 17:41:42 VMESTONAME NetworkManager: <info>  Activation (wlan0) failed.
Sep  5 17:41:42 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 9 -> 3 (reason 0)
Sep  5 17:41:42 VMESTONAME NetworkManager: <info>  (wlan0): deactivating device (reason: 0).
Sep  5 17:41:42 VMESTONAME NetworkManager: <info>  Hostname is not changed because Xorg server is active
Sep  5 17:41:42 VMESTONAME NetworkManager: <info>  Hostname is not changed because Xorg server is active
Sep  5 17:43:52 VMESTONAME kernel: [ 1342.528272] [drm] Loading RV610 CP Microcode
Sep  5 17:43:52 VMESTONAME kernel: [ 1342.528664] [drm] Loading RV610 PFP Microcode
Sep  5 17:43:52 VMESTONAME kernel: [ 1342.543611] [drm] Resetting GPU
Sep  5 17:44:05 VMESTONAME kernel: [ 1355.152290] [drm] Resetting GPU

« Последнее редактирование: 21.09.2010 14:25:58 от Mario_z »

Оффлайн myshbesh

  • Участник
  • *
  • Сообщений: 62
Re: wifi проблемы авторизации
« Ответ #13 : 21.09.2010 13:55:59 »
3.Соединение происходит. (При наведении мыши на иконку, пишет соеденино, но нет красного кружочка( или сердечка), как при нормальном подключении.) Но пакеты не ходят. Никакие.

Sep 20 21:42:44 VMESTONAME NetworkManager: <info>  Activation (wlan0/wireless): asking for new secrets
Sep 20 21:42:44 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> disconnected
Sep 20 21:42:47 VMESTONAME NetworkManager: <WARN>  update_one_setting(): Failed to update connection secrets: 1 802-1x
Sep 20 21:42:47 VMESTONAME NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.
Sep 20 21:42:47 VMESTONAME NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 6 -> 4 (reason 0)
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  Activation (wlan0/wireless): connection 'default' has security, and secrets exist.  No new secrets needed.
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  Config: added 'ssid' value 'default'
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  Config: set interface ap_scan to 1
Sep 20 21:42:47 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Sep 20 21:42:48 VMESTONAME kernel: [ 2455.551719] wlan0: direct probe to AP 00:19:5b:be:a3:c1 (try 1)
Sep 20 21:42:48 VMESTONAME kernel: [ 2455.552003] wlan0: deauthenticating from 00:19:5b:be:a3:c1 by local choice (reason=3)
Sep 20 21:42:48 VMESTONAME kernel: [ 2455.552068] wlan0: direct probe to AP 00:19:5b:be:a3:c1 (try 1)
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Sep 20 21:42:48 VMESTONAME kernel: [ 2455.556202] wlan0: direct probe responded
Sep 20 21:42:48 VMESTONAME kernel: [ 2455.556206] wlan0: authenticate with AP 00:19:5b:be:a3:c1 (try 1)
Sep 20 21:42:48 VMESTONAME kernel: [ 2455.559801] wlan0: authenticated
Sep 20 21:42:48 VMESTONAME kernel: [ 2455.559822] wlan0: associate with AP 00:19:5b:be:a3:c1 (try 1)
Sep 20 21:42:48 VMESTONAME kernel: [ 2455.562182] wlan0: RX AssocResp from 00:19:5b:be:a3:c1 (capab=0x431 status=0 aid=2)
Sep 20 21:42:48 VMESTONAME kernel: [ 2455.562186] wlan0: associated
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> group handshake
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'default'.
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 5 -> 7 (reason 0)
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction.
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  dhcpcd started with pid 10347
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Sep 20 21:42:48 VMESTONAME dhcpcd[10347]: wlan0: dhcpcd 4.0.15 starting
Sep 20 21:42:48 VMESTONAME NetworkManager: <info>  DHCP: device wlan0 state changed stop -> preinit
Sep 20 21:42:48 VMESTONAME dhcpcd[10347]: wlan0: broadcasting for a lease
Sep 20 21:42:49 VMESTONAME dhcpcd[10347]: wlan0: offered 192.168.0.3 from 192.168.0.1 `My Host'
Sep 20 21:42:49 VMESTONAME dhcpcd[10347]: wlan0: acknowledged 192.168.0.3 from 192.168.0.1 `My Host'
Sep 20 21:42:49 VMESTONAME dhcpcd[10347]: wlan0: leased 192.168.0.3 for 604800 seconds
Sep 20 21:42:49 VMESTONAME avahi-daemon[7303]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.3.
Sep 20 21:42:49 VMESTONAME avahi-daemon[7303]: New relevant interface wlan0.IPv4 for mDNS.
Sep 20 21:42:49 VMESTONAME avahi-daemon[7303]: Registering new address record for 192.168.0.3 on wlan0.IPv4.
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>  DHCP: device wlan0 state changed preinit -> bound
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>    address 192.168.0.3
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>    prefix 24 (255.255.255.0)
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>    gateway 192.168.0.1
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>    nameserver '213.234.192.7'
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>    nameserver '85.21.192.5'
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>    nameserver '192.168.0.1'
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>    domain name 'MSHOME'
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Sep 20 21:42:49 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Sep 20 21:42:49 VMESTONAME avahi-daemon[7303]: Withdrawing address record for 192.168.0.3 on wlan0.
Sep 20 21:42:49 VMESTONAME avahi-daemon[7303]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.3.
Sep 20 21:42:49 VMESTONAME avahi-daemon[7303]: Interface wlan0.IPv4 no longer relevant for mDNS.
Sep 20 21:42:49 VMESTONAME avahi-daemon[7303]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.3.
Sep 20 21:42:49 VMESTONAME avahi-daemon[7303]: New relevant interface wlan0.IPv4 for mDNS.
Sep 20 21:42:49 VMESTONAME avahi-daemon[7303]: Registering new address record for 192.168.0.3 on wlan0.IPv4.
Sep 20 21:42:50 VMESTONAME NetworkManager: <info>  (wlan0): writing resolv.conf to /sbin/resolvconf
Sep 20 21:42:51 VMESTONAME named[6432]: loading configuration from '/etc/named.conf'
Sep 20 21:42:51 VMESTONAME named[6432]: using default UDP/IPv4 port range: [1024, 65535]
Sep 20 21:42:51 VMESTONAME named[6432]: using default UDP/IPv6 port range: [1024, 65535]
Sep 20 21:42:51 VMESTONAME named[6432]: listening on IPv4 interface wlan0, 192.168.0.3#53
Sep 20 21:42:51 VMESTONAME named[6432]: could not listen on UDP socket: permission denied
Sep 20 21:42:51 VMESTONAME bind: sending signal 1 to named succeeded
Sep 20 21:42:51 VMESTONAME named[6432]: creating IPv4 interface wlan0 failed; interface ignored
Sep 20 21:42:51 VMESTONAME NetworkManager: <info>  Hostname is not changed because Xorg server is active
Sep 20 21:42:51 VMESTONAME NetworkManager: <info>  (wlan0): device state change: 7 -> 8 (reason 0)
Sep 20 21:42:51 VMESTONAME NetworkManager: <info>  Hostname is not changed because Xorg server is active
Sep 20 21:42:51 VMESTONAME NetworkManager: <info>  Activation (wlan0) successful, device activated.
Sep 20 21:42:51 VMESTONAME NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.

« Последнее редактирование: 21.09.2010 14:25:18 от Mario_z »

Оффлайн myshbesh

  • Участник
  • *
  • Сообщений: 62
Re: wifi проблемы авторизации
« Ответ #14 : 21.09.2010 13:59:35 »
Граждане помогите, кто чем может.  :)
Систему переустанавливал.
Обновления проводил.
Ядро обновил с 2.6.30 до 2.6.32.
Ни чего не помогает. :'(