大网数据广告活动
服务器运维问答

trying to netboot Linux using PXELinux 6.03 in a EUFI 64 board, tftp too slow

· 52CE 我爱测

I am trying to set up a kids-school lab, using x5-Z8350 based mini PCs: https://ark.intel.com/products/93361/Intel-Atom-x5-Z8350-Processor-2M-Cache-up-to-1_92-GHz Mine seems to have an AMI 64 UEFI "bios". I have managed to offer …

问题原文

原帖链接 · Juanito · CC BY-SA 3.0

I am trying to set up a kids-school lab, using x5-Z8350 based mini PCs:

https://ark.intel.com/products/93361/Intel-Atom-x5-Z8350-Processor-2M-Cache-up-to-1_92-GHz

Mine seems to have an AMI 64 UEFI "bios". I have managed to offer IP from Ubuntu Server (syslinux 6.03, no need for 6.04 yet) , tftp syslinux.efi, then ldlinux.e64 later, then vmlinuz image and initrm that takes ages. And then freezes...

I came across:

Syslinux: How to correctly configure for UEFI PXE boot?

My client declaration also is

PXEClient:Arch:00007:UNDI:003016.

I have 2 problems as of today:

1) InitRM (about 40Mb) is taking like 20 minutes to load, is this due to aforementioned tftp bugs?. I am using atftpd. How can I come around this? vmlinuz and initrm from nfs? other tftp server?

2) Freezing suposedly when loading or executing the kernel. This maybe due to trying to use an i386 image on top of this board...?

Any help or hint very much welcome.

Cheers, Juan.

已采纳解答

原帖链接 · Pat · CC BY-SA 3.0

1) Definitely the 20 min for a 40 Meg TFTP transfer is the result of Syslinux 6.03 UEFI TFTP bug/s. The only way you have to overcome this is either upgrade Syslinux (even when today 6.04 final does not exist) or transfer by HTTP instead.

2) Arch:00007 implies you have an UEFI 64 client, you might have several issues loading UEFI 32 and/or 32 Bit OSs on that architecture.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-12-01)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。