search for: bioses

..._phys(high_mem_pgend)-1: + * RAM above 4GB + * extra_mem written to CMOS is represented as 64kb chunks + */ + extra_mem = hvm_info->high_mem_pgend; + extra_mem = (extra_mem > 0x100000) ? + (((extra_mem - 0x100000) << PAGE_SHIFT) >> 16) : 0; + /* All BIOSes: conventional memory (CMOS *always* reports 640kB). */ cmos_outb(0x15, (uint8_t)(base_mem >> 0)); cmos_outb(0x16, (uint8_t)(base_mem >> 8)); @@ -166,6 +176,11 @@ static void cmos_write_memory_size(void) /* Some BIOSes: alternative extended memory (64kB chunks above 16MB)....

...c void __devinit init_amd(struct cp 3DNow is IDd by bit 31 in extended CPUID (1*32+31) anyway */ clear_bit(0*32+31, c->x86_capability); +#ifdef CONFIG_X86_64 + if (c->x86 == 0xf && c->x86_model < 0x14 + && cpu_has(c, X86_FEATURE_LAHF_LM)) { + /* + * Some BIOSes incorrectly force this feature, but only K8 + * revision D (model = 0x14) and later actually support it. + * (AMD Erratum #110, docId: 25759). + */ + unsigned int lo, hi; + + clear_bit(X86_FEATURE_LAHF_LM, c->x86_capability); + if (!rdmsr_amd_safe(0xc001100d, &lo, &hi)) { + hi...

I have released SYSLINUX 2.10-pre2. I *really* would like testing reports for this one, especially ISOLINUX, since I've included Knut Petersen's fix for Award BIOSes... Changes in 2.10: * MEMDISK: Handle images compressed with zip as well as with gzip. Some Windows-based image tools apparently generate these kinds of images by default. Patch by Patrick LoPresti. * Major menu improvement from Murali Ganapathy...

Hi I have used pxelinux successfully in some situations. However, I am unable to boot IBM NetVista thin clients using pxelinux. The kernel that does boot up these thin clients over the net is in elf format (it is called kernel.2200). # file kernel.2200 kernel.2200: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, not stripped So, I would have liked to compile

...ined at boot time for devices which are considered hard disks by the BIOS. Unfortunately, this is not possible for devices which are considered floppy disks, which includes zipdisks and LS-120 superfloppies. The -z option is useful for USB devices which are considered hard disks by some BIOSes and zipdrives by other BIOSes. $ ./syslinux-git/working-directory/linux/syslinux Usage: ../syslinux-git/working-directory/linux/syslinux [options] device --offset -t Offset of the file system on the device --directory -d Directory for installation target --install -i Install over...

...ca07ff1f0a5 -r ae10d7804168 xen/drivers/acpi/apei/erst.c --- a/xen/drivers/acpi/apei/erst.c Tue Aug 09 17:48:16 2011 +0100 +++ b/xen/drivers/acpi/apei/erst.c Tue Aug 09 18:06:43 2011 +0100 @@ -715,13 +715,7 @@ static int __init erst_check_table(struct acpi_table_erst *erst_tab) { - /* - * Some old BIOSes include the ACPI standard header in the ERST header - * length; new BIOSes do not. Our check allows for both methods. - */ - if ((erst_tab->header_length != - (sizeof(struct acpi_table_erst) - sizeof(erst_tab->header))) - && (erst_tab->header_length != sizeof(struct acpi_table_erst...

Hi H. Peter Anvin wrote the following at 20:55 26.05.2002: >.... >Most BIOSes are highly cantankerous booting off extended-format >floppies. They may not be able to read more than a single sector at a >time, and then have to wait for the floppy to rotate a full turn to read >the next sector. SYSLINUX will fall back on this mode of operation if it >has to....

...3:33:13.000000000 +0400 +++ syslinux-4.02/libinstaller/syslxopt.c 2010-08-17 22:37:24.955852630 +0400 @@ -125,5 +125,5 @@ void __attribute__ ((noreturn)) usage(in "\n" " The -z option is useful for USB devices which are considered\n" - " hard disks by some BIOSes and zipdrives by other BIOSes."); + " hard disks by some BIOSes and zipdrives by other BIOSes.\n"); exit(rv);

...hinkpad x200 and thinkpad x1 carbon) using syslinux 3.05 or syslinux 4.05. And i change localboot 0xffff to localboot 0x80, boot from local drive is available. I find "0x80 is the primary hard drive. The special value -1(0xffff) causes ISOLINUX to report failure to the BIOS, which, on recent BIOSes, should mean that the next device in the boot sequence should be activated" on syslinux wiki. Isn't the syslinux and bios compatible, can I upgrade syslinux to use localboot 0xffff? Thanks!

...require you to hit a key to make them actually boot from the disc. I've kind of tried to emulate this behavior using chain.c32, but, it requires me to specify which harddrive, and I'd rather see an independant setup. I've tried localboot -1, but, it seems it's not supported by all BIOSes (including that of my previous system -- haven't tested my current one.) Of course, if such a thing were possible, it'd need to be an optional thing and with configurable time (I don't like the default short periods because sometimes it takes that long for the display and monitor to co...

Hello Peter & Jeremy, I've found an ordinary desktop PC (with Phoenix Award BIOS 6.00PG) that won't boot off a USB stick created by livecd-tools-024 with syslinux (tested both versions 3.75 and 3.81). The boot process drops to the "boot:" prompt with an error message: could not find kernel image: linux The same USB stick boots fine on any other computer I could find.

...compile a custom ipxe.efi binary with an embedded script > that downloads syslinux.efi and the config files before executing "chian > syslinux.efi". > iPXE would still be load via TFTP. If the issue is to load even the NBP via HTTP, then the BIOS has to support it. Most UEFI BIOSes do, but you have to enable it in BIOS. Its typically next to the PXE BOOT settings, and you can choose IPv4, IPv6, HTTP, etc. Older UEFI BIOSes may not support this...

Hello, are there known issues with some bioses not booting from Superfloppy format? All I get is the Syslinux (c) line and nothing else happens afterwords. Everything works fine if a partition is added to the device. Unfortunately however the target device can not be partitioned. Any hint? Sven -- Why are there so many Unix-haters-handboo...

Howdy to all, We've been using isolinux quite successfully for quite some time now, and I have come across a couple of laptops where isolinux balks at my config file.. Upon booting on this systems, the image background appears corrupted, and at the boot prompt, the following happens automatically. Unknown keyword in config file. Could not find kernel image: 1 boot: Any label input here

...to extract information (like what dmidecode provides) from within PXELINUX and, based on this information, selectively perform an action? What I'm trying to do is provide a method of flashing the BIOS of our HP Linux workstations but different workstations use different methods of updating the BIOSes. For example, the xw9300 uses 'rompaq' where the xw8400 uses 'flashbin'. I have this working for the xw9300 workstations but I don't want to rely on people selecting the correct option, I rather parse 'Handle 0x0002' and choose automatically based on 'Product Name...

...y, microsoft[ish] systems. First two examples, then the improvement idea. Example #1 My usb stick has zip-compatible geometry, which should work fine both in hdd and zip modes. It usually does, at least as far as syslinux and normal software is considered - excluding some of a bit older award bioses that regardless of everything, seem to forcibly treat the usb stick as a floppy (or some unspecified alien), unless the actual filesystem is FAT16 (and I mean /actual/ filesystem, not partition type flag in mbr - this is the same issue as once described in this thread - http://syslinux.zytor.co...

...ere in sight. That means that compliance with EDD-4 requires returning the last-booted drive number regardless of the user's DL query. _However_, eltorito.sys has to deal with _other_ [non-EDD-4] cases, which one reason for why it performs a scan. 3. Since probing 0xFF is buggy on some BIOSes, eltorito.sys prefers to scan upward. 4. Since the general strategy of injecting the El Torito drive number and shifting the conflicting drive number up can be adopted (for consistency) for no-emulation mode, then a pre-existing 0xA0 can be shifted to 0xA1 and a upward scan is preferred for...

...y current theory is that vendors prefer to record > a cylinder aligned end CHS address over recording > an end CHS address which exploits the whole capacity. > This is used as an (inofficial ?) protocol to publish > the CHS factors H' and S'. > Indeed it is -- at least some BIOSes "deduce" the H/S to use from that. -hpa

...to put a 60GB hard disk into Gateway 2000 Pentium 150 (from '96 or '97 or so I think) running FreeBSD 4.8 RELEASE. Can anybody tell me how successful this is likely to be? Will I be able to use the full capacity of the drive? I seem to recall that the trick with large hard disks and old BIOSes is to disable the drive in the BIOS and let the OS detect the disk itself... is this the case with FreeBSD as well? Thanks. - -- Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP ID: 0x33795A2C KDE/Qt/C++/PHP Developer: http://www.kde.org --...

I am still unable to build and boot large floppy images. 1.44, 2.88, and any size HD images work great. No problem. However I have BIOSes with problems booting HD images and would like to get large floppy working. I have tried every script and method I could find with PC DOC 7 and MS DOS 6.22. I have spent too much time analyzing boot sectors. So a few questions: 1. Who has actually see it work? 2. How did you make the image?...