search for: 32kib

On 03/18/2017 04:15 PM, Ady Ady via Syslinux wrote: > >> On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote: >>> _ With the USB device connected to (one of) the problematic >>> computer(s), power up the system and get into the BIOS setup. In >>> the BIOS setup screen(s), change the boot order in such way that >>> the USB device is recognized as first

...x86-64 constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority *-cache:0 description: L1 cache physical id: 5 slot: L1-Cache size: 32KiB capacity: 32KiB capabilities: internal write-back data *-cache:1 description: L2 cache physical id: 6 slot: L2-Cache size: 2MiB capacity: 2MiB capabilities: internal varies unified *...

On 03/19/2017 01:12 AM, Ady Ady via Syslinux wrote: > Regarding distros for older computers, there are several. The > problem, at least at this point, is bootability. Although Antix is > for older computers, it is also based on Debian and the latest > ISOLINUX will also be bigger than 32KiB. Perhaps Knoppix or some (of > the many) PuppyLinux would still use ISOLINUX 4.xx or older. SUSE > derivatives also use v. 4.xx. Slackware derivatives too. DSL used to > provide a floppy-emulation ISO image, but it is no longer maintained > and not suitable for USB either. On 03/21/20...

...with no problems, while some might need a floppy-emulation mode. Back on topic, there are too many reasons for these systems to fail with this Debian ISO image. For example, some BIOS implementations don't "like" when the bootloader file, "isolinux.bin", is bigger than 32KiB. Others don't like when the bootloader file is located on LBA values over a certain limit. Incidentally, Debian 8.7 is using ISOLINUX 6.03+, which happens to be bigger than 32KiB, whereas isolinux.bin version 4.xx was much smaller than 32KiB. We could even mention partition alignment issues...

...that if using isolinux.bin from syslinux-4.07 works fine in both > > cases (under high LBA addreses and low). > > So maybe it is not BIOS but SYSLINUX which does not like > the high addresses. Or both of them in happy cooperation. I guess that being isolinux.bin 4.07 smaller than 32KiB (24KiB), while isolinux.bin 6.02 being bigger (42KiB), and with the addition of multiple alternative boot images in the same ISO, the chances of isolinux.bin being located on a higher sector in the media seem to be higher. So, perhaps the potential problem was always there, just that the chan...

...uot;USB" options, typically "USB-AUTO", "USB-HDD", "USB-ZIP", "USB-FLOPPY", among others. As I mentioned in a prior email, using an older version of ISOLINUX (and related packages) would probably give you an "isolinux.bin" file smaller than 32KiB, which is one of the possible solutions (if its current size happens to be the source for failure). In another email, you mentioned your desire to use USB devices instead of optical ones. You do not need to build ISO images just for USB devices. As I explained before, there is an alternative me...

...really large size, OpenSSH will just close the connection as soon as it sees the header with the large write. the server hardcodes 256KiB (SFTP_MAX_MSG_LENGTH) and any attempt to write anything larger than that is immediately rejected. this is not friendly and clients basically have to default to 32KiB all the time and force users to manually select a size that they happen to know the server they're connecting to supports. if the server supports an extension to dynamically query the exact limits the server imposes, the client can start with the 32KiB default, and then automatically increase...

...be a CPU bottleneck? Though we should also bear in mind that compression can be pipelined with writes in i) and debug info loading could be lazy in ii) (e.g. for highly compressible data we've generally seen ~10MiB/s output bandwidth on single thread i7 @3.2GHz memory to memory for zlib9 with 32KiB window, that doesn't stack up well against modern IO) How is the compression implemented in lld? Is it chunked and therefore paralellizable (and able to be pipelined with IO) or more serial? I think the intention is i) so we'd be happy to link a few of our game titles with varying compres...

...than the boot _order_ screen. If the main screen in your BIOS can list the USB device as the first device in the list, and it can also be set as the first device in the boot order settings, then the chances of booting successfully can increase. This procedure is independent of the potential 32KiB limitation for isolinux.bin for certain BIOS implementations. This potential additional issue can still be an impediment to boot in certain systems anyway. The same goes for other potential issues. Yet, if the BIOS cannot list / detect the USB device as if it was a common HDD (UNrelated to the...

On Sun, Mar 19, 2017 at 04:34:06PM -0700, David Christensen via Syslinux wrote: > > If anyone knows of a Linux distribution targeted at 32-bit hardware, > please say so. > Please elaborate

...://cdrecord.berlios.de/private/man/mkisofs-2.0.html So, should the eltorito_boot_image for -no-emul-boot (isolinux.bin) be (better) limited to 16 sectors (for maximum compatibility, for any optical media type)? And, is there any method to reduce its size (which in Syslinux 6.02 is bigger than 32KiB)? Thanks and Best Regards, Ady.

Hi, Ady wrote: > I guess that being isolinux.bin 4.07 smaller than 32KiB (24KiB), > while isolinux.bin 6.02 being bigger (42KiB), and with the addition > of multiple alternative boot images in the same ISO, the chances of > isolinux.bin being located on a higher sector in the media seem to be > higher. > > So, perhaps the potential problem was alw...

...bear in mind that >> compression can be pipelined with writes in i) and debug info loading could >> be lazy in ii) >> >> (e.g. for highly compressible data we've generally seen ~10MiB/s output >> bandwidth on single thread i7 @3.2GHz memory to memory for zlib9 with 32KiB >> window, that doesn't stack up well against modern IO) >> >> How is the compression implemented in lld? Is it chunked and therefore >> paralellizable (and able to be pipelined with IO) or more serial? >> >> I think the intention is i) so we'd be happy t...

...ession can be pipelined with writes in i) and debug info loading could >>>> be lazy in ii) >>>> >>>> (e.g. for highly compressible data we've generally seen ~10MiB/s output >>>> bandwidth on single thread i7 @3.2GHz memory to memory for zlib9 with 32KiB >>>> window, that doesn't stack up well against modern IO) >>>> >>>> How is the compression implemented in lld? Is it chunked and therefore >>>> paralellizable (and able to be pipelined with IO) or more serial? >>>> >>>> I...

David Christensen wrote: > It seems that most Linux distributions I look at are dropping support > for 32-bit hardware. Aren't you using Debian? AFAIK jessie supports i586, so if Pentium is old enough for you you're good to go for likely at least two more years. After that I guess I'd be using old unsupported Debians for the ancient ones. I don't have this old hw on the

On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote: > Some of the things you should / could (re)test / (re)try: > > _ Verify the md5sum of the ISO image. SHA256 verified for downloaded image and for contents of USB flash drive (see below). > _ Is this particular USB device _still_ capable of booting newer > computers? Yes. > What happens if you would try _again_ to boot a

On 11/25/2013 08:40 AM, Thomas Schmitt wrote: > Hi, > > Ady wrote: >> I guess that being isolinux.bin 4.07 smaller than 32KiB (24KiB), >> while isolinux.bin 6.02 being bigger (42KiB), and with the addition >> of multiple alternative boot images in the same ISO, the chances of >> isolinux.bin being located on a higher sector in the media seem to be >> higher. >> >> So, perhaps the po...

http://bugs.freedesktop.org/show_bug.cgi?id=11918 Summary: drmMap of framebuffer failed Product: Mesa Version: CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: pmandin at

I can't seem to get the read and write performance better than approximately 40MB/s on an ext2 file system. IMO, this is horrible performance for a 6-drive, hardware RAID 5 array. Please have a look at what I'm doing and let me know if anybody has any suggestions on how to improve the performance... System specs: ----------------- 2 x 2.8GHz Xeons 6GB RAM 1 3ware 9500S-12 2 x 6-drive,

...Kontron Europe GmbH physical id: 0 version: C.0.4 serial: NKD130002 *-firmware description: BIOS vendor: Kontron Europe GmbH physical id: 0 version: MVV1R111 X64 date: 10/14/2014 size: 128KiB capacity: 4032KiB capabilities: pci upgrade shadowing cdboot bootselect edd int5printscreen int9keyboard int14serial int17printer int10video pc98 acpi usb biosbootspecification netboot uefi *-cpu description: CPU product: Atom vendor: Intel Corp. physical id: 4...