[prev in list] [next in list] [prev in thread] [next in thread]
List: wimax
Subject: Re: Unable to connect to CLEAR Boston under Fedora 14-Alpha i686
From: Inaky Perez-Gonzalez <inaky () linux ! intel ! com>
Date: 2010-10-18 17:15:20
Message-ID: 1287422120.14063.2.camel () localhost ! localdomain
[Download RAW message or body]
Hi Guys
On Mon, 2010-10-18 at 11:16 -0400, Ward, David - 0663 - MITLL wrote:
> Is anyone successfully using the latest Linux WiMAX driver and
> userspace code with an Intel WiMAX/WiFi Link 5150? Under what operating
> system?
>
> Is the problem that Aaron Gutman is having (see "WiMAX difficulties", 14
> October 2010) the same as mine? We have the same kernel, same WiMAX
> adapter, and same result when trying to connect.
>
> I would really appreciate further help with this.
I am really sorry, but I've been swamped and haven't been able to look
further into this.
I use WiMAX daily with FC13/32-bit and v1.5.1 on a 5350.
I finally got a hold of a 5150 and as soon as I have some time, I'll
slip it in a laptop and give it a try, see if I can reproduce the issue.
> Thanks,
>
> David
>
>
> -------- Original Message --------
>
> Hi Inaky,
>
> > > > > > > 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 firmware, driver,
> > > > > > > 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.
> > > > > > >
> > > > I am wondering if the thing gets to the WiMAX authentication part
> > > > or not.
> > > >
> > Nope, it doesn't.
> >
> > This is version 1.5, right? Can you try 1.5.1?
>
> I just updated libeap to 0.7.2, and wimax-tools and
> wimax-network-service to the latest version from git.
>
> > 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.
>
> This is the output of wimaxcu when trying to connect -- nothing has
> changed:
>
> $ wimaxcu ron
> HW and SW Radios are ON.
> $ wimaxcu connectmode connect manual scan semi
> The specified connect mode is already in place.
> Connection and Scan Mode:
> Connection: manual
> Scan: semi-manual
> $ wimaxcu scan
>
> Network found.
> NSP : CLEAR
> ID : 2
> Signal : Excellent
> RSSI : -48 dBm
> CINR : 32 dB
> Network Type: Home Network
> Activated
>
> Network found.
> NSP : SPRINT
> ID : 47
> Signal : Excellent
> RSSI : -48 dBm
> CINR : 32 dB
> Network Type: Home Network
> Activated
>
> Network found.
> NSP : Comcast
> ID : 48
> Signal : Excellent
> RSSI : -48 dBm
> CINR : 32 dB
> Network Type: Home Network
> Activated
>
> Network found.
> NSP : Time Warner Cable 4G
> ID : 51
> Signal : Excellent
> RSSI : -48 dBm
> CINR : 32 dB
> Network Type: Home Network
> Activated
> $ wimaxcu connect network 2
> Connecting to CLEAR Network...
> Connection failure
> $ wimaxcu connect network 2
> Connecting to CLEAR Network...
> Connection failure
> $ wimaxcu connect network 2
> Connecting to CLEAR Network...
> Connection failure
>
>
>
> This is the output of wimaxd -- after the upgrade, it no longer shows
> even the few messages that it did before:
>
> # wimaxd -i wmx0 -d
> Enter Command:
> q - Quit AppSrv
> t - Trace ReInit (ReLoads Registry Values)
> u - uplink(Apdo uplink event
> h - Help
> d - Toggle driver messages to display - debug& internal only
>
>
> AppSrv is ready !
> Act_FullRestart!
> Act_DriverDeviceStatus - DRIVER_UP
>
>
>
> I did run 'wimaxcu status' repeatedly during this process. The output
> normally cycles between "Scanning..." and "Ready." When trying to
> connect, the output is "Connecting...", then when it fails, it goes
> back to "Scanning...".
>
> Thanks again for your help,
>
> David
>
>
>
>
_______________________________________________
wimax mailing list
wimax@linuxwimax.org
http://lists.linuxwimax.org/listinfo/wimax
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic