search for: l262

Until Syslinux 3.86, isolinux.bin contained a checksum that was calculated by 'core/checksumiso.pl'. The checksum is related to the patching of the boot info table. During May 2009, a commit by Peter deleted the checksumiso.pl file. The commit is: core: LZO compress the PM part of the core repo.or.cz/syslinux.git/commit/0d82b71304d596d80f3c4520f9dcf90048ca50b7 And so, since

...thing to cross post to linux-usb? I guess, although they might need to know some additional details about your libusb configuration (real libusb-0.1.x, or libusb-1.x with libusb-compat). Here is the relevant portion of the code: https://github.com/networkupstools/nut/blob/master/drivers/libusb.c#L262 > On Mon, Nov 23, 2015 at 8:47 PM, Charles Lepple <clepple at gmail.com> wrote: > On Nov 20, 2015, at 11:22 AM, Nicholas Leippe <leippe at gmail.com> wrote: > > > > 1389.279158 Trying to match device > > 1389.279164 Device matches > > 1389.279169...

.../usr/lib/ISOLINUX/isolinux.bin and the checksum changed from 0x09e675b8 to 0x8cc6977a. But i never had to change the algorithm in libisofs in order to keep the result bootable. The isolinux,bin binaries do boot and in http://repo.or.cz/syslinux.git/blob/refs/heads/master:/core/isolinux.asm#l262 i see a checksum computation and later a test which would lead to label "kaboom" if not matching. So where did the checksum 0x09e675b8 in Sid's installed isolinux.bin come from ? The source code sets it to 4-byte value 0xdeadbeef See the comments from http://repo.or.cz/syslinux...

This issue has been occurring for years on my setup. OS: Gentoo most recent kernel: 4.1.12 UPS: Eaton Powerware 9130 rackmount 2000kVA, connected via USB The upsdrv service dies and must be restarted several times a day. Zero output to dmesg or any other log other than failed reattempts reporting no such file or directory errors. "/lib64/nut/usbhid-ups -DDD -q -a powerware" exited 1

https://bugzilla.mindrot.org/show_bug.cgi?id=2564 Bug ID: 2564 Summary: ssh_config AddKeysToAgent doesn't set key name/path Product: Portable OpenSSH Version: 7.2p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee:

...; > I guess, although they might need to know some additional details about > your libusb configuration (real libusb-0.1.x, or libusb-1.x with > libusb-compat). > > Here is the relevant portion of the code: > > https://github.com/networkupstools/nut/blob/master/drivers/libusb.c#L262 > > > On Mon, Nov 23, 2015 at 8:47 PM, Charles Lepple <clepple at gmail.com> > wrote: > > On Nov 20, 2015, at 11:22 AM, Nicholas Leippe <leippe at gmail.com> wrote: > > > > > > 1389.279158 Trying to match device > > > 1389.279164 Devi...

...x.bin > > and the checksum changed from 0x09e675b8 to 0x8cc6977a. > > But i never had to change the algorithm in libisofs in order to keep the > result bootable. The isolinux,bin binaries do boot and in > http://repo.or.cz/syslinux.git/blob/refs/heads/master:/core/isolinux.asm#l262 > i see a checksum computation and later a test which would lead to label > "kaboom" if not matching. > > > So where did the checksum 0x09e675b8 in Sid's installed isolinux.bin come > from ? > > The source code sets it to 4-byte value > 0xdeadbeef >...