#778: upgrading madwifi, ubuntu breaks wireless on thinkpad
---------------------------------------+------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: other | Version: trunk
Resolution: | Keywords: ubuntu, thinkpad,
regression
Patch_attached: 0 |
---------------------------------------+------------------------------------
Comment (by [EMAIL PROTECTED]):
This is a Thinkpad Z60t running Ubuntu; typical travel laptop seeing
many access points at hotels, conferences, etc. /etc/network/interfaces
has ``iface ath0 inet dhcp'' and ``pre-up ifconfig ath0 up'' and,
depending on location, typically a few wireless-* lines. What I expect
``ifup ath0'' to do is to run dhclient and obtain an IP address via DHCP
within a few tries.
Ubuntu ships an old madwifi having the known ``ath_attach: unable to
attach hardware: 'Hardware didn't respond as expected' (HAL status 3)''
bug, preventing ath0 from working at all. So, whenever Ubuntu upgrades
the kernel, I remove Ubuntu's old madwifi and install a recent version
of madwifi.
If I boot with a very recent madwifi (svn r1687) under the latest kernel
shipped by Ubuntu, wireless is a disaster: ``ifup ath0'' practically
always fails to obtain an IP address. I've tried this on several access
points at several locations and it's consistently a disaster.
If I boot with an older madwifi (svn 1518) under an older kernel,
wireless works exactly as I expect. There's none of the disastrous
behavior; sure, I'll occasionally have trouble connecting to an access
point several rooms away, but a reasonably strong signal always works.
Obviously there's nothing wrong with the access points, nothing wrong
with the laptop hardware, and nothing wrong with the overall setup.
It's crystal clear that there's a bug in the newer software.
http ://cr.yp.to/unix/madwifi/madwifi-failing and
http ://cr.yp.to/unix/madwifi/madwifi-working are two examples of
athdebug +xmit output. Same access point, same laptop location, but I
have an IP address with the older software and not with the newer
software. I consistently obtain failures by booting with the newer
madwifi and the newer kernel, and I consistently obtain successes by
booting with the older madwifi and the older kernel.
--
Ticket URL: <http://madwifi.org/ticket/778>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
