@ziolucione Well there are 2 options,
- Use the Grub menu and pick one of the registration options (2 or 3 if I remember correctly)
- Go into the web ui and in host management and create a new host. Key in the proper values and the mac address you collected from the target computer during the debug session.
Either way will work.
Hi, I have reconfigured the FOG server to use wifi.
How can I register the MAC address manually?
Option 2 in the FOS menu list?
@george1421 from the wifi network I cannot reach the wired one. So, because FOG server is on the wired one, I have to revert back the FOG server to use the wifi. They are on 2 different subnets with no network rules between them.
I have to change the FOG configuration to use the wifi
I don’t understand this, you shouldn’t have to do anything with the FOG Server end for wifi since the target computer is the only bits using wifi to connect to your network infrastructure. I want to make sure we are on the same page when setting this up.
@george1421 Alright, I have to change the FOG configuration to use the wifi instead of ethernet. I’ll keep you posted.
@ziolucione Ok now lets take baby steps.
Manually register the mac address of the wifi adapter with FOG
ip link showwill get you the mac addresses. Once the target computer is registered create a image definition to capture the tablet to (we are only interested to see if we can capture the image, we don’t care about the image). Assign that image to the target computer. Then schedule a capture task in FOG. Now reboot the tablet and pick option 1 in the grub menu. Hopefully the target computer will start capturing the image and completes fully. IF that works then we can discuss the load and go steps since we don’t have iPXE to help us use the standard method.
@george1421 Thanks, I have the wireless adapter wlp1s0 (and I believe I have also an IP address now)
Download this to the usb stick replacing bzImageWiFi on the flash drive.
@ziolucione OK great that is what I needed iwlwifi-7265D
@ziolucione In case you don’t know how to use vi (very basic and cryptic text editor to look at messages file)
the key sequence is very cryptic but key in the following
/ no suitable firmware foundand press enter. It should jump you down to the line where the firmware isn’t found. If it doesn’t get the line with iwlwifi in it (the name of the intel driver) hit
/and press enter again it will jump to the next occurrence. Take a screen shot of where its says the proper firmware needed. Then to exit the vi editor hit
guys sorry for the quality :D
@ziolucione In the section picture, The lines we need to investigate in the log file have minimum version required iwlwifif-7 (can’t see the rest). This should be the area in the log file that describes what went wrong.
Also post what sebastian posted with a twist.
lspci -nn |grep -i net
@george1421 Hi, I was looking into it.
@ziolucione While you are on the CLI please run the following commands, take pictures (!) and post her:
lspci -nn dmesg | grep -i -e eth -e wifi -e 80211
@ziolucione As I mentioned in the debugging steps, you need to review the /var/log/messages file. You should see where it loads the network drivers after it loads the intel network drivers there probably will be a mention of needing specific firmware. When I get to work, I’ll boot the image on a different dell computer that’s missing the firmware to show you exactly what I’m looking for, but we are pretty close to a solution now.
@george1421 Hi guys,
I have tried this new image and I have no more errors, I have reached the CLI, but no network device is found. :(
@ziolucione Well lets start with this image: https://drive.google.com/open?id=1trOHt0B3X1SUYTVczYxs1TI3qQWC06Sy
This is a usb boot image that has been adjusted for wifi. Download the image and then “burn” to a usb flash drive using RUFUS like the previous one you did. Edit the /boot/grub/grub.cnf file as before setting your fog server’s ip address as well as ssid (wireless name) and ssidpw (wifi password) values. Save the grub config file then usb boot into the grub menu. Select option 6 (debug) and then boot to the fos linux comand prompt. If you see it mentioning the wireless lan adapter name (in my test case it was wlp2s0) during the startup process then we have some luck.
When you get to the command prompt key in
ip addr show. Hopefully you will have an ip address for your wireless adapter. If not, then we need to debug a bit more.
For debugging we need to review the file /var/log/messages, near the middle of the file should be the code where it loads the wifi driver (in the case of the intel adapters the drivers should start with il). If you look just past that section you may see something about firmware for the wireless adapter and it needed a specific version of firmware, I need to know that specific version of firmware. I should have it loaded in the kernel already but your network adapter is an intel 3165 and I only found the firmware for the 3160 model so I loaded that hoping the base model is 3160. The messages file will tell us what the network adapter needs.
I’ve tested this image on a Dell 7240 and a e6230 and it works correctly on my home wifi that uses wpa2 for security. The boot image is not complete, but if this part doesn’t work then the rest is of no value.
Just wondering if this is a RAMDISk size issue as well?
Possible depending on the config file settings. Once I have it perfected I’ll create a FOS boot image of it so the settings are right.
@Sebastian-Roth Hi Sebastian,
I have pulled the master branch from Git.
Thank you @george1421