similar to: efi64 boot fail during download from kernel and initrd via http

Op 2013-07-15 om 12:40 schreef Michael Szerencsits: > > If it is http://rosa.stappers.nl/ff/boot-efi-s100.cap > > then is at packet 2242 the client ( .243) started to send > > "TCP Dup ACK" of packet 2241 > > > > > > Thing I what to mention is that there packets of sizes bigger as 9000bytes. > } So large as a jumbo frame. > > > > I

Op 2013-07-13 om 19:58 schreef Michael Szerencsits: > Hi, > > I tested the following config: > > DEFAULT AutoInstall > PROMPT 0 > LABEL AutoInstall > KERNEL http://server/vmlinuz64 > APPEND initrd=http://server/initrd64.img > root=live:http://server/LiveOS/squashfs.img quiet lang=en > keymap=de-latin1 systemd.unit=rescue.target > system.unit=rescue.target

Hi, I tested the following config: DEFAULT AutoInstall PROMPT 0 LABEL AutoInstall KERNEL http://server/vmlinuz64 APPEND initrd=http://server/initrd64.img root=live:http://server/LiveOS/squashfs.img quiet lang=en keymap=de-latin1 systemd.unit=rescue.target system.unit=rescue.target system.unit=rescue.target I use VMWare Player 5.02 build 1031769 on Win2k8 R2 64bit. I found that the last

The following is a pxelinux problem, specifically to do with including config files with the menu include directive and the ifcpu64.c32 com module. I have a working ifcpu64.c32 setup that jumps to the label rescue64 in the case of a 64-bit CPU. The label "rescue64" defines a 64-bit kernel and a 64-bit initrd.img. The setup jumps to a label named "rescue32" in the case of a

Am 01. Juli 2013 18:13:25 schrieb Matt Fleming <matt at console-pimps.org>: > > Does reverting to -pre4 make things work again? > > -- > Matt Fleming, Intel Open Source Technology Center Yes, with pre4 it work. But as I wrote the problem during searching for the configfile and hung from the program already exist. Gesendet mit AquaMail f?r Android http://www.aqua-mail.com

On Sat, 13 Jul, at 07:58:21PM, Michael Szerencsits wrote: > I use VMWare Player 5.02 build 1031769 on Win2k8 R2 64bit. > I found that the last working version is 6.02-pre1 but beginning > with pre2 and also latest version 6.02-pre5 it fail to boot. Are you sure that 6.02-pre1 worked? There was only one commit between 6.02-pre1 and 6.02-pre2 and it shouldn't have affected anything at

I've been using linux:TC from a USBstik in order to not break the M$ capability, as previously always happened. Since TC runs in RAM, it has many extra problems; like reinstalling all the apps and your private settings at each boot. The sample isolinux.cfg which I've been emailed by the oficianado is very unfamiliar and worrying. Where is the official syntax ? -- Without knowing if/how

Hello, I tried to make my own binary with 'make efi64 install' but it fail with make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop. make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi' make[2]: *** [install] Error 2 make[2]: Leaving directory `/root/syslinux-6.02-pre3/efi64' make[1]: ***

Am 19. Juli 2013, 18:05, schrieb Matt Fleming> > : > > Out of curiousity, are you able to build 6.02-pre2 from git? > > -- > Matt Fleming, Intel Open Source Technology Center I've never done this before, but would try it if you tell me how. Regards Michael

I'm a beginner to libvirt and creating VMs, for that matter. I have a set of specifications for VMs I need to create and log into, but I have to create them on an Ubuntu box that I only have ssh access to. I won't have desktop GUI access, although I do have dynamic port forwarding, so I can access a browser GUI from my desktop. Reading through the libvirt info, I see numerous mentions

Thanks for replying. Good info so far. After I start the VM, I’m going to need to see the boot console, and I’ll need to ssh into it with a hostname or IP. What are some required steps for those needs? This VM is going to need to access a few associated networks. I can see that the “—networks” option is part of the interface for configuring this. What are some things I’ll have to do for

> Actually, can you grab the version I built from, > > ftp://syslinux.org/pub/syslinux/tests/syslinux-6.02-pre2.tar.gz > > And see whether things work for you? I'm just trying to rule out any > kind of distribution error on the Syslinux build machine. > > -- > Matt Fleming, Intel Open Source Technology Center > _______________________________________________

> Sorry about that. I've fixed the Makefiles in 6.02-pre4. > > > Would this also create memdisk for efi64 boot? > > No, memdisk is inherently tied to bios and isn't build for efi32/efi64. > > -- > Matt Fleming, Intel Open Source Technology Center > Hi Matt, thanks for your response. Would there be memdisk or a similar program/methode to emulate a cdrom

I was working on windows xp for a while and now i am back to linux ( not sure which kind but I can find out if that helps ) and i just have two questions that are really environment R questions rather than R code questions. 1) i use emacs ( or xemacs if need be ) and i vaguely being able to cut a line or a region in an emacs window and then paste it at my R prompt so that it ran. Could I be

Hi folks My ultimate goal is to be able to add an initramfs to the end my syslinux.cfg resulting in an additional initramfs being loaded when the system boots. So I need to work out how to get initrd+= to work. I?ve been trying for days now everything I possibly can to get initrd+= to work but nothing I do works. I've also been trying to get initrdfile= to work but no success with that

This is offtopic, but related to what you’ve told me so far. I’m having some trouble getting the VNC connection to work. Technically, the “connection” is working fine, but the Windows TightVNC Viewer comes up with an error dialog saying this: Xsession: unable to start X session --- no "/home/.../.xsession" file, no "/home/.../.Xsession" file, no session managers, no window

> If the Windows OS is running and a program is checking for an optical > disc drive, then you really need one of: > - A physical optical disc drive with the expected disc > - A virtual optical disc drive with the expected disc > > Are you using either of these right now? If you are using a physical > OD, does it have a Syslinux EFI on it? If you are [thinking about]

I’m confused. You’re asking if I’m able to connect with VNC in response to my comment that I’m unable to connect with VNC? What I see when I open the viewer on the port is a window titled “<username> X desktop”, with a grey background, an “X” cursor, and an error dialog (with an “okay” prompt) saying what I described before. Ctrl-Alt-F1 and similar keys do nothing. From: Jeff Tchang

$ git checkout RELEASE-4.2.2 $ git clean -ffdx [do a build, install, reboot] $ xl create a0 $ xl cd-eject a0 hdc [However, the guest OS still sees the CD inserted] $ xl block-list a0 Segmentation fault $ xl cd-insert a0 hdc file:/images/xs-tools-6.0.0.iso Segmentation fault The problem seems to be that xl cd-eject is writing corrupt values to xenstore. Note that vbd/1/5632 is still there

On Thu, 11 Jul, at 01:55:12PM, Michael Szerencsits wrote: > Hello, > > I tried to make my own binary with 'make efi64 install' but it fail with > > make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop. > make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi' > make[2]: ***