This sounds like a hardware issue.

I’m assuming you’ve enabled PXE Boot from the Network in the BIOS?

If the USB NIC is disconnected, does the system (in bios) allow you to choose Network?

OK got it. Will give it a try today or tomorrow and see what happens. Need to do some scanning on some systems for this damn bug. Thanks for the help. I’ll be back…

Thanks Tom, You have been a big help. I actually understand more about the boot process now. I added the missing firmware file to lib/firmware/bnx2/… in the init.gz but it still didn’t work.

It does not appear that these desktops have UEFI capable BIOS, I searched pretty thoroughly through the BIOS options and came up empty. No worries though, I’m having them swapped for a couple of identical units. I was able to image two of the four successfully so I’m just going to chalk this up as bad luck for now.

Ooh. Sorry. I just boxed up my test T7600 once I got everything working. I can test it on a T7500, though. You won’t hear back for a bit, though. I’m taking the next couple of days off for Christmas.

Chris and Ted,

Can you please try my latest kernel?

I’ve added a whole lot of drivers dealing with the different types of Drive Controllers and anything, I found seeming relevant, to deal with SSD’s and what have you. I don’t know if it will help/work, but theoretically there’s enough information in the kernel from the 3.8.8 to now that things should work.

Thank you,

[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]

Hi there

I only made this Kernel because the ones that I could download through fog just wouldn’t work with this Atheros LAN card. I have been using it as a main Kernel, but ideally one needs to be made that has all LAN adapters on, as some earlier machines still fail to work.

Just for information,
I have updated Lenovo Thinkcentre 72 to the latest available BIOS : F1KT58AUS (dated 2013-11-28) and the problem remains :
Can’t boot from HD if PXE has been selected first.
Nicolas

[quote=“chad-bisd, post: 14605, member: 18”]You may have to configure multicast groups/preferences in the switch. We use DLINK DGS-3120 POE series switches, and they had some advanced settings for making Multicast work for some other applications.

A few things to note about multicast. They only go as fast as the slowest client, and I believe use a lot more memory on the server as the image is decompressed on the server before being sent out to all the clients.[/quote]

all our machines are brand new Dell latitude 3330’s with Identical spec’s and all imaged perfectly with unicast. I am not sure our switches truly support multicast. Despite Netgear claiming they do.

Which kernel did you use?

3.8.8? 3.12.2?

This is fixed, built my own kernel using kitchensink and adding Atheros NIC to it. I’m able to add the host manually and flash.

Excellent. Copying the file from pen drive to the \kernel folder proved to be a problem, but managed to resolve that. It took a while to load but full inventory of computer completed successfully and imaging the laptop now.

Really, really appreciate your help, don’t know how to thank you.

Brilliant.
RRM

I managed to deploy!
but in debug mode.

I create an image in debug mode, then deploy in debug mode.

the default does not work:
error during deployment:
[URL=http://www.dump-it.fr/screenshot2013-11-15-12-39-25png/a57aa2ef039b07200e81e352693d052a.png.html][IMG]http://www.dump-it.fr/upload/images/miniatures/a57aa2ef039b07200e81e352693d052a.png[/IMG][/URL]

I also noticed an error on Ubuntu 13.10:
I jpgraph does not work properly. that is to say, no visible graphic.

big thank!

I set up one of the desktops alone with monitor, keyboard, and mouse all hooked up. Updated the kernel, which I think is why the “[I]checking in”[/I] error occurred. Fog worked fine.

However, as a test I pulled out the VGA cable and plugged it back in during an image deployment, and [I]“irq#16: will be disabled” [/I](or something along those lines) message popped up in the FOG screen. So, even though I don’t understand how or why, it appears that this error is, in my case at least, related to monitor connections or the video cards. It’s possible that if the output changes in some way, FOG isn’t sure how to handle it.

For assurance’s sake, we will just have our desktops fully hooked up from now on. Strange FOG would barf over something so trivial, but who knows.

Thanks for your help Tom!

Glad you got it sorted, Open another thread and lets get started on your deployment issues 🙂

I don’t think the kernel is use issue here as it’s able to communicate with your FOG Server and get to the point to try to mount your NFS Share, which comes off the server.

ON your server, can you let us know what OS you’re using? It’ll help us with command troubleshooting.

FOR UBUNTU TRY:
[CODE]sudo service portmap restart
sudo service nfs-kernel-server restart[/code]

FOR CENTOS/REDHAT/FEDORA TRY:
[code]service rpcbind restart
service nfs restart[/code]

try a new kernel.

Maybe mine:

[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]

Found a solution. Needed to use FOG kernel 2.6.24 KS. Hope this helps someone else.

Lo siento si mi español es horrible, no tengo capacidad de hablar en este idioma. Así que estoy usando translate.google.com

Si estoy entendiendo el problema correctamente, usted está necesitando imagen en una unidad “en blanco”, pero FOG no es lo que le permite.

La forma de hacerlo es, inicie el cliente con la nueva unidad en modo de depuración.

Cuando usted consigue el tipo shell:
[CODE]
fdisk -l
[/CODE]
Encontrar cuál es la unidad, normalmente /dev/sda

a continuación, para obtener datos en él, ejecute el siguiente comando:
[CODE]
fdisk /dev/sda
[/CODE]

Esto le llevará a la pantalla de espera para la clave es ser introducido.

Escriba esta serie:

[CODE]
p
1
n
t
7
w
[/CODE]

Esto debe escribir la tabla de particiones.

Entonces siempre me quedo:
[CODE]
mkfs.ntfs /dev/sda1
[/CODE]

Entonces romperá si. Esto asegura que el sistema de archivos está en existencia por FOG para trabajar fuera.

Espero que esto ayude.