Does it eventually work? Or does it halt? During the start-up process it’s normal to see some of these errors. Do you get to enter “full registration”?

I used a different kernel to address a hardware capability issue (Kernel -2.6.37). It PXE boots but when I press enter for full registration nothing happens. What am I overlooking?

Let me clarify, the client PXE boots and I am offered a menu, I go down and select “Full Registration” and it doesn’t advance to the next screen it just stays on that screen.

When I put back the bzImage that I previously had (that worked for my other workstations) it functions correctly and gets past the “Full Registration”. The only reason I replaced the bzImage is so I could image an Optiplex 790. I read somewhere on this forum that they were successful with Kernel 2.6.37. The issue is I get the snowy screen due to the Radeon video card.

Thanks.

Thanks for the response.

Yes, I did reformat and rebuild the image. So I guess the the next thing to try is “single partition”. All of my other computers had no issues with the multipartition non-resizeable. I will see what happens.

Thanks for the response.

No I don’t use Dell OEM Windows.

I deleted the partitions on the drive. For the utility partition I just used diskpart and had to use the ‘override’ command to get rid of the Dell Utility partition. I re-uploaded the image again and it still didn’t work. I used multi-part non resizeable. I only started with that one only because it sees to be what everyone uses on the forums. Technically though, it only has 1 partition. It’s the craziest thing… the next thing to try would be single partition in FOG. I haven’t had any time today to try it though and don’t know if it will matter.

So basically, no kernel or panic errors. Using recommended kernel from the problematic devices wiki. It uploads the image fine. When I go to deploy the image it will get to 1-10% and just hang and not go anywhere.

[LIST]
[][FONT=sans-serif][COLOR=#000000]Kernel 2.6.27 RC9 [/COLOR][/FONT]
[][FONT=sans-serif][COLOR=#000000]Fog .32[/COLOR][/FONT]
[*][FONT=sans-serif][COLOR=#000000]Multiple Partition Non-Resizable Single Disk[/COLOR][/FONT]
[/LIST]
[FONT=sans-serif][COLOR=#000000]Upload is perfect, it races through SDA and then starts with SDA2 (takes longer). There are no hangs or freeze. Now when it comes to download it will stop at 10% or so. It just halts. I also notice it starts with SDA2 and not SDA (why?). I assume it is skipping one of the partitions. I read that the Dell Utility can cause problems. Why? Because it mixed file systems? I believe the dell utility is FAT16. Does it fail because it’s mixed file systems on the hard drive? Any thoughts or opinions? What is the best method to remove it?[/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000]Thanks[/COLOR][/FONT]

It will load the kernel using the same machine if I drop a different version in /tftpboot/fog/kernel/. Very odd.

Yes, this is the only step I did and it worked correctly.
Copy (replace) the bzImage to /tftpboot/fog/kernel/

I understand your confusion though. I tried Kernel-2.6.33.3.PS (rename bzImage) for my Optiplex 740 (after reading it would work) and nothing happens. When I get to the FOG Menu and I select Full Registration, nothing happens. It just re-presents the MENU. I try another kernel and it at least gets to host name prompt. Very odd.

astrouga, can you share your kernels? The links you posted no longer have your kernels.

I am a bit confused on the difference between: kitchensink.config/core.config.

First, what are they? How do they differ from the BzImage kernel. Second, it seems that kitchensink would have the whole ‘kit and kaboodle’ so why mess with core.config?

How do I switch between the two?

Thanks.

I used Erics kernel for E6520, surprised it doesn’t work for E6510.
You using core.config or kitchensink?