MacBook Pro and USB727 Issue

benuwine · EVDO Newbie Joined: 11 Jun 2008 Posts: 1

Hello Everyone,

Hope someone can help out here, I recently tried to install my USB727 USB modem into my MacBook Pro. After installing VZAccess Manager and going through the wizard, it fails when trying to Detect the USB modem (which is plugged in and has a solid green light).

Am I missing anything and/or can I revert the installation somehow to get the modem to work?

Any help is appreciated.

ricksta · EVDO Newbie Joined: 12 Aug 2008 Posts: 1

Hi,

I also had this exact same problem, and a couple friends at work helped me track down what was wrong.

Question: Do you by chance have your Macbook Pro configured with a "case sensitive" file structure?

If so, then here is what I discovered.

There is a bug in the Verizon software that incorrectly accesses at least 1 file using the wrong file name case. If your machine uses the default, "case insensitive" file structure, you would never see the problem.

The problem is that one of the kernel extensions fails to load because of the case problem. I manually worked around the problem by running the following with Administrator permission:

cd /Systems/Library/Extensions/NovatelWireless3G.kext/Contents/Plugins
kextload NovatelWireless3GData.kext

You can see it is now loaded by running:

kextstat -l

Now run VZAccess Manager and it will detect the device.

I think you will need to re-run this manual load every time you plug in the USB727, *and* this load of course will not survive a reboot.

You can see for sure there is at least 1 problem with these instructions that my friend sent me:

% cd /System/Library/Extensions/NovatelWireless3G.kext/Contents
% find . -type f | xargs strings | grep -i plugins
/System/Library/Extensions/NovatelWireless3G.kext/Contents/PlugIns/NovatelWireless3GData.kext

Note the name of the "PlugIns" directory.

Note the directory on your filesystem is called "Plugins".

To fix you should be able to:

% cd /System/Library/Extensions/NovatelWireless3G.kext/Contents
% ln -s Plugins PlugIns

You may need to reboot.

I'll try his suggestion later tonight or tomorrow to see if this fixes it permanently.

Rick