Fog 0.33 Beta Issue
-
You need a different kernel then, just because your nic card works before “linux” boots doesn’t mean that “linux” is happy with the driver supplied.
To be more specific, you need to include your network card driver in the kernel.
-
How would I go about getting this nic card in the kernel?
[B][SIZE=6][COLOR=#4d4e53][FONT=Prelo-Bold][SIZE=24px]Lenovo ThinkCentre M83 10AM - Core i3 4130 3.4 GHz[/SIZE][/FONT][/COLOR][/SIZE][/B] -
I’ll need to look, which kernel are you using? Are you sure you’re using the one you downloaded?
The kernel I’ve created has all networking drivers capable so far. It jus doesn’t have wireless drivers.
-
I was using the one you gave in the download above. 3.11.1 I believe is what it was.
-
If you downloaded from my site, the kernel is 3.11.6, but can you provide more information about the type of network on your system? I can try to add that driver to the kernel.
-
I am running cat 5e cable to a mix of hp 2848 gb procurve switches and cisco 100mb cisco 3500 switches. The pc is a
[B][SIZE=6][COLOR=#4d4e53][FONT=Prelo-Bold][SIZE=24px]Lenovo ThinkCentre M83 10AM - Core i3 4130 3.4 GHz[/SIZE][/FONT][/COLOR][/SIZE][/B]My current pc’s that work with fog now are Lenovo M75’s
Is this what you are looking for
-
No I need to what what type of network is it. I’ll look up what it is if I can.
-
Thank You
-
So I’ve rebuilt a kernel, though it looks like the type of driver you need is an Intel driver, which I assure you has been built in. This new kernel is 18Mb and contains anything and everything I could find pertaining to drivers. It has many many things inside.
Give it a go, if it works, awesome, if not I’ll try again.
[url]https://mastacontrola.com/fogboot/kernel/bzImageAllDevice[/url]
-
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.