SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hey buddy, how goes the study?. I was hoping someone might have a slightly clearer explanation then the following:
– On a Linux host, a local domain socket is used instead. On Linux there
are various tools which can connect to a local domain socket or create
one in server mode. The most ﬂexible tool is socat and is available as
part of many distributions.
In this case, you can conﬁgure whether VirtualBox should create the
named pipe (or, on Linux, the local domain socket) itself or whether
VirtualBox should assume that the pipe (or socket) exists already. With
the VBoxManage command-line options, this is referred to as “server” or
“client” mode, respectively.
Can someone translate half of this or more into english?!?
Well, sorry, I cannot translate it ... because I have no idea either
But, it says there is an option in the gui that allows you to configure serial ports. Just do option number 2 out of the three listed there, that looks like it is the most sensible: i.e. Connecting the virtual port to a physical serial port on the host.
As for my study, well I graduated college ... yay ! Now on to medical school ...
Last edited by H_TeXMeX_H; 09-24-2007 at 01:20 PM.
oh man! H_TeXMeX_H i ma so glad for you, you should be REALLY proud of yourself. Gosh the last time we chatted you were busy studying and helping me out. I kept hoping you would do well. Well done buddy fair play to you.
I hope everything you plan for comes to pass! i hope you celebrated?
As for the options iv'e tried them all but to no avail. think maybe it might be a host side problem, like maybe i dont have serial ports active or something.
lsof /dev/ttyS* # will list serial ports which are open
ls /dev/ttyS* # list all serial ports
See which ones you want to connect. I think VirtualBox support a maximum of two serial ports at any one time.
2) Look through section 8.5 of that manual. It says you can use 'VBoxManage modifyvm' to set up the serial ports.
The options are listed there, but the most important ones are:
-uart<1-N> off|<I/O base> <IRQ>: With this option you can conﬁgure
virtual serial ports for the VM; see chapter 3.7.9, Serial ports, page 44 for an
introduction. -uartmode<1-N> <arg>: This setting controls how VirtualBox connects a
given virtual serial port (previously conﬁgured with the -uartX setting, see
above) to the host on which the virtual machine is running. As described in de-
tail in chapter 3.7.9, Serial ports, page 44, for each such port, you can specify
<arg> as one of the following options:
– disconnected: Even though the serial port is shown to the guest, it has
no “other end” – like a real COM port without a cable.
– server <pipename>: On a Windows host, this tells VirtualBox to create
a named pipe on the host named <pipename> and connect the virtual
serial device to it. Note that Windows requires that the name of a named
pipe begin with \\pipe\.
On a Linux host, instead of a named pipe, a local domain socket is used.
– client <pipename>: This operates just like server ..., except that
the pipe (or local domain socket) is not created by VirtualBox, but assumed
to exist already. – <devicename>: If, instead of the above, the device name of a physical
hardware serial port of the host is speciﬁed, the virtual serial port is con-
nected to that hardware port. On a Windows host, the device name will
be a COM port such as COM1; on a Linux host, the device name will look
like /dev/ttyS0. This allows you to “wire” a real serial port to a virtual
This also might be of use:
1. what kind of serial port the virtual machine should see by selecting an I/O base
address and interrupt (IRQ). For these, we recommend to use the traditional
values1 , which are:
a) COM1: I/O base 0x3F8, IRQ 4
b) COM2: I/O base 0x2F8, IRQ 3
c) COM3: I/O base 0x3E8, IRQ 4
d) COM4: I/O base 0x2E8, IRQ 3
So you might do something like:
VBoxManage modifyvm -uart1 0x3F8 4 # to set up COM1
VBoxManage modifyvm -uartmode1 /dev/ttyS0 # link it to physical port ttyS0
assuming '/dev/ttyS0' is the right serial port (that you found out in step 1, above).
I've never done this before, so try it out and see if it works. If anyone else has done it, please say so.
Last edited by H_TeXMeX_H; 09-25-2007 at 06:01 AM.
Well i tried both and nothing sttod out on the first command, i would post the feedback here but it's a little long. The second again, threw back nothing, here's the last few lines:
# Trying port address 031b
# Trying port address 0323
# Trying port address 032b
# Trying port address 0333
# Trying port address 033b
# Trying port address 0343
# Trying port address 034b
# Trying port address 0353
# Trying port address 035b
# Trying port address 0363
# Trying port address 036b
# Trying port address 0373
# Trying port address 037b
# Trying port address 0383
# Trying port address 038b
# Trying port address 0393
# Trying port address 039b
# Trying port address 03a3
# Trying port address 03ab
# Trying port address 03b3
# Trying port address 03bb
# Trying port address 03e3
# Trying port address 03eb
# Trying port address 03f3
# No boards found
oh man, maybe i should recompilt the kernel with serial support or something?
I have exactly the same problem and I can't find a solution.
Running Slackware 12 as a host and Windows XP as a guest.
I have uncommented all ttyS0-4 in /etc/serial.conf and rebooted after that.
$ dmesg|grep ttyS
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:0e: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
And after running VirtualBox:
$ lsof /dev/ttyS*
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
VirtualBo 3170 ivanatora 45u CHR 4,64 4527 /dev/tts/0
VirtualBo 3170 ivanatora 48u CHR 4,65 4509 /dev/tts/1
I have not Ports section in Device Manager. The Windows was installed before I enable these serial ports. Is it possible for it to 'remember' that state and cannot find any ports after that? Seems ridiculous.
There is something else that happened after I tried to enable COM ports - Windows can't stop properly. I have to kill the VirtualBox process always when I want to stop Windows.
I tried using COM ports as pipe, but still no success in Device Manager.
Is there a way to troubleshoot serial ports?
After I do
the terminal prompts don't stop and wait or give anything, but returns immediately:
Some debug info! I tried to send some file to the serial port (I have a loopback cable):
cp /proc/kcore /dev/ttyS0
And listening it on the same time:
tail -f /dev/ttyS0
And on the last screen I saw bunch of non printable characters like:
So after all my serial port is operational?
Go to Windows and using the Add New Hardware wizzard add your ports. It will detect them automatically!