I have not installed the madwifi specific kernel stuff (kdml and hal-kdml) from atrpms. I have installed with wpa rpms. And my Atheros card is working with almost no work on my part (other than runing wpa_supplicant as a deamon). Nice!
On Mon, Jun 18, 2007 at 08:03:39AM -0400, Robert Moskowitz wrote:> I have not installed the madwifi specific kernel stuff (kdml and > hal-kdml) from atrpms. I have installed with wpa rpms. > > And my Atheros card is working with almost no work on my part (other > than runing wpa_supplicant as a deamon). > > Nice!But how is that supposed to work? Perhaps you don't have an atheros chipset at all? If you have an atheros chipset then you will need madwifi/dadwifi and hal/openhal to use it. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20070618/cfff9886/attachment-0001.sig>
Robert Moskowitz
2007-Jun-18 14:05 UTC
[CentOS] Re: Madwifi just seems to work in Centos 5
Axel Thimm wrote:> On Mon, Jun 18, 2007 at 08:03:39AM -0400, Robert Moskowitz wrote: > >> I have not installed the madwifi specific kernel stuff (kdml and >> hal-kdml) from atrpms. I have installed with wpa rpms. >> >> And my Atheros card is working with almost no work on my part (other >> than runing wpa_supplicant as a deamon). >> >> Nice! >> > > But how is that supposed to work? Perhaps you don't have an atheros > chipset at all? If you have an atheros chipset then you will need > madwifi/dadwifi and hal/openhal to use it.Oh, it is definitely the Atheros chipset. Given to me by my friends at Atheros at one of the 802.11 meetings over a year ago.... I was supprised/shocked. I was watching the boot and saw an attempt to aquire an IP address for wifi0. Gee, I had not configured my wireless card at all. Why did Kudzu discover the card, I had never installed the madwifi kernel drivers. Yeah, I DID install the WPA and wireless tools (wpa_supplicant, wpa_cli, wpa_dui, iwconfig, wlanconfig, etc) but not the madwifi-kmdl or madwifi-hal-kdml. So what is going on? All I had to do was to get the wpasupplicant running as a deamon, reading my wpasupplicant.conf file (with the PSK for my network), and I was Associated. Then grab a dhcp lease and off I went wirelessly. Is there any tool to analyse the kernel to see if the madwifi drivers are in the sauce?
Robert Moskowitz
2007-Jun-18 14:51 UTC
[CentOS] Re: Madwifi just seems to work in Centos 5
Andy Green wrote:> Robert Moskowitz wrote: > >> Axel Thimm wrote: >> >>> On Mon, Jun 18, 2007 at 08:03:39AM -0400, Robert Moskowitz wrote: >>> >>> >>>> I have not installed the madwifi specific kernel stuff (kdml and >>>> hal-kdml) from atrpms. I have installed with wpa rpms. >>>> >>>> And my Atheros card is working with almost no work on my part (other >>>> than runing wpa_supplicant as a deamon). >>>> >>>> Nice! >>>> >>>> >>> But how is that supposed to work? Perhaps you don't have an atheros >>> chipset at all? If you have an atheros chipset then you will need >>> madwifi/dadwifi and hal/openhal to use it. >>> >> Oh, it is definitely the Atheros chipset. Given to me by my friends at >> Atheros at one of the 802.11 meetings over a year ago.... >> > > Well, we'll see... type lspci to hear about the card and lsmod to see > what modules you have loaded, post the results.Will be rebooting to Centos 5 shortly. And with the lvm mounting (vgscan and vgchange) instructions, I might just get my email switched over and just respond from there!
Robert Moskowitz
2007-Jun-18 15:55 UTC
[CentOS] Re: Madwifi just seems to work in Centos 5
Migration in progress. But fonts are wrong in Thunderbird.... Andy Green wrote:> Robert Moskowitz wrote: > >> Axel Thimm wrote: >> >>> On Mon, Jun 18, 2007 at 08:03:39AM -0400, Robert Moskowitz wrote: >>> >>> >>>> I have not installed the madwifi specific kernel stuff (kdml and >>>> hal-kdml) from atrpms. I have installed with wpa rpms. >>>> >>>> And my Atheros card is working with almost no work on my part (other >>>> than runing wpa_supplicant as a deamon). >>>> >>>> Nice! >>>> >>>> >>> But how is that supposed to work? Perhaps you don't have an atheros >>> chipset at all? If you have an atheros chipset then you will need >>> madwifi/dadwifi and hal/openhal to use it. >>> >> Oh, it is definitely the Atheros chipset. Given to me by my friends at >> Atheros at one of the 802.11 meetings over a year ago.... >> > > Well, we'll see... type lspci to hear about the card and lsmod to see > what modules you have loaded, post the results.Here is the results from lspci and lsmod. There is ONE madwifi rpm installed: madwifi-0.9.2.1-2.el5.rf.i386.rpm and for wpa: wpa_supplicant-0.4.8-10.1.fc6.i386.rpm cat lspci.lst 00:00.0 Host bridge: ATI Technologies Inc RS200/RS200M AGP Bridge [IGP 340M] (rev 02) 00:01.0 PCI bridge: ATI Technologies Inc PCI Bridge [IGP 340M] 00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 02) 00:07.0 ISA bridge: ALi Corporation M1533/M1535 PCI to ISA Bridge [Aladdin IV/V/V+] 00:08.0 Modem: ALi Corporation M5457 AC'97 Modem Controller 00:09.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01) 00:0b.0 CardBus bridge: O2 Micro, Inc. OZ711M1/MC1 4-in-1 MemoryCardBus Controller (rev 20) 00:0b.1 CardBus bridge: O2 Micro, Inc. OZ711M1/MC1 4-in-1 MemoryCardBus Controller (rev 20) 00:0b.2 System peripheral: O2 Micro, Inc. OZ711Mx 4-in-1 MemoryCardBus Accelerator 00:10.0 IDE interface: ALi Corporation M5229 IDE (rev c4) 00:11.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU] 00:12.0 USB Controller: NEC Corporation USB (rev 43) 00:12.1 USB Controller: NEC Corporation USB (rev 43) 00:12.2 USB Controller: NEC Corporation USB 2.0 (rev 04) 00:13.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705M Gigabit Ethernet (rev 03) 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon IGP 330M/340M/350M cat lsmod.lst Module Size Used by autofs4 23749 2 hidp 23105 2 rfcomm 42457 0 l2cap 29633 10 hidp,rfcomm bluetooth 53925 5 hidp,rfcomm,l2cap sunrpc 142973 1 ip_conntrack_netbios_ns 6977 0 ipt_REJECT 9537 1 xt_state 6209 3 ip_conntrack 53153 2 ip_conntrack_netbios_ns,xt_state nfnetlink 10713 1 ip_conntrack iptable_filter 7105 1 ip_tables 17029 1 iptable_filter ip6t_REJECT 9409 1 xt_tcpudp 7105 12 ip6table_filter 6849 1 ip6_tables 18181 1 ip6table_filter x_tables 17349 6 ipt_REJECT,xt_state,ip_tables,ip6t_REJECT,xt_tcpudp,ip6_tables cpufreq_ondemand 10573 1 video 19269 0 sbs 18533 0 i2c_ec 9025 1 sbs button 10705 0 battery 13637 0 asus_acpi 19289 0 ac 9157 0 radeon 103905 2 drm 65493 3 radeon ipv6 250369 19 ip6t_REJECT lp 15849 0 joydev 13185 0 snd_ali5451 25165 1 snd_ac97_codec 87009 1 snd_ali5451 snd_ac97_bus 6337 1 snd_ac97_codec snd_seq_dummy 7877 0 snd_seq_oss 32705 0 snd_seq_midi_event 11073 1 snd_seq_oss snd_seq 49841 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 11853 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 42849 0 snd_mixer_oss 19137 1 snd_pcm_oss snd_pcm 71621 3 snd_ali5451,snd_ac97_codec,snd_pcm_oss wlan_scan_sta 16128 0 snd_timer 24901 2 snd_seq,snd_pcm snd 51909 11 snd_ali5451,snd_ac97_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 13217 1 snd pcspkr 7105 0 snd_page_alloc 13641 1 snd_pcm parport_pc 29157 1 parport 37513 2 lp,parport_pc ath_pci 86180 0 ath_rate_sample 16896 1 ath_pci wlan 172764 4 wlan_scan_sta,ath_pci,ath_rate_sample i2c_ali1535 10565 0 tg3 99781 0 i2c_ali15x3 11333 0 ath_hal 195280 3 ath_pci,ath_rate_sample serio_raw 10693 0 i2c_core 23745 3 i2c_ec,i2c_ali1535,i2c_ali15x3 dm_snapshot 20581 0 dm_zero 6209 0 dm_mirror 29713 0 dm_mod 56537 8 dm_snapshot,dm_zero,dm_mirror ext3 123081 3 jbd 56553 1 ext3 ehci_hcd 32845 0 ohci_hcd 23261 0 uhci_hcd 25421 0 So stuff is there....