Posts made by Sebastian Roth

@chaonatic The error seen in the picture points to a spelling issue in the filename I am pretty sure. Linux is case sensitive! Make sure it’s named exactly as seen in the picture.

@Pilar As I said before you should fine log files with more details on your FOG server in /var/log/mysql/ directory!

https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@Pilar The output from systemctl doesn’t give enough information. Check the log files I suggested.

when It failed I had a lack of disk space but now i have a new disk bigger to add.

Most probably the database is “corrupted”. In most cases this can be recovered easily but we need the information from the logs to be able to help you.

@WT_101 Probably you have a proxy server in your network. Search the forums for proxy and you’ll find information on this.

@Pilar First check disk space (command df -h) and if that’s fine then start looking at the log files to see what error is causing the DB to start. Usually you find those in /var/log/mysql/...!

@george1421 said in New release?:

I think everything has been solved in 1.5.9.111, right?

No. There is a fair amount of things still open that would be great to get fixed before the release: https://github.com/FOGProject/fogproject/issues plus a few things I track in the forums and on another list, maybe even look into the fog-client/zazzles issues for a next fog-client version to release with it.

On top we shall get the act together and finalize documentation on docs.fogproject.org (and bury the somewhat dated wiki)!

Anyone keen to work together and get this done?

@Tom-Elliott said:

The UI for 1.5 was itself quite an overhaul but shows too little progress now (that we’re at 1.5.9). Moving to 1.5.10 seems cursory at this point, in my opinion.

Not sure I understand what you mean by “cursory”? We have done more than 100 commits (114 as of today) since the release of 1.5.9, fixed many things plus a few dozen more commits in the FOS repo as well and I reckon it worth another 1.5.x release.

I’m keen, if everybody else is, to look over 1.6 vs 1.5.x and just simply moving over to it.

Don’t think we are ready to push everyone to 1.6.x just now - yet the support we’d need to provide in the forums. While a fair amount of people got with the dev version and even dove into the new 1.6.x branch we also have many users asking for some stability in FOG. For those I’d suggest they stick with 1.5.x for now and probably some months down the road until 1.6.x is fully ready for production. Just my opinion.

@amjfrankenstein Can you please post a full diff of the changes you made?

@migsterzs Can you please post your fog-client log here so we see the actually calls and might be able to help.

@cul3r0 OK so you are trying to setup FOG with a custom certificate. I suppose you have the private key matching that certificate as well as the CA certificate at hand, right?

@JYost Updating to 1.5.9.111 is one way but you can also just update the FOS init.

In the picture we see you’re still using the FOS init that was released with FOG 1.5.9. This init definitely has issues with newer 20H2 (and also earlier version I think).

To update the init just follow these commands (run as root on your FOG server):

cd /var/www/html/fog/service/ipxe/
mv init.xz init.xz.orig
mv init_32.xz init_32.xz.orig
wget https://github.com/FOGProject/fos/releases/latest/download/init.xz
wget https://github.com/FOGProject/fos/releases/latest/download/init_32.xz

Try a new capture and pay attention to the “Init version” that is shown on bootup. Should be newer than what we see in the picture now.

@cul3r0 In this topic the issue is very likely due to a custom CA and certificates. When FOG generates self signed certs for you it’s usually working out of the box if you don’t mess with it.

As every case is different I may ask you to open a fresh new topic on your own. Link to this one as reference but then more important give us your details, like FOG version, custom modifications and so on.

@george1421 said in Ubuntu Server 20.04.3 LTS with FOG 1.5.9 - Standalone:

The author of the post should be able to edit it.

Looks like this is only possible for a certain amount of time if you’re not a moderator. @Tom-Elliott is that a setting we can change?

Sorry for messing up this post. We’ll delete all that later on.

@bristow-0 said in Modify the linux system of a workstation in multi-boot ?:

I guess I have to copy the d1p2.img file? What about the other files, I don’t need them?

Yes in this case you would copy d1p2.img but name it d1p5.img in the new image directory (so it will be deployed to the correct partition on the new systems). No other files needed because you only deploy that single partition.

Be aware it’s very likely the bootloader won’t play nicely without more work on this but give it a try.

@Chuck2000 The mentioned disk space is just one problem that can lead to this. Obviously it’s not the case for you.

The picture you posted seems from an older version of FOG. Which version of FOG do you use?

@Roc1479-0 Edited as you wish.

@zaqen said in HP 405 G6 deploy error:

Is it possible to give the kernel name at group level?

Sure, FOG web UI -> FOG COnfiguration -> FOG Settings -> expand all -> search for Kernel.

Or simply rename the bzImage-5.15.5 to bzImage (and rename the original bzImage instead of overwriting it just to be sure to have a backup copy).

@michaeloberg Ok, I just build a new kernel without the cdc_ether driver included (latest 5.10.83): https://fogproject.org/kernels/bzImage-no-cdc_ether

Give that a try and let us know.

@roc1479-0 Thanks for posting this tutorial.

git clone https://github.com/fogproject/fogproject.git fog_latest/
./fog_stable/bin/installfog.sh

Those two commands don’t add up. Path names don’t match. As well we suggest to run the installer script within the same directory, so

 cd /opt/fog_.../bin
./installfog.sh

@michaeloberg said in HP Probook 430 G8 System MAC not passing through USB Type-C Dongle:

MAC Address passthrough works through iPXE but not any higher level Operating Systems - Linux, FOS, or Windows.

This is definitely something HP needs to explain I would think! If Windows is not able to see the system/pass-through MAC then it’s likely their fault. Though I still find it interesting that iPXE has access to this MAC.

Definitely look into firmware updates as suggested by George.

Edit: Ok, looking at the pictures again and again I might have another route here. The USB NIC chip seems to be a Realtek 8153 according to the USB IDs. Without much thinking I opened the (first link on the web)[http://linux-hardware.org/?id=usb:0bda-8153] and found the cdc_ether driver mentioned in there. This driver has a story to it. We removed it from our kernel back in the days of the 4.x Linux kernel series because it caused trouble with MS Surface devices. When going to the 5.x series it was re-enabled (for unknown reasons - by kernel oldconfig?) and we still have it in our kernels now. There was a post about this in March but we never got to decide weather we would remove the cdc_ether again or not: https://forums.fogproject.org/topic/15238/laptop-with-integrated-4g-modem