Prolific USB-Serial Controller

2008-02-02 Thread Chris
I am trying to a access a switch connected to a USB-Serial controller
to my laptop's USB port. When I plug in the USB port to my laptop I
get the following in my /var/log/messages. But I am not sure which
/dev/ to use in minicom to access the switch. I can see there
is no /dev/uplcom0 or /dev/ucom0 or /dev/uhub1. I tried /dev/tty00,
/dev/tty01, /dev/tty02, /dev/tty03 and /dev/cua00 but minicom says
device not configured.

Any help would be much appreciated. Thanks.

Feb  2 20:31:58 red /bsd: uplcom0 at uhub1 port 2
Feb  2 20:31:58 red /bsd:
Feb  2 20:31:58 red /bsd: uplcom0: Prolific Technology Inc. USB-Serial
Controller, rev 1.10/3.00, addr 2
Feb  2 20:31:58 red /bsd: ucom0 at uplcom0



Re: Prolific USB-Serial Controller

2008-02-02 Thread Stuart Henderson
/dev/ttyU0

On 2008/02/02 20:53, Chris wrote:
> I am trying to a access a switch connected to a USB-Serial controller
> to my laptop's USB port. When I plug in the USB port to my laptop I
> get the following in my /var/log/messages. But I am not sure which
> /dev/ to use in minicom to access the switch. I can see there
> is no /dev/uplcom0 or /dev/ucom0 or /dev/uhub1. I tried /dev/tty00,
> /dev/tty01, /dev/tty02, /dev/tty03 and /dev/cua00 but minicom says
> device not configured.
> 
> Any help would be much appreciated. Thanks.
> 
> Feb  2 20:31:58 red /bsd: uplcom0 at uhub1 port 2
> Feb  2 20:31:58 red /bsd:
> Feb  2 20:31:58 red /bsd: uplcom0: Prolific Technology Inc. USB-Serial
> Controller, rev 1.10/3.00, addr 2
> Feb  2 20:31:58 red /bsd: ucom0 at uplcom0



Re: Prolific USB-Serial Controller

2008-02-02 Thread Sigi Rudzio
2008/2/2, Chris <[EMAIL PROTECTED]>:
> I am trying to a access a switch connected to a USB-Serial controller
> to my laptop's USB port. When I plug in the USB port to my laptop I
> get the following in my /var/log/messages. But I am not sure which
> /dev/ to use in minicom to access the switch. I can see there
> is no /dev/uplcom0 or /dev/ucom0 or /dev/uhub1. I tried /dev/tty00,
> /dev/tty01, /dev/tty02, /dev/tty03 and /dev/cua00 but minicom says
> device not configured.
>
> Any help would be much appreciated. Thanks.


for USB-Serial controllers you have to use /dev/cuaU0 (callout) or /dev/ttyU0

Sigi



Re: Prolific USB-Serial Controller

2008-02-02 Thread Marc Balmer

Chris wrote:

I am trying to a access a switch connected to a USB-Serial controller
to my laptop's USB port. When I plug in the USB port to my laptop I
get the following in my /var/log/messages. But I am not sure which
/dev/ to use in minicom to access the switch. I can see there
is no /dev/uplcom0 or /dev/ucom0 or /dev/uhub1. I tried /dev/tty00,
/dev/tty01, /dev/tty02, /dev/tty03 and /dev/cua00 but minicom says
device not configured.


use /dev/cuaU0 (or /dev/cuaU)



Any help would be much appreciated. Thanks.

Feb  2 20:31:58 red /bsd: uplcom0 at uhub1 port 2
Feb  2 20:31:58 red /bsd:
Feb  2 20:31:58 red /bsd: uplcom0: Prolific Technology Inc. USB-Serial
Controller, rev 1.10/3.00, addr 2
Feb  2 20:31:58 red /bsd: ucom0 at uplcom0




Re: Prolific USB-Serial Controller

2008-02-02 Thread Marc Balmer

Stuart Henderson wrote:


/dev/ttyU0


you should use /dev/cuaU0 for "dial-out".



On 2008/02/02 20:53, Chris wrote:

I am trying to a access a switch connected to a USB-Serial controller
to my laptop's USB port. When I plug in the USB port to my laptop I
get the following in my /var/log/messages. But I am not sure which
/dev/ to use in minicom to access the switch. I can see there
is no /dev/uplcom0 or /dev/ucom0 or /dev/uhub1. I tried /dev/tty00,
/dev/tty01, /dev/tty02, /dev/tty03 and /dev/cua00 but minicom says
device not configured.

Any help would be much appreciated. Thanks.

Feb  2 20:31:58 red /bsd: uplcom0 at uhub1 port 2
Feb  2 20:31:58 red /bsd:
Feb  2 20:31:58 red /bsd: uplcom0: Prolific Technology Inc. USB-Serial
Controller, rev 1.10/3.00, addr 2
Feb  2 20:31:58 red /bsd: ucom0 at uplcom0




Re: Prolific USB-Serial Controller

2008-02-02 Thread Chris
On Feb 2, 2008 10:29 PM, Marc Balmer <[EMAIL PROTECTED]> wrote:
> > /dev/ttyU0
> you should use /dev/cuaU0 for "dial-out".

Thanks. I tried both /dev/ttyU0 and /dev/cuaU0 in minicom. They both
seem to go to the "initializing modem" phase but when I turn on the
switch with "/dev/cuaU0" configuration, minicom doesn't show anything
on the screen and minicom with /dev/ttyU0 configuration throws out
garbage characters on the screen -

..5%(.!3..=.3'=./A-#-.'!=7A/5'.5;!!. .-.9/.('5.
..5%((W/5(3!''!.-#1(9!%%=#7.(.-''(-#-.-='-53'=./(3-'5.
..5%(/=.(;55#(-#.5..57(.!.!(-#-.-='-.=..=..9..9.9.O%!75%(3-

Here's my minicom rc file -

pu port /dev/ttyU0
pu baudrate  9600
pu bits 8
pu parity   N
pu stopbits 1

The USB Serial converter is detected as "Prolific Technology Inc.
USB-Serial Controller
rev 1.10/3.00, addr 2" in /var/log/messages.

Thanks for any further help on this issue.



Re: Prolific USB-Serial Controller

2008-02-02 Thread johan beisser
A) don't bother initializing a modem. Forget minicom. It's nearly  
useless for what you're doing.


B) openbsd has a utility built in to do just these kinds of things:  
"cu(1)"


C) to use cu(1) with a USB serial: "cu -l /dev/cuaU0"




On Feb 2, 2008, at 1:57 PM, Chris wrote:


On Feb 2, 2008 10:29 PM, Marc Balmer <[EMAIL PROTECTED]> wrote:

/dev/ttyU0

you should use /dev/cuaU0 for "dial-out".


Thanks. I tried both /dev/ttyU0 and /dev/cuaU0 in minicom. They both
seem to go to the "initializing modem" phase but when I turn on the
switch with "/dev/cuaU0" configuration, minicom doesn't show anything
on the screen and minicom with /dev/ttyU0 configuration throws out
garbage characters on the screen -

..5%(.!3..=.3'=./A-#-.'!=7A/5'.5;!!. .-.9/.('5.
..5%((W/5(3!''!.-#1(9!%%=#7.(.-''(-#-.-='-53'=./(3-'5.
..5%(/=.(;55#(-#.5..57(.!.!(-#-.-='-.=..=..9..9.9.O%!75%(3-

Here's my minicom rc file -

pu port /dev/ttyU0
pu baudrate  9600
pu bits 8
pu parity   N
pu stopbits 1

The USB Serial converter is detected as "Prolific Technology Inc.
USB-Serial Controller
rev 1.10/3.00, addr 2" in /var/log/messages.

Thanks for any further help on this issue.




Re: Prolific USB-Serial Controller

2008-02-02 Thread Okan Demirmen
On Sun 2008.02.03 at 08:57 +1100, Chris wrote:
> On Feb 2, 2008 10:29 PM, Marc Balmer <[EMAIL PROTECTED]> wrote:
> > > /dev/ttyU0
> > you should use /dev/cuaU0 for "dial-out".
> 
> Thanks. I tried both /dev/ttyU0 and /dev/cuaU0 in minicom. They both
> seem to go to the "initializing modem" phase but when I turn on the
> switch with "/dev/cuaU0" configuration, minicom doesn't show anything
> on the screen and minicom with /dev/ttyU0 configuration throws out
> garbage characters on the screen -
> 
> ..5%(.!3..=.3'=./A-#-.'!=7A/5'.5;!!. .-.9/.('5.
> ..5%((W/5(3!''!.-#1(9!%%=#7.(.-''(-#-.-='-53'=./(3-'5.
> ..5%(/=.(;55#(-#.5..57(.!.!(-#-.-='-.=..=..9..9.9.O%!75%(3-
> 
> Here's my minicom rc file -
> 
> pu port /dev/ttyU0
> pu baudrate  9600
> pu bits 8
> pu parity   N
> pu stopbits 1

try "cu -l cuaU0" - man 1 cu.

also, what is the speed of the serial console on your switch?  verify
what that the default is, then apply -s accordingly.  you may also toy
around with tip(1).



Re: Prolific USB-Serial Controller

2008-02-02 Thread Chris
On Feb 3, 2008 9:27 AM, johan beisser <[EMAIL PROTECTED]> wrote:
> C) to use cu(1) with a USB serial: "cu -l /dev/cuaU0"

I tried "cu -l /dev/cuaU0", "cu -l /dev/cuaU0 -s 9600" - it says
"Connected" after that nothing happens. Should I try changing the baud
rate? This Cisco 3950 switch is usually connected at 9600 baud rate
via serial console. Here's /var/log/aculog -

/var/log/aculog -

chris (Sun Feb  3 10:05:04 2008)  call completed
chris (Sun Feb  3 10:09:06 2008)  call terminated
chris (Sun Feb  3 10:09:08 2008)  call completed

Thanks.



Re: Prolific USB-Serial Controller

2008-02-02 Thread johan beisser

On Feb 2, 2008, at 3:17 PM, Chris wrote:


On Feb 3, 2008 9:27 AM, johan beisser <[EMAIL PROTECTED]> wrote:

C) to use cu(1) with a USB serial: "cu -l /dev/cuaU0"


I tried "cu -l /dev/cuaU0", "cu -l /dev/cuaU0 -s 9600" - it says
"Connected" after that nothing happens. Should I try changing the baud
rate? This Cisco 3950 switch is usually connected at 9600 baud rate
via serial console. Here's /var/log/aculog -


You may hit space or enter. Sometimes it just has to wake up. Cisco,  
by default, uses 9600 8,N,1 if i remember correctly.



/var/log/aculog -

chris (Sun Feb  3 10:05:04 2008)  call completed
chris (Sun Feb  3 10:09:06 2008)  call  
terminated

chris (Sun Feb  3 10:09:08 2008)  call completed


Is there any dmesg output related to the USB serial controller?



Re: Prolific USB-Serial Controller

2008-02-02 Thread Chris
On Feb 3, 2008 10:22 AM, johan beisser <[EMAIL PROTECTED]> wrote:
> You may hit space or enter.

I did but looks like it just hangs in there - jammed. Nothing happens.

> Sometimes it just has to wake up. Cisco,
> by default, uses 9600 8,N,1 if i remember correctly.

Yes. You are right.

> Is there any dmesg output related to the USB serial controller?

Yep. Here's /var/log/messages output -

Feb  3 10:19:57 red /bsd: uplcom0 at uhub1 port 2
Feb  3 10:19:57 red /bsd:
Feb  3 10:19:57 red /bsd: uplcom0: Prolific Technology Inc. USB-Serial
Controller, rev 1.10/3.00, addr 2
Feb  3 10:19:57 red /bsd: ucom0 at uplcom0

Thanks.



Re: Prolific USB-Serial Controller

2008-02-02 Thread Okan Demirmen
On Sun 2008.02.03 at 10:28 +1100, Chris wrote:
> On Feb 3, 2008 10:22 AM, johan beisser <[EMAIL PROTECTED]> wrote:
> > You may hit space or enter.
> 
> I did but looks like it just hangs in there - jammed. Nothing happens.
> 
> > Sometimes it just has to wake up. Cisco,
> > by default, uses 9600 8,N,1 if i remember correctly.
> 
> Yes. You are right.

did you say cisco - do you have the correct cable, a rollover? (or
pin-out in your adapter)

> > Is there any dmesg output related to the USB serial controller?
> 
> Yep. Here's /var/log/messages output -
> 
> Feb  3 10:19:57 red /bsd: uplcom0 at uhub1 port 2
> Feb  3 10:19:57 red /bsd:
> Feb  3 10:19:57 red /bsd: uplcom0: Prolific Technology Inc. USB-Serial
> Controller, rev 1.10/3.00, addr 2
> Feb  3 10:19:57 red /bsd: ucom0 at uplcom0
> 
> Thanks.