Intel Boot Agent problem

Asked by Steve Richardson

Boot-up problem is on a Toshiba Satellite Pro laptop, 5105-S501. The installed OS is Ubuntu, Rel 6.06. The base install went on with no problems. Subsequent to the install, the system downloaded and successfully installed some 250+ updates, again with no problems.

If I boot-up the laptop without being connected to the ethernet, there are no problems. The boot goes as planned and I ultimately reach the Ubuntu logon screen.

The problem comes in when I attempt to boot this machine while connected to the ethernet coax. Immediately after power-on, the Intel boot-agent activates. Next, the machine attempts to retrieve an IP via DHCP thru the network domain controller (windows network). This likewise goes satisfactorily.

That same boot agent then attempts a TFTP connection. I receive (3) successive PXE-E32 TFTP OPEN TIMEOUT errors over approx. a 5-8 min. time period. After that, the boot agent exits and the machine boots normally.

Following the boot, I then examine the network connection which shows that the ethernet connection is active, no IP was assigned via DHCP.

Any assistance in resolving this issue would be most appreciated.

Regards,

Steve

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Steve Richardson
Solved:
Last query:
Last reply:
Revision history for this message
Paolo Sammicheli (xdatap1) said :
#1

have you seen on laptop manual how to disable Intel Boot Agent. Afaik you don't need it, it's the operative system that set up properly the ethernet card. i wondering what it is trying to download.

Let me know

Revision history for this message
Best Steve Richardson (sdr4326) said :
#2

Disabled thru bios option - resolved problem. Thanks for your assistance.

Revision history for this message
williamts99 (williamts99) said :
#3

Steve, was being disabled the default bios setting?

Revision history for this message
Steve Richardson (sdr4326) said :
#4

I'm going to say it was not the default in that I had not taken any known action which would have enabled this feature. Once disabled, though, I had no further problems.

Revision history for this message
williamts99 (williamts99) said :
#5

Awesome, glad you got it taken care of, and thank you for your response.

Best Regards,
Williamts99