Topics created by fabritrento

@fabritrento I’ll be honest, I have no idea what you’re saying is isn’t happening here?

@fabritrento That’s not how this works. Just saying lol. 6.1.22 works fast for your situation, but that doesn’t mean there’s truly something wrong with the kernel for everybody. So when the next stable release comes out, you should remember to switch back to 6.1.22 and we’ll work to keep trying to update the kernels and hope that you’ll test them to see if it works for your situation so you don’t have to revert it to 6.1.22.

@fabritrento As you stated it, UAC is preventing access. There is no real way to fix user cleanup that I’m aware of.

We have started working to remove the features that we cannot manage.

case 'service-autologout': $this->serviceAutologoutPost(); break; case 'service-displaymanager': $this->serviceDisplaymanagerPost(); break; case 'service-hostnamechanger': $this->serviceHostnamechangerPost(); break; case 'service-hostregister': $this->serviceHostregisterPost(); break; case 'service-powermanagement': $this->servicePowermanagementPost(); break; case 'service-printermanager': $this->servicePrintermanagerPost(); break; case 'service-snapinclient': $this->serviceSnapinclientPost(); break; case 'service-taskreboot': $this->serviceTaskrebootPost(); break; case 'service-usertracker': $this->serviceUsertrackerPost();

Sorry that it isn’t “pretty” but this is the code moving forward. You can think of anything not on this list, but still accessible in the 1.5.x versions as being deprecated (to non-functionality)

@fabritrento yes, you can interchange them though sometimes (not the case here) the biggest concern is schema updates between different versions.

In this case, dev-branch is the basis of stable, so these should be effectively interchangable.

Change your Boot Exit settings in the fog web GUI to GRUB. If that is your current setting change to SANBOOT.

@fabritrento said in what tftp image is right to use?:

PXEClient:Arch:00007

FWIW there are 3 or 4 uefi arch classes. I would at least create arch 7 and arch 9 classes, the others are for 32 bit processors.

solved, ip on dhcp server option was incorrect

@fabritrento For others that might find this thread, the FOG installer doesn’t support and has not been tested on ubuntu 22.04 as of this post. Since 22.04 is an LTS release it will be supported in the near future with FOG 1.5.10 when its released. For now use 20.04 as the OP of the thread found.

@fabritrento No.

Github on different branches might. The Tar files are built off the repository.

If you use the dev-branch or master branches from github, it’s identical to how the tar.gz file operates.

@fabritrento Try apt-get autoremove

with latest svn the problem is solved

From where to where did you update?? Version 1.2.0 to current SVN? I did that lately and thought that FOG had deleted my files but it just moved them (to /tftpboot.prev and /var/www/fog.prev if I remember right)…

Though I will admit, I don’t know if we tested XP/2000 OSID type.

Known about issue and is fixed in SVN.

Partition one is your Windows system, partition two looks like it’s the start of your linux system, but what volume is partition actually formatted in?

First things first,

How is this fog’s fault? What I mean, if you put the Video card in and the system can’t boot network, wouldn’t that indicate there’s something wrong with the motherboard? There’s nothing I can do for that.

Second,

When you task the system, does it perform the tasking and you just can’t see the information? I mean, that would indicate a kernel driver problem, but seeing as the problem (seemingly) starts before this, it once again leads back to the system motherboard of video card being problemattic. If the case is that imaging tasks and such actually are operating, I’ll request that you attempt making a custom kernel, but from the information I got from this very short post, this probably isn’t going to fix the problem.

finally i get a working config:

:UBUNTU
See [url]http://manpages.ubuntu.com/manpages/precise/man7/casper.7.html[/url] for casper cmdline details
kernel [url]http://192.168.0.3/fog/iso/ubuntu/casper/vmlinuz[/url]
initrd [url]http://192.168.0.3/fog/iso/ubuntu/casper/initrd.lz[/url]
imgargs vmlinuz root=/dev/nfs boot=casper netboot=nfs nfsroot=192.168.0.3:/var/www/fog/iso/ubuntu/ locale=en_US.UTF-8 keyboard-configuration/layoutcode=no mirror/country=NO
boot || goto failed
goto start

$ cat /etc/exports
/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
/var/www/fog/iso/ubuntu/ *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)

administrator@fog:/var/www/fog/iso/ubuntu$ ls -la
totale 32
dr-xr-xr-x 5 root root 4096 dic 5 12:48 .
drwxr-xr-x 3 root root 4096 dic 5 12:47 …
dr-xr-xr-x 3 root root 4096 dic 9 08:37 casper
dr-xr-xr-x 2 root root 4096 ago 9 22:19 .disk
dr-xr-xr-x 2 root root 4096 ago 9 22:19 isolinux
-r-xr-xr-x 1 root root 8351 ago 9 22:20 SHA256SUMS
administrator@fog:/var/www/fog/iso/ubuntu$

This is, again, the nature of UDP. It just blasts your network. It’s not a failure to get dhcp, it’s a failure that your switch cannot cope with the hammering effects of Multicast.

Are you talking about multiboot or is this single boot systems?

[quote=“Jaymes Driver, post: 39693, member: 3582”]Is there a particular reason you want to multicast these?[/quote]

100Mb switch maybe 🙂