HOWTO: madwifi in FC2 (& FC2T3)

[Picomp314]

make sure you add your key to the 'KEY=' line at the bottom
alright your ifcfg-ath0 will be as follows:

STARTMODE=hotplug
DEVICE=ath0
WIRELES=yes
MODE=Managed
ESSID=MSHOME
CHANNEL=6
IPADDR=192.168.0.5
GATEWAY=192.168.0.1
KEY=

as far as DNS
edit the file /etc/resolv.conf, remove all lines, and add these:

nameserver 194.168.4.100
nameserver 194.168.8.100

as far as the workgroup... that is handled by samba, and is completely seperate

[Pendragon]

Thanks for your help...

Next question... When the card is busy the computer slows down, the mouse is most affected. If I was to guess it looks like an hardware interupt conflict. (going back to my DOS/Win3.1 days)

[tinydancer]

Hi there,

I've got a Netgear WG311 and I'm running Fedora Core 2. I've built madwifi from the most recent cvs source and the ath_pci, ath_lan and wlan modules are loaded, but when I try and bring up ath0 I get the following message:

Bringing up interface ath0: ath_pci device ath0 does not seem to be present, delaying initialization.

I've been searching the forum, and various faqs, but unfortuately I haven't been able to pinpoint where I'm going wrong. My settings are as follows:

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

STARTMODE=hotplug
DEVICE=ath0
BOOTPROTO=dhcp
WIRELESS=yes
MODE=Managed
ONBOOT=yes
ESSID=any
KEY=<my-key>

/sbin/ifconfig

eth0 Link encap:Ethernet HWaddr 00:0E:2E:01:12:A4
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20e:2eff:fe01:12a4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25049 errors:0 dropped:0 overruns:0 frame:0
TX packets:23203 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:16032142 (15.2 Mb) TX bytes:7437653 (7.0 Mb)
Interrupt:9 Base address:0xd400

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:1856 errors:0 dropped:0 overruns:0 frame:0
TX packets:1856 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1876884 (1.7 Mb) TX bytes:1876884 (1.7 Mb)


/sbin/iwconfig

lo no wireless extensions.

sit0 no wireless extensions.

eth0 no wireless extensions.


/sbin/lspci -v

00:0c.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface
Subsystem: Netgear: Unknown device 4c00
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at dfffc000 (32-bit, non-prefetchable)
Memory at dffc0000 (32-bit, non-prefetchable) [size=128K]
Capabilities: <available only to root>

Thanks

[Picomp314]

this is not the driver for you.
http://acx100.sf.net

[tinydancer]

Thanks ever so much :-)

[ravalox]

I got the kernel source rpm installed and it dumped a whole mess of stuff in usr/src/redhat/SOURCES that hardly seem applicable to doing a make all or even a make oldconfig. Am I missing a vital install step like a -notatotalmess option in doing a source rpm?

[emarquezarreaza]

I tried the RPM http://www.fedoraforum.org/forum/sho...6708#post96708, it didn't work because of Kernel incompatability and RPM for 2.6.8.1 are still experimental

Also, I tried to compile using this HOWTO. But, it didn't work either

Therefore, if someone could give a nice how-to, I would greatly appreciate it

[Picomp314]

there is a problem the current madwifi drivers have with kernel 2.6.8.x, several patches for the madwifi tree have been released
http://users.informatik.haw-hamburg....0821.patch.bz2 download that and etract within the madwifi directory
then apply the patch, and it should build fine

[emarquezarreaza]

Thank you again!
After a whole lot of reading and almost 5 hours all together. I am finally Wireless

[bohlke]

Can anyone help me with this, I am hell bent to get this driver to compile with 2.6.7


Ok so I found through some digging that the IEEE_802.11 flag wasnt set in my kernel, which then of course explained the unresolved symbols. I am so close now however it appears that the modules are missing references to their own libraries?? Anyone have any idea why I am getting the following warnings when I try to compile the modules? FWIW the machine now reboots when I load the module which is better than a hard freeze



*** Warning: "ath_hal_init_channels" [/home/bohlke/madwifi/tmp/madwifi/ath/ath_pci.ko] undefined!
*** Warning: "ath_hal_probe" [/home/bohlke/madwifi/tmp/madwifi/ath/ath_pci.ko] undefined!
*** Warning: "ath_hal_detach" [/home/bohlke/madwifi/tmp/madwifi/ath/ath_pci.ko] undefined!
*** Warning: "ath_hal_mhz2ieee" [/home/bohlke/madwifi/tmp/madwifi/ath/ath_pci.ko] undefined!
*** Warning: "ath_hal_computetxtime" [/home/bohlke/madwifi/tmp/madwifi/ath/ath_pci.ko] undefined!
*** Warning: "_ath_hal_attach" [/home/bohlke/madwifi/tmp/madwifi/ath/ath_pci.ko] undefined!

Hopefully someone can help me with this, I "think" that these symbols are in the uuencoded file as they dont show up in any of the .c files. Any help would be great.

[aatc20]

hello guys, I am a newbie to linux, even though I have been using it for a while now, what an irony. Anyhow,
I am trying to setup my proxim orinoco silver combo card chipset atheros 8461-05. I downloaed the madwifi, kernel source 2.6.5-1.358 and compiled them. Did insmod etc. After that whenever I type ifconfig ath0 up it keeps saying
ath0: unknown interface: No such device
ifup ath0 gives me
ath_pci
ath_pci device ath0 does not seem to be present, delaying initialization.
my ifcfg-ath0 file is as followed:
STARTMODE=hotplug
DEVICE=ath0
BOOTPROTO=dhcp
WIRELESS=yes
MODE=Managed
ESSID=any
IPV6INIT=no
ONBOOT=yes
USERCTL=no
PEERDNS=no

I added the alias ath0 ath_pci line in modprobes.conf, modules.conf

nothing seems to help me. When I boot the pc with the pc card in the slot, it gets stuck at

starting pcmcia

but boots fine if the pccard is not in the slot. Will anybody please help me?

BTW, I am using a hp ze1250 amd laptop if that matters at all.

[bohlke]

Originally Posted by bohlke

Can anyone help me with this, I am hell bent to get this driver to compile with 2.6.7


Ok so I found through some digging that the IEEE_802.11 flag wasnt set in my kernel, which then of course explained the unresolved symbols. I am so close now however it appears that the modules are missing references to their own libraries?? Anyone have any idea why I am getting the following warnings when I try to compile the modules? FWIW the machine now reboots when I load the module which is better than a hard freeze



*** Warning: "ath_hal_init_channels" [/home/bohlke/madwifi/tmp/madwifi/ath/ath_pci.ko] undefined!
*** Warning: "ath_hal_probe" [/home/bohlke/madwifi/tmp/madwifi/ath/ath_pci.ko] undefined!
*** Warning: "ath_hal_detach" [/home/bohlke/madwifi/tmp/madwifi/ath/ath_pci.ko] undefined!
*** Warning: "ath_hal_mhz2ieee" [/home/bohlke/madwifi/tmp/madwifi/ath/ath_pci.ko] undefined!
*** Warning: "ath_hal_computetxtime" [/home/bohlke/madwifi/tmp/madwifi/ath/ath_pci.ko] undefined!
*** Warning: "_ath_hal_attach" [/home/bohlke/madwifi/tmp/madwifi/ath/ath_pci.ko] undefined!

Hopefully someone can help me with this, I "think" that these symbols are in the uuencoded file as they dont show up in any of the .c files. Any help would be great.

AAARRRRRRGHHHH!!!!!!

I finally got the thing to pseudo compile in the 2.6.7 kernel tree and it still locks my computer tight

I have a fujitsu 5020d does anyone have a tarball of a version of this driver that works with 2.6.7???

Please please please.......

sigh

[Picomp314]

bohlke: whenever i compile it i generally get like 30 things that are undefined
normally that doesnt cause any problems, i find it interesting that it does in your case
maybe they released some new code in the madwifi CVS
2.6.7 was by far the easiest that the madwifi source worked for me, with 2.6.8.x you had to patch the sourcecode
my best suggestion is to do a new checkout of the CVS, and hopefully any bugs are fixed
if this doesnt work PM me or AIM me and i can link you to a gzipped backup i have of some an older madwifi CVS

aatc20:
what commands are you using to bring the card up when you boot?
normally i do

ifconfig ath0 up
dhclient ath0

that seems to be the best combination
also, if there is another ethernet interface i.e. eth0 i would do ifconfig eth0 down: because sometimes they conflict with one another

[aatc20]

Picomp, thanks for your reply. When I manage to get the os loaded without the pcmcia card, I just type

ifconfig ath0 up
it says ath0: no such interface

if I type

ifup ath0 it says
ath0 does not seem to be present, delaying initialization.

I dont have the laptop with me right now so these are from my memory(no exact error msg) but you get the point.

Can you please tell me how I can get the OS to see the ath0 interface. I also tried the GUI system-network-config. It shows the ath0 interface but when I try to activate it, it says
ath0 does not seem to be present, delaying initialization.

Thanks for your help in advance. I greatly appreciate it.

[bohlke]

Originally Posted by aatc20

Picomp, thanks for your reply. When I manage to get the os loaded without the pcmcia card, I just type

ifconfig ath0 up
it says ath0: no such interface

if I type

ifup ath0 it says
ath0 does not seem to be present, delaying initialization.

I dont have the laptop with me right now so these are from my memory(no exact error msg) but you get the point.

Can you please tell me how I can get the OS to see the ath0 interface. I also tried the GUI system-network-config. It shows the ath0 interface but when I try to activate it, it says
ath0 does not seem to be present, delaying initialization.

Thanks for your help in advance. I greatly appreciate it.

FWIW I got the same type of error when I loaded an older version of madwifi, I looked in /var/log/messages and it said:

Sep 14 23:08:03 lifebook kernel: ath%%d: unable to attach hardware; HAL status 3488169984

which I assume means that the driver is loaded but isnt seeing the hardware correctly. Another thing I noticed is my laptop assigned eth2 to the ath_pci module, if you do an ifconfig -a it will list all of the adapters possibly its named something else

I am still having trouble but at least I am getting to reboot often