upgrade wheezy-jessie

[kmchen]

Hi every body

I upgraded yesterday from Wheezy to Jessie and I don't have any wifi connexion now. The wifi card is working because I see neighbours networks around but WAP authentication fails. I did not change any authentication datas of course.

Any help greatly apreciated cause I do not have mail on my working laptop anymore

[Head_on_a_Stick]

I upgraded yesterday from Wheezy to Jessie

Perhaps you did it wrong.

Check: https://www.debian.org/releases/stable/ ... ng.en.html

[kmchen]

Unfortunately this morning it doesn't connect ! Never seen such an instable wifi connexion. Here is the syslog when I try to connect via WICD:

Code: Select all

Aug 27 11:21:56 kmcs dhclient: Listening on LPF/wlan0/f8:16:54:6b:ed:ba
Aug 27 11:21:56 kmcs dhclient: Sending on   LPF/wlan0/f8:16:54:6b:ed:ba
Aug 27 11:21:56 kmcs dhclient: Sending on   Socket/fallback
Aug 27 11:21:56 kmcs dhclient: DHCPRELEASE on wlan0 to 192.168.43.1 port 67
Aug 27 11:21:56 kmcs dhclient: send_packet: Network is unreachable
Aug 27 11:21:56 kmcs dhclient: send_packet: please consult README file regarding broadcast address.
Aug 27 11:21:56 kmcs dhclient: dhclient.c:2331: Failed to send 300 byte long packet over fallback interface.
Aug 27 11:21:56 kmcs kernel: [ 3120.291822] iwlwifi 0000:04:00.0: L1 Disabled - LTR Enabled
Aug 27 11:21:56 kmcs kernel: [ 3120.292054] iwlwifi 0000:04:00.0: L1 Disabled - LTR Enabled
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> (wlan0): supplicant interface state: inactive -> disabled
Aug 27 11:21:56 kmcs kernel: [ 3120.304172] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> (wlan0): supplicant interface state: disabled -> scanning
Aug 27 11:21:56 kmcs postfix/master[1660]: reload -- version 2.11.3, configuration /etc/postfix
Aug 27 11:21:56 kmcs dhclient:
Aug 27 11:21:56 kmcs wpa_supplicant[15630]: wlan0: CTRL-EVENT-TERMINATING
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> wpa_supplicant stopped
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> (wlan0): supplicant interface state: scanning -> down
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'supplicant-failed') [30 20 10]
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> (wlan0): deactivating device (reason 'supplicant-failed') [10]
Aug 27 11:21:56 kmcs NetworkManager[1235]: <warn> (wlan0): add_pending_action (2): 'waiting for supplicant' already pending
Aug 27 11:21:56 kmcs NetworkManager[1235]: file devices/nm-device.c: line 6328 (nm_device_add_pending_action): should not be reached
Aug 27 11:21:56 kmcs dbus[735]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Aug 27 11:21:56 kmcs dbus[735]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> wpa_supplicant started
Aug 27 11:21:56 kmcs wpa_supplicant[15749]: Successfully initialized wpa_supplicant
Aug 27 11:21:56 kmcs dhclient: Listening on LPF/eth0/80:fa:5b:09:15:77
Aug 27 11:21:56 kmcs dhclient: Sending on   LPF/eth0/80:fa:5b:09:15:77
Aug 27 11:21:56 kmcs dhclient: Sending on   Socket/fallback
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> (wlan0) supports 5 scan SSIDs
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> (wlan0): supplicant interface state: starting -> ready
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> (wlan0): supplicant interface state: ready -> disconnected
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> (wlan0) supports 5 scan SSIDs
Aug 27 11:21:56 kmcs kernel: [ 3120.498043] r8169 0000:05:00.2 eth0: link down
Aug 27 11:21:56 kmcs kernel: [ 3120.498173] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 27 11:21:56 kmcs NetworkManager[1235]: <info> (wlan0): supplicant interface state: disconnected -> disabled

.
Says network unreachable but WICD lists the networks reachables so the wifi card works.

I have another laptop under Wheezy that works fine on the same network:

Code: Select all

keynux:/home/kmc# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:90:f5:5c:1e:16  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:369098474 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interruption:17 Adresse de base:0x2c00 

lo        Link encap:Boucle locale  
          inet adr:127.0.0.1  Masque:255.0.0.0
          adr inet6: ::1/128 Scope:Hôte
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:23 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0 
          RX bytes:2054 (2.0 KiB)  TX bytes:2054 (2.0 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:19:d2:4a:b2:d2  
          inet adr:192.168.43.248  Bcast:192.168.43.255  Masque:255.255.255.0
          adr inet6: fe80::219:d2ff:fe4a:b2d2/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:2595 (2.5 KiB)  TX bytes:11955 (11.6 KiB)

keynux:/home/kmc# route
Table de routage IP du noyau
Destination     Passerelle      Genmask         Indic Metric Ref    Use Iface
default         192.168.43.1    0.0.0.0         UG    0      0        0 wlan0
192.168.43.0    *               255.255.255.0   U     0      0        0 wlan0
keynux:/home/kmc# ping 192.168.43.1
PING 192.168.43.1 (192.168.43.1) 56(84) bytes of data.
64 bytes from 192.168.43.1: icmp_req=1 ttl=64 time=1.73 ms
64 bytes from 192.168.43.1: icmp_req=2 ttl=64 time=1.18 ms
64 bytes from 192.168.43.1: icmp_req=3 ttl=64 time=1.17 ms

Any help greatl apreciated

[kmchen]

Seems there is nobody on that forum. Debain is dying

[kiyop]

How about checking if debian jessie live can connect to internet with the problematic wifi and problematic laptop?

If it can, how about installing jessie? Don't forget to backup your important data first.

Have you read thoroughly the given link: https://www.debian.org/releases/stable/ ... ng.en.html ?

WPA supplicant (on Arch Wiki): https://wiki.archlinux.org/index.php/WPA_supplicant

Seems there is nobody on that forum. Debain is dying

I can guess why you abuse debian and this forum.
But, you will be hated and won't get answers if you abuse this forum.

[Ardouos]

Seems there is nobody on that forum. Debain is dying

If no one wants to bother helping you from now on, this is why.

You have bot even posted any information on your sources, WiFi configuration, your hardware (and much more). Yet you claim "Debain" is dying? Heh...

This is a community forum, the Debian project has no affiliation with it.

[runfrodorun]

Seems there is nobody on that forum. Debain is dying

Many left with systemd.

Can we get your lspci? I doubt it, but there is a possibility you're using a card that got dropped

-RJ