search for: szerencsit

Op 2013-07-12 om 14:06 schreef syslinux-owner at zytor.com: > Reason: Message body is too big: 1780404 bytes with a limit of 512 KB So previous not on the mailinglist. > Date: Fri, 12 Jul 2013 23:05:05 +0200 (CEST) > From: Michael Szerencsits <szerencsits.michael at gmx.at> > To: syslinux at zytor.com > Subject: efi64 boot fail during download from kernel and initrd via http > Message-ID: <trinity-9af93b8b-bab6-43b6-a448-5906da74f449-1373663105545 at 3capp-gmx-bs57> > > Hi, > > I tested the following...

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

> 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

On Tue, 25 Jun, at 09:43:02PM, Matt Fleming wrote: > Aha, yes, you're right. I'll take a look at fixing this. Michael, could you try out Syslinux 6.01-pre2 and see if things are now working for you? -- Matt Fleming, Intel Open Source Technology Center

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-p...

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.u...

> OK, staring at this packet dump, I see that your firmware isn't setting > a default value for the IP TTL field, but seeing as the UEFI spec > doesn't require this, that's a Syslinux bug. Interestingly, the firmware > on my test machine does fill out the TTL field with a value of 64. > > -- > Matt Fleming, Intel Open Source Technology Center > Some

> 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]

On Mon, 24 Jun, at 11:17:29AM, Michael Szerencsits wrote: > Hello, > > I tried to boot the new syslinux.efi (32bit) from the released > syslinux 6 via PXE. In a wireshark trace I can see that the > syslinux.efi was loaded successfully via TFTP. Then the client try to > load ldlinux.e32. I see the request and also the acknoledge...

On Tue, 25 Jun, at 01:51:52PM, Michael Szerencsits wrote: > Hi Matt, > > I think I've found the problem. Thanks for doing this analysis. > In /core/fs/pxe/tftp.c in function tftp_open: > First you do a core_udp_connect to port 69 (TFTP) at line 264. -> source port = x > After that you sent the filerequest at line 265 &...

On Tue, 25 Jun, at 03:14:00PM, Michael Szerencsits wrote: > Hi Matt, > > the server is listening on the port. I reviewed the RFC for TFTP and > it say that the server would response with an error if the source TID > is not correct: Aha, yes, you're right. I'll take a look at fixing this. -- Matt Fleming, Intel Open Sourc...

On Wed, 26 Jun, at 03:15:51PM, Michael Szerencsits wrote: > Sure, > > here it is OK, staring at this packet dump, I see that your firmware isn't setting a default value for the IP TTL field, but seeing as the UEFI spec doesn't require this, that's a Syslinux bug. Interestingly, the firmware on my test machine does fill out t...

On Thu, 27 Jun, at 02:08:34PM, Michael Szerencsits wrote: > > > Oh, also, if possible please test 6.01-pre4, just to make sure it's not > > the TCP packets that are now causing problems on your Sony machine. > > > > -- > > Matt Fleming, Intel Open Source Technology Center > > > > I tested the p...

> > I can't see any HTTP traffic in either of these dumps. Which machine did > you capture these logs on? Are you sure that the HTTP packets are > reaching your server? > > -- > Matt Fleming, Intel Open Source Technology Center > The boot-efi5.cap is from the booting lenovo system. I ran the trace again, but the file is 100MB

On Thu, 27 Jun, at 03:25:57PM, Michael Szerencsits wrote: > The boot-efi5.cap is from the booting lenovo system. I ran the trace again, but the file is 100MB Oh, I just remembered, the DNS resolving code isn't fully functional for EFI. If you replace hostnames with IP addresses, do you see any different behaviour? Of course, it's possi...

On Thu, 27 Jun, at 04:18:04PM, Michael Szerencsits wrote: > Change hostname to IP address, but same problem. > Copy the default config to uuid of the system, same problem > PROMPT 1 -> I see boot: but cannot do anything. If I press a key nothing happen OK, now that's just weird. You don't see any response whatsoever from tappi...

On Thu, 27 Jun, at 08:16:35PM, Michael Szerencsits wrote: > Am 27. Juni 2013 17:44:58 schrieb Matt Fleming <matt at console-pimps.org>: > >OK, now that's just weird. You don't see any response whatsoever from > >tapping at the keys? > > That's correct. Nothing happen. Bad :-/ > >If you set a TIMEOUT...

> Gesendet: Donnerstag, 27. Juni 2013 um 17:44 Uhr > OK, now that's just weird. You don't see any response whatsoever from > tapping at the keys? > > If you set a TIMEOUT, can you run a DEFAULT even though you cannot type? > That's one way to figure out whether the machine is dead at that point > or not. A useful DEFAULT might be reboot.c32, that way even if the

On Mon, 01 Jul, at 04:30:19PM, Michael Szerencsits wrote: > I tried to test the 6.01-pre5 version, but after loading from > ldlinux.e64 nothing happen in the trace. If I test the efi32 in > VMWare it comes up with a 'Firmware error' and close the VMWare. > > It seems that syslinux.efi from pre5 is broken > > I now w...

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]: ***