Fog 0.33 Beta Issue
-
your link is broken, I have the download but it should be [url]https://mastacontrola.com/fogboot/kernel/bzImageAllDevice[/url]
Thanks I will try it
-
The new Kernel will not load at all. Here is a pic of what it says. On this kernel I cant even boot to the client system information screens. Thanks again for taking the time to review this.[ATTACH=full]428[/ATTACH]
[url=“/_imported_xf_attachments/0/428_photo (1).JPG?:”]photo (1).JPG[/url]
-
The driver that seems to be needed is:
Intel L217LMI’m pretty sure that’s already built in but not 100% sure. I’m rebuilding a new kernel that just basically adds the intel chipsets for support to see if that’ll help you out as well. If it doesn’t I’ll try looking further into actually building it into the kernel directly as it’s the only method I can think of to get it there. I’ll basically have to create the driver building process directly which I’ve never done before. This may take a little bit, but in the mean time, give the new kernel a shot. It’ll be named:
[url]https://mastacontrola.com/fogboot/kernel/bzImageIntelChips[/url] -
That link is broken. Can you please verify the link. Thanks
-
I haven’t placed the file, about to now.
-
The new I got this message. [ATTACH=full]429[/ATTACH]
[url=“/_imported_xf_attachments/0/429_photo (2).JPG?:”]photo (2).JPG[/url]
-
I’m rebuilding the kernel. Maybe the new one will work.
It should load now. Again, I don’t know how well it will work, but it’ll be at the same link:
[url]https://mastacontrola.com/fogboot/kernel/bzImageIntelChips[/url] -
Scott,
Can you try my new kernel? It is 3.12.0 and had a couple new drivers added to it, I’m keeping my fingers crossed that this is the driver you need.
-
hey tom would your bzImage help wiht a HP DC8300 SFF/Micro with SSD. I having a hell of a time trying to get fog to register my DC8300 with a SSD but if i put a SATA it works perfect. Fog 0.32 Kernel 3.8.8
-
Well the network driver worked but now once the imaging process begins it hangs, it gets through the inital loading and then it shows waiting for disks to settle, then goes to the imaging screen and something completes very quickly (I believe this is that small win 7 partition that it creates quickly) Then begins to try to load the image. Mine gets to 0% then locks up it copied 97.61 mib before it locked.
-
Well, I take back my last post it is not locked up. It is just running super slow. It has been sitting on the imaging screen now for a half hour and just moved to 1 percent.
-
Attache dis the imaging screen shot. [ATTACH=full]431[/ATTACH]
[url=“/_imported_xf_attachments/0/431_photo (3).JPG?:”]photo (3).JPG[/url]
-
just cruising by since yesterday…what speeds where you getting before you updated to Toms latest bzImage for this exact deploy image? Are you at least 1Gb all the way around from the workstation to the network switch to the fog server? Also what are your specs for the fog server? is it a direct install with linux or you using a VM?
-
Before we were getting very good speeds. We could push this same image to a pc in about 17mins. Th efog server is a quad core beefed up VM
-
Scott,
Check the switch between your client and your server. As these systems network drivers never worked until this latest kernel, how were you imaging them before? Are other clients affected by slow speeds?
-
The switching appears to be fine. If I revert back to 3.8 kernel I can image any other machine with excellent speeds using the same cable/switch. I have never imaged this lenovo pc. It is a new pc I am testing before I purchase them. I want to be sure I can use them with fog before I buy a bunch of them. My M73 Lenovos image perfectly using the same switch/cable to the server. I can put a 40 gb image down in about 17 mins.
-
While on the 3.12, does it affect the speeds of the known good systems?
-
I will check this tomorrow. Thank You
-
The systems that are known to be good are slow as well using 3.12 kernel.
-
Scott,
I’m currently rebuilding another 3.12.0 kernel that is based strictly off the Core Config. Removed the KMS Requirements and added all network drivers back. There are no other tweaks to this configuration. Please test this new kernel to see if you have an improvement. If you don’t I’ll keep tweaking the kernel settings as then I know it’s likely something with the drivers that’s causing your issue.
It will probably be about 30 minutes or so, but it will be at the same link as it’s the same file. Just give me till the turn of the next hour and it’ll be up. I hope this helps.
