• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Eazis
    3. Posts
    • Profile
    • Following 0
    • Followers 0
    • Topics 6
    • Posts 38
    • Best 2
    • Controversial 0
    • Groups 0

    Posts made by Eazis

    • RE: ASUS NUC14MNK fos kernel no netwerk drivers

      @Tom-Elliott Afbeelding van WhatsApp op 2025-06-17 om 17.24.38_76bd3e74.jpg

      posted in FOG Problems
      EazisE
      Eazis
    • RE: ASUS NUC14MNK fos kernel no netwerk drivers

      @Tom-Elliott Is there anything i can do for you? Maybe we can chat anywhere?

      posted in FOG Problems
      EazisE
      Eazis
    • RE: ASUS NUC14MNK fos kernel no netwerk drivers

      @Tom-Elliott Is there any other we could try?

      posted in FOG Problems
      EazisE
      Eazis
    • RE: ASUS NUC14MNK fos kernel no netwerk drivers

      @Tom-Elliott

      All 3 commands didn’t work.
      Here is a output from /sbin/ip addr
      I have also added a screenshot from my BIOS, i hope that helps
      NOTE: the enp0s20f0u7 is a USB->NIC adapter i need this to go into the FOS kernel. So normally this USB->NIC adapter is not connected to the system.

      Afbeelding van WhatsApp op 2025-06-13 om 16.28.10_f61de18b.jpg Afbeelding van WhatsApp op 2025-06-13 om 16.28.11_46943113.jpg

      posted in FOG Problems
      EazisE
      Eazis
    • RE: ASUS NUC14MNK fos kernel no netwerk drivers

      @george1421

      Here you go. I have done this with the FOS kernel which Tom have created.
      The enp0s20f0u7 which you see is my usb -> nic adapter, otherwise i cant start a deploy task.

      Afbeelding van WhatsApp op 2025-06-13 om 13.15.40_a1ec94ab.jpg

      Afbeelding van WhatsApp op 2025-06-13 om 13.13.14_1e116919.jpg

      Afbeelding van WhatsApp op 2025-06-13 om 13.13.14_6e4b9197.jpg

      posted in FOG Problems
      EazisE
      Eazis
    • RE: ASUS NUC14MNK fos kernel no netwerk drivers

      @Tom-Elliott

      Thanks i tried your version but now i got this inside the FOS kernel.
      The normal FOS kernel can boot into other pc’s except for the ASUS NUC.

      Afbeelding van WhatsApp op 2025-06-12 om 16.17.51_dba25bf5.jpg

      posted in FOG Problems
      EazisE
      Eazis
    • RE: ASUS NUC14MNK fos kernel no netwerk drivers

      @george1421 said in ASUS NUC14MNK fos kernel no netwerk drivers:

      @Eazis Ok A little google-fu shows this is not an 8169 nic but a 8125 (2.5GbE) nic. (I personally really dislike realtek because of this BS).

      So now we need to figure out how to add 8125 native nic support to the FOS kernel.

      It seems the FOS kernel is misleading us 🙂
      Windows already reports the hardware ID as 8125.

      Is there any chance of getting this driver included in the FOS kernel?

      For now, I have a workaround using USB-to-LAN to boot into FOS, but it’s far from ideal.
      MAC address swapping inside the GUI etc.

      posted in FOG Problems
      EazisE
      Eazis
    • RE: ASUS NUC14MNK fos kernel no netwerk drivers

      @george1421 I have tried Linux kernel 6.12.25 unfortunately this didn’t fix the NIC driver problem.

      posted in FOG Problems
      EazisE
      Eazis
    • RE: ASUS NUC14MNK fos kernel no netwerk drivers

      @george1421 said in ASUS NUC14MNK fos kernel no netwerk drivers:

      @Eazis will you check to see if the beta version 6.12.x series fixes the issue? https://github.com/FOGProject/fos/releases

      If not we will need compile a special kernel with the current realtek driver installed. The linux mainstream kernel drivers typically lags current hardware.

      I will try tomorrow and let you know.

      posted in FOG Problems
      EazisE
      Eazis
    • RE: ASUS NUC14MNK fos kernel no netwerk drivers

      @Eazis I have made a screenshot in Windows 11 >

      afbeelding (3).png

      posted in FOG Problems
      EazisE
      Eazis
    • ASUS NUC14MNK fos kernel no netwerk drivers

      I’m discovering a missing network driver inside the latest FOS kernel (6.6.69) for the ASUS NUC14MNK.
      Is there a way to add this driver?

      NIC: Realtek PCIe 2.5GbE Family Controller

      Afbeelding van WhatsApp op 2025-06-06 om 13.19.19_2453aba3.jpg

      Afbeelding van WhatsApp op 2025-06-06 om 13.19.19_00be390e.jpg

      posted in FOG Problems
      EazisE
      Eazis
    • RE: Multicast stuck

      @george1421 said in Multicast stuck:

      [09-18-24 9:36:35 am] Interface not ready, waiting for it to come up: 10.54.68.101
      [09-18-24 9:36:45 am] Interface not ready, waiting for it to come up: 10.54.68.101
      [09-18-24 9:36:55 am] Interface not ready, waiting for it to come up: 10.54.68.101

      If you disable the storage node then you will get this message inside the log.

      I found out that it wasn’t a FOG problem but i mixed up some vlans together.
      Multicast works now. Problem solved.

      posted in FOG Problems
      EazisE
      Eazis
    • RE: Multicast stuck

      @george1421 Thanks for you answer.

      Ok i will give you much info as needed.
      My first setup about a year ago was one physical server. This physical server was retired and needed to be replaced.
      I replaced this with a HP DL360 Gen9 and put this into my virtual datacenter lab (which is ovirt), Here work’s my multicast.
      On this time i had only one VM running FOG.
      Then I decided to change to a cluster with 3x HP DL360 Gen9 and split FOG into master and storage node, to have a failover.
      All 3 servers have a physical network link to the same switch (Netgear GS108PE) and these networks are only used inside the VM.
      Both VM’s are on the same subnet. Other network ports from the HPs are in use for gluster network and management network which are needed inside ovirt and are not available inside both vm’s and are connected to my ubiquiti switches.

      The storage node is the master node. Maybe this is wrong? Maybe i mixed some things up?

      FOG installation -> 10.54.68.101
      FOG storage node -> 10.54.68.102

      My FOG installation multicast.log says this ->

      [09-18-24 9:36:35 am] Interface not ready, waiting for it to come up: 10.54.68.101
      [09-18-24 9:36:45 am] Interface not ready, waiting for it to come up: 10.54.68.101
      [09-18-24 9:36:55 am] Interface not ready, waiting for it to come up: 10.54.68.101
      [09-18-24 9:37:05 am] Interface not ready, waiting for it to come up: 10.54.68.101
      [09-18-24 9:37:15 am] Interface not ready, waiting for it to come up: 10.54.68.101
      [09-18-24 9:37:25 am] Interface not ready, waiting for it to come up: 10.54.68.101
      [09-18-24 9:37:35 am] Interface not ready, waiting for it to come up: 10.54.68.101
      [09-18-24 9:37:45 am] Interface not ready, waiting for it to come up: 10.54.68.101
      

      network interface on master

      1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
          link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
          inet 127.0.0.1/8 scope host lo
             valid_lft forever preferred_lft forever
          inet6 ::1/128 scope host
             valid_lft forever preferred_lft forever
      2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
          link/ether 56:6f:26:4b:00:09 brd ff:ff:ff:ff:ff:ff
          inet 10.54.68.101/24 brd 10.54.68.255 scope global noprefixroute enp1s0
             valid_lft forever preferred_lft forever
          inet6 fe80::546f:26ff:fe4b:9/64 scope link noprefixroute
             valid_lft forever preferred_lft forever
      

      network interface on node

      1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
          link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
          inet 127.0.0.1/8 scope host lo
             valid_lft forever preferred_lft forever
          inet6 ::1/128 scope host
             valid_lft forever preferred_lft forever
      2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
          link/ether 56:6f:26:4b:00:08 brd ff:ff:ff:ff:ff:ff
          inet 10.54.68.102/24 brd 10.54.68.255 scope global noprefixroute enp1s0
             valid_lft forever preferred_lft forever
          inet6 fe80::546f:26ff:fe4b:8/64 scope link noprefixroute
             valid_lft forever preferred_lft forever
      

      If you need any more info from me, i can give you this.

      posted in FOG Problems
      EazisE
      Eazis
    • Multicast stuck

      Hello,

      Some weeks ago i changed my configuration into two vm’s. One installation as normal and the other as storage node.
      After this my multicast is not working anymore. I have really no idea how this can be resolved. Is there anyone who can point me in the right direction?

      Both vm’s are running on almalinux 9 and FOG 1.5.10.16

      Afbeelding van WhatsApp op 2024-09-17 om 12.01.05_1949e18d.jpg

      multicast configuration
      ac5ab8dc-3efb-409a-82fe-6061fc52c2c6-image.png

      storage node configuration
      d434b434-b7cf-4235-b4ad-721fcf7cbe5b-image.png

      multicast.log.udpcast.5 on storage node

      [09-17-24 11:21:16 am] Task started
      Udp-sender 20200328
      Using mcast address 234.54.68.102
      UDP sender for /home/images/EEETopASUSPROA4110/d1p1.img at 10.54.68.102 on enp1s0
      Broadcasting control to 224.0.0.1
      New connection from 10.54.68.119  (#0) 00000009
      New connection from 10.54.68.170  (#1) 00000009
      Starting transfer: 00000009
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
      Dropping client #0 because of timeout
      Disconnecting #0 (10.54.68.119)
      Dropping client #1 because of timeout
      Disconnecting #1 (10.54.68.170)
      bytes=                re-xmits=0000000 (  0.0%) slice=0112 -   0
      Transfer complete.^G
      
      Udp-sender 20200328
      Using mcast address 234.54.68.102
      UDP sender for /home/images/EEETopASUSPROA4110/d1p2.img at 10.54.68.102 on enp1s0
      Broadcasting control to 224.0.0.1
      
      

      multicast.log on storage node

      [09-17-24 11:21:16 am]  | Task ID: 5 Name: Multi-Cast Task - Clone1 is new
      [09-17-24 11:21:16 am]  | Task ID: 5 Name: Multi-Cast Task - Clone1 image file found, file: /home/images/EEETopASUSPROA4110
      [09-17-24 11:21:16 am]  | Task ID: 5 Name: Multi-Cast Task - Clone1 2 clients found
      [09-17-24 11:21:16 am]  | Task ID: 5 Name: Multi-Cast Task - Clone1 sending on base port 52186
      [09-17-24 11:21:16 am]  | Command: /usr/local/sbin/udp-sender --interface enp1s0 --min-receivers 2 --max-wait 600 --portbase 52186 --full-duplex --ttl 32 --nokbd --nopointopoint --file /home/images/EEETopASUSPROA4110/d1p1.img;/usr/local/sbin/udp-sender --interface enp1s0 --min-receivers 2 --max-wait 60 --portbase 5>
      [09-17-24 11:21:16 am]  | Task ID: 5 Name: Multi-Cast Task - Clone1 has started
      [09-17-24 11:21:26 am]  | Task ID: 5 Name: Multi-Cast Task - Clone1 is already running with pid: 130868
      [09-17-24 11:21:36 am]  | Task ID: 5 Name: Multi-Cast Task - Clone1 is already running with pid: 130868
      [09-17-24 11:21:46 am]  | Task ID: 5 Name: Multi-Cast Task - Clone1 is already running with pid: 130868
      [09-17-24 11:21:56 am]  | Task ID: 5 Name: Multi-Cast Task - Clone1 is already running with pid: 130868
      [09-17-24 11:22:06 am]  | Task ID: 5 Name: Multi-Cast Task - Clone1 is already running with pid: 130868
      
      

      .fogsettings on storage node

      ## Start of FOG Settings
      ## Created by the FOG Installer
      ## Find more information about this file in the FOG Project wiki:
      ##     https://wiki.fogproject.org/wiki/index.php?title=.fogsettings
      ## Version: 1.5.10.29
      ## Install time: Mon Jun 24 10:11:34 2024
      ipaddress='10.54.68.102'
      copybackold='0'
      interface='enp1s0'
      submask='255.255.255.0'
      hostname='server-08.eazis'
      routeraddress=''
      plainrouter=''
      dnsaddress=''
      username='fogproject'
      password='aNjVWQhQeiW9KpXxeP*t'
      osid='1'
      osname='Redhat'
      dodhcp=''
      bldhcp=''
      dhcpd='dhcpd'
      blexports='1'
      installtype='S'
      snmysqluser='fogstorage'
      snmysqlpass='BL-XFitFm0lNFkhh5UGI'
      snmysqlhost='10.54.68.101'
      mysqldbname='fog'
      installlang='0'
      storageLocation='/home/images'
      fogupdateloaded=1
      docroot='/var/www/html/'
      webroot='/fog/'
      caCreated='yes'
      httpproto='http'
      startrange=''
      endrange=''
      packages='bc curl gcc gcc-c++ genisoimage git gzip httpd lftp m4 make mariadb mariadb-server mod_ssl mtools net-tools nfs-utils openssl php php-bcmath php-cli php-common php-fpm php-gd php-ldap php-mbstring php-mysqlnd php-process syslinux tar tftp-server unzip util-linux-user vsftpd wget xz-devel'
      noTftpBuild=''
      tftpAdvOpts=''
      sslpath='/opt/fog/snapins/ssl/'
      backupPath='/home/'
      armsupport=''
      php_ver='8.0'
      sslprivkey='/opt/fog/snapins/ssl//.srvprivate.key'
      sendreports='Y'
      ## End of FOG Settings
      
      posted in FOG Problems
      EazisE
      Eazis
    • RE: Use of different ipx files between different hardware

      @george1421 Ok thanks for your reply. In the past i already did some research and found the arch 7 flags.

      I will check out the uuid and come back with results. Thanks.

      posted in Hardware Compatibility
      EazisE
      Eazis
    • Use of different ipx files between different hardware

      I have already a long time a problem with my DHCP on all clients (EEETop ASUS ASUSPRO A41GAR) .

      My DHCP config is this:

      class "UEFI-64-1" {
          match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
         #filename "ipxe.efi";
         filename "snponly.efi";
      }
      

      The system EEETop ASUS ASUSPRO A41GART needs to use snponly.efi and the system EEETop ASUS E1600WK needs to use ipxe.efi.
      All the other system can also use ipxe.efi.

      I have also tried other efi files but there is not any file which works for all the system.

      When this happens my collegue ask me to change the dhcp settings and restarting the dhcp service, but when i’m a day off they have problem to image such system who needs snponly.efi

      How can i solve this problem?

      posted in Hardware Compatibility
      EazisE
      Eazis
    • RE: LDAP plugin

      @Tom-Elliott Yes this resolves the issue.

      posted in General
      EazisE
      Eazis
    • RE: LDAP plugin

      @kamburta said in LDAP plugin:

      PHP Fatal error: Uncaught TypeError: ldap_unbind(): Argument #1 ($ldap) must be of type resource, null given in

      7c8afbbb-f0b7-45d8-9c3b-3e5949a3139a-image.png

      ldap is enabled in php.

      posted in General
      EazisE
      Eazis
    • RE: LDAP plugin

      I have the same problem when installing the same version.
      Did anyone resolve this issue?

      posted in General
      EazisE
      Eazis
    • RE: Another LDAP topic

      @tom-elliott Many thanks!! I used now the internal ip address of the AD server … This was the whole problem.
      A vaild domain name here did not work.

      Normally this AD server is reachable with this fqdn YYYY.XXXX.com (it’s not the real domain). I can’t type public this domain here for security reasons.

      I can now login with users from my AD into FOG.

      posted in General
      EazisE
      Eazis
    • 1 / 1