Thanks for the reply. I have a lot to digest here. I'm not as comfortable in this territory as others.
I did do the usual ldmod's etc and establish that what I expected (HAL, etc) was loading. If I'm reading you right, the ones I have may be out of date and/or broken. So I should either update or roll back. I don't mind leaving the safety of rpm's but I am not sure where to go for source tar balls or which to get. Perhaps if you or someone out there has madwifi working with any kernel, you can give me the specs on your stuff and I could try making my machine comply. You already indicated that my kernel might need upgrading. On Thu, Feb 16, 2006 at 11:27:30PM -0800, DJA wrote: > Lan Barnes wrote: > >I've just emerged from email hell starting with Neil's RAID collapse > >(Neil, I feel your pain), proceeding through a bloody upgrade of my > >primary server linus FC3 -> FC4 (a reinstall with repartitioning, > >actually, but no data loss thanks to good planning and back-ups), and an > >IP address change by those Cox suckers. > > > >So I'm back, and I have this problem. My FC4 Toshiba laptop now refuses > >to find its wireless PCIMIA card. > > > >Here's the short version. While in FC3, the Toshiba connected with the > >atheros (madwifi) driver, although giving an "error 3 -- unable to > >reset" error when I brought ath0 up. I figured it was a slight > >incompatibility in the module/kernel compiles, and shined it on because, > >heck, it worked. All of this was with Airlink garbage -- card, router, > >etc. > > Following several dev mailing lists so that I can keep my laptop up to > day provided this recent exchange (on the NetworkManager list: > [email protected] > http://mail.gnome.org/mailman/listinfo/networkmanager-list): > > ****************** > On Thu, 2006-02-16 at 10:23 -0500, Darren Albers wrote: > > > >> That brings up a question, should those of us who use Atheros chipset > >> cards use the old Madwifi drivers or Madwifi-ng? > > > madwifi-ng is definitely a lot better than madwifi, but madwifi-ng from > the SVN repository has been broken in odd ways over the last two weeks > or so. > > Robert Love > > ****************** > > On Thu, 2006-02-16 at 11:27 -0500, Dan Williams wrote: > > >> Is there a specific date that has a "known good" SVN pull for madwifi-ng > >> for interacting with wpa_supplicant and NetworkManager? > > > There is -- in that I used to use madwifi-ng with a lot less problems -- > but I don't remember when everything started failing. It was recent. > Just a few weeks ago. > > What problems are you seeing (I am still trying to track down what is > madwifi-ng-related)? Recently, I have problems associating with > _certain_ access points. The criteria seems weird. Maybe 802.11b? I > have a broadcasting, non-encrypted network that stopped working. But a > WPA2 network works fine. > > Robert Love > > ****************** > > > >OK, after I did a reinstall of FC4 on the laptop, complete with all > >errata and updates from RH, the Airlink card just flat refused to work. > >I took it to the InstallFest where Gus gave me a clinic on diagnosis, > >but I was pressed for time and couldn't stay too long. The log messages > >when we plugged in the card said that it was unable to reset and quit. > > > >I decided that it was probably Airlink inadequacies, and bought a D-Link > >PCMCIA wireless card and a D-Link router, both of which were listed as > >madwifi slam-dunks in a copy of an article on Linux wireless. > > > >The D-Link router is now replacing the Airlink router (which in all > >fairness, never seemed to give me any trouble), but the new D-Link > >laptop card is crapping out exactly like the Airlink. > > > >Here is the dingbat from /var/log/messages when I plug the new card in: > > > > > >Feb 12 23:10:38 gypsy kernel: ath_hal: no version for "struct_module" > >found: kernel tainted. > >Feb 12 23:10:38 gypsy kernel: ath_hal: module license 'Proprietary' taints > >kernel. > >Feb 12 23:10:38 gypsy kernel: ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, > >RF5111, RF5112, RF2413) > >Feb 12 23:10:39 gypsy kernel: wlan: 0.8.6.0 (EXPERIMENTAL) > >Feb 12 23:10:39 gypsy kernel: ath_rate_sample: 1.2 > >Feb 12 23:10:39 gypsy kernel: ath_pci: 0.9.6.0 (EXPERIMENTAL) > >Feb 12 23:10:39 gypsy kernel: PCI: Enabling device 0000:02:00.0 (0000 -> > >0002) > >Feb 12 23:10:39 gypsy kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> Link > >[LNKC] -> GSI 11 (level, low) -> IRQ 11 > >Feb 12 23:10:39 gypsy kernel: ath_attach: unable to attach hardware: > >'Hardware didn't respond as expected' (HAL status 3) > >Feb 12 23:10:39 gypsy kernel: ACPI: PCI interrupt for device 0000:02:00.0 > >disabled > > > >I've tried this with the madwifi rpm's for FC4 and also with my own > >compile of the latest cvs snapshot. Neither seems to work. > > > >Here are the present versions of kernel/madwifi: > > > >[EMAIL PROTECTED] ~]$ got madwifi > >madwifi-kmdl-2.6.14-1.1656_FC4-0.9.6.0-18.rhfc4.at > >[EMAIL PROTECTED] ~]$ uname -a > >Linux gypsy 2.6.14-1.1656_FC4 #1 Thu Jan 5 22:13:22 EST 2006 i686 i686 > >i386 GNU/Linux > > > >I'd be grateful for any insight on what I might be doing wrong. > > > >TIA, > > Are your wireless driver, HAL, DBUS, Wireless Tools, and ACPI all up to > date and working okay? If not, you may have to get later versions of > some of these from their maintainers (and don't expect RPM's). > > I've had similar problems with my laptop after a kernel update. I expect > I'll need to update both the wireless driver and firmware along with the > latest stable wireless tools (wireless extensions) now since the latest > release (in fact there were two kernel updates less than a week apart). > > BTW, the FC4 kernel is currently at > > [EMAIL PROTECTED] ~]# uname -r > 2.6.15-1.1831_FC4 > > > For what it's worth, my thoughts on keeping your laptop running the way > you want, is not to mess with it unless it's really necessary. Then be > prepared to do a fair amount of research, tweaking, and even compiling > (including, probably the kernel). > > -- > Best Regards, > ~DJA. > > > -- > [email protected] > http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list -- Lan Barnes [EMAIL PROTECTED] Linux Guy, SCM Specialist 858-354-0616 Tcl/Tk Enthusiast -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
