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 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 >Hi Matt, yes, now the TFTP download work. I'm able to successfully boot into a linux testsystem via VMWare player, which provide a 32bit EFI system. When I try to PXE boot with a Laptop (64bit EFI) the ldlinux.e64 and also the config file gets loaded, but than it hang for arroud 2-3 minutes. After that error message 'TFTP unknown opcode 513' and the system reboot. Regards Michael
On Wed, 26 Jun, at 02:11:36PM, Michael Szerencsits wrote:> Hi Matt, > > yes, now the TFTP download work. > > I'm able to successfully boot into a linux testsystem via VMWare > player, which provide a 32bit EFI system.Great, thanks for testing.> When I try to PXE boot with a Laptop (64bit EFI) the ldlinux.e64 and > also the config file gets loaded, but than it hang for arroud 2-3 > minutes. After that error message 'TFTP unknown opcode 513' and the > system reboot.Are you able to capture a packet dump of this transaction? -- Matt Fleming, Intel Open Source Technology Center
On Wed, 26 Jun, at 03:15:51PM, Michael Szerencsits wrote:> Sure, > > here it isOK, 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
> 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 additional news. The system where the EFI boot fail is a Sony SVC1512. I now tested it with an IBM T430 and there it ... let me say 'boot'. I got the screen with Getting cached packets My IP is 192.168.1.187 but than nothing happen. I run a tcpdump and see that in the background my vmlinuz, initrd and also sqashfs.img was loaded via HTTP. This image run automatically a script which perform a curl against my HTTP server. I see the incomming curl request in my HTTP accesslog, so all run fine, but on my laptop screen only the two rows above are shown. When booting in BIOS mode, the screen change and I see the boot of the linux and also the curl command and reply from the HTTP server. This reply tells me if the system was successfully registered and is important to see Regards Michael
On Wed, 26 Jun, at 03:39:52PM, Matt Fleming wrote:> 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 the TTL field with a value of 64.Michael, I've just released 6.01-pre3 which should hopefully get your Sony machine working. Let me know how you get on. -- Matt Fleming, Intel Open Source Technology Center