Setting up Novatel Mifi 2200 on 8.2-REL

Ryan Coleman editor at d3photography.com
Mon Mar 14 22:56:31 UTC 2011


An update:

I rebuilt the kernel and still don't see it. On the office server it was immediately recognized...

x5020 = the embeded zeroCD
x6000 must be the modem and there's a line for it already
"product NOVATEL U760            0x6000  Novatel U760"

Any further ideas?

On Mar 14, 2011, at 10:09 AM, Ryan Coleman wrote:

> Curveball - 
> 
> I have the same image of 8.2 installed in VMware on my MacBook and it found the modem immediately.
> 
> Has to be VMware-related as to why it found it because the office network appliance I have cannot see it and only sees the wintel disc partition, right?
> --
> Ryan
> 
> On Mar 14, 2011, at 6:53 AM, Ryan Coleman wrote:
> 
>> 
>> 
>> On Mar 14, 2011, at 2:28 AM, Maciej Milewski wrote:
>> 
>>> 
>>> Monday 14 of March 2011 01:38:21 Ryan Coleman napisał(a):
>>>> Are you up to a challenge?
>>>> 
>>>> I have my Virgin Mobile MIFI 2200 connected to my new remote server via USB
>>>> (8.2-RELEASE) that I just set up and it's not seeing the modem, but it
>>>> does see the virtual drive on it.
>>>> 
>>>> dmesg output:
>>>>> ugen3.2: <Novatel Wireless Inc.> at usbus3
>>>>> Mar 13 18:39:07 camserve kernel: cd0: <Novatel Mass Storage 1.00> Removable
>>>>> CD-ROM SCSI-2 device
>>> It is recognized as cd device (it's called a feature in windows world - it has 
>>> a drivers for the modem to autoinstall it). Ejecting this cd should detach 
>>> umass and attach modem/serial device:
>>> camcontrol eject cd0
>> 
>> If I don't plug in the device after startup it never sees it. And running that command gets me:
>> # camcontrol eject cd0                              
>> camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed
>> cam_lookup_pass: No such file or directory
>> cam_lookup_pass: either the pass driver isn't in your kernel
>> cam_lookup_pass: or cd0 doesn't exist
>> 
>> 
>>> I think that adding
>>> product NOVATEL ZEROCD2                0x5020  Novatel ZeroCD
>>> into sys/dev/usb/usbdevs and recompiling kernel may work.
>> 
>> Sigh. I don't like recompiling kernels.  I'll check it out._______________________________________________
>> freebsd-net at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
> 
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"



More information about the freebsd-net mailing list