Results 1 to 5 of 5
I need some help getting connected to internet via wireless device, please if you can help me out. I have a Sony Vaio laptop. When I boot up in Vista, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 08-07-2008 #1
How do I get wireless modem to work?
I need some help getting connected to internet via wireless device, please if you can help me out.
I have a Sony Vaio laptop. When I boot up in Vista, I connect to the internet wirelessly using a "Novatel Wireless Expedite EV-DO Modem". There's a little antenna on the right side of the laptop, mounted on the "hinge" where the lid opens & closes.
I've attached a log file for the modem (a .txt file from Vista).
My wireless service is already up and running from Vista. I recently installed and am learning & comparing Ubuntu, Mandriva, and Xandros. I've also been comparing Fedora, OpenSuse, PCLinuxOS, but only on the live distro discs.
I can already connect to WiFi networks from Linuxes; I need the other service because I'm not always near an unlocked WiFi network, however I'm usually within range of Sprint's wireless network.
What do I need to learn to get my wireless internet service working on Linux? Can these alterations be made to a live distro (e.g. I could put them in a .sh script file on a USB drive so I don't have to type them over and over), or do they only work on an installed Linux system?
Versions of installed linuxes: Ubuntu version 8.04, Mandriva Spring 2008 One, Xandros Desktop Pro). I don't have the versions of the live distro CDs handy, but I downloaded and burned live CDs within the last 30 days or so.
I searched on this forum for Novatel and wireless modem, but I didn't find much, so here goes:
I found 'Novatel' here (that person has a different situation than mine, I believe) and here (no replies to original post so no help there).
A reply in this thread said to show output of lsusb and lsmod. I don't know if this is a USB modem - it isn't plugged into a physical USB port, but I'll add that information anyway.
I've also read a little bit about "ndiswrapper", but it pretty much went over my head. I attempted to compile it when I had one of the live distros booted up, but it very quickly got out of hand with error messages. Maybe I'll try again on the installed Ubuntu... I just wish I understood better what ndiswrapper is and what it does and why it does it. I'll read the wiki page again; maybe it'll start making sense. It says something about ndiswrapper not working for Vista?
In the meantime, here's some additional data: From Vista, the driver files listed for the Novatel wireless EVDO modem are
(a) c:\windows\system32\drivers\modem.sys version 6.0.6000.16386 from Microsoft and
(b) c:\windows\system32\drivers\nwusbmdm.sys version 22.214.171.124 from Novatel Wireless Inc
Location of device in Vista is 0000.001a.0001.001.000.000.000.000.000
The Wiki page mentions a .inf file as well as .sys files. I guess I found the .sys files, but what are .inf files and where are they?
Would it be better for me to look at Novatel, Sprint, or Sony's web sites for additional help?
Here's lsusb output from Ubuntu:
Bus 007 Device 002: ID 054c:0281 Sony Corp.
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 003: ID 05ca:183a Ricoh Co., Ltd
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 1410:2120
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 147e:2016
Bus 001 Device 001: ID 0000:0000
Module Size Used by ipv6 267780 10 rfcomm 41744 2 l2cap 25728 13 rfcomm bluetooth 61156 4 rfcomm,l2cap sonypi 23192 0 ppdev 10372 0 acpi_cpufreq 10796 2 cpufreq_ondemand 9740 1 cpufreq_userspace 5284 0 cpufreq_stats 7104 0 cpufreq_conservative 8712 0 cpufreq_powersave 2688 0 freq_table 5536 3 acpi_cpufreq,cpufreq_ondemand,cpufreq_stats container 5632 0 dock 11280 0 sbs 15112 0 sbshc 7680 1 sbs iptable_filter 3840 0 ip_tables 14820 1 iptable_filter x_tables 16132 1 ip_tables nls_iso8859_1 4992 1 nls_cp437 6656 1 vfat 14464 1 fat 54556 1 vfat sbp2 24072 0 parport_pc 36260 0 lp 12324 0 parport 37832 3 ppdev,parport_pc,lp snd_hda_intel 344728 2 snd_pcm_oss 42144 0 snd_mixer_oss 17920 1 snd_pcm_oss snd_pcm 78596 2 snd_hda_intel,snd_pcm_oss pcmcia 40876 0 snd_page_alloc 11400 2 snd_hda_intel,snd_pcm snd_hwdep 10500 1 snd_hda_intel joydev 13120 0 snd_seq_dummy 4868 0 snd_seq_oss 35584 0 snd_seq_midi 9376 0 snd_rawmidi 25760 1 snd_seq_midi snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi iwl4965 105844 0 uvcvideo 58116 0 snd_seq 54224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event compat_ioctl32 2304 1 uvcvideo iwlwifi_mac80211 219108 1 iwl4965 snd_timer 24836 2 snd_pcm,snd_seq videodev 29440 1 uvcvideo battery 14212 0 snd_seq_device 9612 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq v4l1_compat 15492 2 uvcvideo,videodev v4l2_common 18304 2 uvcvideo,videodev cfg80211 15112 1 iwlwifi_mac80211 ac 6916 0 serio_raw 7940 0 sky2 47492 0 i2c_core 24832 0 sony_laptop 35292 0 tifm_7xx1 8576 0 tifm_core 11012 1 tifm_7xx1 yenta_socket 27276 1 rsrc_nonstatic 13696 1 yenta_socket pcmcia_core 40596 3 pcmcia,yenta_socket,rsrc_nonstatic tpm_infineon 10152 0 video 19856 0 output 4736 1 video intel_agp 25492 0 psmouse 40336 0 button 9232 0 snd 56996 15 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device iTCO_wdt 13092 0 iTCO_vendor_support 4868 1 iTCO_wdt shpchp 34452 0 pci_hotplug 30880 1 shpchp tpm 16544 1 tpm_infineon tpm_bios 8320 1 tpm pcspkr 4224 0 agpgart 34760 1 intel_agp evdev 13056 7 soundcore 8800 1 snd ext3 136712 2 jbd 48404 1 ext3 mbcache 9600 1 ext3 usb_storage 73664 0 libusual 19108 1 usb_storage sg 36880 0 sd_mod 30720 4 sr_mod 17956 0 cdrom 37408 1 sr_mod ata_piix 19588 3 pata_acpi 8320 0 ata_generic 8324 0 libata 159344 3 ata_piix,pata_acpi,ata_generic ohci1394 33584 0 scsi_mod 151436 6 sbp2,usb_storage,sg,sd_mod,sr_mod,libata ieee1394 93752 2 sbp2,ohci1394 ehci_hcd 37900 0 uhci_hcd 27024 0 usbcore 146028 6 uvcvideo,usb_storage,libusual,ehci_hcd,uhci_hcd thermal 16796 0 processor 36872 4 acpi_cpufreq,thermal fan 5636 0 fbcon 42912 0 tileblit 3456 1 fbcon font 9472 1 fbcon bitblit 6784 1 fbcon softcursor 3072 1 bitblit fuse 50708 3
- 08-07-2008 #2
- Join Date
- Jul 2004
I really don't think that this uses wireless technology (WiFi) to connect. I remember reading that some can connect using the dialup method. NDISwrapper is for WiFi, and uses a WinXP driver to connect in Linux.
I do see a WiFi driver loaded, the iwl4965 driver for Intel wireless chips.
It is possible that this device is a PCI device. It would then show in the output of this command
Edit: I see you said a Sony Vaio Laptop
I Googles EV-DO in Linux, and came up with some info:
Linux.com :: Get broadband wireless with Verizon EVDO and Linux
Just another Blog: How to get Reliance ZTE MG880 working with Ubuntu Linux 7.04
Crystal Networking » Blog Archive » Setting up EVDO in LinuxPlease do not send Private Messages to me with requests for help. I will not reply.
- 08-07-2008 #3
- Join Date
- Jul 2004
I was checking the USB devices you listed, one I can't find any info on:
Bus 007 Device 002: ID 054c:0281 Sony Corp. (A webcam?) Bus 007 Device 001: ID 0000:0000 Bus 006 Device 003: ID 05ca:183a Ricoh Co., Ltd (Another webcam?) Bus 006 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 002: ID 1410:2120 (Modem?) Bus 002 Device 001: ID 0000:0000 Bus 001 Device 002: ID 147e:2016 (Fingerprint reader) Bus 001 Device 001: ID 0000:0000
tristate "USB driver for GSM and CDMA modems"
depends on USB_SERIAL
Say Y here if you have a GSM or CDMA modem that's connected to USB.
This driver also supports several PCMCIA cards which have a
built-in OHCI-USB adapter and an internally-connected GSM modem.
The USB bus on these cards is not accessible externally.
Supported devices include (some of?) those made by:
Option, Huawei, Audiovox, Novatel Wireless, or Anydata.
To compile this driver as a module, choose M here: the
module will be called option.
If this driver doesn't recognize your device,
it might be accessible via the FTDI_SIO driver.
sudo modprobe optionPlease do not send Private Messages to me with requests for help. I will not reply.
- 08-08-2008 #4
Thanks for taking a look at my issue! I appreciate your assistance.
I can already connect using WiFi, in Ubuntu and Mandriva (but not in Xandros, but I intend to ask for support from the Xandros people to help me through that problem).
I cannot connect using the Novatel Wireless modem. That's what I'm trying to learn how to do.
I have a single webcam. I don't know how to use it from Linux. The laptop is a Sony, so the bus 7 device 2 no doubt is referring to some Sony device other than a camera.
>> There is a kernel module for GSM amd CDMA modems. From what I can tell, it is simply called "option". I don't know if your modem is supported, but Novatel Wireless is on the list of having cards that use this module.
Can you dumb this down just a wee bit. A kernel module = a chunk of software that manages some of the computer's resources. I don't know GSM, CDMA, but do I need to?
Are you saying the name of the kernel module for managing "gsm" and "cdma" modules is "option"? I don't see "option" on my original list of modules. Should I add the 'option' module and if so, how would I do so?
I don't know what you mean by
>>Novatel Wireless is on the list of having cards that use this module
I don't see a card on my computer, though it could be internal within the laptop. Where is this list you mention?
Everything from this point forward in your message made almost no sense to me, I'm sad to say. What is the difference between kernel modules and NDiswrapper? If NDiswrapper is not a good alternative for me, is the discussion of kernel modules relevant?
I'll try to find the doc which you are quoting. Is it here? Both that webpage and your quote are very confusing; it seems as though you (or the author of that doc) are combining instructions of things to type with additional comments. I don't understand the context in which these things have been written. I'm talking about the quote starting with:
>>Try and load it, and see if your card shows up at /dev/ttyACM0
Try and load what? How? Sorry to be so DENSE!
>> NDISwrapper is for WiFi, and uses a WinXP driver
Since I'm not trying to connect via WiFi, and I have Vista & not WinXP, are you saying NDISwrapper won't be useful to me?
Thanks for the other 3 links :thumbsup:. I'll read them over the next few days and I hope I'll become more enlightened.
I'll also try the lspci -nn command and post it back here.
Again, thank you for your time and your help.
- 08-08-2008 #5
- Join Date
- Jul 2004
First, in order to get your Novatel card working in Linux, you are going to have to use a terminal window. The terminal window is where you enter commands to the system. In Windows it is called the Command Line.
In the output of lsusb, the sequence of eight numbers and/or letters separated by a colon, are the hardware ID's of the chips for that card. And yes, the cards can be internal. I just Googled the ID number and name (if any was given) for my information.
Just Google this info and see what you get:
054c:0281 Sony Corp
The drivers in Linux are usually created as modules of the kernel. So a kernel module is usually some type of driver. You can find out more info on a module by using the "modinfo" command in a terminal:
The list of cards I referred to is in the configuration file that I referred to above. Since the "option" driver module did not load automatically, there could be three reasons.
1) The Novatel does not use the "option" driver module.
2) The "option" module is not compiled into your kernel
3) Neither 1 or 2 are correct, but it just doesn't recognize the Novatel as needing the "option" module. So it doesn't load it.
Yes, you can manually load the driver module with the command that I posted before:
sudo modprobe option
As for NDISwrapper, it too is a kernel module. It is only for WinXP WiFi drivers, no Vista drivers. It was developed back when the Linux WiFi drivers were not yet fully developed and dependable. There are still some WiFi cards that don't have Linux drivers, so NDISwrapper is the only method to use them. You have a Linux driver module already loading for your WiFI, so NDISwrapper is not needed.
I think I covered all your questions. let me know if I missed any.Please do not send Private Messages to me with requests for help. I will not reply.