Re: [gentoo-user] Problems with madwifi

[Pupeno]

On Wednesday 17 August 2005 10:05, Robert Crawford wrote:
> On Tuesday 16 August 2005 11:52 pm, Pupeno wrote:
> > Hello,
> > I have an IBM wifi card that has an Atheros chipset that was working
> > perfectly with the madwifi driver untill the update that happened
> > recently, now it is a big mess.
> > When I plug it in or at boot if it is plugged in when coldplugging pnp
> > devices I got somethig like:
> >
> > PREEMPT
> > Modules linked in: md5 ipv6 pcmcia tsdev ohci_hcd parport_pc parport
> > floppy psmouse rtc pcspkr yenta_socket rsrc_nonstatic pcmcia_core tg3
> > snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd soundcore
> > snd_page_alloc i2c_i801 i2c_core piix shpchp pci_hotplug ehci_hcd
> > uhci_hcd intelfb intel_agp agpgart evdev usbcore aes_i586 dm_crypt
> > ath_pci ath_rate_sample
> > ath_rate_onoe ath_rate_amrr wlan_xauth wlan_wep wlan_tkip wlan_ccmp
> > wlan_acl wlan ath_hal ibm_acpi thermal processor fan button battery ac
> > loop dm_mod ide_cd cdrom nls_utf8 nls_base
> > CPU:    0
> > EIP:    0060:[<f01436a0>]    Tainted: P      VLI
> > EFLAGS: 00010246   (2.6.12-suspend2-r4)
> > EIP is at ath_rate_ctl_reset+0xd0/0x470 [ath_rate_sample]
> > eax: 00000000   ebx: ee300800   ecx: ec62c000   edx: 00000000
> > esi: 70007972   edi: 00000000   ebp: ee300800   esp: ed8e5cc8
> > ds: 007b   es: 007b   ss: 0068
> > Process pccardd (pid: 6197, threadinfo=ed8e4000 task=ef3db020)
> > Stack: c034e946 ed8e5d10 00000046 ef22ca40 c042ff10 000f4bd1 ef22ca40
> > ef22ca40 4145c780 000f4bd1 000d9038 4145c780 000f4bd1 ef22ca40 ee3009fc
> > ec62c620 ec62c000 ee300800 f01a1490 ee300ff8 ec62c000 f01a242b ec62c000
> > ee300800 Call Trace:
> >  [<c034e946>] schedule+0x336/0x620
> >  [<f01a1490>] ath_key_update_begin+0x0/0x70 [ath_pci]
> >  [<f01a242b>] ath_node_alloc+0x9b/0xc0 [ath_pci]
> >  [<f01a1490>] ath_key_update_begin+0x0/0x70 [ath_pci]
> >  [<f0189f93>] ieee80211_node_lateattach+0x13/0xe0 [wlan]
> >  [<f01a1490>] ath_key_update_begin+0x0/0x70 [ath_pci]
> >  [<f0183a9f>] ieee80211_media_init+0x1f/0x4a0 [wlan]
> >  [<f01a198c>] ath_setslottime+0x2c/0x50 [ath_pci]
> >  [<f018453f>] ieee80211_watchdog+0x5f/0x90 [wlan]
> >  [<f0183699>] ieee80211_ifattach+0x159/0x2e0 [wlan]
> >  [<f01a1500>] ath_key_update_end+0x0/0x70 [ath_pci]
> >  [<f01a1490>] ath_key_update_begin+0x0/0x70 [ath_pci]
> >  [<f0189f93>] ieee80211_node_lateattach+0x13/0xe0 [wlan]
> >  [<f01a1490>] ath_key_update_begin+0x0/0x70 [ath_pci]
> >  [<f0183a9f>] ieee80211_media_init+0x1f/0x4a0 [wlan]
> >  [<f01a198c>] ath_setslottime+0x2c/0x50 [ath_pci]
> >  [<f018453f>] ieee80211_watchdog+0x5f/0x90 [wlan]
> >  [<f0183699>] ieee80211_ifattach+0x159/0x2e0 [wlan]
> >  [<f01a1500>] ath_key_update_end+0x0/0x70 [ath_pci]
> >  [<f01a1490>] ath_key_update_begin+0x0/0x70 [ath_pci]
> >  [<f019f889>] ath_attach+0x889/0xb00 [ath_pci]
> >  [<f01a0b40>] ath_media_change+0x0/0x40 [ath_pci]
> >  [<f0184360>] ieee80211_media_status+0x0/0x180 [wlan]
> >  [<f01a6656>] ath_pci_probe+0x226/0x3e0 [ath_pci]
> >  [<c025b162>] pci_device_probe_static+0x52/0x70
> >  [<c025b1bc>] __pci_device_probe+0x3c/0x50
> >  [<c025b1fc>] pci_device_probe+0x2c/0x50
> >
> > if I try to connect I get:
> >
> >  # /etc/init.d/net.ath0 start
> >   * Starting ath0
> >   *   Bringing up ath0
> >   *     Configuration not set for ath0 - assuming dhcp
> >   *     dhcp
> >   *       ath0 does not exist
> >
> > in some cases I just get: failed to connect.
> > Checking a bit more, ath0 doesn't exist, and I can't even see it on
> > lspci.
> >
> > When I unplug it, I get a kernel panic.
> >
> > I am loading the modules:
> > ath_hal
> > wlan
> > wlan_acl
> > wlan_ccmp
> > wlan_tkip
> > wlan_wep
> > wlan_xauth
> > ath_rate_amrr
> > ath_rate_onoe
> > ath_pci
> > at boot thru /etc/modules.autoload.d/kernel-2.6.
> >
> > Any ideas what is going on ? Am I doing something wrong ?
> >
> > Thank you.
>
> Which updates are you talking about-
madwifi, it was updated some days ago, to be exact, version 0.1_pre20050809 
released on 2005/08/10 12:44:19, while previously I was using 
0.1_pre20050420.

> did you change kernels? Maybe you need
> to reemerge all the wifi and dhcpcd stuff.
No, I didn't change kernel (I am familiar with externas modules).


> I have a D-link Atheros based card, and here's what I do:
>
> 1. compile into the kernel all support items for wifi (not modules)
>
> 2. emerge all madwifi stuff (tools, driver), and dhcpcd
>
> 3. As root, type
>
> iwconfig ath0
>
> This brings up the config list, but no essid, and the address is all zeros.
>
> then I type
>
>  dhcpcd ath0
>
> and it connects fine.
>
> If I redo the iwconfig ath0 command, it now lists the essid name of my
> wireless router (linksys), and the numerical isp address dhcpcd found.
This is more or less what I used to do with the old driver that didn't cause 
kernel panics.

Thank you.
-- 
Pupeno <pupeno@××××××.com> (http://pupeno.com)
Reading ? Science Fiction ? http://sfreaders.com.ar