search for: 115200

...I get back serial output >>> when I move back to syslinux 4.06. >> >> >> Hi Daniel, >> >> What hardware are you working on? In some cases (eg. IBM Bladecenter >> serial over LAN) it became necessary to supply flow control options >> (like SERIAL 1 115200 0x13) to get any output. I never got the >> opportunity to narrow it down to the exact version, but you may want to >> try it until somebody knowledgeable responds. > > > Indeed, I usually use: > serial 1 115200 0x003 > > ...which doesn't work here either. > &g...

...libc.so.6 => /lib/libc.so.6 (0x40186000) libdl.so.2 => /lib/libdl.so.2 (0x402ad000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) then ok. lpinfo -v gives: network socket network http network ipp network lpd direct parallel:/dev/lp0 direct scsi serial serial:/dev/ttyS0?baud=115200 serial serial:/dev/ttyS1?baud=115200 serial serial:/dev/ttyS2?baud=115200 serial serial:/dev/ttyS3?baud=115200 serial serial:/dev/ttyS4?baud=115200 serial serial:/dev/ttyS5?baud=115200 serial serial:/dev/ttyS6?baud=115200 ----------------------------------------------- serial serial:/dev/ttyS29?bau...

...ndering if you've tried poking at them with 'setserial'? > Thanks for the suggestion. I looked at them with setserial, but I have no familiarity with the program to know what to change. setserial -ag /dev/ttyS* /dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4 ??? Baud_base: 115200, close_delay: 50, divisor: 0 ??? closing_wait: 3000 ??? Flags: spd_normal skip_test /dev/ttyS1, Line 1, UART: 16550A, Port: 0x8000, IRQ: 17 ??? Baud_base: 115200, close_delay: 50, divisor: 0 ??? closing_wait: none ??? Flags: spd_normal skip_test /dev/ttyS2, Line 2, UART: 16550A, Port: 0x8400...

...e prompt on the serial console terminal. Likewise, when I drop to single user mode on the serial console I do not see the single user prompt on the terminal connected to the box itself. Is this expected, or have I configured something incorrectly? In /etc/make.conf I have BOOT_COMCONSOLE_SPEED=115200 In my kernel configuration file I have: options CONSPEED=115200 I have rebuilt and installed world and the kernel. In /etc/ttys I have ttyd0 "/usr/libexec/getty std.115200" vt100 on secure I have also re-installed the bootstrap code: cd /usr/src/sys/boot make install bsdla...

...t I don't get any kernel messages which does somewhat limit the utility.. The BMC creates COM3 (/dev/cuau2) which works with getty. I modified /boot/loader.conf like so.. boot_multicons="yes" boot_serial="YES" console="comconsole vidconsole" comconsole_speed="115200" # Disable console flags on these 2 ports hint.uart.0.flags="0x00" hint.uart.1.flags="0x00" # Set console flag hint.uart.2.flags="0x10" Does anyone have any hints? -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.a...

On Mon, May 27, 2013 at 12:04 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 05/27/2013 04:49 AM, Gene Cumm wrote: >> >> 115200 = 0x1C200 so "SERIAL 1 115200" should be setting the bit rate >> to 9600 and the flow control to 0x200. >> > > I really hope that is not true. Should "SERIAL port [[baudrate] flowcontrol]" actually be "SERIAL port [baudrate [flowcontrol]]"? -- -Gene

...on, May 27, 2013 at 2:03 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 05/27/2013 11:01 AM, Gene Cumm wrote: >> On Mon, May 27, 2013 at 12:04 PM, H. Peter Anvin <hpa at zytor.com> wrote: >>> On 05/27/2013 04:49 AM, Gene Cumm wrote: >>>> >>>> 115200 = 0x1C200 so "SERIAL 1 115200" should be setting the bit rate >>>> to 9600 and the flow control to 0x200. >>>> >>> >>> I really hope that is not true. >> >> Should "SERIAL port [[baudrate] flowcontrol]" actually be "SERI...

On Sun, Jun 30, 2013 at 7:42 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, Jun 30, 2013 at 1:12 AM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >> Could it be that syslinux is waiting for ever if you use serial mode? >> >> SERIAL 0 115200 > >> TIMEOUT 300 > > Gert, Romain: Have you tried lowering the serial rate or timeout? ie: > > SERIAL 0 9600 > TIMEOUT 30 > > Romain: is this observed on a physical or virtual machine? Rather, have you only observed this under qemu? -- -Gene

...me to the console but then when I type I get those funny characters. Somehow an agetty is already being run: root 46110 1 0 16:13 ttyS1 00:00:00 /sbin/agetty /dev/ttyS1 19200 vt100-nav Is udev starting this up for me somehow? It says 19200 when everything I have read says it should be 115200. How do I change this? Some docs say I should create my own /etc/init/serial-ttyS1.conf containing: # For IPMI serial console # ttyS1 - agetty # # This service maintains a agetty on ttyS1. stop on runlevel [S016] start on runlevel [23] respawn exec agetty -h -L -w /dev/ttyS1 115200 vt102 but wh...

...39;t open device 'com3'! trace:comm:GetCommState handle 132, ptr 0x40596080 trace:comm:GetCommState OK trace:comm:GetCommState bytesize 8 baudrate 110 fParity 0 Parity 0 stopbits 1 trace:comm:GetCommState ~IXON ~IXOFF trace:comm:GetCommState CRTSCTS trace:comm:BuildCommDCBAndTimeoutsA (com2:115200,n,8,1,0x40596080,(nil)) trace:comm:BuildCommDCB16 (com2:115200,n,8,1), ptr 0x40596004 trace:comm:BuildCommDCB16 baudrate (110) trace:comm:BuildCommDCB16 parity (N) trace:comm:BuildCommDCB16 charsize (8) trace:comm:BuildCommDCB16 stopbits (1) trace:comm:SetCommState handle 132, ptr 0x40596080 trace:...

...both work. I can get either one to fully work but not both. When using serial, I do still get a login prompt on the vga, But not all the boot up output. Seems like half to the vga and the rest to the serial port I added lines to /etc/inittab # console port T0:12345:respawn:/sbin/agetty -L ttyS0 115200 And added to /etc/lilo.conf append="console=tty0 console=ttyS0,115200n8" I tried to add to "serial=0,115200n8" lilo.conf, but this gives error unsoported baud rate, commenting the line out seems to work. Any ideas on how to get both VGA and serial console to fully work? May...

On Tue, Jun 30, 2015 at 4:29 PM, poma <pomidorabelisima at gmail.com> wrote: > "A real serial port that can reliably operate at 115200 8n1 may be > necessary." > > Gene, is there something special in "A real serial port" usage, compared to emulated? I should restate: A serial port that responds on BIOS IO port 3F8h that can reliably operate at 115200 8n1 may be necessary. A USB serial port that the BIOS d...

The current early-printk support for ARM is rather hard-coded, making it hard to add machines or tweak settings. This series slightly moves some code to gather UART settings in xen/arch/arm/Rules.mk instead of the actual .c files. Also it allows two different machines with different settings to share the same driver, which the last patch exploits to add support the Calxeda Midway hardware. This

hi, It looks that Xen currently only support ISA serial port, which is onboard. Is there any plan to support the PCI serial port? Thanks, Neo -- I would remember that if researchers were not ambitious probably today we haven''t the technology we are using! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

...the prebuilt > binaries or making your own? Using (vesa)menu.c32? Could your > DEFAULT or ONTIMEOUT be broken? > I use extlinux 5.11-pre3 compiled from buildroot. I reproduced the problem under qemu. The only difference between the two config is the addition of the line "SERIAL 0 115200 0". I need to test without SERIAL on the computer to confirm that the problem comes there. (see also the report "6.01-pre 4 no timeout when using serial") Best regards, Romain Here is my configuration: Contents of "boot_label" file DEFAULT 1 ----------------------------...

...with 'setserial'? > > > Thanks for the suggestion. > > I looked at them with setserial, but I have no familiarity with the > program to know what to change. > > setserial -ag /dev/ttyS* > /dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4 > ??? Baud_base: 115200, close_delay: 50, divisor: 0 > ??? closing_wait: 3000 > ??? Flags: spd_normal skip_test > > /dev/ttyS1, Line 1, UART: 16550A, Port: 0x8000, IRQ: 17 > ??? Baud_base: 115200, close_delay: 50, divisor: 0 > ??? closing_wait: none > ??? Flags: spd_normal skip_test > > /dev/t...

...10:30:43 +0200] LoadDevices: Added device "ipp"... D [03/Mar/2004:10:30:43 +0200] LoadDevices: Added device "lpd"... D [03/Mar/2004:10:30:43 +0200] LoadDevices: Added device "scsi"... D [03/Mar/2004:10:30:44 +0200] LoadDevices: Added device "serial:/dev/ttyS0?baud=115200"... D [03/Mar/2004:10:30:44 +0200] LoadDevices: Added device "serial:/dev/ttyS1?baud=115200"... D [03/Mar/2004:10:30:44 +0200] LoadDevices: Added device "serial:/dev/ttyS2?baud=115200"... D [03/Mar/2004:10:30:44 +0200] LoadDevices: Added device "serial:/dev/ttyS3?baud=...

How, exactly, does CentOS-6.3 with udev recognize an USB modem when it is plugged in. How is it indicated? What other configuration is required? I can find the modem in /sys/class/tty and I can get the attributes using udevadm but I do not see anything in ps that refers to the modem device. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne

...Check = no Stupid Mode = yes wen i try to detect the modem it gives me a failure wvdialconf /etc/wvdial.conf ::::::: Scanning your serial ports for a modem. ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Port Scan<*1>: S1 S2 S3 WvModem<*1>: Cannot get information for serial port. ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, n...

...d 4 idle states [ 3.590852] ACPI: \_PR_.CP06: Found 4 idle states [ 3.596037] ACPI: \_PR_.CP07: Found 4 idle states [ 3.644065] Freeing initrd memory: 6740K [ 3.742932] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 3.750409] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [ 3.762111] serial 0000:00:16.3: enabling device (0000 -> 0003) [ 3.771589] 0000:00:16.3: ttyS1 at I/O 0xf0a0 (irq = 17, base_baud = 115200) is a 16550A [ 3.782503] Linux agpgart interface v0.103 [ 3.787805] ACPI: bus type drm_connector registered <--- boot stops her...