search for: 8n1

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

With this config: $ head -n2 isolinux/isolinux.cfg serial 0 9600 default vesamenu.c32 via the "Raw File Port Mode - VirtualBox" I got this: $ file /tmp/serial0.txt /tmp/serial0.txt: empty For the kernel log this in turn works OK: console=ttyS0 console=tty0 ignore_loglevel Is it really needed, exclusively a physical serial connection for the isolinux debug?

Hi everybody, I've got an Unitek iZi UPS 525 with a serial interface. The supplied cable looks fairly simple: RX->RX , TX->TX and GND->GND. Using this cable and Minicom with 2400 8N1 I'm able to issue commands to the UPS using the "Megatec Protocol" http://www.networkupstools.org/protocols/megatec.html so I know the UPS is fairly "intelligent" :-) and the serial connection works. Questions: 1. Which cable should I use for "Megatec Protocol&quo...

Hi, I'm trying to get an Effekta UPS (works directly with blazer_ser) working behind a seriell to ethernet converter (Brainboxes ES-246). I've set the converter to 2400 baud, 8N1, no flow control. On the linux side I started socat and blazer_ser. All I got are timeouts after 12 seconds. I can see network traffic with tcpdump but I've no idea what to do to get this working. Does anyone have experencies with blazer_ser and a remote UPS connected via seriell ethernet conv...

On 30.06.2015 22:52, Gene Cumm wrote: > 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 >...

On Tue, Jun 30, 2015 at 5:39 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 06/30/2015 01:52 PM, Gene Cumm via Syslinux wrote: >> >> 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 doesn't bother setting up for IO port 3F8h >> is just random hardware. >> > > A USB serial port looks completely different from a UART serial port, so > that is not really an option. I wasn't sure if it's...

I was wondering if anyone has seen anything like this standby power supply for Dell servers. http://www.ebay.co.uk/itm/200824909297?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649 I made up a cable and can connect to it at 9600 baud 8N1. The problem is that all it ever does is respond with a "?" and ends it with a LF it does this whenever it recieves a LF - I'm begining to think its mocking me! I've tried each of the NUT drivers in turn, none of them like what they see. Under the covers theres a PIC controller...

...rks as expected, until I try to send a sysrq. To send a break in minicom, I type [Ctrl]+[a] then [f]. Then I type the character [m] to do a test. I expect to see memory information print to screen, or at least show up in dmesg. Instead I only see the letter m on my shell. I'm using 115200, 8N1, VT102. I can echo m > /proc/sysctl-trigger, and dmesg shows that the sysrq was received when initiated via the procfs interface. But not over serial, and that's what I need. -- Billy Crook ? Network and Security Administrator ? RiskAnalytics, LLC

hi, I'm using the SCD-20 solar controller from IVT Gmbh in combination with a 230Ah battery and a photovoltaic panel to power a small server based on an Intel ATOM N270 CPU. the controller is (will be) connected to the server via RS232 (1200 8n1) and works like this: - if the battery voltage drops below 12V, a warning LED is switched on - if the battery voltage drops below 10.5V, the load (the server) is powered off to prevent exhaustive battery discharge - if the battery voltage raises above 12V, the power to the server is switched back...

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

...stools.org/cables/mgeups.html I tried making the cable, but the pin numbering on the modular jack (RJ12) wasn't clear on the page so I tried it both ways. Neither seems to work for me. Which way is the right way? I may need some help resolving this. Trying minicom on /dev/ttyS0 with 2400 bps 8n1 I can see that anything I type, gets echoed back character by character (in both pin configurations I tried). I don't know if it's a good or a bad thing. Nevertheless I can't get it to react in any other way. This is what I get in both configurations: # /lib/nut/mge-shut -a mge-shut -...

...d.img by the command: mkinitramfs -o initrd.img-2.6.31.13 2.6.31.13 6. Edit the grub/menu.lst adding the following line title xen 4.0 Linux Kernel 2.6.31.13 root (hd0, 1) kernel /boot/xen-4.0.gz dom0_mem=512M loglvl=all guest_loglvl=all sync_console console_to_ring com1=1152000, 8n1 console=com1 iommu=off module /boot/vmlinuz-2.6.31.13 ro root=UUID=xxxxxxxxxxxxxxxxxxxxxxx console=hvc0 earlyprintk=xen nomodest loglevel=10 module /boot/initrd.img-2.6.31.13 7. run ''update-rc.d xend defaults 20 21'', ''update-rc.d xendomain defaults 21 20&q...

...| +-----------------------------------------------------------------+ | | | Operation: The UPS communicates with the Computer via | | ordinary RS-232 serial protocol at 2400-8N1 with software | | flow control. Jumpered pins in the DB9F connector are for | | automatic or PNP cable identification by UPS software. | | | +-----------------------------------------------------------------+ |...

Hi, I'm forwarding your mail to the NUT list, because of a lack of time, and also since some others (Charles) already looked at this issue IIRC (related to the development branch 'netport'). cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

On 29.06.2015 17:06, Matthew Miller via Syslinux wrote: > > It actuallly looks from Adam's investigation that this isn't different > for this package. So, less than certainly. It looks like maybe more a > gcc 5 difference. > > > Regardless of whatever is actually causing this, here is the isolinux-debug.bin output: Booting from DVD/CD... ISOLINUX 6.03

...help solve this > mystery? There's not any mechanism that I know of aside from using cptime.c32 to time how long it takes for the files to be loaded or enabling some of the debug functionality (with debug.c32 to the screen or a recompile to output to a serial port at IO port 3F8h at 115200 8n1). There are some obvious questions that are yet unanswered: 1) What version? Where did it come from? 2) Where is it installed? SYSLINUX on a hard drive or perhaps installed to a USB drive of some sort? Some USB BIOSs are horribly slow. Perhaps ISOLINUX on a CD or hybridized to a hard drive o...

Hello, I''m using Red Hat AS 5 with Xen 3.0, and sometimes ''xm console'' does not work, the most of times when I''m trying to connect one full-virt machine with different arch from server, for example: [root@xen-5 ~]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1933 8

Hi Gene Thanks for your reply.I'm trying to breakdown overall system boot time and to understand each component duration. My linux image is a ~10 MB bzImage file with the rootfs cpio'ed inside. I also have 2 BIOS images:- some general purpose BIOS - a custom BIOS which loads real quick I'm using TSC to measure time. I'm not sure it's the best way (I've read about CPU's

...e: battery mode)... I have monitored (with statserial) the serial port with no result: all signals do not change... There is a proprietary application (closed source) that can comunicate with the UPS... I have saved the dialog between the application and the UPS; it seems that they use a 9600 bauds 8N1 configuration for the RS232... This is the trace of the data between the two (a small piece): Host --> 0x02 0x20 0x21 0x47 0x49 0x30 0x30 0x30 0x31 0x33 0x31 0x03 Device --> 0x02 0x21 0x20 0x47 0x49 0x33 0x38 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0...

...LBA = 00000A12 > isolinux: Image read, jumping to main code... > _ > So most of the nasm code should be OK. > If anyone has an idea how to debug this further, > do not hesitate. > Sooner or later all distros gonna hit this. A real serial port that can reliably operate at 115200 8n1 may be necessary. Build logs help sometimes for new warnings. Has anyone attempted builds outside the .src.rpm files? > syslinux-6.04-1.fc23.x86_64 I didn't expect to see that. I incremented version solely to indicate it's past 6.03. 6.04 hasn't even seen a pre-release yet (off...