Latest FOG 0.33b
-
Hi Tom,
I have this problem in the inventory of my new computer (Intel NUC) :
[CODE]i8042 not found…[/CODE]
[CODE]
System Manufacturer # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
System Product # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
System Version # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
System Serial Number # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
System Type Type: Desktop
BIOS Vendor # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. Intel Corp.
BIOS Version # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. WYLPT10H.86A.0025.2014.0303.1008
BIOS Date # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. 03/03/2014
Motherboard Manufacturer # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. Intel Corporation
Motherboard Product Name # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. D54250WYK
Motherboard Version # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. H13922-303
Motherboard Serial Number # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. GEWY40300HP7
Motherboard Asset Tag # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
CPU Manufacturer # SMBIOS implementations newer than version 2.7 are not fully supported by this of dmidecode. Intel
Corp.
CPU Version # SMBIOS implementations newer than version 2.7 are not fully supported by this of dmidecode. Intel Core
i5-4250U CPU @ 1.30GHz
CPU Normal Speed Current Speed: 1300 MHz
CPU Max Speed ${cpu_mspeed}
Memory 7.73 GB
Hard Disk Model
Hard Disk Firmware
Hard Disk Serial Number
Chassis Manufacturer # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
Chassis Version
Chassis Serial # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
Chassis Asset # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode.
[/CODE] -
Okay.
What does this mean?
-
I’m already running the latest version of dmidecode in the init files so there’s nothing I can really do at the moment.
I’m sorry.
-
Warp,
If you want you can update to r1436.
I’ve changed the version relationship, though I don’t know how far it will actually work. It’s just a theory.
All,
r1436 released. Just addes a patch for the dmidecode file to change the versioning needs.
-
I concur, it does appear to be a problem in VirtualBox only. The adapter is being kept by the VirtualBox Manager process, which, if you leave running for long enough, will crash and reset. Thank you for looking at this.
I do have another potential issue for you. This one is to do with uploading an image. I have created a new Image on the server, given it a name and OS type (Linux). I then created a task for my Host so that an Image would be taken from the Host (a Debian VM) and uploaded to the server. On PXE boot the task begins, an image is taken, but it is never uploaded to the server (I get the attached error on the host).
[ATTACH=full]644[/ATTACH][ATTACH=full]645[/ATTACH][ATTACH]644[/ATTACH][ATTACH]645[/ATTACH]
[url=“/_imported_xf_attachments/0/644_Error.png?:”]Error.png[/url][url=“/_imported_xf_attachments/0/645_Error.png?:”]Error.png[/url]
-
I have tested fog rev 1435 and got the same problem in virtualbox and on a real pc.
-
r1437 should fix the Tasks’ issue you all were seeing. Many changes had to be made, all relatively minor though. Just so the new fields get appropriated properly.
-
r1439 released.
Move to post variables for the boot url’s. Adds checking for the architecture type. If the arch is set as i386, it will set the init.xz to init_32.xz and use bzImage32. May make a database entry adding 32 bit kernel/init.xz options for dynamics, for right now they’re hard coded. Kernel only gets set if the Host does not have a kernel set in it.
-
[quote=“Tom Elliott, post: 25110, member: 7271”]r1439 released.
Move to post variables for the boot url’s. Adds checking for the architecture type. If the arch is set as i386, it will set the init.xz to init_32.xz and use bzImage32. May make a database entry adding 32 bit kernel/init.xz options for dynamics, for right now they’re hard coded. Kernel only gets set if the Host does not have a kernel set in it.[/quote]
I am sad I can only like this once, I think this is an invaluable feature, thank you!
-
Just giving credit where credit is due,
Wolfbane8653 was the one who suggested the use of architecture checking. I completely forgot that was a command available to iPXE so thank you very much Wolfbane for the recommendation and command sequence needed to get it working.
-
r1440 released.
Fixes the default.ipxe file creation so it set’s to the new post stuff as well on update/install.
-
r1441 released.
Addes the two fields to the TFTP Server setting for 32 bit kernel and init setting. Updates the BootMenu to use these settings.
-
r1443 released.
FOG Settings categories are now expandable/collapsable elements.
-
r1445 released.
Fixes an issue where the forms weren’t being updated appropriately. SORRY guys.
-
r1446 released.
Just sets one form element so if you make multiple changes, the changes take effect on all elements you’ve changed.
-
r1448 released.
Sets the FOG Settings so the categories are no longer underlined. The div slides out underneath it as well.
Thank you,
-
Hello,
about The fog client in 0.33 does it work ?
Thanks!!
-
[quote=“lepretre, post: 25176, member: 3202”]Hello,
about The fog client in 0.33 does it work ?
Thanks!![/quote]
You could always install it and find out… It is stable but we are making changes constantly so if you use the SVN there may be problems here and there as we update. But then again you should never be using a Beta for a production environment.
-
I have it installed, It’s working on 0.32 but not and 0.33
I have php warning on the apache fog server.
It’s not a probleme i have the 0.32 and i can leave it running only for the fogclient.I test it in production :oops:where it’s not crucial and i always have a second solution !!(0.32 and clonezilla)
Thanks you very much for the answers!!!
-
The FOG client works fine in 33b… I’ve been using it for months.
You may want to provide more details or post a help thread elsewhere instead of in the release thread so we can troubleshoot and resolve your problem.
