[quote=“M Bodelson, post: 8961, member: 1787”]Hello Eric
I used the kernel you posted on scatteredspace and I was able to register my Dell Optiplex 990s with the AMD Radeon HD6540 Video Card. At this point when I try to create the image it creates 3 very small image files. The status bars that display when building the image just quickly flash by. Are there any parameters I need to set in fog or anything else I should do when I upload an image from the Optiplex 990? Thanks.[/quote]

I’m not sure what the three files are. I didn’t have to set any parameters that I can remember. However, I didn’t set much of the Fog back end up so I could be missing something. When I created my image over the summer I did the following:

(I’m using Fog .32)

• Went to image managment and created a default x86 Windows 7 Master Image
• Image type was set to Multiple Partition Image - Single Disk (Not Re sizable)

In Windows:

• I put the PC in audit mode after a clean install
• Made my changes the PC
• Used Windows CMD PNPUtil to add all the drivers for every Optiplex I have directly into the image
• Sysprep’ed the PC using the following CMD : Sysprep.exe /generalize /oobe /shutdown /Unattend:unattend-X86.xml

Must create an unattend file using MS tools and then navigate to C:\Windows\system32\sysprep

After Sysprep I loaded Gparted: [url]http://gparted.sourceforge.net/[/url]

• After the PC shuts down I reboot it and load Gparted immediately.
• I shrink the partition to its smallest possible size to so that the image fits on all available hard drive sizes
• Once the partition is shrunk I reboot and let scandisk complete. After scandisk completes the PC reboots
• Once PXE loads I register the PC and have it upload its Image to Fog

When the PC reboots I have a script that runs that loads any drivers that PNPutil.exe could not handle and use diskpart.exe extendvol to expand the hard drive back to its full size. Ive also found in my experince that have the script delay the Fog service helps with it automatically joining the domain.

[quote=“Fabian Wostal, post: 4210, member: 189”]Good Morning Eric,

Could you please provide me some information what parameters did you choice by creating the Kernel for OptiPlex PCs?
The problem was exactly the same like it’s showing on your print screen. I create yesterday the Kernel with the version Linux-3.4 and choice all default values not to waste to much time us I work yesterday about 9.5 hours. Could you please provide me the information that you choice to make the PXE boot starting properly with ATI graphic cards installed in the PC?

Thank you in advance.
Fabian[/quote]

When I created the kernel I just followed the instructions from here: [url]http://fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel[/url]

Once I was able to edit the kernel I simply added all the NICs and Video drivers available. I also know that there is a custom parameter that you can set to remove the snow screen issue in Fog but I cannot find the command or the forum post that mentioned it at this time.

I ran into this problem myself. I work for a school district and we have nothing but Optiplex systems. Basically this problem occurs on any devices that use an ATI/AMD graphics card. Like you said above, using the on board graphics (Intel) work just fine. Below is a post I made on here awhile ago which has resolved a lot of these snow screen issues for people.Basically I created my own kernel to see if it would fix these video issues and it has. Ive been using it to deploy over 1000s or optiplex PCs in my district and also resolves problems with PCs using VGA or DVI ports.

[QUOTE]I recently made my own Kernel as a proof of concept. Its based of the Linux 3.3 Kernel and it resolved a lot of problems for me. Its attached in my post here. Be sure to backup any of your existing Kernels in /tftpboot/fog/kernel/

Let me know if it works for you.

[url]http://scatteredspace.com/Fog/bzImage.zip[/url][/QUOTE]

I posted my custom 3.3 Kernel in another thread. It resolved the snowy screen issue that I had on some of my Dells. Maybe it will help you too? Below is what I posted in another thread:

I recently made my own Kernel as a proof of concept. Its based of the Linux 3.3 Kernel and it resolved a lot of problems for me. Its attached in my post here. Be sure to backup any of your existing Kernels in /tftpboot/fog/kernel/

Let me know if it works for you.

[url]http://scatteredspace.com/Fog/bzImage.zip[/url]

[quote=“sid, post: 2694, member: 558”]something that I just did.
I logged into ubunto, my fog server, and tried to read the permission on the tftpboot folder.
it shows that Fog is the owner and doesn’t let me do anything[/quote]

My guess is that you would need to open up Terminal on your Ubuntu hosting fog. From there you would need to use sudo to copy the bzImage over so that you have elevated privages. Example:

sudo cp /media/C810-83C8/bzImage /tftpboot/fog/kernel/bzImage

/media/C810-83C8/bzImage <-- Being my flash drive and /tftpboot/fog/kernel/bzImage <-- Being the location where kernel needs to go.

[quote=“The Dealman, post: 2684, member: 53”]What hardware models does this kernel support?[/quote]

I work for a school district that primarily uses Dell PCs these days. I recently ran into a few video problems which were annoying.

The first problem occurred when imaging Dell Optiplex 745’s. 745’s have an on board VGA port and a DVI riser card. When imaging these machines I would get a “Resolution out of range” message on the monitors.

The second problem occurred on any machine using an ATI/AMD video card. I would typically get what people call on here the “snow/ scrambled” screen. While the PCs still imaged with both of these problems, I could not tell how the progress of the image was going by looking directly at the PC.

By creating my custom Kernel I told it to include all ATI, Intel, and Misc graphics drivers. It appears to resolve both of my major problems, however, I am not sure if it is because I included these drivers or because the linux kernel is newer.

I have tested my Kernel on the following models of PCs:
Dell Optiplex
380, 390, 745, 755, 760, 790

Dell Latitude (netbooks)
2100, 2110, 2120

[quote=“sid, post: 2680, member: 558”]Thanks for the kernel, but I keep getting permission denied when I try to copy it to tftpboot/fog/kernel folder.
I use winscp and log on to server with admin account.
any Idea?
thanks[/quote]

I’m not sure… It could be because the folder only has root access. In Winscp I would check the Kernel’s folder permissions to make sure you have write access to it.

I recently made my own Kernel as a proof of concept. Its based of the Linux 3.3 Kernel and it resolved a lot of problems for me. Its attached in my post here. Be sure to backup any of your existing Kernels in /tftpboot/fog/kernel/

Let me know if it works for you.

[url]http://scatteredspace.com/Fog/bzImage.zip[/url]

It looks like I may have worked around this now. I was resizing the partition in Windows before I imaged with fog but after booting into Gparted live I noticed that the NTFS partition was still the max size of the disk even though Windows was reporting that the disk size was smaller. What I ended up doing was shrinking the partition in GParted and that worked.

On a side note, I noticed that shrinking the partition in GParted causes windows 7 to do a check disk right before the OS boots. To make a cleaner image I let the system go through with the check disk and then after it rebooted it bounced it up to Fog. I still haven’t had any luck getting Single Disk Resizable working…

Hi there,
I’m running into a few issues using Fog .32 but one of the most annoying problems that I see consistantly is the “can’t have a [I]partition outside of disk” [/I]error.

For some reason if I try to use Single Disk Resizable, Fog will finish verifying resizing the disk but will freeze after that step. Because of this we have been using Multiple Disk Single Disk Nonresizable, which works most of the time. To work around this partition issue I reduced the OS partition on my image to 30GB because I was worried that this message was appearing because I was trying to take an image from a PC with a 80GB OS partition to a hard drive that only had a max size of 60GB. This, however, has not resolved my problem.

So I guess my two questions are, what steps can I take to get Single Disk Resizable working (Ive tried different Kernels) and why does a 30GB OS partition cause this error to show up on 60GB hard drive (granted the imaged was taken from a drive that has a max size of 80GB but the OS partition was shrunk to 30GB)? Any input or advice would be appreciated on this.

EDIT:
Actually I may have resolved this issue by using GParted to shrink the HDD partition down to 20GB. I will have to do further testing.