similar to: Unicode problem.

Hello list, I'm trying to reuse a fairly old PC based embedded system. It has no video output at all, no VGA, nothing older, and no keyboard / mouse connectors. The console is on a standard RS232 interface, including BIOS output and the minimal BIOS loader. The BIOS emulates / redirects text output to and keyboard input from the console RS232 interface, but unfortunately, this emulation

Hello! I've been attempting to add EFI support to a linux live distro (slax), it's built on a syslinux bootloader. I can get EFI to work using menu.c32 on syslinux 6.03; however ideally we'd like the VESA menu as well. When we use the vesamenu.c32 and libcom32.c32 from 6.03 we end up with a blank screen and the machine seems to hang. I've tried adding MENU RESOLUTION based on

Hi: Two scripts (mkbd.fails and mkbd.works) are attached to this message. The only difference between them is in how syslinux.cfg (on a RedHat boot image) is replaced. mkbd.fails: syslinux.cfg is replaced via "mv -f". vmlinuz can't be found. mkbd.works: syslinux.cfg is replaced via "cp". vmlinuz is found. The only difference I can see between these two methods is that

--32u276st3Jlj2kUU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all (two) klibc hackers! 8) Here's the stuff I've been using to build an initramfs image and run it on one of my machines. Unfortunately, the "init" script contains hard coded information about where to find the root, etc, but it should give people a working base to start from. It

Hi there, I failed to boot an installer in a VMware player (Version6.0.3 build-1895310) using syslinux 6.03, be it off an hybrid ISO image and an USB stick. Booting succeeds if the VM is set to use a BIOS firmware with both media, but fails using an efi firmware. Trying to boot off the ISO image I get an error message "The firmware encountered an unexpected exception" Trying to

I have syslinux booting slax off of a usb stick but in the process I think I may have found a bug in syslinux im using version syslinux-3.31 my syslinux.cfg use to look as follows <== beginning display boot/splash.cfg default slax autoexec=startx prompt 1 timeout 40 F1 boot/splash.txt F2 boot/splash2.txt F3 boot/splash.cfg label slax kernel boot/vmlinuz append vga=769 changes=slaxsave.dat

There is a maximum of 255 characters of parameters you can pass to the kernel. At least that's what I recall, but I may be wrong. -----Original Message----- From: Roberto De Leo [mailto:deleo at unica.it] Sent: Thursday, October 03, 2002 5:19 PM To: syslinux at zytor.com Subject: [syslinux] maximum number of characters in APPEND Hi, I wonder whether there is a maximum number of

Hi all, I've searched the depths of the resources on the internet; however I'm having trouble deploying a pxeboot solution via pxelinux. So far what I have successfully implemented in my infrastructure is a successful pxeboot setup for FreeBSD ( without the use of pxelinux ). I'd ultimately like to have a solution that will allow me to choose a network install of various Unix-like

Hello, I am having a problem with the second-generation of a custom isolinux boot CD for one of the PCs here in the lab. We have three types of PC here - two Dells and one from SGI (a SGI 230). The previous version of the custom bootcd still works on all three platforms. The new version only works on the Dells. It fails on only the SGIs with:

Boot options which have been obtained in an architecture-specific fashion have to be copied to /arch.cmd in the rootfs. This implements that functionality for sparc32; the code is identical to sparc64 minus the openprom support for obtaining nfsroot options. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit fc8c0c09f9dd5139dd8d797eaf9fe33962b6cd2c tree

Hello all! I try mondo/mindi for some days now but it does not work and I don't know the reason. It is an intel Suse-8.0 Client and I use the Suse-8.0 packages from ftp.mondorescue.org. dhcp and tftp work fine. mondoarchive works, but I don't find any initrd.img for pxe/nfs. All initrd I have found ask for a CDROM and as they cannot find any they ask for a floppy when starting the pxe

Sparc64 has support for a bunch of architecture-specific options taken from the PROM. Convert them to kernel command line form and write the file /arch.cmd in the rootfs, which can be recovered by kinit and processed. The kinit support has already been committed. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit c6e5c5a77681f5bf6f9fea55d031115e9f58ada6 tree

Hello list, I am trying to use the console to setup my machine. During boot I am able see the syslinux boot prompt on the serial console *and* the monitor, but I can not use the console keyboard. I can only use the keyboard that is connected on the machine. After the kernel is loaded, the console keyboard starts working, but, this does not help me much, since I still need to use the keyboard

> Hello, > > I'm experiencing an issue where if I use vesamenu.c32 with PXELINUX 6.03 when network booting a virtual machine hosted on VMware ESXi 6.0, it hangs (the version message is printed and then nothing - the VM has to be powered off and back on again). > > This happens no matter if I choose the E1000 network interface or the VMXNET3 network interface when creating the

Hello, I'm experiencing an issue where if I use vesamenu.c32 with PXELINUX 6.03 when network booting a virtual machine hosted on VMware ESXi 6.0, it hangs (the version message is printed and then nothing - the VM has to be powered off and back on again). This happens no matter if I choose the E1000 network interface or the VMXNET3 network interface when creating the VM. The same problem

I've just tried 4.07 and that has the same results. I should note that I appear to be in error about things working OK with menu.c32 as opposed to vesamenu.c32 - I do indeed see the menu (which with vesamenu.c32 it does not get that far), but when I attempt to choose the Windows Deployment Services option, it hangs. Thanks, Dan Jackson (Lead ITServices Technician). -----Original

Hello! I am running Slackware Linux 10.2 with kernel bareacpi.i 2.4.31. My UPS is inform GUARD series line interactive UPS This is all the info I could extract from my UPS's documentation. I downloaded and installed the NUT Slcakware package nut-1.4.1-i486-1JKv. The hostname of my system is "marto", the domain name is "mydomain". Apart from the "root", I have

Hello, Thanks very much for your suggestions. I have double checked that all .c32 files are from the same version of syslinux. What I don't know - I only put those .c32 files I have in there on the basis of trial and error - is what .c32 files are actually needed for menu.c32 and/or vesamenu.c32. I thought perhaps there might be a .c32 file missing that I needed to put in there (though

Hi Xen developers, We are hitting a DomU Linux kernel panic and we''d like to find a solution for it. We are porting our virtual appliance to Amazon''s AWS. Our kernel is 2.6.27.57. We know it is old but we have to stay with it for now. The problem is when the kernel (64-bit) boots up in EC2 ( a large instance with 7.5 GB memory), the kernel crashes when hitting the BUG in

Hello! I am running Slackware Linux 10.2 with kernel bareacpi.i 2.4.31. My UPS is inform GUARD series line interactive UPS This is all the info I could extract from my UPS's documentation. I downloaded and installed the NUT Slcakware package nut-1.4.1-i486-1JKv. The hostname of my system is "marto", the domain name is "mydomain". Apart from the "root", I have one