Sierra wireless drivers

I have physically installed the Sierra Wireless MC8775 card into my S10-3, but do not have the drivers. Can anyone steer me to the drivers and the Sierra Wireless 3G Watcher ?
Also, if anyone knows how to install bluetooth in the s10-3.

Hi,
drivers take the one of the Thinkpad X61 ...WWAN Driver here.
...Connection with watcher take this Sierra Watcher this one i use on my TP X60s ...
sincerely KalvinKlein
Thinkies 2x X200s/X301 8GB 256GB SSD @ Win 7 64
Ideas Centre A520 ,Yoga 2 256GB SSD,Yoga 2 tablet @ Win 8.1

Similar Messages

AT&T 3G (Sierra Wireless) Drivers Working Under 10.6?

Anyone have any luck getting AT$T's Sierra Wireless modem working under 10.6. I have downloaded the latest drivers from Sierra's website which are suppose to allow using Apples WWAN utility; however, the WWAN software does not launch when the device is attached.
I have uninstalled and reinstalled the drive with no luck.
Any suggestions?

I removed everything Sierra I could find. The problem now is that the modem is recognized as a USB disk rather than a modem. Sierra has a switcher application that is supposed to (at the kernel extension -- kext -- level) switch the modem from USB disk to modem mode. That ought to fire up Snow Leopard's natural drivers.
Problem is -- when I install the lastest switcher kext I can find from Sierra's website, installer tells me it didn't install correctly. I think it works with 10.5.5 (or 10.5.6) and higher, but not with 10.6.
Anyone with more information -- it would be greatly appreciated. Thanks.
I have a support e-mail into Sierra but it will probably take them a while to walk me through all the things I have already done before they get to the meat of the matter. (No slam on Sierra support -- just that most support trails take a while for the support personnel to walk one through the standard stuff.)
I'll let everyone know if I hear anything from Sierra.
Or ... perhaps I have a unique, flaky situation.

Sierra Wireless AT&T WWAN issue

Hi - I've got a Lenovo Thinkpad X300 with an OEM Sierra Wireles MC8775 HSDPA card, driver 2.0.9.0, 1/11/2007. It has worked fine except in two instances: first when traveling from the US to Switzerland, upon arrival it "failed to initialize" the device as I tried to run the dialer. This was true despite cold restarts. About a day later it started working, and working consistently, in Switzerland. Upon return to the US exactly the same phenomenon: unable to initialize for about a day. Then, working fine.Lenovo is ready to replace the card, but does anyone know if this is a software or other glitch for which I shouldn't trouble them? Something having to do with switching countries? (And do I appear to be running the latest firmware/drivers? Firmware is H1_1_9_3MCAP.)
Thanks,JZ

To follow up for any that come later: the card was replaced, but experienced the same phenomenon in going to the Netherlands and back again to the US. This time I downloaded and ran the "Sierra Wireless Watcher." After the wireless radio was turned on it sat at "searching..." for about five minutes, then found the new band. Once found it sticks, so the regular Lenovo dialer can then be used. So it's not a hardware problem, and there's a solution. ...JZ

Windows 8.1 Ent. Helix - Sierra Wireless EM7700 device error code 43

System:
Helix 3701XXX
Windows 8.1 Enterprise 64-bit
Third Apps installed
Latest Lenovo Drivers installed
Problem:
Sierra Wireless EM7700 device experiences device code error 43 or not “USB device not recognized.” There are also times where there are two or more instances of the same device in Device Manager.
When the problem occurs, users are unable to see the mobile broadband device under Network connections menu (Charms menu->Settings->Network Connections). Installed drivers on system: Sierra Wireless QMI Lenovo Driver Package 2.6.1.209.0. Experienced this issue with the Lenovo pre-load image and corporate image. The problem has been reported by 10+ users/systems;
When it occurs:
The problem is intermittent; it often occurs after waking the system up from sleep or starting the system from a cold boot. As a workaround, the user has to restart the system a couple to several times in order for the device to be recognized.
Wondering if anyone else has been experiencing this on the Helix 3701XXX Windows 8.1 Enterprise? Any advice is appreciated.

I get similar problems with the Ericsson C5621 wireless card.
To be honest, almost every 3G\4G internal card I've experienced (in Dell, Toshiba and now Lenovo) have suffered from the same two problems (when used against UK mobile providers):
i) issues resuming from sleep - typically the card not responding or not found until doing another sleep\resume or power cycle
ii) issues when moving quickly between cells (e.g. if using the device on a train etc.), when the card will stop transmitting traffic although claims to be connected, and then will become unresponsive attempted a disconnect and reconnect. Again power cycling the card (via sleep\resume, reboot, or occasionally disabling\renabling or uninstalling\reinstalling the driver) will resolve this.
Given that these cards are typically used in mobile devices where sleep\hibernate and being on the move are pretty common scenarios, it is frustrating that the 3G\4G hardware companies still can't get them to work reliable.
Matthew

Using VZAccess Manager v7 With Sierra Wireless SB555 Embedded Device

We have several Panasonic CF-29 Toughbooks with embedded Sierra Wireless SB555 devices. Up to now we were running VZAccess Manager v6.9 on these laptops without any issues.
For consistency sake we want to upgrade VZAccess Manager in these laptops to v7. From what I could determine VZAccess Manager 7 should work with the SB555 devices. This is where I came across an issue.
After installing VZAccess Manager v7 the Verizon Wireless - VZAccess dial-up networking connection was not created. Trying to connect failed: Connection not available.
I manually created the connection and I was able to connect. The problem is that whenever I use Detect Device VZAccess Manager deletes the connection and a new one is not created.
I have a temporary solution by creating a connection named BACKUP Verizon Wireless - VZAccess and then when needed just duplicate this backup connection and rename it properly. At least that is a solution in the lab.
This leads to 3 questions:
Is there a way to make VZAccess anager create the connection as it normally should?
When the automatic area coverage updating takes place, does that trigger a Detect Device? If it does not I guess I am safe to believe that the connection will not be deleted in the field.
Is there a way to reduce the time between the coverage area updates so that I can test this in the lab without having to wait days or weeks for it to happen on its own?
Thanks!

I would recommend uninstalling the current version of VZAM on the PC, and installing the VZAM software from www.vzam.net. I have listed the instructions below on navigating to the software.
Once on the VZAM home page, select supported devices on the red menu located on the left hand side of the screen
Scroll towards the bottom of the page for Laptops with Embedded Verizon Wireless WWAN Module
The 4th selection from the top is labeled “Panasonic Toughbook with global module.” Click on the version number that fits your Windows OS
Enter your wireless number
Before you download, check the two links below on whether you will need drivers for the WWAN device, or the Toughbook itself. I have listed the link below:
http://panasonic.com/toughbook/support
http://www.vzam.net/UploadedFiles/Pan03_RevA_Driver.exe
If you are okay with the drivers, you can proceed to download the VZAM software by clicking the red download now button. Once selected, save the file to your desktop and install the software
***Download version 7.2.9 (2470a) for either Windows XP/Vista or Windows 7
***If step 1 is completed successfully (the drivers installed, the device was found, and the set up completed), the VZAM network connection will be automatically built.
2. At the point that the automatic coverage update initiates, it has already detected the device. (If a device is not detected, you will not be able to activate it or update the coverage information.)
3. To reduce the amount of time a coverage update can take, you can periodically perform a activation on the device. This can be done by selecting the “options” tab at the top of the VZAM menu, and select “activation”. This process will update the PRL (Preferred Roaming List) and coverage area.
I hope this information was helpful.

Need wireless drivers for Satellite A100-259

Hi
Had to reformat my daughters laptop (A100-259 PSAA2) due to virus issues and am in the process of rebuilding it. Almost there but can't seem to get the wireless bit to work. Nothing appears in the system tray even when it's switched on (little switch on the right has the light on). I assume because i've reinstalled XP that i need to reinstall the wireless drivers but i can't seem to find them on the toshiba web site (http://uk.computers.toshiba-europe.com/innovation/download_drivers_bios.jsp?service=UK). It only shows the Atheros management utility.
Any advice would be greatly appreciate especially as i'm pretty new to this kind of stuff and she has lost the manual that came with the laptop.
many thanks
Norrie

Hi!
I dont know why no WLAN drivers are available for this A100 model and Windows XP but you can search for an other A100 model (for example Satellite A100 PSAA8).
Then you will find an Atheros WLAN driver for Windows XP and it should also work.
Bye

HP all in one ms237 cant get wireless drivers to work

Hi i have a HP all in one PC, ive had this PC for a very long time, we upgraded to windows 8 and i dont remember how but i did manage to get wireless drivers on it at one point. the PC's hard drive went out and so i bought a new one and re-installed windows 8 (64 bit) onto it and now i cant get wireless drivers to get installed on it. I tried running the drivers with windows 7 compatability but no dice. I also tried different versions of the driver and still no luck, device manager will see the wireless card but says its not working properly (driver issue) the weird thing is that when i uninstall the drivers for it i can see the adapter in adpater settings, however when i install newer drivers and it goes back to being non existent lol. Any ideas?

Hello @rapid3642,
I understand that you are having issues getting your wireless to work on your HP Pavilion All-in-One MS237 Desktop PC running Windows 8. As you probably have already figured out there are no Windows 8 drivers for your computer. I can see why you would have issues installing Windows 7 drivers on a Windows 8 computer. What you probably did initially was upgrade your Windows 7 to Windows 8 with the driver already installed. Unlike a new Windows 8 installation where you need to install the drivers an upgrade will already have drivers installed and the operating system is simply replacing what is needed without having to go through the installation process.
I would recommend that you either install your original Windows 7 and then upgrade to Windows 8 or you may want to look at replacing the 802.11 b/g/n PCI express wireless half-length mini card with one that is compatible with Windows 8.
I hope this helps. Thank you for posting on the HP Forums. Have a great day!
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
Dunidar
I work on behalf of HP
Find out a bit more about me by checking out my profile!
"Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

WRT54G3G-ST + Sierra Wireless AC597E issue

I've been experiencing some difficulty with my WRT54G3G-ST router in regards to using a Sierra Wireless AC597E. Namely the router fails to recognize the card when plugged in. Everything on the card is still on factory settings, Is there anything particular on the card's setup that needs to be enabled/disabled for the router to recognize it?
The router is using the firmware 2.01.12
Message Edited by Raithgar on 03-04-2008 02:50 PM

Are youusing the a wired broadband router like cable or dsl at the same time using the mobile broadband card? If so, only one service can be used at a time. If the mobile broadband card is enabled, then the wired connection coming from the cable or dsl modem is automatically disabled.

Need a router to conect ipad to a telstra 4G usb Sierra wireless "AirCard 320U

need a router to conect ipad to a telstra 4G usb Sierra wireless "AirCard 320U

You need a MiFi. Talk to your cell provider.

Scientific Linux On G50 Laptop No Wireless Drivers

I bought a brand new G50 laptop with a core i5 intel processor for my business as I do with every computer I installed scientific linux and the wireless drivers aren't available.
I need to find some that will work in a bad way.

Maybe try System76: http://system76.com/index.php?cPath=28
I think they use open source drivers for everything, except the ones with Nvidia cards that probably use the closed source Nvidia drivers (not a problem on Arch obviously). I've heard a lot of good things about System76, and they even sent me free Ubuntu stickers
EDIT: Looks like they use "Intel Wi-Fi Link 5100" for wireless, at least on the one that I checked. Here's more info: http://wiki.archlinux.org/index.php/Wir … 000-series The firmware it talks about I belive is available on the Install CD as long as you tell it to install, or of course with pacman (duh).
Look at the "Windows" button
Last edited by doorknob60 (2009-08-08 01:06:47)

After I loaded Mac OS lion, it won't let me install my Sierra Wireless telstra. It keeps telling me to install it even though i already have. help please?

After I loaded Mac OS lion, it won't let me install my Sierra Wireless telstra. It keeps telling me to install it even though i already have. help please?

Check for new 64 bit software for the modem, other wise you I'll probably have to boot your Mac in 32 bit mode first.. And then every time you want to go online.
I have the Sierra wireless 306 and have their 64 bit lion software installed. Works well.
Best.

Mac OS 10.6 cannot connect to my AT&T Sierra Wireless...help!!

I just purchased my macbook pro OS 10.6 snow leopard today. My entire life ive used windows. all i would like to do is connect to the internet. I have the sierra wireless usbconnect 811 thru AT&T, i spent 3 hours at Apple with 3 different Genius bar guys and all they concluded was it is incompatible but if i do enough research online i could find a way....well ive spent 2 hours online and no luck. people talked about finding some telephone icon under networks but i cannot find that either. i feel helpless~

Hi,
Go to the Sierra website and look for their supporrt area. I did see Mac OS compatibiity, but it doesn't mention Snow Leopard. Most likely they haven't updated their software/hardware for 10.6
The only mention of Mac OS here is 10.4. That was Tiger, two operating systems back from Snow Leopard.
http://www.sierrawireless.com/resources/documents/support/2130853Watcher_QSG_for_Mac_OS_10.4.xv1.2.pdf
Carolyn

Network Manager fails to connect with Sierra Wireless 3G/4G modem

Hi,
I have three Asus Laptops running with Arch (Asus N56VZ, Asus F3JC, Asus UL80VS). All laptops work with Cinnamon Desktop. Everything works fine except 3G Modem in Network Manager. I have two USB modems: Sierra Wireless AirCard 310U and Sierra Wireless AirCard 320U.
Modems had worked fine in end of year 2012, when NetworkManager version was 0.9.6.4 and ModemManager 0.6.0.0. After update (NM >0.8.X.X, MM >0.7.X. - when the ModemManager.service appeared) until now, I can't connect to the internet on all Asus laptops. Since 2013 I have to use wvdial, because in wvdial modems works fine. It is Arch problem, because in Linux Mint 15 I can connect with NetworkManager.
Sierra AirCard 310U - When I'm connecting to the internet, modem reboots itself.
Sierra AirCard 320U - When I'm connecting to the internet, Network Manager can't obtain DHCP address.
I would be grateful for any help.
Sierra Wireless AirCard 310U (USB 3G Modem) log:
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) starting connection 'Orange PL'
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled...
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started...
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete.
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Simple connect started...
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Simple connect state (3/8): Enable
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
aug 22 13:41:35 AsusN56VZ ModemManager[308]: <warn> (ttyUSB2): port attributes not fully set
aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:41:39 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '260', MNC: '3', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:41:40 AsusN56VZ kernel: usb 3-2: USB disconnect, device number 3
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ ModemManager[308]: mm_serial_port_close: assertion `priv->open_count > 0' failed
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (4/8): Wait to get fully enabled
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (5/8): Register
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> (tty/ttyUSB2): released by modem /sys/devices/pci0000:00/0000:00:14.0/usb3/3-2
aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (6/8): Bearer
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB0: Sierra USB modem converter now disconnected from ttyUSB0
aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.0: device disconnected
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: Sierra USB modem converter now disconnected from ttyUSB1
aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.1: device disconnected
aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: Sierra USB modem converter now disconnected from ttyUSB2
aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.3: device disconnected
aug 22 13:41:40 AsusN56VZ kernel: sierra_net 3-2:1.7 wwp0s20u2i7: unregister 'sierra_net' usb-0000:00:14.0-2, Sierra Wireless USB-to-WWAN Modem
aug 22 13:41:40 AsusN56VZ kernel: ModemManager[308]: segfault at 28 ip 0000000000433350 sp 00007ffff409e088 error 4 in ModemManager[400000+e0000]
aug 22 13:41:40 AsusN56VZ systemd[1]: ModemManager.service: main process exited, code=dumped, status=11/SEGV
aug 22 13:41:40 AsusN56VZ systemd[1]: Unit ModemManager.service entered failed state.
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> ModemManager disappeared from bus
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): device state change: prepare -> unmanaged (reason 'removed') [40 10 36]
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): deactivating device (reason 'removed') [36]
aug 22 13:41:40 AsusN56VZ laptop-mode[2414]: Laptop mode
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): cleaning up...
aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): taking down device.
aug 22 13:41:40 AsusN56VZ laptop-mode[2415]: enabled, not active
aug 22 13:41:40 AsusN56VZ systemd-coredump[2336]: Process 308 (ModemManager) dumped core.
aug 22 13:41:40 AsusN56VZ systemd[1]: Starting Modem Manager...
aug 22 13:41:40 AsusN56VZ systemd[1]: ModemManager.service holdoff time over, scheduling restart.
aug 22 13:41:40 AsusN56VZ systemd[1]: Stopping Modem Manager...
aug 22 13:41:40 AsusN56VZ systemd[1]: Starting Modem Manager...
aug 22 13:41:43 AsusN56VZ kernel: sierra_net 3-2:1.7 (unregistered net_device): usb_control_msg failed, status -19
Sierra Wireless AirCard 320U (3G/4G Modem) log:
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) starting connection 'Orange PL'
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) scheduled...
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) started...
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) complete.
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Simple connect started...
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Simple connect state (3/8): Enable
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (disabled -> enabling)
aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <warn> (ttyUSB3): port attributes not fully set
aug 22 13:48:02 AsusN56VZ ModemManager[314]: <warn> (ttyUSB4): port attributes not fully set
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (unknown -> registering)
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (registering -> home)
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: '260', MNC: '3', Location area code: '4FB9', Cell ID: '9C65539')
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (enabling -> registered)
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (4/8): Wait to get fully enabled
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (5/8): Register
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (6/8): Bearer
aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> WWAN now enabled by management service
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (7/8): Connect
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (registered -> connecting)
aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (40)
aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: access technology changed (unknown -> hsdpa, hsupa)
aug 22 13:48:09 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connecting -> connected)
aug 22 13:48:09 AsusN56VZ ModemManager[314]: <info> Simple connect state (8/8): All done
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) scheduled...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) starting...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: prepare -> config (reason 'none') [40 50 0]
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): bringing up device.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) successful.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) scheduled.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) complete.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) started...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (wwp0s20u2i7) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 22 13:48:09 AsusN56VZ kernel: IPv6: ADDRCONF(NETDEV_UP): wwp0s20u2i7: link is not ready
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> dhclient started with pid 2351
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) complete.
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) started...
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) complete.
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Internet Systems Consortium DHCP Client 4.2.5-P1
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Copyright 2004-2013 Internet Systems Consortium.
aug 22 13:48:09 AsusN56VZ dhclient[2351]: All rights reserved.
aug 22 13:48:09 AsusN56VZ dhclient[2351]: For info, please visit https://www.isc.org/software/dhcp/
aug 22 13:48:09 AsusN56VZ dhclient[2351]:
aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (wwp0s20u2i7): DHCPv4 state changed nbi -> preinit
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Listening on LPF/wwp0s20u2i7/8e:1d:fe:e0:02:07
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Sending on LPF/wwp0s20u2i7/8e:1d:fe:e0:02:07
aug 22 13:48:09 AsusN56VZ dhclient[2351]: Sending on Socket/fallback
aug 22 13:48:09 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 5
aug 22 13:48:14 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 5
aug 22 13:48:19 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
aug 22 13:48:26 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
aug 22 13:48:33 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
aug 22 13:48:36 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (40)
aug 22 13:48:40 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 10
aug 22 13:48:50 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 17
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <warn> (wwp0s20u2i7): DHCPv4 request timed out.
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (wwp0s20u2i7): canceled DHCP transaction, DHCP client pid 2351
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) started...
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <warn> Activation (ttyUSB3) failed for connection 'Orange PL'
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) complete.
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: failed -> disconnected (reason 'none') [120 30 0]
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): deactivating device (reason 'none') [0]
aug 22 13:48:54 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connected -> disconnecting)
aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'connected' --> 'disconnecting' (reason: user-requested)
Last edited by Shocker (2013-09-14 20:08:08)

Shocker wrote:I don't think it's kernel problem, because Linux Mint 15 have kernel 3.8 and there is everything fine. Maybe systemd (Fedora & Arch have systemd, but Mint sysvinit..), maybe version of dhcpcd, I have no idea...
To test, I downgraded my kernel
~ ᐅ uname -r
3.9.5-301.fc19.x86_64.debug
And now I see in messages
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) starting connection 'Telstra'
Sep 15 09:46:17 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) scheduled...
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) started...
Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) complete.
Sep 15 09:46:17 localhost modem-manager[757]: <info> (ttyUSB2) opening serial port...
Sep 15 09:46:17 localhost modem-manager[757]: <warn> (ttyUSB2): port attributes not fully set
Sep 15 09:46:17 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling)
Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <info> (ttyUSB2) opening serial port...
Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <warn> (ttyUSB2): port attributes not fully set
Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling)
Sep 15 09:46:18 localhost dbus-daemon[618]: modem-manager[757]: <info> (ttyUSB2): using PDU mode for SMS
Sep 15 09:46:18 localhost modem-manager[757]: <info> (ttyUSB2): using PDU mode for SMS
Sep 15 09:46:18 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling -> enabled)
Sep 15 09:46:18 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling -> enabled)
Sep 15 09:46:18 localhost NetworkManager[724]: <info> WWAN now enabled by management service
Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabled -> registered)
Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabled -> registered)
Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> connected)
Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> connected)
Sep 15 09:46:19 localhost kernel: [ 5056.773068] IPv6: ADDRCONF(NETDEV_UP): wwp0s29u1u1i7: link is not ready
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) scheduled...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) starting...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: prepare -> config (reason 'none') [40 50 0]
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): bringing up device.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) successful.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) complete.
Sep 15 09:46:19 localhost avahi-daemon[607]: Registering new address record for fe80::c0c3:a2ff:fe4a:207 on wwp0s29u1u1i7.*.
Sep 15 09:46:19 localhost kernel: [ 5056.876750] IPv6: ADDRCONF(NETDEV_CHANGE): wwp0s29u1u1i7: link becomes ready
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) started...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Beginning DHCPv4 transaction (timeout in 45 seconds)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> dhclient started with pid 10376
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) complete.
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) started...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Sep 15 09:46:19 localhost dhclient[10376]: Internet Systems Consortium DHCP Client 4.2.5
Sep 15 09:46:19 localhost dhclient[10376]: Copyright 2004-2013 Internet Systems Consortium.
Sep 15 09:46:19 localhost dhclient[10376]: All rights reserved.
Sep 15 09:46:19 localhost dhclient[10376]: For info, please visit https://www.isc.org/software/dhcp/
Sep 15 09:46:19 localhost dhclient[10376]:
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed nbi -> preinit
Sep 15 09:46:19 localhost dhclient[10376]: Listening on LPF/wwp0s29u1u1i7/c2:c3:a2:4a:02:07
Sep 15 09:46:19 localhost dhclient[10376]: Sending on LPF/wwp0s29u1u1i7/c2:c3:a2:4a:02:07
Sep 15 09:46:19 localhost dhclient[10376]: Sending on Socket/fallback
Sep 15 09:46:19 localhost dhclient[10376]: DHCPREQUEST on wwp0s29u1u1i7 to 255.255.255.255 port 67 (xid=0x6e8c90b2)
Sep 15 09:46:19 localhost dhclient[10376]: DHCPNAK from 10.102.67.253 (xid=0x6e8c90b2)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed preinit -> expire
Sep 15 09:46:19 localhost dhclient[10376]: DHCPDISCOVER on wwp0s29u1u1i7 to 255.255.255.255 port 67 interval 6 (xid=0xae2cec8)
Sep 15 09:46:19 localhost dhclient[10376]: DHCPREQUEST on wwp0s29u1u1i7 to 255.255.255.255 port 67 (xid=0xae2cec8)
Sep 15 09:46:19 localhost dhclient[10376]: DHCPOFFER from 10.102.67.253
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed expire -> preinit
Sep 15 09:46:19 localhost dhclient[10376]: DHCPACK from 10.102.67.253 (xid=0xae2cec8)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed preinit -> bound
Sep 15 09:46:19 localhost NetworkManager[724]: <info> address 10.102.67.12
Sep 15 09:46:19 localhost NetworkManager[724]: <info> prefix 24 (255.255.255.0)
Sep 15 09:46:19 localhost NetworkManager[724]: <info> gateway 10.102.67.12
Sep 15 09:46:19 localhost NetworkManager[724]: <info> nameserver '10.4.81.103'
Sep 15 09:46:19 localhost NetworkManager[724]: <info> nameserver '10.4.182.20'
Sep 15 09:46:19 localhost NetworkManager[724]: nm_ip4_config_add_wins: assertion `wins > 0' failed
Sep 15 09:46:19 localhost NetworkManager[724]: <info> wins '0.0.0.0'
Sep 15 09:46:19 localhost NetworkManager[724]: nm_ip4_config_add_wins: assertion `wins > 0' failed
Sep 15 09:46:19 localhost NetworkManager[724]: <info> wins '0.0.0.0'
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Commit) started...
Sep 15 09:46:19 localhost avahi-daemon[607]: Joining mDNS multicast group on interface wwp0s29u1u1i7.IPv4 with address 10.102.67.12.
Sep 15 09:46:19 localhost avahi-daemon[607]: New relevant interface wwp0s29u1u1i7.IPv4 for mDNS.
Sep 15 09:46:19 localhost avahi-daemon[607]: Registering new address record for 10.102.67.12 on wwp0s29u1u1i7.IPv4.
Sep 15 09:46:19 localhost dhclient[10376]: bound to 10.102.67.12 -- renewal in 97473 seconds.
Sep 15 09:46:20 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Sep 15 09:46:20 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Commit) complete.
Sep 15 09:46:20 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 15 09:46:20 localhost NetworkManager[724]: <info> Policy set 'Telstra' (wwp0s29u1u1i7) as default for IPv4 routing and DNS.
Sep 15 09:46:20 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) successful, device activated.
I'm going to ask on #fedora and see how i can best diagnose what's going on. At least I now have it working, albeit on an older kernel.
Last edited by qnm (2013-09-14 23:48:05)

Windows 7 and Sierra Wireless 5725 Modem (Verizon)

I have tried to download just about everything to get the Sierra Wireless 5725 Modem for Verizon to work. Any help would be appreciated.
K

Hi @emma22
I would like to do my best to help, but please bear in mind the issue you are expressing is an inquiry for Microsoft not HP. I did find something I think will be most helpful, and I hope it resolves the issue, but if the issue persists, or you have additional questions, it might be best to reach out to the Microsoft community.
Here is what I found; HomeGroup from start to finish.
In the top right hand corner of the article, you can change it from WIndows 7 to Windows 8. I hope this helps.
Please click the Thumbs up icon below to thank me for responding.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
Sunshyn2005 - I work on behalf of HP

Sierra Wireless Aircard - not receiving data while connected to the network

Hello,
Can anyone please help me out here please.
I have a wireless internet connection on the Bigpond 3g network in Australia. It uses the Sierra Wireless Aircard 880U and the Bigpond connection manager software (version 2.10.18) to connect to the internet. This has been running pretty fine since I installed it some 4 months ago.
Now in the last 3 weeks I've been having connection problems, or actually I'm still connected, but data just suddenly stops coming in. The connection manager software states that I'm still connected to the 3g network; and I can see that data is still sent from my mac (the software tracks the data sent and data received); however there's no more data coming in (or very little, as in bytes), and Safari (or any other application like Skype, the widgets or mail) eventually fails (just happened again: "Safari could not open the page “http://discussions.apple.com/post!post.jspa?forumID=1222&reply=false” because the server is not responding" - while I was still connected according to the connection manager).
Also I can't ping anymore. Packets are sent out, but nothing comes back.
Now I've spent the last 3 weeks on the phone with Bigpond support but they can't resolve the problem. We have tried all the resources; including reinstalling the software, de- and reactivating my account, rebooting, removing and reconnecting the device, creating a specific location for the wireless card as to reduce any possible interference from airport, etc. But this hasn't resolved the problem.
The support people are now stating that it is not their device or software that is faulty (as the can see that I'm connected to the network just fine on their side), but something specific to my Mac that is causing the data problem and that I need to contact mac support.
The annoying fact is that the problem is erratic. Usually when I start up my mac in the morning; I can connect and surf the web without a problem, but later in the day, the internet connection will fail. I will restart the mac and bigpond connection manager and sometimes I may be able to get back online, but most of the time there is no more data (or very little data) coming in even though the connection manager tells me I am connected to the network and data is going out and very little coming back in (a few kilobytes at the most). Personally I have the impression that the Bigpond connection manager software is not too stable, but I can't put my finger on it.
Also the connection manger software seems to behave erratic. Sometimes it is connected and I can surf fine, while it states that it is (still) determining the IP adress, other times it will show a valid IP adress but I'm not getting data (or vice versa). Also I've been getting other error messages, like: "unable to initialise the device" and a mac popup message: " a modem error ocurred; cannot negotiate a valid set of ppp...."
Hopefully theres someone who can give me a hand here based on what I've written. I'm at wits end. Just let me know if I need to supply need more info;
thanks

I have just discovered another aspect of this issue.
If I have the Macbook connected to my router which is then connected to the Mac Pro but the router is not connected to the internet then PS on the Macbook starts up with no problem.
If the Mac Pro is not connected to the Router then PS will not start up on the Mac Book.
I suspect that this behavour started after I installed 10.5.7 - however as I cannot recollect starting up PS in standalone mode prior to last week before I installed 10.5.7 via the combo package.
So any clues please
Derek

Sierra wireless drivers

Similar Messages

Maybe you are looking for