[NTLUG:Discuss] Any idea howtogetaSprintEVDOwirelessbroadbandcard to

Fri Jul 21 22:51:18 CDT 2006

Wow.  You're dead-set on the notion of NDIS wrapper to the rescue.  The 
fact is, though, I have the very same card.  I run it under Fedora Core 5.  
Never figured out why pppd didn't update /etc/resolv.conf, but that's 
another story... it works and I didn't need any special anything, including 
NDIS wrapper.  I am a bit surprised that NDIS wrapper would also work on 
USB to serial devices though... never knew that.  I just know what NDIS is 
for and what layer of OSI it resides in.  I also know that since it's a USB 
modem/serial device and uses pppd to get a network connection set up, that 
definitely goes outside of the scope of NDIS.

As for SuSE handling hardware differently from other Linux distros?  Wow!  
Another new revelation.  I've observed that Knoppix does an amazingly good 
job of detecting hardware and even utilizing it.  The purpose of the 
suggestion was to get another view of the hardware... a second opinion if 
you will.  I know mine works for me... but then I run FC5.  Gettng another 
view will show us what modules get loaded and stuff like that.  Compare 
that with what's not happening under SuSE and we'll have a pretty good idea 
of how to make SuSE act in a way that let's this thing work.

> >From Ndiswrapper wesite ,
>With ndiswrapper , virtually every miniPCI (bulitin), PCI, PCMCIA (Cardbus
>only) or USB wireless network card works in Linux.
>Although ndiswrapper is intended for wireless network cards, other devices
>are known to work : e.g., USB to serial port device,ethernet card,home 
phone
>network device etc. See Wiki entry List for devices known to work .
>
>On 7/21/06, . Daniel <xdesign at hotmail.com> wrote:
> >
> > Interesting.  Let's try another OS.  Do you have a Knoppix or other 
live
> > CD
> > available to you?  Can you get one?  Let's have you boot up with one of
> > those and see what an alternative OS reports to you.
> >
> > >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