similar to: 6.01-pre 4 no timeout when using serial

Trying syslinux-6.00 and get the following error using ramdisk isotest or memtest DEFAULT ramdisk LABEL ramdisk linux /casper/vmlinuz append boot=casper toram initrd=/casper/initrd.img nomodeset LABEL isotest linux /casper/vmlinuz append boot=casper integrity-check initrd=/casper/initrd.img nomodeset LABEL memtest kernel /install/memtest append - LABEL disk localboot 0x80 append -

On Sun, Jun 30, 2013 at 7:42 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, Jun 30, 2013 at 1:12 AM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >> Could it be that syslinux is waiting for ever if you use serial mode? >> >> SERIAL 0 115200 > >> TIMEOUT 300 > > Gert, Romain: Have you tried lowering the serial rate or timeout? ie: >

On Thu, Jun 27, 2013 at 2:50 PM, Gert Cuykens <gert.cuykens at gmail.com> wrote: > Trying syslinux-6.00 and get the following error using ramdisk isotest > or memtest > Loading /casper/vmlinuz... ok > Loading /casper/initrd.img...ok > No linux boot function registered for firmware > Booting kernel failed: Bad file number Try the current -pre (6.01-pre4) -- -Gene

On Fri, Jun 28, 2013 at 2:31 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Jun 27, 2013 at 6:03 PM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >> Using syslinux 6.01-pre4 and ubuntu 13.10 kernel 32bit >> >> LABEL halt >> com32 poweroff.c32 >> >> Does not power off my qemu, it stays open in halt mode. >> qemu -cdrom

Gert Cuykens wrote: > On Fri, Jun 28, 2013 at 2:41 AM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >> On Fri, Jun 28, 2013 at 2:31 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On Thu, Jun 27, 2013 at 6:03 PM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >>>> Using syslinux 6.01-pre4 and ubuntu 13.10 kernel 32bit >>>>

Using syslinux 6.01-pre4 and ubuntu 13.10 kernel 32bit LABEL halt com32 poweroff.c32 Does not power off my qemu, it stays open in halt mode. qemu -cdrom ubuntu.iso -boot d -net nic,model=virtio -m 1024 -curses If I boot into ubuntu first and do sudo halt -p it powers off and closes qemu. Can poweroff.c32 do the same as sudo halt -p in ubuntu?

Gert Cuykens wrote: > On Mon, Jul 1, 2013 at 10:50 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: >> Gert Cuykens wrote: >>> >>> On Sun, Jun 30, 2013 at 6:12 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: >>>> >>>> Which qemu version with which bios are you trying? >>> >>> >>> inside a vmware player 5.0.2

Gert Cuykens wrote: > On Sun, Jun 30, 2013 at 6:12 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: >> Which qemu version with which bios are you trying? > > inside a vmware player 5.0.2 build-1031769 running ubuntu 13.10 > SeaBIOS (version 1.7.2-20130528_111335-allspice) > QEMU emulator version 1.5.0 QEMU starting from v1.3.0-408-g9ee59f3 no longer supports the Bochs

Le 30/06/2013 13:47, Gene Cumm a ?crit : > On Sun, Jun 30, 2013 at 7:42 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Sun, Jun 30, 2013 at 1:12 AM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >>> Could it be that syslinux is waiting for ever if you use serial mode? >>> >>> SERIAL 0 115200 >> >>> TIMEOUT 300 >> >>

On Sun, Jun 30, 2013 at 1:12 AM, Gert Cuykens <gert.cuykens at gmail.com> wrote: > Could it be that syslinux is waiting for ever if you use serial mode? > > SERIAL 0 115200 > TIMEOUT 300 Gert, Romain: Have you tried lowering the serial rate or timeout? ie: SERIAL 0 9600 TIMEOUT 30 Romain: is this observed on a physical or virtual machine? -- -Gene

Op 2013-07-03 om 23:33 schreef Gert Cuykens: > On Wed, Jul 3, 2013 at 9:47 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: > > Gert Cuykens wrote: > >> > >> Ok thanks, but I was wondering what the difference is between halt -p ? > > > > > > poweroff.c32 uses APM. Linux can also use ACPI. > > > > Is ACPI possible to implement or way

On Tue, Dec 19, 2017 at 3:47 PM, Jeff Sadowski via Syslinux <syslinux at zytor.com> wrote: > I have an odd issue. > I have one machine that does not display to the monitor when it goes > to a linux boot loader. > It has the issue with grub and pxelinux. > > I see the bios but between bios and graphics driver I see a blank screen. > > Any recommendations on how to fix

Hallo, syslinux, I'm working with an USB stick and an *.iso image. On an USB stick I can use "casper-rw" and "home-rw" for persistent directories/files. Under PXE I haven't yet found a similar option. Is that a syslinux-/pxelinux problem, or is that a "casper" problem? Example: USB stick, part of "isolinux.cfg": label desinfect menu label

On 09/05/2013 01:55 AM, Gene Cumm wrote: > On Wed, Sep 4, 2013 at 2:34 PM, Piotr Karbowski > <piotr.karbowski at gmail.com> wrote: > >> With syslinux (extlinux) it will jump to last INCLUDE'ed menu always, with >> 5.01 it will display list of elements, then allow me to choose which one I >> want to enter. >> >> Even if the include part contain a

Have you tried a different monitor? Has that monitor ever shown you a boot loader menu? It might be that it just doesn't support the low-level resolutions Grub is trying to use. On Wed, Dec 20, 2017 at 7:09 PM, Jeff Sadowski via Syslinux < syslinux at zytor.com> wrote: > I want to see things, I'm not sure how quiet would work. > Maybe next time I get the box I can re-put

I have an odd issue. I have one machine that does not display to the monitor when it goes to a linux boot loader. It has the issue with grub and pxelinux. I see the bios but between bios and graphics driver I see a blank screen. Any recommendations on how to fix it? More to it. It is a newer nvidia card, That I need to drive a 4K monitor at 60Hz . If I replace it with an old nvidia card I can

my postfix setup http://code.google.com/p/appwsgi/wiki/smtp my dovecot setup http://code.google.com/p/appwsgi/wiki/imap root at localhost:~# /etc/postfix/test/root 220 localhost.localdomain ESMTP Postfix (Ubuntu) 250-localhost.localdomain 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250-STARTTLS 250-AUTH PLAIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN 235 2.7.0 Authentication successful

I am back at this, again, trying to get my linux PXE server back up and running. I have the x86_pc (pxelinux.0) boots fine. I can boot Ubuntu Gnome 16.04 to teh setup screen. Every time I attempt to boot the same nfs from a computer which can boot via efi (x64_efi), I get a failed transfer. This is with 6.04_pre I grabbed well over a year ago. What happens is I get a TFT transport error. This is

I want to see things, I'm not sure how quiet would work. Maybe next time I get the box I can re-put in the older working card and try to do a firmware upgrade. This does not seem distro specific. All versions of grub and syslinux do not work in the default configs. I will try using menu.c32 vs vesamenu.c32 as well. To see if it won't display. On Wed, Dec 20, 2017 at 4:52 AM, Gene Cumm

On Sun, Jun 30, 2013 at 6:12 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: > Gert Cuykens wrote: >> >> On Fri, Jun 28, 2013 at 2:41 AM, Gert Cuykens <gert.cuykens at gmail.com> >> wrote: >>> >>> On Fri, Jun 28, 2013 at 2:31 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>>> >>>> On Thu, Jun 27, 2013 at 6:03 PM,