[ltp] Re: iwl4965, Hardy x86_64, and frustration (long)

John Jason Jordan linux-thinkpad@linux-thinkpad.org
Tue, 13 May 2008 08:39:52 -0700


On Fri, 09 May 2008 23:40:42 -0400
Shannon McMackin <smcmackin@gmail.com> dijo:

> John Jason Jordan wrote:
> > On Thu, 08 May 2008 20:02:40 +0200
> > Peter Frühberger <peter.fruehberger@gmail.com> dijo:
> > 
> >> modinfo iwl4965 
> >>
> >> you can build wireless compat (mentioned somewhere here on the list)
> > 
> > Thanks for the modinfo command. Worked great. Turns out I have version
> > 1.2.25. 
> > 
> > I can't find the reference on the list for what is the latest version.
> > I went to Lenovo:
> > 
> > http://tinyurl.com/65dbx5
> > 
> > And they don't list any wireless drivers. I'm sure it's somewhere on
> > Lenovo's site, I just can't find it.
> I would never go to Lenovo for a linux driver unless you're running SLED10.
> 
> For the Intel, go to the Intel wireless site and get the compat-wireless 
> package.  The one I have is from 5/3/08 and is 1.2.26kd.  I've been 
> taking this approach for over a month and it's been stable.
> 
> The Ubuntu backports package should also be sufficient now as well...

I should have posted an update. After upgrading to Hardy the LED was
not on (nor was it before), and I discovered that I was still getting
random disconnects. However, my problem is that I do not have any way
to test wireless at home because my home is wired for ethernet -
everything is gigabit capable, including cat6 wiring. I have to wait
until I go to the university or someplace to test the wireless. And the
next day after the upgrade to Hardy I went to the university and found
that I was disconnected after an hour or so. That's when I started this
thread.

I should also add that the problem was not really a disconnect but,
rather, losing my DHCP lease. In fact, all the GUI tools and the
command line would say I was connected and display the IP address, yet
I could not go anywhere. I am not an expert with Linux so I was not
aware that I could restore it easily from the command line with "sudo
dhclient wlan0."

Since then I have added the headers and now the LED lights up. I have
also had several instances where I have gone to the university and
stayed connected for several hours. Other than that one time I have had
no further problems with losing the DHCP lease.

I am keeping my fingers crossed and I am still carrying around a
borrowed Netgear card for just in case. But it appears that whatever
the problem was has been resolved.