search for: 63488

I needed these for some work I'm doing in clang... -------------- next part -------------- A non-text attachment was scrubbed... Name: set.patch Type: application/octet-stream Size: 1925 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090211/82192816/attachment.obj>

...l Section Header Entry) PlatformId: 0xef (EFI) Section Entries: 1 ID: "" Boot Catalog Section Entry: Entry is bootable Boot Media emulation type: no emulation Media load address: 0 (0x0000) System type: 0 (0x00) Load Sectors: 63488 (0xf800) Load LBA: 23301 (0x00005b05) $ dumpet -i archlinux-2013.10.03-dual.iso Validation Entry: Header Indicator: 0x01 (Validation Entry) PlatformId: 0x00 (80x86) ID: "" Checksum: 0x55aa Key bytes: 0x55aa Boot Catalog Default Entry:...

-- Re-sent as original may be stuck at awaiting "authorisation" (originally sent before I joined the mailing list) Hi All, It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via CD or DVD on older - non-UEFI - systems. Any attempt to do so will result in the following error message: ISOLINUX 6.02 ETCDisolinux: Disk error 01, AX = 4279, drive FE It is still possible to

Hello ! Asterisk 1.0.9 running on Linux 2.6.12. I'm not able to call iax2 channels. There can be no translation path found. When I try to call from a ZAP PRI channel the following error occurs: channel.c:1891 ast_request: No translator path exists for channel type IAX2 (native 63488) to 72 dial_exec: Unable to create channel of type 'IAX2' What is wrong ? Here is my iax.conf: [general] bindport=4569 language=de disallow=all jitterbuffer=no tos=lowdelay [iax-test1] type=friend username=iax-test1 secret=xxxxxx context=from_IAX host=dynamic qualify=yes allow=alaw all...

...Id: 0xef (EFI) > Section Entries: 1 > ID: "" > Boot Catalog Section Entry: > Entry is bootable > Boot Media emulation type: no emulation > Media load address: 0 (0x0000) > System type: 0 (0x00) > Load Sectors: 63488 (0xf800) > Load LBA: 23301 (0x00005b05) > > $ dumpet -i archlinux-2013.10.03-dual.iso > Validation Entry: > Header Indicator: 0x01 (Validation Entry) > PlatformId: 0x00 (80x86) > ID: "" > Checksum: 0x55aa > Key by...

...n from DOS bootblock is: The data for partition 1 is: sysid 0 (0000),(unused) start 0, size 1081344 (528 Meg), flag 80 (active) beg: cyl 0/ head 0/ sector 1; end: cyl 527/ head 63/ sector 32 The data for partition 2 is: sysid 239 (0xef),(EFI System Partition) start 248, size 63488 (31 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: <UNUSED> The data for partition 4 is: <UNUSED> ========================================================================== Humm... well... son-of-a-gun!!...

...r de 1 * 512 = 512 octets Taille de secteur (logique / physique) : 512 octets / 512 octets taille d'E/S (minimale / optimale) : 512 octets / 512 octets Identifiant de disque : 0x44533712 P?riph?rique Amorce D?but Fin Blocs Id Syst?me /dev/loop1p1 * 0 129023 64512 0 Vide /dev/loop1p2 136 127111 63488 ef EFI (FAT-12/16/32) bash-4.2# ?--- I no nothing about the ISO9660 spec, but I assume that the firmware should see the EFI partition. Is that right? I also assume that the firmware can "see" the content of the EFI partition as if I mount efi.img. Right? let's mount it: ?--- bash-4.2...

...538112 ( 3981.1 kb/s) 23040 ( 3214.3 kb/s) 56320 ( 3928.6 kb/s) 27648 ( 3000.0 kb/s) 314368 ( 3837.5 kb/s) 17920 ( 2916.7 kb/s) 249344 ( 3927.4 kb/s) 27648 ( 3000.0 kb/s) 18432 ( 3000.0 kb/s) Output of backup script on P4 config: 37888 ( 146.2 kb/s) 63488 ( 73.8 kb/s) 59392 ( 92.1 kb/s) 29184 ( 67.9 kb/s) 24576 ( 114.3 kb/s) 97280 ( 74.9 kb/s) 137216 ( 79.7 kb/s) 56320 ( 87.3 kb/s) 36352 ( 84.5 kb/s) 88451 ( 82.3 kb/s) 96256 ( 74.7 kb/s) 62464 ( 72.5 kb/s) 606180 ( 76.2 kb/s...

Hi, Ady wrote: > http://www.syslinux.org/archives/2015-October/024526.html I still have it in my mailbox: ADY4UEFI.IMG in ADY4UEFI.ZIP. The test results are the same as with Didier's partition image. Wrapped in an ISO and presented as -cdrom it reboots in cycles. Presented as -hda it boots as naked disk image and as part of a GPT enhanced ISO 9660. > the wiki page needs

Hi, (mixing statements from various mails) Ronald F. Guilmette wrote: > To repeat, I already do know exactly how to set or unset the bootable > flag. Sorry for not getting this right on the first reading. I currently understand that a set active/bootable flag prevents the USB stick from showing up in BIOS, and that without that flag it begins to boot but fails with files not found.

...9 10:00:44 0 0 0 0 2011-01-29 10:00:45 0 0 0 0 2011-01-29 10:00:46 0 0 0 0 2011-01-29 10:00:47 0 0 0 0 2011-01-29 10:00:48 0 0 0 0 2011-01-29 10:00:49 0 0 0 0 2011-01-29 10:00:50 0 0 0 0 2011-01-29 10:00:51 0 0 0 0 2011-01-29 10:00:52 0 0 0 0 2011-01-29 10:00:53 8 0 20480 0 2011-01-29 10:00:54 42 0 63488 0 2011-01-29 10:00:55 58 4 721920 655360 2011-01-29 10:00:56 16 3 29696 524288 2011-01-29 10:00:57 0 0 0 131072 2011-01-29 10:00:58 17 0 27648 0 2011-01-29 10:00:59 26 5 119808 786432 2011-01-30 10:00:00 0 0 0 0 2011-01-30 10:00:01 0 0 2560 0 2011-01-30 10:00:02 0 0 0 0 2011-01-30 10:00:03 0 0 0 0...

Hello, I have an odd problem on a dual processor, dual core Opteron system. Obviosously it is x86_64 so should have no problem with large amounts of RAM. The system has 4 GB installed (2GB on each processor). If I boot the system with a fresh install of Debian Etch it sees all the memory fine. dmesg reports: Memory: 4107008k/5242880k available (1929k kernel code, 86836k reserved, 864k data, 176k