similar to: Kernel Image CRC checking

Displaying 20 results from an estimated 1000 matches similar to: "Kernel Image CRC checking"

2019 Jun 08
2
Kernel Image CRC checking
On 6/4/19 4:05 AM, Gene Cumm via Syslinux wrote: > On Sat, May 25, 2019 at 8:33 AM Johann Obermayr via Syslinux > <syslinux at syslinux.org> wrote: >> >> Hello, >> >> Is there a function to check a bzImage CRC ? >> >> If (ImageCRC("/bzImage") == -1) >> Load_kernel("/BACKUP/bzImage") or what else >>
2019 Jun 04
0
Kernel Image CRC checking
On Sat, May 25, 2019 at 8:33 AM Johann Obermayr via Syslinux <syslinux at syslinux.org> wrote: > > Hello, > > Is there a function to check a bzImage CRC ? > > If (ImageCRC("/bzImage") == -1) > Load_kernel("/BACKUP/bzImage") or what else > > Thanks > > Regards > Johann It doesn't appear so. I'm assuming
2014 Jan 15
1
extlinux device trouble
On Wed, Jan 15, 2014 at 3:26 AM, Johann Obermayr <johann.obermayr at sigmatek.at> wrote: > Am 15.01.2014 04:57, schrieb Gene Cumm: > >> On Tue, Jan 14, 2014 at 10:50 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> >>> On Tue, Jan 14, 2014 at 9:28 AM, Johann Obermayr >>> <johann.obermayr at sigmatek.at> wrote: >>>>
2014 Jan 15
3
extlinux device trouble
On Tue, Jan 14, 2014 at 10:50 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Tue, Jan 14, 2014 at 9:28 AM, Johann Obermayr > <johann.obermayr at sigmatek.at> wrote: >> Hello, >> >> i'm using version 4.07. >> On my computer extlinux does not work. >> after debugging, i found the trouble. >> >> in the function parse_mountinfo there
2014 Jan 14
2
extlinux device trouble
Hello, i'm using version 4.07. On my computer extlinux does not work. after debugging, i found the trouble. in the function parse_mountinfo there was using a function get_string. in the function get_string there was a line (42) } else if (ch == '\\') { but in my mountinfo list, there was \ , but not with octal digit. so the function get_string will fail. here are some information
2014 May 07
2
Issues with syslinux_run_command(str) and parameters
>> >> >From the perspective of a final user, breaking the prior behavior of >> directives needs to have very clear advantages. > > Reviewing the commit history, I would say that the prior behavior is currently broken. > > The ALLOWOPTIONS feature was added in 2004: >
2019 Jun 08
0
Kernel Image CRC checking
On 6/7/19 10:19 PM, H. Peter Anvin via Syslinux wrote: >> >> It doesn't appear so. I'm assuming you're referring to the CRC32 >> present in Linux x86 boot protocol 2.08+ found in Linux versions >> 2.6.26+ ? libupload has a CRC-16 function. zlib has a CRC-32 >> function but looks like it's initialized with different >> polynomial/remainder.
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 May 05
2
Issues with syslinux_run_command(str) and parameters
> I didn't see any further communication here; would anyone be > against my submitting/proposing a patch for this? Contributions are always welcome. > > I can see two possible approaches. One approach would be to > isolate the restriction on user commands away from > syslinux_run_command / load_kernel. > > Another would perhaps be to add support for a
2011 Apr 01
1
[GIT PULL] elflink ldlinux
The following changes since commit 8c576f1fe03e34879921311f46613a35c6530000: Merge remote-tracking branch 'mfleming/for-hpa/elflink/fix-compiler-warnings' into elflink (2011-03-16 12:53:58 -0700) are available in the git repository at: git://git.zytor.com/users/mfleming/syslinux.git for-hpa/elflink/ldlinux Matt Fleming (1): ldlinux: Perform auto-boot if NOESCAPE set in config
2014 Apr 29
2
Issues with syslinux_run_command(str) and parameters
> More context to this: syslinux_run_command calls into load_kernel(), and somewhere behind load_kernel things break. This is also broken at the boot: console prompt. Any commands executed at the boot: prompt also lose all parameters. > > > With the latest 6.03pre I'm seeing an issue where no parameters are passed to the image executed via syslinux_run_command(). > > An
2014 May 08
2
compile error about 6.0.2
make -r -C /mlsyslinux -f /mlsyslinux/Makefile SRC="/mlsyslinux" \ OBJ=/mlsyslinux objdir=/mlsyslinux bios make[1]: Entering directory `/mlsyslinux' make -r -C /mlsyslinux/bios -f /mlsyslinux/Makefile SRC="/mlsyslinux" \ objdir=/mlsyslinux/bios OBJ=/mlsyslinux/bios HAVE_FIRMWARE=1 \ ARCH=i386 LDLINUX=ldlinux.c32 all make[2]:
2023 Mar 28
1
syslinux starting a efi application
Hello, is there a way to start a efi-application (bios update tool) from syslinux ? best regards Johann
2019 Jun 08
2
Kernel Image CRC checking
On 6/7/19 10:25 PM, H. Peter Anvin via Syslinux wrote: >> >> However, the CRC polynomial for zlib and the Linux kernel should both be the >> same: 0x04c11db7. > > I just double-checked, and the CRC tables are indeed identical. I was pretty > sure, because I wrote that code a long time ago... > Ah, it seems that zlib's CRC32 returns the binary inverse of the
2014 May 12
2
compile error about 6.0.2
It's x86 arch.The reason of compiling pxelinux only is that i want to add tcp support, not http and ftp. ? 2014-05-08 18:09:15?"Gene Cumm" <gene.cumm at gmail.com> ??? On May 7, 2014 11:54 PM, "??" <muliu92 at 163.com> wrote: > make[4]: Entering directory `/mlsyslinux/bios/com32/libupload' > gcc -Wp,-MT,cpio.o,-MD,./.cpio.o.d -std=gnu99 -m32
2019 Jun 08
2
Kernel Image CRC checking
On 6/7/19 10:48 PM, H. Peter Anvin via Syslinux wrote: > On 6/7/19 10:34 PM, H. Peter Anvin via Syslinux wrote: >> On 6/7/19 10:25 PM, H. Peter Anvin via Syslinux wrote: >>>> >>>> However, the CRC polynomial for zlib and the Linux kernel should both be the >>>> same: 0x04c11db7. >>> >>> I just double-checked, and the CRC tables are
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
2019 May 24
3
syslinux efi64 test c32 module
Hello, does someone have test syslinux EFI64 bootloader in qemu ? we have a own c32 module. And some build of this module will hang booting. Now I will (debug / test) this in qemu. Is that possible? if so, what do I need except qemu-syste-x86-64. And how do I have to start the qemu? Thanks & regards Johann
2014 Nov 21
1
[PATCH 1/2] libupload: fix parallel build issue
Fixed: cp -r syslinux-6.01/com32/libupload/*.h image/usr/share/syslinux/com32/include/ [snip] rm -rf image/usr/share/syslinux/com32/include [snip] cp: cannot create regular file `image/usr/share/syslinux/com32/include/serial.h': No such file or directory The cp is happened in the "libupload" dir, while "rm -fr" is happend in "lib" dir, let "libupload"
2014 Apr 29
2
Issues with syslinux_run_command(str) and parameters
With the latest 6.03pre I'm seeing an issue where no parameters are passed to the image executed via syslinux_run_command(). An example of this is whichsys.c32, which uses this. E.g., using an example from the wiki page - whichsys.c32 -iso- chain.c32 hd0 -sys- chain.c32 hd1 swap - results in a loop back to the isolinux menu as chain.c32 receives no parameters. Similarly, using -iso- memdisk