search for: flowcontrol

...>>>> >>>> 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]]"? >> > > Yes. Was there ever a time that the behavior was "SERIAL port [[baudrate] flowcontrol]" or has it been misdocumented for years? -- -Gene

...ytor.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

Hi: I took me a while to figure this out, so I thought it might be good to document on the wiki. When using Syslinux's SERIAL option ( https://wiki.syslinux.org/wiki/index.php?title=SYSLINUX#SERIAL_port_.5Bbaudrate_.5Bflowcontrol.5D.5D ) in conjunction with Serial over LAN ( https://en.wikipedia.org/wiki/Serial_over_LAN), there is no "CTS assertion" (at least with some BIOS), but DTR and RTS are still needed. I would like to request that the following line be added to the "Typical values" section of ht...

...t;>> 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]]"? >>> >> >> Yes. > > Was there ever a time that the behavior was "SERIAL port [[baudrate] > flowcontrol]" or has it been misdocumented for years? > It's just a typo. -...

...ight be evident to developers, but not to users. _ Line 406: Suggestion: Similarly to the suggestion for 'Line 135' above, explicitly mentioning the particular case of 'ONTIMEOUT label' might be helpful for newcomers. _ Line 429: Suggestion: Correct "SERIAL port [[baudrate] flowcontrol]" to "SERIAL port [baudrate [flowcontrol]]" _ Line 598: This comment is not about documentation (so it's off-topic here), but about a request / reminder to fix the 'ASCII24+LSS16+newline' issue still present in Syslinux 5.10 (since 5.00). _ Line 825: Suggestion: The w...

...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]]"? > Yes. -hpa

On Mon, May 27, 2013 at 5:55 AM, Daniel J Blueman <daniel at 1degreenorth.com> wrote: > On 27/05/2013 17:53, Ferenc Wagner wrote: >> >> Daniel J Blueman <daniel at 1degreenorth.com> writes: >> >>> When moving from syslinux 4.06 to 5.01, I found serial output isn't >>> working. The issue reproduces simply [1] and I get back serial output

...HWTAGGING,TSO4,VLAN_HWTSO,LINKSTATE> ether 00:11:2f:2a:c7:03 inet 10.0.1.199 netmask 0xffffff00 broadcast 10.0.1.255 inet6 fe80::211:2fff:fe2a:c703%msk0 prefixlen 64 scopeid 0x1 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet autoselect (100baseTX <full-duplex,flowcontrol,rxpause,txpause>) status: active It sent the following packet: (data content abbreviated) 02:14:42.081617 IP 10.0.1.199.443 > 10.0.1.2.61258: Flags [P.], seq 930:4876, ack 846, win 1040, options [nop,nop,TS val 401838072 ecr 920110183], length 3946 0x0000: 4500 0f9e ea89 4000 4006 2a08...

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

...c4 wvdial[3034]: Re-Sending: ATZ Aug 11 17:50:16 c4 wvdial[3034]: Modem not responding. Aug 11 17:50:16 c4 pppd[3019]: Connect script failed Aug 11 17:50:17 c4 pppd[3019]: Exit. /etc/wvdial.conf [Modem0] Modem = /dev/ttyACM0 Baud = 57600 SetVolume = 0 Dial Command = ATDT Init1 = ATZ Init3 = ATM0 FlowControl = Hardware (CRTSCTS) [Dialer mymodem] Username = XXXXXXXXX Password = xxxx Phone = XXXXX Stupid Mode = 1 Inherits = Modem0 ----------------------------------------- Fedora Core 1: /var/log/messages --> Aug 11 09:54:58 c1 kernel: usb.c: USB device not accepting new address=9 (error=-110) Aug 1...

...screen0: always reports core events (**) Option "Device" "/dev/ttyS4" (**) Option "BaudRate" "9600" (**) Option "StopBits" "1" (**) Option "DataBits" "8" (**) Option "Parity" "None" (**) Option "FlowControl" "None" (**) Elographics X device name: TOUCHSCREEN (**) Option "ScreenNo" "0" (**) Elographics associated screen: 0 (**) Elographics untouch delay: 50 ms (**) Elographics report delay: 10 ms (**) Option "MaxX" "4000" (**) Elographics maximum x...

...one hour. +DTM BEGIN ------------------------------------------------------------ +SHOWTIMEOUT flag_val + If flag_val is not equal to 0, show the four hex digits timer + value to timeout. +DTM END -------------------------------------------------------------- + SERIAL port [[baudrate] flowcontrol] Enables a serial port to act as the console. "port" is a number (0 = /dev/ttyS0 = COM1, etc.) or an I/O port address (e.g. 0x3F8); if "baudrate" is omitted, the baud rate defaults to 9600 bps. The serial parameters are hardcoded to be 8 bits, no parity, 1 stop bit....

...he function will run properly out of the commandline or even . And in some situations, having power is even more critical: hospitals, for example, need to have top-notch electric power backup systems. I get the same result, whether it's at the command line or in an m-file. This looks like a flowcontrol mismatch issue to me. Can you please help me? The two answers that you did get were about as much as anyone will provide. Any suggestion and advice would be appreciated. This BuyerZone Coffee Service Buyer's Guide will take you through the various service offerings, help determine if it's...

...rter now attached to ttyUSB0 usbcore: registered new driver usbserial_generic drivers/usb/serial/usb-serial.c: USB Serial Driver core i edit the vi /etc/wvdial.conf with the following content [Dialer Defaults] Modem = /dev/ttyUSB0 Baud = 57600 Setvolume = 0 Dial-AT-OK ATDT Command = Init1 = ZTE FlowControl = Hardware (CRTSCTS) Phone = #777 Username = 7228412233 Password = 7228412233 New PPPD = yes Carrier 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 -- faile...

...cards. Searching around, I found posts saying that disabling acpi with the kernel options "acpi=off noacpi" would fix it, but it did not. I tried added explicit modprobe options for the driver in /etc/modprobe.conf (options e1000 XsumRX=0 Speed=1000 Duplex=2 InterruptThrottleRate=0 FlowControl=3 RxDescriptors=4096 TxDescriptors=4096 RxIntDelay=0 TxIntDelay=0). Still no change. Still getting experiencing the problem. I then tried another suggestion I found in a forum discussion `ethtool -K eth0 tso=off`. Seems to have had no effect on the problem. This problem occurs immediately whe...

Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen

Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen

I have a Cable ''modem'' that has a problem that many of these devices is bound to have. I was wondering what other lartc user thought about this and if DSL has simular problems. Cable, being Asymetrical, is able to upload at a given rate and hopefully has a buffer, in the modem, of some kind. When I nc(netcat) to a UDP echo, or discard, server I get about 10Mbps out on my

> Le 11 avr. 2019 ? 14:48, Ady Ady via Syslinux <syslinux at syslinux.org> a ?crit : > > >> Hello, >> >> Here's a small enhancement feature for menu.c32. Looking for feedback before >> starting any coding (not sure when I'll have time for implementation) >> >> Regards, >> Dany St-Amant >> >> >> *Problem

Hi, These patches contain support for some features that are already in Syslinux 4 but weren't working properly on the elflink branch. It's another step closer to feature parity with Syslinux 4. Having to jump through the comboot API for localboot support is less than ideal and I'll eventually fix that, probably when we move a big chunk of code from asm to C. Also, there's a