Crack-wifi.com FORUM

LE FORUM DU SITE

Wifi, Backtrack, crack WEP et WPA...

Vous n'êtes pas identifié(e).  

Annonce

Visitez la boutique Wifi-highpower.com, votre revendeur agr Alfa Network: du matriel Wifi slectionn, cartes Wifi USB Awus036h et Awus036nh, antennes omnis, yagis, panel, amplis wifi, accessoires...

#1 14-01-2011 18:03:33

Shipping LAN
Membre
Lieu : Annecy
Inscription : 12-01-2011
Messages : 19

Channel bonding sur BT4 ?

Bonjour,

J'ai 2 cartes wifi (celle de mon PC portable et une clé USB wifi SAGEM).
Chacune est connectée à une box internet différente.

J'ai trouvé un tuto très bien fait sous Debian pour pouvoir réaliser une agrégation de lien et ainsi doubler sa bande passante. Problème : lors de l'installation Debian ne reconnait pas ma carte ethernet, et IMPOSSIBLE de trouver le driver... bref du coup j'ai abandonné Debian.

Est-ce possible de faire du channel bonding sous BT4, afin de doubler sa bande passante (dans la mesure où les 2 box ont quasiment la même BP) ?

Dernière modification par Shipping LAN (14-01-2011 18:05:06)


Shipping LAN

Étudiant en 1ère année de D.U.T. Réseaux et Télécommunications

Hors Ligne

Annonce

Visitez la boutique Wifi-highpower.com, votre revendeur agr Alfa Network: du matriel Wifi slectionn, cartes Wifi USB Awus036h et Awus036nh, antennes omnis, yagis, panel, amplis wifi, accessoires...

#2 14-01-2011 23:20:04

antares145
Membre d'honneur
Inscription : 29-09-2009
Messages : 5 199
Site Web

Re : Channel bonding sur BT4 ?

Salut

Je n'ai jamais étudié la possibilité de faire du CB sur BackTrack, donc je ne pense pas que je serai d'une grande aide hmm Par contre, BackTrack est basée sur Ubuntu, qui est elle-même basée sur Debian ; peut-être que ton tutoriel est adaptable directement à BT4, mais à mon avis il faudra quelques ajustements...

Tu peux aussi jeter un oeil à cet autre tuto, qui a l'air plus simple --> Channel bonding wireless et ethernet
Là encore, il y aura quelques adaptations à faire pour remplacer l'ethernet par la deuxième interface wlan, et si tu es en WPA il faudra chipoter un peu parce que tu ne peux pas passer par iwconfig, mais rien d'insurmontable smile

Essaie déjà avec ça, et tiens nous au courant du résultat !

Hors Ligne

#3 16-01-2011 19:04:02

Shipping LAN
Membre
Lieu : Annecy
Inscription : 12-01-2011
Messages : 19

Re : Channel bonding sur BT4 ?

J'ai commencé, et voilà mes premières questions (les citations viennent du tuto que tu m'as donné) :

Le but de la manoeuvre était de me permettre de rester connecté sur un portable équipé d'une dongle wifi et d'une carte ethernet
Dans la mesure où je n'ai pas de connexion ethernet mais seulement 2 interfaces WIFI, je pense que son script n'est pas bon. J'ai essayé de le comprendre, mais beaucoup de choses m'échappent encore.
Je vais avancé d'étapes en étapes :

J'ai modifié en premier lieu le fichier /etc/network/interfaces en ne déclarant que l'interface de loopback.
Ça ça a été OK : j'ai bêtement supprimé tout le reste sauf "auto lo , iface lo inet loopback"

Puis j'ai ajouté dans /etc/rc2.d un script de démarrage nommé S20bonding qui pointe vers /etc/init.d/bonding
J'ai copié/collé le script qu'il propose, en modifiant l'essid et la key.

- Maintenant, dois-je modifier BOND_ADDR="192.168.0.75/24" et LISTE_ETH="wlan0 eth0" ? Dans la mesure où je ne suis pas concerné par une liaison Ethernet filaire, le LISTE_ETH="wlan0 eth0" n'a pas sa place dans le script non ?
Aussi, que représente cette adresse IP : BOND_ADDR="192.168.0.75/24" ?

- Pour faire le script, j'ai "créer un nouveau fichier texte" nommé S20bonding dans /etc/rc2.d, copié/collé, puis enregistré. Seulement comment le "faire pointer vers /etc/init.d/bonding" ?

Je n'ai pas pu aller plus loin...

Dernière modification par Shipping LAN (16-01-2011 19:05:37)


Shipping LAN

Étudiant en 1ère année de D.U.T. Réseaux et Télécommunications

Hors Ligne

#4 16-01-2011 21:43:32

antares145
Membre d'honneur
Inscription : 29-09-2009
Messages : 5 199
Site Web

Re : Channel bonding sur BT4 ?

Bon, avant tout je tiens à signaler que tu t'attaques à un sujet qui dépasse largement le cadre d'apprentissage du débutant que tu es sensé être big_smile
J'ai peu entendu parler du channel bonding jusqu'ici, je n'ai jamais regardé ça de près et je ne connais personne qui ait essayé de mettre ça en place (encore moins sous BackTrack). Tu peux pas demander comment installer MSN comme tout le monde ? tongue
Bon, on va quand même essayer de voir si on arrive à quelque chose wink

Le problème pour adapter les différents tutos au WiFi, c'est qu'en matière de sans-fil le channel bonding c'est tout à fait autre chose (fusionner 2 canaux de 20 MHz en 1 seul de 40 MHz pour augmenter la Bande Passante radio), donc Google n'est pas d'une grande aide. Y a quelques liens que je dois encore zieuter, mais j'ai rien de concret pour toi pour l'instant...

Avant d'automatiser tout ça avec des /etc/rc (les scripts /etc/rc.* et /etc/init.d sont les scripts lancés au démarrage du système) on va essayer de faire marcher le truc de façon simple. Donc je te propose un autre lien, qui a l'avantage de détailler les modes du CB --> Tutoriel : Mettre en place du channel bonding
Nous ici je pense que c'est le mode 4 qui nous intéresse, mais je ne sais pas s'il est supporté par le WiFi. Au pire, on se rabattra sur le mode 0. Allez hop, on met ses gants et on est partis *craquement de phalanges*, voilà comment je propose d'adapter le script proposé sur le lien sus-mentionné :

- tu connectes tes 2 interfaces à leurs réseaux respectifs (au passage, tu as quoi comme sécurité sur chaque lien ? OPN, WEP, WPA ?)
- tu charges le module kivabien et tu lui donnes ses options :

modprobe bonding mode=4 miimon=100

- tu coupes la liaison IP des 2 interfaces (elles restent configurées, mais le système ne peut pas s'en servir) :

ifconfig wlan0 down	
ifconfig wlan1 down

(en supposant que wlan0 et wlan1 sont tes interfaces, évidemment)
- tu crées une interface bond0 avec une Mac au hasard (temporairement)

ifconfig bond0 hw ether 11:22:33:44:55:66

- tu donnes une adresse IP et une passerelle à notre interface bond0

ifconfig bond0 192.168.0.4 netmask 255.255.255.0 gateway 192.168.0.254 up

- tu intègres tes 2 interfaces WiFi à l'interface bond0 :

ifenslave bond0 wlan0
ifenslave bond0 wlan1

Normalement avec ça on est bons. Fais un test et dis-nous ce que ça raconte, si ça marche on verra à mettre tout ça en script proprement mais j'aime autant débugger sur une base "simple" wink
Note que tu peux intégrer toutes les commandes dans un script unique (comme dans le lien), tu copies-colles dans un fichier [c]bonding.sh[/c], ensuite dans une console tu tapes la commande "[c]chmod +x bonding.sh[/c]" pour en autoriser l'exécution.

Ca va, l'apprentissage accéléré en Linux, tu suis toujours ? big_smile

Hors Ligne

#5 16-01-2011 22:08:38

Shipping LAN
Membre
Lieu : Annecy
Inscription : 12-01-2011
Messages : 19

Re : Channel bonding sur BT4 ?

antares145 a écrit :

- tu connectes tes 2 interfaces à leurs réseaux respectifs (au passage, tu as quoi comme sécurité sur chaque lien ? OPN, WEP, WPA ?)

J'en ai un en WEP et l'autre en WPA.

- tu charges le module kivabien

Le module ? quel module ?


Shipping LAN

Étudiant en 1ère année de D.U.T. Réseaux et Télécommunications

Hors Ligne

#6 16-01-2011 22:23:17

antares145
Membre d'honneur
Inscription : 29-09-2009
Messages : 5 199
Site Web

Re : Channel bonding sur BT4 ?

Mouais, le WPA sera peut-être un peu casse-cou*lle à automatiser mais avec [c]wpa_supplicant[/c] ça devrait passer...

La commande "[c]modprobe[/c]" sert à charger le module passé en argument (exemple : "modprobe iwlagn"). Ici, on parle donc bien du module "bonding" grâce à la commande "[c]modprobe bonding mode=5 miimon=100[/c]".

Dans chacune des étapes que je te donne, je commence par décrire ce qu'on va faire puis je donne la/les commande(s) pour le faire smile

Hors Ligne

#7 16-01-2011 22:59:07

Shipping LAN
Membre
Lieu : Annecy
Inscription : 12-01-2011
Messages : 19

Re : Channel bonding sur BT4 ?

antares145 a écrit :

Ca va, l'apprentissage accéléré en Linux, tu suis toujours ? big_smile

Oui oui smile
Je m'efforce de poser les bonnes questions pour pouvoir avancer au mieux... pour le moment je ne m'en plait pas big_smile



Après avoir taper tes commandes, je fais un petit iwconfig + ifconfig et voilà ce que ça me donne :

[email protected]:~# ifconfig
bond0     Link encap:Ethernet  HWaddr aa:bb:cc:dd:ee:aa
          inet6 addr: fe80::a8bb:ccff:fedd:eeaa/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:1533 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1387 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1393400 (1.3 MB)  TX bytes:228337 (228.3 KB)

eth0      Link encap:Ethernet  HWaddr 54:42:49:61:fc:e3
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:18

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1484 (1.4 KB)  TX bytes:1484 (1.4 KB)

wlan0     Link encap:Ethernet  HWaddr aa:bb:cc:dd:ee:aa
          inet addr:192.168.1.186  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:51 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5421 (5.4 KB)  TX bytes:6179 (6.1 KB)

wlan1     Link encap:Ethernet  HWaddr aa:bb:cc:dd:ee:aa
          inet addr:192.168.0.16  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:1482 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1347 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1387979 (1.3 MB)  TX bytes:222158 (222.1 KB)







[email protected]:~# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan1     IEEE 802.11bgn  ESSID:"RocknRollDecadence"
          Mode:Managed  Frequency:2.422 GHz  Access Point: 0E:B7:8B:A5:EA:14
          Bit Rate=150 Mb/s   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=59/70  Signal level=-51 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

bond0     no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"DartyBox_7C64_WEP"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 06:23:08:3D:61:4D
          Bit Rate=1 Mb/s   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:394C-3347-4550-4552-5454-3754-52
          Power Management:off
          Link Quality=45/70  Signal level=-65 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Au final, je suis bien connecté sur les 2 boxs, mais je ne peux pas surfer sur internet... bizarre ?

Dernière modification par Shipping LAN (16-01-2011 23:00:03)


Shipping LAN

Étudiant en 1ère année de D.U.T. Réseaux et Télécommunications

Hors Ligne

#8 16-01-2011 23:16:17

antares145
Membre d'honneur
Inscription : 29-09-2009
Messages : 5 199
Site Web

Re : Channel bonding sur BT4 ?

Bon bon bon... Déjà, comment ça se fait que tes 2 interfaces wlan* ont la même adresse MAC ? T'as changé ça toi-même ou bien c'est une conséquence du bonding (je penche pour la deuxième proposition). Bon, elles ne sont pas sur le même réseau donc ça ne devrait pas poser problème, mais peut-être qu'on devra changer ça par la suite...

Le problème ici est à la fois simple et complexe : simple parce que c'est bond0 qui n'a pas d'adresse IP (pas d'adresse pas de surf), compliqué parce que je sais pas pourquoi big_smile On dirait qu'il n'a pas tenu compte de cette commande (retape-la un coup pour vérifier) :

ifconfig bond0 192.168.0.4 netmask 255.255.255.0 gateway 192.168.0.254 up

Tu vois la ligne "inet addr:192.168. [...]" de tes 2 interfaces wlan ? Il faut qu'il y aie le même genre pour bond0.

Le truc, c'est que là on lui donne une adresse sur le même sous-réseau (192.168.0.*) qu'une des 2 interfaces, sans doute pas une bonne idée. Si la commande ci-dessus ne donne rien, tente sur un autre sous-réseau :

ifconfig bond0 192.168.42.4 netmask 255.255.255.0 gateway 192.168.42.254 up

Si ça ne marche toujours pas, on va recommencer avec le bonding en mode 0, ça passera peut-être mieux. En rapide ça donne ça :

ifconfig bond0 down #désactiver bond0
modprobe -r bonding #décharger le module
modprobe bonding mode=0 miimon=100 
ifconfig wlan0 down	
ifconfig wlan1 down	
ifconfig bond0 hw ether 11:22:33:44:55:66
ifconfig bond0 192.168.42.4 netmask 255.255.255.0 gateway 192.168.42.254 up
ifenslave bond0 wlan0
ifenslave bond0 wlan1

Une fois que t'as fait ça, regarde si bond0 a bien son IP comme prévu, et regarde si tu sais aller sur le net. Si ce n'est pas le cas, copie-moi la même chose qu'au dessus, avec aussi le résultat de la commande "route".

Au passage, je sais pas si tu gagneras grand chose avec ton bonding, la bande passante sur wlan1 a l'air beaucoup moins bonne que wlan0 (seulement 1 MBps). Mais c'est peut-être juste une illusion d'optique smile

Hors Ligne

#9 16-01-2011 23:44:19

Shipping LAN
Membre
Lieu : Annecy
Inscription : 12-01-2011
Messages : 19

Re : Channel bonding sur BT4 ?

Voilà ce que ça donne avec le bonding en mode 0 :
(quand je rentre l'adresse IP pour le bond0, il ne reconnait pas l'option gateway, elle n'existe pas... du coup je tape la ligne de commande sans le gateway 192.168.42.254)

[email protected]:~# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan1     IEEE 802.11bgn  ESSID:"DartyBox_7C64_WEP"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 06:23:08:3D:61:4D
          Bit Rate=1 Mb/s   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:394C-3347-4550-4552-5454-3754-52
          Power Management:off
          Link Quality=48/70  Signal level=-62 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

wlan0     IEEE 802.11bg  ESSID:"RocknRollDecadence"
          Mode:Managed  Frequency:2.422 GHz  Access Point: 0E:B7:8B:A5:EA:14
          Bit Rate=1 Mb/s   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=63/70  Signal level=-47 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

bond0     no wireless extensions.




[email protected]:~# ifconfig
bond0     Link encap:Ethernet  HWaddr aa:bb:cc:dd:ee:aa
          inet addr:192.168.42.4  Bcast:192.168.42.255  Mask:255.255.255.0
          inet6 addr: fe80::a8bb:ccff:fedd:eeaa/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:10576 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9383 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10440345 (10.4 MB)  TX bytes:1455035 (1.4 MB)

eth0      Link encap:Ethernet  HWaddr 54:42:49:61:fc:e3
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:18

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:162 errors:0 dropped:0 overruns:0 frame:0
          TX packets:162 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:15990 (15.9 KB)  TX bytes:15990 (15.9 KB)

wlan0     Link encap:Ethernet  HWaddr aa:bb:cc:dd:ee:aa
          inet addr:192.168.0.16  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:37 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9387 (9.3 KB)  TX bytes:9356 (9.3 KB)

wlan1     Link encap:Ethernet  HWaddr aa:bb:cc:dd:ee:aa
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:10539 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9325 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10430958 (10.4 MB)  TX bytes:1445679 (1.4 MB)




[email protected]:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 wlan0
192.168.42.0    *               255.255.255.0   U     0      0        0 bond0

EDIT : sinon aucun changement ! malgré qu'on puisse voir une adresse IP pour le bond0, je ne peux toujours pas avoir accès au net... bizarre again ? hmm

[EDIT] je vais me coucher, je commence très tôt demain... j'espère qu'on va y arriver big_smile

Dernière modification par Shipping LAN (17-01-2011 00:00:26)


Shipping LAN

Étudiant en 1ère année de D.U.T. Réseaux et Télécommunications

Hors Ligne

#10 17-01-2011 00:08:42

antares145
Membre d'honneur
Inscription : 29-09-2009
Messages : 5 199
Site Web

Re : Channel bonding sur BT4 ?

Non, ce n'est pas bizarre dans le sens où ta commande "tronquée" ne spécifie pas de passerelle. Comme la passerelle sert à définir par où tout le trafic doit passer (pour partir sur le net), c'est normal que tu ne puisses pas accéder au réseau wink

C'est curieux qu'ifconfig ne prenne plus l'option "gateway". Tant pis, on peut la remplacer par la commande "route". Par contre, plus j'y pense et plus je me dis que si on donne une IP bidon à bond0, y a aucune raison qu'elle arrive à trouver son chemin toute seule...
Ce qu'on va quand même essayer, c'est de donner une IP "valide" (c-à-d sur le même subnet qu'une des 2 wlan) à bond0, et la passerelle qui va bien. Donc ça donne :

ifconfig bond0 192.168.0.42 netmask 255.255.255.0
route add default gw 192.168.0.254

Hé mais attends... Rhaaaaaaa, mais pourquoi wlan1 a perdu son IP maintenant ?! 2873.gif
C'est le problème, comme je parle de quelque chose que je ne connais pas (le channel bonding) je ne comprends pas exactement tout ce qui se passe, et donc je sais pas du tout si c'est normal (conséquence du bonding) ou si c'est une autre cou*lle dans le pâté sad

Bon. Calme, cool, zen, lexomil. Essaie ce que j'ai proposé juste au dessus, et si ça ne marche pas, désactive bond0 (ifconfig bond0 down), reconnecte tes 2 interfaces WiFi, réactive le bond0 (avec modprobe) en mode 4 puisque là au moins on a une IP sur chaque wlan, et ensuite tape les commandes suivantes :

ifconfig bond0 192.168.0.42 netmask 255.255.255.0
route add default gw 192.168.0.254

Après, tu essaies un "ping extérieur" (par exemple ping 8.8.8.8), et tu vois si ça passe ou si t'es en "network unreachable". Si ça ne passe pas, essaie de ping'er ta passerelle (ping 192.168.0.254), je suis pas sûr que c'est cette adresse-là. C'est quoi comme box ?

Après tout ça, redonne moi les commandes habituelles (ifconfig, iwconfig et route). Demain j'essaierai de faire du CB de mon côté pour chipoter un peu sur les détails. Enfin, j'essayerai (je pense pas que j'aurai le temps...)

[EDIT] Tant que j'y pense, tu devrais jeter un œil (et éventuellement donner une copie) des dernières lignes de "dmesg", après avoir formé bond0. Apparemment, le statut de réussite ou d'échec s'y trouve avec quelques explications wink

Hors Ligne

#11 17-01-2011 18:23:13

Shipping LAN
Membre
Lieu : Annecy
Inscription : 12-01-2011
Messages : 19

Re : Channel bonding sur BT4 ?

Résultat : iwconfig

[email protected]:~# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"DartyBox_7C64_WEP"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 06:23:08:3D:61:4D
          Bit Rate=54 Mb/s   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:394C-3347-4550-4552-5454-3754-52
          Power Management:off
          Link Quality=55/70  Signal level=-55 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

wlan1     IEEE 802.11bg  ESSID:"RocknRollDecadence"
          Mode:Managed  Frequency:2.422 GHz  Access Point: 0E:B7:8B:A5:EA:14
          Bit Rate=11 Mb/s   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=61/70  Signal level=-49 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

bond0     no wireless extensions.

Je trouve bizarre que bond0 ne soit pas considéré comme une interface wifi, nan ?

Résultat : ifconfig

[email protected]:~# ifconfig
bond0     Link encap:Ethernet  HWaddr aa:bb:cc:dd:ee:ff
          inet addr:192.168.0.42  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::a8bb:ccff:fedd:eeff/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:3065 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2006 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1344032 (1.3 MB)  TX bytes:269264 (269.2 KB)

eth0      Link encap:Ethernet  HWaddr 54:42:49:61:fc:e3
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:18

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:254 errors:0 dropped:0 overruns:0 frame:0
          TX packets:254 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:25712 (25.7 KB)  TX bytes:25712 (25.7 KB)

wlan0     Link encap:Ethernet  HWaddr aa:bb:cc:dd:ee:ff
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:2805 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1709 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1330126 (1.3 MB)  TX bytes:246654 (246.6 KB)

wlan1     Link encap:Ethernet  HWaddr aa:bb:cc:dd:ee:ff
          inet addr:192.168.0.17  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:260 errors:0 dropped:0 overruns:0 frame:0
          TX packets:297 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13906 (13.9 KB)  TX bytes:22610 (22.6 KB)

Là on voit bien que bond0, wlan0 et wlan1 ont la même adresse MAC... Pourtant je n'ai pas accès au web.
Je n'arrive pas à pinguer mes box (une FreeBox, l'autre est une DartyBox).


Résultat : route

[email protected]:~# route add default gw 192.168.0.254
SIOCADDRT: File exists


[email protected]:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 bond0
192.168.0.0     *               255.255.255.0   U     0      0        0 wlan1

Je ne comprend pas le message : SIOCADDRT: File exists


Résultat : dmseg

[email protected]:~# dmseg
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009e800 (usable)
 BIOS-e820: 000000000009e800 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000dee7c000 (usable)
 BIOS-e820: 00000000dee7c000 - 00000000deebc000 (ACPI NVS)
 BIOS-e820: 00000000deebc000 - 00000000deecd000 (reserved)
 BIOS-e820: 00000000deecd000 - 00000000deedf000 (ACPI NVS)
 BIOS-e820: 00000000deedf000 - 00000000deee0000 (reserved)
 BIOS-e820: 00000000deee0000 - 00000000deee3000 (ACPI NVS)
 BIOS-e820: 00000000deee3000 - 00000000def11000 (reserved)
 BIOS-e820: 00000000def11000 - 00000000def12000 (ACPI NVS)
 BIOS-e820: 00000000def12000 - 00000000def15000 (reserved)
 BIOS-e820: 00000000def15000 - 00000000def17000 (ACPI NVS)
 BIOS-e820: 00000000def17000 - 00000000def1b000 (reserved)
 BIOS-e820: 00000000def1b000 - 00000000def1e000 (ACPI data)
 BIOS-e820: 00000000def1e000 - 00000000def22000 (reserved)
 BIOS-e820: 00000000def22000 - 00000000def31000 (ACPI NVS)
 BIOS-e820: 00000000def31000 - 00000000e0000000 (reserved)
 BIOS-e820: 00000000f8000000 - 00000000fc000000 (reserved)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fed10000 - 00000000fed14000 (reserved)
 BIOS-e820: 00000000fed18000 - 00000000fed1a000 (reserved)
 BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffa00000 - 00000000ffc00000 (reserved)
 BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000100000000 - 0000000118000000 (usable)
Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
DMI 2.6 present.
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved)
e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
last_pfn = 0xdee7c max_arch_pfn = 0x100000
MTRR default type: uncachable
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-BFFFF uncachable
  C0000-CFFFF write-protect
  D0000-E7FFF uncachable
  E8000-FFFFF write-protect
MTRR variable ranges enabled:
  0 base 000000000 mask F80000000 write-back
  1 base 080000000 mask FC0000000 write-back
  2 base 0C0000000 mask FE0000000 write-back
  3 base 100000000 mask FE0000000 write-back
  4 base 118000000 mask FF8000000 uncachable
  5 base 0FFE00000 mask FFFE00000 write-protect
  6 disabled
  7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
initial memory mapped : 0 - 00c00000
found SMP MP-table at [c00fc980] fc980
init_memory_mapping: 0000000000000000-00000000377fe000
 0000000000 - 0000400000 page 4k
 0000400000 - 0037400000 page 2M
 0037400000 - 00377fe000 page 4k
kernel direct mapping tables up to 377fe000 @ 15000-1a000
RAMDISK: 37a9c000 - 37ff0000
Allocated new RAMDISK: 00a3e000 - 00f91936
Move RAMDISK from 0000000037a9c000 - 0000000037fef935 to 00a3e000 - 00f91935
ACPI: RSDP 000f0410 00024 (v02   Sony)
ACPI: XSDT def1ce18 0005C (v01   Sony     VAIO 20100720 MSFT 00010013)
ACPI: FACP def15d98 000F4 (v04   Sony     VAIO 20100720 MSFT 00010013)
ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20100428/tbfadt-369)
ACPI Warning: 32/64X FACS address mismatch in FADT - 0xDEF2DF40/0x00000000DEF30D40, using 32 (20100428/tbfadt-486)
ACPI: DSDT deecd018 0ADBB (v01   Sony     VAIO 20100720 INTL 20051117)
ACPI: FACS def2df40 00040
ACPI: APIC def1bf18 0008C (v02   Sony     VAIO 20100720 MSFT 00010013)
ACPI: MCFG def2fd18 0003C (v01   Sony     VAIO 20100720 MSFT 00000097)
ACPI: HPET def2fc98 00038 (v01   Sony     VAIO 20100720 MSFT 00000003)
ACPI: SLIC def28a18 00176 (v01   Sony     VAIO 20100720 Sony 01000000)
ACPI: SSDT def16018 009F1 (v01   Sony     VAIO 20100720 INTL 20051117)
ACPI: SSDT def15c18 0014B (v01   Sony     VAIO 20100720 INTL 20051117)
ACPI: Local APIC address 0xfee00000
2678MB HIGHMEM available.
887MB LOWMEM available.
  mapped low ram: 0 - 377fe000
  low ram: 0 - 377fe000
Zone PFN ranges:
  DMA      0x00000010 -> 0x00001000
  Normal   0x00001000 -> 0x000377fe
  HighMem  0x000377fe -> 0x000dee7c
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
    0: 0x00000010 -> 0x0000009e
    0: 0x00000100 -> 0x000dee7c
On node 0 totalpages: 912906
free_area_init_node: node 0, pgdat c0944840, node_mem_map c1001200
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 3950 pages, LIFO batch:0
  Normal zone: 1744 pages used for memmap
  Normal zone: 221486 pages, LIFO batch:31
  HighMem zone: 5357 pages used for memmap
  HighMem zone: 680337 pages, LIFO batch:31
Using APIC driver default
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x05] enabled)
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] disabled)
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] disabled)
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] disabled)
ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] disabled)
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a701 base: 0xfed00000
SMP: Allowing 8 CPUs, 4 hotplug CPUs
nr_irqs_gsi: 40
early_res array is doubled to 64 at [16000 - 167ff]
PM: Registered nosave memory: 000000000009e000 - 000000000009f000
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
Allocating PCI resources starting at e0000000 (gap: e0000000:18000000)
setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
early_res array is doubled to 128 at [16800 - 177ff]
PERCPU: Embedded 13 pages/cpu @c2c00000 s29056 r0 d24192 u524288
pcpu-alloc: s29056 r0 d24192 u524288 alloc=1*4194304
pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 905773
Kernel command line: root=UUID=6508274a-dde5-4d1d-b03e-7fa2e666d20e ro quiet splash 
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Subtract (71 early reservations)
  #1 [0000001000 - 0000002000]   EX TRAMPOLINE
  #2 [0000100000 - 0000a395a4]   TEXT DATA BSS
  #3 [0000a3a000 - 0000a3d1b4]             BRK
  #4 [00000fc990 - 0000100000]   BIOS reserved
  #5 [00000fc980 - 00000fc990]    MP-table mpf
  #6 [000009e800 - 00000fc6f0]   BIOS reserved
  #7 [00000fc910 - 00000fc980]   BIOS reserved
  #8 [00000fc6f0 - 00000fc910]    MP-table mpc
  #9 [0000010000 - 0000011000]      TRAMPOLINE
  #10 [0000011000 - 0000015000]     ACPI WAKEUP
  #11 [0000015000 - 0000016000]         PGTABLE
  #12 [0000a3e000 - 0000f92000]     NEW RAMDISK
  #13 [0001000000 - 0001001000]         BOOTMEM
  #14 [0001001000 - 0002be1000]         BOOTMEM
  #15 [0002be1000 - 0002be1004]         BOOTMEM
  #16 [0002be1040 - 0002be1100]         BOOTMEM
  #17 [0002be1100 - 0002be1154]         BOOTMEM
  #18 [0002be1180 - 0002be4180]         BOOTMEM
  #19 [0002be4180 - 0002be427c]         BOOTMEM
  #20 [0002be4280 - 0002bf0280]         BOOTMEM
  #21 [0002bf0280 - 0002bf02a5]         BOOTMEM
  #22 [0002bf02c0 - 0002bf02e7]         BOOTMEM
  #23 [0002bf0300 - 0002bf0610]         BOOTMEM
  #24 [0002bf0640 - 0002bf0680]         BOOTMEM
  #25 [0002bf0680 - 0002bf06c0]         BOOTMEM
  #26 [0002bf06c0 - 0002bf0700]         BOOTMEM
  #27 [0002bf0700 - 0002bf0740]         BOOTMEM
  #28 [0002bf0740 - 0002bf0780]         BOOTMEM
  #29 [0002bf0780 - 0002bf07c0]         BOOTMEM
  #30 [0002bf07c0 - 0002bf0800]         BOOTMEM
  #31 [0002bf0800 - 0002bf0840]         BOOTMEM
  #32 [0002bf0840 - 0002bf0880]         BOOTMEM
  #33 [0002bf0880 - 0002bf08c0]         BOOTMEM
  #34 [0002bf08c0 - 0002bf0900]         BOOTMEM
  #35 [0002bf0900 - 0002bf0940]         BOOTMEM
  #36 [0002bf0940 - 0002bf0980]         BOOTMEM
  #37 [0002bf0980 - 0002bf09c0]         BOOTMEM
  #38 [0002bf09c0 - 0002bf0a00]         BOOTMEM
  #39 [0002bf0a00 - 0002bf0a40]         BOOTMEM
  #40 [0002bf0a40 - 0002bf0a80]         BOOTMEM
  #41 [0002bf0a80 - 0002bf0ac0]         BOOTMEM
  #42 [0002bf0ac0 - 0002bf0b00]         BOOTMEM
  #43 [0002bf0b00 - 0002bf0b40]         BOOTMEM
  #44 [0002bf0b40 - 0002bf0b80]         BOOTMEM
  #45 [0002bf0b80 - 0002bf0bc0]         BOOTMEM
  #46 [0002bf0bc0 - 0002bf0c00]         BOOTMEM
  #47 [0002bf0c00 - 0002bf0c40]         BOOTMEM
  #48 [0002bf0c40 - 0002bf0c80]         BOOTMEM
  #49 [0002bf0c80 - 0002bf0cc0]         BOOTMEM
  #50 [0002bf0cc0 - 0002bf0d00]         BOOTMEM
  #51 [0002bf0d00 - 0002bf0d10]         BOOTMEM
  #52 [0002bf0d40 - 0002bf0d80]         BOOTMEM
  #53 [0002bf0d80 - 0002bf0dc0]         BOOTMEM
  #54 [0002c00000 - 0002c0d000]         BOOTMEM
  #55 [0002c80000 - 0002c8d000]         BOOTMEM
  #56 [0002d00000 - 0002d0d000]         BOOTMEM
  #57 [0002d80000 - 0002d8d000]         BOOTMEM
  #58 [0002e00000 - 0002e0d000]         BOOTMEM
  #59 [0002e80000 - 0002e8d000]         BOOTMEM
  #60 [0002f00000 - 0002f0d000]         BOOTMEM
  #61 [0002f80000 - 0002f8d000]         BOOTMEM
  #62 [0002bf2dc0 - 0002bf2dc4]         BOOTMEM
  #63 [0002bf2e00 - 0002bf2e04]         BOOTMEM
  #64 [0002bf2e40 - 0002bf2e60]         BOOTMEM
  #65 [0002bf2e80 - 0002bf2ea0]         BOOTMEM
  #66 [0002bf2ec0 - 0002bf2f58]         BOOTMEM
  #67 [0002bf2f80 - 0002bf2fb8]         BOOTMEM
  #68 [0002bf2fc0 - 0002bf6fc0]         BOOTMEM
  #69 [0002f8d000 - 000300d000]         BOOTMEM
  #70 [0002c0d000 - 0002c4d000]         BOOTMEM
Initializing HighMem for node 0 (000377fe:000dee7c)
Memory: 3606864k/3652080k available (6256k kernel code, 44760k reserved, 2233k data, 488k init, 2742776k highmem)
virtual kernel memory layout:
    fixmap  : 0xfff17000 - 0xfffff000   ( 928 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000   ( 120 MB)
    lowmem  : 0xc0000000 - 0xf77fe000   ( 887 MB)
      .init : 0xc094b000 - 0xc09c5000   ( 488 kB)
      .data : 0xc071c138 - 0xc094a744   (2233 kB)
      .text : 0xc0100000 - 0xc071c138   (6256 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
Hierarchical RCU implementation.
	RCU-based detection of stalled CPUs is disabled.
	Verbose stalled-CPUs detection is disabled.
NR_IRQS:512
Extended CMOS year: 2000
Console: colour VGA+ 80x25
console [tty0] enabled
hpet clockevent registered
Fast TSC calibration using PIT
spurious 8259A interrupt: IRQ7.
Detected 2260.766 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 4523.92 BogoMIPS (lpj=7535886)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 9 MCE banks
CPU0: Thermal monitoring handled by SMI
using mwait in idle threads.
Performance Events: PEBS fmt1+, Westmere events, Intel PMU driver.
... version:                3
... bit width:              48
... generic registers:      4
... value mask:             0000ffffffffffff
... max period:             000000007fffffff
... fixed-purpose events:   3
... event mask:             000000070000000f
ACPI: Core revision 20100428
Enabling APIC mode:  Flat.  Using 1 I/O APICs
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
CPU0: Intel(R) Core(TM) i3 CPU       M 350  @ 2.27GHz stepping 02
Booting Node   0, Processors  #1
Initializing CPU#1
CPU1: Thermal monitoring handled by SMI
 #2
Initializing CPU#2
CPU2: Thermal monitoring handled by SMI
 #3
Initializing CPU#3
CPU3: Thermal monitoring handled by SMI
Brought up 4 CPUs
Total of 4 processors activated (18095.62 BogoMIPS).
xor: automatically using best checksumming function: pIII_sse
   pIII_sse  :  8686.800 MB/sec
xor: using function: pIII_sse (8686.800 MB/sec)
NET: Registered protocol family 16
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
PCI: Using MMCONFIG for extended config space
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Executed 2 blocks of module-level executable AML code
ACPI: BIOS _OSI(Linux) query ignored
ACPI: SSDT def1a918 003F0 (v01  PmRef  Cpu0Ist 00003000 INTL 20051117)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT (null) 003F0 (v01  PmRef  Cpu0Ist 00003000 INTL 20051117)
ACPI: SSDT def18018 00891 (v01  PmRef  Cpu0Cst 00003001 INTL 20051117)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT (null) 00891 (v01  PmRef  Cpu0Cst 00003001 INTL 20051117)
ACPI: SSDT def19a98 00303 (v01  PmRef    ApIst 00003000 INTL 20051117)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT (null) 00303 (v01  PmRef    ApIst 00003000 INTL 20051117)
ACPI: SSDT def17d98 00119 (v01  PmRef    ApCst 00003000 INTL 20051117)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT (null) 00119 (v01  PmRef    ApCst 00003000 INTL 20051117)
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
ACPI: No dock devices found.
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
\_SB_.PCI0:_OSC invalid UUID
_OSC request data:1 8 1f 
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
pci_root PNP0A08:00: host bridge window [io  0x0000-0x0cf7]
pci_root PNP0A08:00: host bridge window [io  0x0d00-0xffff]
pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000d3fff]
pci_root PNP0A08:00: host bridge window [mem 0x000d4000-0x000d7fff]
pci_root PNP0A08:00: host bridge window [mem 0x000d8000-0x000dbfff]
pci_root PNP0A08:00: host bridge window [mem 0x000dc000-0x000dffff]
pci_root PNP0A08:00: host bridge window [mem 0x000e0000-0x000e3fff]
pci_root PNP0A08:00: host bridge window [mem 0x000e4000-0x000e7fff]
pci_root PNP0A08:00: host bridge window [mem 0xe0000000-0xfeafffff]
pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: PME# disabled
pci 0000:00:16.0: reg 10: [mem 0xf5e0a000-0xf5e0a00f 64bit]
pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
pci 0000:00:16.0: PME# disabled
pci 0000:00:1a.0: reg 10: [mem 0xf5e08000-0xf5e083ff]
pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.0: PME# disabled
pci 0000:00:1b.0: reg 10: [mem 0xf5e00000-0xf5e03fff 64bit]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.1: PME# disabled
pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.2: PME# disabled
pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.5: PME# disabled
pci 0000:00:1d.0: reg 10: [mem 0xf5e07000-0xf5e073ff]
pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.0: PME# disabled
pci 0000:00:1f.2: reg 10: [io  0xe070-0xe077]
pci 0000:00:1f.2: reg 14: [io  0xe060-0xe063]
pci 0000:00:1f.2: reg 18: [io  0xe050-0xe057]
pci 0000:00:1f.2: reg 1c: [io  0xe040-0xe043]
pci 0000:00:1f.2: reg 20: [io  0xe020-0xe03f]
pci 0000:00:1f.2: reg 24: [mem 0xf5e06000-0xf5e067ff]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.2: PME# disabled
pci 0000:00:1f.3: reg 10: [mem 0xf5e05000-0xf5e050ff 64bit]
pci 0000:00:1f.3: reg 20: [io  0xe000-0xe01f]
pci 0000:01:00.0: reg 10: [mem 0xe0000000-0xefffffff 64bit pref]
pci 0000:01:00.0: reg 18: [mem 0xf0020000-0xf003ffff 64bit]
pci 0000:01:00.0: reg 20: [io  0xd000-0xd0ff]
pci 0000:01:00.0: reg 30: [mem 0xf0000000-0xf001ffff pref]
pci 0000:01:00.0: supports D1 D2
pci 0000:01:00.1: reg 10: [mem 0xf0040000-0xf0043fff 64bit]
pci 0000:01:00.1: supports D1 D2
pci 0000:00:01.0: PCI bridge to [bus 01-01]
pci 0000:00:01.0:   bridge window [io  0xd000-0xdfff]
pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xf00fffff]
pci 0000:00:01.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
pci 0000:02:00.0: reg 10: [mem 0xf4a00000-0xf4a0ffff 64bit]
pci 0000:02:00.0: supports D1
pci 0000:02:00.0: PME# supported from D0 D1 D3hot D3cold
pci 0000:02:00.0: PME# disabled
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:00:1c.0:   bridge window [io  0xc000-0xcfff]
pci 0000:00:1c.0:   bridge window [mem 0xf4a00000-0xf5dfffff]
pci 0000:00:1c.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
pci 0000:03:00.0: reg 10: [mem 0xf3602000-0xf36020ff]
pci 0000:03:00.0: supports D1 D2
pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:00.0: PME# disabled
pci 0000:03:00.1: reg 10: [mem 0xf3601000-0xf36010ff]
pci 0000:03:00.1: supports D1 D2
pci 0000:03:00.1: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:00.1: PME# disabled
pci 0000:03:00.4: reg 10: [mem 0xf3600000-0xf36000ff]
pci 0000:03:00.4: supports D1 D2
pci 0000:03:00.4: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:00.4: PME# disabled
pci 0000:00:1c.1: PCI bridge to [bus 03-03]
pci 0000:00:1c.1:   bridge window [io  0xb000-0xbfff]
pci 0000:00:1c.1:   bridge window [mem 0xf3600000-0xf49fffff]
pci 0000:00:1c.1:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
pci 0000:04:00.0: reg 10: [mem 0xf2220000-0xf2223fff 64bit]
pci 0000:04:00.0: reg 18: [io  0xa000-0xa0ff]
pci 0000:04:00.0: reg 30: [mem 0xf2200000-0xf221ffff pref]
pci 0000:04:00.0: supports D1 D2
pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:04:00.0: PME# disabled
pci 0000:00:1c.2: PCI bridge to [bus 04-04]
pci 0000:00:1c.2:   bridge window [io  0xa000-0xafff]
pci 0000:00:1c.2:   bridge window [mem 0xf2200000-0xf35fffff]
pci 0000:00:1c.2:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
pci 0000:00:1c.5: PCI bridge to [bus 05-0c]
pci 0000:00:1c.5:   bridge window [io  0x9000-0x9fff]
pci 0000:00:1c.5:   bridge window [mem 0xf0200000-0xf21fffff]
pci 0000:00:1c.5:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
pci 0000:00:1e.0: PCI bridge to [bus 0d-0d] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0xf000-0x0000] (disabled)
pci 0000:00:1e.0:   bridge window [mem 0xfff00000-0x000fffff] (disabled)
pci 0000:00:1e.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
pci 0000:00:1e.0:   bridge window [io  0x0000-0x0cf7] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x0d00-0xffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000dc000-0x000dffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000e0000-0x000e3fff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000e4000-0x000e7fff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xe0000000-0xfeafffff] (subtractive decode)
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEGP._PRT]
\_SB_.PCI0:_OSC invalid UUID
_OSC request data:1 19 1f 
ACPI: PCI Root Bridge [CPBG] (domain 0000 [bus 3f])
pci_bus 0000:3f: on NUMA node 0
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 *4 5 6 7 10 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 *5 6 7 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 1 *3 4 5 6 7 10 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12 14 15)
vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
raid6: int32x1    857 MB/s
raid6: int32x2    943 MB/s
raid6: int32x4    692 MB/s
raid6: int32x8    636 MB/s
raid6: mmxx1     2861 MB/s
raid6: mmxx2     3367 MB/s
raid6: sse1x1    2567 MB/s
raid6: sse1x2    3086 MB/s
raid6: sse2x1    5103 MB/s
raid6: sse2x2    6069 MB/s
raid6: using algorithm sse2x2 (6069 MB/s)
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
reserve RAM buffer: 000000000009e800 - 000000000009ffff 
reserve RAM buffer: 00000000dee7c000 - 00000000dfffffff 
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Switching to clocksource tsc
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 11 devices
ACPI: ACPI bus type pnp unregistered
system 00:05: [io  0x0680-0x069f] has been reserved
system 00:05: [io  0xff00-0xff0f] has been reserved
system 00:05: [io  0xff10-0xff13] has been reserved
system 00:05: [io  0x0800-0x0803] has been reserved
system 00:05: [io  0x0400-0x047f] has been reserved
system 00:05: [io  0x0500-0x057f] has been reserved
system 00:05: [io  0x164e-0x164f] has been reserved
system 00:09: [mem 0xfed1c000-0xfed1ffff] has been reserved
system 00:09: [mem 0xfed10000-0xfed13fff] has been reserved
system 00:09: [mem 0xfed18000-0xfed18fff] has been reserved
system 00:09: [mem 0xfed19000-0xfed19fff] has been reserved
system 00:09: [mem 0xf8000000-0xfbffffff] has been reserved
system 00:09: [mem 0xfed20000-0xfed3ffff] has been reserved
system 00:09: [mem 0xfed45000-0xfed8ffff] has been reserved
system 00:09: [mem 0xff000000-0xffffffff] could not be reserved
system 00:09: [mem 0xfee00000-0xfeefffff] could not be reserved
system 00:09: [mem 0xf5e0b000-0xf5e0bfff] has been reserved
pci 0000:00:1c.0: BAR 9: assigned [mem 0xf5f00000-0xf60fffff 64bit pref]
pci 0000:00:1c.1: BAR 9: assigned [mem 0xf6100000-0xf62fffff 64bit pref]
pci 0000:00:1c.2: BAR 9: assigned [mem 0xf6300000-0xf64fffff 64bit pref]
pci 0000:00:1c.5: BAR 9: assigned [mem 0xf6500000-0xf66fffff 64bit pref]
pci 0000:00:01.0: PCI bridge to [bus 01-01]
pci 0000:00:01.0:   bridge window [io  0xd000-0xdfff]
pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xf00fffff]
pci 0000:00:01.0:   bridge window [mem pref disabled]
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:00:1c.0:   bridge window [io  0xc000-0xcfff]
pci 0000:00:1c.0:   bridge window [mem 0xf4a00000-0xf5dfffff]
pci 0000:00:1c.0:   bridge window [mem 0xf5f00000-0xf60fffff 64bit pref]
pci 0000:00:1c.1: PCI bridge to [bus 03-03]
pci 0000:00:1c.1:   bridge window [io  0xb000-0xbfff]
pci 0000:00:1c.1:   bridge window [mem 0xf3600000-0xf49fffff]
pci 0000:00:1c.1:   bridge window [mem 0xf6100000-0xf62fffff 64bit pref]
pci 0000:00:1c.2: PCI bridge to [bus 04-04]
pci 0000:00:1c.2:   bridge window [io  0xa000-0xafff]
pci 0000:00:1c.2:   bridge window [mem 0xf2200000-0xf35fffff]
pci 0000:00:1c.2:   bridge window [mem 0xf6300000-0xf64fffff 64bit pref]
pci 0000:00:1c.5: PCI bridge to [bus 05-0c]
pci 0000:00:1c.5:   bridge window [io  0x9000-0x9fff]
pci 0000:00:1c.5:   bridge window [mem 0xf0200000-0xf21fffff]
pci 0000:00:1c.5:   bridge window [mem 0xf6500000-0xf66fffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 0d-0d]
pci 0000:00:1e.0:   bridge window [io  disabled]
pci 0000:00:1e.0:   bridge window [mem disabled]
pci 0000:00:1e.0:   bridge window [mem pref disabled]
pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:01.0: setting latency timer to 64
pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.1: setting latency timer to 64
pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
pci 0000:00:1c.2: setting latency timer to 64
pci 0000:00:1c.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.5: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7]
pci_bus 0000:00: resource 5 [io  0x0d00-0xffff]
pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff]
pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff]
pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff]
pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff]
pci_bus 0000:00: resource 11 [mem 0x000e0000-0x000e3fff]
pci_bus 0000:00: resource 12 [mem 0x000e4000-0x000e7fff]
pci_bus 0000:00: resource 13 [mem 0xe0000000-0xfeafffff]
pci_bus 0000:01: resource 0 [io  0xd000-0xdfff]
pci_bus 0000:01: resource 1 [mem 0xe0000000-0xf00fffff]
pci_bus 0000:02: resource 0 [io  0xc000-0xcfff]
pci_bus 0000:02: resource 1 [mem 0xf4a00000-0xf5dfffff]
pci_bus 0000:02: resource 2 [mem 0xf5f00000-0xf60fffff 64bit pref]
pci_bus 0000:03: resource 0 [io  0xb000-0xbfff]
pci_bus 0000:03: resource 1 [mem 0xf3600000-0xf49fffff]
pci_bus 0000:03: resource 2 [mem 0xf6100000-0xf62fffff 64bit pref]
pci_bus 0000:04: resource 0 [io  0xa000-0xafff]
pci_bus 0000:04: resource 1 [mem 0xf2200000-0xf35fffff]
pci_bus 0000:04: resource 2 [mem 0xf6300000-0xf64fffff 64bit pref]
pci_bus 0000:05: resource 0 [io  0x9000-0x9fff]
pci_bus 0000:05: resource 1 [mem 0xf0200000-0xf21fffff]
pci_bus 0000:05: resource 2 [mem 0xf6500000-0xf66fffff 64bit pref]
pci_bus 0000:0d: resource 4 [io  0x0000-0x0cf7]
pci_bus 0000:0d: resource 5 [io  0x0d00-0xffff]
pci_bus 0000:0d: resource 6 [mem 0x000a0000-0x000bffff]
pci_bus 0000:0d: resource 7 [mem 0x000d0000-0x000d3fff]
pci_bus 0000:0d: resource 8 [mem 0x000d4000-0x000d7fff]
pci_bus 0000:0d: resource 9 [mem 0x000d8000-0x000dbfff]
pci_bus 0000:0d: resource 10 [mem 0x000dc000-0x000dffff]
pci_bus 0000:0d: resource 11 [mem 0x000e0000-0x000e3fff]
pci_bus 0000:0d: resource 12 [mem 0x000e4000-0x000e7fff]
pci_bus 0000:0d: resource 13 [mem 0xe0000000-0xfeafffff]
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
pci 0000:00:1a.0: EHCI: BIOS handoff failed (BIOS bug?) 01010001
pci 0000:00:1d.0: EHCI: BIOS handoff failed (BIOS bug?) 01010001
pci 0000:01:00.0: Boot video device
PCI: CLS 64 bytes, default 64
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 5456k freed
apm: BIOS not found.
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
NTFS driver 2.1.29 [Flags: R/O].
msgmni has been set to 1698
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pcieport 0000:00:01.0: setting latency timer to 64
pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
pcieport 0000:00:1c.0: setting latency timer to 64
pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
pcieport 0000:00:1c.1: setting latency timer to 64
pcieport 0000:00:1c.1: irq 42 for MSI/MSI-X
pcieport 0000:00:1c.2: setting latency timer to 64
pcieport 0000:00:1c.2: irq 43 for MSI/MSI-X
pcieport 0000:00:1c.5: setting latency timer to 64
pcieport 0000:00:1c.5: irq 44 for MSI/MSI-X
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: AC Adapter [ADP1] (on-line)
input: Lid Switch as /class/input/input0
ACPI: Lid Switch [LID0]
input: Power Button as /class/input/input1
ACPI: Power Button [PWRB]
ACPI: acpi_idle registered with cpuidle
Monitor-Mwait will be used to enter C-1 state
Monitor-Mwait will be used to enter C-3 state
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [TZ00] (48 C)
thermal LNXTHERM:02: registered as thermal_zone1
ACPI: Thermal Zone [TZ01] (48 C)
isapnp: Scanning for PnP cards...
ACPI: Battery Slot [BAT0] (battery present)
isapnp: No Plug & Play device found
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
brd: module loaded
loop: module loaded
Compaq SMART2 Driver (v 2.6.0)
HP CISS Driver (v 3.6.20)
Uniform Multi-Platform E-IDE driver
ide_generic: please use "probe_mask=0x3f" module parameter for probing all legacy ISA IDE ports
Probing IDE interface ide0...
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
ide1 at 0x170-0x177,0x376 on irq 15
ide-gd driver 1.18
ide-cd driver 5.00
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
Loading Adaptec I2O RAID: Version 2.4 Build 5go
Detecting Adaptec I2O RAID controllers...
Adaptec aacraid driver 1.1-5[26400]-ms
aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded
scsi: <fdomain> Detection failed (no card)
sym53c416.c: Version 1.0.0-ac
qlogicfas: no cards were found, please specify I/O address and IRQ using iobase= and irq= options
QLogic Fibre Channel HBA Driver: 8.03.02-k2
iscsi: registered transport (qla4xxx)
QLogic iSCSI HBA Driver
Emulex LightPulse Fibre Channel SCSI driver 8.3.12
Copyright(c) 2004-2009 Emulex.  All rights reserved.
Failed initialization of WD-7000 SCSI card!
DC390: clustering now enabled by default. If you get problems load
       with "disable_clustering=1" and report to maintainers
megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
megasas: 00.00.04.17.1-rc1 Thu. Oct. 29, 11:41:51 PST 2009
GDT-HA: Storage RAID Controller Driver. Version: 3.05
3ware Storage Controller device driver for Linux v1.26.02.003.
3ware 9000 Storage Controller device driver for Linux v2.26.02.014.
nsp32: loading...
ipr: IBM Power RAID SCSI Device Driver version: 2.5.0 (February 11, 2010)
RocketRAID 3xxx/4xxx Controller driver v1.6 (090910)
st: Version 20081215, fixed bufsize 32768, s/g segs 256
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ahci 0000:00:1f.2: irq 45 for MSI/MSI-X
ahci: SSS flag set, parallel bus scan disabled
ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 4 ports 3 Gbps 0x23 impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pio slum part sxs apst 
ahci 0000:00:1f.2: setting latency timer to 64
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
scsi6 : ahci
scsi7 : ahci
ata1: SATA max UDMA/133 abar [email protected] port 0xf5e06100 irq 45
ata2: SATA max UDMA/133 abar [email protected] port 0xf5e06180 irq 45
ata3: DUMMY
ata4: DUMMY
ata5: DUMMY
ata6: SATA max UDMA/133 abar [email protected] port 0xf5e06380 irq 45
I2O subsystem v1.325
i2o: max drivers = 8
I2O Configuration OSM v1.323
I2O Bus Adapter OSM v1.317
I2O Block Device OSM v1.325
I2O SCSI Peripheral OSM v1.316
I2O ProcFS OSM v1.316
Fusion MPT base driver 3.04.15
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SPI Host driver 3.04.15
Fusion MPT FC Host driver 3.04.15
Fusion MPT SAS Host driver 3.04.15
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ehci_hcd 0000:00:1a.0: setting latency timer to 64
ehci_hcd 0000:00:1a.0: EHCI Host Controller
ehci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.0: debug port 2
ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported
ehci_hcd 0000:00:1a.0: irq 16, io mem 0xf5e08000
ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.0: setting latency timer to 64
ehci_hcd 0000:00:1d.0: EHCI Host Controller
ehci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.0: debug port 2
ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported
ehci_hcd 0000:00:1d.0: irq 23, io mem 0xf5e07000
ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
116x: driver isp116x-hcd, 03 Nov 2005
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
sl811: driver sl811-hcd, 19 May 2005
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-alauda
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-isd200
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-karma
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
usbcore: registered new interface driver ums-usbat
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
md: multipath personality registered for level -4
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised: [email protected]
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
Using IPI No-Shortcut mode
input: AT Translated Set 2 keyboard as /class/input/input2
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
ata1.00: ATA-8: Hitachi HTS545032B9SA00, PB3OC64G, max UDMA/133
ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
ata1.00: configured for UDMA/133
usb 1-1: new high speed USB device using ehci_hcd and address 2
scsi 2:0:0:0: Direct-Access     ATA      Hitachi HTS54503 PB3O PQ: 0 ANSI: 5
sd 2:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
sd 2:0:0:0: [sda] Attached SCSI disk
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 6 ports detected
usb 2-1: new high speed USB device using ehci_hcd and address 2
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATAPI: Optiarc DVD RW AD-7700H, 1.V0, max UDMA/100
ata2.00: configured for UDMA/100
scsi 3:0:0:0: CD-ROM            Optiarc  DVD RW AD-7700H  1.V0 PQ: 0 ANSI: 5
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 8 ports detected
sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 3:0:0:0: Attached scsi CD-ROM sr0
usb 1-1.2: new high speed USB device using ehci_hcd and address 3
usb 2-1.2: new low speed USB device using ehci_hcd and address 3
ata6: SATA link down (SStatus 0 SControl 300)
input: Microsoft  Compact Optical Mouse 500 as /class/input/input3
generic-usb 0003:045E:0737.0001: input: USB HID v1.11 Mouse [Microsoft  Compact Optical Mouse 500] on usb-0000:00:1d.0-1.2/input0
Freeing unused kernel memory: 488k freed
fuse init (API version 7.14)
sky2: driver version 1.28
sky2 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
sky2 0000:04:00.0: setting latency timer to 64
sky2 0000:04:00.0: Yukon-2 Optima chip revision 1
sky2 0000:04:00.0: irq 46 for MSI/MSI-X
sky2 0000:04:00.0: eth0: addr 54:42:49:61:fc:e3
sd 2:0:0:0: Attached scsi generic sg0 type 0
sr 3:0:0:0: Attached scsi generic sg1 type 5
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda5): mounted filesystem with writeback data mode
udevd version 124 started
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Linux agpgart interface v0.103
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
iTCO_wdt: Found a HM55 TCO device (Version=2, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pci 0000:03:00.0: SDHCI controller found [1180:e822] (rev 0)
sdhci-pci 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
sdhci-pci 0000:03:00.0: Will use DMA mode even though HW doesn't fully claim to support it.
sdhci-pci 0000:03:00.0: setting latency timer to 64
Registered led device: mmc0::
mmc0: SDHCI controller on PCI [0000:03:00.0] using DMA
sdhci-pci 0000:03:00.4: SDHCI controller found [1180:e822] (rev 0)
sdhci-pci 0000:03:00.4: PCI INT C -> GSI 19 (level, low) -> IRQ 19
sdhci-pci 0000:03:00.4: Will use DMA mode even though HW doesn't fully claim to support it.
sdhci-pci 0000:03:00.4: setting latency timer to 64
Registered led device: mmc1::
mmc1: SDHCI controller on PCI [0000:03:00.4] using DMA
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
cfg80211: Calling CRDA to update world regulatory domain
[Firmware Bug]: ACPI(VGA) defines _DOD but not _DOS
acpi device:4a: registered as cooling_device4
input: Video Bus as /class/input/input4
ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
sony-laptop: Sony Notebook Control Driver v0.6.
rtc_cmos 00:06: RTC can wake from S4
rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one year, y3k, 242 bytes nvram, hpet irqs
input: Sony Vaio Keys as /class/input/input5
input: Sony Vaio Jogdial as /class/input/input6
sony-laptop: brightness ignored, must be controlled by ACPI video driver
fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
Disabling lock debugging due to kernel taint
ath9k 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ath9k 0000:02:00.0: setting latency timer to 64
input: ImPS/2 Generic Wheel Mouse as /class/input/input7
[fglrx] Maximum main memory to use for locked dma buffers: 3373 MBytes.
[fglrx]   vendor: 1002 device: 68e0 count: 1
[fglrx] ioport: bar 4, base 0xd000, size: 0x100
pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:01:00.0: setting latency timer to 64
[fglrx] Kernel PAT support is enabled
[fglrx] module loaded - fglrx 8.80.5 [Nov 25 2010] with 1 minors
cfg80211: World regulatory domain updated:
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
usb 1-1.6: new full speed USB device using ehci_hcd and address 4
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: irq 47 for MSI/MSI-X
HDA Intel 0000:00:1b.0: setting latency timer to 64
phy0: Selected rate control algorithm 'ath9k_rate_control'
Registered led device: ath9k-phy0::radio
Registered led device: ath9k-phy0::assoc
Registered led device: ath9k-phy0::tx
Registered led device: ath9k-phy0::rx
phy0: Atheros AR9285 Rev:2 mem=0xf8b40000, irq=16
HDA Intel 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
HDA Intel 0000:01:00.1: irq 48 for MSI/MSI-X
HDA Intel 0000:01:00.1: setting latency timer to 64
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
lp: driver loaded but no devices found
EXT3-fs (sda5): using internal journal
ip_tables: (C) 2000-2006 Netfilter Core Team
fglrx_pci 0000:01:00.0: irq 49 for MSI/MSI-X
[fglrx] Firegl kernel thread PID: 6602
[fglrx] IRQ 49 Enabled
[fglrx] Gart USWC size:1104 M.
[fglrx] Gart cacheable size:437 M.
[fglrx] Reserved FB block: Shared offset:0, size:1000000 
[fglrx] Reserved FB block: Unshared offset:f98b000, size:375000 
[fglrx] Reserved FB block: Unshared offset:1fff4000, size:c000 
sky2 0000:04:00.0: eth0: enabling interface
sky2 0000:04:00.0: eth0: disabling interface
sky2 0000:04:00.0: eth0: enabling interface
ath9k: Two wiphys trying to scan at the same time
wlan0: authenticate with 0e:b7:8b:a5:ea:14 (try 1)
wlan0: authenticated
wlan0: associate with 0e:b7:8b:a5:ea:14 (try 1)
wlan0: RX AssocResp from 0e:b7:8b:a5:ea:14 (capab=0x411 status=0 aid=1)
wlan0: associated
padlock: VIA PadLock not detected.
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
bonding: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
bonding: MII link monitoring set to 100 ms
usb 2-1.2: USB disconnect, address 3
usb 2-1.5: new low speed USB device using ehci_hcd and address 4
input: Microsoft  Compact Optical Mouse 500 as /class/input/input8
generic-usb 0003:045E:0737.0002: input: USB HID v1.11 Mouse [Microsoft  Compact Optical Mouse 500] on usb-0000:00:1d.0-1.5/input0
usb 2-1.6: new high speed USB device using ehci_hcd and address 5
usb 2-1.6: reset high speed USB device using ehci_hcd and address 5
phy1: Selected rate control algorithm 'minstrel'
zd1211rw 2-1.6:1.0: phy1
usbcore: registered new interface driver zd1211rw
wlan0: deauthenticating from 0e:b7:8b:a5:ea:14 by local choice (reason=3)
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
sky2 0000:04:00.0: eth0: disabling interface
sky2 0000:04:00.0: eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
sky2 0000:04:00.0: eth0: disabling interface
sky2 0000:04:00.0: eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ath9k: Two wiphys trying to scan at the same time
wlan0: authenticate with 0e:b7:8b:a5:ea:14 (try 1)
wlan0: authenticated
wlan0: associate with 0e:b7:8b:a5:ea:14 (try 1)
wlan0: associate with 0e:b7:8b:a5:ea:14 (try 2)
wlan0: associate with 0e:b7:8b:a5:ea:14 (try 3)
wlan0: association with 0e:b7:8b:a5:ea:14 timed out
wlan0: authenticate with 0e:b7:8b:a5:ea:14 (try 1)
wlan0: authenticated
wlan0: associate with 0e:b7:8b:a5:ea:14 (try 1)
wlan0: RX AssocResp from 0e:b7:8b:a5:ea:14 (capab=0x411 status=0 aid=1)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
ADDRCONF(NETDEV_UP): bond0: link is not ready
wlan0: deauthenticating from 0e:b7:8b:a5:ea:14 by local choice (reason=3)
bonding: bond0: enslaving wlan0 as a backup interface with a down link.
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
wlan0: authenticate with 0e:b7:8b:a5:ea:14 (try 1)
wlan0: authenticated
wlan0: associate with 0e:b7:8b:a5:ea:14 (try 1)
wlan0: RX AssocResp from 0e:b7:8b:a5:ea:14 (capab=0x411 status=0 aid=1)
wlan0: associated
bonding: bond0: link status definitely up for interface wlan0.
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
zd1211rw 2-1.6:1.0: firmware version 4725
zd1211rw 2-1.6:1.0: zd1211b chip 079b:0062 v4810 high 00-60-b3 AL2230_RF pa0 g---S
cfg80211: Calling CRDA for country: DE
cfg80211: Regulatory domain changed to country: DE
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
    (5150000 KHz - 5350000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    (5470000 KHz - 5725000 KHz @ 40000 KHz), (N/A, 2698 mBm)
bonding: bond0: enslaving wlan1 as a backup interface with a down link.
wlan0: deauthenticating from 0e:b7:8b:a5:ea:14 by local choice (reason=3)
cfg80211: Calling CRDA to update world regulatory domain
bonding: bond0: link status definitely down for interface wlan0, disabling it
cfg80211: World regulatory domain updated:
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
sky2 0000:04:00.0: eth0: disabling interface
sky2 0000:04:00.0: eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 0000:04:00.0: eth0: disabling interface
sky2 0000:04:00.0: eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
bond0: no IPv6 routers present
ath9k: Two wiphys trying to scan at the same time
wlan0: authenticate with 0e:b7:8b:a5:ea:14 (try 1)
wlan0: authenticated
wlan0: associate with 0e:b7:8b:a5:ea:14 (try 1)
wlan0: RX AssocResp from 0e:b7:8b:a5:ea:14 (capab=0x411 status=0 aid=1)
wlan0: associated
bonding: bond0: link status definitely up for interface wlan0.
wlan0: deauthenticating from 0e:b7:8b:a5:ea:14 by local choice (reason=3)
bonding: bond0: link status definitely down for interface wlan0, disabling it
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
sky2 0000:04:00.0: eth0: disabling interface
sky2 0000:04:00.0: eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 0000:04:00.0: eth0: disabling interface
sky2 0000:04:00.0: eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
wlan0: authenticate with 06:23:08:3d:61:4d (try 1)
wlan0: authenticated
wlan0: associate with 06:23:08:3d:61:4d (try 1)
wlan0: RX AssocResp from 06:23:08:3d:61:4d (capab=0x431 status=0 aid=1)
wlan0: associated
cfg80211: Calling CRDA for country: FR
cfg80211: Current regulatory domain updated by AP to: FR
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
bonding: bond0: link status definitely up for interface wlan0.
sky2 0000:04:00.0: eth0: disabling interface
sky2 0000:04:00.0: eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 0000:04:00.0: eth0: disabling interface
sky2 0000:04:00.0: eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
wlan1: authenticate with 0e:b7:8b:a5:ea:14 (try 1)
wlan1: authenticated
wlan1: associate with 0e:b7:8b:a5:ea:14 (try 1)
wlan1: RX AssocResp from 0e:b7:8b:a5:ea:14 (capab=0x411 status=0 aid=1)
wlan1: associated
bonding: bond0: link status definitely up for interface wlan1.
wlan0: deauthenticating from 06:23:08:3d:61:4d by local choice (reason=3)
bonding: bond0: link status definitely down for interface wlan0, disabling it
wlan1: deauthenticating from 0e:b7:8b:a5:ea:14 by local choice (reason=3)
bonding: bond0: link status definitely down for interface wlan1, disabling it
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
sky2 0000:04:00.0: eth0: disabling interface
sky2 0000:04:00.0: eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
bonding: bond0: released all slaves
bonding: Unknown parameter `iimon'
bonding: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
bonding: MII link monitoring set to 100 ms
ADDRCONF(NETDEV_UP): bond0: link is not ready
bonding: bond0: enslaving wlan0 as a backup interface with a down link.
wlan0: authenticate with 06:23:08:3d:61:4d (try 1)
wlan0: authenticated
wlan0: associate with 06:23:08:3d:61:4d (try 1)
wlan0: RX AssocResp from 06:23:08:3d:61:4d (capab=0x431 status=0 aid=1)
wlan0: associated
cfg80211: Calling CRDA for country: FR
cfg80211: Current regulatory domain updated by AP to: FR
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
bonding: bond0: link status definitely up for interface wlan0.
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
bond0: no IPv6 routers present
bonding: bond0: enslaving wlan1 as a backup interface with a down link.
wlan0: deauthenticating from 06:23:08:3d:61:4d by local choice (reason=3)
bonding: bond0: link status definitely down for interface wlan0, disabling it
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
wlan0: authenticate with 06:23:08:3d:61:4d (try 1)
wlan0: authenticated
wlan0: associate with 06:23:08:3d:61:4d (try 1)
wlan0: RX AssocResp from 06:23:08:3d:61:4d (capab=0x431 status=0 aid=1)
wlan0: associated
cfg80211: Calling CRDA for country: FR
cfg80211: Current regulatory domain updated by AP to: FR
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
bonding: bond0: link status definitely up for interface wlan0.
sky2 0000:04:00.0: eth0: disabling interface
sky2 0000:04:00.0: eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
wlan1: authenticate with 0e:b7:8b:a5:ea:14 (try 1)
wlan1: authenticated
wlan1: associate with 0e:b7:8b:a5:ea:14 (try 1)
wlan1: RX AssocResp from 0e:b7:8b:a5:ea:14 (capab=0x411 status=0 aid=1)
wlan1: associated
bonding: bond0: link status definitely up for interface wlan1.

Je n'arrive pas tout à décrypter...

Dernière modification par Shipping LAN (17-01-2011 18:31:55)


Shipping LAN

Étudiant en 1ère année de D.U.T. Réseaux et Télécommunications

Hors Ligne

#12 17-01-2011 20:33:49

antares145
Membre d'honneur
Inscription : 29-09-2009
Messages : 5 199
Site Web

Re : Channel bonding sur BT4 ?

Bon, le fait que bond0 ne soit pas considérée comme une interface WiFi, perso ça me semble normal (enfin, acceptable). C'est une interface "générique" en Ethernet (tout comme wlan0 et wlan1 d'ailleurs) et elle n'a pas de partie "radio (SSID, canal, signal,...), donc moi j'accepte tongue

Par contre pour le reste, je suis pas plus avancé que toi (donc en clair on est 2 à être noyés big_smile). Il faut que je fasse des tests de mon côté pour chipoter un peu, mais j'ai pas le temps pour l'instant donc je mets ça en standby. mais je t'oublie pas, d'ici une semaine (ptet 2) je devrais avoir avancé. Si tu trouves d'ici-là, poste tes progrès ici.

Bonne chance ! smile

Hors Ligne

#13 25-01-2011 16:20:21

Shipping LAN
Membre
Lieu : Annecy
Inscription : 12-01-2011
Messages : 19

Re : Channel bonding sur BT4 ?

Bien alors après de multiples et multiples tests (avec un ami), on en est arrivé à 2 autres axes de recherches :
- bricoler un routeur Cisco virtuel afin de faire du load balancing afin de coupler les connexions
- utiliser la commande ip route (je crois que c'est ça...), mais apparemment ça diminuerai le débit (selon mon ami)...

Bref on est partis sur un autre projet (mdk3 ...) en attendant de voir ce que donne tes recherches wink


Shipping LAN

Étudiant en 1ère année de D.U.T. Réseaux et Télécommunications

Hors Ligne

#14 10-03-2011 10:36:21

kmleon
Membre
Inscription : 03-10-2009
Messages : 13

Re : Channel bonding sur BT4 ?

bonjour antares145

as-tu eu le temps d'effectuer quelques tests concernant le bonding ou pas ?

je me propose d'effectuer quelques manips (BT4-R2 sur micro-USB16Go + 2 interfaces ou 3 interfaces USB Wifi et 1 ou 2 interfaces LAN)

Je vais commencer par reprendre la config depuis le début de ce post puis poster les résultats.

a bientôt.

kmleon

Dernière modification par kmleon (10-03-2011 10:38:33)

Hors Ligne

#15 10-03-2011 18:56:22

antares145
Membre d'honneur
Inscription : 29-09-2009
Messages : 5 199
Site Web

Re : Channel bonding sur BT4 ?

Non, pas eu le temps d'effectuer des tests, je suis fort pris ces derniers temps.

D'après ce que j'ai cru comprendre, les interfaces "bond" n'aiment pas le WiFi, mais j'ai pas creusé.

Bonne chance pour tes tests, tiens-nous au courant si ça marche ! smile

Hors Ligne

Annonce

Visitez la boutique Wifi-highpower.com, votre revendeur agr Alfa Network: du matriel Wifi slectionn, cartes Wifi USB Awus036h et Awus036nh, antennes omnis, yagis, panel, amplis wifi, accessoires...

Pied de page des forums


Le coin des bonnes affaires, achats informatiques:


|   Alfa 1000 mW AWUS036H   |    Linksys WRT54GL   |    Misco, informatique   |   
 |    Ebay   |    PC portables   |    PC Gamers & Tuning   |    Cles USB   |   
|   Disques durs externes 2 To   |   
|   Wifi-highpower.com   |   


Server Stats - [ Generated in 0.038 seconds ]   Forum Stat - [ Most users ever online on the forum was : 150 on 20-09-2009 17:06:59 ]