Ubuntu wpa driver precise

By Nicolas Bernaerts Creation Update owaday, interface like Network manager makes wifi connexion setup a very simple task. But in some specific cases (ubuntu server, ubuntu minimal media center. you may need to setup you WEP or WPA wifi connexion directly from command line, without using network manager. This article explains how to fully configure a WEP or WPA encrypted wifi network from a console terminal, using only command line tools. It has been tested on Ubuntu Precise 12.04, but it should work on any modern Ubuntu or Debian flavored distro. If not already installed, we have to install the wireless-tools and hwinfo packages : sudo apt-get install wireless-tools hwinfo We can now easily determine the name of the wifi interface with the iwconfig command : iwconfiglo no wireless extensions.wlan0 IEEE 802.11abg ESSID: Mode:xxx Frequency:5.2 GHz Access Point: 00:xx:xx:xx:xx:xx Bit Rate=xx Mb/s Tx- Power=xx d Bm.eth0 no wireless extensions. In this example, the wifi interface is named wlan0. hwinfo tool will even give us more information about the wifi device capabilities and the module handling the device : hwinfo -netcard.27: PCI 1000.0: 0282 WLAN controller[ Created at pci.318] Unique ID: y9sn. X4 Ey7 Ce Hg Q0 Parent ID: q Tvu.b JAo Dpzv G5 FSys FS ID: /devices/pci :1c.0 Sys FS Bus ID: Hardware Class: network Model: Intel PRO/ Wireless 4965 AG or AGN [ Kedron] Network Connection Vendor: pci 0x8086 Intel Corporation Device: pci 0x4229 PRO/ Wireless 4965 AG or AGN [ Kedron] Network Connection Sub Vendor: pci 0x8086 Intel Corporation Sub Device: pci 0x1001 Revision: 0x61 Driver: iwl4965 Driver Modules: iwl4965 Device File: wlan0 Features: WLANMemory Range: 0xe0000000-0xe0001fff (rw,non-prefetchable) IRQ: 45 (5428877 events) HW Address: c:8e:0f:a7 Link detected: yes WLAN channels:.
This happened on my home linux machine (64 bit, recently updated to Ubuntu Precise). A tab was playing a video, that I reloaded. It blocked for maybe a second and then rebooted. The last thing I saw in the system logs before the reboot is: Jun 14 piman kernel: [320438.391299] type=1701 audit(133969 auid= uid=15 gid=15 ses= pid=12993 comm= chrome reason= seccomp sig=0 syscall=2 compat=0 ip=0x7f6197266eb0 code=0x50002 Jun 14 piman kernel: [320438.391323] type=1701 audit(133969 auid= uid=15 gid=15 ses= pid=12993 comm= chrome reason= seccomp sig=0 syscall=2 compat=0 ip=0x7f6197266eb0 code=0x50002 Jun 14 piman kernel: [320438.393496] type=1701 audit(133969 auid= uid=15 gid=15 ses= pid=12999 comm= chrome reason= seccomp sig=0 syscall=59 compat=0 ip=0x7f code=0x50002 Jun 14 piman kernel: [320439.028558] type=1701 audit(133969 auid= uid=15 gid=15 ses= pid=11801 comm= chrome reason= seccomp sig=0 syscall=83 compat=0 ip=0x7f7ffb491e47 code=0x50002 Jun 14 piman kernel: [320439.028568] type=1701 audit(133969 auid= uid=15 gid=15 ses= pid=11801 comm= chrome reason= seccomp sig=0 syscall=83 compat=0 ip=0x7f7ffb491e47 code=0x50002 Jun 14 piman kernel: [320439.076660] type=1701 audit(133969 auid= uid=15 gid=15 ses= pid=11801 comm= chrome reason= seccomp sig=0 syscall=2 compat=0 ip=0x7f7ffb491eb0 code=0x50002 Jun 14 piman kernel: [320439.076673] type=1701 audit(133969 auid= uid=15 gid=15 ses= pid=11801 comm= chrome reason= seccomp sig=0 syscall=2 compat=0 ip=0x7f7ffb491eb0 code=0x50002 This corresponds to the time of the reboot. GPU Driver: Open GL vendor string: NVIDIA Corporation.