RE: Satellite Broadband Internet Modem IP freebsd-stable@freebsd.org
___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
9-STABLE and Iphone modem (tethering), anyone succeed ?
Hello, does anyone succeed in using an Iphone as modem on 9-STABLE (sources as of March 16) ? I follow the instructions from 'http://forums.freebsd.org/showthread.php?t=19995' using 'usbmuxd' and 'libimobiledevice' from ports. When I start 'usbmuxd' I indeed see in dmesg(1) : ipheth0: on usbus1 ue0: on ipheth0 ue0: bpf attached ue0: Ethernet address: XXX I did not find 'ipheth-pair' (or something equiivalent) in ports, I build it from the sources as indicated in the forum-post, but it fails with : # ./ipheth-pair -v ./ipheth-pair: -14: cannot get lockdown The corresponsing log from 'usbmuxd -v -v ' says (stripped) : [16:29:20.490][3] usbmuxd v1.0.7 starting up [16:29:20.491][4] Creating socket [16:29:20.491][5] client_init [16:29:20.491][5] device_init [16:29:20.491][4] Initializing USB [16:29:20.491][5] usb_init for linux / libusb 1.0 [16:29:20.491][4] Found new device with v/p 05ac:1297 at 1-3 [16:29:20.491][4] Found interface 1 with endpoints 04/85 for device 1-3 [16:29:20.495][4] Using wMaxPacketSize=512 for device 1-3 [16:29:20.495][3] Connecting to new device on location 0x10003 as ID 1 [16:29:20.495][4] 1 device detected [16:29:20.495][3] Initialization complete [16:29:20.495][5] usb polling enable: 0 [16:29:20.496][3] Connected to v1.0 device 1 on location 0x10003 with serial number XXX [16:29:20.496][5] client_device_add: id 1, location 0x10003, serial XXX [16:29:46.428][4] New client on fd 9 [16:29:46.428][5] Client command in fd 9 len 16 ver 0 msg 3 tag 1 [16:29:46.428][5] send_pkt fd 9 tag 1 msg 1 payload_length 4 [16:29:46.428][5] Client 9 now LISTENING [16:29:46.428][5] Enlarging client 9 reply buffer 1024 -> 1308 to make space for device notifications [16:29:46.428][5] send_pkt fd 9 tag 0 msg 4 payload_length 268 [16:29:47.437][4] Client 9 connection closed [16:29:47.437][4] Disconnecting client fd 9 [16:29:47.437][4] New client on fd 9 [16:29:47.437][5] Client command in fd 9 len 24 ver 0 msg 2 tag 2 [16:29:47.437][5] Client 9 connection request to device 1 port 62078 [16:29:47.437][5] [OUT] dev=1 sport=1 dport=62078 seq=0 ack=0 flags=0x2 window=131072[512] len=0 [16:29:47.439][5] [IN] dev=1 sport=62078 dport=1 seq=0 ack=1 flags=0x12 window=131072[512] len=0 [16:29:47.439][5] [OUT] dev=1 sport=1 dport=62078 seq=1 ack=1 flags=0x10 window=131072[512] len=0 [16:29:47.440][5] send_pkt fd 9 tag 2 msg 1 payload_length 4 [16:29:47.440][5] Client 9 switching to CONNECTED state [16:29:47.442][5] [OUT] dev=1 sport=1 dport=62078 seq=1 ack=1 flags=0x10 window=131072[512] len=4 ... (all having 'flags=0x10') [16:29:47.499][5] [IN] dev=1 sport=62078 dport=1 seq=3502 ack=14410 flags=0x10 window=131072[512] len=279 [16:29:47.501][5] [IN] dev=1 sport=62078 dport=1 seq=3781 ack=14410 flags=0x4 window=0[0] len=32 [16:29:47.501][5] RST reason: [16:29:47.501][4] Connection reset by device 1 (1->62078) [16:29:47.501][5] connection_teardown dev 1 sport 1 dport 62078 [16:29:47.501][4] Disconnecting client fd 9 [16:29:47.501][4] client_process: fd 9 not found in client list I hope anyone reading this has had more succes ;-). Thanx, Arno NB 1, Iphone not 'jailbroken' NB 2, yes 'it works' under Windows ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: add k3772z 3g modem support for FreeBSD-9
Hi! usb/165815 On 3/7/12, Adrian Chadd wrote: > Hi! > > Would you please submit this as a PR? > > That way it Doesn't get (as) lost. > > Thanks! > > > adrian > > On 6 March 2012 16:53, Oliver Pinter wrote: >> Hi all! >> >> I wrote a patch, to add support for Vodafone K3772-Z 3g modem. >> >> -- >> Oliver Pinter >> (Tresorium) >> >> ___ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ > freebsd-curr...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: add k3772z 3g modem support for FreeBSD-9
Hi! Would you please submit this as a PR? That way it Doesn't get (as) lost. Thanks! adrian On 6 March 2012 16:53, Oliver Pinter wrote: > Hi all! > > I wrote a patch, to add support for Vodafone K3772-Z 3g modem. > > -- > Oliver Pinter > (Tresorium) > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
add k3772z 3g modem support for FreeBSD-9
Hi all!
I wrote a patch, to add support for Vodafone K3772-Z 3g modem.
--
Oliver Pinter
(Tresorium)
commit 092aa1246e1dde0ffe11a7bc06b540f4fa5851c9
Author: Oliver Pinter
Date: Wed Mar 7 01:47:51 2012 +0100
added support for Vodafone 3772-Z to u3g driver
ugen1.2: at usbus1
ugen1.2: at usbus1 (disconnected)
ugen1.2: at usbus1
umodem0: on usbus1
umodem0: data interface 2, has CM over data, has break
umodem1: on usbus1
umodem1: data interface 4, has CM over data, has break
cdce0: on usbus1
ue0: on cdce0
ue0: Ethernet address: 02:77:c1:XX:XX:XX
umass0: on usbus1
(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0
(probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI status: Check Condition
(probe0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to rea
dy change, medium may have changed)
Signed-off-by: Oliver Pinter
diff --git a/share/man/man4/u3g.4 b/share/man/man4/u3g.4
index 4df0b26..a2122cb 100644
--- a/share/man/man4/u3g.4
+++ b/share/man/man4/u3g.4
@@ -61,6 +61,8 @@ Option GT 3G, GT 3G Quad, etc.
.It
Vodafone Mobile Connect Card 3G
.It
+Vodafone Mobile Broadband K3772-Z
+.It
Qualcomm Inc. CDMA MSM
.It
Huawei B190, E180v, E220 ('')
diff --git a/sys/dev/usb/serial/u3g.c b/sys/dev/usb/serial/u3g.c
index e0b38bd..23b0f6c 100644
--- a/sys/dev/usb/serial/u3g.c
+++ b/sys/dev/usb/serial/u3g.c
@@ -422,6 +422,7 @@ static const STRUCT_USB_HOST_ID u3g_devs[] = {
U3G_DEV(QUALCOMMINC, SURFSTICK, 0),
U3G_DEV(QUALCOMMINC, E2002, 0),
U3G_DEV(QUALCOMMINC, E2003, 0),
+ U3G_DEV(QUALCOMMINC, K3772_Z, U3GINIT_SCSIEJECT),
U3G_DEV(QUALCOMMINC, MF626, 0),
U3G_DEV(QUALCOMMINC, MF628, 0),
U3G_DEV(QUALCOMMINC, MF633R, 0),
diff --git a/sys/dev/usb/usbdevs b/sys/dev/usb/usbdevs
index c770043..bc990c8 100644
--- a/sys/dev/usb/usbdevs
+++ b/sys/dev/usb/usbdevs
@@ -2744,6 +2744,7 @@ product QUALCOMMINC E0078 0x0078 3G modem
product QUALCOMMINC E0082 0x0082 3G modem
product QUALCOMMINC E0086 0x0086 3G modem
product QUALCOMMINC SURFSTICK 0x0117 1&1 Surf Stick
+product QUALCOMMINC K3772_Z 0x1179 3G modem
product QUALCOMMINC ZTE_STOR 0x2000 USB ZTE Storage
product QUALCOMMINC E2002 0x2002 3G modem
product QUALCOMMINC E2003 0x2003 3G modem
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On Friday, June 03, 2011 3:00:09 pm Willy Offermans wrote: > Hello John and FreeBSD friends, > > On Fri, Jun 03, 2011 at 09:48:26AM -0400, John Baldwin wrote: > > On Friday, June 03, 2011 8:34:54 am Willy Offermans wrote: > > > Dear John and FreeBSD friends, > > > > > > On Tue, May 31, 2011 at 11:01:23AM -0400, John Baldwin wrote: > > > > On Monday, May 30, 2011 5:25:14 am Willy Offermans wrote: > > > > > Hello John and FreeBSD friends, > > > > > > > > > > On Fri, May 27, 2011 at 10:43:34AM -0400, John Baldwin wrote: > > > > > > On Friday, May 27, 2011 10:38:02 am Willy Offermans wrote: > > > > > > > Dear John and FreeBSD friends, > > > > > > > > > > > > > > On Fri, May 27, 2011 at 08:05:56AM -0400, John Baldwin wrote: > > > > > > > > On Thursday, May 26, 2011 4:58:37 pm Mike Tancsa wrote: > > > > > > > > > On 5/26/2011 4:12 PM, John Baldwin wrote: > > > > > > > > > > > > > > > > > > > > Hmm, can you get 'pciconf -lb' output? > > > > > > > > > > > > > > > > > > > > Hmm, wow, I wonder how uart(4) works at all. It tries to > > reuse it's softc > > > > > > > > > > structure in uart_bus_attach() that was setup in > > uart_bus_probe(). Since > > > > > > > > it > > > > > > > > > > doesn't return 0 from its probe routine, that is forbidden. > > > > > > > > > > > > I guess it > > > > > > > > > > accidentally works because of the hack where we call > > DEVICE_PROBE() again > > > > > > > > > > to make sure the device description is correct. > > > > > > > > > > > > > > > > > > > > > > > > > > > I think this is a similar card. Had it laying about for a > > > > > > > > > while > > and > > > > > > > > > popped it in. cu -l to it, attaches, but I am not able to > > interact with it. > > > > > > > > > > > > > > > > > > none3@pci0:5:0:0: class=0x070002 card=0x20282205 > > chip=0x015213a8 > > > > > > > > > rev=0x02 hdr=0x00 > > > > > > > > > vendor = 'Exar Corp.' > > > > > > > > > device = 'XR17C/D152 Dual PCI UART' > > > > > > > > > class = simple comms > > > > > > > > > subclass = UART > > > > > > > > > bar [10] = type Memory, range 32, base 0xe895, size > > 1024, enabled > > > > > > > > > > > > > > > > > > > > > > > > > > > NetBSD supposedly has support for this card > > > > > > > > > > > > > > > > Oh, hmm, looks like the clock has an unusual multiplier. Does > > > > > > > > it > > work if you > > > > > > > > use 'cu -l -s 1200' to talk at 9600 for example? (In general > > > > > > > > use > > speed / 8 > > > > > > > > as the speed to '-s'.) > > > > > > > > > > > > > > > > Also, is your card a modem or a dual-port card? > > > > > > > > > > > > > > > > -- > > > > > > > > John Baldwin > > > > > > > > > > > > > > It is a modem. > > > > > > > > > > > > > > As suggested: > > > > > > > > > > > > > > kosmos# cu -l /dev/cuau0 -s 1200 > > > > > > > Stale lock on cuau0 PID=3642... overriding. > > > > > > > Connected > > > > > > > at&F > > > > > > > OK > > > > > > > atdt0045*** > > > > > > > NO DIALTONE > > > > > > > > > > > > Ok, try this updated patch. After this you should be able to use > > > > > > the > > correct > > > > > > speed: > > > > > > > > > > > > Index: uart_bus_pci.c > > > > > > =
Re: modem support MT9234ZPX-PCIE-NV
On Fri, Jun 03, 2011 at 09:00:09PM +0200, Willy Offermans wrote: > Hello John and FreeBSD friends, ... > > The latter patch seems to work: > > >From the boot.msg: > > > > puc0: mem 0xfbfffc00-0xfbff irq 16 at device 0.0 on pci6 > puc0: failed to enable port mapping! > puc0: [FILTER] > uart0: <16750 or compatible> on puc0 > uart0: [FILTER] > uart1: <16750 or compatible> on puc0 > uart1: [FILTER] > > > > As I already pointed out, I do not have a line connected to the modem yet. > This connection will hopefully be established tomorrow. After some rigorous > testing I will post a mail with the on stream results. On the other hand, > if someone knows some off stream testing procedures, then I'm happy to hear > about that. ... Many if not most modems supporting a Hayes-style command set include several loopback points (digital and analog) which you can turn on via specific command. Those commands are all non-standardized, so I can't tell you the commands for yours, but if you can look through a user manual or command reference you should be able to find them. Turning on loopback should allow you to do some basic verification tests, e.g. pipe a file of random binary values into it while concurrently reading it, and verify that you get the same contents. Personally, I'd try to get the digital loopback working first, then if that's OK try the analog loopback point. -- Clifton -- Clifton Royston -- clift...@iandicomputing.com / clift...@volcano.org President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
Hello John and FreeBSD friends,
On Fri, Jun 03, 2011 at 09:48:26AM -0400, John Baldwin wrote:
> On Friday, June 03, 2011 8:34:54 am Willy Offermans wrote:
> > Dear John and FreeBSD friends,
> >
> > On Tue, May 31, 2011 at 11:01:23AM -0400, John Baldwin wrote:
> > > On Monday, May 30, 2011 5:25:14 am Willy Offermans wrote:
> > > > Hello John and FreeBSD friends,
> > > >
> > > > On Fri, May 27, 2011 at 10:43:34AM -0400, John Baldwin wrote:
> > > > > On Friday, May 27, 2011 10:38:02 am Willy Offermans wrote:
> > > > > > Dear John and FreeBSD friends,
> > > > > >
> > > > > > On Fri, May 27, 2011 at 08:05:56AM -0400, John Baldwin wrote:
> > > > > > > On Thursday, May 26, 2011 4:58:37 pm Mike Tancsa wrote:
> > > > > > > > On 5/26/2011 4:12 PM, John Baldwin wrote:
> > > > > > > > >
> > > > > > > > > Hmm, can you get 'pciconf -lb' output?
> > > > > > > > >
> > > > > > > > > Hmm, wow, I wonder how uart(4) works at all. It tries to
> reuse it's softc
> > > > > > > > > structure in uart_bus_attach() that was setup in
> uart_bus_probe(). Since
> > > > > > > it
> > > > > > > > > doesn't return 0 from its probe routine, that is forbidden.
> I guess it
> > > > > > > > > accidentally works because of the hack where we call
> DEVICE_PROBE() again
> > > > > > > > > to make sure the device description is correct.
> > > > > > > >
> > > > > > > >
> > > > > > > > I think this is a similar card. Had it laying about for a
> > > > > > > > while
> and
> > > > > > > > popped it in. cu -l to it, attaches, but I am not able to
> interact with it.
> > > > > > > >
> > > > > > > > none3@pci0:5:0:0: class=0x070002 card=0x20282205
> chip=0x015213a8
> > > > > > > > rev=0x02 hdr=0x00
> > > > > > > > vendor = 'Exar Corp.'
> > > > > > > > device = 'XR17C/D152 Dual PCI UART'
> > > > > > > > class = simple comms
> > > > > > > > subclass = UART
> > > > > > > > bar [10] = type Memory, range 32, base 0xe895, size
> 1024, enabled
> > > > > > > >
> > > > > > > >
> > > > > > > > NetBSD supposedly has support for this card
> > > > > > >
> > > > > > > Oh, hmm, looks like the clock has an unusual multiplier. Does it
> work if you
> > > > > > > use 'cu -l -s 1200' to talk at 9600 for example? (In general use
> speed / 8
> > > > > > > as the speed to '-s'.)
> > > > > > >
> > > > > > > Also, is your card a modem or a dual-port card?
> > > > > > >
> > > > > > > --
> > > > > > > John Baldwin
> > > > > >
> > > > > > It is a modem.
> > > > > >
> > > > > > As suggested:
> > > > > >
> > > > > > kosmos# cu -l /dev/cuau0 -s 1200
> > > > > > Stale lock on cuau0 PID=3642... overriding.
> > > > > > Connected
> > > > > > at&F
> > > > > > OK
> > > > > > atdt0045***
> > > > > > NO DIALTONE
> > > > >
> > > > > Ok, try this updated patch. After this you should be able to use the
> correct
> > > > > speed:
> > > > >
> > > > > Index: uart_bus_pci.c
> > > > > ===
> > > > > --- uart_bus_pci.c(revision 85)
> > > > > +++ uart_bus_pci.c(working copy)
> > > > > @@ -110,6 +110,8 @@ static struct pci_id pci_ns8250_ids[] = {
> > > > > { 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus
> 16950 UART",
> > > > > 0x10, 16384000 },
> > > > > { 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem",
> 0x10 },
> > > > > +{ 0x13a8, 0x0152, 0x2205, 0x2026, "MultiTech MultiModem ZPX", 0x
Re: modem support MT9234ZPX-PCIE-NV
On Friday, June 03, 2011 8:34:54 am Willy Offermans wrote:
> Dear John and FreeBSD friends,
>
> On Tue, May 31, 2011 at 11:01:23AM -0400, John Baldwin wrote:
> > On Monday, May 30, 2011 5:25:14 am Willy Offermans wrote:
> > > Hello John and FreeBSD friends,
> > >
> > > On Fri, May 27, 2011 at 10:43:34AM -0400, John Baldwin wrote:
> > > > On Friday, May 27, 2011 10:38:02 am Willy Offermans wrote:
> > > > > Dear John and FreeBSD friends,
> > > > >
> > > > > On Fri, May 27, 2011 at 08:05:56AM -0400, John Baldwin wrote:
> > > > > > On Thursday, May 26, 2011 4:58:37 pm Mike Tancsa wrote:
> > > > > > > On 5/26/2011 4:12 PM, John Baldwin wrote:
> > > > > > > >
> > > > > > > > Hmm, can you get 'pciconf -lb' output?
> > > > > > > >
> > > > > > > > Hmm, wow, I wonder how uart(4) works at all. It tries to
reuse it's softc
> > > > > > > > structure in uart_bus_attach() that was setup in
uart_bus_probe(). Since
> > > > > > it
> > > > > > > > doesn't return 0 from its probe routine, that is forbidden.
I guess it
> > > > > > > > accidentally works because of the hack where we call
DEVICE_PROBE() again
> > > > > > > > to make sure the device description is correct.
> > > > > > >
> > > > > > >
> > > > > > > I think this is a similar card. Had it laying about for a while
and
> > > > > > > popped it in. cu -l to it, attaches, but I am not able to
interact with it.
> > > > > > >
> > > > > > > none3@pci0:5:0:0: class=0x070002 card=0x20282205
chip=0x015213a8
> > > > > > > rev=0x02 hdr=0x00
> > > > > > > vendor = 'Exar Corp.'
> > > > > > > device = 'XR17C/D152 Dual PCI UART'
> > > > > > > class = simple comms
> > > > > > > subclass = UART
> > > > > > > bar [10] = type Memory, range 32, base 0xe895, size
1024, enabled
> > > > > > >
> > > > > > >
> > > > > > > NetBSD supposedly has support for this card
> > > > > >
> > > > > > Oh, hmm, looks like the clock has an unusual multiplier. Does it
work if you
> > > > > > use 'cu -l -s 1200' to talk at 9600 for example? (In general use
speed / 8
> > > > > > as the speed to '-s'.)
> > > > > >
> > > > > > Also, is your card a modem or a dual-port card?
> > > > > >
> > > > > > --
> > > > > > John Baldwin
> > > > >
> > > > > It is a modem.
> > > > >
> > > > > As suggested:
> > > > >
> > > > > kosmos# cu -l /dev/cuau0 -s 1200
> > > > > Stale lock on cuau0 PID=3642... overriding.
> > > > > Connected
> > > > > at&F
> > > > > OK
> > > > > atdt0045***
> > > > > NO DIALTONE
> > > >
> > > > Ok, try this updated patch. After this you should be able to use the
correct
> > > > speed:
> > > >
> > > > Index: uart_bus_pci.c
> > > > ===
> > > > --- uart_bus_pci.c (revision 85)
> > > > +++ uart_bus_pci.c (working copy)
> > > > @@ -110,6 +110,8 @@ static struct pci_id pci_ns8250_ids[] = {
> > > > { 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus
16950 UART",
> > > > 0x10, 16384000 },
> > > > { 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem",
0x10 },
> > > > +{ 0x13a8, 0x0152, 0x2205, 0x2026, "MultiTech MultiModem ZPX", 0x10,
> > > > + 8 * DEFAULT_RCLK },
> > > > { 0x9710, 0x9820, 0x1000, 1, "NetMos NM9820 Serial Port", 0x10 },
> > > > { 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
> > > > { 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10
},
> > > >
> > > > --
> > > > John Baldwin
> > >
> > > The structure you have provided in your magic line would also need
> > > some explanati
Re: modem support MT9234ZPX-PCIE-NV
Dear John and FreeBSD friends,
On Tue, May 31, 2011 at 11:01:23AM -0400, John Baldwin wrote:
> On Monday, May 30, 2011 5:25:14 am Willy Offermans wrote:
> > Hello John and FreeBSD friends,
> >
> > On Fri, May 27, 2011 at 10:43:34AM -0400, John Baldwin wrote:
> > > On Friday, May 27, 2011 10:38:02 am Willy Offermans wrote:
> > > > Dear John and FreeBSD friends,
> > > >
> > > > On Fri, May 27, 2011 at 08:05:56AM -0400, John Baldwin wrote:
> > > > > On Thursday, May 26, 2011 4:58:37 pm Mike Tancsa wrote:
> > > > > > On 5/26/2011 4:12 PM, John Baldwin wrote:
> > > > > > >
> > > > > > > Hmm, can you get 'pciconf -lb' output?
> > > > > > >
> > > > > > > Hmm, wow, I wonder how uart(4) works at all. It tries to reuse
> > > > > > > it's softc
> > > > > > > structure in uart_bus_attach() that was setup in
> > > > > > > uart_bus_probe(). Since
> > > > > it
> > > > > > > doesn't return 0 from its probe routine, that is forbidden. I
> > > > > > > guess it
> > > > > > > accidentally works because of the hack where we call
> > > > > > > DEVICE_PROBE() again
> > > > > > > to make sure the device description is correct.
> > > > > >
> > > > > >
> > > > > > I think this is a similar card. Had it laying about for a while and
> > > > > > popped it in. cu -l to it, attaches, but I am not able to interact
> > > > > > with it.
> > > > > >
> > > > > > none3@pci0:5:0:0: class=0x070002 card=0x20282205
> > > > > > chip=0x015213a8
> > > > > > rev=0x02 hdr=0x00
> > > > > > vendor = 'Exar Corp.'
> > > > > > device = 'XR17C/D152 Dual PCI UART'
> > > > > > class = simple comms
> > > > > > subclass = UART
> > > > > > bar [10] = type Memory, range 32, base 0xe895, size 1024,
> > > > > > enabled
> > > > > >
> > > > > >
> > > > > > NetBSD supposedly has support for this card
> > > > >
> > > > > Oh, hmm, looks like the clock has an unusual multiplier. Does it
> > > > > work if you
> > > > > use 'cu -l -s 1200' to talk at 9600 for example? (In general use
> > > > > speed / 8
> > > > > as the speed to '-s'.)
> > > > >
> > > > > Also, is your card a modem or a dual-port card?
> > > > >
> > > > > --
> > > > > John Baldwin
> > > >
> > > > It is a modem.
> > > >
> > > > As suggested:
> > > >
> > > > kosmos# cu -l /dev/cuau0 -s 1200
> > > > Stale lock on cuau0 PID=3642... overriding.
> > > > Connected
> > > > at&F
> > > > OK
> > > > atdt0045***
> > > > NO DIALTONE
> > >
> > > Ok, try this updated patch. After this you should be able to use the
> > > correct
> > > speed:
> > >
> > > Index: uart_bus_pci.c
> > > ===
> > > --- uart_bus_pci.c(revision 85)
> > > +++ uart_bus_pci.c(working copy)
> > > @@ -110,6 +110,8 @@ static struct pci_id pci_ns8250_ids[] = {
> > > { 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus 16950
> > > UART",
> > > 0x10, 16384000 },
> > > { 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem", 0x10
> > > },
> > > +{ 0x13a8, 0x0152, 0x2205, 0x2026, "MultiTech MultiModem ZPX", 0x10,
> > > + 8 * DEFAULT_RCLK },
> > > { 0x9710, 0x9820, 0x1000, 1, "NetMos NM9820 Serial Port", 0x10 },
> > > { 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
> > > { 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10 },
> > >
> > > --
> > > John Baldwin
> >
> > The structure you have provided in your magic line would also need
> > some explanation. The data concerns the description of the chip and the
> > card I guess and can be gained by `pciconf -lv`
> >
> > uart0
Re: modem support MT9234ZPX-PCIE-NV
On Monday, May 30, 2011 5:25:14 am Willy Offermans wrote:
> Hello John and FreeBSD friends,
>
> On Fri, May 27, 2011 at 10:43:34AM -0400, John Baldwin wrote:
> > On Friday, May 27, 2011 10:38:02 am Willy Offermans wrote:
> > > Dear John and FreeBSD friends,
> > >
> > > On Fri, May 27, 2011 at 08:05:56AM -0400, John Baldwin wrote:
> > > > On Thursday, May 26, 2011 4:58:37 pm Mike Tancsa wrote:
> > > > > On 5/26/2011 4:12 PM, John Baldwin wrote:
> > > > > >
> > > > > > Hmm, can you get 'pciconf -lb' output?
> > > > > >
> > > > > > Hmm, wow, I wonder how uart(4) works at all. It tries to reuse
> > > > > > it's softc
> > > > > > structure in uart_bus_attach() that was setup in uart_bus_probe().
> > > > > > Since
> > > > it
> > > > > > doesn't return 0 from its probe routine, that is forbidden. I
> > > > > > guess it
> > > > > > accidentally works because of the hack where we call DEVICE_PROBE()
> > > > > > again
> > > > > > to make sure the device description is correct.
> > > > >
> > > > >
> > > > > I think this is a similar card. Had it laying about for a while and
> > > > > popped it in. cu -l to it, attaches, but I am not able to interact
> > > > > with it.
> > > > >
> > > > > none3@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8
> > > > > rev=0x02 hdr=0x00
> > > > > vendor = 'Exar Corp.'
> > > > > device = 'XR17C/D152 Dual PCI UART'
> > > > > class = simple comms
> > > > > subclass = UART
> > > > > bar [10] = type Memory, range 32, base 0xe895, size 1024,
> > > > > enabled
> > > > >
> > > > >
> > > > > NetBSD supposedly has support for this card
> > > >
> > > > Oh, hmm, looks like the clock has an unusual multiplier. Does it work
> > > > if you
> > > > use 'cu -l -s 1200' to talk at 9600 for example? (In general use speed
> > > > / 8
> > > > as the speed to '-s'.)
> > > >
> > > > Also, is your card a modem or a dual-port card?
> > > >
> > > > --
> > > > John Baldwin
> > >
> > > It is a modem.
> > >
> > > As suggested:
> > >
> > > kosmos# cu -l /dev/cuau0 -s 1200
> > > Stale lock on cuau0 PID=3642... overriding.
> > > Connected
> > > at&F
> > > OK
> > > atdt0045***
> > > NO DIALTONE
> >
> > Ok, try this updated patch. After this you should be able to use the
> > correct
> > speed:
> >
> > Index: uart_bus_pci.c
> > ===
> > --- uart_bus_pci.c (revision 85)
> > +++ uart_bus_pci.c (working copy)
> > @@ -110,6 +110,8 @@ static struct pci_id pci_ns8250_ids[] = {
> > { 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus 16950
> > UART",
> > 0x10, 16384000 },
> > { 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem", 0x10 },
> > +{ 0x13a8, 0x0152, 0x2205, 0x2026, "MultiTech MultiModem ZPX", 0x10,
> > + 8 * DEFAULT_RCLK },
> > { 0x9710, 0x9820, 0x1000, 1, "NetMos NM9820 Serial Port", 0x10 },
> > { 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
> > { 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10 },
> >
> > --
> > John Baldwin
>
> The structure you have provided in your magic line would also need
> some explanation. The data concerns the description of the chip and the
> card I guess and can be gained by `pciconf -lv`
>
> uart0@pci0:6:0:0: class=0x070002 card=0x20262205 chip=0x015213a8 rev=0x02
> hdr=0x00
> vendor = 'Exar Corp.'
> device = 'XR17C/D152 Dual PCI UART'
> class = simple comms
> subclass = UART
>
>
> A more detailed explanation would not harm. The data 0x10 and
> 8 * DEFAULT_RCLK are still totally miraculous to me.
0x10 is the resource id for the first PCI BAR (rids for PCI device resources
use the offset in PCI config space of the associated BAR). It would perhaps
be more obvious if uart(4) and puc(4) used PCIR_BAR(0) rather than 0x10.
Bumping the clock by a multiple of 8 was based on looking at the change in
NetBSD that Mike Tancsa pointed to and that you verified by noting that
'cu -s 1200' connected at 9600 (9600 / 1200 == 8).
One question though, would you be able to test the patch for puc(4) that I
sent to Mike Tancsa to see if your modem works with puc(4)? The puc(4)
patch is more general and if it works fine for your modem I'd rather just
commit that.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
Hello John and FreeBSD friends,
On Fri, May 27, 2011 at 10:43:34AM -0400, John Baldwin wrote:
> On Friday, May 27, 2011 10:38:02 am Willy Offermans wrote:
> > Dear John and FreeBSD friends,
> >
> > On Fri, May 27, 2011 at 08:05:56AM -0400, John Baldwin wrote:
> > > On Thursday, May 26, 2011 4:58:37 pm Mike Tancsa wrote:
> > > > On 5/26/2011 4:12 PM, John Baldwin wrote:
> > > > >
> > > > > Hmm, can you get 'pciconf -lb' output?
> > > > >
> > > > > Hmm, wow, I wonder how uart(4) works at all. It tries to reuse it's
> > > > > softc
> > > > > structure in uart_bus_attach() that was setup in uart_bus_probe().
> > > > > Since
> > > it
> > > > > doesn't return 0 from its probe routine, that is forbidden. I guess
> > > > > it
> > > > > accidentally works because of the hack where we call DEVICE_PROBE()
> > > > > again
> > > > > to make sure the device description is correct.
> > > >
> > > >
> > > > I think this is a similar card. Had it laying about for a while and
> > > > popped it in. cu -l to it, attaches, but I am not able to interact
> > > > with it.
> > > >
> > > > none3@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8
> > > > rev=0x02 hdr=0x00
> > > > vendor = 'Exar Corp.'
> > > > device = 'XR17C/D152 Dual PCI UART'
> > > > class = simple comms
> > > > subclass = UART
> > > > bar [10] = type Memory, range 32, base 0xe895, size 1024,
> > > > enabled
> > > >
> > > >
> > > > NetBSD supposedly has support for this card
> > >
> > > Oh, hmm, looks like the clock has an unusual multiplier. Does it work if
> > > you
> > > use 'cu -l -s 1200' to talk at 9600 for example? (In general use speed /
> > > 8
> > > as the speed to '-s'.)
> > >
> > > Also, is your card a modem or a dual-port card?
> > >
> > > --
> > > John Baldwin
> >
> > It is a modem.
> >
> > As suggested:
> >
> > kosmos# cu -l /dev/cuau0 -s 1200
> > Stale lock on cuau0 PID=3642... overriding.
> > Connected
> > at&F
> > OK
> > atdt0045***
> > NO DIALTONE
>
> Ok, try this updated patch. After this you should be able to use the correct
> speed:
>
> Index: uart_bus_pci.c
> ===
> --- uart_bus_pci.c(revision 85)
> +++ uart_bus_pci.c(working copy)
> @@ -110,6 +110,8 @@ static struct pci_id pci_ns8250_ids[] = {
> { 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus 16950
> UART",
> 0x10, 16384000 },
> { 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem", 0x10 },
> +{ 0x13a8, 0x0152, 0x2205, 0x2026, "MultiTech MultiModem ZPX", 0x10,
> + 8 * DEFAULT_RCLK },
> { 0x9710, 0x9820, 0x1000, 1, "NetMos NM9820 Serial Port", 0x10 },
> { 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
> { 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10 },
>
> --
> John Baldwin
Hello John,
After inserting the magic line into uart_bus_pci.c, things start to be
really good. Minicom is now able to communicate with the device in a proper
way. Hereafter you can see some response from the modem.
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
at
OK
ati
Agere OCM V.92 MT9234ZPX-PCIE Internal Data/Fax/Voice Modem Version 1.02d
OK
at&F
OK
atdt0,0455444944
NO DIALTONE
Of course there is no dialtone, since the telephone line is not connected
yet. I will ask the people on the remote site to connect the line as soon
as possible.
The status of HylaFAX is also as expected:
kosmos# faxstat
HylaFAX scheduler on localhost: Running
Modem cuau0 (+31455667077): Running and idle
As soon as the line is established and as soon as I have established a
proper setup with HylaFAX and performed some tests, I will report about the
results again.
I would like to thank you for your support so far. It was of great help and
without it I would certainly not have succeed. However, since it does not
seem to be so difficult, it would be wise to put the setup into
http://www.freebsd.org/doc/handbook/serial.html. Other users would benefit
from it. The structure you have prov
Re: modem support MT9234ZPX-PCIE-NV
On 5/27/2011 4:22 PM, John Baldwin wrote: > On Friday, May 27, 2011 3:38:04 pm Mike Tancsa wrote: >> On 5/27/2011 3:33 PM, John Baldwin wrote: >>> >>> Actually, can you just try this: >>> >>> Index: pucdata.c >> >> Hi, >> Patch applies, but it doesnt compile on RELENG_8 > > Ugh, looks like the offset can't handle 0x200, try this instead: > > Index: pucdata.c > === Thanks! that applies cleanly and I see both ports now. However, I still cannot interact with the modem. Let me fire up LINUX 0(ich10)# patch < p Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Index: pucdata.c |=== |--- pucdata.c (revision 222364) |+++ pucdata.c (working copy) -- Patching file pucdata.c using Plan A... Hunk #1 succeeded at 48. Hunk #2 succeeded at 547 (offset -1 lines). Hunk #3 succeeded at 953 (offset -75 lines). done 0(ich10)# puc0: mem 0xe895-0xe89503ff irq 21 at device 0.0 on pci5 puc0: [FILTER] uart2: <16750 or compatible> on puc0 uart2: [FILTER] uart3: <16750 or compatible> on puc0 uart3: [FILTER] -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On Friday, May 27, 2011 3:38:04 pm Mike Tancsa wrote:
> On 5/27/2011 3:33 PM, John Baldwin wrote:
> >
> > Actually, can you just try this:
> >
> > Index: pucdata.c
>
> Hi,
> Patch applies, but it doesnt compile on RELENG_8
Ugh, looks like the offset can't handle 0x200, try this instead:
Index: pucdata.c
===
--- pucdata.c (revision 222364)
+++ pucdata.c (working copy)
@@ -48,8 +48,8 @@ __FBSDID("$FreeBSD$");
#include
static puc_config_f puc_config_amc;
-static puc_config_f puc_config_cronyx;
static puc_config_f puc_config_diva;
+static puc_config_f puc_config_exar;
static puc_config_f puc_config_icbook;
static puc_config_f puc_config_quatech;
static puc_config_f puc_config_syba;
@@ -548,11 +548,25 @@ const struct puc_cfg puc_pci_devices[] = {
PUC_PORT_8S, 0x18, 0, 8,
},
+ { 0x13a8, 0x0152, 0x, 0,
+ "Exar XR17C/D152",
+ DEFAULT_RCLK * 8,
+ PUC_PORT_2S, 0x10, 0, -1,
+ .config_function = puc_config_exar
+ },
+
+ { 0x13a8, 0x0154, 0x, 0,
+ "Exar XR17C154",
+ DEFAULT_RCLK * 8,
+ PUC_PORT_4S, 0x10, 0, -1,
+ .config_function = puc_config_exar
+ },
+
{ 0x13a8, 0x0158, 0x, 0,
- "Cronyx Omega2-PCI",
+ "Exar XR17C158",
DEFAULT_RCLK * 8,
PUC_PORT_8S, 0x10, 0, -1,
- .config_function = puc_config_cronyx
+ .config_function = puc_config_exar
},
{ 0x13a8, 0x0258, 0x, 0,
@@ -1014,28 +1028,28 @@ puc_config_amc(struct puc_softc *sc, enum puc_cfg_
}
static int
-puc_config_cronyx(struct puc_softc *sc, enum puc_cfg_cmd cmd, int port,
+puc_config_diva(struct puc_softc *sc, enum puc_cfg_cmd cmd, int port,
intptr_t *res)
{
+ const struct puc_cfg *cfg = sc->sc_cfg;
+
if (cmd == PUC_CFG_GET_OFS) {
- *res = port * 0x200;
+ if (cfg->subdevice == 0x1282) /* Everest SP */
+ port <<= 1;
+ else if (cfg->subdevice == 0x104b) /* Maestro SP2 */
+ port = (port == 3) ? 4 : port;
+ *res = port * 8 + ((port > 2) ? 0x18 : 0);
return (0);
}
return (ENXIO);
}
static int
-puc_config_diva(struct puc_softc *sc, enum puc_cfg_cmd cmd, int port,
+puc_config_exar(struct puc_softc *sc, enum puc_cfg_cmd cmd, int port,
intptr_t *res)
{
- const struct puc_cfg *cfg = sc->sc_cfg;
-
if (cmd == PUC_CFG_GET_OFS) {
- if (cfg->subdevice == 0x1282) /* Everest SP */
- port <<= 1;
- else if (cfg->subdevice == 0x104b) /* Maestro SP2 */
- port = (port == 3) ? 4 : port;
- *res = port * 8 + ((port > 2) ? 0x18 : 0);
+ *res = port * 0x200;
return (0);
}
return (ENXIO);
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On 5/27/2011 3:33 PM, John Baldwin wrote: > > Actually, can you just try this: > > Index: pucdata.c Hi, Patch applies, but it doesnt compile on RELENG_8 patch < p Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Index: pucdata.c |=== |--- pucdata.c (revision 222364) |+++ pucdata.c (working copy) -- Patching file pucdata.c using Plan A... Hunk #1 succeeded at 48. Hunk #2 succeeded at 546 (offset -1 lines). Hunk #3 succeeded at 949 (offset -75 lines). done ===> puc (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/ipsec/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -I/usr/obj/usr/src/sys/ipsec -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /usr/src/sys/modules/puc/../../dev/puc/pucdata.c cc1: warnings being treated as errors /usr/src/sys/modules/puc/../../dev/puc/pucdata.c:552: warning: overflow in implicit constant conversion /usr/src/sys/modules/puc/../../dev/puc/pucdata.c:558: warning: overflow in implicit constant conversion /usr/src/sys/modules/puc/../../dev/puc/pucdata.c:564: warning: overflow in implicit constant conversion *** Error code 1 Stop in /usr/src/sys/modules/puc. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/ipsec. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On Friday, May 27, 2011 1:54:54 pm Mike Tancsa wrote:
> On 5/27/2011 12:00 PM, John Baldwin wrote:
> >>
> >> uart2@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8
> >> rev=0x02 hdr=0x00
> >> vendor = 'Exar Corp.'
> >> device = 'XR17C/D152 Dual PCI UART'
> >> class = simple comms
> >> subclass = UART
> >
> > Possibly. Did you try adding it via puc instead?
>
> Yes, same result. But I am not sure what values to plugin for some of
> the options.
>
> I tried this is uart
>
> 1(ich10)# diff -u uart_bus_pci.c.orig uart_bus_pci.c
> --- uart_bus_pci.c.orig 2011-05-24 17:10:21.0 -0400
> +++ uart_bus_pci.c 2011-05-27 10:49:05.0 -0400
> @@ -110,6 +110,8 @@
> { 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus
> 16950 UART",
> 0x10, 16384000 },
> { 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem", 0x10 },
> +{ 0x13a8, 0x0152, 0x2205, 0x2028, "MultiTech MultiModem ZPX", 0x10,
> + 8 * DEFAULT_RCLK },
> { 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
> { 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10 },
> { 0x9710, 0x9901, 0xa000, 0x1000,
> 1(ich10)#
>
> Then I removed the entry from uart and added the following for pucdata.c
>
>
> { 0x13a8, 0x0152, 0x, 0,
> "Exar Multitech",
> DEFAULT_RCLK * 8,
> PUC_PORT_2S, 0x10, 0, -1,
> },
>
> But it does not seem to want to attach ?
Actually, can you just try this:
Index: pucdata.c
===
--- pucdata.c (revision 222364)
+++ pucdata.c (working copy)
@@ -48,7 +48,6 @@ __FBSDID("$FreeBSD$");
#include
static puc_config_f puc_config_amc;
-static puc_config_f puc_config_cronyx;
static puc_config_f puc_config_diva;
static puc_config_f puc_config_icbook;
static puc_config_f puc_config_quatech;
@@ -548,11 +547,22 @@ const struct puc_cfg puc_pci_devices[] = {
PUC_PORT_8S, 0x18, 0, 8,
},
+ { 0x13a8, 0x0152, 0x, 0,
+ "Exar XR17C/D152",
+ DEFAULT_RCLK * 8,
+ PUC_PORT_2S, 0x10, 0, 0x200,
+ },
+
+ { 0x13a8, 0x0154, 0x, 0,
+ "Exar XR17C154",
+ DEFAULT_RCLK * 8,
+ PUC_PORT_4S, 0x10, 0, 0x200,
+ },
+
{ 0x13a8, 0x0158, 0x, 0,
- "Cronyx Omega2-PCI",
+ "Exar XR17C158",
DEFAULT_RCLK * 8,
- PUC_PORT_8S, 0x10, 0, -1,
- .config_function = puc_config_cronyx
+ PUC_PORT_8S, 0x10, 0, 0x200,
},
{ 0x13a8, 0x0258, 0x, 0,
@@ -1014,17 +1024,6 @@ puc_config_amc(struct puc_softc *sc, enum puc_cfg_
}
static int
-puc_config_cronyx(struct puc_softc *sc, enum puc_cfg_cmd cmd, int port,
-intptr_t *res)
-{
- if (cmd == PUC_CFG_GET_OFS) {
- *res = port * 0x200;
- return (0);
- }
- return (ENXIO);
-}
-
-static int
puc_config_diva(struct puc_softc *sc, enum puc_cfg_cmd cmd, int port,
intptr_t *res)
{
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On Friday, May 27, 2011 1:54:54 pm Mike Tancsa wrote:
> On 5/27/2011 12:00 PM, John Baldwin wrote:
> >>
> >> uart2@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8
> >> rev=0x02 hdr=0x00
> >> vendor = 'Exar Corp.'
> >> device = 'XR17C/D152 Dual PCI UART'
> >> class = simple comms
> >> subclass = UART
> >
> > Possibly. Did you try adding it via puc instead?
>
> Yes, same result. But I am not sure what values to plugin for some of
> the options.
>
> I tried this is uart
>
> 1(ich10)# diff -u uart_bus_pci.c.orig uart_bus_pci.c
> --- uart_bus_pci.c.orig 2011-05-24 17:10:21.0 -0400
> +++ uart_bus_pci.c 2011-05-27 10:49:05.0 -0400
> @@ -110,6 +110,8 @@
> { 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus
> 16950 UART",
> 0x10, 16384000 },
> { 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem", 0x10 },
> +{ 0x13a8, 0x0152, 0x2205, 0x2028, "MultiTech MultiModem ZPX", 0x10,
> + 8 * DEFAULT_RCLK },
> { 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
> { 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10 },
> { 0x9710, 0x9901, 0xa000, 0x1000,
> 1(ich10)#
>
> Then I removed the entry from uart and added the following for pucdata.c
>
>
> { 0x13a8, 0x0152, 0x, 0,
> "Exar Multitech",
> DEFAULT_RCLK * 8,
> PUC_PORT_2S, 0x10, 0, -1,
> },
Use '0x200' rather than -1.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On 5/27/2011 12:00 PM, John Baldwin wrote:
>>
>> uart2@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8
>> rev=0x02 hdr=0x00
>> vendor = 'Exar Corp.'
>> device = 'XR17C/D152 Dual PCI UART'
>> class = simple comms
>> subclass = UART
>
> Possibly. Did you try adding it via puc instead?
Yes, same result. But I am not sure what values to plugin for some of
the options.
I tried this is uart
1(ich10)# diff -u uart_bus_pci.c.orig uart_bus_pci.c
--- uart_bus_pci.c.orig 2011-05-24 17:10:21.0 -0400
+++ uart_bus_pci.c 2011-05-27 10:49:05.0 -0400
@@ -110,6 +110,8 @@
{ 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus
16950 UART",
0x10, 16384000 },
{ 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem", 0x10 },
+{ 0x13a8, 0x0152, 0x2205, 0x2028, "MultiTech MultiModem ZPX", 0x10,
+ 8 * DEFAULT_RCLK },
{ 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
{ 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10 },
{ 0x9710, 0x9901, 0xa000, 0x1000,
1(ich10)#
Then I removed the entry from uart and added the following for pucdata.c
{ 0x13a8, 0x0152, 0x, 0,
"Exar Multitech",
DEFAULT_RCLK * 8,
PUC_PORT_2S, 0x10, 0, -1,
},
But it does not seem to want to attach ?
---Mike
--
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada http://www.tancsa.com/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On Friday, May 27, 2011 10:43:23 am Mike Tancsa wrote: > On 5/27/2011 8:05 AM, John Baldwin wrote: > > > > > Oh, hmm, looks like the clock has an unusual multiplier. Does it work if you > > use 'cu -l -s 1200' to talk at 9600 for example? (In general use speed / 8 > > as the speed to '-s'.) > > > > Also, is your card a modem or a dual-port card? > > If I add in the device IDs, I am not able to talk to it at any speed. > However, the port that is exposed, might just not be echoing back chars > and the second port which is not showing up, might be the "control port" ? > > uart2@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8 > rev=0x02 hdr=0x00 > vendor = 'Exar Corp.' > device = 'XR17C/D152 Dual PCI UART' > class = simple comms > subclass = UART Possibly. Did you try adding it via puc instead? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On 5/27/2011 8:05 AM, John Baldwin wrote: > > Oh, hmm, looks like the clock has an unusual multiplier. Does it work if you > use 'cu -l -s 1200' to talk at 9600 for example? (In general use speed / 8 > as the speed to '-s'.) > > Also, is your card a modem or a dual-port card? If I add in the device IDs, I am not able to talk to it at any speed. However, the port that is exposed, might just not be echoing back chars and the second port which is not showing up, might be the "control port" ? uart2@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8 rev=0x02 hdr=0x00 vendor = 'Exar Corp.' device = 'XR17C/D152 Dual PCI UART' class = simple comms subclass = UART -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On Friday, May 27, 2011 10:38:02 am Willy Offermans wrote:
> Dear John and FreeBSD friends,
>
> On Fri, May 27, 2011 at 08:05:56AM -0400, John Baldwin wrote:
> > On Thursday, May 26, 2011 4:58:37 pm Mike Tancsa wrote:
> > > On 5/26/2011 4:12 PM, John Baldwin wrote:
> > > >
> > > > Hmm, can you get 'pciconf -lb' output?
> > > >
> > > > Hmm, wow, I wonder how uart(4) works at all. It tries to reuse it's
> > > > softc
> > > > structure in uart_bus_attach() that was setup in uart_bus_probe().
> > > > Since
> > it
> > > > doesn't return 0 from its probe routine, that is forbidden. I guess it
> > > > accidentally works because of the hack where we call DEVICE_PROBE()
> > > > again
> > > > to make sure the device description is correct.
> > >
> > >
> > > I think this is a similar card. Had it laying about for a while and
> > > popped it in. cu -l to it, attaches, but I am not able to interact with
> > > it.
> > >
> > > none3@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8
> > > rev=0x02 hdr=0x00
> > > vendor = 'Exar Corp.'
> > > device = 'XR17C/D152 Dual PCI UART'
> > > class = simple comms
> > > subclass = UART
> > > bar [10] = type Memory, range 32, base 0xe895, size 1024,
> > > enabled
> > >
> > >
> > > NetBSD supposedly has support for this card
> >
> > Oh, hmm, looks like the clock has an unusual multiplier. Does it work if
> > you
> > use 'cu -l -s 1200' to talk at 9600 for example? (In general use speed / 8
> > as the speed to '-s'.)
> >
> > Also, is your card a modem or a dual-port card?
> >
> > --
> > John Baldwin
>
> It is a modem.
>
> As suggested:
>
> kosmos# cu -l /dev/cuau0 -s 1200
> Stale lock on cuau0 PID=3642... overriding.
> Connected
> at&F
> OK
> atdt0045***
> NO DIALTONE
Ok, try this updated patch. After this you should be able to use the correct
speed:
Index: uart_bus_pci.c
===
--- uart_bus_pci.c (revision 85)
+++ uart_bus_pci.c (working copy)
@@ -110,6 +110,8 @@ static struct pci_id pci_ns8250_ids[] = {
{ 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus 16950 UART",
0x10, 16384000 },
{ 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem", 0x10 },
+{ 0x13a8, 0x0152, 0x2205, 0x2026, "MultiTech MultiModem ZPX", 0x10,
+ 8 * DEFAULT_RCLK },
{ 0x9710, 0x9820, 0x1000, 1, "NetMos NM9820 Serial Port", 0x10 },
{ 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
{ 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10 },
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
Dear John and FreeBSD friends, On Fri, May 27, 2011 at 08:05:56AM -0400, John Baldwin wrote: > On Thursday, May 26, 2011 4:58:37 pm Mike Tancsa wrote: > > On 5/26/2011 4:12 PM, John Baldwin wrote: > > > > > > Hmm, can you get 'pciconf -lb' output? > > > > > > Hmm, wow, I wonder how uart(4) works at all. It tries to reuse it's softc > > > structure in uart_bus_attach() that was setup in uart_bus_probe(). Since > it > > > doesn't return 0 from its probe routine, that is forbidden. I guess it > > > accidentally works because of the hack where we call DEVICE_PROBE() again > > > to make sure the device description is correct. > > > > > > I think this is a similar card. Had it laying about for a while and > > popped it in. cu -l to it, attaches, but I am not able to interact with it. > > > > none3@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8 > > rev=0x02 hdr=0x00 > > vendor = 'Exar Corp.' > > device = 'XR17C/D152 Dual PCI UART' > > class = simple comms > > subclass = UART > > bar [10] = type Memory, range 32, base 0xe895, size 1024, enabled > > > > > > NetBSD supposedly has support for this card > > Oh, hmm, looks like the clock has an unusual multiplier. Does it work if you > use 'cu -l -s 1200' to talk at 9600 for example? (In general use speed / 8 > as the speed to '-s'.) > > Also, is your card a modem or a dual-port card? > > -- > John Baldwin It is a modem. As suggested: kosmos# cu -l /dev/cuau0 -s 1200 Stale lock on cuau0 PID=3642... overriding. Connected at&F OK atdt0045*** NO DIALTONE The last message can be explained. There is no line connected yet. But this looks very promising again. What do you exactly mean with ``Oh, hmm, looks like the clock has an unusual multiplier.'' What kind of multiplier are you talking about? How to proceed? B.t.w. cu looks like a nice tool. I was not aware of its existence. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On 5/27/2011 8:05 AM, John Baldwin wrote: > > Oh, hmm, looks like the clock has an unusual multiplier. Does it work if you > use 'cu -l -s 1200' to talk at 9600 for example? (In general use speed / 8 > as the speed to '-s'.) > > Also, is your card a modem or a dual-port card? Its a 3G modem. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On Thursday, May 26, 2011 4:58:37 pm Mike Tancsa wrote: > On 5/26/2011 4:12 PM, John Baldwin wrote: > > > > Hmm, can you get 'pciconf -lb' output? > > > > Hmm, wow, I wonder how uart(4) works at all. It tries to reuse it's softc > > structure in uart_bus_attach() that was setup in uart_bus_probe(). Since it > > doesn't return 0 from its probe routine, that is forbidden. I guess it > > accidentally works because of the hack where we call DEVICE_PROBE() again > > to make sure the device description is correct. > > > I think this is a similar card. Had it laying about for a while and > popped it in. cu -l to it, attaches, but I am not able to interact with it. > > none3@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8 > rev=0x02 hdr=0x00 > vendor = 'Exar Corp.' > device = 'XR17C/D152 Dual PCI UART' > class = simple comms > subclass = UART > bar [10] = type Memory, range 32, base 0xe895, size 1024, enabled > > > NetBSD supposedly has support for this card Oh, hmm, looks like the clock has an unusual multiplier. Does it work if you use 'cu -l -s 1200' to talk at 9600 for example? (In general use speed / 8 as the speed to '-s'.) Also, is your card a modem or a dual-port card? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On Thu, May 26, 2011 at 04:58:37PM -0400, Mike Tancsa wrote:
> On 5/26/2011 4:12 PM, John Baldwin wrote:
> >
> > Hmm, can you get 'pciconf -lb' output?
> >
> > Hmm, wow, I wonder how uart(4) works at all. It tries to reuse it's softc
> > structure in uart_bus_attach() that was setup in uart_bus_probe(). Since it
> > doesn't return 0 from its probe routine, that is forbidden. I guess it
> > accidentally works because of the hack where we call DEVICE_PROBE() again
> > to make sure the device description is correct.
>
>
> I think this is a similar card. Had it laying about for a while and
> popped it in. cu -l to it, attaches, but I am not able to interact with it.
>
> none3@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8
> rev=0x02 hdr=0x00
> vendor = 'Exar Corp.'
> device = 'XR17C/D152 Dual PCI UART'
> class = simple comms
> subclass = UART
> bar [10] = type Memory, range 32, base 0xe895, size 1024, enabled
>
>
> NetBSD supposedly has support for this card
>
> http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/pci/pucdata.c.diff?r1=1.43&r2=1.44
>
>
> ---Mike
>
> --
> ---
> Mike Tancsa, tel +1 519 651 3400
> Sentex Communications, m...@sentex.net
> Providing Internet services since 1994 www.sentex.net
> Cambridge, Ontario Canada http://www.tancsa.com/
I guess you refer to this part:
+ { "EXAR XR17D152",
+ { 0x13a8, 0x0152, 0, 0 },
+ { 0x, 0x, 0, 0 },
+ {
+ { PUC_PORT_TYPE_COM, 0x10, 0x, COM_FREQ * 8 },
+ { PUC_PORT_TYPE_COM, 0x10, 0x0200, COM_FREQ * 8 },
+ },
+ },
I also found this link, but I cannot do anything with the entries. Maybe a
developer can use this.
--
Met vriendelijke groeten,
With kind regards,
Mit freundlichen Gruessen,
Willy
*
W.K. Offermans
Home: +31 45 544 49 44
Mobile: +31 681 15 87 68
e-mail: wi...@offermans.rompen.nl
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
Dear John and FreeBSD friends,
On Thu, May 26, 2011 at 04:12:40PM -0400, John Baldwin wrote:
> On Thursday, May 26, 2011 3:01:35 pm Willy Offermans wrote:
> > Dear John and FreeBSD friends,
> >
> > On Wed, May 25, 2011 at 12:36:30PM -0400, John Baldwin wrote:
> > > On Saturday, May 21, 2011 5:20:37 am Willy Offermans wrote:
> > > > Dear FreeBSD friends,
> > > >
> > > > I need support with a MultiTech modem, MT9234ZPX-PCIE-NV
> > > > (http://www.multitech.com/en_US/PRODUCTS/Families/MultiModemZPX/)
> > > >
> > > > The modem is recognised during the boot event:
> > > >
> > > >
> > > > pci6: at device 0.0 (no driver attached)
> > > >
> > > >
> > > > and also appears in the list of found hardware over the PCI bus:
> > > >
> > > >
> > > > none1@pci0:6:0:0: class=0x070002 card=0x20262205 chip=0x015213a8
> > > rev=0x02 hdr=0x00
> > > > vendor = 'Exar Corp.'
> > > > device = 'XR17C/D152 Dual PCI UART'
> > > > class = simple comms
> > > > subclass = UART
> > > >
> > > >
> > > > However, as the boot process already mentions, there is no driver
> > > > attached
> > > > and I cannot get the modem to appear as an accessible and functional
> > > > device. Is there someone, who can help me to get this modem to work?
> > >
> > > Try this patch to sys/dev/uart/uart_bus_pci.c:
> > >
> > > Index: uart_bus_pci.c
> > > ===
> > > --- uart_bus_pci.c(revision 48)
> > > +++ uart_bus_pci.c(working copy)
> > > @@ -110,6 +110,7 @@ static struct pci_id pci_ns8250_ids[] = {
> > > { 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus 16950
> > > UART",
> > > 0x10, 16384000 },
> > > { 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem", 0x10
> > > },
> > > +{ 0x13a8, 0x0152, 0x2205, 0x2026, "MultiTech MultiModem ZPX", 0x10 },
> > > { 0x9710, 0x9820, 0x1000, 1, "NetMos NM9820 Serial Port", 0x10 },
> > > { 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
> > > { 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10 },
> > >
> > > --
> > > John Baldwin
> >
> > I have applied your suggested patch.
> >
> > Upon reboot the system showed an extra serial device:
> > crw-rw 1 uucp dialer0, 36 May 26 19:13 /dev/cuau0
> > crw-rw 1 uucp dialer0, 37 May 26 19:00 /dev/cuau0.init
> > crw-rw 1 uucp dialer0, 38 May 26 19:00 /dev/cuau0.lock
> > crw-rw 1 uucp dialer0, 55 May 26 19:00 /dev/cuau1
> > crw-rw 1 uucp dialer0, 56 May 26 19:00 /dev/cuau1.init
> > crw-rw 1 uucp dialer0, 57 May 26 19:00 /dev/cuau1.lock
> > crw-rw 1 uucp dialer0, 61 May 26 19:00 /dev/cuau2
> > crw-rw 1 uucp dialer0, 62 May 26 19:00 /dev/cuau2.init
> > crw-rw 1 uucp dialer0, 63 May 26 19:00 /dev/cuau2.lock
> >
> > the boot messages concerning uart were:
> >
> > uart0: failed to enable port mapping!
> > uart0: failed to enable port mapping!
> > uart0: <16750 or compatible> mem 0xfbfffc00-0xfbff irq 16 at device 0.0
> > on pci6
> > uart0: [FILTER]
>
> Hmm, can you get 'pciconf -lb' output?
>
> Hmm, wow, I wonder how uart(4) works at all. It tries to reuse it's softc
> structure in uart_bus_attach() that was setup in uart_bus_probe(). Since it
> doesn't return 0 from its probe routine, that is forbidden. I guess it
> accidentally works because of the hack where we call DEVICE_PROBE() again
> to make sure the device description is correct.
>
> --
> John Baldwin
I guess this is the interesting part:
uart0@pci0:6:0:0: class=0x070002 card=0x20262205 chip=0x015213a8 rev=0x02
hdr=0x00
bar [10] = type Memory, range 32, base 0xfbfffc00, size 1024, enabled
--
Met vriendelijke groeten,
With kind regards,
Mit freundlichen Gruessen,
Willy
*
W.K. Offermans
Home: +31 45 544 49 44
Mobile: +31 681 15 87 68
e-mail: wi...@offermans.rompen.nl
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On 5/26/2011 4:12 PM, John Baldwin wrote: > > Hmm, can you get 'pciconf -lb' output? > > Hmm, wow, I wonder how uart(4) works at all. It tries to reuse it's softc > structure in uart_bus_attach() that was setup in uart_bus_probe(). Since it > doesn't return 0 from its probe routine, that is forbidden. I guess it > accidentally works because of the hack where we call DEVICE_PROBE() again > to make sure the device description is correct. I think this is a similar card. Had it laying about for a while and popped it in. cu -l to it, attaches, but I am not able to interact with it. none3@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8 rev=0x02 hdr=0x00 vendor = 'Exar Corp.' device = 'XR17C/D152 Dual PCI UART' class = simple comms subclass = UART bar [10] = type Memory, range 32, base 0xe895, size 1024, enabled NetBSD supposedly has support for this card http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/pci/pucdata.c.diff?r1=1.43&r2=1.44 ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On Thursday, May 26, 2011 3:01:35 pm Willy Offermans wrote:
> Dear John and FreeBSD friends,
>
> On Wed, May 25, 2011 at 12:36:30PM -0400, John Baldwin wrote:
> > On Saturday, May 21, 2011 5:20:37 am Willy Offermans wrote:
> > > Dear FreeBSD friends,
> > >
> > > I need support with a MultiTech modem, MT9234ZPX-PCIE-NV
> > > (http://www.multitech.com/en_US/PRODUCTS/Families/MultiModemZPX/)
> > >
> > > The modem is recognised during the boot event:
> > >
> > >
> > > pci6: at device 0.0 (no driver attached)
> > >
> > >
> > > and also appears in the list of found hardware over the PCI bus:
> > >
> > >
> > > none1@pci0:6:0:0: class=0x070002 card=0x20262205 chip=0x015213a8
> > rev=0x02 hdr=0x00
> > > vendor = 'Exar Corp.'
> > > device = 'XR17C/D152 Dual PCI UART'
> > > class = simple comms
> > > subclass = UART
> > >
> > >
> > > However, as the boot process already mentions, there is no driver attached
> > > and I cannot get the modem to appear as an accessible and functional
> > > device. Is there someone, who can help me to get this modem to work?
> >
> > Try this patch to sys/dev/uart/uart_bus_pci.c:
> >
> > Index: uart_bus_pci.c
> > ===
> > --- uart_bus_pci.c (revision 222248)
> > +++ uart_bus_pci.c (working copy)
> > @@ -110,6 +110,7 @@ static struct pci_id pci_ns8250_ids[] = {
> > { 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus 16950
> > UART",
> > 0x10, 16384000 },
> > { 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem", 0x10 },
> > +{ 0x13a8, 0x0152, 0x2205, 0x2026, "MultiTech MultiModem ZPX", 0x10 },
> > { 0x9710, 0x9820, 0x1000, 1, "NetMos NM9820 Serial Port", 0x10 },
> > { 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
> > { 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10 },
> >
> > --
> > John Baldwin
>
> I have applied your suggested patch.
>
> Upon reboot the system showed an extra serial device:
> crw-rw 1 uucp dialer0, 36 May 26 19:13 /dev/cuau0
> crw-rw 1 uucp dialer0, 37 May 26 19:00 /dev/cuau0.init
> crw-rw 1 uucp dialer0, 38 May 26 19:00 /dev/cuau0.lock
> crw-rw 1 uucp dialer0, 55 May 26 19:00 /dev/cuau1
> crw-rw 1 uucp dialer0, 56 May 26 19:00 /dev/cuau1.init
> crw-rw 1 uucp dialer0, 57 May 26 19:00 /dev/cuau1.lock
> crw-rw 1 uucp dialer0, 61 May 26 19:00 /dev/cuau2
> crw-rw 1 uucp dialer0, 62 May 26 19:00 /dev/cuau2.init
> crw-rw 1 uucp dialer0, 63 May 26 19:00 /dev/cuau2.lock
>
> the boot messages concerning uart were:
>
> uart0: failed to enable port mapping!
> uart0: failed to enable port mapping!
> uart0: <16750 or compatible> mem 0xfbfffc00-0xfbff irq 16 at device 0.0
> on pci6
> uart0: [FILTER]
Hmm, can you get 'pciconf -lb' output?
Hmm, wow, I wonder how uart(4) works at all. It tries to reuse it's softc
structure in uart_bus_attach() that was setup in uart_bus_probe(). Since it
doesn't return 0 from its probe routine, that is forbidden. I guess it
accidentally works because of the hack where we call DEVICE_PROBE() again
to make sure the device description is correct.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
Dear John and FreeBSD friends,
On Wed, May 25, 2011 at 12:36:30PM -0400, John Baldwin wrote:
> On Saturday, May 21, 2011 5:20:37 am Willy Offermans wrote:
> > Dear FreeBSD friends,
> >
> > I need support with a MultiTech modem, MT9234ZPX-PCIE-NV
> > (http://www.multitech.com/en_US/PRODUCTS/Families/MultiModemZPX/)
> >
> > The modem is recognised during the boot event:
> >
> >
> > pci6: at device 0.0 (no driver attached)
> >
> >
> > and also appears in the list of found hardware over the PCI bus:
> >
> >
> > none1@pci0:6:0:0: class=0x070002 card=0x20262205 chip=0x015213a8
> rev=0x02 hdr=0x00
> > vendor = 'Exar Corp.'
> > device = 'XR17C/D152 Dual PCI UART'
> > class = simple comms
> > subclass = UART
> >
> >
> > However, as the boot process already mentions, there is no driver attached
> > and I cannot get the modem to appear as an accessible and functional
> > device. Is there someone, who can help me to get this modem to work?
>
> Try this patch to sys/dev/uart/uart_bus_pci.c:
>
> Index: uart_bus_pci.c
> ===
> --- uart_bus_pci.c(revision 48)
> +++ uart_bus_pci.c(working copy)
> @@ -110,6 +110,7 @@ static struct pci_id pci_ns8250_ids[] = {
> { 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus 16950
> UART",
> 0x10, 16384000 },
> { 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem", 0x10 },
> +{ 0x13a8, 0x0152, 0x2205, 0x2026, "MultiTech MultiModem ZPX", 0x10 },
> { 0x9710, 0x9820, 0x1000, 1, "NetMos NM9820 Serial Port", 0x10 },
> { 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
> { 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10 },
>
> --
> John Baldwin
I have applied your suggested patch.
Upon reboot the system showed an extra serial device:
crw-rw 1 uucp dialer0, 36 May 26 19:13 /dev/cuau0
crw-rw 1 uucp dialer0, 37 May 26 19:00 /dev/cuau0.init
crw-rw 1 uucp dialer0, 38 May 26 19:00 /dev/cuau0.lock
crw-rw 1 uucp dialer0, 55 May 26 19:00 /dev/cuau1
crw-rw 1 uucp dialer0, 56 May 26 19:00 /dev/cuau1.init
crw-rw 1 uucp dialer0, 57 May 26 19:00 /dev/cuau1.lock
crw-rw 1 uucp dialer0, 61 May 26 19:00 /dev/cuau2
crw-rw 1 uucp dialer0, 62 May 26 19:00 /dev/cuau2.init
crw-rw 1 uucp dialer0, 63 May 26 19:00 /dev/cuau2.lock
the boot messages concerning uart were:
uart0: failed to enable port mapping!
uart0: failed to enable port mapping!
uart0: <16750 or compatible> mem 0xfbfffc00-0xfbff irq 16 at device 0.0 on
pci6
uart0: [FILTER]
uart1: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0
uart1: [FILTER]
uart2: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
uart2: [FILTER]
pciconf -lv gave the following:
uart0@pci0:6:0:0: class=0x070002 card=0x20262205 chip=0x015213a8 rev=0x02
hdr=0x00
vendor = 'Exar Corp.'
device = 'XR17C/D152 Dual PCI UART'
class = simple comms
subclass = UART
However minicom was not able to initialise the modem properly. I only saw
some ooo.oo signs.
HylaFAX could find the modem, but was not able to initialise it:
HylaFAX scheduler on localhost: Running
Modem modem (+31455**): Waiting for modem to come ready
In the debug.log:
May 26 20:57:05 kosmos HylaFAX[2889]: Parsing hostPort(): "EPRT"
May 26 20:57:05 kosmos HylaFAX[2889]: Parsing "|1|127.0.0.1|62073|"
May 26 20:57:05 kosmos HylaFAX[2889]: `-> s.length() = 19
May 26 20:57:05 kosmos HylaFAX[2889]: `-> s[0] = '|'
May 26 20:57:05 kosmos HylaFAX[2889]: `-> s[2] = '|'
May 26 20:57:05 kosmos HylaFAX[2889]: `-> s[18] = '|'
May 26 20:57:05 kosmos HylaFAX[2889]: Looks like extended syntax:
"|1|127.0.0.1|62073|" [7C: |]
May 26 20:57:05 kosmos HylaFAX[2889]: `-> Got a: 127.0.0.1[13]
May 26 20:57:05 kosmos HylaFAX[2889]: `-> Got a: 62073[19]
May 26 20:57:05 kosmos HylaFAX[2889]: Parsed: Family 1 Address 127.0.0.1 Port
62073
May 26 20:57:06 kosmos HylaFAX[2891]: Parsing hostPort(): "EPRT"
May 26 20:57:06 kosmos HylaFAX[2891]: Parsing "|1|127.0.0.1|60536|"
May 26 20:57:06 kosmos HylaFAX[2891]: `-> s.length() = 19
May 26 20:57:06 kosmos HylaFAX[2891]: `-> s[0] = '|'
May 26 20:57:06 kosmos HylaFAX[2891]: `-> s[2] = '|'
May 26 20:57:06 kosmos HylaFAX[2891]: `-> s[18] = '|'
May 26 20:57:06 kosmos HylaFAX[2891]: Looks like extended syntax:
"|1|127.0.0.1|60536|" [7C: |]
May 26 20:57:06 kosmos HylaFAX[2891]: `-> Got a: 127.0.0.1[
Re: modem support MT9234ZPX-PCIE-NV
On Saturday, May 21, 2011 5:20:37 am Willy Offermans wrote:
> Dear FreeBSD friends,
>
> I need support with a MultiTech modem, MT9234ZPX-PCIE-NV
> (http://www.multitech.com/en_US/PRODUCTS/Families/MultiModemZPX/)
>
> The modem is recognised during the boot event:
>
>
> pci6: at device 0.0 (no driver attached)
>
>
> and also appears in the list of found hardware over the PCI bus:
>
>
> none1@pci0:6:0:0: class=0x070002 card=0x20262205 chip=0x015213a8
rev=0x02 hdr=0x00
> vendor = 'Exar Corp.'
> device = 'XR17C/D152 Dual PCI UART'
> class = simple comms
> subclass = UART
>
>
> However, as the boot process already mentions, there is no driver attached
> and I cannot get the modem to appear as an accessible and functional
> device. Is there someone, who can help me to get this modem to work?
Try this patch to sys/dev/uart/uart_bus_pci.c:
Index: uart_bus_pci.c
===
--- uart_bus_pci.c (revision 48)
+++ uart_bus_pci.c (working copy)
@@ -110,6 +110,7 @@ static struct pci_id pci_ns8250_ids[] = {
{ 0x1415, 0x950b, 0x, 0, "Oxford Semiconductor OXCB950 Cardbus 16950
UART",
0x10, 16384000 },
{ 0x151f, 0x, 0x, 0, "TOPIC Semiconductor TP560 56k modem", 0x10 },
+{ 0x13a8, 0x0152, 0x2205, 0x2026, "MultiTech MultiModem ZPX", 0x10 },
{ 0x9710, 0x9820, 0x1000, 1, "NetMos NM9820 Serial Port", 0x10 },
{ 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
{ 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10 },
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On 25/05/2011, at 16:04, Willy Offermans wrote: > I'm using FreeBSD 7.2-RELEASE-p2. I have enclosed the dmesg.boot file. > > puc was already incorporated into the kernel: > > kosmos# kldload -v puc > kldload: can't load puc: File exists > > So I assume puc has already been loaded. You could try editing /usr/src/sys/dev/puc/pucdata.c to add your card's ID and then rebuild & reload the puc module. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On 25/05/2011, at 16:10, Willy Offermans wrote: > According to the manufacturer > (http://www.multitech.com/en_US/PRODUCTS/Families/MultiModemZPX/) > it is not a soft modem, but a ``hardware'' modem. It says: Built-in > processor does the work, so your computer doesn't have to. I do not know if > this is sufficient to work under FreeBSD, but it seems to indicate that it > does not need any proprietary driver. Ahh, sounds promising.. You could just try adding the device IDs to the PUC driver and seeing what happens. Failing that ask Multitech if they can help you out. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
Dear Daniel and FreeBSD friends, On Sun, May 22, 2011 at 10:48:03AM +0200, Daniel O'Connor wrote: > > On 22/05/2011, at 9:16, Jeremy Chadwick wrote: > >> However, as the boot process already mentions, there is no driver attached > >> and I cannot get the modem to appear as an accessible and functional > >> device. Is there someone, who can help me to get this modem to work? > > > > It would be helpful if you could specify what FreeBSD version you're > > using. > > > > Assuming 8.2 or RELENG_8: no promises, but puc(4) is probably what > > you're looking for. I would try adding: > > > > puc_load="yes" > > > > To your /boot/loader.conf, then see what happens after booting. uart(4) > > may auto-attach to that. Again, no promises. > > I have my doubts it would work though, most likely it's a soft modem which > will only work with proprietary drivers. > > I couldn't find any details on the web page though so you might get lucky I > suppose :) > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > > > > > > According to the manufacturer (http://www.multitech.com/en_US/PRODUCTS/Families/MultiModemZPX/) it is not a soft modem, but a ``hardware'' modem. It says: Built-in processor does the work, so your computer doesn't have to. I do not know if this is sufficient to work under FreeBSD, but it seems to indicate that it does not need any proprietary driver. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
Hello Jeremy and FreeBSD friends, On Sun, May 22, 2011 at 12:16:42AM -0700, Jeremy Chadwick wrote: > On Sat, May 21, 2011 at 11:20:37AM +0200, Willy Offermans wrote: > > Dear FreeBSD friends, > > > > I need support with a MultiTech modem, MT9234ZPX-PCIE-NV > > (http://www.multitech.com/en_US/PRODUCTS/Families/MultiModemZPX/) > > > > The modem is recognised during the boot event: > > > > > > pci6: at device 0.0 (no driver attached) > > > > > > and also appears in the list of found hardware over the PCI bus: > > > > > > none1@pci0:6:0:0: class=0x070002 card=0x20262205 chip=0x015213a8 > > rev=0x02 hdr=0x00 > > vendor = 'Exar Corp.' > > device = 'XR17C/D152 Dual PCI UART' > > class = simple comms > > subclass = UART > > > > > > However, as the boot process already mentions, there is no driver attached > > and I cannot get the modem to appear as an accessible and functional > > device. Is there someone, who can help me to get this modem to work? > > It would be helpful if you could specify what FreeBSD version you're > using. > > Assuming 8.2 or RELENG_8: no promises, but puc(4) is probably what > you're looking for. I would try adding: > > puc_load="yes" > > To your /boot/loader.conf, then see what happens after booting. uart(4) > may auto-attach to that. Again, no promises. > > -- > | Jeremy Chadwick j...@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP 4BD6C0CB | > I'm using FreeBSD 7.2-RELEASE-p2. I have enclosed the dmesg.boot file. puc was already incorporated into the kernel: kosmos# kldload -v puc kldload: can't load puc: File exists So I assume puc has already been loaded. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * Dr. W.K. Offermans CAT Postdoctoral Fellow CAT Catalytic Center Institut f�r Technische und Makromolekulare Chemie RWTH Aachen Worringerweg 1, Raum 38C-150 D-52074 Aachen, Germany Phone: +49 241 80 28592 Fax:+49 241 80 22593 Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl e-mail: willy.offerm...@catalyticcenter.rwth-aachen.de Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...0 0 done All buffers synced. Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-RELEASE-p2 #3: Thu May 12 16:15:47 CEST 2011 wi...@kosmos.rompen.nl:/usr/obj/usr/src/sys/KOSMOS Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU X3360 @ 2.83GHz (2266.76-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x1067a Stepping = 10 Features=0xbfebfbff Features2=0x408e3fd,XSAVE> AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 4 usable memory = 4285059072 (4086 MB) avail memory = 4116738048 (3926 MB) ACPI APIC Table: <082608 APIC0956> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 This module (opensolaris) contains code covered by the Common Development and Distribution License (CDDL) see http://opensolaris.org/os/licensing/opensolaris_license/ ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: <082608 RSDT0956> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, dff0 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci5: on pcib1 pcib2: at device 0.0 on pci
Re: modem support MT9234ZPX-PCIE-NV
On 22/05/2011, at 9:16, Jeremy Chadwick wrote: >> However, as the boot process already mentions, there is no driver attached >> and I cannot get the modem to appear as an accessible and functional >> device. Is there someone, who can help me to get this modem to work? > > It would be helpful if you could specify what FreeBSD version you're > using. > > Assuming 8.2 or RELENG_8: no promises, but puc(4) is probably what > you're looking for. I would try adding: > > puc_load="yes" > > To your /boot/loader.conf, then see what happens after booting. uart(4) > may auto-attach to that. Again, no promises. I have my doubts it would work though, most likely it's a soft modem which will only work with proprietary drivers. I couldn't find any details on the web page though so you might get lucky I suppose :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: modem support MT9234ZPX-PCIE-NV
On Sat, May 21, 2011 at 11:20:37AM +0200, Willy Offermans wrote: > Dear FreeBSD friends, > > I need support with a MultiTech modem, MT9234ZPX-PCIE-NV > (http://www.multitech.com/en_US/PRODUCTS/Families/MultiModemZPX/) > > The modem is recognised during the boot event: > > > pci6: at device 0.0 (no driver attached) > > > and also appears in the list of found hardware over the PCI bus: > > > none1@pci0:6:0:0: class=0x070002 card=0x20262205 chip=0x015213a8 > rev=0x02 hdr=0x00 > vendor = 'Exar Corp.' > device = 'XR17C/D152 Dual PCI UART' > class = simple comms > subclass = UART > > > However, as the boot process already mentions, there is no driver attached > and I cannot get the modem to appear as an accessible and functional > device. Is there someone, who can help me to get this modem to work? It would be helpful if you could specify what FreeBSD version you're using. Assuming 8.2 or RELENG_8: no promises, but puc(4) is probably what you're looking for. I would try adding: puc_load="yes" To your /boot/loader.conf, then see what happens after booting. uart(4) may auto-attach to that. Again, no promises. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
modem support MT9234ZPX-PCIE-NV
Dear FreeBSD friends, I need support with a MultiTech modem, MT9234ZPX-PCIE-NV (http://www.multitech.com/en_US/PRODUCTS/Families/MultiModemZPX/) The modem is recognised during the boot event: pci6: at device 0.0 (no driver attached) and also appears in the list of found hardware over the PCI bus: none1@pci0:6:0:0: class=0x070002 card=0x20262205 chip=0x015213a8 rev=0x02 hdr=0x00 vendor = 'Exar Corp.' device = 'XR17C/D152 Dual PCI UART' class = simple comms subclass = UART However, as the boot process already mentions, there is no driver attached and I cannot get the modem to appear as an accessible and functional device. Is there someone, who can help me to get this modem to work? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Re: Re: FreeBSD 8.2 and Lenovo X300 WWAN Modem
Wednesday 18 of May 2011 14:13:00 crsnet.pl napisał(a): > >> No. > >> I check with minicom that AT+CFUN=1 (Turns modem on) give Error but > >> AT+PCSTATE=1 turns it on. > >> Unfortunately when i change it in ppp.conf from AT+CFUN=1 to > >> AT+PCSTATE=1 that give me > >> May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Send: AT+PCSTATE=1^M > >> May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Expect(2): OK > >> > >> May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Received: > >> AT+PCSTATE=1^M^M > >> > >> May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Received: ERROR^M > >> May 18 12:13:50 x60s ppp[2697]: tun0: Chat: Expect timeout > > > > Oh and very important thing: > > MC5725 is a CDMA EV-DO card. It will not work in GSM/UMTS network > > AFAIK. > > > > https://www.sierrawireless.com/Newsroom/newsreleases/2006/09-18_sierra_wi > > reless_reaches_two_ev- do_revision_a_product_milestones.aspx > > > :( I must check that is a available CDMA network in Poland. Look on the http://www.bez- kabli.pl/viewtopic.php?t=12788&postdays=0&postorder=asc&start=15 > But if any here know that i can use GPS builded into this Modem i will > be gratful. > > Adrian. http://forum.thinkpads.com/viewtopic.php?f=30&t=61164 -- Maciej ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Re: FreeBSD 8.2 and Lenovo X300 WWAN Modem
No. I check with minicom that AT+CFUN=1 (Turns modem on) give Error but AT+PCSTATE=1 turns it on. Unfortunately when i change it in ppp.conf from AT+CFUN=1 to AT+PCSTATE=1 that give me May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Send: AT+PCSTATE=1^M May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Expect(2): OK May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Received: AT+PCSTATE=1^M^M May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Received: ERROR^M May 18 12:13:50 x60s ppp[2697]: tun0: Chat: Expect timeout Oh and very important thing: MC5725 is a CDMA EV-DO card. It will not work in GSM/UMTS network AFAIK. https://www.sierrawireless.com/Newsroom/newsreleases/2006/09-18_sierra_wireless_reaches_two_ev- do_revision_a_product_milestones.aspx :( I must check that is a available CDMA network in Poland. But if any here know that i can use GPS builded into this Modem i will be gratful. Adrian. -- Maciej ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Re: FreeBSD 8.2 and Lenovo X300 WWAN Modem
Wednesday 18 of May 2011 12:22:37 crsnet.pl napisał(a): > On Wed, 18 May 2011 12:05:20 +0200, Maciej Milewski > > wrote: > > Dnia środa, 18 maja 2011 o 11:40:36 crsnet.pl napisał(a): > >> Hello. > >> Have here anyone run this modem/GPS under FreeBSD 8.2 ? Modem is > >> recognized, but when i try to run ppp -ddial iplus i get this error > >> > >> > >> /var/log/messages > >> May 18 11:20:59 x60s ppp[1656]: tun0: Warning: Chat script failed > >> > >> /var/log/ppp > >> May 18 11:20:53 x60s ppp[1656]: tun0: Phase: deflink: opening -> > >> > >> dial > >> > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT^M > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT^M^M > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: OK^M > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT+CFUN=1^M > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT+CFUN=1^M^M > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: ERROR^M > >> > >> > >> For GPS i try to use > >> gpsdrive-2.09_11A GPS navigation system > >> viking-1.0.2Program to manage GPS data (tracks, waypoints, > >> > >> etc) > >> > >> But any of them can use X300 GPS;/ > >> > >> #uname -a > >> FreeBSD x60s 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18 > >> > >> 02:24:46 > >> > >> UTC 2011 > >> > >> r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > >> > >> i386 > >> > >> #dmesg > >> ugen6.3: at usbus6 > >> ugen4.2: at usbus4 > >> u3g0: on usbus4 > >> u3g0: Found 3 ports. > >> > >> #sudo usbconfig > >> ugen4.2: >> > >> Incorporated> > >> > >> at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > >> ugen6.4: at usbus6, cfg=0 md=HOST spd=HIGH > >> (480Mbps) pwr=ON > >> > >> #ls -la /dev/cuaU* > >> crw-rw 1 uucp dialer0, 123 18 maj 09:39 /dev/cuaU0.0 > >> crw-rw 1 uucp dialer0, 124 18 maj 09:39 /dev/cuaU0.0.init > >> crw-rw 1 uucp dialer0, 125 18 maj 09:39 /dev/cuaU0.0.lock > >> crw-rw 1 uucp dialer0, 129 18 maj 09:39 /dev/cuaU0.1 > >> crw-rw 1 uucp dialer0, 130 18 maj 09:39 /dev/cuaU0.1.init > >> crw-rw 1 uucp dialer0, 131 18 maj 09:39 /dev/cuaU0.1.lock > >> crw-rw 1 uucp dialer0, 135 18 maj 09:39 /dev/cuaU0.2 > >> crw-rw 1 uucp dialer0, 136 18 maj 09:39 /dev/cuaU0.2.init > >> crw-rw 1 uucp dialer0, 137 18 maj 09:39 /dev/cuaU0.2.lock > >> > >> #cat /etc/ppp/ppp.conf > >> > >> iplus: > >> set log Phase Chat LCP IPCP CCP tun command > >> ident user-ppp VERSION (built COMPILATIONDATE) > >> > >> set device /dev/cuaU0.0 > >> set speed 460800 > >> #set speed 115200 > >> set dial "ABORT BUSY TIMEOUT 2 \ > >> > >> \"\" \ > >> AT OK-AT-OK \ > >> AT+CFUN=1 OK-AT-OK \ > >> AT+CMEE=2 OK-AT-OK \ > >> AT+CSQ OK \ > >> AT+CGDCONT=1,\\\"IP\\\",\\\"internet\\\" OK \ > >> AT+CGACT? OK-AT-OK \ > >> AT+CGATT? OK \ > >> AT+CGCLASS? OK \ > >> AT+COPS? OK \ > >> ATD*99***1# CONNECT" > >> > >> set timeout 180 > >> enable dns > >> set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > >> add default HISADDR > >> > >> Regards, Adrian. > > > > Do you have a pin defined on sim? > > No. > I check with minicom that AT+CFUN=1 (Turns modem on) give Error but > AT+PCSTATE=1 turns it on. > Unfortunately when i change it in ppp.conf from AT+CFUN=1 to > AT+PCSTATE=1 that give me > May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Send: AT+PCSTATE=1^M > May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Expect(2): OK > May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Received: AT+PCSTATE=1^M^M > May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Received: ERROR^M > May 18 12:13:50 x60s ppp[2697]: tun0: Chat: Expect timeout Oh and very important thing: MC5725 is a CDMA EV-DO card. It will not work in GSM/UMTS network AFAIK. https://www.sierrawireless.com/Newsroom/newsreleases/2006/09-18_sierra_wireless_reaches_two_ev- do_revision_a_product_milestones.aspx -- Maciej ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Re: FreeBSD 8.2 and Lenovo X300 WWAN Modem
Wednesday 18 of May 2011 12:22:37 crsnet.pl napisał(a): > On Wed, 18 May 2011 12:05:20 +0200, Maciej Milewski > > wrote: > > Dnia środa, 18 maja 2011 o 11:40:36 crsnet.pl napisał(a): > >> Hello. > >> Have here anyone run this modem/GPS under FreeBSD 8.2 ? Modem is > >> recognized, but when i try to run ppp -ddial iplus i get this error > >> > >> > >> /var/log/messages > >> May 18 11:20:59 x60s ppp[1656]: tun0: Warning: Chat script failed > >> > >> /var/log/ppp > >> May 18 11:20:53 x60s ppp[1656]: tun0: Phase: deflink: opening -> > >> > >> dial > >> > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT^M > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT^M^M > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: OK^M > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT+CFUN=1^M > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT+CFUN=1^M^M > >> May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: ERROR^M > >> > >> > >> For GPS i try to use > >> gpsdrive-2.09_11A GPS navigation system > >> viking-1.0.2Program to manage GPS data (tracks, waypoints, > >> > >> etc) > >> > >> But any of them can use X300 GPS;/ > >> > >> #uname -a > >> FreeBSD x60s 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18 > >> > >> 02:24:46 > >> > >> UTC 2011 > >> > >> r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > >> > >> i386 > >> > >> #dmesg > >> ugen6.3: at usbus6 > >> ugen4.2: at usbus4 > >> u3g0: on usbus4 > >> u3g0: Found 3 ports. > >> > >> #sudo usbconfig > >> ugen4.2: >> > >> Incorporated> > >> > >> at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > >> ugen6.4: at usbus6, cfg=0 md=HOST spd=HIGH > >> (480Mbps) pwr=ON > >> > >> #ls -la /dev/cuaU* > >> crw-rw 1 uucp dialer0, 123 18 maj 09:39 /dev/cuaU0.0 > >> crw-rw 1 uucp dialer0, 124 18 maj 09:39 /dev/cuaU0.0.init > >> crw-rw 1 uucp dialer0, 125 18 maj 09:39 /dev/cuaU0.0.lock > >> crw-rw 1 uucp dialer0, 129 18 maj 09:39 /dev/cuaU0.1 > >> crw-rw 1 uucp dialer0, 130 18 maj 09:39 /dev/cuaU0.1.init > >> crw-rw 1 uucp dialer0, 131 18 maj 09:39 /dev/cuaU0.1.lock > >> crw-rw 1 uucp dialer0, 135 18 maj 09:39 /dev/cuaU0.2 > >> crw-rw 1 uucp dialer0, 136 18 maj 09:39 /dev/cuaU0.2.init > >> crw-rw 1 uucp dialer0, 137 18 maj 09:39 /dev/cuaU0.2.lock > >> > >> #cat /etc/ppp/ppp.conf > >> > >> iplus: > >> set log Phase Chat LCP IPCP CCP tun command > >> ident user-ppp VERSION (built COMPILATIONDATE) > >> > >> set device /dev/cuaU0.0 > >> set speed 460800 > >> #set speed 115200 > >> set dial "ABORT BUSY TIMEOUT 2 \ > >> > >> \"\" \ > >> AT OK-AT-OK \ > >> AT+CFUN=1 OK-AT-OK \ > >> AT+CMEE=2 OK-AT-OK \ > >> AT+CSQ OK \ > >> AT+CGDCONT=1,\\\"IP\\\",\\\"internet\\\" OK \ > >> AT+CGACT? OK-AT-OK \ > >> AT+CGATT? OK \ > >> AT+CGCLASS? OK \ > >> AT+COPS? OK \ > >> ATD*99***1# CONNECT" > >> > >> set timeout 180 > >> enable dns > >> set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > >> add default HISADDR > >> > >> Regards, Adrian. > > > > Do you have a pin defined on sim? > > No. > I check with minicom that AT+CFUN=1 (Turns modem on) give Error but > AT+PCSTATE=1 turns it on. > Unfortunately when i change it in ppp.conf from AT+CFUN=1 to > AT+PCSTATE=1 that give me > May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Send: AT+PCSTATE=1^M > May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Expect(2): OK > May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Received: AT+PCSTATE=1^M^M > May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Received: ERROR^M > May 18 12:13:50 x60s ppp[2697]: tun0: Chat: Expect timeout http://sierrawireless.custhelp.com/app/answers/detail/a_id/500/~/can-i-use-my- sierra-wireless-modem-on-a-linux-operating-system-%3F-%28-v.1.7.36%29 Sometimest command port is different than data port. Try different cuau0.0, cuau0.1, cuau0.2 also GPS many times has his own subinterface so that may be the point. My working ppp.conf dial definition, with pin enabled: set dial "ABORT BUSY ABORT NO\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK \ AT OK-AT-OK AT+CPIN= OK-AT-OK\ AT+CGDCONT=1,\\\"IP\\\",\\\"internet\\\" OK \ AT OK-AT-OK \\dATDT\\T TIMEOUT 40 CONNECT" -- Maciej ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 8.2 and Lenovo X300 WWAN Modem
Dnia środa, 18 maja 2011 o 11:40:36 crsnet.pl napisał(a): > Hello. > Have here anyone run this modem/GPS under FreeBSD 8.2 ? Modem is > recognized, but when i try to run ppp -ddial iplus i get this error : > > /var/log/messages > May 18 11:20:59 x60s ppp[1656]: tun0: Warning: Chat script failed > > /var/log/ppp > May 18 11:20:53 x60s ppp[1656]: tun0: Phase: deflink: opening -> dial > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT^M^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: OK^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT+CFUN=1^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT+CFUN=1^M^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: ERROR^M > > > For GPS i try to use > gpsdrive-2.09_11A GPS navigation system > viking-1.0.2Program to manage GPS data (tracks, waypoints, etc) > But any of them can use X300 GPS;/ > > #uname -a > FreeBSD x60s 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18 02:24:46 > UTC 2011 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > i386 > > #dmesg > ugen6.3: at usbus6 > ugen4.2: at usbus4 > u3g0: on usbus4 > u3g0: Found 3 ports. > > #sudo usbconfig > ugen4.2: > at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON > ugen6.4: at usbus6, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=ON > > #ls -la /dev/cuaU* > crw-rw 1 uucp dialer0, 123 18 maj 09:39 /dev/cuaU0.0 > crw-rw 1 uucp dialer0, 124 18 maj 09:39 /dev/cuaU0.0.init > crw-rw 1 uucp dialer0, 125 18 maj 09:39 /dev/cuaU0.0.lock > crw-rw 1 uucp dialer0, 129 18 maj 09:39 /dev/cuaU0.1 > crw-rw 1 uucp dialer0, 130 18 maj 09:39 /dev/cuaU0.1.init > crw-rw 1 uucp dialer0, 131 18 maj 09:39 /dev/cuaU0.1.lock > crw-rw 1 uucp dialer0, 135 18 maj 09:39 /dev/cuaU0.2 > crw-rw 1 uucp dialer0, 136 18 maj 09:39 /dev/cuaU0.2.init > crw-rw 1 uucp dialer0, 137 18 maj 09:39 /dev/cuaU0.2.lock > > #cat /etc/ppp/ppp.conf > iplus: > set log Phase Chat LCP IPCP CCP tun command > ident user-ppp VERSION (built COMPILATIONDATE) > > set device /dev/cuaU0.0 > set speed 460800 > #set speed 115200 > set dial "ABORT BUSY TIMEOUT 2 \ > \"\" \ > AT OK-AT-OK \ > AT+CFUN=1 OK-AT-OK \ > AT+CMEE=2 OK-AT-OK \ > AT+CSQ OK \ > AT+CGDCONT=1,\\\"IP\\\",\\\"internet\\\" OK \ > AT+CGACT? OK-AT-OK \ > AT+CGATT? OK \ > AT+CGCLASS? OK \ > AT+COPS? OK \ > ATD*99***1# CONNECT" > > set timeout 180 > enable dns > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > add default HISADDR > > Regards, Adrian. Do you have a pin defined on sim? -- Maciej ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 8.2 and Lenovo X300 WWAN Modem
On Wed, May 18, 2011 at 11:40:36AM +0200, crsnet.pl wrote: > Hello. > Have here anyone run this modem/GPS under FreeBSD 8.2 ? Modem is > recognized, but when i try to run ppp -ddial iplus i get this error > : > > /var/log/messages > May 18 11:20:59 x60s ppp[1656]: tun0: Warning: Chat script failed > > /var/log/ppp > May 18 11:20:53 x60s ppp[1656]: tun0: Phase: deflink: opening -> dial > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT^M^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: OK^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT+CFUN=1^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT+CFUN=1^M^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: ERROR^M I'm not familiar with GPS modem units, but I am familiar with classic modems and a little bit with chat scripts from my Linux days. A couple things -- and possibly these GPS modems behave differently than what I was used to back in the early 90s: 1) Based on the chat logs above, it looks like echo mode is enabled on the modem. The client should be sending "AT\r", and it should receive the response "OK\r". Instead, the log indicates what you're getting back is "AT\r\rOK\r". 2) Regardless of #1, the AT+CFUN=1 command you're sending to the modem results in the modem itself responding with ERROR. This isn't coming from ppp, chat, or anything else -- the modem is literally responding with ERROR itself. Meaning, that command (obviously not Hayes!) the modem firmware doesn't know how to interpret. I have no idea what +CFUN=1 does, but then again the modem doesn't seem to either. :-) So I guess my advice would be: fix your chat script to work properly with your modem. :-) Your script is here: > set dial "ABORT BUSY TIMEOUT 2 \ > \"\" \ > AT OK-AT-OK \ > AT+CFUN=1 OK-AT-OK \ > AT+CMEE=2 OK-AT-OK \ > AT+CSQ OK \ > AT+CGDCONT=1,\\\"IP\\\",\\\"internet\\\" OK \ > AT+CGACT? OK-AT-OK \ > AT+CGATT? OK \ > AT+CGCLASS? OK \ > AT+COPS? OK \ > ATD*99***1# CONNECT" -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 8.2 and Lenovo X300 WWAN Modem
On Wed, 18 May 2011 12:05:20 +0200, Maciej Milewski wrote: Dnia środa, 18 maja 2011 o 11:40:36 crsnet.pl napisał(a): Hello. Have here anyone run this modem/GPS under FreeBSD 8.2 ? Modem is recognized, but when i try to run ppp -ddial iplus i get this error : /var/log/messages May 18 11:20:59 x60s ppp[1656]: tun0: Warning: Chat script failed /var/log/ppp May 18 11:20:53 x60s ppp[1656]: tun0: Phase: deflink: opening -> dial May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT^M May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT^M^M May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: OK^M May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT+CFUN=1^M May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT+CFUN=1^M^M May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: ERROR^M For GPS i try to use gpsdrive-2.09_11A GPS navigation system viking-1.0.2Program to manage GPS data (tracks, waypoints, etc) But any of them can use X300 GPS;/ #uname -a FreeBSD x60s 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18 02:24:46 UTC 2011 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 #dmesg ugen6.3: at usbus6 ugen4.2: at usbus4 u3g0: on usbus4 u3g0: Found 3 ports. #sudo usbconfig ugen4.2: Incorporated> at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen6.4: at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON #ls -la /dev/cuaU* crw-rw 1 uucp dialer0, 123 18 maj 09:39 /dev/cuaU0.0 crw-rw 1 uucp dialer0, 124 18 maj 09:39 /dev/cuaU0.0.init crw-rw 1 uucp dialer0, 125 18 maj 09:39 /dev/cuaU0.0.lock crw-rw 1 uucp dialer0, 129 18 maj 09:39 /dev/cuaU0.1 crw-rw 1 uucp dialer0, 130 18 maj 09:39 /dev/cuaU0.1.init crw-rw 1 uucp dialer0, 131 18 maj 09:39 /dev/cuaU0.1.lock crw-rw 1 uucp dialer0, 135 18 maj 09:39 /dev/cuaU0.2 crw-rw 1 uucp dialer0, 136 18 maj 09:39 /dev/cuaU0.2.init crw-rw 1 uucp dialer0, 137 18 maj 09:39 /dev/cuaU0.2.lock #cat /etc/ppp/ppp.conf iplus: set log Phase Chat LCP IPCP CCP tun command ident user-ppp VERSION (built COMPILATIONDATE) set device /dev/cuaU0.0 set speed 460800 #set speed 115200 set dial "ABORT BUSY TIMEOUT 2 \ \"\" \ AT OK-AT-OK \ AT+CFUN=1 OK-AT-OK \ AT+CMEE=2 OK-AT-OK \ AT+CSQ OK \ AT+CGDCONT=1,\\\"IP\\\",\\\"internet\\\" OK \ AT+CGACT? OK-AT-OK \ AT+CGATT? OK \ AT+CGCLASS? OK \ AT+COPS? OK \ ATD*99***1# CONNECT" set timeout 180 enable dns set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR Regards, Adrian. Do you have a pin defined on sim? No. I check with minicom that AT+CFUN=1 (Turns modem on) give Error but AT+PCSTATE=1 turns it on. Unfortunately when i change it in ppp.conf from AT+CFUN=1 to AT+PCSTATE=1 that give me May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Send: AT+PCSTATE=1^M May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Expect(2): OK May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Received: AT+PCSTATE=1^M^M May 18 12:13:48 x60s ppp[2697]: tun0: Chat: Received: ERROR^M May 18 12:13:50 x60s ppp[2697]: tun0: Chat: Expect timeout -- Maciej ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 8.2 and Lenovo X300 WWAN Modem
Hello. Have here anyone run this modem/GPS under FreeBSD 8.2 ? Modem is recognized, but when i try to run ppp -ddial iplus i get this error : /var/log/messages May 18 11:20:59 x60s ppp[1656]: tun0: Warning: Chat script failed /var/log/ppp May 18 11:20:53 x60s ppp[1656]: tun0: Phase: deflink: opening -> dial May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT^M May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT^M^M May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: OK^M May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT+CFUN=1^M May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT+CFUN=1^M^M May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: ERROR^M For GPS i try to use gpsdrive-2.09_11A GPS navigation system viking-1.0.2Program to manage GPS data (tracks, waypoints, etc) But any of them can use X300 GPS;/ #uname -a FreeBSD x60s 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18 02:24:46 UTC 2011 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 #dmesg ugen6.3: at usbus6 ugen4.2: at usbus4 u3g0: on usbus4 u3g0: Found 3 ports. #sudo usbconfig ugen4.2: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen6.4: at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON #ls -la /dev/cuaU* crw-rw 1 uucp dialer0, 123 18 maj 09:39 /dev/cuaU0.0 crw-rw 1 uucp dialer0, 124 18 maj 09:39 /dev/cuaU0.0.init crw-rw 1 uucp dialer0, 125 18 maj 09:39 /dev/cuaU0.0.lock crw-rw 1 uucp dialer0, 129 18 maj 09:39 /dev/cuaU0.1 crw-rw 1 uucp dialer0, 130 18 maj 09:39 /dev/cuaU0.1.init crw-rw 1 uucp dialer0, 131 18 maj 09:39 /dev/cuaU0.1.lock crw-rw 1 uucp dialer0, 135 18 maj 09:39 /dev/cuaU0.2 crw-rw 1 uucp dialer0, 136 18 maj 09:39 /dev/cuaU0.2.init crw-rw 1 uucp dialer0, 137 18 maj 09:39 /dev/cuaU0.2.lock #cat /etc/ppp/ppp.conf iplus: set log Phase Chat LCP IPCP CCP tun command ident user-ppp VERSION (built COMPILATIONDATE) set device /dev/cuaU0.0 set speed 460800 #set speed 115200 set dial "ABORT BUSY TIMEOUT 2 \ \"\" \ AT OK-AT-OK \ AT+CFUN=1 OK-AT-OK \ AT+CMEE=2 OK-AT-OK \ AT+CSQ OK \ AT+CGDCONT=1,\\\"IP\\\",\\\"internet\\\" OK \ AT+CGACT? OK-AT-OK \ AT+CGATT? OK \ AT+CGCLASS? OK \ AT+COPS? OK \ ATD*99***1# CONNECT" set timeout 180 enable dns set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR Regards, Adrian. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
--On Friday, January 22, 2010 10:05 PM +0100 Nicolas Rachinsky wrote: * Jeremy Chadwick [2010-01-19 23:46 -0800]: You cannot do something like where box1 COM1 is wired to box2 COM1, and depending on what box you're on doing the "cu -l ttyu0" from, get a login prompt on the other. It doesn't work like that. :-) Isn't the reason for different dial-in and dial-out devices that this should work? Or does that only work with modem? You can't with two directly connected machines. When the two are physically wired together, and getty is configured (via ttys) to fire up on the port it takes over the port. If you connect two machines via a null modem cable, both with getty on the same port, the getty's will be chatting with each other. The locking mechanism will "break" the chat loop when you try to use the dialout device on one end or the other but you may have to wait some time before the other end restarts getty (because it previously would have been dieing very rapidly due to login failures) A NULL modem connection is ALWAYS active. A regular modem, is NOT. It has a state of 'inactive' or 'waiting for ring' if you will. The correct way to do what you want is as others have suggested, two serial null modem cables, and two com ports on each machine. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
* Jeremy Chadwick [2010-01-19 23:46 -0800]: > You cannot do something like where box1 COM1 is wired to box2 COM1, and > depending on what box you're on doing the "cu -l ttyu0" from, get a > login prompt on the other. It doesn't work like that. :-) Isn't the reason for different dial-in and dial-out devices that this should work? Or does that only work with modem? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/serial.html#ACCESS-SERIAL-PORTS Nicolas -- http://www.rachinsky.de/nicolas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On Fri, Jan 22, 2010 at 10:02 AM, N.J. Mann wrote: > In message <717f7a3e1001210137p7884adcbxc66a4f7fff928...@mail.gmail.com>, > Marin Atanasov (dna...@gmail.com) wrote: > > Hello Jeremy, > > > > Now I'm a little confused :) > > > > I've made some tests with my machines and a couple of null modem cables, > and > > here's what I've got. > > > > On Wed, Jan 20, 2010 at 9:46 AM, Jeremy Chadwick > > wrote: > > > > > On Wed, Jan 20, 2010 at 08:46:48AM +0200, Marin Atanasov wrote: > > > > Hello, > > > > > > > > Using `cu' only works with COM1 for me. > > > > > > > > Currently I have two serial ports on the system, and only the first > is > > > able > > > > to make the connection - the serial consoles are enabled in /etc/tty, > but > > > as > > > > I said only COM1 is able to make the connection. > > > > > > I'm a little confused by this statement, so I'll add some clarify: > > > > > > /etc/ttys is for configuring a machine to tie getty (think login > prompt) > > > to a device (in this case, a serial port). Meaning: the device on the > > > other end of the serial cable will start seeing "login:" and so on > > > assuming you attach to the serial port there. > > > > > > For example: > > > > > > box1 COM1/ttyu0 is wired to box2 COM3/ttyu2 using a null modem cable. > > > box1 COM2/ttyu1 is wired to box2 COM4/ttyu3 using a null modem cable. > > > > > > On box1, you'd have something like this in /etc/ttys: > > > > > > ttyu0 "/usr/libexec/getty std.9600" vt100 on secure > > > ttyu1 "/usr/libexec/getty std.9600" vt100 on secure > > > > > > > Here's what I did: > > > > box1 COM1/ttyd0 -> box2 COM1/ttyd0 -> using null modem cable > > box1 COM2/ttyd1 -> box3 COM1/ttyd0 -> using null modem cable > > > > On box1 I have this in /etc/ttys: > > > > ttyd0 "/usr/libexec/getty std.9600" vt100 on secure > > ttyd1 "/usr/libexec/getty std.9600" vt100 on secure > > > > Now if I want to connect to box1 from box2 or box3 through the serial > > connection it should work, right? > > But I only can connect to box1 from box2, because box2's COM port is > > connected to box1's COM1 port. > > > > >From box2 I can get a login prompt > > box2# cu -l /dev/cuad0 -s 9600 > > Connected > > > > login: > > ) > > (host.domain) (ttyd0) > > > > login: ~ > > [EOT] > > > > But if I try to connect to box1 from box3 - no success there. > > box3# cu -l /dev/cuad0 -s 9600 > > Connected > > ~ > > [EOT] > > You need to reduce the number of unknowns, e.g. where is the problem: > box1, box3 or in between. So, swap the cables on box1 so that you now > have box1:COM1 -> box3:COM1 and box1:COM2 -> box2:COM1. Now repeat the > tests above and post your results. > > > Cheers, > Nick. > -- > > Seems I've found the issue, that I'm having - a broken null modem cable :( The last time I was using that cable it was working fine. And now that I connected a second one to the machine, it seemed that only the one connected to COM1 was actually working, and I was left with the impression from the documentation that only COM1 is able to do a serial console connection. I'm very sorry to bother you like that. I'll continue setting up the servers once I get a new null modem cable. Thanks and regards, Marin -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On Fri, Jan 22, 2010 at 08:36:51AM +0200, Marin Atanasov wrote: > On Thu, Jan 21, 2010 at 6:26 PM, Ulrich Spörlein wrote: > > > On Thu, 21.01.2010 at 11:37:06 +0200, Marin Atanasov wrote: > > > Here's what I did: > > > > > > box1 COM1/ttyd0 -> box2 COM1/ttyd0 -> using null modem cable > > > box1 COM2/ttyd1 -> box3 COM1/ttyd0 -> using null modem cable > > > > > > On box1 I have this in /etc/ttys: > > > > > > ttyd0 "/usr/libexec/getty std.9600" vt100 on secure > > > ttyd1 "/usr/libexec/getty std.9600" vt100 on secure > > > > > > Now if I want to connect to box1 from box2 or box3 through the serial > > > connection it should work, right? > > > But I only can connect to box1 from box2, because box2's COM port is > > > connected to box1's COM1 port. > > > > Are there actually two gettys running on the serial ports? Did you do > > kill -1 1 after the changes to /etc/ttys? > > > > On box1, what do the following commands produce > > > > egrep "uart|sio" /var/run/dmesg.boot > > pgrep -fl getty > > > > Regards, > > Uli > > > Hi, > > This is the output from the requested commands: > > box1# egrep 'uart|sio' /var/run/dmesg.boot > usb0: USB revision 1.0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > > box1# pgrep -fl getty > 3066 /usr/libexec/getty std.9600 ttyd1 > 3065 /usr/libexec/getty std.9600 ttyd0 > 534 /usr/libexec/getty Pc ttyv7 > 533 /usr/libexec/getty Pc ttyv6 > 532 /usr/libexec/getty Pc ttyv5 > 531 /usr/libexec/getty Pc ttyv4 > 530 /usr/libexec/getty Pc ttyv3 > 529 /usr/libexec/getty Pc ttyv2 > 528 /usr/libexec/getty Pc ttyv1 > 527 /usr/libexec/getty Pc ttyv0 Can you run the same commands on box2 please? -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
In message <717f7a3e1001210137p7884adcbxc66a4f7fff928...@mail.gmail.com>, Marin Atanasov (dna...@gmail.com) wrote: > Hello Jeremy, > > Now I'm a little confused :) > > I've made some tests with my machines and a couple of null modem cables, and > here's what I've got. > > On Wed, Jan 20, 2010 at 9:46 AM, Jeremy Chadwick > wrote: > > > On Wed, Jan 20, 2010 at 08:46:48AM +0200, Marin Atanasov wrote: > > > Hello, > > > > > > Using `cu' only works with COM1 for me. > > > > > > Currently I have two serial ports on the system, and only the first is > > able > > > to make the connection - the serial consoles are enabled in /etc/tty, but > > as > > > I said only COM1 is able to make the connection. > > > > I'm a little confused by this statement, so I'll add some clarify: > > > > /etc/ttys is for configuring a machine to tie getty (think login prompt) > > to a device (in this case, a serial port). Meaning: the device on the > > other end of the serial cable will start seeing "login:" and so on > > assuming you attach to the serial port there. > > > > For example: > > > > box1 COM1/ttyu0 is wired to box2 COM3/ttyu2 using a null modem cable. > > box1 COM2/ttyu1 is wired to box2 COM4/ttyu3 using a null modem cable. > > > > On box1, you'd have something like this in /etc/ttys: > > > > ttyu0 "/usr/libexec/getty std.9600" vt100 on secure > > ttyu1 "/usr/libexec/getty std.9600" vt100 on secure > > > > Here's what I did: > > box1 COM1/ttyd0 -> box2 COM1/ttyd0 -> using null modem cable > box1 COM2/ttyd1 -> box3 COM1/ttyd0 -> using null modem cable > > On box1 I have this in /etc/ttys: > > ttyd0 "/usr/libexec/getty std.9600" vt100 on secure > ttyd1 "/usr/libexec/getty std.9600" vt100 on secure > > Now if I want to connect to box1 from box2 or box3 through the serial > connection it should work, right? > But I only can connect to box1 from box2, because box2's COM port is > connected to box1's COM1 port. > > >From box2 I can get a login prompt > box2# cu -l /dev/cuad0 -s 9600 > Connected > > login: > ) > (host.domain) (ttyd0) > > login: ~ > [EOT] > > But if I try to connect to box1 from box3 - no success there. > box3# cu -l /dev/cuad0 -s 9600 > Connected > ~ > [EOT] You need to reduce the number of unknowns, e.g. where is the problem: box1, box3 or in between. So, swap the cables on box1 so that you now have box1:COM1 -> box3:COM1 and box1:COM2 -> box2:COM1. Now repeat the tests above and post your results. Cheers, Nick. -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On Thu, Jan 21, 2010 at 6:26 PM, Ulrich Spörlein wrote: > On Thu, 21.01.2010 at 11:37:06 +0200, Marin Atanasov wrote: > > Here's what I did: > > > > box1 COM1/ttyd0 -> box2 COM1/ttyd0 -> using null modem cable > > box1 COM2/ttyd1 -> box3 COM1/ttyd0 -> using null modem cable > > > > On box1 I have this in /etc/ttys: > > > > ttyd0 "/usr/libexec/getty std.9600" vt100 on secure > > ttyd1 "/usr/libexec/getty std.9600" vt100 on secure > > > > Now if I want to connect to box1 from box2 or box3 through the serial > > connection it should work, right? > > But I only can connect to box1 from box2, because box2's COM port is > > connected to box1's COM1 port. > > Are there actually two gettys running on the serial ports? Did you do > kill -1 1 after the changes to /etc/ttys? > > On box1, what do the following commands produce > > egrep "uart|sio" /var/run/dmesg.boot > pgrep -fl getty > > Regards, > Uli > Hi, This is the output from the requested commands: box1# egrep 'uart|sio' /var/run/dmesg.boot usb0: USB revision 1.0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A box1# pgrep -fl getty 3066 /usr/libexec/getty std.9600 ttyd1 3065 /usr/libexec/getty std.9600 ttyd0 534 /usr/libexec/getty Pc ttyv7 533 /usr/libexec/getty Pc ttyv6 532 /usr/libexec/getty Pc ttyv5 531 /usr/libexec/getty Pc ttyv4 530 /usr/libexec/getty Pc ttyv3 529 /usr/libexec/getty Pc ttyv2 528 /usr/libexec/getty Pc ttyv1 527 /usr/libexec/getty Pc ttyv0 Regards, Marin -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On Thu, 21.01.2010 at 11:37:06 +0200, Marin Atanasov wrote: > Here's what I did: > > box1 COM1/ttyd0 -> box2 COM1/ttyd0 -> using null modem cable > box1 COM2/ttyd1 -> box3 COM1/ttyd0 -> using null modem cable > > On box1 I have this in /etc/ttys: > > ttyd0 "/usr/libexec/getty std.9600" vt100 on secure > ttyd1 "/usr/libexec/getty std.9600" vt100 on secure > > Now if I want to connect to box1 from box2 or box3 through the serial > connection it should work, right? > But I only can connect to box1 from box2, because box2's COM port is > connected to box1's COM1 port. Are there actually two gettys running on the serial ports? Did you do kill -1 1 after the changes to /etc/ttys? On box1, what do the following commands produce egrep "uart|sio" /var/run/dmesg.boot pgrep -fl getty Regards, Uli ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
Hello Jeremy, Now I'm a little confused :) I've made some tests with my machines and a couple of null modem cables, and here's what I've got. On Wed, Jan 20, 2010 at 9:46 AM, Jeremy Chadwick wrote: > On Wed, Jan 20, 2010 at 08:46:48AM +0200, Marin Atanasov wrote: > > Hello, > > > > Using `cu' only works with COM1 for me. > > > > Currently I have two serial ports on the system, and only the first is > able > > to make the connection - the serial consoles are enabled in /etc/tty, but > as > > I said only COM1 is able to make the connection. > > I'm a little confused by this statement, so I'll add some clarify: > > /etc/ttys is for configuring a machine to tie getty (think login prompt) > to a device (in this case, a serial port). Meaning: the device on the > other end of the serial cable will start seeing "login:" and so on > assuming you attach to the serial port there. > > For example: > > box1 COM1/ttyu0 is wired to box2 COM3/ttyu2 using a null modem cable. > box1 COM2/ttyu1 is wired to box2 COM4/ttyu3 using a null modem cable. > > On box1, you'd have something like this in /etc/ttys: > > ttyu0 "/usr/libexec/getty std.9600" vt100 on secure > ttyu1 "/usr/libexec/getty std.9600" vt100 on secure > Here's what I did: box1 COM1/ttyd0 -> box2 COM1/ttyd0 -> using null modem cable box1 COM2/ttyd1 -> box3 COM1/ttyd0 -> using null modem cable On box1 I have this in /etc/ttys: ttyd0 "/usr/libexec/getty std.9600" vt100 on secure ttyd1 "/usr/libexec/getty std.9600" vt100 on secure Now if I want to connect to box1 from box2 or box3 through the serial connection it should work, right? But I only can connect to box1 from box2, because box2's COM port is connected to box1's COM1 port. >From box2 I can get a login prompt box2# cu -l /dev/cuad0 -s 9600 Connected login: ) (host.domain) (ttyd0) login: ~ [EOT] But if I try to connect to box1 from box3 - no success there. box3# cu -l /dev/cuad0 -s 9600 Connected ~ [EOT] > This means that login prompts for box1 will be spawned/available on both > serial ports (ttyu0 and ttyu1). > > If you get on box2 and do "cu -l ttyu2", this will connect you to box2's > COM3 port, which is physically connected to box1's COM1 port. Hit enter > and you should see a login: prompt for box1. > > The same applies if you get on box2 and do "cu -l ttyu3" (but for box2's > COM4 port, which is wired to box1's COM2 port). > > With the above configuration in mind, you SHOULD NOT: > > - Mess with /etc/ttys on box2 > - Execute "cu -l ttyu0" or "cu -l ttyu1" on box1 -- this probably won't > work (likely will return some message about the device being locked or > in use already). > > You cannot do something like where box1 COM1 is wired to box2 COM1, and > depending on what box you're on doing the "cu -l ttyu0" from, get a > login prompt on the other. It doesn't work like that. :-) > > Now, about actual *serial console* itself -- that is to say, kernel > output during boot, etc... on a serial port. AFAIK, on FreeBSD you can > only set serial console to a single serial port, and that defaults to > COM1/ttyu0. You can change what port/device, but there can only be one. > > Yes, probably I didn't explain myself better, but you did it good - what I was trying to say is that I can use only one COM port for serial console, which of course defaults to COM1. Also is conserver/conserver-com able to handle more than one serial consoles on a machine? I haven't tried conserver yet. Thanks for the good explanation again :) Marin > HTH... > Now > > > On Sun, Jan 17, 2010 at 3:32 PM, Ronald Klop < > ronald-freeb...@klop.yi.org>wrote: > > > > > On Fri, 15 Jan 2010 07:34:17 +0100, Marin Atanasov > > > wrote: > > > > > > Thank you a lot for your feedback! > > >> > > >> Now to the real question again, because I'm a little confused now - > can I > > >> still get a usb-to-serial port converter having let's say 8 serial > ports > > >> and > > >> then connect each machine to the usb-to-serial hub and manage them > > >> remotely > > >> from a single location (the host having the usb-to-serial hub)? That > way I > > >> just specify a serial port number and I get to a specific machine? > > >> > > >> The model provided by Boris looks nice, and that was my initial idea, > but > > >> I'm not sure if I could get it working under FreeBSD. Is conserver or > >
Re: Multiple serial consoles via null modem cable
On Wed, Jan 20, 2010 at 08:46:48AM +0200, Marin Atanasov wrote: > Hello, > > Using `cu' only works with COM1 for me. > > Currently I have two serial ports on the system, and only the first is able > to make the connection - the serial consoles are enabled in /etc/tty, but as > I said only COM1 is able to make the connection. I'm a little confused by this statement, so I'll add some clarify: /etc/ttys is for configuring a machine to tie getty (think login prompt) to a device (in this case, a serial port). Meaning: the device on the other end of the serial cable will start seeing "login:" and so on assuming you attach to the serial port there. For example: box1 COM1/ttyu0 is wired to box2 COM3/ttyu2 using a null modem cable. box1 COM2/ttyu1 is wired to box2 COM4/ttyu3 using a null modem cable. On box1, you'd have something like this in /etc/ttys: ttyu0 "/usr/libexec/getty std.9600" vt100 on secure ttyu1 "/usr/libexec/getty std.9600" vt100 on secure This means that login prompts for box1 will be spawned/available on both serial ports (ttyu0 and ttyu1). If you get on box2 and do "cu -l ttyu2", this will connect you to box2's COM3 port, which is physically connected to box1's COM1 port. Hit enter and you should see a login: prompt for box1. The same applies if you get on box2 and do "cu -l ttyu3" (but for box2's COM4 port, which is wired to box1's COM2 port). With the above configuration in mind, you SHOULD NOT: - Mess with /etc/ttys on box2 - Execute "cu -l ttyu0" or "cu -l ttyu1" on box1 -- this probably won't work (likely will return some message about the device being locked or in use already). You cannot do something like where box1 COM1 is wired to box2 COM1, and depending on what box you're on doing the "cu -l ttyu0" from, get a login prompt on the other. It doesn't work like that. :-) Now, about actual *serial console* itself -- that is to say, kernel output during boot, etc... on a serial port. AFAIK, on FreeBSD you can only set serial console to a single serial port, and that defaults to COM1/ttyu0. You can change what port/device, but there can only be one. HTH... > On Sun, Jan 17, 2010 at 3:32 PM, Ronald Klop > wrote: > > > On Fri, 15 Jan 2010 07:34:17 +0100, Marin Atanasov > > wrote: > > > > Thank you a lot for your feedback! > >> > >> Now to the real question again, because I'm a little confused now - can I > >> still get a usb-to-serial port converter having let's say 8 serial ports > >> and > >> then connect each machine to the usb-to-serial hub and manage them > >> remotely > >> from a single location (the host having the usb-to-serial hub)? That way I > >> just specify a serial port number and I get to a specific machine? > >> > >> The model provided by Boris looks nice, and that was my initial idea, but > >> I'm not sure if I could get it working under FreeBSD. Is conserver or > >> conserver-com able to handle this? I know that cu uses COM1 only, but will > >> conserver able to handle serial consoles on different ports, since the > >> usb-to-serial port would appear as multiple serial ports. > >> > > > > You can provide cu with the port to connect to on the command line. > > > > cu -l cuaU0 -s 115200 > > cu -l cuaU1 -s 115200 > > etc. > > > > You can not connect several servers on 1 serial port, but you can connect > > several servers on several serial ports. With serial-over-usb it scales to > > many serial ports. > > > > Ronald. > > > > > >> Thank you and regards, > >> Marin > >> > >> > >> On Tue, Jan 12, 2010 at 7:04 PM, Boris Samorodov wrote: > >> > >> On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote: > >>> > >>> > I'm thinking about the following situation - 1 system acting like a > >>> host > >>> > with a serial port hub, each port of the hub is connected to a > >>> different > >>> > machine on sio0, using null modem cables. > >>> > >>> Along with milti-io serial cards we use multi-usb serial > >>> converters, such as SUNIX UTS7009P (7 USB to serial adapter): > >>> http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
Hello, Using `cu' only works with COM1 for me. Currently I have two serial ports on the system, and only the first is able to make the connection - the serial consoles are enabled in /etc/tty, but as I said only COM1 is able to make the connection. Regards, Marin On Sun, Jan 17, 2010 at 3:32 PM, Ronald Klop wrote: > On Fri, 15 Jan 2010 07:34:17 +0100, Marin Atanasov > wrote: > > Thank you a lot for your feedback! >> >> Now to the real question again, because I'm a little confused now - can I >> still get a usb-to-serial port converter having let's say 8 serial ports >> and >> then connect each machine to the usb-to-serial hub and manage them >> remotely >> from a single location (the host having the usb-to-serial hub)? That way I >> just specify a serial port number and I get to a specific machine? >> >> The model provided by Boris looks nice, and that was my initial idea, but >> I'm not sure if I could get it working under FreeBSD. Is conserver or >> conserver-com able to handle this? I know that cu uses COM1 only, but will >> conserver able to handle serial consoles on different ports, since the >> usb-to-serial port would appear as multiple serial ports. >> > > You can provide cu with the port to connect to on the command line. > > cu -l cuaU0 -s 115200 > cu -l cuaU1 -s 115200 > etc. > > You can not connect several servers on 1 serial port, but you can connect > several servers on several serial ports. With serial-over-usb it scales to > many serial ports. > > Ronald. > > > > >> Thank you and regards, >> Marin >> >> >> On Tue, Jan 12, 2010 at 7:04 PM, Boris Samorodov wrote: >> >> On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote: >>> >>> > I'm thinking about the following situation - 1 system acting like a >>> host >>> > with a serial port hub, each port of the hub is connected to a >>> different >>> > machine on sio0, using null modem cables. >>> >>> Along with milti-io serial cards we use multi-usb serial >>> converters, such as SUNIX UTS7009P (7 USB to serial adapter): >>> http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm >>> >>> -- >>> WBR, Boris Samorodov (bsam) >>> Research Engineer, http://www.ipt.ru Telephone & Internet SP >>> FreeBSD Committer, http://www.FreeBSD.org The Power To Serve >>> >>> >> >> >> > -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On Fri, 15 Jan 2010 07:34:17 +0100, Marin Atanasov wrote: Thank you a lot for your feedback! Now to the real question again, because I'm a little confused now - can I still get a usb-to-serial port converter having let's say 8 serial ports and then connect each machine to the usb-to-serial hub and manage them remotely from a single location (the host having the usb-to-serial hub)? That way I just specify a serial port number and I get to a specific machine? The model provided by Boris looks nice, and that was my initial idea, but I'm not sure if I could get it working under FreeBSD. Is conserver or conserver-com able to handle this? I know that cu uses COM1 only, but will conserver able to handle serial consoles on different ports, since the usb-to-serial port would appear as multiple serial ports. You can provide cu with the port to connect to on the command line. cu -l cuaU0 -s 115200 cu -l cuaU1 -s 115200 etc. You can not connect several servers on 1 serial port, but you can connect several servers on several serial ports. With serial-over-usb it scales to many serial ports. Ronald. Thank you and regards, Marin On Tue, Jan 12, 2010 at 7:04 PM, Boris Samorodov wrote: On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote: > I'm thinking about the following situation - 1 system acting like a host > with a serial port hub, each port of the hub is connected to a different > machine on sio0, using null modem cables. Along with milti-io serial cards we use multi-usb serial converters, such as SUNIX UTS7009P (7 USB to serial adapter): http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
Yeap, that makes sense :) Thank you, I'm gonna try it as soon as I get that device :) Thanks again, Marin On Fri, Jan 15, 2010 at 8:45 AM, Jeremy Chadwick wrote: > On Fri, Jan 15, 2010 at 08:34:17AM +0200, Marin Atanasov wrote: > > Thank you a lot for your feedback! > > > > Now to the real question again, because I'm a little confused now - can I > > still get a usb-to-serial port converter having let's say 8 serial ports > and > > then connect each machine to the usb-to-serial hub and manage them > remotely > > from a single location (the host having the usb-to-serial hub)? That way > I > > just specify a serial port number and I get to a specific machine? > > > > The model provided by Boris looks nice, and that was my initial idea, but > > I'm not sure if I could get it working under FreeBSD. Is conserver or > > conserver-com able to handle this? I know that cu uses COM1 only, but > will > > conserver able to handle serial consoles on different ports, since the > > usb-to-serial port would appear as multiple serial ports. > > I'm referencing the product Charles showed, but the topology would look > like this: > > ++ > | USB to serial hub| > | U1 FreeBSD box running conserver > || > || > +-P1---P2---P3---P4---..-+ > |||| > |||| > |||`-- box #4 > ||`--- box #3 > |` box #2 > `- box #1 > > "U1" is the uplink port, which has to connect to something -- in this > case the FreeBSD box where conserver would run. The uplink port would > connect to a single USB port on the FreeBSD box. > > The cabling between a port (Px) and a box would be serial (probably > DB9). > > What you end up with on the FreeBSD box is a series of /dev entries > which are associated with all of the ports on the USB to serial hub, > using ucom(4). For example: > > /dev/ttyU0 = P1 = box #1 > /dev/ttyU1 = P2 = box #2 > ... > > You'd then tell conserver using its configuration file that "box name > foo is attached to /dev/ttyU0, box name bar is attached to /dev/ttyU1" > and so on. > > Then to get access to the serial console of either foo or bar, you'd SSH > to the FreeBSD machine and type "console foo" or "console bar". Voila. > > Make sense? > > -- > | Jeremy Chadwick j...@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On Fri, Jan 15, 2010 at 08:34:17AM +0200, Marin Atanasov wrote: > Thank you a lot for your feedback! > > Now to the real question again, because I'm a little confused now - can I > still get a usb-to-serial port converter having let's say 8 serial ports and > then connect each machine to the usb-to-serial hub and manage them remotely > from a single location (the host having the usb-to-serial hub)? That way I > just specify a serial port number and I get to a specific machine? > > The model provided by Boris looks nice, and that was my initial idea, but > I'm not sure if I could get it working under FreeBSD. Is conserver or > conserver-com able to handle this? I know that cu uses COM1 only, but will > conserver able to handle serial consoles on different ports, since the > usb-to-serial port would appear as multiple serial ports. I'm referencing the product Charles showed, but the topology would look like this: ++ | USB to serial hub| | U1 FreeBSD box running conserver || || +-P1---P2---P3---P4---..-+ |||| |||| |||`-- box #4 ||`--- box #3 |` box #2 `- box #1 "U1" is the uplink port, which has to connect to something -- in this case the FreeBSD box where conserver would run. The uplink port would connect to a single USB port on the FreeBSD box. The cabling between a port (Px) and a box would be serial (probably DB9). What you end up with on the FreeBSD box is a series of /dev entries which are associated with all of the ports on the USB to serial hub, using ucom(4). For example: /dev/ttyU0 = P1 = box #1 /dev/ttyU1 = P2 = box #2 ... You'd then tell conserver using its configuration file that "box name foo is attached to /dev/ttyU0, box name bar is attached to /dev/ttyU1" and so on. Then to get access to the serial console of either foo or bar, you'd SSH to the FreeBSD machine and type "console foo" or "console bar". Voila. Make sense? -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
Thank you a lot for your feedback! Now to the real question again, because I'm a little confused now - can I still get a usb-to-serial port converter having let's say 8 serial ports and then connect each machine to the usb-to-serial hub and manage them remotely from a single location (the host having the usb-to-serial hub)? That way I just specify a serial port number and I get to a specific machine? The model provided by Boris looks nice, and that was my initial idea, but I'm not sure if I could get it working under FreeBSD. Is conserver or conserver-com able to handle this? I know that cu uses COM1 only, but will conserver able to handle serial consoles on different ports, since the usb-to-serial port would appear as multiple serial ports. Thank you and regards, Marin On Tue, Jan 12, 2010 at 7:04 PM, Boris Samorodov wrote: > On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote: > > > I'm thinking about the following situation - 1 system acting like a host > > with a serial port hub, each port of the hub is connected to a different > > machine on sio0, using null modem cables. > > Along with milti-io serial cards we use multi-usb serial > converters, such as SUNIX UTS7009P (7 USB to serial adapter): > http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm > > -- > WBR, Boris Samorodov (bsam) > Research Engineer, http://www.ipt.ru Telephone & Internet SP > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve > -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On 2010-Jan-12 08:08:16 -0800, Jeremy Chadwick wrote: [serial to TCP/IP adapters] >As far as present-day devices go, the ones I can recommend are the ... > >You can also consider looking for used hardware -- either Xyplex devices DECservers are good for this sort of thing as well. AFAIK we're still using them at work. I've also used the Digiboard Xem adapters quite successfully on both FreeBSD and Solaris. Unfortunately, they are a bit tempramental on FreeBSD: They can't share interrupts (you get interrupt storms if you attempt it), digi(4) is limited to 16 ports (no expansion boxes) and digi(4) hasn't been adapted to the new TTY subsystem and so won't work on FreeBSD 8. >There's two ports which can make interfacing/using these devices, or a >multiport serial card, much easier -- Conserver[3]. I work with the guy >who wrote it, so I'm biased. :-) I can also thoroughly recommend conserver-com - as well as handling local serial devices, it can talk to serial-over-TCP ports, handles logging, distributed master/client hosts and allowed multiple people to connect to a single serial port (though only one person has write access at a time). Note that it's embedded in the LOM processor on (eg) Sun v20Z. -- Peter Jeremy pgpQuOWSWr7aw.pgp Description: PGP signature
Re: Multiple serial consoles via null modem cable
On Tue, 12 Jan 2010, Jeremy Chadwick wrote: On Tue, Jan 12, 2010 at 02:50:29PM -0500, Charles Sprickman wrote: On Tue, 12 Jan 2010, Charles Sprickman wrote: On Jan 12, 2010, at 12:04 PM, Boris Samorodov wrote: On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote: I'm thinking about the following situation - 1 system acting like a host with a serial port hub, each port of the hub is connected to a different machine on sio0, using null modem cables. Along with milti-io serial cards we use multi-usb serial converters, such as SUNIX UTS7009P (7 USB to serial adapter): http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm I need to look it up when I'm in front of a real computer, but there are a number of reasonably priced multport USB to serial converters out there. Here we go: http://www.usbgear.com/USB-Serial.html Some very cool stuff there. They also list the chipset used in some of those so you have some idea if it will work with FreeBSD. I think Vixie originally pointed me to this model: http://www.usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RM&cats=199&catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 If anyone has the lowdown on which chipsets generally work with FreeBSD (especially with all the changes in 8.0), that would be great. The same device appears here: http://www.serialgear.com/USB-16COM-RM.html http://www.allserial.com/usb_16com-rm.html Damn, $130 more than usbgear.com... Quite inexpensive compared to an actual serial console server! Very much so! And if you already have a sort of "utility box" in a rack, this makes a nice add-on. There are some very cheap 4 and 8 port models as well. I had no idea such a device existed (well, USB-to-serial adapters, sure, just not ones which housed 16 adapters or was rack-mountable. :-) ). Who knows what's inside, there are two USB hubs in there... But yeah, rack-mount and AC power are nice. Decently sized FIFO buffers as well (128/384 byte Tx/Rx), at least compared to a classic 16650A (14/16 byte Tx/Rx). Usually larger FIFO == can handle higher bps without character loss. I've 5 questions about this device: * Does it work with/use hardware flow control (CTS/RTS)? Yes. There were a few machines that were giving me issues with the old 3-wire RocketPort card we had (which only had 8 ports, cost more *used* than this USB thing cost new, had buggy drivers, and only had a 3-wire interface) and they worked fine when moved to this device. * Have you tested it for character loss at 115200bps rates? Nope, never had much luck getting everything (BIOS, loader, getty) all talking at the same speed, so I just leave it at 9600. Zero issues though... * How do you configure each port (speed, flow, etc.)? I let conserver deal with that - I set the baud, parity and "options" in the default stanza for all ports. It apparently does the "right thing" when opening the port. Again, zero issues. * Does it work under FreeBSD 8.x (given that the entire USB stack was re-written)? No idea, don't even have an 8.x machine at that site. If you have any contacts over at ISC, you might ask there, I got the impression from Vixie that this device became part of their standard co-lo build. * Do you have any idea what the power usage is on this device (in amps)? (Our MRV claims 1A max, but drives about 0.25A or so). No clue, but I imagine it's negligible. The device generates almost no heat, and all of that is in the area around the power supply. The above model works great on an old 4.11 box. It's an FTDI chipset - at the very bottom of the page they even claim FreeBSD and OpenBSD support. dmesg: uhub2: Genesys Logic USB Hub, class 9/0, rev 1.01/0.11, addr 2 uhub2: 7 ports with 7 removable, self powered ucom0: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 3 [...] ucom11: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 8 [...] uhub3: Genesys Logic USB Hub, class 9/0, rev 1.01/0.12, addr 9 uhub3: 4 ports with 4 removable, self powered ucom12: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 10 [...] ucom15: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 11 Very nice -- the fact they're using FTDI chips is good (from what I understand of USB-to-serial adapters). Yep, this was all plug-and-play. I also found a source for db9-db9 null modem cables at about $3 a pop - much simpler than building rj-xx to db9 adapters (xyplex, rocketport) or dealing with giant harnesses (cisco, xylogics). We have a 16 port model that's rack mounted and cost around $400. It works better many of the more expensive multiport serial cards. Paired with conserver, it's a really nice solution. Conserver's logging is great... I've used old dedicated terminal servers in the past and they can be a pain to deal with. The newer ones are probably nicer, but are also lots of money. Cla
Re: Multiple serial consoles via null modem cable
On Tue, 2010-01-12 at 17:14 +0200, Marin Atanasov wrote: > Hello there, > > I'd like to ask you about the following - is it possible to have multiple > serial consoles coming from a single host? > > What I am talking about is connecting multiple machines using a null modem > cable - I know it is possible only to connect two machines and they need to > be connected on sio0 (COM1). > > I'm thinking about the following situation - 1 system acting like a host > with a serial port hub, each port of the hub is connected to a different > machine on sio0, using null modem cables. > > This would make the first machine something like a cheaper kind of a > terminal concentrator :) > > What do you think, have someone tried this and is it possible at all? I have a dozen UBS2serial (uplcom) up 24/7 over more than 6 months, on 8.0 (NanoBSD on ITX-board) in our serverrooms. They work pretty stable and are dead cheap. Max 20 Euro per line, including a null-modem adapter. like: http://www.gridconnect.com/numomatomadb.html or http://www.buyextras.com/numoaddb9fef.html I payed about ~3 dollars per adapter. (shipping to Europe was most expensive) Kind regards, Marten > > Thanks and regards, > DNAeon > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- http://www.voedselbankleiden.nl needs your help! http://martenvijn.nl http://bsd.wifisoft.org/nek/ http://opencommunitycamp.org OCC 2010 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On Tue, Jan 12, 2010 at 02:50:29PM -0500, Charles Sprickman wrote: > On Tue, 12 Jan 2010, Charles Sprickman wrote: > > >On Jan 12, 2010, at 12:04 PM, Boris Samorodov wrote: > > > >>On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote: > >> > >>>I'm thinking about the following situation - 1 system acting like a host > >>>with a serial port hub, each port of the hub is connected to a different > >>>machine on sio0, using null modem cables. > >> > >>Along with milti-io serial cards we use multi-usb serial > >>converters, such as SUNIX UTS7009P (7 USB to serial adapter): > >>http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm > >> > > > >I need to look it up when I'm in front of a real computer, but > >there are a number of reasonably priced multport USB to serial > >converters out there. > > Here we go: > > http://www.usbgear.com/USB-Serial.html > > Some very cool stuff there. They also list the chipset used in some > of those so you have some idea if it will work with FreeBSD. I > think Vixie originally pointed me to this model: > > http://www.usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RM&cats=199&catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 > > If anyone has the lowdown on which chipsets generally work with > FreeBSD (especially with all the changes in 8.0), that would be > great. The same device appears here: http://www.serialgear.com/USB-16COM-RM.html http://www.allserial.com/usb_16com-rm.html Quite inexpensive compared to an actual serial console server! I had no idea such a device existed (well, USB-to-serial adapters, sure, just not ones which housed 16 adapters or was rack-mountable. :-) ). Decently sized FIFO buffers as well (128/384 byte Tx/Rx), at least compared to a classic 16650A (14/16 byte Tx/Rx). Usually larger FIFO == can handle higher bps without character loss. I've 5 questions about this device: * Does it work with/use hardware flow control (CTS/RTS)? * Have you tested it for character loss at 115200bps rates? * How do you configure each port (speed, flow, etc.)? * Does it work under FreeBSD 8.x (given that the entire USB stack was re-written)? * Do you have any idea what the power usage is on this device (in amps)? (Our MRV claims 1A max, but drives about 0.25A or so). > The above model works great on an old 4.11 box. It's an FTDI > chipset - at the very bottom of the page they even claim FreeBSD and > OpenBSD support. > > dmesg: > > uhub2: Genesys Logic USB Hub, class 9/0, rev 1.01/0.11, addr 2 > uhub2: 7 ports with 7 removable, self powered > ucom0: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 3 > [...] > ucom11: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 8 > [...] > uhub3: Genesys Logic USB Hub, class 9/0, rev 1.01/0.12, addr 9 > uhub3: 4 ports with 4 removable, self powered > ucom12: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 10 > [...] > ucom15: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 11 Very nice -- the fact they're using FTDI chips is good (from what I understand of USB-to-serial adapters). > > We have a 16 port model that's rack mounted and cost around $400. > >It works better many of the more expensive multiport serial cards. > >Paired with conserver, it's a really nice solution. Conserver's > >logging is great... > > > >I've used old dedicated terminal servers in the past and they can > >be a pain to deal with. The newer ones are probably nicer, but > >are also lots of money. Classic devices (like the Portmaster) are indeed a pain in the butt to deal with. I've no experience with Ciscos, but in the case of the PM, documentation vs. implementation mismatch galore. The MRV devices are thoroughly documented (it borders on overwhelming -- I'd say half of the configuration parameters are foreign to me), and I think the Cyclades TS devices are as well; it's the cost of the Cyclades which blows my mind (zero justification for it too, other than "enterprise cost mentality", e.g. charge as much as possible because large businesses will pay it). I think for folks who want a multiport serial console device that sits on Ethernet, the MRV or Cyclades device would be a good choice, since it's a standalone unit which doesn't need to be physically cabled to a "host" box (and often a good choice for those who want modem-based OOB access to devices, since it can house a v.90 modem). For those with less requirements and want to spend less, the above USB-to-serial device looks fantastic -- and at almost 1/4th the cost of our MRV. :-) As usual, thanks for the insights, Charles! -- | Jeremy Chadwick
Re: Multiple serial consoles via null modem cable
On Tue, 12 Jan 2010, Charles Sprickman wrote: On Jan 12, 2010, at 12:04 PM, Boris Samorodov wrote: On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote: I'm thinking about the following situation - 1 system acting like a host with a serial port hub, each port of the hub is connected to a different machine on sio0, using null modem cables. Along with milti-io serial cards we use multi-usb serial converters, such as SUNIX UTS7009P (7 USB to serial adapter): http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm I need to look it up when I'm in front of a real computer, but there are a number of reasonably priced multport USB to serial converters out there. Here we go: http://www.usbgear.com/USB-Serial.html Some very cool stuff there. They also list the chipset used in some of those so you have some idea if it will work with FreeBSD. I think Vixie originally pointed me to this model: http://www.usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RM&cats=199&catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 If anyone has the lowdown on which chipsets generally work with FreeBSD (especially with all the changes in 8.0), that would be great. The above model works great on an old 4.11 box. It's an FTDI chipset - at the very bottom of the page they even claim FreeBSD and OpenBSD support. dmesg: uhub2: Genesys Logic USB Hub, class 9/0, rev 1.01/0.11, addr 2 uhub2: 7 ports with 7 removable, self powered ucom0: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 3 [...] ucom11: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 8 [...] uhub3: Genesys Logic USB Hub, class 9/0, rev 1.01/0.12, addr 9 uhub3: 4 ports with 4 removable, self powered ucom12: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 10 [...] ucom15: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 11 Charles We have a 16 port model that's rack mounted and cost around $400. It works better many of the more expensive multiport serial cards. Paired with conserver, it's a really nice solution. Conserver's logging is great... I've used old dedicated terminal servers in the past and they can be a pain to deal with. The newer ones are probably nicer, but are also lots of money. C -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On Jan 12, 2010, at 12:04 PM, Boris Samorodov wrote: On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote: I'm thinking about the following situation - 1 system acting like a host with a serial port hub, each port of the hub is connected to a different machine on sio0, using null modem cables. Along with milti-io serial cards we use multi-usb serial converters, such as SUNIX UTS7009P (7 USB to serial adapter): http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm I need to look it up when I'm in front of a real computer, but there are a number of reasonably priced multport USB to serial converters out there. We have a 16 port model that's rack mounted and cost around $400. It works better many of the more expensive multiport serial cards. Paired with conserver, it's a really nice solution. Conserver's logging is great... I've used old dedicated terminal servers in the past and they can be a pain to deal with. The newer ones are probably nicer, but are also lots of money. C -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org " ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote: > I'm thinking about the following situation - 1 system acting like a host > with a serial port hub, each port of the hub is connected to a different > machine on sio0, using null modem cables. Along with milti-io serial cards we use multi-usb serial converters, such as SUNIX UTS7009P (7 USB to serial adapter): http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On Tue, 12 Jan 2010 08:08:16 -0800 Jeremy Chadwick wrote: > Yes this is possible with FreeBSD -- but you'll need to purchase a And easy enough with conserver[1] and conserver-com[2] in ports. No reason to exclude FreeBSD from this task. :) References: 1) http://www.freshports.org/comms/conserver/ 2) http://www.freshports.org/comms/conserver-com/ -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
Hi Marin, I'd like to ask you about the following - is it possible to have multiple > serial consoles coming from a single host? > In theory, no :-) RS232 is a point-to-point connection. If you want to feed several consoles through the same serial port, you will need some kind of switch to route the traffic to the corresponding port (whether the cable needs to be null modem or not wil depend on the switch itself). What I am talking about is connecting multiple machines using a null modem > cable - I know it is possible only to connect two machines and they need to > be connected on sio0 (COM1). > > I'm thinking about the following situation - 1 system acting like a host > with a serial port hub, each port of the hub is connected to a different > machine on sio0, using null modem cables. > > This would make the first machine something like a cheaper kind of a > terminal concentrator :) > The options that come up to my mind are: - a mechanical switch but it would not allow seamless routing (requires operator action to change channel) - a software switch using ESCAPE codes to change channel through an ad-hoc device driver - but there, make sure you don't miss bytes or the traffic may end up on the wrong terminal - if you fancy a home design, you could use the parallel port to send an address word but you will have to design your own seial port emulation on top of the standard sio0 to synchronize the signals... I would not bet too much on this one ;-) Also, evaluate if you need priority management: you may get to a situation where you need to send urgently characters to a terminal while another one has a long queue pending. In this case, you may be better off with Ethernet-to-Serial or USB-to-Serial converters. Hope it helps Cheers -- Olivier Gautherot oliv...@gautherot.net Cel:+56 98 730 9361 www.gautherot.net http://www.linkedin.com/in/ogautherot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On 12/01/2010 16:08, Jeremy Chadwick wrote: > On Tue, Jan 12, 2010 at 05:14:44PM +0200, Marin Atanasov wrote: >> Hello there, >> >> I'd like to ask you about the following - is it possible to have multiple >> serial consoles coming from a single host? >> >> What I am talking about is connecting multiple machines using a null modem >> cable - I know it is possible only to connect two machines and they need to >> be connected on sio0 (COM1). >> >> I'm thinking about the following situation - 1 system acting like a host >> with a serial port hub, each port of the hub is connected to a different >> machine on sio0, using null modem cables. >> >> This would make the first machine something like a cheaper kind of a >> terminal concentrator :) >> >> What do you think, have someone tried this and is it possible at all? > > What you're describing is basically the concept of a serial console > server, where a FreeBSD box contains a multi-port serial card that's > connected to multiple other servers. An individual would get on the > FreeBSD box with a multiport serial card (see below) and attach to the > serial port associated (wired to) whatever other box they want to log on > to. > > Yes this is possible with FreeBSD -- but you'll need to purchase a > multiport serial card that's supported natively by FreeBSD. The two I'm > familiar with are Cyclades and DigiBoard, but this would've been back in > the day of FreeBSD 2.2.x and I've no idea what people use present-day. > I'm certain others here can recommend stuff that works. You've actually mentioned one here, Digi. They make console devices and I've used, with great success. Ours had modems as well so we had a normal TCP and a phone line for DR. There is a range of sizes, SSH2 and some have 2 psu's. They have American as well as European providers, though I can't remember where we purchased ours from. We didn't use ours on servers however, they where just for switches, routers, load balancers et al so I can't comment on how well they worked with those, but I can't see it being any different. http://www.digi.com/products/consoleservers/digicm.jsp ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On Tue, Jan 12, 2010 at 05:14:44PM +0200, Marin Atanasov wrote: > Hello there, > > I'd like to ask you about the following - is it possible to have multiple > serial consoles coming from a single host? > > What I am talking about is connecting multiple machines using a null modem > cable - I know it is possible only to connect two machines and they need to > be connected on sio0 (COM1). > > I'm thinking about the following situation - 1 system acting like a host > with a serial port hub, each port of the hub is connected to a different > machine on sio0, using null modem cables. > > This would make the first machine something like a cheaper kind of a > terminal concentrator :) > > What do you think, have someone tried this and is it possible at all? What you're describing is basically the concept of a serial console server, where a FreeBSD box contains a multi-port serial card that's connected to multiple other servers. An individual would get on the FreeBSD box with a multiport serial card (see below) and attach to the serial port associated (wired to) whatever other box they want to log on to. Yes this is possible with FreeBSD -- but you'll need to purchase a multiport serial card that's supported natively by FreeBSD. The two I'm familiar with are Cyclades and DigiBoard, but this would've been back in the day of FreeBSD 2.2.x and I've no idea what people use present-day. I'm certain others here can recommend stuff that works. But my personal/professional opinion is that you consider purchasing an actual serial console server rather than "hack up" a FreeBSD box. Most serial console servers these days (and even old Portmasters) can do serial-to-TCP association, which allows you to literally do "telnet consoleserver " where is a TCP port which is bound to a serial port connected to each individual server. E.g. port 2000 = box#1, port 2100 = box#2, etc.. As far as present-day devices go, the ones I can recommend are the LX-series devices[1] from MRV Communications. They're Linux-based, and although may seem expensive (16-port w/out modem = ~US$1400), are a one-time purchase. Cyclades also makes identical devices, but they cost something like US$3000-4000, and they wouldn't provide me with a test/demo unit so I blew 'em off. You can also consider looking for used hardware -- either Xyplex devices (MRV bought Xyplex), or Portmaster[2] products. I believe Cisco made some devices as well. WRT Portmasters, be aware that some of the firmware images are spotty in quality (HELP commands missing, undocumented commands, etc.). There's two ports which can make interfacing/using these devices, or a multiport serial card, much easier -- Conserver[3]. I work with the guy who wrote it, so I'm biased. :-) ports/comms/conserver ports/comms/conserver-com I'm not sure what the first port is to be honest, but the 2nd port is what I'm used to using with an MRV LX-4016S device. If you'd like a bit more detail about "how it all works" (the software, the hardware, configuration details, wiring, etc.), I can describe it in greater detail. Just ask. [1]: http://www.mrv.com/oobn/ [2]: http://portmasters.com/ [3]: http://www.conserver.com/ -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Multiple serial consoles via null modem cable
Hello there, I'd like to ask you about the following - is it possible to have multiple serial consoles coming from a single host? What I am talking about is connecting multiple machines using a null modem cable - I know it is possible only to connect two machines and they need to be connected on sio0 (COM1). I'm thinking about the following situation - 1 system acting like a host with a serial port hub, each port of the hub is connected to a different machine on sio0, using null modem cables. This would make the first machine something like a cheaper kind of a terminal concentrator :) What do you think, have someone tried this and is it possible at all? Thanks and regards, DNAeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: GSM Modem versus GSM Telemetry
Exemys wrote: [ Charset ISO-8859-1 unsupported, converting... ] > This is a message in multipart MIME format. Your mail client should > not be displaying this. Consider upgrading your mail client to view > this message correctly. Come again? Alphons -- All right, that does it Bill [Donahue]. I'm pretty sure that killing Jesus is not very Christian. -- Pope Benedict XVI, Southpark season 11 episode 5 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
GSM Modem versus GSM Telemetry
This is a message in multipart MIME format. Your mail client should not be displaying this. Consider upgrading your mail client to view this message correctly. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Curitel PC5740 Wireless Modem (EVDO)
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
[EMAIL PROTECTED]:/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=0x clss=0x0002 subclss=0x
prtcl=0x
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 AddressSize Name
1 13 0xc040 47ca94 kernel
21 0xc087d000 45b8 snd_t4dwave.ko
32 0xc0882000 22b88sound.ko
41 0xc08a5000 3000 uftdi.ko <<<<
52 0xc08a8000 32a8 ucom.ko<<<<
61 0xc08ac000 59fa4acpi.ko
71 0xc2c4e000 16000linux.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
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Curitel PC5740 Wireless Modem (EVDO)
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 >[EMAIL PROTECTED]:/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) > >UMODEM(4) FreeBSD Kernel Interfaces Manual >UMODEM(4) >NAME > umodem -- USB modem support >SYNOPSIS > device umodem > device ucom >DESCRIPTION > The umodem driver provides support for USB modems in the >Communication > Device Class using the Abstract Control Model. ... > > The device is accessed through the ucom(4) driver which makes >it behave > like a tty(4). > >HARDWARE > Devices supported by the umodem driver include: > > o 3Com 5605 > o Curitel PC5740 Wireless Modem > o Metricom Ricochet GS USB wireless modem >... > > As stated above 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_CTRLR_ATTACH >USB_EVENT_CTRLR_ATTACH >usbd: driver-attach event cookie=4 devname=uhub2 >USB_EVENT_DRIVER_ATTACH >USB_EVENT_DRIVER_ATTACH >usbd: device-attach event at 1167852825.963798000, OHCI root hub, NEC: > vndr=0x prdct=0x rlse=0x0100 clss=0x0009 subclss=0x >prtcl=0x > device names: uhub2 >usbd: Found action 'USB device' for OHCI root hub, NEC at uhub2 >usbd: ctrlr-attach event bus=3 >USB_EVENT_CTRLR_ATTACH >USB_EVENT_CTRLR_ATTACH >usbd: driver-attach event cookie=5 devname=uhub3 >USB_EVENT_DRIVER_ATTACH >USB_EVENT_DRIVER_ATTACH >usbd: device-attach event at 1167852826.599332000, OHCI root hub, NEC: > vndr=0x prdct=0x rlse=0x0100 clss=0x0009 subclss=0x >prtcl=0x > device names: uhub3 >usbd: Found action 'USB device' for OHCI root hub, NEC at uhub3 >usbd: driver-attach event cookie=6 devname=ugen0 >USB_EVENT_DRIVER_ATTACH >USB_EVENT_DRIVER_ATTACH >usbd: device-attach event at 1167852828.349083000, Curitel >Communications, Inc., Curitel Communications, Inc.: > vndr=0x106c prdct=0x3701 rlse=0x clss=0x0002 subclss=0x >prtcl=0x > 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 AddressSize Name > 1 13 0xc040 47ca94 kernel > 21 0xc087d000 45b8 snd_t4dwave.ko > 32 0xc0882000 22b88sound.ko > 41 0xc08a5000 3000 uftdi.ko <<<< > 52 0xc08a8000 32a8 ucom.ko<<<< > 61 0xc08ac000 59fa4acpi.ko > 71 0xc2c4e000 16000linux.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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Curitel PC5740 Wireless Modem (EVDO)
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
[EMAIL PROTECTED]:/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)
UMODEM(4) FreeBSD Kernel Interfaces Manual
UMODEM(4)
NAME
umodem -- USB modem support
SYNOPSIS
device umodem
device ucom
DESCRIPTION
The umodem driver provides support for USB modems in the
Communication
Device Class using the Abstract Control Model. ...
The device is accessed through the ucom(4) driver which makes
it behave
like a tty(4).
HARDWARE
Devices supported by the umodem driver include:
o 3Com 5605
o Curitel PC5740 Wireless Modem
o Metricom Ricochet GS USB wireless modem
...
As stated above 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_CTRLR_ATTACH
USB_EVENT_CTRLR_ATTACH
usbd: driver-attach event cookie=4 devname=uhub2
USB_EVENT_DRIVER_ATTACH
USB_EVENT_DRIVER_ATTACH
usbd: device-attach event at 1167852825.963798000, OHCI root hub, NEC:
vndr=0x prdct=0x rlse=0x0100 clss=0x0009 subclss=0x
prtcl=0x
device names: uhub2
usbd: Found action 'USB device' for OHCI root hub, NEC at uhub2
usbd: ctrlr-attach event bus=3
USB_EVENT_CTRLR_ATTACH
USB_EVENT_CTRLR_ATTACH
usbd: driver-attach event cookie=5 devname=uhub3
USB_EVENT_DRIVER_ATTACH
USB_EVENT_DRIVER_ATTACH
usbd: device-attach event at 1167852826.599332000, OHCI root hub, NEC:
vndr=0x prdct=0x rlse=0x0100 clss=0x0009 subclss=0x
prtcl=0x
device names: uhub3
usbd: Found action 'USB device' for OHCI root hub, NEC at uhub3
usbd: driver-attach event cookie=6 devname=ugen0
USB_EVENT_DRIVER_ATTACH
USB_EVENT_DRIVER_ATTACH
usbd: device-attach event at 1167852828.349083000, Curitel
Communications, Inc., Curitel Communications, Inc.:
vndr=0x106c prdct=0x3701 rlse=0x clss=0x0002 subclss=0x
prtcl=0x
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 AddressSize Name
1 13 0xc040 47ca94 kernel
21 0xc087d000 45b8 snd_t4dwave.ko
32 0xc0882000 22b88sound.ko
41 0xc08a5000 3000 uftdi.ko <<<<
52 0xc08a8000 32a8 ucom.ko<<<<
61 0xc08ac000 59fa4acpi.ko
71 0xc2c4e000 16000linux.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...)
--
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
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to connects to Linux machine via null-modem cable and cu command?
On Wednesday 11 October 2006 17:20, Oleg Dambaev wrote: > > Two questions > > 1) Is cuad0 the correct port? Have you tried cuad1? > > 2) What baud rate are you using? (the -s flag) > > Good way to try *first*: > 0. man stty > 1. use tip instead cu I prefer cu - you just specify the baud rate and tty and connect :) Of course if you aren't doing 8N1 it's a PITA but there you go. If I need "fancy" stuff (eg local echo) then I just use minicom (as un-unixlike as it is) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpJwP8d6trq7.pgp Description: PGP signature
Re: How to connects to Linux machine via null-modem cable and cu command?
Daniel O'Connor wrote: On Wednesday 11 October 2006 13:15, Sun Zongjun-E5739C wrote: I run the command on device running FreeBSD 6.1 Test# cu -l /dev/cuad0 Connected There is no response on the FreeBSD except the "Connected" string. Such string can occur even there is no cable available. What happens to cu command on FreeBSD? Two questions 1) Is cuad0 the correct port? Have you tried cuad1? 2) What baud rate are you using? (the -s flag) Good way to try *first*: 0. man stty 1. use tip instead cu ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to connects to Linux machine via null-modem cable and cu command?
On Wednesday 11 October 2006 13:15, Sun Zongjun-E5739C wrote: > I run the command on device running FreeBSD 6.1 > > Test# cu -l /dev/cuad0 > Connected > > There is no response on the FreeBSD except the "Connected" string. Such > string can occur even there is no cable available. > > What happens to cu command on FreeBSD? Two questions 1) Is cuad0 the correct port? Have you tried cuad1? 2) What baud rate are you using? (the -s flag) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpduxvEORjkC.pgp Description: PGP signature
RE: How to connects to Linux machine via null-modem cable and cu command?
Hi, Koshy Thanks for your timely reply. It is my fault configuration on the linux machine. I use linux instead of vt100 (vt102). S1:23:respawn: /sbin/agetty -L ttyS0 115200, 9600 linux Windows can work with this configuration, but cu and FreeBSD can't. I replaced it with vt100 S1:23:respawn:/sbin/agetty -L ttyS0 115200, 9600 vt100 That is OK. Thanks a lot Best Regards Sun Zongjun -Original Message- From: Joseph Koshy [mailto:[EMAIL PROTECTED] Sent: 2006年10月11日 12:02 To: Sun Zongjun-E5739C Subject: Re: How to connects to Linux machine via null-modem cable and cu command? On 10/11/06, Sun Zongjun-E5739C <[EMAIL PROTECTED]> wrote: > HI, all > > I am a newbie to FreeBSD. I want to connect one my pc running FreeBSD > 6.1 to another PC running Fedora core 5 via a null modem cable. > > I can login the PC running the Fedora Core 5 from PC running Windows > via one NULL modem cable. > > When I connect the two serial ports of two pc, one running FreeBSD6.1 > and the other is FC5 which acts a server. > > I run the command on device running FreeBSD 6.1 > > Test# cu -l /dev/cuad0 > Connected > > There is no response on the FreeBSD except the "Connected" string. > Such string can occur even there is no cable available. What happens when you hit 'Enter' a few times? > What happens to cu command on FreeBSD? One thing you could check is the expected baud-rate/parity/stop-bit settings at the server. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to connects to Linux machine via null-modem cable and cu command?
HI, all I am a newbie to FreeBSD. I want to connect one my pc running FreeBSD 6.1 to another PC running Fedora core 5 via a null modem cable. I can login the PC running the Fedora Core 5 from PC running Windows via one NULL modem cable. When I connect the two serial ports of two pc, one running FreeBSD6.1 and the other is FC5 which acts a server. I run the command on device running FreeBSD 6.1 Test# cu -l /dev/cuad0 Connected There is no response on the FreeBSD except the "Connected" string. Such string can occur even there is no cable available. What happens to cu command on FreeBSD? Thanks for your kind support. Thanks Regards Zongjun ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6-STABLE crashes when surfing via modem
Hello!
I am running FreeBSD 6-STABLE (last update 14.5.06) on a Fujitsu Siemens
Amilo A notebook. This machine has internet access via kppp and a
Creative ModemBlaster V.92 serial modem.
Sometimes when surfing on the internet (most times with Opera 8.51
AFAIR) the system completly locks up and reboots. I found
http://www.at.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
and tried to analysis the crash dump in /var/crash but I am totally new
to these things.
"kgdb kernel.debug /var/crash/vmcore.2" on my system gives the following
output:
[GDB will not be able to debug user-mode threads:
/usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
(...)
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x29
fault code = supervisor write, page not present
instruction pointer = 0x20:0xc06ad6a6
stack pointer = 0x28:0xd992f9d0
frame pointer = 0x28:0xd992fa00
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 793 (opera)
trap number = 12
panic: page fault
Uptime: 19m31s
Dumping 478 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 478MB (122352 pages) 462 446 430 414 398 382 366 350 334 318
302 286 270 254 238 222 206 190 174 158 142 126 110 94 (CTRL-C to abort)
(CTRL-C to abort) 78 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to
abort) 62 46 30 14
#0 doadump () at pcpu.h:165
165 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) quit
Has anybody an idea what goes wrong on my system? What could I do in
order to find out what goes wrong?
Many thanks in advance,
Michael
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
re:dhclient and cable modem
often is the mtu value between your machine and your internet provider /r/ wlodek ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient and cable modem
> Dear list! > For a month or two I will be connected > to cable net. So, I tried it on another > location and... did not work. Laptop > has 6.0 and "rl". I used empty dhclent. > conf and then populated it with every > option I found on the net. Firewall > got no traffic, the packet was not leaving > the box. When at home, I learned that > I had not checked ethernet possibilities. > Ifconfig shows 10tx, auto mode and no ip > address. > In this moment I'm sure that the system > works correct and that I misconfigured > something. But what? How should look > conf file? Or to add some hints to rl > on the command line. > Provider offers dhcp and no static address. > Rl sands discovery and receives no offer. > What i'm doing wrong? > Best regards Did you restart the cablemodem between change of attached computer? That might be neccessery. -- Regards from Lars > > Zoran > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dhclient and cable modem
Dear list! For a month or two I will be connected to cable net. So, I tried it on another location and... did not work. Laptop has 6.0 and "rl". I used empty dhclent. conf and then populated it with every option I found on the net. Firewall got no traffic, the packet was not leaving the box. When at home, I learned that I had not checked ethernet possibilities. Ifconfig shows 10tx, auto mode and no ip address. In this moment I'm sure that the system works correct and that I misconfigured something. But what? How should look conf file? Or to add some hints to rl on the command line. Provider offers dhcp and no static address. Rl sands discovery and receives no offer. What i'm doing wrong? Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Qualcomm modem via USB
On Tue, 1 Nov 2005 22:10, Павел Е. Черкаев wrote: > console: > ucom0: Qualcomm, Incorporated Qualcomm CDMA Technologies MSM, rev > 1.01/0.00, addr 2, iclass 2/2 > ucom0: data interface 1, has CM over data, has break > ucom0: could not set data multiplex mode > device_attach: ucom0 attach returned 6 I woulud say it's because umodem doesn't support modems that don't do multiplexed mode. See /usr/src/sys/dev/usb/umodem.c line 78. So, basically, it's an unsupported device unless someone writes the code to get it going. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp9ZrLTO72U8.pgp Description: PGP signature
Qualcomm modem via USB
console: ucom0: Qualcomm, Incorporated Qualcomm CDMA Technologies MSM, rev 1.01/0.00, addr 2, iclass 2/2 ucom0: data interface 1, has CM over data, has break ucom0: could not set data multiplex mode device_attach: ucom0 attach returned 6 #uname -a FreeBSD proxy.omk-kuzbass.ru 5.4-STABLE FreeBSD 5.4-STABLE #0: what i can add to my kernel configuration ? I need this modem :( ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: internal modem / pnp0 / FAQ error ?
From: "Oliver Fromme" <[EMAIL PROTECTED]> Subject: Re: internal modem / pnp0 / FAQ error ? > > If ltmdm doesn't support your winmodem, then it's pretty > much a dead horse. I would rather recommend to buy a real > modem. > > thanks for the reply It is a case of having equipment on hand and wanting to see if it can be made to work. I agree with your advice and will be dropping the win modem and just using an external. Pan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: internal modem / pnp0 / FAQ error ?
pan <[EMAIL PROTECTED]> wrote: > From: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html > > 4.5.2. Why is FreeBSD not finding my internal Plug & Play modem? > > You will need to add the modem's PnP ID to the PnP ID list in the serial > driver. [...] That FAQ entry is very outdated. And it does not apply to your case at all. > I have a pci winmodem The term "PnP" from the FAQ entry refers to ISA PnP cards, not to PCI cards. Furthermore, it refers to cards which are controlled by the sio driver (serial I/O), not to "win modems". It's a completely different thing. > (yes I know - plan on using ltmdm) So your winmodem card uses the Lucent chipset supported by ltmdm? If so, you only need to install ltmdm, and that's all you need to do. If ltmdm doesn't support your winmodem, then it's pretty much a dead horse. I would rather recommend to buy a real modem. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Emacs ist für mich kein Editor. Für mich ist das genau das gleiche, als wenn ich nach einem Fahrrad (für die Sonntagbrötchen) frage und einen pangalaktischen Raumkreuzer mit 10 km Gesamtlänge bekomme. Ich weiß nicht, was ich damit soll." -- Frank Klemm, de.comp.os.unix.discussion ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
internal modem / pnp0 / FAQ error ?
From: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html 4.5.2. Why is FreeBSD not finding my internal Plug & Play modem? You will need to add the modem's PnP ID to the PnP ID list in the serial driver. To enable Plug & Play support, compile a new kernel with controller pnp0 in the configuration file, then reboot the system. The kernel will print the PnP IDs of all the devices it finds. Copy the PnP ID from the modem to the table in /sys/i386/isa/sio.c, at about line 2777. Look for the string SUP1310 in the structure siopnp_ids[] to find the table. Build the kernel again, install, reboot, and your modem should be found. You may have to manually configure the PnP devices using the pnp command in the boot-time configuration with a command like pnp 1 0 enable os irq0 3 drq0 0 port0 0x2f8 to make the modem show. Compiling with the suggested line "controller pnp0" gets: "obsolete keyword 'controller' found - use 'device' o.k. Compiling with "device pnp0" gets: "Warning: device "pnp" is unknown *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src Trying the pnp enable line at boot doesn't change a thing So - is the FAQ entry an error? uname -a FreeBSD cody.npqr.net 4.11-STABLE FreeBSD 4.11-STABLE #3: Sun Apr 24 18:04:54 PDT 2005 [snip] i386 I have a pci winmodem (yes I know - plan on using ltmdm) inserted into an open pci slot. dmesg shows pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: (vendor=0x11c1, dev=0x0440) at 9.0 irq 11 pci0: at 10.0 irq 10 dc0: <82c169 PNIC 10/100BaseTX> port 0x6300-0x63ff mem 0xe4001000-0xe40010ff irq 9 at device 11.0 on pci0 Anyone know how I can really get the card recognized and maybe go on to install and get working ppp with this modem ? tia Pan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: misc/74786: Smartlink Modem causes interrupt storm on RELENG_4 and RELENG_5
[cc'ing to FreeBSD-Stable] Hi, I know that the proposed patches I submitted are not the best patches, but given that the next release of RELENG_4 is coming out, would it not be better to commit those to RELENG_4 as they allow the modem to work when it shares an interrupt with another device ? The sio and interrupt handling code in RELENG_5 is different enough that I doubt the patches you are proposing would make it back to RELENG_4. This at least lets the modem work and prevents the machine from locking up in an interrupt storm on RELENG_4 without breaking any functionality (as far as I know). ---Mike At 02:22 AM 08/12/2004, Bruce Evans wrote: I think I understand this now. sio can indeed drive the interrupt (after you open an sio device, but not immediately at the end of the attach except in the serial console case). The main bugs are: 1. sio asks for exclusive access to the interrupt for no good reason (some buses like isa might only support exclusive accesses, but sio doesn't care). uhci gets access first in your configuration, so allocation of the interrupt resource fails. 2. Error handling for the failure in (1) is null, so both devices are "successfully" attached. 3. sio sets a flag to tell it to use polling if there is no interrupt resource, but it doesn't set the flag if the interrupt resource couldn't be allocated or if the interrupt couldn't be set up. 4. Upper layers provide negative help for debugging (3) using their own version of (3). They print "irq N" in boot messages if an interrupt resource justs exists. This doesn't mean that the device is using it. 5. Device interrupts are still enabled in polling mode. This depends on nothing else sucessfully setting up the (shared) interrupt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pccard modem and ethernet don't work together
In message: <[EMAIL PROTECTED]> Ronald Klop <[EMAIL PROTECTED]> writes: : On Wed, 10 Nov 2004 01:56:09 -0700 (MST), M. Warner Losh <[EMAIL PROTECTED]> : wrote: : : > In message: <[EMAIL PROTECTED]> : > Ronald Klop <[EMAIL PROTECTED]> writes: : > : I posted the same text as below to current@ on 20 Oct, but got no : > answer. : > : Is there somebody here who knows more about this or can tell me where : > to : > : look further? : > : I got a 'me too' message from somebody who googled my previous : > question, : > : so there are more people with this problem. : > : > I ment to reply, but got busy with the release. I'll see if I can : > recreate the problem. : > : > Warner : : Thanks in advance. : I am still looking around myself and am wondering if I need to run pccardd? : I thought it was replaced by devd, but it is still in the system. : Does pccardd have more functionality than devd and is it possible that it : can solve my problem? : Or am I looking in the wrong direction? pccardd won't help. The problem is almost certainly some kind of resource allocation issue that's casuing the cards to fail. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pccard modem and ethernet don't work together
On Wed, 10 Nov 2004 01:56:09 -0700 (MST), M. Warner Losh <[EMAIL PROTECTED]> wrote: In message: <[EMAIL PROTECTED]> Ronald Klop <[EMAIL PROTECTED]> writes: : I posted the same text as below to current@ on 20 Oct, but got no answer. : Is there somebody here who knows more about this or can tell me where to : look further? : I got a 'me too' message from somebody who googled my previous question, : so there are more people with this problem. I ment to reply, but got busy with the release. I'll see if I can recreate the problem. Warner Thanks in advance. I am still looking around myself and am wondering if I need to run pccardd? I thought it was replaced by devd, but it is still in the system. Does pccardd have more functionality than devd and is it possible that it can solve my problem? Or am I looking in the wrong direction? Ronald. -- Ronald Klop, Amsterdam, The Netherlands ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pccard modem and ethernet don't work together
In message: <[EMAIL PROTECTED]> Ronald Klop <[EMAIL PROTECTED]> writes: : I posted the same text as below to current@ on 20 Oct, but got no answer. : Is there somebody here who knows more about this or can tell me where to : look further? : I got a 'me too' message from somebody who googled my previous question, : so there are more people with this problem. I ment to reply, but got busy with the release. I'll see if I can recreate the problem. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PCMCIA modem heating
In message: <[EMAIL PROTECTED]> Zoran Kolic <[EMAIL PROTECTED]> writes: : Hi all! : Don't wonna make stupid : quiestions, but this is : something I have to know : to make reclamation if neces- : sary. : After 5-10 minutes of inter- : net connection, when detached, : my pccard modem is hot as fur- : nace. I can barely take it in : my hand. Is it normal beha- : veour? : Model is Zoltrix, has "cirrus" : on the sticker. Try setting debug.mpsafenet=0 in your /boot/loader.conf. I have similar sounding issues with -current and my USB modem + ppp. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
pccard modem and ethernet don't work together
Hello, I posted the same text as below to current@ on 20 Oct, but got no answer. Is there somebody here who knows more about this or can tell me where to look further? I got a 'me too' message from somebody who googled my previous question, so there are more people with this problem. Ronald. --- original mail below --- My laptop will not recognize my pccard modem and pccard ethernet if I insert them both. When I only insert my modem it detects: Oct 19 21:34:13 laptop kernel: pccard0: Allocation failed for cfe 15 Oct 19 21:34:13 laptop kernel: sio4: at port 0x2f8-0x2ff irq 11 function 0 config 23 on pccard0 Oct 19 21:34:13 laptop kernel: sio4: type 16550A Oct 19 21:34:13 laptop kernel: sio4: unable to activate interrupt in fast mode - using normal mode When I only insert my ethernet it detects: Oct 19 20:48:44 laptop kernel: ep0: <3Com Megahertz 589E> at port 0x100-0x10f irq 11 function 0 config 1 on pccard0 Oct 19 20:48:44 laptop kernel: ep0: Ethernet address: 00:50:da:d1:01:25 When I insert both the ethernet and the modem it detects: Oct 19 21:26:44 laptop kernel: ep0: <3Com Megahertz 589E> at port 0x100-0x10f irq 11 function 0 config 1 on pccard0 Oct 19 21:26:44 laptop kernel: ep0: Ethernet address: 00:50:da:d1:01:25 Oct 19 21:26:44 laptop kernel: pccard1: Allocation failed for cfe 15 Oct 19 21:26:44 laptop kernel: sio4: at port 0x2f8-0x2ff irq 11 function 0 config 23 on pccard1 Oct 19 21:26:44 laptop kernel: device_attach: sio4 attach returned 6 What can I supply to help debugging this? Should I toggle some sysctl switches? My dmesg is added below. Hope, somebody can help me with this. Ronald. uname -a FreeBSD laptop 5.3-BETA7 FreeBSD 5.3-BETA7 #55: Thu Oct 14 16:06:04 CEST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPTOP i386 cat /var/run/dmesg.boot Copyright (c) 1992-2004 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.3-BETA7 #55: Thu Oct 14 16:06:04 CEST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPTOP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (266.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 100622336 (95 MB) avail memory = 92979200 (88 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 pcib1: at device 0.1 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) cbb0: mem 0x7fffe000-0x7fffefff irq 11 at device 12.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: mem 0x7000-0x7fff irq 11 at device 12.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 isab0: at device 14.0 on pci0 isa0: on isab0 atapci0: port 0x1000-0x100f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 14.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 14.2 (no driver attached) cpu0 on motherboard pmtimer0 on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) sbc0: at port 0x330-0x331,0x388-0x38b,0x220-0x22f irq 5 drq 0,1 on isa0 sbc0: [GIANT-LOCKED] pcm0: on sbc0 pcm0: [GIANT-LOCKED] Timecounters tick every 4.000 msec ipfw2 initialized, divert enabled, rule-based forwarding disabled, default to deny, logging unlimited ad0: 9590MB [19485/16/63] at ata0-master PIO4 pccard0: Allocation failed for cfe 15 sio4: at port 0x2f8-0x2ff irq 11 function 0 config 23 on pccard0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted WARNING: /mnt/oldtmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted /var: mount pending error: blocks 32 files 1 /var: superblock summary recomputed -- Ronald Klop, Amsterdam, The
Re: PCMCIA modem heating
Zoran Kolic said: > Hi all! > Don't wonna make stupid > quiestions, but this is > something I have to know > to make reclamation if neces- > sary. > After 5-10 minutes of inter- > net connection, when detached, > my pccard modem is hot as fur- > nace. I can barely take it in > my hand. Is it normal beha- > veour? > Model is Zoltrix, has "cirrus" > on the sticker. > Best regards > > ZK Stupid questions are certainly allowed, but [EMAIL PROTECTED] might have been a better list for this type of query. Regarding the query, yes, this is normal behavior for many laptops. Many are designed (unfortunately) with heat-generating circuitry right above/below the cardbus slots. If the card and laptop work correctly, for extended periods of time, then you have nothing to worry about. Just have a pair of tongs handy when you're ready to take it out. -- Charles Ulrich System Administrator Ideal Solution, LLC - http://www.idealso.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PCMCIA modem heating
Hi all! Don't wonna make stupid quiestions, but this is something I have to know to make reclamation if neces- sary. After 5-10 minutes of inter- net connection, when detached, my pccard modem is hot as fur- nace. I can barely take it in my hand. Is it normal beha- veour? Model is Zoltrix, has "cirrus" on the sticker. Best regards ZK ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Zoltrix modem
On Sun, Jan 26, 2003 at 08:58:32AM +0100, Zoran Kolic wrote: >Dear FreeBSD! >Hope that someone on the list has > expirience with external Zoltrix modem > named Rainbow. It should change my > nightmare: lucent winmodem. Maker > has a lot of data about windows com- > pability, but freeBSD is not even men- > tioned. Should I buy it? (Modem on the > machine? Yes, gonna be RELEASE. I have > no possibility to cvs or some other fancy > thing.) If it is based on the Lucent Winmodem chipset, as you say, it might be supported by the /usr/ports/comm/ltmdm port. Should you buy it? Only if you can return it for a refund should you find that it won't work with FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Zoltrix modem
Dear FreeBSD! Hope that someone on the list has expirience with external Zoltrix modem named Rainbow. It should change my nightmare: lucent winmodem. Maker has a lot of data about windows com- pability, but freeBSD is not even men- tioned. Should I buy it? (Modem on the machine? Yes, gonna be RELEASE. I have no possibility to cvs or some other fancy thing.) Thnx Zoran Kolic To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
