search for: efi5

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

> 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

...are now causing problems on your Sony machine. > > > > -- > > Matt Fleming, Intel Open Source Technology Center > > > > I tested the pre4 on both systems. Same problems as before. > > I attached the trace from both system boot-efi4.cap is from sony and boot-efi5.cap from lenovo > > I've seen that sony load the syslinux64.efi 2 times, while lenovo doesn't. 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, Inte...

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 possible you're not getting...