Earlier this year I bought my wife an Acer Aspire One AOA110 netbook. I installed UNR (Jaunty 9.04) which worked perfectly from the the Live USB image, but once installed It couldn’t see any wireless networks. In the end I blacklisted the madwifi drivers and switched to the ath5k atheros driver, and everything seemed to be ok. In the past few weeks we found that the wireless connection would regulary drop, and network manager would then take 30 seconds or so to connect to the router again. This was very annoying. It seemed to happen more often when transferring larger amounts of data, like uploading images to facebook. The message being written to /var/log/messages was:

ath5k phy0: unsupported jumbo

In the end I compiled the latest madwifi source code by hand, and re-enabled the driver. Here is what I had to do:

1. Blacklist the ath5k driver. Add the following to /etc/modprobe.d/blacklist.conf:blacklist ath5k
   blacklist acer_wmi
2. Add the following to the /etc/modules file to ensure the madwifi driver is loadedath_pci
3. Install Subversion:sudo apt-get install subversion
4. Extract the latest madwifi source code from the subversion server:svn co http://svn.madwifi-project.org/madwifi/trunk madwifi
5. Build it:cd madwifi/scripts
   sudo ./find-madwifi-modules.sh -r
   cd ..
   make
   sudo make install
6. Reboot.

If everything went well your wireless will work as usual, but will be running the madwifi drivers, and not the ath5k atheros driver. If you do experience any problems, change the entry in the blacklist to ath_pci, change the entry in /etc/modules to ath5k, restart networking (or reboot) and you should be back on the ath5k driver.

I tend to minimise the instances when I have to change of Linux version on my computer (a Macbook Pro Santa Rosa), for this always is a traumatic event with potential consequences on my work, and therefore I had postponed leaving Kubuntu 7.10 (Gutsy Gibbon) in a typical procrastinating attitude,  i.e. till something stopped working! This happened yesterday with a failed attempt at upgrading R and I thus moved to Kubuntu 8.04 (Hardy Heron), using the upgrade option rather than re-installing the whole thing from scratch. The only manual steps were to change xorg.conf to accomodate the touchpad and to install madwif to get access to the wireless—the most frustrating part was finding a valid address! (Upgrading Ubuntu means that each intermediate version needs to be installed before moving to the next.) Now that everything works nicely (including suspend and hibernate, and my earlier heating problem seems to be resolved as well!), I am wondering whether or not I should move to the next version of Kubuntu 8.10 (Intrepid Ibex, terrible tee-shirt!) or even to the most recent  Kubuntu 9.04 (Jaunty Jackalope, terrible name: jaundiced jackal, jovial jabiru, jocular jellyfish, or jittery jaguar would have sounded way better! The next animal in the list of releases is a koala, although karmic would hardly have been my adjective of choice)… As an aside about this future release, an interesting announcement is that Ubuntu 9.10 would support cloud computing.

I downloaded madwifi in madwifi-project site.

But compile error came out on the way to [make].

Through googling, I found below method.

svn checkout http://madwifi-project.org/svn/madwifi/trunk madwifi

Configurazione di Mad-wifi dai rep rpm fusion.Da terminal:

su -c 'yum -y install madwifi kmod-madwifi'

su -c 'gedit /etc/modprobe.conf'

## Start Atheros Stuff
alias wifi0 ath_pci
alias ath0 ath_pci
options ath_pci autocreate=sta
## End Atheros Stuff

Infine configurazione del wireless
System -> Administration -> Network

PROBLEM SOLUTION:

download madwifi-trunk-current.tar.gz

extract madwifi-trunk-current.tar.gz

cd /madwifi-trunk-r4081-20090731/scripts

./madwifi-unload

./find-madwifi-modules.sh $(uname -r)

r

cd ..

make

make install

modprobe ath_pci

/etc/init.d/networking restart

IMPORTANT:

blacklist ath5k

ath_pci, ath_hal must be activated

kill acpid w/ sudo /etc/init.d/acpid stop

PROBLEM:

hotkeys are acpid dependant, ergo hotkeys stop working after acpid is killed

SOLUTION PENDING,

OVER AND OUT.

Siang ini, seperti biasa saya nyalakan notebook acer aspire 5050, masuk ke ubuntu 9.04 untuk melakukan rutinitas browsing internet. Baru beberapa menit muncul update notifier, tersedia update untuk beberapa paket. Tanpa pikir panjang langsung saya klik tombol install updates, setelah beberapa menit berlalu update selesei dan muncul pesan system perlu di restart. Menuruti perintah akhirnya saya restart notebook, tapi upss… wireless atheros koq gak aktif ya?! Saya cek di System > Administration > Hardware Drivers, Alternate Atheros “madwifi” driver dalm kondisi aktif.

Ternyata setelah dirunut masalahnya berasal dari kernel yang ikut terupdate. Akhirnya saya putuskan untuk instal ulang driver atherosnya, setelah googling akhirnya ditemukan langkah-langkahnya.

Langkah pertama adalah instal build-essential

$ sudo apt-get install build-essential

Download driver madwifi dari sini dengan perintah:

$ wget http://snapshots.madwifi-project.org/madwifi-hal-0.10.5.6-current.tar.gz

Disable Atheros Hardware Access Layer (HAL) and Support untuk Atheros 802.11 wireless lan cards melalui menu System > Administration > Hardware Drivers, kemudian reboot (jika diperlukan). Edit berkas linux-restricted-modules-common untuk memastikan modul ath_hal tidak lagi dimuat

$ sudo gedit /etc/default/linux-restricted-modules-common

Tambahkan ath_hal pada Disabled_Modules.

DISABLED_MODULES=”ath_hal”

Untar file madwifi-hal-0.10.5.6-current.tar.gz yang telah selesai di download, gunakan perintah:

$ tar xzvf madwifi-hal-0.10.5.6-current.tar.gz

Masuk ke direktori dimana madwifi Anda letakkan, gunakan perintah:

$ cd madwifi-hal-0.10.5.6-r4068-20090705

catatan : madwifi-hal-0.10.5.6-r4068-20090705 adalah nama direktor/folder hasil untar file madwifi-hal-0.10.5.6-current.tar.gz
Kemudian Jalankan script madwifi-unload dan find-madwifi-modules.sh, gunakan perintah:

$ sudo ./madwifi-unload
$ sudo ./find-madwifi-modules.sh $(uname -r)

Keluar dari direktori madwifi-hal-0.10.5.6-r4068-20090705, gunakan perintah:

$ cd ..

Jalankan perintah berikut untuk memastikan driver terdahulu bersih.

$ make clean

Masuk kembali ke direktori madwifi-hal-0.10.5.6-r4068-20090705, Jalankan perintah-perintah berikut:

$ make
$ sudo make install
$ sudo modprobe ath_pci

Sampai tahap ini driver atheros sudah terinstal.

Referensi:
1. http://cutec.wordpress.com
2. http://blog.singgihsaptadi.asia

Seit Kernel Version 2.6.29 gibt es KMOD nicht mehr und ihr bekommt  beim emergen von madwifi-ng-0.9.4 eventuell die Fehlermeldung “Requires CONFIG_KMOD”.  Auf bugs.gentoo.org befindet sich mittlerweile ein neuer Ebuild mit Patches um das Problem zu beheben.

http://bugs.gentoo.org/show_bug.cgi?id=262761

A quintessential hallmark of an authoritarian regime, particularly one that operates within highly-militarized, though nominally democratic states such as ours, is the maintenance of a system of internal control; a seamless panopticon where dissent is equated with criminality and the rule of law derided as a luxury ill-afforded “during a time of war.”

In this context, the deployment of new offensive technologies which can wreck havoc on human populations deemed expendable by the state, are always couched in a defensive rhetoric by militarist aggressors and their apologists.

While the al-Qaeda brand may no longer elicit a compelling response in terms of mobilizing the population for new imperial adventures, novel threats–and panics–are required to marshal public support for the upward transfer of wealth into the corporate trough. Today, “cyber terror” functions as the “new Osama.”

And with Congress poised to pass the Cybersecurity Act of 2009, an Orwellian bill that would give the president the power to “declare a cybersecurity emergency” and shut down or limit Internet traffic in any “critical” information network “in the interest of national security” of course, the spaces left for the free flow of information–and meaningful dissent–slowly contract.

Defense Advanced Research Projects Agency–and Cybersecurity Grifters–to the Rescue

But protecting critical infrastructure from hackers, criminals and terrorists isn’t the only game in town. The Pentagon is planning to kick-start a new office, Cyber Command, armed with the capacity to launch devastating attacks against any nation or group deemed an official enemy by Washington.

As Antifascist Calling reported last year, the Defense Advanced Research Projects Agency (DARPA), the Pentagon’s “geek squad,” is building a National Cyber Range (NCR). As Cyber Command’s research arm, the agency’s Strategic Technology Office (STO) describes NCR as

DARPA’s contribution to the new federal Comprehensive National Cyber Initiative (CNCI), providing a “test bed” to produce qualitative and quantitative assessments of the Nation’s cyber research and development technologies. Leveraging DARPA’s history of cutting-edge research, the NCR will revolutionize the state of the art for large-scale cyber testing. Ultimately, the NCR will provide a revolutionary, safe, fully automated and instrumented environment for our national cyber security research organizations to evaluate leap-ahead research, accelerate technology transition, and enable a place for experimentation of iterative and new research directions. (“National Cyber Range,” Defense Advanced Research Projects Agency, Strategic Technology Office, no date)

According to a January 2009 press release, the agency announced that NCR “will accelerate government research and development in high-risk, high-return areas and work in close cooperation with private-sector partners to jump-start technical cyber transformation.”

Given the Pentagon’s proclivity to frame debates over defense and security-related issues as one of “dominating the adversary” and discovering vulnerabilities that can be “exploited” by war planners, one can hypothesize that NCR is a testing range for the creation of new offensive weapons.

Amongst the “private-sector partners” chosen by the agency to “develop, field, and test new ‘leap ahead’ concepts and capabilities” are:

BAE Systems, Information and Electronic Systems Integration Inc., Wayne, N.J. ($3,279,634); General Dynamics, Advanced Information Systems, San Antonio, Texas ($1,944,094); Johns Hopkins University Applied Physics Laboratory, Laurel Md. ($7,336,805); Lockheed Martin Corp., Simulation, Training and Support, Orlando, Fla. ($5,369,656); Northrop Grumman, Intelligence, Surveillance and Reconnaissance Systems Division, Columbia, Md. ($344,097); Science Applications International Corporation, San Diego, Calif. ($2,821,725); SPARTA, Columbia, Md. ($8,603,617).

While little-known outside the defense and intelligence establishment, SPARTA describes its “core business areas” as “strategic defense and offense systems, tactical weapons systems, space systems.” Its security and intelligence brief includes “intelligence production, computer network operations, and information assurance.”

Investigative journalist James Bamford wrote in The Shadow Factory that SPARTA “hired Maureen Baginski, the NSA’s powerful signals intelligence director, in October 2006, as president of its National Security Systems Sector.” According to Bamford, the firm, like others in the netherworld of corporate spying are always on the prowl for intelligence analysts “to pursue access and exploitation of targets of interest.”

Given their spooky résumé, information on SPARTA’s contracts are hard to come by. Indeed, the firm claims that under Section 508 of the Rehabilitation Act they are exempt from providing the public with information because their products involve “the operation, or use of… intelligence activities… related to national security, command and control of military forces, equipment that is an integral part of a weapon or weapons system, or systems which are critical to the direct fulfillment of military or intelligence missions.” How’s that for openness and transparency! One can only hazard a guess as to the firm’s role in devising DARPA’s “leap-ahead” National Cyber Range.

While the initial outlay of defense funds for NCR may appear to be a substantial amount of boodle for enterprising contractors, it is merely a down payment on Phase I of the project. Melissa Hathaway, the Obama administration’s director of the Joint Interagency Cyber Task Force said, “I don’t believe that this is a single-year or even a multi-year investment–it’s a multi-decade approach.” Hathaway, a former consultant at the spooky Booz Allen Hamilton corporation, told the Intelligence and National Security Alliance (INSA) in April,

Building toward the architecture of the future requires research and development that focuses on game-changing technologies that could enhance the security, reliability, resilience and trustworthiness of our digital infrastructure. We need to be mindful of how we, government and industry together, can optimize our collective research and development dollars and work together to improve market incentives for secure and resilient hardware and software products, new security innovation, and secure managed services. (“Remarks by Melissa E. Hathaway, Acting Senior Director for Cyberspace for the National Security and Homeland Security Councils,” INSA, April 30, 2009)

That Hathaway chose INSA as a forum is hardly surprising. Describing itself as a “non-profit professional association created to improve our nation’s security through an alliance of intelligence and national security leaders in the private and public sectors,” INSA was created by and for contractors in the heavily-outsourced shadow world of U.S. intelligence. Founded by BAE Systems, Booz Allen Hamilton, Computer Sciences Corporation, General Dynamics, Hewlett-Packard, Lockheed Martin, ManTech International, Microsoft, the Potomac Institute For Policy Studies and Science Applications International Corporation, The Washington Post characterized INSA as “a gathering place for spies and their business associates.”

“Partners” who benefit directly from the launch of DARPA’s National Cyber Range. No doubt, Hathaway’s remarks are music to the ears of “beltway bandits” who reap hundreds of billions annually to fund taxpayer-fueled “national security priorities.” That the Pentagon is richly rewarding INSA-connected firms with documented track records of “misconduct such as contract fraud and environmental, ethics, and labor violations,” according to the Project on Government Oversight’s (POGO) Federal Contractor Misconduct Database (FCMD) hardly elicits a yawn from Congress.

Among the corporations selected by the agency to construct the National Cyber Range, Lockheed Martin leads the pack in “Misconduct $ since 1995″ according to POGO, having been fined $577.2 million (No. 1); Northrop Grumman, $790.4 million (No. 3); General Dynamics, $63.2 million (No. 4); BAE Systems, $1.3 million (No. 6); Science Applications International Corporation (SAIC), $14.5 million (No. 9); Johns Hopkins University, $4.6 million, (No. 81)

But as disturbing as these figures are, representing corporate grifting on a massive scale, equally troubling is the nature of the project itself. As Aviation Week reports, “Devices to launch and control cyber, electronic and information attacks are being tested and refined by the U.S. military and industry in preparation for moving out of the laboratory and into the warfighter’s backpack.”

High-Tech Tools for Aggressive War

The American defense establishment is devising tools that can wreck havoc with a keystroke. DARPA is currently designing “future attack devices” that can be deployed across the imperialist “battlespace” by the “non-expert,” that is by America’s army of robosoldiers. According to Aviation Week, one such device “combines cybersleuthing, technology analysis and tracking of information flow. It then offers suggestions to the operator on how best to mount an attack and, finally, reports on success of the effort.”

The heart of this attack device is its ability to tap into satellite communications, voice over Internet, proprietary SCADA networks–virtually any wireless network. SCADA (supervisory control and data acquisition) is of particular interest since it is used to automatically control processes at high-value targets for terrorists such as nuclear facilities, power grids, waterworks, chemical plants and pipelines. The cyberattack device would test these supposedly inviolate networks for vulnerabilities to wireless penetration. (David A. Fulghum, “Network Attack Weapons Emerge,” Aviation Week, May 21, 2009)

As can be expected, the Pentagon’s rhetorical mise-en-scène is always a purely “defensive” response to future depredations by nefarious and shadowy forces threatening the heimat. In fact, the United States has systematically employed battlefield tactics that target civilian infrastructure as a means of breaking the enemy’s will to fight. Stretching across the decades, from Southeast Asia to Iraq to Yugoslavia, imperialist strategists have committed war crimes by targeting the electrical grid, water supply and transportation- and manufacturing infrastructure of their adversaries.

The NCR will potentially serve as a new and improved means to bring America’s rivals to their knees. Imagine the capacity for death and destruction implicit in a tool that can, for example, at the push of a button cause an adversary’s chemical plant to suddenly release methyl isocyanate (the Bhopal effect) on a sleeping city, or a nuclear power plant to go supercritical, releasing tens of billions of curies of radioactive death into the atmosphere?

During NATO’s 1999 “liberation” of the narco-state Kosovo from the former Yugoslavia, American warplanes dropped what was described as a graphite “blackout bomb,” the BLU-114/B “soft bomb” on Belgrade and other Serbian cities during its war of aggression. As the World Socialist Web Site reported at the time,

A particularly dangerous consequence of the long-term power blackout is the damage to the water systems in many Yugoslav cities, which are dependent on pumping stations run by electrical power. Novi Sad, a city of 300,000 which is the capital of the Vojvodina province of Serbia, has been without running water for eight days, according to residents. Families have been compelled to get water from the Danube river to wash and operate the toilet, and a handful of wells to provide drinking water.

Sewage treatment plants have also been shut down, with the result that raw, untreated sewage has begun to flow into the network of rivers that feed into the Danube, central Europe’s most important waterway. (Marty McLaughlin, “Wall Street celebrates stepped-up bombing of Serbia,” World Socialist Web Site, May 5, 1999)

With technological advances courtesy of DARPA’s National Cyber Range and their “private-sector partners,” the potential for utterly devastating societies ripe for resource extraction by American corporatist war criminals will increase exponentially. As Wired reported,

Comparisons between nuclear and cyberweapons might seem strained, but there’s at least one commonality. Scholars exploring the ethics of wielding logic bombs, Trojan horses, worms and bots in wartime often find themselves treading on ground tilled by an earlier generation of Cold War nuclear gamesmen.

“There are lots of unknowns with a cyberattack,” says Neil Rowe, a professor at the Center for Information Security Research at the U.S. Naval Postgraduate School, who rejects cyberattacks as a legitimate tool of war. “The potential for collateral damage is worse than nuclear technology…. With cyber, it can spread through the civilian infrastructure and affect far more civilians.” (Marty Graham, “Welcome to Cyberwar Country, USA,” Wired, February 11, 2008)

Initiatives such as the National Cyber Range are fully theorized as one facet of “network-centric warfare,” the Rumsfeldian “Revolution in Military Affairs.” Durham University geographer Stephen Graham describes the Pentagon notion that dominance can be achieved through “increasingly omnipotent surveillance and ’situational awareness’, devastating and precisely-targeted aerial firepower, and the suppression and degradation of the communications and fighting ability of any opposing forces.”

Indeed, these are integrated approaches that draw from corporate management theory to create “continuous, always-on support for military operations in urban terrain,” an imperialist battlespace where Wal-Mart seamlessly morphs into The Terminator.

Notebook novo (Dell A860), hardware novo, e lá vou eu instalar o ubuntu 8.10.

Tiro o note da caixa, jogo os cds do vista, drivers, blablabla dentro da caixa, e tiro meu cd do ubuntu 8.10.

A instalação correu normalmente, e o sistema já iniciou com o driver da vga intel X3100 habilitado e com o compiz ativado, som, bluetooth, tudo detectado e funcionando, a única coisa que não foi detectada foi a placa wi-fi, modelo Atheros AR242x 802.11abg, vamos então instalar a placa..

Primeiro procurei no google como instalar a placa atheros, minhas pesquisas me retomaram ao driver opensource madwifi, porém, no site do madwifi está tudo muito confuso de se instalar, procurei então por madwifi no ubuntu 8.10, e encontrei no forum do Ubuntu o seguinte post.

Mas antes de instalar o madwifi, desabilite o driver que o ubuntu tentou (sem sucesso) habilitar para sua placa:

Vá em Sistema/Administração/Drivers de Hardware e desabilite o driver atheros, reinicie o pc para ele entrar sem carregar o driver.

Driver descarregado, certifique-se que ele não seja mais carregado pelo kernel, usando um editor de texto abra o arquivo blacklist:

sudo gedit /etc/modprobe.d/blacklist

Vá ao fim do arquivos e digite numa nova linha:

blacklist ath5k

Feche e salve o arquivo.

Agora sim vamos instalar o madwifi. Para compilar o driver, você irá precisar do pacote build-essential do Ubuntu, esse pacote instalará as ferramentas necessárias para compilar qualquer pacote no seu sistema, no terminal digite:

sudo apt-get install build-essential

Agora, de acordo com o post do forum, baixe o arquivo dos fontes do madwifi:

http://snapshots.madwifi-project.org/madwifi-hal-0.10.5.6-current.tar.gz

Extraia o conteúdo do arquivo e pelo terminal entre na pasta criada:

cd madwifi-hal-0.10.5.6-r3879-20081204

Use o comando make para compilar o driver:

make

Após compilar use o make novamente para instalar o driver:

sudo make install

Reinicie o pc e o driver deverá funcionar, se por algum motivo ele não funcionar, tente carregar o driver manualmente, digite no terminal:

sudo modprobe ath_pci

Pronto, wi-fi funcionando.

Fontes:

www.google.com

http://ubuntuforum-br.org/index.php?topic=46398.0

–

Editado em 11/11/2009:

No Ubuntu 9.10 foi tudo tranquilo, e não precisou instalar nenhum driver.

I don’t know why but with ath5k driver doesn’t work anymore.

***Actually i gotcha …. this freacking wifi card …. well turn off the computer … and disconnect the plug now press now press the computer’s button … that should consume the residual voltage. and now start the pc. this fucking atheros works again with ath5k. WTFuck.****

someone says for a bug in the kernel

well i don’t care. i want it works.

so i have tried madwifi driver. and if you download the standard driver you can got some trouble when you try to compile it.

so this is my personal way.

you need of some programs to compile:

subversion (svn) and build essentials

sudo apt-get install subversion build-essential

now you should be able to compile.
**note if you download standard madwifi you could have some trouble compiling them

svn checkout http://svn.madwifi-project.org/madwifi/trunk madwifi ; cd madwifi ; make

** you can do sudo make install if you have not installed checkinstall.

sudo checkinstall

now we must disable the old driver ath5k :

sudo nano /etc/modprobe.d/blacklist.conf

add this

#blacklist ath5k driver
blacklist ath5k

press CTRL X
save and exit.

now we must load the driver : ath_pci

with

sudo modprobe ath_pci

well if you restart the driver will not load on you kernel , everytime you should write sudo modprobe etc etc…

to automatize

kdesudo kate /etc/modules

add the driver , so it will be loaded at the boot time

ath_pci

to check if your system has loaded ath_pci , after the rebooting you should type this

lsmod | grep ath

and you should get ath_pci (ath5k should not appear.)

NOTE FOR KARMIC

when you compile you could get this message

e needs E or Fmake C ./tools all || exit 1

and when you type

sudo make install

your could get some errors… this is bad but if your look well you can still add ath_pci on your kernel…
so just reboot and then use ath_pci like said in this article. here on kubuntu 9.10 tested and it works

If you are trying to install wireless driver for linux in your ubuntu or debian machine try the following bash script in order to get read of the problem. For this you have to use madwifi and have to do modprobe as being the super user or root user (sudo). Here I will first download the madwifi from their site and then untar it then, modprobe the required drivers.

Please comment about your result.

#!/bin/bash

wget -c http://snapshots.madwifi.org/special/madwifi-ng-r2756+ar5007.tar.gz
tar xvf madwifi-ng-r2756+ar5007.tar.gz
cd madwifi-ng-r2756+ar5007

sudo make install
sudo modprobe ath_pci
sudo modprobe wlan_scan_sta

Obs.: Este post é válido para os notebook’s da série C700BR ou afins que possuem o controlador de redes wireless Atheros:

• AR5418+AR5133

• AR5416+AR5133

• AR5416+AR2133

• AR9160

• AR9280

• AR9281

• AR9285

• AR9102 (AHB)

• AR9103 (AHB)

• AR5210 – 802.11a (Crete/fez)

• AR5211 – 802.11ab (Oahu)

• AR5212 – 802.11abg (Venice)

• AR5213 – 802.11abg (Hainan)

• AR2413/4 – 802.11bg (Griffin)

• AR5413/4 – 802.11abg (Eagle)

• AR5423/4 – 802.11abg (Condor) (PCI-E)

• AR2425 – 802.11bg (Swan) (PCI-E)

• AR2417 – 802.11bg (Nala) (PCI-E)

Para descobrir qual o seu controlador, dê o comando lspci | grep Atheros e verifique!

Se o seu controlador nao está listado mas é atheros, siga o post e acompanhe alguma mensagem de erro, se tiver.

Ok! Agora, mãos a obra!

O madwifi é um conjunto de drivers de placas wireless, em especial, as que possuem o chipset atheros, na versão compatível e compilável do linux. Sem mais delongas, vamos lá!

Bem, para facilitar a vida, temos que preparar o terreno antes de começar a plantar (blah!). Vá até o gerenciador de drivers sinapticos (em ambiente gráfico) ou no aptitude (shell). Procure por linux-restricted-modules. Remova-os! Sim, pode remover sem preocupações. Explicação:

O linux-restricted-modules é um modulo que tem a função de auxiliar os usuários novatos do ubuntu, porém, não é o que acontece no caso das placas atheros. Para as placas funcionarem, o modulo tem que ser retirado para ser colocado no lugar os “modulos” do madwifi.

Vá a um shell, como root, e mate todos os processos do networkmanager. Por mais bonzinho que ele tente ser, acaba atrapalhando o serviço!

Vê o numero do processo:
# ps ax | grep nm

Mata-lo:
# kill -9 [numero]

Baixe alguns pacotes necessários para a compilação:

# apt-get install build-essential libncurses5-dev kernel-package

A versão que usei foi a 0.9.4, compactada em tar.gz, baixada do site souceforge.net. Depois de fazer o download, descompacte:

$ tar -xzvf madwifi-0.9.4.tar.gz

Após a descompactação, crie uma pasta chamada modules em/usr/src e mova a pasta madwifi-0.9.4 que foi descompactada lá para dentro:

# mv madwifi-0.9.4 /usr/src/modules

Entre na pasta e agora sim, vamos a destruição:

# make

Se tudo correr bem (o que nao acontece sempre!), prossiga:

# make install

Se tudo ainda continuar bem, recarregue o módulo ath_pci :

# modprobe -e ath_pci

# modprobe ath_pci

Agora verifique se nao aconteceu nada de errado dando uma espiada no dmesg:

# dmesg

Se nao apareceu nenhuma mensagem de erro, sua placa já está pronta para usar.

Uma possível mensagem de erro:

wifi%d: unable to attach hardware: ‘Hardware didn’t respond as expected’ (HAL status 3)

Caso aconteça esta, reincie seu notebook e verifique.

The MadWifi project is …

… a team of volunteer developers working on Linux kernel drivers for Wireless LAN devices with Atheros chipsets. We currently provide three drivers, MadWifi, ath5k and ath9k.

MadWifi is one of the most advanced WLAN drivers available for Linux today. It is stable and has an established userbase. The driver itself is open source but depends on the proprietary Hardware Abstraction Layer (HAL) that is available in binary form only. The current stable release is v0.9.4.

Download and Check

$ wget http://ufpr.dl.sourceforge.net/sourceforge/madwifi/madwifi-0.9.4.tar.bz2
$ tar -zxvf madwifi-0.9.4.tar.gz
$ cd madwifi-0.9.4/
$ cd scripts/
$ ./madwifi-unload.bash
$ ./find-madwifi-modules.sh $(uname -r)
$ cd ..

Build and comment

$ make

Checking requirements… ok.
Checking kernel configuration… ok.
make -C /lib/modules/2.6.18-92.1.13.el5/build SUBDIRS=/home/rafa/0_Down/1_Source/WireLess/madwifi-0.9.4 modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-92.1.13.el5-i686′
CC [M]  /home/rafa/0_Down/1_Source/WireLess/madwifi-0.9.4/ath/if_ath.o
In file included from <command line>:1:
/home/rafa/0_Down/1_Source/WireLess/madwifi-0.9.4/ath/../include/compat.h:140: error: redefinition of ’skb_end_pointer’
….
….
….
make[3]: *** [/home/rafa/0_Down/1_Source/WireLess/madwifi-0.9.4/ath/if_ath.o] Error 1
make[2]: *** [/home/rafa/0_Down/1_Source/WireLess/madwifi-0.9.4/ath] Error 2
make[1]: *** [_module_/home/rafa/0_Down/1_Source/WireLess/madwifi-0.9.4] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.18-92.1.13.el5-i686′
make: *** [modules] Error 2

$ cd include
$ cp compat.h compat.h.old
$ vim compat.h
$ diff -U 3 -dHrN -- compat.h compat.h.old
$cat compat.h.diff

— compat.h 2009-03-19 02:02:49.000000000 -0400
+++ compat.h.old 2009-03-18 19:09:37.000000000 -0400
@@ -134,7 +134,7 @@
#define IRQF_SHARED SA_SHIRQ
#endif
-/* #if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,22)
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,22)
#include
static inline unsigned char *skb_end_pointer(const struct sk_buff *skb)
{
@@ -165,7 +165,7 @@
{
skb->mac.raw = skb->data;
}
-#endif */
+#endif
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,24)
#define CTL_AUTO -2

$ cd ../
$ make

Checking requirements… ok.
Checking kernel configuration… ok.
make -C /lib/modules/2.6.18-92.1.13.el5/build SUBDIRS=/home/rafa/0_Down/1_Source/WireLess/madwifi-0.9.4 modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-92.1.13.el5-i686′
CC [M]  /home/rafa/0_Down/1_Source/WireLess/madwifi-0.9.4/ath/if_ath.o
…
…
…
make[1]: Entering directory `/home/rafa/0_Down/1_Source/WireLess/madwifi-0.9.4/tools’
gcc -o athstats -g -O2 -Wall -I. -I../hal -I.. -I../ath  athstats.c
gcc -o 80211stats -g -O2 -Wall -I. -I../hal -I..  80211stats.c
gcc -o athkey -g -O2 -Wall -I. -I../hal -I..  athkey.c
gcc -o athchans -g -O2 -Wall -I. -I../hal -I..  athchans.c
gcc -o athctrl -g -O2 -Wall -I. -I../hal -I..  athctrl.c
gcc -o athdebug -g -O2 -Wall -I. -I../hal -I..  athdebug.c
gcc -o 80211debug -g -O2 -Wall -I. -I../hal -I..  80211debug.c
gcc -o wlanconfig -g -O2 -Wall -I. -I../hal -I..  wlanconfig.c
gcc -o ath_info -g -O2 -Wall ath_info.c
make[1]: Leaving directory `/home/rafa/0_Down/1_Source/WireLess/madwifi-0.9.4/tools’

# make install

sh scripts/find-madwifi-modules.sh 2.6.18-92.1.13.el5
for i in ath/ ath_hal/ ath_rate/ net80211/; do \
make -C $i install || exit 1; \
done
…
…
…
install -d /usr/local/man/man8
install -m 0644 man/*.8 /usr/local/man/man8
make[1]: Leaving directory `/home/rafa/0_Down/1_Source/WireLess/madwifi-0.9.4/tools’

Configuration and re-boot

# modprobe ath_pci
# iwconfig

lo        no wireless extensions.

eth1      no wireless extensions.

eth2      no wireless extensions.

sit0      no wireless extensions.

wifi0     no wireless extensions.

ath0      IEEE 802.11b  ESSID:”"

Mode:Managed  Channel:0  Access Point: Not-Associated
Bit Rate:0 kb/s   Tx-Power:0 dBm   Sensitivity=1/1
Retry:off   RTS thr:off   Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/70  Signal level=-256 dBm  Noise level=-256 dBm
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:0   Missed beacon:0

# ifconfig ath0 up
# wlanconfig ath0 list scan

SSID            BSSID              CHAN RATE  S:N   INT CAPS
00:1f:41:23:1a:e1    1   54M  1:0   100 EPSs WPA WME
Miss Price    00:1b:11:90:60:f8    6   54M  5:0   100 ESs
00:11:09:0d:50:85   11   54M 49:0   100 E
AAGUAR      00:22:15:1d:90:0c    5   54M 22:0   100 EPs
NICOLE        00:23:f8:86:23:2c    6   54M  3:0   100 EPSs

# iwconfig ath0 essid "WaterflyGalactica"
# dhclient ath0

Internet Systems Consortium DHCP Client V3.0.5-RedHat
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wifi0: unknown hardware address type 801
/sbin/dhclient-script: configuration for ath0 not found. Continuing with defaults.
…
…
…
/sbin/dhclient-script: configuration for ath0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 78: ath0: No such file or directory
bound to 192.168.1.113 — renewal in 3223326 seconds.

# ping ftp.udec.cl

PING www2.udec.cl (152.74.16.10) 56(84) bytes of data.

— www2.udec.cl ping statistics —

5 packets transmitted, 0 received, 100% packet loss, time 3999ms

grrrrrrrr !!!!

# reboot

…
…
…

# ifconfig ath0 up
# iwconfig ath0 essid WaterflyGalactica
# dhclient ath0

Internet Systems Consortium DHCP Client V3.0.5-RedHat
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:13:46:e3:1b:c7
Sending on   LPF/ath0/00:13:46:e3:1b:c7
Sending on   Socket/fallback
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.254
bound to 192.168.1.113 — renewal in 3428548 seconds.

$ ping www.diq.udec.cl

PING melquiades.diq.udec.cl (152.74.13.10) 56(84) bytes of data.
64 bytes from melquiades.diq.udec.CL (152.74.13.10): icmp_seq=1 ttl=54 time=50.6 ms
64 bytes from melquiades.diq.udec.CL (152.74.13.10): icmp_seq=2 ttl=54 time=40.7 ms
64 bytes from melquiades.diq.udec.CL (152.74.13.10): icmp_seq=3 ttl=54 time=32.5 ms

Automatic connection

$ cat /etc/sysconfig/network-scripts/ifcfg-ath0

# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
TYPE=Wireless
DEVICE=ath0
BOOTPROTO=dhcp
ONBOOT=yes
USERCTL=yes
IPV6INIT=no
ESSID=WaterflyGalactica
CHANNEL=11
RATE=’54 Mb/s’

The END

Det trådlösa nätverket fungerar inte direkt efter installation så vi får ladda ner, kompilera och installera drivrutinen manuellt.
——————————–
I en terminal skriver du följande

mkdir source
cd source
wget http://snapshots.madwifi-project.org/madwifi-hal-0.10.5.6-current.tar.gz
tar xzvf madwifi-hal-0.10.5.6-current.tar.gz
cd madwifi-hal-0.10.5.6-r3816-20080724
sudo apt-get install build-essential linux-headers-$(uname -r)

Här gör vi en ny mapp, hämtar drivrutinen vi ska använda, packar upp den och hämtar ett par paket som
är nödvändiga.

Nu installerar vi drivrutinen.

make
sudo make install
sudo modprobe ath_pci

För att det nu ska funka måste vi lägga till en rad i /etc/modules och då gör vi följande.
I terminalen skriver du

sudo gedit /etc/modules

och lägger till

ath_pci

Detta får modulen att laddas automatiskt vid uppstart.

Av någon anledning buggar detta sig efter varje kernel-update så du får göra följande efter varje kernel-update:
I terminalen letar du dig fram till där du lagt madwifi-mappen(/home/dittnamn/source/madwifixxxx).
Där skriver du följande rader

make clean
make
sudo make install

Sono ancora troppo contento per essere riuscito finalmente a far funzionare la rete cifrata in wpa2 sia con il modulo ath_pci che con quello in sviluppo ath5k, quindi salvo subito le configurazioni pubblicandole nel blog, magari potranno servire anche ad altri

Le configurazioni per netcfg2 sono quelle classiche e non richiedono alcun parametro aggiuntivo, comunque:

[~] cat /etc/network.d/home
#
# Network Profile
#
CONNECTION="wireless"
DESCRIPTION=""
# Network Settings
INTERFACE=wlan0 #per ath5k
#INTERFACE=ath0 #se si usa ath_pci
HOSTNAME="acerone"
# Interface Settings
IP="static"
IFOPTS="192.168.0.6 netmask 255.255.255.0 broadcast 192.168.0.255"
GATEWAY=192.168.0.1
# DNS Settings
DNS1=208.67.222.222
DNS2=208.67.220.220
# Wireless Settings
SECURITY="wpa-config"
ESSID="marinz's_net"
KEY=""
SCAN="no"
TIMEOUT=40
# WPA Specific Settings
WPA_OPTS=""
WPA_CONF="/etc/network.d/wpa_supplicant/home.conf"


e quella per wpa_supplicant:


[~] sudo cat /etc/network.d/wpa_supplicant/home.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
fast_reauth=1
#ap_scan=2 #decommentare solo se si usa ath_pci
network={
ssid="marinz's_net"
key_mgmt=WPA-PSK
psk="di almeno 60 caratteri, max 63"
proto=WPA2
}
[~]


Bueno, he vuelto de mis vacaciones! Ya estoy despejado, descansado, asi que arranca mi año (es como decir que ya perdí un mes del año ).

Mi portátil es una Acer 4520, lindo bichito, no tengo quejas. En fin, la placa wi-fi es una Atheros5007EG, y no funcionó de buenas a primeras con Intrepid. Hay dos maneras de activarla, una muy facil, otra un poco mas… consolera, digamos.

Opción 1: Instalar los drivers backports
Conectados por cable, abrimos una consola y tipeamos:

~$ sudo apt-get install linux-backports-modules-intrepid-generic

y reiniciamos. Luego abrimos Sistema/Administración/Controladores de Hardware, deshabilitamos el soporte para Atheros 802.11 Wireless Lan y habilitamos soporte para Atheros serie 5xxx. Reiniciamos nuevamente y listo.

Opción 2: Instalar los drivers Madwifi
Usar esta opción implica bajar el código fuente de dichos drivers, compilarlos e instalarlos.

Descargar el driver:

~$ wget http://snapshots.madwifi-project.org/madwifi-hal-0.10.5.6/madwifi-hal-0.10.5.6-r3879-20081204.tar.gz

Descomprimir y entrar a la carpeta creada:
~$ tar -xvzf madwifi-hal-0.10.5.6-r3879-20081204.tar.gz
~$ cd madwifi-hal-0.10.5.6-r3879-20081204

Compilamos e instalamos:
~$ sudo make
~$ sudo make install

Por ultimo editamos el archivo de carga de módulos:
~$ sudo gedit /etc/modules

y agregamos al final la linea “ath_pci” (sin las comillas). Reiniciamos y listo.

Otra cosa, cuando instalemos una nueva versión del kernel deberemos recompilar este driver. La ventaja del mismo es que permite usar nuestra tarjeta en modo monitor, para poder hacer “auditorias wireless”. Pero eso lo dejo para una próxima entrada. Suerte!

Q: Why do some people get mad while installing wireless drivers?

Ans: Because they use Atheros chipsets and have to install madwifi.

Courtesy: The one who pwns Santa.

It’s been too long since my last blog post. I’m afraid the time and motivation had temporarily escaped me. But I am back now, with what I hope will be some handy information for someone out there in cyberspace.

I recently ordered a new Toshiba laptop, an L305-S5933, from newegg.com. It was really a great deal; I couldn’t pass it up. Upon initially recieving the laptop, I spent a few hours removing all of the pre-loaded crap software (and let me tell you, there was quite a bit), preventing annoying things from running on startup, and installing the latest and greatest Windows updates. After that, I promptly installed Kubuntu 8.10. I have to note, I found it quite humerous that there is now a Windows installer on the Ubuntu install CD. My what a long way we’ve come from the earlier days of RedHat 5.x when I first got started with Linux.

Actually, I lied, I promptly booted into the Kubuntu live CD so I could give things a go before committing to this distro. And of course, without fail, I immediately noticed my lack of an internet connection (so I guess, more appropriately put – with fail?). Anywho, this is a sticky situation I’ve found myself in a number of times before. I’ve discovered Linux + wireless = a recipe for disaster. That’s one formula I’ve had no problems remembering. There are often issues with proprietary drivers/firmware, etc… So we end up with terrible incarnations like the ndiswrapper and so forth. In this case it turns out the currently released version of the wireless driver for my wireless card was not up to date enough to handle my card. This laptop has an Atheros wifi card, identified as AR242x by lspci, which has the AR5007EG chipset. The driver for this card is the madwifi driver. The project seems to be in a chaotic state, with the stable madwifi driver lacking resources, and apparently two newer versions in the works (ath5k and ath9k, neither of which are stable).

Fortunately, the good folks at #madwifi on freenode tipped me off to a newer version of the driver. Unfortunately, this “newer version” has never been released and therefore must be built from source. You can either get the source of this driver from git (which I’ll leave to you to figure out), or you can find the most up to date snapshot here. I’ll first mention, this process involves a reboot, so it is not possible to get wireless working in the live CD environment. Before we begin, you’ll need to make sure you have both the “build-essential” and “linux-headers” packages installed on your system. Start off by extracting the driver files from the archive:

tar xzf madwifi-hal-0.10.5.6-r3931-20090125.tar.gz

Be sure to substitute the correct file name here. Next “cd” into your newly extracted directory and run:

make
sudo make install

When you “make install”, this should remove the old drivers from your system and install the new drivers. Once you reboot, assuming you are running NetworkManager, you should be good to go. If you ever get a kernel update available via adept or apt-get upgrade, you may want to consider not installing it. If you do, you will have to rebuild this driver in the new kernel.

Do not blacklist the Atheros driver that comes with kubuntu, or you will find your computer will lock up during boot. If this happens, simply use the switch on the front of the laptop to disable the device until you have installed a new driver.

Hopefully I will be back soon with a review of KDE 4.2, which releases tomorrow.

ubuntu jaunty issues on dell vostro

here is how you can make wireless work on dell vostro

https://help.ubuntu.com/community/WifiDocs/Driver/Atheros

you need to reboot after the madwifi is disbled

here is how the Hardware Driver should look

System -> Administration -> Hardware Drivers
And Support for Atheros Should be Disabled

ubuntu jaunty issues on dell vostro

here is how you can make wireless work on dell vostro

https://help.ubuntu.com/community/WifiDocs/Driver/Atheros

you need to reboot after the madwifi is disbled

here is how the Hardware Driver should look

System -> Administration -> Hardware Drivers
And Support for Atheros Should be Disabled

Well, I really wanted to test this thing out but it looks like my wireless card will never be supported…

I have an Atheros AR242x and Madwifi doesn’t work on openSUSE 11.1, ndiswrapper is a mess and compat-wireless drivers killed my card’s firmware…

Many people claim this card works…but not for me…(the card is recognized by the default drivers but the wireless network is not…so that means the card is not really working). So until this issue is fully fixed without using weird drivers, like in Ubuntu, it’s bye-bye openSUSE for me…or at least when I can have a wired-LAN computer. My laptop seemed to work fine with wired-LAN but I’m 20 feet away from the router on another room, so a long cable is not by best choice…

Anyways, I encourage you to try it out and test if it works for you. At least for me it didn’t…

En vista de que esta tarjeta inalámbrica es la que más quebraderos de cabeza está dando últimamente, he decidido rescatar un viejo script que tenía por ahí para un portátil, voy a explicarlo paso a paso:

1 – Instalamos los paquetes necesarios para compilar:

sudo apt-get install linux-headers-`uname-r` build-essential

2 – Bajamos el siguiente paquete:

Madwifi

3 – Descomprimimos y vamos con el terminal a la carpeta en la que hemos descomprimido

cd /home/tuusuario/carpetadescomprimida

4 – Compilamos

sudo make

5 – Instalamos

sudo make install

6 – Insertamos el módulo en el kernel:

sudo modprobe ath_pci

7 – Configuramos el módulo para que se cargue siempre al inicio:

sudo gedit /etc/modules

8 – Y agregamos lo siguiente al final del archivo:

ath_pci

Reinicias y… ¡listo!

Actualización:

Ya no es necesario utilizar madwifi, desde Ubuntu 9.04 las tarjetas Atheros funcionan perfectamente.

Imagen de cabecera: Mashup 3.7 icon theme

Para os que se depararam com a mensagem de erro

wifi%d: unable to attach hardware: ‘Hardware didn’t respond as expected’ (HAL status 3)

Segue aqui mais um post informando como resolver!

Primeira coisa é saber a versão do kernel de sua maquina. Para saber isso, uname -r

Para kernel com versão superior à 2.6.26 (>=2.6.27), baixe este aquivo. Para kernel com versão inferior a 2.6.27 (<=2.6.26), baixe este arquivo.

Descompacte o arquivo:

$ tar jxvf compat-wireless-$(date -I).tar.bz2

Entre na pasta e compile:

# make

Em alguns casos aparece uma mensagem de erro informando que nao foi encontrado o diretório. Verifique se no caminho da pasta nao há diretórios com acentuações!

Algumas mensagens de erro aparece durante a compilação mas nada que comprometa o assunto do post! Se ocorrer um erro durante o make que faça-o parar de compilar, por favor, poste aqui!

Agora instalando…

# make install

Bem, agora está tudo instalado, porém, é preciso derrubar os módulos antigos e carregar os novos, para isso, existe alguns script’s na agulha para faze-lo:

# make unload

# make load

Depois é só reiniciar o computador e navegar!