Re: [CFT] Sierra Wireless HSPA+ USB modem
On Friday 08 July 2011 03:25:39 PseudoCylon wrote: On Thu, Jul 7, 2011 at 6:47 AM, Hans Petter Selasky hsela...@c2i.net wrote: On Thursday 07 July 2011 14:43:22 PseudoCylon wrote: On Wed, Jul 6, 2011 at 9:19 AM, Hans Petter Selasky hsela...@c2i.net wrote: Hi, I'm going to review and import your driver. --HPS Hi, The intial patch had some bad code and didn't compile on 9-current. I've tried to clean it up. Please test and report back if I didn't break anything. http://hselasky.homeunix.org:8192/usie_for_FreeBSD_9_current.patch --HPS Hello, Hi, Can I remove the mock DHCP client? It does not appear to be sending the DHCP frames anywhere, except BPF ? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Sierra Wireless HSPA+ USB modem
Hi, I found some more bugs/issues before I committed the driver. Please verify: http://svn.freebsd.org/changeset/base/223864 --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Sierra Wireless HSPA+ USB modem
On Fri, Jul 8, 2011 at 1:35 AM, Hans Petter Selasky hsela...@c2i.net wrote: On Friday 08 July 2011 03:25:39 PseudoCylon wrote: On Thu, Jul 7, 2011 at 6:47 AM, Hans Petter Selasky hsela...@c2i.net wrote: On Thursday 07 July 2011 14:43:22 PseudoCylon wrote: On Wed, Jul 6, 2011 at 9:19 AM, Hans Petter Selasky hsela...@c2i.net wrote: Hi, I'm going to review and import your driver. --HPS Hi, The intial patch had some bad code and didn't compile on 9-current. I've tried to clean it up. Please test and report back if I didn't break anything. http://hselasky.homeunix.org:8192/usie_for_FreeBSD_9_current.patch --HPS Hello, Hi, Can I remove the mock DHCP client? Yes, you can. I had a feeling of it won't go into the src tree. That's why it was in a separate file. The only drawback is now users have to manually set up the connection. Here is an updated how-to-use #ifconfig usie0 up IP and DNS addr will be printed on the console. Using those addr, #ifconfig usie0 inet N.N.N.N #ifconfig usie0 defaultif #echo nameserver N.N.N.N /etc/resolv.conf One nemaserve is sufficient. #echo nameserver N.N.N.N /etc/resolv.conf And, I have tried the committed version of the driver, and it is working fine. Thanks for committing. AK ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Sierra Wireless HSPA+ USB modem
On Wed, Jul 6, 2011 at 9:19 AM, Hans Petter Selasky hsela...@c2i.net wrote: Hi, I'm going to review and import your driver. --HPS Hi, The intial patch had some bad code and didn't compile on 9-current. I've tried to clean it up. Please test and report back if I didn't break anything. http://hselasky.homeunix.org:8192/usie_for_FreeBSD_9_current.patch --HPS Hello, Thanks for the patch. if_usie.c 241 if (usbd_lookup_id_by_uaa(usie_devs, sizeof(usie_devs), uaa) != 0) 242 return; /* no device match */ It should return non-zero on success, but somehow this caused the process to exit, and modem stayed being a CD-ROM. The compiler complained about uninitialized int if_usie.c: 1484 - uint8_t pad; + uint8_t pad = 0; Otherwise it worked fine. AK ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Sierra Wireless HSPA+ USB modem
On Thursday 07 July 2011 14:43:22 PseudoCylon wrote: On Wed, Jul 6, 2011 at 9:19 AM, Hans Petter Selasky hsela...@c2i.net wrote: Hi, I'm going to review and import your driver. --HPS Hi, The intial patch had some bad code and didn't compile on 9-current. I've tried to clean it up. Please test and report back if I didn't break anything. http://hselasky.homeunix.org:8192/usie_for_FreeBSD_9_current.patch --HPS Hello, Thanks for the patch. if_usie.c 241 if (usbd_lookup_id_by_uaa(usie_devs, sizeof(usie_devs), uaa) != 0) 242 return; /* no device match */ It should return non-zero on success, but somehow this caused the process to exit, and modem stayed being a CD-ROM. Hi, Is this device changing its USB vendor and product ID ? We need this ID check, else all mass storage devices will receive the eject command! --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Sierra Wireless HSPA+ USB modem
On Thursday 07 July 2011 14:43:22 PseudoCylon wrote:
The compiler complained about uninitialized int
if_usie.c: 1484
- uint8_t pad;
+ uint8_t pad = 0;
I changed it so that pad is set in both cases:
pad = (hip-id USIE_HIP_PAD) ? 1 : 0;
if ((hip-id USIE_HIP_MASK) == USIE_HIP_CNS2H) {
cns = (struct usie_cns *)(((uint8_t *)(hip + 1)) +
pad);
--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Sierra Wireless HSPA+ USB modem
On Thu, Jul 7, 2011 at 6:47 AM, Hans Petter Selasky hsela...@c2i.net wrote:
On Thursday 07 July 2011 14:43:22 PseudoCylon wrote:
On Wed, Jul 6, 2011 at 9:19 AM, Hans Petter Selasky hsela...@c2i.net
wrote:
Hi,
I'm going to review and import your driver.
--HPS
Hi,
The intial patch had some bad code and didn't compile on 9-current. I've
tried to clean it up. Please test and report back if I didn't break
anything.
http://hselasky.homeunix.org:8192/usie_for_FreeBSD_9_current.patch
--HPS
Hello,
Thanks for the patch.
if_usie.c
241 if (usbd_lookup_id_by_uaa(usie_devs, sizeof(usie_devs), uaa) != 0)
242 return; /* no device match */
It should return non-zero on success, but somehow this caused the
process to exit, and modem stayed being a CD-ROM.
Hi,
Is this device changing its USB vendor and product ID ?
Yes, it does. So I added the device id for cd-rom, SIERRA, TRUINSTALL
(already in usbdevs).
static const STRUCT_USB_HOST_ID usie_devs[] = {
#define USIE_DEV(v, d) {\
USB_VP(USB_VENDOR_##v, USB_PRODUCT_##v##_##d) }
USIE_DEV(SIERRA, MC8700),
USIE_DEV(AIRPRIME, USB308),
+USIE_DEV(SIERRA, TRUINSTALL),
#undef USIE_DEV
};
Now it works even if the modem is plugged in before loading the
driver. The device id 0x0fff is for cd-rom, but sierra didn't specify
the vendor id. So, there might be (AIRPRIME, TRUINSTALL).
With your uint8_t pad fix, the driver works fine.
Thanks
AK
Here is a patch.
diff --git a/sys/dev/usb/net/if_usie.c b/sys/dev/usb/net/if_usie.c
index 552765b..f6f6c60 100644
--- a/sys/dev/usb/net/if_usie.c
+++ b/sys/dev/usb/net/if_usie.c
@@ -88,6 +88,7 @@ static const STRUCT_USB_HOST_ID usie_devs[] = {
USB_VP(USB_VENDOR_##v, USB_PRODUCT_##v##_##d) }
USIE_DEV(SIERRA, MC8700),
USIE_DEV(AIRPRIME, USB308),
+ USIE_DEV(SIERRA, TRUINSTALL),
#undef USIE_DEV
};
@@ -1522,8 +1523,9 @@ usie_hip_rsp(struct usie_softc *sc, uint8_t
*rsp, uint32_t len)
DPRINTF(hip: len=%d msgID=%02x, param=%02x\n,
be16toh(hip-len), hip-id, hip-param);
+ pad = (hip-id USIE_HIP_PAD) ? 1 : 0;
+
if ((hip-id USIE_HIP_MASK) == USIE_HIP_CNS2H) {
- pad = (hip-id USIE_HIP_PAD) ? 1 : 0;
cns = (struct usie_cns *)(((uint8_t *)(hip + 1)) + pad);
if (j (sizeof(struct usie_cns) +
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Sierra Wireless HSPA+ USB modem
Hi, I'm going to review and import your driver. --HPS Hi, The intial patch had some bad code and didn't compile on 9-current. I've tried to clean it up. Please test and report back if I didn't break anything. http://hselasky.homeunix.org:8192/usie_for_FreeBSD_9_current.patch --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Sierra Wireless HSPA+ USB modem
On Tuesday 28 June 2011 06:58:37 PseudoCylon wrote: Hello Here is a driver for Sierra Wireless HSPA+ USB modem. Please test it. My subscription will expire on June 29, 2011. (Yes, it sounds silly.) So, try it before too late. source tree https://gitorious.org/usie/usie/trees/master tarball https://gitorious.org/usie/usie/archive-tarball/master The driver should work on CURRENT and 8.2 RELEASE. Supports only Direct IP supported models with device ID of 0x68a3 (Direct IP == the device has a port we can throw IP packets at, no need to use any serial port) A list of supported device names are posted on FreeBSD forum. http://forums.freebsd.org/showthread.php?p=138758#post138758 * How to use 0) add a following to somewhere in /usr/src/sys/dev/usbdevs product AIRPRIME USB3080x68A3 USB308 HSPA+ USB Modem 1) compile 2) #kldload usie 3) plugin the device (Make sure load the module first) 4) wait while the modem is going though power up cycle 5) #dhclient usie0 6) surf * To disconnect #ifconfig usie0 down or #kldunload usie Hi, I'm going to review and import your driver. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Sierra Wireless HSPA+ USB modem
- Original Message - From: Hans Petter Selasky hsela...@c2i.net To: freebsd-current@freebsd.org; PseudoCylon moonlightak...@yahoo.ca Cc: freebsd-wirel...@freebsd.org freebsd-wirel...@freebsd.org Sent: Tuesday, June 28, 2011 12:50:57 AM Subject: Re: [CFT] Sierra Wireless HSPA+ USB modem On Tuesday 28 June 2011 06:58:37 PseudoCylon wrote: Hello Here is a driver for Sierra Wireless HSPA+ USB modem. Please test it. My subscription will expire on June 29, 2011. (Yes, it sounds silly.) So, try it before too late. source tree https://gitorious.org/usie/usie/trees/master tarball https://gitorious.org/usie/usie/archive-tarball/master The driver should work on CURRENT and 8.2 RELEASE. Supports only Direct IP supported models with device ID of 0x68a3 (Direct IP == the device has a port we can throw IP packets at, no need to use any serial port) A list of supported device names are posted on FreeBSD forum. http://forums.freebsd.org/showthread.php?p=138758#post138758 * How to use 0) add a following to somewhere in /usr/src/sys/dev/usbdevs product AIRPRIME USB3080x68A3 USB308 HSPA+ USB Modem 1) compile 2) #kldload usie 3) plugin the device (Make sure load the module first) 4) wait while the modem is going though power up cycle 5) #dhclient usie0 6) surf * To disconnect #ifconfig usie0 down or #kldunload usie Hi, I'm going to review and import your driver. Thank you. BTW, U3G_DEV(SIERRA, MC8700, 0) in u3g.c and USIE_DEV(SIERRA,MC8700) in usie.c are referring the same device, and MC8700 should support direct IP. AK ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[CFT] Sierra Wireless HSPA+ USB modem
Hello Here is a driver for Sierra Wireless HSPA+ USB modem. Please test it. My subscription will expire on June 29, 2011. (Yes, it sounds silly.) So, try it before too late. source tree https://gitorious.org/usie/usie/trees/master tarball https://gitorious.org/usie/usie/archive-tarball/master The driver should work on CURRENT and 8.2 RELEASE. Supports only Direct IP supported models with device ID of 0x68a3 (Direct IP == the device has a port we can throw IP packets at, no need to use any serial port) A list of supported device names are posted on FreeBSD forum. http://forums.freebsd.org/showthread.php?p=138758#post138758 * How to use 0) add a following to somewhere in /usr/src/sys/dev/usbdevs product AIRPRIME USB3080x68A3 USB308 HSPA+ USB Modem 1) compile 2) #kldload usie 3) plugin the device (Make sure load the module first) 4) wait while the modem is going though power up cycle 5) #dhclient usie0 6) surf * To disconnect #ifconfig usie0 down or #kldunload usie AK ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
uplcom driver and USB modem
I've recently been trying to get my USB modem working in FreeBSD -CURRENT, without much success. In Linux, I can load the pl2303 driver and a ttyUSB0 device node is then used to communicate with the modem as if were attached to a serial port. In FreeBSD, I load the uplcom driver and the Prolific PL-2303 device is found and a ucom0 node gets created, but after that there doesn't seem to be any communications with the modem. Is the uplcom driver broken for my Jetway modem, or is there something I can do to get comms working? I know I should probably get a 'proper' serial modem, but I'd like to know if it's at all possible to get my current modem working. -- Bruce Cran ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb modem problem
On Thu, Nov 28, 2002 at 11:44:10PM -0700, [EMAIL PROTECTED] wrote: Hello, I am trying to use an usb modem under freebsd. It is detected during boot. My system is current as of yesterday sources. Dmesg output is attached. Modem is recognized as /dev/ugen0 and there is another node /dev/ugen0.1 I setup my ppp.conf file to use /dev/ugen0 when I try to use it the result is below: test# ppp Working in interactive mode Using interface: tun0 ppp ON test term deflink: Entering terminal mode on /dev/ugen0 Type '~?' for help ugenpool: no edesc ugenpool: no edesc ppp ON test q test# ugen0 is a generic raw usb device, which is used as a fallback if no specific driver is available. ugen is not a tty type as expected by ppp. Did you compile ucom and umodem in your kernel? uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0x2440-0x245f irq 11 at device 31.2 on pci0 usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: STMicroelectronics USB Communicator, rev 1.00/1.01, addr 2 -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
usb modem problem
Hello, I am trying to use an usb modem under freebsd. It is detected during boot. My system is current as of yesterday sources. Dmesg output is attached. Modem is recognized as /dev/ugen0 and there is another node /dev/ugen0.1 I setup my ppp.conf file to use /dev/ugen0 when I try to use it the result is below: test# ppp Working in interactive mode Using interface: tun0 ppp ON test term deflink: Entering terminal mode on /dev/ugen0 Type '~?' for help ugenpool: no edesc ugenpool: no edesc ppp ON test q test# I do not know if I forget to do something. Best regards, -- Ertan Kucukoglu [EMAIL PROTECTED] \M-kH\^Y\M^?\^W'\^_\M-~\^Wp\^_\M-~\^W\M-\^_\M-~\^Wk \M-~\^W\M-,)\M^?\^W@\^B Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #5: Thu Nov 28 14:19:16 EET 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/OPTIMIZED_KERNEL Preloaded elf kernel /boot/kernel/kernel at 0xc0432000. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 1594831500 Hz CPU: Pentium 4 (1594.83-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf12 Stepping = 2 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 402653184 (384 MB) avail memory = 386584576 (368 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled acpi0: COMPAQ CPQ003E on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 9 entries at 0xc00ebfd0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0xf808-0xf80b on acpi0 acpi_cpu0: CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82845 host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: PCIBIOS PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 fxp0: Intel Pro/100 Ethernet port 0x1000-0x103f mem 0xfc40-0xfc400fff irq 5 at device 8.0 on pci2 fxp0: Ethernet address 00:08:02:16:d9:0e inphy0: i82562EM 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 ATA100 controller port 0x2460-0x246f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0x2440-0x245f irq 11 at device 31.2 on pci0 usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: STMicroelectronics USB Communicator, rev 1.00/1.01, addr 2 pci0: multimedia, audio at device 31.5 (no driver attached) acpi_button0: Power Button on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model 4D Mouse, device ID 6 ppc0 port 0x778-0x77d,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/13 bytes threshold plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 npx0: math processor on motherboard npx0: INT 16 interface pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 1.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 10 packets/entry by default DUMMYNET initialized (011031) acpi_cpu: CPU throttling enabled, 8 steps from 100% to 12.5% ad0: 19092MB WDC WD200EB-11CPF0 [38792/16/63] at ata0-master UDMA100 acd0: CDROM LTN486S at ata1-master PIO4 Mounting root from ufs:/dev/ad0s2a ugenpoll: no edesc ugenpoll: no edesc
Re: USB modem?
Is it a case of being in the usbdevs list _and_ supporting those specs? Or just following the specs? I believe that being listed in usbdevs isn't a requirement, but I'm not positive. I also haven't had any look getting the thing to work dynamically loading the various modules involved. It is detected as a generic device: ugen0: Siemens AG Vox Chicago 390 ISDN, rev 1.10/1.00, addr 2 I will try to build a kernel with the umodem device in it, see if that makes a difference -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB modem?
Whether a device is recognized by a driver depends on one thing only: the probe routine in the driver. It either has to conform to the specs and this device obviously doesn't, or it has to be supported by the driver and therefore the IDs of the device need to be known. The entries in usbdevs* are simply converted to a list of device names plus defines for the use of drivers, to make things simpler. Nick On Tue, 12 Dec 2000, Mark Huizer wrote: Is it a case of being in the usbdevs list _and_ supporting those specs? Or just following the specs? I believe that being listed in usbdevs isn't a requirement, but I'm not positive. I also haven't had any look getting the thing to work dynamically loading the various modules involved. It is detected as a generic device: ugen0: Siemens AG Vox Chicago 390 ISDN, rev 1.10/1.00, addr 2 I will try to build a kernel with the umodem device in it, see if that makes a difference -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Qube Software, Ltd. Private: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB modem?
I have a USB modem here, (Siemens), that I would like to get to work under FreeBSD, but I can't even find the right tools to get vendor and product ID's to add to usbdevs :-( Try looking in dmesg - USB device that don't have known product and vendor ID's have theirs printed. Failing that, check the usbdevs(8) man page. The serious catch about USB modems is that they have to support the USB CDC spec. Not all of them do. If it does, the serial device will be umodem0 (1, 2, 3, ...), and you use it just like a tty line tied to an external modem. Is it a case of being in the usbdevs list _and_ supporting those specs? Or just following the specs? I have the modem in the office, not at home. And of course there is that tricky part where Windows wants my BIOS set to PNP OS=YES and FreeBSD wants it set to NO. but well :-) we can survive that for the moment. Mark -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB modem?
Mark Huizer [EMAIL PROTECTED] types: I have a USB modem here, (Siemens), that I would like to get to work under FreeBSD, but I can't even find the right tools to get vendor and product ID's to add to usbdevs :-( Try looking in dmesg - USB device that don't have known product and vendor ID's have theirs printed. Failing that, check the usbdevs(8) man page. The serious catch about USB modems is that they have to support the USB CDC spec. Not all of them do. If it does, the serial device will be umodem0 (1, 2, 3, ...), and you use it just like a tty line tied to an external modem. Is it a case of being in the usbdevs list _and_ supporting those specs? Or just following the specs? I believe that being listed in usbdevs isn't a requirement, but I'm not positive. I also haven't had any look getting the thing to work dynamically loading the various modules involved. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/ Independent WWW/Unix/FreeBSD consultant,email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB modem?
Mark Huizer [EMAIL PROTECTED] types: Does anyone here have experience on tryuing to add USB devices? I do. I have a USB modem here, (Siemens), that I would like to get to work under FreeBSD, but I can't even find the right tools to get vendor and product ID's to add to usbdevs :-( Try looking in dmesg - USB device that don't have known product and vendor ID's have theirs printed. Failing that, check the usbdevs(8) man page. The serious catch about USB modems is that they have to support the USB CDC spec. Not all of them do. If it does, the serial device will be umodem0 (1, 2, 3, ...), and you use it just like a tty line tied to an external modem. mike -- Mike Meyer http://www.mired.org/home/mwm/ Independent WWW/Unix/FreeBSD consultant,email for rates. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB Modem??
Hey there, Has anyone managed to get USB modem support compiled into the 4.0 kernel using the patches from the projects site?? Or can it be done another way?? Unfortunately my 33.6K internal has rolled over and died and now I just have a 56.6K external USB modem which I haven't been able to get the support for yet (hence I can't cvsup to 4.0 like most ppl have suggested, but thanks for the responses anyway!!). See Ya! -- Brett White [EMAIL PROTECTED] How many Tux could the Daemon Chuck slay if the Daemon Chuck could slay Tux? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
