Latest Development FOG
-
Yeah for sure. Im running right now 2473
-
ok, tom tells me that if you have the latest fog and add to the host profile the host kernel argument [CODE]has_usb_nic=1[/CODE] that you will get what you need. you will need to unplug the usb nic and plug it back in after the kernel loads in order to ensure it get’s DHCP properly, however.
-
how do I add it to the host profile ?
-
on the page for that host, under general, there is a field for “Host Kernel Arguments”
-
just tried it. Didn’t work
running 2475 -
Ok so new issues guys. Ever since I went to the new build 2475 when I go to register the PC for full inventory It says unable to register the pc for the following reasons and doesn’t give a reason but scrolls threw like its registering and just sits there. This didn’t happen with 2473. Also I took out the kernel argument as well.
-
quick registration does the same … however you will get attempting to register host and a blinking curser keeps moving down the screen.
-
So at what point were you able to register the systems before?
What I mean, 2473 to 2475 didn’t have anything dealing with kernel drivers or anything of the sort. So from an OS layer (bzImage and initrd) standpoint, nothing had changed. The only thing we wanted you to do was add:
has_usb_nic=1 to the parameters of the Host. If the hosts aren’t registered, you’re more than likely going to have to register, manually, the host and MAC of the nic you’re trying to boot. I’m sorry it’s not fully automated, but there simply isn’t a way for me to know what type of nic you have to determine if it’s USB or local. So the registration step could be skipped.
Basically, if you have a nic, the MAC Address should be printed on the back of it.
Create the Host by going to the GUI. Go to Host Management Page.
From the Host Management Page, choose Create New Host.
Type in the Hostname you want, and the MAC Address of the nic.
Then save and it should create the host for you. Once it’s saved, it will take you to the edit page. You can then add the Host Kernel Arguments. It is in that field that you would put has_usb_nic=1
Then you can setup taskings for it such as upload or download. Put the NIC in the host and boot it up. When the init loads, it will stop requesting you to remove the NIC and then plug it back in. I’d recommend waiting a few seconds once it’s unplugged to ensure it removes. Then plug it back in and press enter. It will then try obtaining an IP address.
It is in this part I believe your system is failing. It recognizes the NIC, but the kernel can’t release it to allow it to pick up a new ip. This is why removing and adding the adapter back in seems to help.
While it’s a couple extra steps, it certainly beats imaging a system using CD.
-
Tom,
I cant even register regular non UEFI PXE computers ever since i upgraded to 2475. The Dell Venu Tablet is another issue. I cant image anything now. When i said i couldnt register devices i meant regular pxe booting.
-
The way i registered hosts was through pxe booting. Basically boot to the network card and select perform full host registration and inventory. The process begins and that’s where i get the error and says can not register this device for the following reason…doesnt give you a reason and then you get a blinking cursor . This is happening with everything now. Again this isnt anything to do with the tablets with UEFI. Once i get everything else to image again ill re-approach with the kernel argument.
-
SVN 2481 released.
This weekend I spent most of my time moving snapins to an FTP based system. I built a snapin replicator service. I added storage group setting to the snapins as well.
Basically, this means, especially with location plugins, snapins can be located to the relevant nodes as well.
-
[quote=“Ray Zuchowski, post: 38239, member: 24449”]The way i registered hosts was through pxe booting. Basically boot to the network card and select perform full host registration and inventory. The process begins and that’s where i get the error and says can not register this device for the following reason…doesnt give you a reason and then you get a blinking cursor . This is happening with everything now. Again this isnt anything to do with the tablets with UEFI. Once i get everything else to image again ill re-approach with the kernel argument.[/quote]
Can you do me a favor?
As you’ve updated to svn, first re-update to 2481.
[code]cd /your/location/where/you/downloaded/trunk
svn up
cd bin
sudo ./installfog.sh
y
[Enter]
[Enter][/code]Then copy the trunk’s version of the BootItem.hook.php to your lib hooks directory:
[code]sudo cp packages/web/lib/hooks/BootItem.hook.php /var/www/fog/lib/hooks/BootItem.hook.php[/code]Then test if you can at least get the menu and boot one of your working systems to register.
-
2482 solve my registration problem
-
Tom,
Everything works now. I haven’t tried testing again with the tablets yet but I will today. Imaging now with no issues, however multicasting still doesn’t work. When you go to join the session the clients just make two separate udpcast sessions and the originally multicast session lists as Queued . Also since my tablets are running a UEFI bios. What should I change my Undionly.kpxe to ?
-
you don’t have the option to use legacy methods with the tablets?
-
Not on these. These are Dell Venue 11 Pro 5130s . No option to put in legacy mode. I don’t know why Dell did this. Very dumb on their part.
-
Is it possible in later releases to have undionly.kpxe and a UEFI version stacked ? Meaning when a laptop or tablet is booted … the boot file will first try booting with undionly however if it detects the bios is uefi… Can it then go to that UEFI boot file ? I think I read somewhere online that its possible but it would be cool if maybe possible that was already built in to the undionly.kpxe file as an argument. Maybe have under the general settings the option to specify the UEFI boot file .
-
[quote=“Ray Zuchowski, post: 38265, member: 24449”]Is it possible in later releases to have undionly.kpxe and a UEFI version stacked?[/quote]
That is relevant to my interests.
-
I would LOVE to have this functionality, but haven’t a clue how to handle this programmatically from the undi scripts and what not.
SVN 2483 released. Hopefully should fix the multicast name joining.
-
Tom,
Just upgraded to 2483 to test the multicast on 3 computers and after you type in the session name it loads the script and just sits at the network screen Broadcom Network PXE all rights reserved. So its not longer making its own UDP session but multicast wont start. Also under the multicast section in the gui… is it seconds or minutes for the time out ? I put in 60 for time out cause im basing it off seconds but maybe put something in parenthesis so we know if its mins or seconds. Just a suggestion.
Ray Z
