Displaying 20 results from an estimated 700 matches similar to: "[PATCH] core: Incorrect detection of EDD in /core/fs/diskio_bios.c"
2014 Feb 23
1
[PATCH] core: Incorrect detection of EDD in /core/fs/diskio_bios.c
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
2014 Feb 22
0
[PATCH] core: Incorrect detection of EDD in /core/fs/diskio_bios.c
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
> +++
2013 Oct 18
1
[RFC/PATCH 2/3] core: MultiFS infrastructure added.
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
2019 Jan 21
2
A bug in command localboot was introduced in version 6.03.
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
2012 Jul 16
5
[PATCH 0/5] Deleting __intcall() from Syslinux
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
2014 Oct 30
0
Display graphic from filename broken?
> 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
2014 Oct 30
3
Display graphic from filename broken?
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
2015 Jul 22
13
[PULL 0/8] MultiFS suppport for BIOS and EFI
So last week I was wondering if XFS was still working -- even with its
last on-disk structure changes -- and it _suprisingly_ worked as
expected. Right, now I can finally get rid of GRUB and use Syslinux to
boot my Linux on EFI from a rootfs with xfs. Shit, I have two
partitions (the first one being the required ESP) so there is no way to
access the other partitions since because Syslinux does not
2011 Apr 16
20
[PATCH 00/20] Switch to ELF modules
From: Matt Fleming <matt.fleming at linux.intel.com>
This series fixes some bugs and switches the elflink branch to be
entirely ELF modules. It applies on top of,
http://syslinux.zytor.com/archives/2011-April/016369.html
The deletions in the diff stat below are mainly from deleting
com32/elflink/modules (finally!). Now there should be no duplicate
code because we don't need COM32 and
2006 Oct 29
1
The simple menu system doesn't work with serial console
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
2012 Jun 26
2
[GIT PULL] elflink bug fixes
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:
2012 Mar 23
19
[PATCH 00/19][elflink] Improve compatibility with 4.x
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
2012 Aug 14
1
[GIT PULL] elflink fixes
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
2007 Jan 27
1
FXS - Init Indirect Registers UNSUCCESSFULLY.
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
2011 Feb 21
3
Problem installing FXS module in old digium 4 channel tdm card
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
2011 May 25
1
[GIT PULL] elflink ldlinux
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
2012 Aug 20
13
[PATCH 00/12] Multidisk support
Hello,
the following patches should get multidisk access working.
The syntax accepted is the following:
(hdx,y)/path/to/file
where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk.
the other accepted syntax is using MBR's 32 bits disk signature so for example:
(mbr:0x12345678,2)/foo/bar
would address
2019 Jan 21
0
A bug in command localboot was introduced in version 6.03.
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,
2005 May 30
1
Where to start to solve hardware problem?
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
2012 Apr 17
2
[GIT PULL] elflink warning fixes and auto extension support
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