Asus X200M
-
Hello,
I have an Asus X200M that I cannot get to communicate with my FOG server. I have gone into the BIOS and disabled Secure Boot. I then Enabled CSM and Network Stack Configuration. On my Asus X200L it then gives me the option to enable “Launch PXE OpROM Policy” This option doesn’t appear in the X200M and leaves me the only network boot option as UEFI: IP4 Realtek PCIe FE family controller. When I try to PXE boot from this it states NBF file loaded successfully, then reboots to the Hard Drive. Please help.
Thank you
-
I guess you use ‘undionly.kpxe’ for all your clients. This iPXE-binary is not capable of booting (U)EFI machines. Try downloading this binary, put it into /tftpboot and change your DHCP-Server config to point to this binary… Does it work? If it does you’ll have to look into so called DHCP user-classes to make this work for your different clients. Let us know if you need assistence with that.
-
Hello,
Thank you for your quick response. When you say “try downloading this binary” was there supposed to link. I’m not sure I follow.
Thank you again
-
You could try the ipxe.efi file already provided in the folder. To make you life a little easier if highly recommend trying svn 3072
-
I will try it and let you know. Thank you so much for your help!
-
Sorry mate, somehow I must have missed to paste the link! My fault! I meant download this: [url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ipxe.efi[/url]
-
No Worries I appreciate all the help. I downloaded the file but I cannot add that file to the tftpboot directory as it states I don’t have permission. It is owned by the user FOG. I have tried using command lines to add the file to no avail. Is there a secret to this or am I just simply missing something? Thanks again.
-
The /tftpboot folder is owned by fog, but should be able to be written by the user “root”.
My guess is you’re logged in under another username (example: Shock2k15) rather than logged into the FOG Server as the user fog or root.
-
Unfortunately i inherited this server and didn’t build it myself. I am logged in under the user “Fogadmin” I can’t seem to access the user “Fog”
Is there normally a default password? I will keep trying. Worst case I guess I just completely rebuild the server. -
Seeing as you can log into the FOG Gui, to find the “FOG” user’s password, goto StorageManagement->YourStorageNode->ManagementPassword
-
AWESOME! I’m in. Sorry I’m a newb. I Can’t thank you guys enough
-
Hi again, could you please walk me trough how to change the DHCP-Server config to point to this binary. I tried researching this but was unsure if what I was looking at was correct. This a VM if that helps.
Thank you
-
In your case it would be easier to just rename the files. Please make sure you don’t delete or overwrite any files. I won’t be liable in case anything goes wrong here! Think twice before you copy paste this commands…
[CODE]cd /tftpboot
mv undionly.kpxe undionly.kpxe.orig
mv ipxe.efi undionly.kpxe[/CODE]Try booting your client. If that works we know that this binary is working for you. We then can go ahead and configure things properly…
-
I took a snap shot of the server last week so we are good. We are definitely making progress as it will now load the fog screen. Sort of. It doesn’t provide the graphics and is just a blue screen with white letters. It still allows me to select register host but when I do I get an error:
Kernal Panic - not syncing: VFS: Unable to Mount root fs on unkown-block(1,0)
Kernal Offset: 0x0 from 0xffffffff81000000 (relocation range: oxffffffff800000000-0xffffffff9ffffffff)
—{ end Kernal panic - not syncing: VFS: Unable to mount root fs on unkown block(1,0)Hope this is useful information. Please let me know how to proceed.
Thank you,
Matt
-
This message is normally seen when you have a cross platform file being loaded.
This means, you have a: 32 bit kernel trying to load on a 64 bit init, or a 64 bit kernel trying to load on a 32 bit init.
Did you make customizations to the kernel files? For example, did you download a new kernel under the plain (x86) but name it as bzImage?
-
Not that I am aware of. I know the previous person installed a undionly.kpxe.INTEL file. Is there a way for me to find out if they are 32 bit or 64 bit?
Thanks,
-
[quote=“Shock2k15, post: 43482, member: 28829”]Kernal Panic - not syncing: VFS: Unable to Mount root fs on unkown-block(1,0)
Kernal Offset: 0x0 from 0xffffffff81000000 (relocation range: oxffffffff800000000-0xffffffff9ffffffff)
—{ end Kernal panic - not syncing: VFS: Unable to mount root fs on unkown block(1,0)[/quote]For me this error also sounds like the initrd issue on mac os x… see here: [url]http://fogproject.org/forum/threads/mac-support.11033/page-2#post-34584[/url]
-
When I try to update the kernal using [url]http://fogproject.org/wiki/index.php/FAQ[/url] i get “bash: FOGWEBDIR: No such file or directory” when I run the 1st command. I’m running FOG_1.2.0. I checked the link but the information is not very detailed as far was what needs to be done. I may just not be understanding. Thank you for your patience.
-
FOGWEBDIR is just a placeholder in this case. If you did not modify it when installing the system it should be like this:
[CODE]cd /var/www/fog/service/ipxe
…[/CODE]
And same again with <CURRDATE>. Just a placeholder. For example use 20150309 instead… -
Ok I figured out how to update the Kernal through the web interface. I have tried several different kernals. Basically the same result. If I select the newest unofficial kernal it just comes back to the “Host is not registered” screen after I select Quick Registration. With the kernal you provided I get the error previously listed. The screen that comes up to register your host is blue with white writing and has a solid blank line over the selected field. Please let me know if there is anything else I can provide that may help you troubleshoot this issue.
Thank you
