• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. george1421
    3. Best
    • Profile
    • Following 1
    • Followers 64
    • Topics 113
    • Posts 15,322
    • Best 2,772
    • Controversial 0
    • Groups 2

    Best posts made by george1421

    • RE: Issue with loading Fog image to HP AMD systems with Realtek PCIe GbE Family Controller.

      @kweldon said in Issue with loading Fog image to HP AMD systems with Realtek PCIe GbE Family Controller.:

      5.15.x development kernel fixed my issue

      Nice. We’ll need to get 5.15.x into the main stream kernels now. It is very strange for the latest linux kernel to fix a very old network adapter running on new hardware.

      Just be aware that if you update FOG it will replace bzImage with what ever is being currently distributing with FOG at the time.

      When FOG 1.5.10 is released it will probably ship with 5.10.x series kernels unless we can get more fog admins to test 5.15.x series before FOG 1.5.10 is released later this spring.

      posted in Hardware Compatibility
      george1421G
      george1421
    • RE: Windows server as FOG Storage Node - proof of concept blog

      Part 1b

      Here is a rough outline on how to do this same thing with Windows 2008 R2. I hope to be able to test this as soon as I get my test environment rebuilt.

      The following executed correctly on Windows 2008 R2 with Windows Managment Framework installed which installs PowerShell 3.0 I’m actually not using very many powershell commands here, basically just to add windows roles and features. Powershell on Windows 2008 is a bit lacking as compared to 2012.

      Set-ExecutionPolicy Unrestricted -Scope CurrentUser
      Import-Module ServerManager
      
      Add-WindowsFeature FS-FileServer
      Add-WindowsFeature FS-NFS-Services
      
      mkdir c:\share
      mkdir c:\share\tftpboot
      mkdir c:\share\images
      mkdir c:\share\snapins
      mkdir c:\share\snapins\ssl
      
      net localgroup fog_users /add
      net user fog_user "mi5ty_cl0ud" /add /EXPIRES:NEVER /PASSWORDCHG:NO /active:YES /Y
      net localgroup fog_users fog_user /add
      icacls c:\share /grant "fog_users:M"
      
      *****
      
      nfsshare images=c:\share\images -o rw sec=sys root unmapped=yes
      netsh advfirewall firewall set rule group="Server for NFS" new enable=Yes
      
      *************
      
      On FOG server
      mount -t nfs 192.168.1.205:/images /mnt
      mkdir /mnt/dev
      touch /mnt/.mntcheck
      touch /mnt/dev/.mntcheck
      umount /mnt
      
      ****************
      
      # On windows server
      Add-WindowsFeature Web-WebServer,Web-Common-Http,Web-FTP-Server,Web-FTP-Service,Web-FTP-Ext,Web-Mgmt-Console
      
      Import-Module WebAdministration
      New-WebFtpSite -Name "FOGFtpSite" -Port 21 -PhysicalPath "c:\share" -IPAddress "192.168.1.205" 
      
      Set-ItemProperty "IIS:\Sites\FOGFtpSite" -Name ftpServer.security.ssl.controlChannelPolicy -Value 0
      Set-ItemProperty "IIS:\Sites\FOGFtpSite" -Name ftpServer.security.ssl.dataChannelPolicy -Value 0
      Set-ItemProperty "IIS:\Sites\FOGFtpSite" -Name ftpServer.security.authentication.basicAuthentication.enabled -Value $true
      Set-ItemProperty "IIS:\Sites\FOGFtpSite" -Name ftpserver.userisolation.mode -Value 4
      Add-WebConfiguration "/system.ftpServer/security/authorization" -value @{accessType="Allow";roles="fog_users";permissions="Read,Write";users=""} -PSPath IIS:\ -location "FOGFtpSite"
      Restart-WebItem "IIS:\Sites\FOGFtpSite"
      
      *********************************
      
      New-Item "IIS:\Sites\Default Web Site\fog" -type Directory
      New-Item "IIS:\Sites\Default Web Site\fog\service" -type Directory
      New-Item "IIS:\Sites\Default Web Site\fog\service\ipxe" -type Directory
      
      ********************************
      
      In IIS management for the default web site must update mime types to add “.*” (dot star without the quotes) and with a type of “application/octet-stream”
      
      ********************************
      
      #Now that IIS is all setup and ready you will need to copy all of the files from /var/www/html/fog/service/ipxe to the IIS server in the windows path IIS:\Sites\Default Web Site\fog\services\ipxe
      #Lets do this with nfs. Create the NFS share on the Windows server
      
      nfsshare fogipxe=C:\inetpub\wwwroot\fog\service\ipxe -o rw sec=sys root unmapped=yes
      
      ****************
      
      On FOG server
      mount -t nfs 192.168.1.205:/fogipxe /mnt
      cp /var/www/html/fog/service/ipxe/* /mnt
      umount /mnt
      
      ****************
      
      # On Windows server, remove the nfs share
      nfsshare fogipxe /delete
      
      (Note: you need to "replace all child objects permission with inheritable permissions from this object" on C:\inetpub\wwwroot\fog\service\ipxe or the bg download test will fail
      # need to figure out the icacls command on this one
      
      Install the TFTP service as outlined in the OP
      
      
      posted in Tutorials
      george1421G
      george1421
    • RE: Edited undionly.kpxe now receive params: command not found

      @george1421 Working through chat and with Tom’s help we’ve come up with this chain command that should work from the FOG iPXE menu: chain tftp://<SCCM_Server_IP>/SMSBoot\x64\pxeboot.0

      So the idea we came up with is to create a menu entry in fog to call the sccm pxe boot instead of doing it from the sccm end to call fog boot.

      Once the OP has the pxe booting into FOG setup, he can use FOG to either default or fall through the FOG iPXE menu and chain to the sccm pxe boot by setting the sccm chain menu as default or just use fog as normal and leave the menu entry to select sccm boot if that is required.

      The key to getting this setup to work was getting the proper path on SCCM to the pxeboot.0 file.

      The OP is going to continue to test this setup, but the preliminary test was successful.

      posted in FOG Problems
      george1421G
      george1421
    • RE: OMEN 30L GT13 PXE Boot Issue

      @aheerds Lets see if recompiling the latest version of iPXE gets you past this issue: https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe/2

      Also you will want to make sure your FOS Kernel is up to date at 5.15.x release for this new hardware.

      posted in Hardware Compatibility
      george1421G
      george1421
    • RE: Windows server as FOG Storage Node - proof of concept blog

      Part 2

      For the remainder of this thread I’ll continue with the Windows 2008 R2 server as the windows storage node. If time permits I’ll circle back and attempt the same thing with 2012, but based on what I’ve done so far I have confidence that 2012 will work equally as well as 2008.

      There is one bit of error data I found running through a QC check before moving onto the next part. I created the FTP site using the powershell command: New-WebFtpSite -Name "FOGFtpSite" -Port 21 -PhysicalPath "c:\share" -IPAddress "192.168.1.205" While testing I found that the -PhysicalPath switch did not update the ftp server setting causing the ftp server to report that the home folder could not be located. I went into the mmc console for IIS and manually set the homedrive for the ftp server. Once that was done I was able to login via FTP.

      On to the QC checks before moving on to the FOG setup of this. For these tests we’ll use a windows 7 workstation.

      First we need to test to see if the FTP server is working and we can login using the fog_user account we setup.

      C:\>ftp 192.168.1.205
      Connected to 192.168.1.205.
      220 Microsoft FTP Service
      User (192.168.1.205:(none)): fog_user
      331 Password required for fog_user.
      Password:
      230 User logged in.
      

      Just issue a dir command to see if we can see the files we created.

      ftp> dir
      200 PORT command successful.
      125 Data connection already open; Transfer starting.
      05-22-16  08:39PM       <DIR>          images
      05-22-16  07:41PM       <DIR>          snapins
      05-24-16  02:42PM       <DIR>          tftpboot
      226 Transfer complete.
      ftp: 144 bytes received in 0.00Seconds 144000.00Kbytes/sec.
      quit
      

      That completes the FTP test

      The next step is to test the tftp server

      C:\>tftp 192.168.1.205 get default.ipxe
      Transfer successful: 427 bytes in 1 second, 427 bytes/s
      

      If your tests matches the above then we can move onto the FOG part of the setup.

      My dev environment was created fresh with the latest trunk version of FOG 1.2.0. The following is the complete steps I went through to setup FOG to communicate with the windows storage node.

      Fog Configuration -> Plugin System
      FOG_PLUGINSYS_ENABLED = checked

      Plugin Managment
      Activate and install Location management plugin

      Storage Management -> Add Storage node
      Name: WinStoreNode
      IP Address: 192.168.1.205
      Web Root: /fog
      Max Clients: 10
      Is Master Node: (unchecked)
      Replication Bandwidth: 0
      Storage Group: default
      Image Path: /images
      FTP Path: /images
      Snapin Path: /snapins
      SSL Path: /snapins/ssl
      Bitrate: (blank)
      Interface: eth0
      Is Enabled: (checked)
      Is Graph enabled: (unchecked)
      Managment Username: fog_user
      Managment Password: mi5ty_cl0ud

      Location Managment -> Create New Location
      Location Name: winsn
      Storage Group: Default
      Storage Node: WinStoreNode
      Use inits and kernels from this node: (checked)
      Press the Add button

      I next copied a host image from my production server to the dev environment. Once all of the files were in place, I went back to the FOG GUI and added an Image reference that defined the image I copied over from my production server.

      And finally I restarted the FOGImageReplication service. Inspecting the /opt/fog/log directory you should see the replication service start up with a transfer log specifically for the windows storage node we just created (i.e. fogreplicator.log.transfer.WinStoreNode.log). If you see this long file, hop over to your windows storage node and inspect the directory c:\share\images to see if the image files have started to copy over from the FOG server.

      posted in Tutorials
      george1421G
      george1421
    • RE: Image replication bucle

      @Malarky Ah ok.

      Now to the issue. The Master Node (fog server) sends to images to the storage node via the ftp protocol. Ensure you have no firewall between the master node and storage node. (check #1)

      The Master Node logs into the storage node using the linux (fog user and password). Note this is NOT the fog user account related to the WebGUI, but the linux fog user. These account settings should be listed in the storage node settings for the server “storageSub”. Confirm (from the Master Node linux console) you can use the ftp command to connect to the storage node and log in with the user ID and Password defined on the storage node configuration page. (sorry for all the words on this check, I needed to explain what is going on under the hood of the FOG car).

      posted in FOG Problems
      george1421G
      george1421
    • RE: No network interfaces found | Dell PowerEdge R650 | Intel E810-XXV

      Don’t worry about understanding this next part, these are notes on the hardware I need.

      [8086:159b] “Ethernet Controller E810-XXV for SFP” first appeared in linux kernel 5.7.x, not currently included in FOS Linux kernel. One off kernel required.

      Kernel config parameter: CONFIG_ICE

      Firmware says ice director firmware for (something) for intex/ice/ddp/ice.pkg failed with error -2 [hint needs firmware]

      raid controller is LSI SAS39xx [1000:10e2] lsblk sees 7 disks in non-raid format or software raid.

      **It looks promising to build a custom kernel for this hardware.

      posted in Hardware Compatibility
      george1421G
      george1421
    • RE: Windows server as FOG Storage Node - proof of concept blog

      Part 3 (Final)

      Today I went in and registered one of my VMs on the dev fog server. I ran through the full registration and allocated this host to the “winsn” location.

      I pxe booted the vm and saw that it initially connected to the dev fog server and then the dev fog server redirected the client to pull the bzImage and init.xz from the Windows storage node (!!getting excited level 20% !!).

      The vm downloaded both bzImage and the init from the windows storage node cleanly (excitement level 50%).

      I saw the FOS kernel boot and started the initial prep work for imaging (excitement level 80%).

      Partclone did its prep work and started downloading the image (excitement level 90%). I quickly checked the windows storage node and ran netstat -an and this was the the line I was searching for

      TCP    192.168.1.205:2049     192.168.1.6:747      ESTABLISHED
      

      This told me that the windows storage node was communicating with an external (dhcp) device over the NFS protocol!!

      Imaging completed and the workstation started booting windows (time for a smoke and a beer) [full disclosure I don’t smoke so I’ll just take two beers instead].

      So it IS possible to setup a FOG / MS Windows Storage node. In the end I’m still not seeing the value in it, but it IS DOABLE.

      !!Success!! and the end of this POC project…

      posted in Tutorials
      george1421G
      george1421
    • RE: Is there any way to prevent FOG from automatically overwriting images

      You can protect the image once it has been captured. Just go into the image and pick the check box label Protected.

      Also side note, you might want to consider upgrading to 1.3.0 or the 1.3.1-RC branch since you are about 15 revisions behind. Outside of that the protected option has been in the software since the early 1.2.0-trunk versions.

      posted in FOG Problems
      george1421G
      george1421
    • RE: aQuantia AQtion PXE Compatability?

      @madnm We do have an alternative to pxe booting into ipxe. We can usb boot into the FOS Engine bypassing iPXE. It would be interesting to see if FOS Linux could talk to that network adapter.

      posted in Hardware Compatibility
      george1421G
      george1421
    • Building USB Booting FOS Image

      Part 1

      The idea for this solution is to build a usb bootable FOS client that will handle the basics of imaging from target registration, suitability checking, debugging, and image capture and deployment.

      This solution is only mean to replace pxe booting where the target can’t pxe boot effectcivly or the network adapter is not supported by the firmware for pxe booting such as with uefi firmware and a usb 2.0 network adapter. The only caveat here is the network adapter MUST be supported by the FOS linux kernel. The usb bootable FOS client also should remove any incompatibilities we’ve seen with the iPXE kernel and and the hardware.

      The USB FOS Client creation must be done on a linux computer. The operating system doesn’t matter much. What ever the FOG Server supports these instructions should work on. The only caveat here is that what ever operating system you use, the OS must use GRUB as the boot loader. I can say for both Centos and Ubuntu that grub is already installed and used.

      The working solution for this solution is based on the work creating the FOSL (FOS Live) usb boot debugging tutorial https://forums.fogproject.org/topic/6532/usb-boot-target-device-into-fog-os-live-fosl-for-debugging and the support of Tom (senior developer) with his quick updates to the trunk build that tied all of the bits together nicely. That brings up the point that this FOS USB Boot drive will only work on/with trunk builds post r8050. If you have an older trunk build than 8050 you must update to get the supporting environment.

      If you are interested in the development process of this product you can review this link: https://forums.fogproject.org/topic/7656/pxe-less-booting-fos-client-os

      Now lets get down to business in Part 2

      posted in Tutorials
      george1421G
      george1421
    • RE: My images not listed after move to 1.3

      It depends on how you moved this images to the new server.

      If you just copied them from the /images of your old FOG server to the /images of your new FOG server then I understand what is wrong. Your physical files are in place, but the database does not know your files are there. The easiest thing to do is call up the old fog server and new fog server and then manually copy and paste the image definitions between the old fog server and the new fog server. With fog 1.3.0 you can export these definitions and import them into the new fog 1.3.0 server right from the management gui.

      posted in FOG Problems
      george1421G
      george1421
    • RE: No network interface found..Lenovo ThinkCentre M70s

      @goll420 yes there is

      Official FOG kernel and inits (FOS) are on github:
      https://github.com/FOGProject/fos/releases

      Download bzImage and bzImage32 to a usb drive and then take them to the FOG server. Rename the files in /var/www/html/fog/service/ipxe directory to .old and then copy these new files over. You can confirm the version of the kernel files by issuing this command from the fog server linux console file /var/www/html/fog/service/ipxe/bzImage it will tell you the kernel version in the text. Make sure you pay attention to case, because it is important with linux.

      posted in Hardware Compatibility
      george1421G
      george1421
    • RE: Building USB Booting FOS Image

      Part 2b

      These steps and script works correctly on a Cento 7 system.

      1. For Centos 7 you must install the following packages
        yum install dosfstools parted kpartx grub2-install grub2-efi-modules grub2-efi -y
      2. Centos 7 is a x64 only OS so if you have a i386 uefi system you MUST USE either Centos 6 or Ubuntu 14.04 LTS to build a usb boot drive that supports i386-efi systems. This is not a big issue because there are not many systems that are both IA32 and efi only.
      3. The second thing to note about Centos 7 it uses grub2 instead of grub (version 1). So the script commands have changed a little.
      4. For Centos 7 paste the following script into mk.fos-usb
      #!/bin/bash
      
      if [ -f /tmp/fogkern.img ]; then
          echo Nuking old FOG Debug image
          rm -f /tmp/fos-usb.img
      fi
      
      echo Make a blank 150MB disk image
      dd if=/dev/zero of=/tmp/fos-usb.img bs=1M count=150
       
      echo Make the partition table, partition and set it bootable.
      parted --script /tmp/fos-usb.img mklabel msdos mkpart p fat32 1 128 set 1 boot on
       
      echo Map the partitions from the image file
      kpartx -a -s /tmp/fos-usb.img
      LOOPDEV=$(losetup -a | grep "/tmp/fos-usb.img" | grep -o "loop[0-9]*")
       
      echo Make an vfat filesystem on the first partition.
      mkfs -t vfat -n GRUB /dev/mapper/${LOOPDEV}p1
       
      echo Mount the filesystem via loopback
      mount /dev/mapper/${LOOPDEV}p1 /mnt
      
      echo Install GRUB
      grub2-install --removable --no-nvram --efi-directory=/mnt --boot-directory=/mnt/boot --target=x86_64-efi
      grub2-install --removable --no-floppy --boot-directory=/mnt/boot --target=i386-pc /dev/${LOOPDEV}
      
      echo Download the FOG kernels and inits
      wget -P /mnt/boot/ https://github.com/FOGProject/fos/releases/latest/download/bzImage
      wget -P /mnt/boot/ https://github.com/FOGProject/fos/releases/latest/download/bzImage32
      wget -P /mnt/boot/ https://github.com/FOGProject/fos/releases/latest/download/init.xz
      wget -P /mnt/boot/ https://github.com/FOGProject/fos/releases/latest/download/init_32.xz
      wget -P /mnt/boot/ https://github.com/FOGProject/fogproject/blob/dev-branch/packages/tftp/ipxe.krn
      wget -P /mnt/boot/ https://github.com/FOGProject/fogproject/blob/dev-branch/packages/tftp/ipxe.efi
      
      echo Create the grub configuration file
      cat > /mnt/boot/grub2/grub.cfg << 'EOF'
      
      set myfogip=http://192.168.1.100
      set myimage=/boot/bzImage
      set myinits=/boot/init.xz
      set myloglevel=4
      set timeout=-1
      insmod all_video
      
      menuentry "1. FOG Image Deploy/Capture" {
       echo loading the kernel
       linux  $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4
       echo loading the virtual hard drive
       initrd $myinits
       echo booting kernel...
      }
      
      menuentry "2. Perform Full Host Registration and Inventory" {
       echo loading the kernel
       linux  $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=manreg
       echo loading the virtual hard drive
       initrd $myinits
       echo booting kernel...
      }
      
      menuentry "3. Quick Registration and Inventory" {
       echo loading the kernel
       linux  $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=autoreg
       echo loading the virtual hard drive
       initrd $myinits
       echo booting kernel...
      }
      
      menuentry "4. Client System Information (Compatibility)" {
       echo loading the kernel
       linux  $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=sysinfo
       echo loading the virtual hard drive
       initrd $myinits
       echo booting kernel...
      }
      
      menuentry "5. Run Memtest86+" {
       linux /boot/memdisk iso raw
       initrd /boot/memtest.bin
      }
      
      menuentry "6. FOG Debug Kernel" {
       echo loading the kernel
       linux  $myimage loglevel=7 init=/sbin/init root=/dev/ram0 rw ramdisk_size=275000 keymap= boottype=usb consoleblank=0 rootfstype=ext4 isdebug=yes
       echo loading the virtual hard drive
       initrd $myinits
       echo booting kernel...
      }
      
      menuentry "7. FOG iPXE Jumpstart BIOS" {
       echo loading the kernel
       linux16  /boot/ipxe.krn
       echo booting iPXE...
      }
      
      menuentry "8. FOG iPXE Jumpstart EFI" {
       echo chain loading the kernel
       insmod chain 
       chainloader /boot/ipxe.efi
       echo booting iPXE-efi...
      }
      
      EOF
       
      echo Unmount the loopback
      umount /mnt
       
      echo Unmap the image
      kpartx -d /tmp/fos-usb.img
       
      # Write the file to flash drive
      # sudo dd bs=1M if=/tmp/fos-usb.img of=/dev/sdX
      

      For the rest of the build follow the Part 2a build.

      posted in Tutorials
      george1421G
      george1421
    • RE: Unable to upload images

      @Doctrg The question is, can (from a windows machine or another linux server) you connect to the FOG server using a ftp client with the user ID and password listed in the storage node configuration.

      The issue is there is a linux user called fog that is different than the webgui admin user called fog. What we’ve seen is the linux user fog’s password gets out of sync with what is displayed in the master storage node configuration.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Lenovo ThinkPad P15

      @austinjt01 Ok this is still in the ipxe realm. So did you try to change your boot loader from ipxe.efi to snponly.efi? Did that help?

      posted in Hardware Compatibility
      george1421G
      george1421
    • RE: The magical, mystical FOG post download script

      Part 7 Tying it all together

      At this point we need to insert the call to our custom bash script into the FOG task sequence. Please do the following:

      1. After your script has been fully debugged we need to tell the fog post install script to call our script. With your favorite text editor edit /images/postdownloadscripts/fog.postdownload and at the end of the script insert . ${postdownpath}fog.postexamp
        It is important you include the dot prefix a space and then the full path to your post install script. While that lonely dot seems to be out of place, it tells the bash shell something important that we need. It tell the bash shell process to include the environment (bash variables) from the calling script to the called script. I’ll say this again, its important for our bash script to know about the variables the fog developers created for their scripts to run. We will use some of these variables in our example scripts.
      2. After you have added the call to our example bash script save and exit out of the fog.postdownload script.

      Thats it, the FOG install sequence will call the fog.postdownload after the image is on the workstation. The fog.postdownload will call our custom application and then return back to the FOG install sequence to finish up the house keeping functions.

      posted in Tutorials
      george1421G
      george1421
    • RE: Could not boot: No such device

      @abos_systemax said in Could not boot: No such device:

      FOG iPXE menu loads; but all the options are not working

      What iPXE kernel as you sending to the target computer (dhcp option 67)?

      Just to be clear, the iPXE menu is detecting an IP address and the part that is failing to get an IP address/detect the MAC address is the FOS Engine (the customized linux OS that captures and deploys images on the target)?

      Have you tested the ipxe7156.efi ipxe kernel to see if you have better success with that boot image.

      We have see similar issues with lenovos with faulty uefi firmware. It will load bzImage and the init.xz but fail to launch the bzImage kernel. This was traced to fault firmware. You might want to check to see if you have the latest firmware on this asus.

      Sorry about being all over the place on this, but its not clear why its failing yet. A clear image taken with a mobile may give better clues too.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Problem With Network Card Realtek RTL8168/8111

      @fagner-patricio OK so you have the latest version of the kernel. So lets debug a bit more.

      Manually register this computer with FOG. You will need the mac address of the network adapter. You will create a host definition file with this action. Connect the host to an image (doesn’t matter which one at the moment as long as it exists).

      Now schedule a deployment task to this computer. But before you hit the schedule task button, tick the debug checkbox. Now schedule the deployment task.

      PXE boot the target computer. The computer should go right into imaging and not stop at the fog iPXE menu. After a few screens of text that you have to clear with the enter key you will be dropped to the FOS Linux command prompt on the target computer. NOTE: You will probably see the same errors as before, but in debug mode it should let you get to the command prompt.

      Now at the FOS Linux command prompt key in the following.

      ip a s
      lspci -nn | grep -i net
      grep -i firm /var/log/syslog

      Snap a clear picture of the output and we will decide the next steps.

      posted in Hardware Compatibility
      george1421G
      george1421
    • RE: The magical, mystical FOG post download script

      (place holder)

      posted in Tutorials
      george1421G
      george1421
    • 1 / 1