Suggestion please
-
@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.
-
@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 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
and
lsusb
-
guys sorry for the quality
-
-
@ziolucione In case you don’t know how to use vi (very basic and cryptic text editor to look at messages file)
vi /var/log/messages
the key sequence is very cryptic but key in the following
/ no suitable firmware found
and 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 hitESC
key then:q!
-
@ziolucione OK great that is what I needed iwlwifi-7265D
-
@ziolucione https://drive.google.com/open?id=1OnLxsKRboYoxv3LMcupyZAMDgvkTp-qa
Download this to the usb stick replacing bzImageWiFi on the flash drive.
-
@george1421 Thanks, I have the wireless adapter wlp1s0 (and I believe I have also an IP address now)
-
@ziolucione Ok now lets take baby steps.
Manually register the mac address of the wifi adapter with FOG
ip link show
will 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 Alright, I have to change the FOG configuration to use the wifi instead of ethernet. I’ll keep you posted.
Thanks indeed
Much appreciated.L.
-
@ziolucione said in Suggestion please:
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 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.
-
@george1421
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?Thanks.
L. -
@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.
-
But let me check the patclone option, probably I have made a mistake. I have selected to not use compression.
Rgards.
L. -
@ziolucione What version of FOG are you using?
-
@george1421 From the master branch v1.5.7 I believe.
-
@Sebastian-Roth this init is using the updated init files from github. Looking at the error code, its almost like bash didn’t do the variable expansion. The troubled line in 2071 from the funcs.sh script.
partclone.$fstype -n "Storage Location $storage, Image name $img" -cs $part -O $fifoname -Nf 1 -a0
Was this section of code changed since 1.5.7?
Edit: Looking at the partclone screen again, I see we are getting the command line parameters into partclone because I can see bits of them on the partclone banner. I’m starting to suspect fog server access now. This is also partclone 0.3.12.