similar to: The simple menu system doesn't work with serial console

Hello, I found another problem in the simple menu system with serial console. The menu system doesn't reset LF/NL which was set in console_ansi_row(), because it never calls the destructor, console_clenup(), and so the LF/NL remains until you run "reset" command in sh on Linux. -- HIRANO Takahito hiranotaka%zng.info

From: Matt Fleming <matt.fleming at intel.com> Since we can't use __intcall() for EFI, and since we can now have the ELF module code resolve all our symbols at runtime, we should delete as many references to __intcall() as possible and just access the symbols directly. The most interesting patch is the support for weak symbols. We need to be able to reference derivative-specific

I'm having problems with a TDM22B. The FXO modules work fine. Both FXS modules fail to initialized. The error messages I see when the module loads: Init Indirect Registers UNSUCCESSFULLY. Indirect Registers failed verification. I already RMA'ed a TDM22B because of this problem. Now that the replacement shows a similar issue, I want to see if anyone else can think of something to

I just installed an FXS module onto a 4 channel tdm thats about 5 years old and it wont work. Running dmesg I can see the following error: Zapata Telephony Interface Registered on major 196 Freshmaker version: 71 Freshmaker passed register test !!!!!!! LOOP_CLOSE_TRES iREG 1C = 1 should be 1000 !!!!!!! RING_TRIP_TRES iREG 1D = 8000 should be 3600 !!!!!!! COMMON_MIN_TRES iREG 1E = 0 should

Hi Peter, The main part of this pull request includes commits that try to replace as many __intcall() invocations as possible. Some remain, but not many (and eventually they'll be gone too). There's also a patch to make better use of ld's --as-needed option and various other bug fixes/cleanups. The following changes since commit ff7334a2ce536b7f4b1f6d6f93ff4e285a3bd45a: Only

DL register is not set to drive number when detecting EDD for drive, so detection may fail. Signed-off-by: Andy Alex<andy at r-tt.com> --- diff -uprN syslinux-6.02.orig/core/fs/diskio_bios.c syslinux-6.02/core/fs/diskio_bios.c --- syslinux-6.02.orig/core/fs/diskio_bios.c 2013-10-13 21:59:03.000000000 +0400 +++ syslinux-6.02/core/fs/diskio_bios.c 2014-02-20 12:15:08.000000000 +0400 @@ -337,7

diff --git a/core/localboot.c b/core/localboot.c index 0b8769e4..30bfb272 100644 --- a/core/localboot.c +++ b/core/localboot.c @@ -63,7 +63,6 @@ __export void local_boot(int16_t ax) ireg.eax.w[0] = 0; /* Reset drive */ __intcall(0x13, &ireg, NULL); - memset(&ireg, 0, sizeof(ireg)); ireg.eax.w[0] = 0x0201; /* Read one sector */ ireg.ecx.w[0] = 0x0001; /* C/H/S = 0/0/1 (first

Yesterday my * server (SuSE 9.2 pro on Athlon) just stopped, no screen, no reaction to keyboard or mouse. I get all kind of messages, or just stop during restart 1. just two lines of a code (immediately after turn on the computer) 113-AM21200-100-GB GV-RX30128D F1 2. Main Processor: AMD Athlon (tm) 64 Processor 3200+ <CPUID: 0FF0 Patch ID: 0041> and BIOS line

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

From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse

http://bderzhavets.blogspot.com/2008/05/install-solaris-nevada-build-87-domu-at.html This message posted from opensolaris.org

I agree. This line was removed during testing because it didn't make big sense (EFLAGS_CF, ebx, and ecx are checked after int 0x13). But it's better to leave it in code to make sure that BIOS conforms standards and clears CF flag on successful call. Adjusted patch is given below. Andy Alex Signed-off-by: Andy Alex <andy at r-tt.com> --- diff -uprN

Hello, I've installed two Digium TDM2400 cards on my server. One has 24FXS and the other has 16 FXS and 4 FXO. They are both connected to power. Unfortunately some of the FXS module fail to initialize and I find following messages in the logs (the rest of the FXS modules work well). Could someone give me some advice? !!!!!!! LOOP_CLOSE_TRES iREG 1C = 1 should be 1000 Feb 9 18:09:45

> Hi, > > the display of LSS16 files from a DISPLAY file (as documented in > http://www.syslinux.org/wiki/index.php/SYSLINUX#Display_graphic_from_filename:) > seems heavily broken since syslinux has been converted from assembler to > C. I already discovered one bug in core/include/graphics.h (and > core/graphics.c): the pointer VGAFilePtr is of type uint16_t*, but > should

Hi, the display of LSS16 files from a DISPLAY file (as documented in http://www.syslinux.org/wiki/index.php/SYSLINUX#Display_graphic_from_filename:) seems heavily broken since syslinux has been converted from assembler to C. I already discovered one bug in core/include/graphics.h (and core/graphics.c): the pointer VGAFilePtr is of type uint16_t*, but should be plain char*. This bug causes the

I would like to use indirect registers for arrays allocated on the stack (alloca) - such as IReg[index]. Is there a way to do this in LLVM (similar to that of mem2reg optimization)?   Thanks, -Sanjay -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20081016/f75ffa3f/attachment.html>

A bug in command localboot was introduced in version 6.03. This bug was created because of inserting memsets in core/localboot.c. The third memset before /* Read one sector */ clears the field ireg.edx, which was assigned earlier and is required for subsequent __intcall0x13. So localboot type works as localboot 0. I think, this third memset in core/localboot.c is useless and excessive.

Op 2014-02-20 om 13:23 schreef Andy Alex: > DL register is not set to drive number when detecting EDD for drive, so detection may fail. > > Signed-off-by: Andy Alex<andy at r-tt.com> > --- > diff -uprN syslinux-6.02.orig/core/fs/diskio_bios.c syslinux-6.02/core/fs/diskio_bios.c > --- syslinux-6.02.orig/core/fs/diskio_bios.c 2013-10-13 21:59:03.000000000 +0400 > +++

I created a bootable usb flash with boot menu. One of items was "Boot from hard drive" with command "localboot 0x81". This item worked when this usb flash was prepared with syslinux 6.02. And it stopped working when the flash was prepared with syslinux 6.03. The message was Booting from local disk... Boot error I extracted the source code, investigated, changed, compiled

On Mon, Jan 21, 2019 at 3:37 AM Victor Sologoubov via Syslinux <syslinux at zytor.com> wrote: > > diff --git a/core/localboot.c b/core/localboot.c > index 0b8769e4..30bfb272 100644 > --- a/core/localboot.c > +++ b/core/localboot.c > @@ -63,7 +63,6 @@ __export void local_boot(int16_t ax) > ireg.eax.w[0] = 0; /* Reset drive */ > __intcall(0x13,