Linux kernel parameters. The following is a consolidated list of the kernel parameters as implemented (mostly) by the __setup() macro and sorted into English Dictionary order (defined as ignoring all punctuation and sorting digits before letters in a case insensitive manner), and with descriptions where known.
Module parameters for loadable modules are specified only as the parameter name with optional '=' and value as appropriate, such as: modprobe usbcore blinkenlights=1 Module parameters for modules that are built into the kernel image are specified on the kernel command line with the module name plus '.' plus parameter name, with '=' and value if appropriate, such as: usbcore.blinkenlights=1 The text in square brackets at the beginning of the description states the restrictions on the kernel for the said kernel parameter to be valid.
ACPI ACPI support is enabled. In addition, the following text indicates that the option: BUGS= Relates to possible processor bugs on the said processor. RFC 2217 - Telnet Com Port Control Option. [Docs] [txt|pdf] [draft-clark-telne...] [Diff1] [Diff2] EXPERIMENTAL Network Working Group G. Clark Request for Comments: 2217 Cisco Systems, Inc. Category: Experimental October 1997 Status of this Memo This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. RFC 2217 Telnet Com Port Control Option October 1997 Many new business functions require a person to connect to remote services to retrieve or deposit information. RFC 2217 Telnet Com Port Control Option October 1997 Though this discussion has focused on outbound modem dialing as the primary use of this protocol, the protocol can also be used for any serial device attached to an access server. 1.
RFC 2217 Telnet Com Port Control Option October 1997 2. Once DO and WILL have been negotiated, the client may send any of the following commands. 3. RFC 2217 Telnet Com Port Control Option October 1997 4. 5. COM port redirector. A COM port redirector is specialized software (often including device driver and user application) that includes the underlying network software necessary to access networked device servers that provide remote serial devices or modems. Overview[edit] The purpose of the redirector is to make the virtual COM port exhibit behavior that closely resembles that of a "real" COM port, i.e., a COM port driver for local serial port hardware. A virtual COM port itself is a relatively simple software mechanism that can be implemented by driver software similar to that of a conventional COM port driver. The main challenges arise in two other areas: the network connection to the device server and the behavior of the device server.
Applications use a COM port redirector through one or more virtual COM ports that the redirector creates, as configured by the user. The performance of a COM port redirector is determined by both its implementation and the network it uses to reach device servers. SYSLINUX - Syslinux Wiki. SYSLINUX is a boot loader for the Linux operating system which runs on an MS-DOS/Windows FAT filesystem. It is intended to simplify first-time installation of Linux, and for creation of rescue and other special purpose boot disks. When properly configured, SYSLINUX can be used to completely eliminate the need for distribution of raw boot floppy images. A SYSLINUX floppy can be manipulated using standard MS-DOS (or any OS capable of accessing an MS-DOS filesystem) tools once it has been created. These are the options common to all versions of the SYSLINUX installer: (Note: The following command line options are valid for older versions of SYSLINUX.
-s Safe, slow, stupid: uses simpler code that boots better. These are only available in the Windows version: -m MBR: install a bootable MBR sector to the beginning of the drive. This can only be used in the linux version:Since version 4.00: -t Specifies the byte offset of the filesystem image in the file. For older versions (deprecated): Syntax: or: Serial console hangs. How to serial port - PC Interface DB9 Pin Serial Port. 9. Locating the Serial Port: IO address, IRQs 9.1 What Bus is my Serial Port On?
If you need to find a serial port it often helps if you know what bus it's on. If the serial port is on a card, you may know what bus the card inserts into (usually a PCI slot). 9.2 IO & IRQ Overview For a serial port to work properly it first must be given both an IO address and an IRQ. 7. (provided the BIOS has not been previously set up to disable it) so that you only need to read this if you're having problems or if you want to understand how it works. The driver must of course know both the IO address and IRQ so that it can talk to the serial port chip. For the old ISA bus, the driver also probes likely serial port addresses to see if there are any serial ports there.
Locating the serial port by giving it an IRQ and IO address is low−level configuring. The low−level configuring consists of assigning an IO address, IRQ, and names (such as ttyS2 = tts/2). You may watch the start−up (= boot−time) messages. Some Knowledge. Or to put it another waydd if=/dev/brain of=/dev/internet If you have a good browser then use CTRL-f to find what you want As always this page will grow and change as time goes by I have gathered this information from a lot of places around the Internet and from my own experience. Feel free to pass on any tips or corrections you may have. Also I have a "How I Did It" page with details on setting up an IPv6 tunnel broker system using OpenVPN.
If you are looking for some Solaris information then have a look at my Solaris page. It was getting too big to include in one page. Quick links to sectionskvmOpenVZLinuxSolarisCisco How I compiled the kernel module and got it to run in bridge mode I started from a standard Ubuntu 7.04 install on an Intel Core2 Duo machine apt-get install gcc-3.4 g++-3.4 uuid-dev zlib1g-dev libsdl1.2-dev build-essential apt-get install libasound2-dev bridge-utils qemu vde Change /etc/network/interface to look like this so bridge mode works Now compile the module #! Then Misc udev. How_to_install_additional_serial_port_boards [ISG D-PHYS README Wiki] This was tested to work on trelawney (while it was a Linux box) using a NetMOS PCI serial board. $ lspci | grep -i serial 01:06.0 Serial controller: Unknown device 9710:9835 (rev 01) $ lspci -v -s 01:06.0 01:06.0 Serial controller: Unknown device 9710:9835 (rev 01) (prog-if 02 [16550]) Subsystem: LSI Logic / Symbios Logic (formerly NCR): Unknown device 0002 Flags: medium devsel, IRQ 11 I/O ports at a000 [size=8] I/O ports at a400 [size=8] I/O ports at a800 [size=8] I/O ports at ac00 [size=8] I/O ports at b000 [size=8] I/O ports at b400 [size=16] in /etc/init.d/serialext (create this file, Note: this assumes devfs mounted on /dev, for classic /dev or standard udev replace /dev/tts/1 with /dev/ttyS1, etc.): /bin/mknod /dev/tts/1 c 4 65 /bin/mknod /dev/tts/2 c 4 66 chown root:dialout /dev/tts/{1,2} chmod 0660 /dev/tts/{1,2} setserial -g /dev/tts/1 setserial -g /dev/tts/2 /etc/init.d/setserial.
SSL Error. Mars is a machine comparable to terra mars also has a Lava Octopus-550 8-port RS232 PCI card. it shows up under lspci -v as: 0000:01:03.0 Serial controller: Lava Computer mfg Inc Lava Octo A (prog-if 02 [16550]) Subsystem: Lava Computer mfg Inc Lava Octo A Flags: slow devsel, IRQ 169 I/O ports at 8000 [size=8] I/O ports at 8400 [size=8] I/O ports at 8800 [size=8] I/O ports at 8c00 [size=8] 0000:01:03.1 Serial controller: Lava Computer mfg Inc Lava Octo B (prog-if 02 [16550]) Subsystem: Lava Computer mfg Inc Lava Octo B Flags: slow devsel, IRQ 169 I/O ports at 9000 [size=8] I/O ports at 9400 [size=8] I/O ports at 9800 [size=8] I/O ports at 9c00 [size=8] there are linux configuration instructions online as it turned out, to properly configure the device, i needed to:
Baudrates for RS-485. View topic - 2 port PCI serial addon card and LIRC troubles. Greetings everyone, I'm having an issue getting a 2 serial port PCI addin card working with LIRC under Debian Lenny with the stock 2.6.22-3-amd64 kernel. This box is used exclusively for MythTV. I was hoping someone here might be able to help. System Hardware: Motherboard: Abit AN-M2HD (NVIDIA GeForce 7050PV/NF630a)RAM: A-DATA Value Series 2GB (2 x 1GB) 240-Pin DDR2 800 SDRAM Dual Channel KitCPU: AMD Athlon X2 BE-2350 Brisbane 2.1GHzVideo: Using the onboard NVIDIA graphics with proprietary driver 169.07Hard Drive: Maxtor DiamondMax 10 300 GB Model 6L300R0DVD+-RW: Plextor PX-740ASerial Port PCI Card: Generic 2 port card (eBay) with a "CH352L" chip.IR Receiver: RS232 IR Blaster from IRBlaster.info The serial port pci card and it's associated IR receiver was added after initial install.
Upon boot, I can see that the BIOS on the motherboard (version 18 ) sees the serial card as "Simple COMM. controller" and assigns it to IRQ 11. Code: Select all In /etc/lirc/hardware.conf... Serial Console - Waikato Linux Users Group. Computer Serial Port Configuration - MobileRobots Research and Academic Customer Support. From MobileRobots Research and Academic Customer Support The serial ports of a robot's onboard computer are preconfigured when the robot is assembled. However, if you are using your own laptop or reinstalled the operating system, and the serial port stops working and you have problems with serial devices such as the robot platform or a SICK laser, you can check that it is configured correctly.
Symptoms of IRQ conflicts in ARIA If ARIA encounters errors communicating with the robot or SICK laser, it will print messages similar to the following: ArRobotPacketReceiver::receivePacket: bad packet, bad checksum Or ArSickPacketReceiver::receivePacket: bad packet, bad checksum ArSickPacketReceiver::receivePacket: wrong address (0x9 instead of 0x80) ArLMS2xxPacketReceiver::receivePacket: bad packet, bad checksum ArLMS2xxPacketReceiver::receivePacket: wrong address (0x9 instead of 0x80) Or it may simply be unable to connect to the device, with message such as: ArSick: waiting for laser to power on. ACCES I/O - Linux Serial Configuration. In order to configure serial ports for Linux, you will need to make use of the setserial command. Firstly, you will need to know the card's base address and and which IRQ it is using.
For an ISA card, this can be read off the jumpers on the card. For a PCI card, our pcifind.plx PERL script provides a friendly listing of all our PCI cards in your system, including their base addresses and IRQs. To run it, open a terminal window and change to its directory, then type "perl pcifind.plx". If, for some reason, you can't run pcifind.plx, type /sbin/lspci -vv -d 494f:* at the command line; this will produce a more detailed but less readable listing of all the resources of our PCI cards.
It may also be useful to determine the UART type of the card as well, but setserial can configure this automatically. Setserial assigns the serial port to one of the devices in /dev. A typical call of the setserial command is: setserial /dev/ttySx port y irq z autoconfig . mknod -m 666 /dev/ttySx c 4 y. Text-Terminal-HOWTO: Terminal Emulation (including the Console) Next Previous Contents 9. Terminal Emulation (including the Console) 9.1 Intro to Terminal Emulation Since a PC has a screen and keyboard (as does a terminal) but also has much more computing power, it's easy to use some of this computing power to make the PC computer behave like a text terminal.
Much emulation software is available for use under the MS Windows OS. 9.2 Don't Use TERM Variable For Emulation Some have erroneously thought that they could create an emulator at a Linux console (monitor) by setting the environment variable TERM to the type of terminal they would like to emulate. If you set it to something else you are fibbing to application programs. 9.3 Communication (Dialing) programs Dialing programs for making a PPP connection to the Internet don't normally include any terminal emulation.
The communication program Kermit doesn't do terminal emulation as it is merely a semi-transparent pipe between whatever terminal you are on and the remote site you are connected to. COM port under Fedora 11. Text-Terminal-HOWTO: Using the Terminal. NextPreviousContents 17. Using the Terminal 17.1 Intro to Using the Terminal This section is about controlling the terminal-computer interface and/or changing the terminal set-up while using the terminal. It explains (or points to explanations of) how the user of a terminal can control and inspect the interface and how to use various commands provided by the device driver. It does not explain how to use the many application programs, shells or most Linux utilities. Clear (to clear the screen) reset (to reset the terminal setterm -reset (alternative for "reset" in case of bug) 17.2 Starting Up the Terminal Of course the power must be on for the terminal to work.
If nothing happens, make sure that both the host computer and the terminal are OK. 17.3 Terminal (Serial) Device Driver When typing at the command line, the shell (such as the Bash shell) is reading what you type and reacting to it. 17.4 Problems with Editors There may be some problems with using both emacs and vi on some terminals. Remote Serial Console HOWTO.
Configure Linux kernel. The Linux kernel is configured to select the console by passing it the console parameter. The console parameter can be given repeatedly, but the parameter can only be given once for each console technology. So console=tty0 console=lp0 console=ttyS0 is acceptable but console=ttyS0 console=ttyS1 will not work. When multiple consoles are listed output is sent to all consoles and input is taken from the last listed console. The last console is the one Linux uses as the /dev/console device. The syntax of the console parameter is given in Figure 5-1. Figure 5-1. Kernel console syntax, in EBNF console=ttyS<serial_port>[,<mode>]console=tty<virtual_terminal>console=lp<parallel_port>console=ttyUSB[<usb_port>[,<mode>] <serial_port> is the number of the serial port. If you are using the devfs device filesystem with your Linux installation the kernel parameter for the first serial port is still ttyS0, even though the first serial device is no longer known as /dev/ttyS0 but as /dev/ttys/0.
Figure 5-2. Configure Linux kernel using GRUB. Using the Configuration Utilities. Now let's spend some time looking at the two most useful serial device configuration utilities: setserial and stty. 4.5.1. The setserial Command The kernel will make its best effort to correctly determine how your serial hardware is configured, but the variations on serial device configuration makes this determination difficult to achieve 100 percent reliably in practice. A good example of where this is a problem is the internal modems we talked about earlier. The UART they use has a 16-byte FIFO buffer, but it looks like a 16450 UART to the kernel device driver: unless we specifically tell the driver that this port is a 16550 device, the kernel will not make use of the extended buffer.
Yet another example is that of the dumb 4-port cards that allow sharing of a single IRQ among a number of serial devices. We may have to specifically tell the kernel which IRQ port it's supposed to use, and that IRQs may be shared. setserial was created to configure the serial driver at runtime. 4.5.2. Serial HOWTO. Text-Terminal-HOWTO. Welcome. E.3.9. /proc/sys/ Linux Network Configuration. Linux/UNIX For DOS Users. Debian Linux: Set a Serial Console. Linux I/O port programming mini-HOWTO. Serial Consoles - Gridwiki. Setserial(8): get/set serial port info.
Linux / UNIX minicom Serial Communication Program. Screen Command: Set Baud Rate [ Terminal Communication ] Serial Programming. Serial HOWTO. Serial HOWTO. Linux Serial Console HOWTO. How to login from serial port under Linux. Configuring serial console in Red Hat and Suse. Setting up a serial console.