Lenovo ThinkPad T460p with Intel Ethernet Connection l219-LM doesn't work with Kernel TomElliot 4.6.4

[george1421]

What version of FOG are you using? (hint: look at the number about the cloud on the FOG management page).

If you are using FOG 1.2.0 stable then the max kernel you can use is FOG 4.1.2. If that kernel doesn’t support your hardware then you will need to upgrade your system to FOG 1.3.0-rc5. And even then your hardware may not be supported.

[mmingorance]

Hi,

The current version of FOG which I have is 1.2.0

[george1421]

@mmingorance Then the best kernels for that install are less than version 4.4. At version 4.4 and above the kernels internally changed requiring additional code from the 1.3.0 version of FOG.

[Wayne Workman]

@george1421 said in Lenovo ThinkPad T460p with Intel Ethernet Connection l219-LM doesn't work with Kernel TomElliot 4.6.4:

@mmingorance Then the best kernels for that install are less than version 4.4. At version 4.4 and above the kernels internally changed requiring additional code from the 1.3.0 version of FOG.

#wiki worthy

[mmingorance]

Ok, I have install the kernel version 4.3.2
Anyways, I would like create a new machine with FOG 1.3.0
Do you know from where can I download this new version? Because I was searching it but I couldn’t find it.

Thank you in advance.

[george1421]

@mmingorance No problem 1.3.0-rc7 is conveniently hidden under the guise of a trunk upgrade: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

If you follow the instructions for upgrade to trunk you will be on 1.3.0-rc7. Install 1.3.0 directly and not upgrade from 1.2.0 if you are creating a new FOG server from the beginning. Also use a current host OS to be sure you don’t have issues with installing FOG 1.3.0 (centos7, ubuntu 14.04, 16.04 [with a special way of launching the fog installer])

[mmingorance]

Hi all,

I have news regarding this topic.

I installed the new version of FOG (1.3.0) but now I received the next error code:
No configuration methods succeeded (http://ipxe.org/040ee119)

I already checked the webpage to solve the issue and I could see that the reason might be a problem in my DHCP Server, but in that case, this issue should affect to all my laptops (not only this model).

Any advise?

Thanks in advance.

[Wayne Workman]

@mmingorance said in Lenovo ThinkPad T460p with Intel Ethernet Connection l219-LM doesn't work with Kernel TomElliot 4.6.4:

I could see that the reason might be a problem in my DHCP Server, but in that case, this issue should affect to all my laptops (not only this model).

Not really true, the laptop has different hardware, which probably requires a different boot ROM. Available boot ROMs can be listed by running ls -laht /tftpboot and you would need to create a DHCP reservation for a test laptop, and setting the reservation’s DHCP option 067 to each file until you found one that works. UEFI type firmware and devices require boot ROMs that end with .efi all the other files available are for Legacy BIOS.

After solving this, you may also be interested in:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

[mmingorance]

Hello all,

I have another question. Is any way to merge all those files in only one? Since we are using a special firewall as DHCP Server, I can’t create any code like in the following link:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

That’s is a really good solution, but it’s not the best one for my environment.

As I asked before, Is any way to merge the files in one?

Thanks in advance.

[Wayne Workman]

@mmingorance I don’t think it’s possible. BIOS and EFI are two fundamentally different things. The reason there are so many different files is some has one kind of driver, another has another kind of driver. One file may not work on some computers but another will.

Is your firewall doing DHCP? What sort of firewall? Can you move DHCP to a Windows or Linux box?

[mmingorance]

@Wayne-Workman I already thought in create a virtual server to work as DHCP in a specific scope and connect the FOG server and the clients in this special scope.

I think is the only possibility inside my environment.