similar to: TDM2400: some FXS module fail

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

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

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

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

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

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 > +++

Hello, I have just get started using pxelinux, and encountered a problem. The document says the simple menu system supports serial console, and it works on syslinux 0.2x, but it doesn't seem to work in 0.3x and 0.4x. I confirmed that this patch fixed the bug. *** com32/lib/sys/xserial_write.c~ 2006-10-30 08:30:35.000000000 +0900 --- com32/lib/sys/xserial_write.c 2006-10-30

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,

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

This patch modifies the simple menu com32 program to include integrated load progress. It also adds new options to the simple menu configuration MENU LOADMSG -- allows the user to specify the text to display when loading MENU LOADMSGROW -- controls where the text is written Example configuration: MENU LOADMSG Booting MENU LOADMSGROW 25 It works with my setup, please let me know if you find

I was having a display problem with memtest86 and dos via a memdisk image not displaying properly when launched using vesamenu.c32 and using a PNG background image. Instead of proper text output the display mode is not changed and the existing menu image is corrupted by the outputted text. This seems to be similar or identical to a problem describe in a previous mailing:

Replace get_config() and execute() with syslinux_config_file() and syslinux_run_command(). - Sebastian Index: syslinux-3.71-pre14-8-gb8f5d7d/com32/modules/ethersel.c =================================================================== --- syslinux-3.71-pre14-8-gb8f5d7d.orig/com32/modules/ethersel.c 2008-07-18 19:45:15.000000000 +0200 +++ syslinux-3.71-pre14-8-gb8f5d7d/com32/modules/ethersel.c

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

Hi, I just pushed out changes that fix pretty much all the compiler build warnings on the elflink branch. Also, I've added "auto extension" support so that if the user doesn't type the file name extension it will automatically be looked up, e.g. now typing "ls" will execute "ls.c32". The following changes since commit

Hi Peter, Please pull the following changes. Paulo, I had to revert your "pxe: resolve names via DNS from protected-mode code" change because dns_resolv() is only implemented for PXELINUX and causes undefined symbol references for ISOLINUX, etc. Feel free to make the change again on top of the revert. The following changes since commit e7bd19def830e8341b1a100956345f1028740b9e:

From: Raphael S. Carvalho <raphael.scarv at gmail.com> MULTIFS SYNTAX: (hd[disk number]:[partition number])/path/to/file The meaning of this_fs was changed to improve the flexibility of the support. Now, this_fs means the file system being currently used. root_fs was created to save the context of the main file system (where ldlinux.sys lives in). get_fs_info is a function pointer that

meminfo.c32: Remove unneeded 'x' characters from output. Commit 5932f124 ("com32: change '%llx' to use PRIx64", committed on 2015-01-06) adds 1 "x" character per each of the 3 hex output columns for the 'INT 15h e820' value(s) in meminfo.c32. These 3 extra "x" characters are not really needed in this context, and they can make the resulting

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.