# \[RÉSOLU\] Paquets pour install WIFI

**URL:** <https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755>\
**Category:** Pause Café\
**Created:** [Février 20, 2016, 7:12 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755 "2016-02-20T19:12:51Z")\
**Posts on this page:** 20\
**Page:** 9

<div class="post-metadata">

**Author:** ![Junichiro2](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/j/b5ac83/32.png) [@Junichiro2](https://www.debian-fr.org/u/Junichiro2)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/161 "2016-02-20T19:18:05Z")

</div>

J’ai déjà eu ce genre de truc durant le boot où ça cherche, ça cherche en dhcp. mais je crois que j’avais joué dans les paramètres réseau et avec network manager (Entre autre mettre en roaming). mais ceci était en mode graphique, sous gnome et avec network manager.

---

<div class="post-metadata">

**Author:** ![fran.b](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/f/d78d45/32.png) [@fran.b](https://www.debian-fr.org/u/fran.b)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/162 "2016-02-20T19:18:05Z")

</div>

Commence par blacklister ipv6 et désactives le de la freebox, j’ai fait ça sur mon portable (je ne me souviens plus la raison, gel de machine je crois) mais bon, un pbm à la fois, l’IPV6 n’est pas simple et tu n’en as pas besoin pour le moment…

---

<div class="post-metadata">

**Author:** ![ricardo](https://www.debian-fr.org/user_avatar/www.debian-fr.org/ricardo/32/3864_2.png) [@ricardo](https://www.debian-fr.org/u/ricardo)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/163 "2016-02-20T19:18:05Z")

</div>

Désactiver sur le portail Free, facile mais blacklister, où ❓❓❓

---

<div class="post-metadata">

**Author:** ![fran.b](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/f/d78d45/32.png) [@fran.b](https://www.debian-fr.org/u/fran.b)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/164 "2016-02-20T19:18:05Z")

</div>

echo “blacklist ipv6” \>\> /etc/modprobe.d/blacklist

---

<div class="post-metadata">

**Author:** ![ricardo](https://www.debian-fr.org/user_avatar/www.debian-fr.org/ricardo/32/3864_2.png) [@ricardo](https://www.debian-fr.org/u/ricardo)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/165 "2016-02-20T19:18:06Z")

</div>

Fait !  
N’y aurait-il pas quelque chose à faire de plus dans le mode routeur de la freebox ❓  
Voilà la copie-écran et la partie basse (1ere copie ecran) n’est pas remplie car je ne sais quoi y mettre

---

<div class="post-metadata">

**Author:** ![fran.b](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/f/d78d45/32.png) [@fran.b](https://www.debian-fr.org/u/fran.b)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/166 "2016-02-20T19:18:08Z")

</div>

Non, ça m’a l’air correct…

---

<div class="post-metadata">

**Author:** ![ricardo](https://www.debian-fr.org/user_avatar/www.debian-fr.org/ricardo/32/3864_2.png) [@ricardo](https://www.debian-fr.org/u/ricardo)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/167 "2016-02-20T19:18:10Z")

</div>

Portail Free :  
routage freebox correct  
essid et clef wep vérifiés = correct  
Que reste-t-il à contrôler ❓  
voici mon ‘interfaces’ simplissime :

[code]# This file describes the network interfaces available on your system

# and how to activate them. For more information, see interfaces(5).

# The loopback network interface

auto lo  
iface lo inet loopback  
address 127.0.0.1  
netmask 255.0.0.0

# The primary network interface

allow-hotplug eth0  
iface eth0 inet dhcp

auto wlan0  
iface wlan0 inet dhcp  
wireless-essid ricardowifi  
wireless-key 123456789  
[/code]

et résolv.conf

`nameserver 212.27.40.241
nameserver 212.27.40.240
`

si tout ça va bien, vers quel autre fichier il faut aller voir ❓

---

<div class="post-metadata">

**Author:** ![ricardo](https://www.debian-fr.org/user_avatar/www.debian-fr.org/ricardo/32/3864_2.png) [@ricardo](https://www.debian-fr.org/u/ricardo)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/168 "2016-02-20T19:18:11Z")

</div>

En ce moment, je suis sous wifi, cable ethernet débranché, mais … sous Kubuntu. ![:smt005](https://www.debian-fr.org/uploads/default/original/1X/cdd45e7dd754015ac5291329b843a2851a0d4fe8.gif)  
J’ai pratiquement tout comparé et c’est identique.  
En tous cas, on ne peut pas incriminer la freebox et sa configuration car rien n’a été modifié de ce côté.  
La seule chose qui pourrait être différente, c’est le module ❓  
À tous hasards, voici la fin de syslog, ptet que vous arriverez à y déchiffrer quelque chose :

`Mar 27 00:53:07 DDext-kub NetworkManager: <info> (eth0): device state change: 1 -> 2 
Mar 27 00:53:07 DDext-kub NetworkManager: <info> (eth0): bringing up device. 
Mar 27 00:53:07 DDext-kub kernel: [42.123296] ADDRCONF(NETDEV_UP): eth0: link is not ready
Mar 27 00:53:07 DDext-kub NetworkManager: <info> (eth0): preparing device. 
Mar 27 00:53:07 DDext-kub NetworkManager: <info> (eth0): deactivating device (reason: 2). 
Mar 27 00:53:07 DDext-kub NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) 
Mar 27 00:53:07 DDext-kub NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) 
Mar 27 00:53:07 DDext-kub NetworkManager: <info> (eth0): carrier now ON (device state 2) 
Mar 27 00:53:07 DDext-kub NetworkManager: <info> (eth0): device state change: 2 -> 3 
Mar 27 00:53:07 DDext-kub NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) 
Mar 27 00:53:07 DDext-kub NetworkManager: <info> (eth0): carrier now OFF (device state 3) 
Mar 27 00:53:07 DDext-kub NetworkManager: <info> (eth0): device state change: 3 -> 2 
Mar 27 00:53:07 DDext-kub NetworkManager: <info> (eth0): deactivating device (reason: 0). 
Mar 27 00:53:07 DDext-kub NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) 
Mar 27 00:53:07 DDext-kub nm-system-settings: Adding default connection 'Auto eth0' for /org/freedesktop/Hal/devices/net_00_22_19_df_1a_5d
Mar 27 00:53:07 DDext-kub kdm_greet[5892]: Cannot set locale. Translations will not work.
Mar 27 00:53:09 DDext-kub kernel: [43.743778] tg3: eth0: Link is up at 100 Mbps, full duplex.
Mar 27 00:53:09 DDext-kub kernel: [43.743789] tg3: eth0: Flow control is off for TX and off for RX.
Mar 27 00:53:09 DDext-kub NetworkManager: <info> (eth0): carrier now ON (device state 2) 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> (eth0): device state change: 2 -> 3 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Activation (eth0) starting connection 'Auto eth0' 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> (eth0): device state change: 3 -> 4 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> (eth0): device state change: 4 -> 5 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> (eth0): device state change: 5 -> 7 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Activation (eth0) Beginning DHCP transaction. 
Mar 27 00:53:09 DDext-kub kernel: [43.745132] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 27 00:53:09 DDext-kub NetworkManager: <info> dhclient started with pid 5901 
Mar 27 00:53:09 DDext-kub NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. 
Mar 27 00:53:09 DDext-kub dhclient: Internet Systems Consortium DHCP Client V3.1.1
Mar 27 00:53:09 DDext-kub dhclient: Copyright 2004-2008 Internet Systems Consortium.
Mar 27 00:53:09 DDext-kub dhclient: All rights reserved.
Mar 27 00:53:09 DDext-kub dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Mar 27 00:53:09 DDext-kub dhclient: 
Mar 27 00:53:09 DDext-kub dhclient: wmaster0: unknown hardware address type 801
Mar 27 00:53:09 DDext-kub NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit 
Mar 27 00:53:09 DDext-kub dhclient: wmaster0: unknown hardware address type 801
Mar 27 00:53:09 DDext-kub dhclient: Listening on LPF/eth0/00:22:19:df:1a:5d
Mar 27 00:53:09 DDext-kub dhclient: Sending on LPF/eth0/00:22:19:df:1a:5d
Mar 27 00:53:09 DDext-kub dhclient: Sending on Socket/fallback
Mar 27 00:53:09 DDext-kub kdm_greet[5892]: Cannot open default user face
Mar 27 00:53:10 DDext-kub kernel: [44.776121] wlan0: no IPv6 routers present
Mar 27 00:53:10 DDext-kub avahi-daemon[5295]: Registering new address record for fe80::222:19ff:fedf:1a5d on eth0.*.
Mar 27 00:53:12 DDext-kub dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Mar 27 00:53:12 DDext-kub dhclient: DHCPOFFER of 192.168.0.10 from 192.168.0.254
Mar 27 00:53:12 DDext-kub dhclient: DHCPREQUEST of 192.168.0.10 on eth0 to 255.255.255.255 port 67
Mar 27 00:53:12 DDext-kub dhclient: DHCPACK of 192.168.0.10 from 192.168.0.254
Mar 27 00:53:12 DDext-kub dhclient: bound to 192.168.0.10 -- renewal in 390151 seconds.
Mar 27 00:53:12 DDext-kub NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound 
Mar 27 00:53:12 DDext-kub NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... 
Mar 27 00:53:12 DDext-kub NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started... 
Mar 27 00:53:12 DDext-kub NetworkManager: <info> address 192.168.0.10 
Mar 27 00:53:12 DDext-kub NetworkManager: <info> prefix 24 (255.255.255.0) 
Mar 27 00:53:12 DDext-kub NetworkManager: <info> gateway 192.168.0.254 
Mar 27 00:53:12 DDext-kub NetworkManager: <info> nameserver '212.27.40.241' 
Mar 27 00:53:12 DDext-kub NetworkManager: <info> nameserver '212.27.40.240' 
Mar 27 00:53:12 DDext-kub NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... 
Mar 27 00:53:12 DDext-kub NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. 
Mar 27 00:53:12 DDext-kub NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... 
Mar 27 00:53:12 DDext-kub avahi-daemon[5295]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.10.
Mar 27 00:53:12 DDext-kub avahi-daemon[5295]: New relevant interface eth0.IPv4 for mDNS.
Mar 27 00:53:12 DDext-kub avahi-daemon[5295]: Registering new address record for 192.168.0.10 on eth0.IPv4.
Mar 27 00:53:13 DDext-kub NetworkManager: <info> (eth0): device state change: 7 -> 8 
Mar 27 00:53:13 DDext-kub NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS. 
Mar 27 00:53:13 DDext-kub NetworkManager: <info> Activation (eth0) successful, device activated. 
Mar 27 00:53:13 DDext-kub NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. 
Mar 27 00:53:13 DDext-kub ntpdate[5997]: adjust time server 91.189.94.4 offset 0.000022 sec
Mar 27 00:53:19 DDext-kub kernel: [54.080123] eth0: no IPv6 routers present
Mar 27 00:53:20 DDext-kub kernel: [55.196703] wlan0: authenticate with AP 82:b2:39:b2:9e:bc
Mar 27 00:53:20 DDext-kub dhclient: There is already a pid file /var/run/dhclient.wlan0.pid with pid 4688
Mar 27 00:53:20 DDext-kub kernel: [55.200783] wlan0: authenticated
Mar 27 00:53:20 DDext-kub kernel: [55.200797] wlan0: associate with AP 82:b2:39:b2:9e:bc
Mar 27 00:53:20 DDext-kub dhclient: killed old client process, removed PID file
Mar 27 00:53:20 DDext-kub dhclient: Internet Systems Consortium DHCP Client V3.1.1
Mar 27 00:53:20 DDext-kub dhclient: Copyright 2004-2008 Internet Systems Consortium.
Mar 27 00:53:20 DDext-kub dhclient: All rights reserved.
Mar 27 00:53:20 DDext-kub dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Mar 27 00:53:20 DDext-kub dhclient: 
Mar 27 00:53:20 DDext-kub dhclient: wmaster0: unknown hardware address type 801
Mar 27 00:53:20 DDext-kub dhclient: wmaster0: unknown hardware address type 801
Mar 27 00:53:20 DDext-kub dhclient: Listening on LPF/pan0/62:66:d1:10:1f:31
Mar 27 00:53:20 DDext-kub dhclient: Sending on LPF/pan0/62:66:d1:10:1f:31
Mar 27 00:53:20 DDext-kub kernel: [55.209604] wlan0: RX ReassocResp from 82:b2:39:b2:9e:bc (capab=0x411 status=0 aid=1)
Mar 27 00:53:20 DDext-kub kernel: [55.209616] wlan0: associated
Mar 27 00:53:20 DDext-kub kernel: [55.209706] wlan0 (WE) : Wireless Event too big (338)
Mar 27 00:53:20 DDext-kub dhclient: Listening on LPF/wmaster0/
Mar 27 00:53:20 DDext-kub dhclient: Sending on LPF/wmaster0/
Mar 27 00:53:20 DDext-kub dhclient: Listening on LPF/wlan0/00:22:fb:17:d2:48
Mar 27 00:53:20 DDext-kub dhclient: Sending on LPF/wlan0/00:22:fb:17:d2:48
Mar 27 00:53:20 DDext-kub dhclient: Listening on LPF/eth0/00:22:19:df:1a:5d
Mar 27 00:53:20 DDext-kub dhclient: Sending on LPF/eth0/00:22:19:df:1a:5d
Mar 27 00:53:20 DDext-kub dhclient: Sending on Socket/fallback
Mar 27 00:53:20 DDext-kub dhclient: Internet Systems Consortium DHCP Client V3.1.1
Mar 27 00:53:20 DDext-kub dhclient: Copyright 2004-2008 Internet Systems Consortium.
Mar 27 00:53:20 DDext-kub dhclient: All rights reserved.
Mar 27 00:53:20 DDext-kub dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Mar 27 00:53:20 DDext-kub dhclient: 
Mar 27 00:53:20 DDext-kub dhclient: wmaster0: unknown hardware address type 801
Mar 27 00:53:20 DDext-kub avahi-daemon[5295]: Withdrawing address record for 192.168.0.12 on wlan0.
Mar 27 00:53:20 DDext-kub avahi-daemon[5295]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.12.
Mar 27 00:53:20 DDext-kub avahi-daemon[5295]: Interface wlan0.IPv4 no longer relevant for mDNS.
Mar 27 00:53:21 DDext-kub dhclient: wmaster0: unknown hardware address type 801
Mar 27 00:53:21 DDext-kub dhclient: Listening on LPF/wlan0/00:22:fb:17:d2:48
Mar 27 00:53:21 DDext-kub dhclient: Sending on LPF/wlan0/00:22:fb:17:d2:48
Mar 27 00:53:21 DDext-kub dhclient: Sending on Socket/fallback
Mar 27 00:53:24 DDext-kub dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Mar 27 00:53:24 DDext-kub dhclient: DHCPOFFER of 192.168.0.12 from 192.168.0.254
Mar 27 00:53:24 DDext-kub dhclient: DHCPREQUEST of 192.168.0.12 on wlan0 to 255.255.255.255 port 67
Mar 27 00:53:24 DDext-kub dhclient: DHCPACK of 192.168.0.12 from 192.168.0.254
Mar 27 00:53:24 DDext-kub avahi-daemon[5295]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.12.
Mar 27 00:53:24 DDext-kub avahi-daemon[5295]: New relevant interface wlan0.IPv4 for mDNS.
Mar 27 00:53:24 DDext-kub avahi-daemon[5295]: Registering new address record for 192.168.0.12 on wlan0.IPv4.
Mar 27 00:53:24 DDext-kub dhclient: bound to 192.168.0.12 -- renewal in 414682 seconds.
Mar 27 00:53:29 DDext-kub python: hp-systray(init)[6278]: warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
Mar 27 00:56:35 DDext-kub kernel: [250.124224] CE: hpet increasing min_delta_ns to 15000 nsec
Mar 27 00:58:03 DDext-kub anacron[5741]: Job `cron.daily' started
Mar 27 00:58:04 DDext-kub anacron[6678]: Updated timestamp for job `cron.daily' to 2009-03-27
Mar 27 01:00:01 DDext-kub /USR/SBIN/CRON[6824]: (root) CMD ([-x /usr/sbin/update-motd] && /usr/sbin/update-motd 2>/dev/null)
`

Un warning aussi ds dmesg :

```auto

```

---

<div class="post-metadata">

**Author:** ![cherif19691](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/c/65b543/32.png) [@cherif19691](https://www.debian-fr.org/u/cherif19691)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/169 "2016-02-20T19:18:11Z")

</div>

Salut

que dit network-admin ?  
que dit ifconfig ?  
tu es toujours sur l’adresse mac de la freebox ?  
reste en ipfixe sur ton portable avec la passerelle qui faut à savoir 192.168.0.254  
les redirections au niveau freebox tu n’as pas à toucher et ipv6 aussi .

si ça marche bien avec un cdlive linux alors à mon avis tu n’as pas mis les bons pilotes pour ta carte wifi .  
avec un cdlive , que donne : ifconfig ?

je suis en wifi , mais moi c’est eth1 et j’ai jamais eu wlan .

---

<div class="post-metadata">

**Author:** ![fran.b](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/f/d78d45/32.png) [@fran.b](https://www.debian-fr.org/u/fran.b)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/170 "2016-02-20T19:18:13Z")

</div>

cherif: le nom dépend du pilote, iwlang donne du wlan.

Ricardo: C’est bien un pbm de pilote et/ou de firmware. Tu peux éventuellement faire trois choses:

- Essayer avec les firmware de ton CD-live.
- Récupérer le noyau du CD live
- Recompiler un module

---

<div class="post-metadata">

**Author:** ![cherif19691](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/c/65b543/32.png) [@cherif19691](https://www.debian-fr.org/u/cherif19691)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/171 "2016-02-20T19:18:14Z")

</div>

Merci fran.b pour cette info

---

<div class="post-metadata">

**Author:** ![bobzer](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/b/41988e/32.png) [@bobzer](https://www.debian-fr.org/u/bobzer)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/172 "2016-02-20T19:18:16Z")

</div>

ricardo moi je suis sous kde avec une lenny et un noyau 64 bit en 2.6.28.7 (que j’ai donc compilé) si tu veut je peut te passer ma conf de noyau ou carrement le noyau et les headers (j’ai fait les deux paquets)  
et pour info moi avec le lien que je t’avais donné (que d’ailleurs j’ai trouve dans ce poste meme) tout fonctionne tres bien

---

<div class="post-metadata">

**Author:** ![ricardo](https://www.debian-fr.org/user_avatar/www.debian-fr.org/ricardo/32/3864_2.png) [@ricardo](https://www.debian-fr.org/u/ricardo)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/173 "2016-02-20T19:18:22Z")

</div>

Réponse en vrac :  
Vous avez ptet mal interprété ce que j’ai dit : je ne suis pas sous un live mais sous UBUNTU qui est installé sur mon DDext branché sur mon portable avec cable Sata.  
Je pense donc que si je dois chercher à installer quelque chose sur ma debian sid, je dois aller trouver cette “chose” sur ma UBUNTU (en l’occurence Kubuntu), non ❓  
voici le noyau :

`ricardo@DDext-kub:~$ uname -r
2.6.27-11-generic
`  
éventuellement :

`ricardo@DDext-kub:~$ lsmod | grep iwl
iwlagn 99716 0
iwlcore 94532 1 iwlagn
rfkill 17176 2 iwlcore
led_class 12164 1 iwlcore
mac80211 216820 2 iwlagn,iwlcore
cfg80211 32392 3 iwlagn,iwlcore,mac80211
`

Si j’ai mal compris, que me faut-il faire pour aller chercher ce qui ne va pas sous debian ❓

---

<div class="post-metadata">

**Author:** ![fran.b](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/f/d78d45/32.png) [@fran.b](https://www.debian-fr.org/u/fran.b)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/174 "2016-02-20T19:18:28Z")

</div>

Tu essayes d’abord en prenant le firmware Ubuntu, puis si ça ne marche pas tu peux installer le noyau Ubuntu (penses juste à refaire l’initrd)

---

<div class="post-metadata">

**Author:** ![ricardo](https://www.debian-fr.org/user_avatar/www.debian-fr.org/ricardo/32/3864_2.png) [@ricardo](https://www.debian-fr.org/u/ricardo)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/175 "2016-02-20T19:18:28Z")

</div>

Excuse mon ignorance mais comment je fais pour aller le chercher ce firmware, sur mon installation où sur leur site ❓  
EDIT :  
je ne l’avais pas trouvé mais je ne cherchais pas au bon endroit et surtout pas avec le bon nom linux-wlan-ng-firmware.  
je vais aller y voir de plus près. là je suis de retour sous debian

---

<div class="post-metadata">

**Author:** ![ricardo](https://www.debian-fr.org/user_avatar/www.debian-fr.org/ricardo/32/3864_2.png) [@ricardo](https://www.debian-fr.org/u/ricardo)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/176 "2016-02-20T19:18:28Z")

</div>

Ben je suis désemparé car retour sous Kubuntu / recherche linux-wlan = 4 paquets mais aucun d’eux n’est installé alors je me demande s’ils sont utiles ?  
linux-wlan-ng  
linux-wlan-ng-firmware  
linux-wlan-ng-doc  
linux-wlan-ng-source  
💡

---

<div class="post-metadata">

**Author:** ![fran.b](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/f/d78d45/32.png) [@fran.b](https://www.debian-fr.org/u/fran.b)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/177 "2016-02-20T19:18:30Z")

</div>

Regarde ce qu’il y a dans /lib/firmware et si dmesg, syslog ou kern.log indique le firmware chargé. (Peut être que le module n’en charge pas)

---

<div class="post-metadata">

**Author:** ![ricardo](https://www.debian-fr.org/user_avatar/www.debian-fr.org/ricardo/32/3864_2.png) [@ricardo](https://www.debian-fr.org/u/ricardo)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/178 "2016-02-20T19:18:31Z")

</div>

seule indication = dmesg (pareil ailleurs)  
ça juste après être passé de eth0 à wlan0 :

` 17.930753] ip_tables: (C) 2000-2006 Netfilter Core Team
[17.966118] iwlagn 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[17.966195] iwlagn 0000:04:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106)
[17.966346] firmware: requesting iwlwifi-5000-1.ucode
[20.119701] ACPI: EC: missing confirmations, switch off interrupt mode.
[20.158838] Registered led device: iwl-phy0:radio
[20.158858] Registered led device: iwl-phy0:assoc
[20.158882] Registered led device: iwl-phy0:RX
[20.158904] Registered led device: iwl-phy0:TX
[21.318765] NET: Registered protocol family 17
[21.906166] wlan0: authenticate with AP 82:b2:39:b2:9e:bc
[21.908341] wlan0: authenticated
[21.908345] wlan0: associate with AP 82:b2:39:b2:9e:bc
[21.917202] wlan0: RX AssocResp from 82:b2:39:b2:9e:bc (capab=0x411 status=0 aid=1)
[21.917206] wlan0: associated
[21.917258] wlan0 (WE) : Wireless Event too big (338)
[31.991169] NET: Registered protocol family 10
[31.991594] lo: Disabled Privacy Extensions
`

Dans /lib/firmware, ce fichier existe :  
iwlwifi-5000-1.ucode  
c’est un exécutable mais qu’en faire ❓

Dans ma debian, j’ai aussi ce paquet dans /lib/firmware mais est-ce le même ❓

EDIT :  
absent demain (Tlse 🙂 ), retour dimanche soir.

---

<div class="post-metadata">

**Author:** ![cherif19691](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/c/65b543/32.png) [@cherif19691](https://www.debian-fr.org/u/cherif19691)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/179 "2016-02-20T19:18:32Z")

</div>

salut  
a tester :  
– reboute 5 fois la freebox

– toutes les versions de clé .

– desactive le dhcp freebox et met toi en ipfixe et debranche le boitier hd

si ça marche pas :

– cdlive whax de préférence ,

tu nous as jamais donné l’adresse mac de ta freeox … c’est laquelle

---

<div class="post-metadata">

**Author:** ![fran.b](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/f/d78d45/32.png) [@fran.b](https://www.debian-fr.org/u/fran.b)\
**Post date:** [Février 20, 2016, 7:18 UTC](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755/180 "2016-02-20T19:18:32Z")

</div>

Le fichier iwlwifi-5000-1.ucode est le firmware. COmpare les deux fichiers (celui sur ta ubuntu et celui de ta debian) via md5sum. Si ils sont différents, essaye avec le firmware Ubuntu.  
Si vraiement ça ne marche pas, tu peux installer le noyau ubuntu

[Page précédente](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755.md?page=8)

[Page suivante](https://www.debian-fr.org/t/resolu-paquets-pour-install-wifi/18755.md?page=10)
