On Wed, 2010-10-06 at 08:47 -0400, Ward, David - 0663 - MITLL wrote: > Inaky, > > On 10/05/2010 07:58 PM, Inaky Perez-Gonzalez wrote: > > > > On Sun, 2010-10-03 at 19:34 -0400, Ward, David - 0663 - MITLL wrote: > > > > > I have a Dell Latitude E6500 that came with an Intel WiMAX/WiFi Link > > > > > 5150. Under Windows 7 x64, I am able to connect to CLEAR Boston > > > > > without any issue. However I have not been able to connect at all > > > > > under Linux yet. I am using the latest versions of the i2400m > > driver, > > > > > firmware, and the userspace components (obtained from git). > > > > > > > > > > I first tried to get this working with RHEL 6 x86_64 (which we > > will use > > > > > at work); this involved patching its kernel > > 2.6.32-44.2.el6.x86_64 to > > > > > update the i2400m driver to version 1.5. However each time I > > tried to > > > > > connect, wimaxcu returned "Connection failure". Now I am trying to > > > > > even get this working under Fedora 14-Alpha i686, which is > > 32-bit and > > > > > already comes with kernel 2.6.35.4-28.fc14.i686.PAE -- but I am > > having > > > > > the same issue. > > > > > > > > > > Below I am including information that I hope is relevant to > > identifying > > > > > the problem. I increased the debug output per website FAQ 6.4. > > > > > Please let me know what additional information I can provide. > > Thanks > > > > > in advance for your help. > > > > Sorry for the very late reply, I've been kinda overloaded. > > > > No worries :) I really do appreciate your help with this. > > > I dug on your logfiles, but unfortunately it is quite difficult to tell > > what's going on. That user space daemon is a pain, let me tell you... > > > > Let's try this: > > > > in a terminal, run as root > > > > $ wimaxd -i wmx0 -d # keeps it in the foregrounf > > > > on another one, as root: > > > > $ wimaxcu scan > > $ wimaxcu connect network X > > > > and let's see what is printed on the daemon's output > > > > I am wondering if the thing gets to the WiMAX authentication part or > > not. > > > > > I'm guessing the answer is no -- here is the output. Nope, it doesn't. This is version 1.5, right? Can you try 1.5.1? This is annoying. Your scan results reported strong links, so we can discard that. Something else I'd like to try (it happens to me sometimes): make sure autoscan and autoconnect are disabled: $ wimaxcu wimaxcu-wpa_cd connectmode connect manual scan semi and then issue a wimax scan plus the wimax connect network. When it times out, try to connect again. I've been at the point a few times where it just took to long for it to connect. Also, in another terminal, run a few 'wimaxcu status', let's see what that reports.
