Again, no critizism about 0.33B. It is very nice and powerful and a lot better than 0.32. I just try to find out how it works. All my questions/feedbacks are not because I dislike/disagree how it works now, but more a question if it works as expected or if it is a bug. It is a beta/release candidate and I thought feedbacks were welcome even if they not always are bugs…
They are welcome, but if you keep throwing information at us without researching if it IS a bug or without ASKING if it is a bug and just assuming and then posting topics like crazy because you don’t understand, you leave us all a little frustrated, and maybe even lead to topics or posts being ignored.
We are more than willing to help you to understand, there some walkthroughs tailored towards individuals that have never used FOG before, and that would be a great place to start.
Please familiarize yourself with the documentation, then come back and ask questions that you don’t understand.
fog_0.33b is still in beta/release candidate, that is correct, and we do want to fix as many bugs as possible. And you can REALLY help us by trying to recreate your issue a couple times. Document how you arrived at the issue, and then attempt to solve it. Make sure to document your steps in solving, as this will help us to help others and to ultimately fix the problem.
Since this is a beta you shouldn’t use it for production anyway, and if you do be prepared to break it and fix it many times, and possibly re-install just as many. Coming to us with a resolve for an issue you found holds a much greater merit than one just saying hey this doesn’t work.
Hello Andy and all the helpful folks in the forums,
This tutorial is great and has me all set up with a generic image. The only issue I am running into right now is that the new Dell machines we are getting in at work don’t have all of their drives in the latest Driver packs.
I looked through their forums and found some tutorials on how to add your own DriverPacks, but they are about 6 years old and I haven’t gotten the steps to work yet, though still working on it. I have found How to add drivers to the existing Driver packs, but thsi means I will have to add the drivers everytime a new DriverPack comes out.
Anyone have any idea how to add my own driver pack so I can put all the missing drivers in it and not have to mess with the driverpacks that can be obtained from the DriverPack site?
Have now connected everything to the school VLAN again.
Rebooted after fixing sleep 30.
Checked multicast log - no log for the last 3 hours
Multicast to 2 HP
TFTP is now running after reboot (problem fixed)
Multicast failed as expected
Stop and start multicast
Multicast to 2 HP
Multicast worked as expected
Checked multicast log - it is running now, BUT, the log shows 7:30 PM when it is actually 9:30 PM on the Ubuntu clock as it is in reality here in Norway. I just mention it in case it has significance.
This multicast problem is now predictable and fixable for me. I’m heading home.
Marking this thread solved for now as the OP is able to capture and deploy his tablets with the modified kernel. Although this is not a proper solution (more a hackish kind of workaround) we cannot do anything else than waiting for the people from HP we got in contact with to possibly fix the UEFI firmware!
As of now the HP devs confirmed our findings (screwed memory addresses) but we haven’t heard back from them for two weeks now. No solution yet…
Add the caveat now to Fedora 19, being that they changed the database (mysql) to mariadb. All works, but requires minor changes in the script. I’ve already created a thread pointing out the issue with Fedora 19 and a fixed tarball for it based on FOG 0.33b, though the same changes could just be made in 0.32.
@Wayne-Workman Update. OK I have been able to test further. Capturing, deploying, and auto join to AD is working fine. Thank you everyone for all your help! This is a pretty powerful program. I am having printer setup issues, however I will either start another thread or jump in on an ongoing printer thread. You can set this thread as solved. :+1:
There were a couple references to this “with a partition scheme suitable for EFI”. Which makes me wonder if there has to be something done special with the init fs to make it efi suitable??
Interesting. Haven’t thought about this before. Well we do have FOG (FOS) running on several different UEFI machines. So I am certain that it works with those inits Tom is building. AFAIK there is no partition scheme involved. initrd is just a compressed image file - no MBR, no partitions, no GPT …
Dell Latitude E5470
Intel Ethernet Connection I219-LM
Intel Boot Agent PXE Base Code
Kernel bzImage Version 4.8.11
Kernel bzImage32 Version 4.8.11
Date Tested 12-01-2016
Multiple Partition Image - Single Disk (Not Resizable)