>>> You can troubleshoot the issue using a tftp client on one
>>> of your test boxes.
>> Nice idea! I booted the client into Knoppix, installed the tftp-hpa client
>> and tested.
>> I could successfully get every single file from the server in /srv/tftp/fai/
>> .
>> Worked without any issue and
> I had problems with my thinkpad in the past when booting UEFI. First I
> needed the newest syslinux binary, in those days I was still running
> stretch. Then, my thinkpad T480 needs a long time and shows several
> transmision error (currently I cannot say which exact messages) when
> doing UEFI
On 12/5/19 5:33 AM, Frank Morawietz wrote:
You can troubleshoot the issue using a tftp client on one
of your test boxes.
Nice idea! I booted the client into Knoppix, installed the tftp-hpa client
and tested.
I could successfully get every single file from the server in /srv/tftp/fai/ .
W
> To clarify, this client can successfully tftp the pxelinux.0 file over
> when configured for legacy BIOS mode?
Yes, exactly. This works.
> This looks suspiciously like a config problem on the server
> (firewall?).
The client is connected via direct cross link TP cable to the server and the
fi
On 12/4/19 1:40 AM, Frank Morawietz wrote:
Some additional information:
I picked the boot files from the local syslinux installation:
- /usr/lib/syslinux/modules/efi32/syslinux.c32 --> syslinux32.efi
- /usr/lib/syslinux/modules/efi64/syslinux.c32 --> syslinux64.efi
- /usr/lib/syslinux/modu
> On Wed, 4 Dec 2019 09:40:45 +, Frank Morawietz
> said:
> So it looks like the UEFI tftp connection refused error happened where
ldlinux should be transferred.
> Is there anything else I could examine to diagnose further?
I had problems with my thinkpad in the past when bo
> have you considered tcp wrappers ?
Thanks for your input.
In my opinion, installation in legacy mode shouldn't work either if something
like tcp wrappers or a firewall would hinder the installation in UEFI mode. IP
addresses and ports would be the same.
Some additional information:
I picked
On 12/3/19 2:50 AM, Frank Morawietz wrote:
Many thanks Steffen and Merlin for your configuration details!
I learned a lot already and I believe that we are on the right track.
I included your suggestions into my dhpcd.conf .
According to the log output below it seems to select the correct f
On Tue, 3 Dec 2019, Frank Morawietz wrote:
Many thanks Steffen and Merlin for your configuration details!
I learned a lot already and I believe that we are on the right track.
I included your suggestions into my dhpcd.conf .
According to the log output below it seems to select the correct fil
Many thanks Steffen and Merlin for your configuration details!
I learned a lot already and I believe that we are on the right track.
I included your suggestions into my dhpcd.conf .
According to the log output below it seems to select the correct file now.
But I still could not yet get it to wo
On 11/29/19 6:44 AM, Frank Morawietz wrote:
In my despair I even called the vendor support. They told me that I needed a
different pxelinux image for UEFI... Can this be true?
Short answer: yes. As Steffen Grunewald points our in his dhcpd.conf
snippet there is a different image file to us
On Fri, 2019-11-29 at 14:44:30 +, Frank Morawietz wrote:
> In a recent discussion I found...
>
> > You have to start the PC using UEFI boot via PXE (instead of legacy) -
> > than grub-install installs the efi-based grub when called by FAI.
>
> ...and that's exactly what I'm fighting with curr
In a recent discussion I found...
> You have to start the PC using UEFI boot via PXE (instead of legacy) -
> than grub-install installs the efi-based grub when called by FAI.
...and that's exactly what I'm fighting with currently.
Has anybody done this already? Booting PXE in UEFI mode in order t
13 matches
Mail list logo
