Incompatibilidade com Dell series 300.
-
What error message do you see? If you have a clear picture of the error taken with a mobile phone, that will help us understand your problem.
-
Consegui atualizando a BIOS do computador e Atualizando o FOG para Ultima versão se acontecer algo mando de novo, Obrigado.
-
@kevinnew22 It works now? You can image with FOG?
-
@george1421 esta funcionando com FOG, todos os dispositivos que estão nessa pagina https://wiki.fogproject.org/wiki/index.php?title=WorkingDevices são dispositivos conhecidos e funciona com FOG?, pois aonde eu trabalho usamos Dell temos a serie 300 e Serie 7000 dos OptiPlex, OptiPlex 320, 330, 360, 380 testei duas dessas esta funcionado perfeito. Sabe se 320, 360 e 380 tem Suporte? Outra duvida Se PXE Inicializa é dificil nao dar certo de fazer a imagem? desde ja agradeço!
-
@kevinnew22 said in Incompatibilidade com Dell series 300.:
Sabe se 320, 360 e 380 tem Suporte?
The 300 series 320 (2006), 360 (2007), 380 (2008) are very old. Will they work with FOG? Yes.
Outra duvida Se PXE Inicializa é dificil nao dar certo de fazer a imagem?
These systems will pxe boot in bios mode so you need undionly.kpxe. If you can get to the iPXE menu you should be able to capture the image and deploy it to another computer. A lot depends on the operating system you are cloning and if you have the mother / golden image configured correctly before you capture the golden image. If its a windows OS then you need to make sure you sysprep the image before image capture to follow the Microsoft recommendations for image cloning.
-
Ok Entendido Obrigado
-
@george1421 estou com problemas no Dell Optiplex 320, estou usando a versao da BIOS 1.1.12 ultima ate o momento, ele da boot no PXE mas fica uma tela preta e fazendo upload eterno do bzImage. Olhei no WIKI FOG aonde coloco o parâmetro:
- list item args de kernel: acpi=force irqpoll - Use Dell Bios 1.1.12
Nao conseguir colocar Imagem em anexo, é isso mesmo? estou usando FOG 1.5.9.29 com undionly.kpxe
-
@kevinnew22 When it uploads bzImage forever, that usually means you have a networking problem. When it errors out you are in the 2nd stage of pxe booting. The first stage is when undionly.kpxe gets transferred over to the target computer and it boots. Then iPXE will download bzImage in the second stage.
Undionly.kpxe uses the network driver built into the network cards. It is possible the network card has a bug in it where undionly.kpxe does not work. You can try to send ipxe.kpxe instead of undionly.kpxe to the target computer see if ipxe.kpxe driver will boot better.
In regards to the
kernel argsof your wiki post you can find it here:
You can go in the FOG web interface FOG Configuration -> FOG Settings -> General Settings and in the KERNEL ARGS field enteracpi=offThen save the settings. Next pxe boot the target computer again see if The acpi=off command will tell the target computer when FOS Linux is running (bzImage) to not use acpi code to talk to the hardware.Your problem right now is with iPXE and not bzImage (where you use kernel args) so you can skip the kernel args part for now until bzImage starts up.
-
@george1421 Entendido, fiz testes aqui, so nao faz a parte dos registros manual e registro rápido do Host, testei deploy deu certo, e registrei manualmente o Host pelo painel de Hosts do FOG, so pelo client do FOG que nao estou conseguindo registrar o Host.
-
@kevinnew22 I don’t understand why registration gets stopped at loading bzImage and imaging works fine. Both tasks transfer bzImage before running FOS Linux on the target computer.
Is it just the Dell 320 model or all models do the same?
-
@george1421 Sim, bem esquisito mas esta funcionando, so registro que nao esta funcionando corretamente neste caso ate troquei para BZImage412.
