[NTLUG:Discuss] AnyideahowtogetaSprintEVDOwirelessbroadbandcard to
. Daniel
xdesign at hotmail.com
Thu Jul 27 08:15:33 CDT 2006
Yeah, I'll be happy to tell my tale. Part of it is on this very list. I
was confused about a great many aspects of getting the thing running. I'll
try to write it up as a how-to, but mostly, it'll be a "how I did." Your
configuration seems to be lacking the most crucial part of the thing --
recognition by the machine/OS.
I will try to write this up today some time while I'm at the office. But
the quick answer the latter:
I use Fedora Core 5. I used instructions intended for Ubuntu. (I posted
the link on a previous comment somewhere back there.) I got some good help
from this very list on how to trouble-shoot and all that, but it all
started with the device working and being recognized.
After having not thought about your problem for some time, I have a little
more perspective on the problem. You say it works under Windows. Is that
Windows on the SAME machine? I hope it is... it would serve to help
eliminate hardware as the problem. If it's not, we might want to spend a
little time investigating to see if the host hardware isn't the problem.
My device shows up as /dev/ttyUSB0. I have read other sites claiming that
it appears as /dev/ttyACM0. The previous "Merlin" card did that... I have
one of those too. I never attempted to make it "work" under Linux. I just
stuck it in my laptop to see what Linux would report it as being. The same
goes for this Sprint EVDO card... I just stuck it in to see what Linux
would report. It reported /dev/ttyUSB0.
Your diagnotics aren't even getting you that far, I'm afraid. I'm hesitant
to suggest changing distros as I'm still having a hard time wrapping my
mind around the idea that the "specialness" of a distro's custom kernel
would enable or disable the use of various hardware. I have never
personally witnessed that problem, though I can say that I'm impressed with
the way Knoppix IDs and sets up hardware. (That's why I suggested trying
to boot from Knoppix to see what the OS reports about your hardware.)
I can't really write a "how to" on detecting hardware. But here's the
short-answer of what I did:
1. Insert PCMCIA card.
2. Check the "dmesg | tail" to see what device came up.
3. ...start setting up the ppp connection settings...
All the stuff I did in step 3 is worth writing about. I didn't have any
problems in steps 1 and 2 though... and as far as I can tell, that's where
you're stuck. BTW, do you have any other PCMCIA devices that work? Do
they work in that machine under Linux?
>Daniel , can you do a how to as to how you accomplished the task here ?
>And what distro you have done this with ?
>
>On 7/26/06, . Daniel <xdesign at hotmail.com> wrote:
> >
> > Almost didn't see the reference to the web site.
> >
> > Interestingly, the site links to a WORD DOCUMENT describing how to do
> > Linux. Maybe I'll do them the favor of saving it out as a PDF...
> >
> > ...or not.
> >
> > >http://wireless-internet-broadband-service.com/
> > >Driver and how to .
> > >On 7/25/06, David Trusty <dwtrusty at hotmail.com> wrote:
> > > >
> > > > I tried doing the modprobe ochi. It said "fatal: no such module".
> > > >
> > > > David
> > > >
> > > >
> > > > >From: "Gilbert Morrow" <gkfmorrow at gmail.com>
> > > > >Reply-To: NTLUG Discussion List <Discuss at ntlug.org>
> > > > >To: "NTLUG Discussion List" <Discuss at ntlug.org>
> > > > >Subject: Re: [NTLUG:Discuss] Any idea
> > > > >howtogetaSprintEVDOwirelessbroadbandcard to
> > > > >Date: Fri, 21 Jul 2006 17:30:51 -0500
> > > > >
> > > > > >From what I have read through some forums , the Sprint Ev-do is
not
> > > > just
> > > > >plug and play , it is however a modem as Daniel described , PCMCIA
> > but
> > > > acts
> > > > >as a USB device , what I saw was that the kernel needed OCHI
> > (modprobe
> > > > >ochi)
> > > > >module to work the USB part of the card . The how-to was very long
> > and
> > > > >required several steps , so no plug and play here .
> > > > >
> > > > >On 7/21/06, David Trusty <dwtrusty at hotmail.com> wrote:
> > > > > >
> > > > > > Yes, i did activate it. In winders it works fine.
> > > > > >
> > > > > > David
> > > > > >
> > > > > >
> > > > > >
> > > > > > >From: "Gilbert Morrow" <gkfmorrow at gmail.com>
> > > > > > >Reply-To: NTLUG Discussion List <Discuss at ntlug.org>
> > > > > > >To: "NTLUG Discussion List" <Discuss at ntlug.org>
> > > > > > >Subject: Re: [NTLUG:Discuss] Any idea how
> > > > > > >togetaSprintEVDOwirelessbroadbandcard to
> > > > > > >Date: Fri, 21 Jul 2006 15:00:39 -0500
> > > > > > >
> > > > > > >One highly relevant question is , did you activate the card
> > through
> > > > > > winders
> > > > > > >first ? , read that that is a must .
> > > > > > >
> > > > > > >On 7/21/06, David Trusty <dwtrusty at hotmail.com> wrote:
> > > > > > > >
> > > > > > > > Regular usb devices (I use Kingston memory stick) work
fine.
> > > > > > > > When I plug in the Kingston, the system recognizes it just
> > fine,
> > > > > > > > but even in this case there is nothing in
> > /proc/bus/usb/devices
> > > > (no
> > > > > > such
> > > > > > > > file or directory).
> > > > > > > >
> > > > > > > > The kernel I use is the standard SUSE 10.1 kernel (Linux
linux
> > > > > > > > 2.6.16.13-4-default). I know some things changed in the
2.6
> > > > >kernels,
> > > > > > > > that is what was referring to when I mentioned the kernel
> > > > >previously.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > >From: ". Daniel" <xdesign at hotmail.com>
> > > > > > > > >Reply-To: NTLUG Discussion List <Discuss at ntlug.org>
> > > > > > > > >To: Discuss at ntlug.org
> > > > > > > > >Subject: Re: [NTLUG:Discuss] Any idea how to
> > > > > > > > >getaSprintEVDOwirelessbroadbandcard to
> > > > > > > > >Date: Fri, 21 Jul 2006 06:32:21 -0500
> > > > > > > > >
> > > > > > > > >That may be one of the best clues so far. You have no
> > > > > > > > >/proc/bus/usb/devices?
> > > > > > > > >
> > > > > > > > >Do you have any other USB devices that corrently work on
this
> > > > > > computer?
> > > > > > > > >
> > > > > > > > >And what do you mean "In this kernel"? Do you suspect it
is
> > > > >compiled
> > > > > > > > >differently? That maybe it left out things pertaining to
> > USB?
> > > > > > > > >
> > > > > > > > >Someone misintepreted what I said about NDIS wrapper.
Let's
> > get
> > > > an
> > > > > > > > >understanding straight from the horses's mouth:
> > > > >http://www.ndis.com/
> > > > > > > > >
> > > > > > > > >---stat from the site---
> > > > > > > > >What is "NDIS"?
> > > > > > > > >
> > > > > > > > >NDIS is short for the "Network Driver Interface
> > Specification".
> > > > The
> > > > > > > > primary
> > > > > > > > >purpose of NDIS is to define a standard API for "Network
> > > > Interface
> > > > > > >Cards"
> > > > > > > > >(NIC's). The details of a NIC's hardware implementation is
> > > > wrapped
> > > > >by
> > > > > > a
> > > > > > > > >"Media Access Controller" (MAC) device driver in such a
way
> > that
> > > > >all
> > > > > > > > NIC's
> > > > > > > > >for the same media (e.g., Ethernet) can be accessed using
a
> > > > common
> > > > > > > > >programming interface.
> > > > > > > > >
> > > > > > > > >NDIS also provides a library of functions (sometimes
called a
> > > > > > >"wrapper")
> > > > > > > > >that can be used by MAC drivers as well as higher level
> > protocol
> > > > > > >drivers
> > > > > > > > >(such as TCP/IP). The wrapper functions serve to make
> > development
> > > > >of
> > > > > > >both
> > > > > > > > >MAC and protocol drivers easier as well as to hide (to
some
> > > > extent)
> > > > > > > > >platform dependencies.
> > > > > > > > >
> > > > > > > > >Early versions of NDIS were jointly developed by Microsoft
> > and
> > > > the
> > > > > > 3Com
> > > > > > > > >Corporation. Current NDIS versions used by Windows For
> > Workgroups
> > > > > > >(WFW),
> > > > > > > > >Windows 9X Windows NT, Windows 2000, Windows XP and
Windows
> > > > Server
> > > > > > 2003
> > > > > > > > are
> > > > > > > > >Microsoft proprietary specifications.
> > > > > > > > >--end from the site---
> > > > > > > > >
> > > > > > > > >So you see, since the EVDO is a "serial" device or modem,
> > NDIS
> > > > > > wrapper
> > > > > > > > does
> > > > > > > > >not apply. USB is a bus architecture and can access a
> > variety
> > of
> > > > > > types
> > > > > > > > of
> > > > > > > > >devices. There are USB ethernet devices and yes, if the
EVDO
> > > > >device
> > > > > > >were
> > > > > > > > >somehow an ethernet device, then it might apply. But for
the
> > > > >moment,
> > > > > > > > he's
> > > > > > > > >trying to get into Sprint's (actually Verizon's) wireless
> > network
> > > > >via
> > > > > > >the
> > > > > > > > >modem.
> > > > > > > > >
> > > > > > > > >I have the EXACT same device. It works for me. Every
> > computer I
> > > > > > have
> > > > > > > > ever
> > > > > > > > >used it with sees it as two USB serial devices, the first
of
> > > > which
> > > > >is
> > > > > > >the
> > > > > > > > >"modem" that responds to the "AT" command set. (ATDT#777
> > connects
> > > > >you
> > > > > > >to
> > > > > > > > >the network) The other device, frankly, is an unexplored
> > mystery
> > > > >to
> > > > > > > > me...
> > > > > > > > >never bothered to investigate what it is. (Could it
somehow
> > be a
> > > > > > > > >USB-serial device with access to 802.11 wireless networks?
> > I'd
> > > > be
> > > > >a
> > > > > > >bit
> > > > > > > > >surprised.)
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >Here is what I am seeing:
> > > > > > > > > >
> > > > > > > > > ># cat /proc/bus/usb/devices
> > > > > > > > > >cat: /proc/bus/usb/devices: No such file or directory
> > > > > > > > > >
> > > > > > > > > >In this kernel, it appears that the devices are shown
here:
> > > > > > > > > >
> > > > > > > > > ># ls -laF /sys/bus/usb/devices
> > > > > > > > > >total 0
> > > > > > > > > >drwxr-xr-x 2 root root 0 Jul 20 17:56 ./
> > > > > > > > > >drwxr-xr-x 4 root root 0 Jul 20 12:56 ../
> > > > > > > > > >lrwxrwxrwx 1 root root 0 Jul 20 17:56 1-0:1.0 ->
> > > > > > > > > >../../../devices/pci0000:00/0000:00:1d.7/usb1/1-0:1.0/
> > > > > > > > > >lrwxrwxrwx 1 root root 0 Jul 20 17:56 2-0:1.0 ->
> > > > > > > > > >../../../devices/pci0000:00/0000:00:1d.0/usb2/2-0:1.0/
> > > > > > > > > >lrwxrwxrwx 1 root root 0 Jul 20 17:56 2-2 ->
> > > > > > > > > >../../../devices/pci0000:00/0000:00:1d.0/usb2/2-2/
> > > > > > > > > >lrwxrwxrwx 1 root root 0 Jul 20 17:56 2-2:1.0 ->
> > > > > > > > >
>../../../devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/
> > > > > > > > > >lrwxrwxrwx 1 root root 0 Jul 20 17:56 usb1 ->
> > > > > > > > > >../../../devices/pci0000:00/0000:00:1d.7/usb1/
> > > > > > > > > >lrwxrwxrwx 1 root root 0 Jul 20 17:56 usb2 ->
> > > > > > > > > >../../../devices/pci0000:00/0000:00:1d.0/usb2/
> > > > > > > > > >
> > > > > > > > > >I have not been able to find any difference in the usb
> > devices
> > > > > > under
> > > > > > > > /sys
> > > > > > > > > >before/after
> > > > > > > > > >the card is inserted.
> > > > > > > > > >
> > > > > > > > > >Also, usbview complains because there is nothing in
> > > > > > > > >/proc/bus/usb/devices.
> > > > > > > > > >
> > > > > > > > > >Any ideas?
> > > > > > > > > >
> > > > > > > > > >Thanks!!
> > > > > > > > > >
> > > > > > > > > >David
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >From: Rick Cook <rickcook at sbcglobal.net>
> > > > > > > > > > >Reply-To: NTLUG Discussion List <Discuss at ntlug.org>
> > > > > > > > > > >To: NTLUG Discussion List <Discuss at ntlug.org>
> > > > > > > > > > >Subject: Re: [NTLUG:Discuss] Any idea how to get
> > > > > > > > > > >aSprintEVDOwirelessbroadband card to
> > > > > > > > > > >Date: Thu, 20 Jul 2006 21:19:53 -0500
> > > > > > > > > > >
> > > > > > > > > > >On Thursday 20 July 2006 20:14, . Daniel wrote:
> > > > > > > > > > > > NDIS wrapper is for ethernet hardware. I couldn't
> > imagine
> > > > > > NDIS
> > > > > > > > >wrapper
> > > > > > > > > > > > helping out on such a device. The network
connection
> > is
> > > > via
> > > > > > >pppd
> > > > > > > > >after
> > > > > > > > > > > > all.
> > > > > > > > > > > >
> > > > > > > > > > > > The device drivers' filenames seem to indicate that
> > the
> > > > >device
> > > > > > >is
> > > > > > > > a
> > > > > > > > >USB
> > > > > > > > > > > > device.
> > > > > > > > > > > >
> > > > > > > > > > > > Does "usbview" indicate anything present?
> > > > > > > > > > > >
> > > > > > > > > > > > >I tried using ndiswrapper. It did not work. I
found
> > two
> > > > > > .inf
> > > > > > > > >files
> > > > > > > > > > > > >from WinXp install CD: nwusbmdm.inf nwusbser.inf.
> > > > > > > > > > > > >The ndiswrapper command ran without errors, but
did
> > not
> > > > >show
> > > > > > > > > > > > >"hardware present".
> > > > > > > > > > > > >
> > > > > > > > > > > > >Also, when I insert the card, it does not cause
any
> > new
> > > > > > entries
> > > > > > > > in
> > > > > > > > > > > > >the "lspci" output. However, I still get the
kernel
> > > > >message:
> > > > > > > > > > > > > pccard: CardBus card inserted into slot 0
> > > > > > > > > > > > >
> > > > > > > > > > > > >Any ideas?
> > > > > > > > > > > > >
> > > > > > > > > > > > >Thanks!!
> > > > > > > > > > > > >
> > > > > > > > > > > > >David
> > > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >Something I read indicates that what you have is
probably
> > > > >treated
> > > > > > >as
> > > > > > > > a
> > > > > > > > >USB
> > > > > > > > > > >serial modem. You might find some pointers at =>
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
> >
http://enterprise.linux.com/enterprise/06/03/08/2138237.shtml?tid=20&tid=100
> >
> > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >Note that the "cat' command appears to be missing a
> > redirect.
> > > > > > Try:
> > > > > > > > > > >
> > > > > > > > > > >cat /proc/bus/usb/devices > devices
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >Good luck,
> > > > > > > > > > >
> > > > > > > > > > >Rick
> > > > > > > > > > >
> > > > > > > > > > >_______________________________________________
> > > > > > > > > > >http://ntlug.pmichaud.com/mailman/listinfo/discuss
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >_______________________________________________
> > > > > > > > > >http://ntlug.pmichaud.com/mailman/listinfo/discuss
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >_______________________________________________
> > > > > > > > >http://ntlug.pmichaud.com/mailman/listinfo/discuss
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > http://ntlug.pmichaud.com/mailman/listinfo/discuss
> > > > > > > >
> > > > > > >_______________________________________________
> > > > > > >http://ntlug.pmichaud.com/mailman/listinfo/discuss
> > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > http://ntlug.pmichaud.com/mailman/listinfo/discuss
> > > > > >
> > > > >_______________________________________________
> > > > >http://ntlug.pmichaud.com/mailman/listinfo/discuss
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > http://ntlug.pmichaud.com/mailman/listinfo/discuss
> > > >
> > >_______________________________________________
> > >http://ntlug.pmichaud.com/mailman/listinfo/discuss
> >
> >
> >
> > _______________________________________________
> > http://ntlug.pmichaud.com/mailman/listinfo/discuss
> >
>_______________________________________________
>http://ntlug.pmichaud.com/mailman/listinfo/discuss
More information about the Discuss
mailing list