TFTP Boot Issue
-
You can try to use the WEB ui to upgrade the kernel. Or you can download a new bzImage to another folder. backup your original, and then overwrite the bzImage file in /tftpboot/fog/kernel with the new one. You may have to chown/chmod.
-
You can also try my 32 bit kernel:
[code]wget -O /tftpboot/fog/kernel/bzImage http://mastacontrola.com/fogboot/kernel/bzImage32[/code]
-
I am running Ubuntu 12.04 32-bit. I am using Fog 0.32. Yes it was functioning properly until yesterday when I had to shut it down and restarted it this morning. I have not made any changes, it is running on a virtual machine in VMware.
-
Can you please try downloading the kernel I stated above.
Your issue with the “fuzzy” screen is because of the kernel you’re currently using.
-
What is running in VMWare? the FOG server or the client or both? Maybe a VMware hardware version upgrade/change could have affected this. Sometimes VM’s are set to upgrade HW on the next boot cycle.
-
Okay, I installed your kernel and everything appears to be working normal again, it is now getting me to the registration and inventory screen. The one thing I noticed through all of this is that now the bzImage file is back to the config looking file instead of just numbers on a sheet, see below…
BEFORE
[ATTACH=full]1203[/ATTACH]AFTER
[ATTACH=full]1204[/ATTACH]Thanks for the help!!
[url=“/_imported_xf_attachments/1/1203_FOG.gif?:”]FOG.gif[/url][url=“/_imported_xf_attachments/1/1204_FOG1.gif?:”]FOG1.gif[/url]
-
Mine always looks like this
[ATTACH=full]1205[/ATTACH][url=“/_imported_xf_attachments/1/1205_Screen Shot 2014-07-24 at 9.34.33 AM.png?:”]Screen Shot 2014-07-24 at 9.34.33 AM.png[/url]
-
The bzImage is not a config file, but a binary kernel.
The “graphic” display is not necessarily an accurate representation of what the file actually is.
This is why I always prefer cli representations. Another way to test is run the command:
[code]file /tftpboot/fog/kernel/bzImage[/code] -
Try adding kernel argument “nomodeset video=uvsafb:mode_option=1024x768-16”, without quotes
-
While I understand what you’re trying to do, my kernel’s have no uvesab stuff and would not require additional parameters.
-
Good to know…That means “video=uvsafb:mode_option=1024x768-16” would not make any difference, right?
