Suggestion please
-
Hi @Quazz
I don’t have any PXE boot feature on these tablets, that’s why I am using the FOS built by george. And the issue is related to the MAC address attached to the USB network adapter I am using. So each terminal will be recognized as the previous one and I cannot choose what image to deploy (because it has been registered to use that image the first time I have used the adapter).
That’s why I’d prefer to explore the wifi workflow instead.Thank you for the support.
Regards.
L. -
@ziolucione If there is no task planned for that MAC, it should boot to the FOG menu, no? You’d choose the image to deploy on the tablets themselves if that makes sense.
But if you prefer to handle it from WebUI then the wifi route is the way to go.
-
@Quazz Hi Quazz,
where is this FOG menu entry in the FOS USB linux sub-system?
If I select the first option it is going to capture or deploy, depending on what I have selected form the FOG server UI on that terminal (registered).There is no item listed where I can select the image ID.
Thank you.
L. -
@ziolucione OK here we go with this session…
It appears that the wifi solution is not totally complete. We got it functional but not nice. The OP I was working with at the time had linux skills so I worked on the hard bits and he got it working.
So lets do the hard bits first.
Here is a wifi kernel. I have about a 70% confidence in this kernel build. It seems like each wifi adapter needs its own firmware. Once we identify the firmware I can build it into the kernel. I’ve included the firmware I “think” it needs based on the device number.We will use the FOS Linux boot drive you created previously for this. Here is the kernel https://drive.google.com/open?id=1aQcwnDOSeX14Lz4vDU4eXBGQlzs8UZ18 download that as bzImage and copy that to the usb flash drive replacing bzImage on that drive. Be mindful of the case because it IS important.
As for the virtual hard drive lets start with this one. https://drive.google.com/open?id=13NYcilNuw0bBRpV7OL7nBZZLcrcThUDq download this and save it at init.xz onto the fog server (not in the ipxe path, but some other location. You will need to work on it.)
We are going to use this process: https://wiki.fogproject.org/wiki/index.php/Modifying_the_Init_Image
xz -d init.xz mkdir initdir mount -o loop init initdirNow from here you need to change to
./initdir/etcdirectory and edit the wpa_supplicant file. In that file edit ssid=“ssid_name” change the ssid_name to match your wifi ssid. Edit #psk=“password” remove the preceding # and replace password with your wifi password. Save and exit the file.Now repack the inits. Change back to the base directory where you unpacked the inits.
umount initdir rmdir initdir xz -C crc32 -9 initThat should recreate init.xz file. Move that file to the usb flash drive replacing the existing init.xz on the flash drive.
Now usb boot FOS linux. At the Grub boot menu select option 6 to Debug. After a few screens of text where you need to clear with an enter key, you will be dropped to a linux command prompt. At this prompt key in
ip addr showto see if you picked up an IP address from your network. If you get to this point good or bad, post your results. -
@ziolucione said in Suggestion please:
There is no item listed where I can select the image ID.
This menu item is not present with booting FOS Linux from a flash drive. This is a function of the iPXE menu that we don’t have. Don’t worry, I have a trick for this too, but lets get wifi working first.
-
@george1421 Hi, tried option 6 and I have gotUnable to mount root fs on unknow block
Kernel offset: disabled
Not syncing: VFS: unable to mount root fs on unknow block.No CLI after this, it’s just frozen at this point.
Any thoughts?Regards.
L. -
@ziolucione Please wait for a bit. I’m working out the solution. It appears that I did not save the previous work I did on this so I have to start over again with the virtual hard drive. No worries I should have it done in the next few hours.
-
@ziolucione Which version of FOG do you have installed?
@george1421 Just wondering if this is a RAMDISk size issue as well?
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Sebastian-Roth Hi Sebastian,
I have pulled the master branch from Git.Thank you @george1421
Thanks guys.
Lucio -
@Sebastian-Roth said in Suggestion please:
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.
-
@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.
-
@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.
Regards.
L. -
@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/messagesthe 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 hitESCkey then:q! -
@ziolucione OK great that is what I needed iwlwifi-7265D
image url)
