Curitel PC5740 Wireless Modem (EVDO)
Ben Hacker Jr
strbenjr at yahoo.com
Wed Jan 3 22:03:08 UTC 2007
Yep... I just tried that just moments prior to your email. THANKS!!!
That solved it.. I only needed to add:
umodem_load="YES" to my /boot/loader.conf. The rest was automatic...
Thanks so much for taking the time to reply!
Gary Palmer wrote:
> On Wed, Jan 03, 2007 at 03:45:25PM -0500, Ben Hacker Jr wrote:
>> Dear Sir,
>>
>> I am attempting to get a Broad Band Modem working on:
>>
>> sony# uname -a
>> FreeBSD sony.family.hom 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #2:
>> Tue Dec 19 16:55:50 EST 2006
>> root at sony.family.hom:/usr/obj/usr/src/sys/SONY01 i386
>>
>> The device is a Sprint PC5740 pc card. When I perform a "man umodem"
>> the card is listed (vendor = Curitel)
>>
>> ---
>>
>> As stated (in the umodem man page) this should be recognized as a usb "ucom" device. I
>> stopped the usbd and restarted using "usbd -dv". When I inserted the
>> device I received the following console message:
>>
>> sony# usbd -dv &
>> [1] 753
>> sony# usbd: opened /dev/usb0
>> usbd: opened /dev/usb1
>> usbd: reading configuration file /etc/usbd.conf
>> usbd: opened /dev/usb
>>
>> sony# usbd: ctrlr-attach event bus=2
>> USB_EVENT_CTRLR_ATTACH
>> ...
>> USB_EVENT_DRIVER_ATTACH
>> usbd: device-attach event at 1167852828.349083000, Curitel
>> Communications, Inc., Curitel Communications, Inc.:
>> vndr=0x106c prdct=0x3701 rlse=0x0000 clss=0x0002 subclss=0x0000
>> prtcl=0x0000
>> device names: ugen0
>> usbd: Found action 'USB device' for Curitel Communications, Inc.,
>> Curitel Communications, Inc. at ugen0
>>
>> Please notice that the last two lines indicate that the device was
>> attached to "ugen0" rather then the "ucom0" that I was expecting (and need).
>>
>> I tried to make sure the proper devices were available by manually
>> loading them prior to inserting the card. Here are my loaded modules:
>> (See items 4 & 5 below)
>>
>> sony# kldstat
>> Id Refs Address Size Name
>> 1 13 0xc0400000 47ca94 kernel
>> 2 1 0xc087d000 45b8 snd_t4dwave.ko
>> 3 2 0xc0882000 22b88 sound.ko
>> 4 1 0xc08a5000 3000 uftdi.ko <<<<
>> 5 2 0xc08a8000 32a8 ucom.ko <<<<
>> 6 1 0xc08ac000 59fa4 acpi.ko
>> 7 1 0xc2c4e000 16000 linux.ko
>>
>> Any help will be greatly appreciated! Please reply directly as well as
>> to the list. I am not currently subscribed.
>>
>> http://bsdforums.org/forums/showthread.php?t=45602 (More info on my
>> efforts...)
>
> The man page isn't 100% clear, but you need to load both ucom and
> umodem to recognize the device. Try loading umodem and ucom and
> then attaching (or detaching and reattaching) the device
>
> The umodem code does have the vendor/product IDs in it that match
> the debug info above, so I expect it will be recognized
--
Ben Hacker, Jr.
Network Systems Administrator
strbenjr {at} yahoo.com
ben_hacker {at} inter-op.net
703.751.3757 (h)
-- -- --
http://www.coeba.org
http://www.inter-op.net
More information about the freebsd-stable
mailing list