The kernel published in my previous post does not work for me. I may be doing something wrong, but it did not work on three different computers I tried to PXE boot.

I found this driver that is not upstream yet but this is for the Qualcom/Atheros ALX series.

[url]http://www.orbit-lab.org/kernel/compat-wireless-3-stable/[/url]

It appears that this is for the 3.6.x series kernel. I’m going to download this kernel and compile it with the latest driver listed on the link above.

Wish me luck…

EDIT: well crap, I have to look up how to compile this module into the new kernel. More later…
I also did find that, under ubuntu, there is the “wireless-compat” package(s) which may contain alx drivers.

[quote=“yogipaolo, post: 10395, member: 61”]Another reason why I love this community. I might be using a slightly different gigabyte mobo than you, but your board is likely to have a qualcom/atheros ar8161/8165 chip in it. This chip apparently is bluttooth as well as lan.

A kind soul has posted this link with a direct link to a bzimage download:
[url]http://fogproject.org/forum/threads/dell-2330-all-in-one-network-issue.1054/#post-8470[/url]

I’m going to try this.

I’m also busily compililng a 3.7.5 kernel for the hell of it. I’m going to see if I can use it as an alternative kernel. FOG has the ability to boot specific kernels for specific hosts (I think). This is configurable under host management >> host kernel[/quote]

Another reason why I love this community. I might be using a slightly different gigabyte mobo than you, but your board is likely to have a qualcom/atheros ar8161/8165 chip in it. This chip apparently is bluttooth as well as lan.

A kind soul has posted this link with a direct link to a bzimage download:
[url]http://fogproject.org/forum/threads/dell-2330-all-in-one-network-issue.1054/#post-8470[/url]

I’m going to try this.

I’m also busily compililng a 3.7.5 kernel for the hell of it. I’m going to see if I can use it as an alternative kernel. FOG has the ability to boot specific kernels for specific hosts (I think). This is configurable under host management >> host kernel

[quote=“rightshift, post: 10200, member: 3197”]To clarify. I can PXE boot on the machine in question - I can access fog menu - but I cannot do any inventory options as they simply don’t work. I thus have no way to deploy my image to these machines.

Thanks,
J[/quote]

I am having the same issue. It hangs on “attempting to send inventory” and scrolls down one line at a time til the screen turns black…

I added the machine to the inventory manually and got an upload task to start, but when it comes time to pull the image, i get the message “rpc error netowork not available”.

So why would the LAN work enough to PXE boot but not to use NFS. I’m thinking a custom kernel might solve this, but I’d need to figure out what is going wrong first. The pressure is on at work and my boss is looking stressed, so I need to get the thing backed up. I"m going to use clonezilla and keep the image on a separate HD.

I’ll keep you posted if I figure anything out…

I found this link that may be helpful as I am about to do the same thing due to a nasty virus infection. Will keep you posted.

[url]http://www.fogproject.org/wiki/index.php/Clamav[/url]

Fog is simply awesome. We’re moving closer to using it to replace altiris DS (version 8 i think…).

Anyway, FOG is making my life at work so much easier. I have immense gratitude for the people who develop it. The forums are very friendly and the developers are kind, generous and patient with their time.

I’d like to contribute something, but unfortunately, I’m not a coder. Besides coding, what other ways can I help the the project and the developers?

Thanks

This definitely worked for me as well!
Thank you for this solution. I have 40 of these bad boys to image and I’m trying to impress my boss with fog. This will go a long way towards that aim.

Would you mind filling us in on what mods you made to this kernel?

I’m going to do some toying with the kernel this weekend.

Thanks!
[quote=“Eric, post: 2726, member: 83”]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]

[quote=“jjdlc, post: 2753, member: 877”]I just recently took over an organization with over 600 computers, and am looking at FOG to handle imaging. I was excited at the prospect of using a GPO to push the client to each machine and then have them auto register. Then I find out it isn’t working. I’ve done a bunch of reading and it looks like up until .28 it was, but in .29 they disabled the functionality for some reason and haven’t re-enabled it. I looked through the source code for .28 and .32, and it looks like they started updating hostregister.dll but haven’t finished it. Manually registering 600 computers is a daunting task. One thing I’ve thought about doing, is maybe installing .28 getting everything registered and then upgrading to .32 since I need support for Windows 7.[/quote]

GARRGHH!!! I just promised my boss I can push the client out to existing computers and get an inventory. Now I’m going to look like a boob. Oh well, wouldn’t be the first time…

I have a similar application for this feature. Installing .28 sounds like an interesting idea.
I wonder also if it’s possible to only use the .dll from .28 or simply some of the code from .28 which makes the registration work automatically…

[quote=“Raff, post: 3613, member: 298”]The windows fog client no longer register’s the clients, it was removed a couple of versions ago. You have to do it manually through pxe menu or import via web console.[/quote]

[S]Your post is the first I’ve heard of this. Where did you get this information? The HostRegister.dll is still included in the fog program file folder. I see no other reference to the removal of this feature.[/S]

Ok, after some digging, I see one other reference to this:
[url]http://fogproject.org/forum/threads/fog-client.606/#post-2753[/url]

I’d love to have this feature back. I wish I knew more about programming! Maybe I’ll change that…

Anyway, how can I help get this feature back?
Anyone think of some work-arounds?

All the clients are connected to the gigabit switch and are using gigabit ports.

[quote=“Zardan, post: 1859, member: 185”]Are the clients also connected to a gigabit switch? 10min for that size sounds like ~100mbit speeds.
Ive had the exact same issue when imaging a computer lab that had a old switch with only 100mbit ports, replacing it with a switch that had 1000mbit uplink to the rest of the network fixed the issue for me. Tftp traffic seems to take big hit when the network is overloaded.
If everything looks ok make sure the server have negotiated 1000mbit with the switch.[/quote]

I am running FOG 0.32 on Ubuntu server 10.04.4.

When I try to image more than two computers at once, the PXE boot process takes as much at 5 minutes to load the kernel. I’ve tried increasing the ramdisk size and increasing the TFTPD block size. No joy.

The server is connected to a gigabit port on our switch. Image load times are about 10 minutes for a 10-13GB image, so network speed does not seem to be an issue.

Has anyone experienced this or does anyone have any suggestions on where to look?

Paul