search for: tullverket

Hello. I've been testing pxelinux.0 (4.04-pre14) on some laptops: - HP EliteBook 6930P with BIOS F.18. - HP EliteBook 8440P with BIOS F.06. - Dell Latitude E4310 with BIOS A06. When booting pxelinux.0, the machines first display some random letters in different colors and then reboot. We've been using 4.02 for some time without problems. I've tested 4.03 too and it seems to work.

I know quite a few people have interest in internationalizing the menu system. This is a tricky problem, since have a full-blown rendering engine for the more complex languages (Indic, Semitic and East Asian languages being the main ones that have substantial complexities.) Given that, I was thinking that the most sensible thing might be to pre-render strings (basically menu items and

The gPXE in the Syslinux tree is ridiculously old. We could either replace it with iPXE or just drop it, giving people a recipe for how to integrate with iPXE themselves. What do people think? -hpa

Hello. I have the same problem as many others, PXELINUX (or rather menu.c32) does not work with Marvell Yukon 88E8055 cards. I have two machines, Fujitsu LIFEBOOK S7110 and P7230 that have the same problem; menu.c32 will not load. The version of Marvell's base code is 1.10.1.3 (20060516), Yukon PXE v5.14.1.3 (20060704), in the machines I have tested. I have tried downgrading the BIOS on the

Hello, I saw this in the release notes for 4.00: "PXELINUX: TFTP URL syntax (tftp://) supported even when not running gPXE/gpxelinux" I can't find any info describing this new functionality (searched wiki and mailing list), I'm guessing you can now use tftp:// in the paths, e g: LABEL mylabel KERNEL tftp://servername/path/to/mykernel APPEND myoptions Correct? I've

> The gPXE in the Syslinux tree is ridiculously old. We could either > replace it with iPXE or just drop it, giving people a recipe for how to > integrate with iPXE themselves. > > What do people think? My vote is replace with iPXE. I've manually replaced gPXE with iPXE for years, works like charm. I suggest updating the Makefile to use undionly.kkkpxe because of the change

Hello. We are using gpxelinux from SYSLINUX 4.02. We recently purchased some HP Proliant BL460c G6 servers with Broadcom BCM 57711 10Gbit NICS. We have a very simple pxelinux.gpxe script compiled into gpxelinux.0: #!gpxe set use-cached 1 dhcp net0 chain http://webserver/gpxe/gpxe.php?IP=${net0/ip} The PHP script dynamically creates a config file that looks something like this: #!gpxe set

Hello. We've been using a very old version of SYS-/PXELINUX, 3.36, going by the proven "if it works, don't break it" philosophy. We us it mostly to load floppy disk images to kick off OS installations. Unfortunately we've recently had some PXE menu problems (USB keyboard stopped working) for a certain Fujitsu PC model, and decided to upgrade to the latest version, i e 3.84.

Hi. I'm working on replacing a PXELINUX/MEMDISK loaded DOS based installation image with a PXELINUX/MEMDISK loaded WinPE ISO image. So far everything seems to work well (appending "bigraw" to memdisk solved booting problems on several machines), but I kind of miss the option of using getargs.com to get/set environment variables from the memdisk command line. Is there any way to

Hi. We've been using PXELINUX for years, to kick off OS installations (floppy images) and booting assorted tools. The addition of ISO support in memdisk opened up some new alternatives that we also use, e.g. booting WinPE ISO images over PXE. Today I downloaded a BIOS for a HP EliteBook 8440p and discovered that the BIOS file is 3 MB. I could probably squeeze it onto a 2.88 MB floppy image