Topics created by darkxeno

@darkxeno Ok you need to ensure that kernel support uefi computers. The could not boot exec format could indicate the kernel doesn’t support uefi.

As for the top post with the iso, that would use memdisk and memdisk only supports bios based computer. I uefi system will throw an error if you try to use memdisk on uefi.

Also try the alternate ipxe syntax I provided.

Lastly on the iso image you have see if there are the uefi directories on that media. /EFI and or /boot

It seems possible to do as a plugin. I’m not suggesting that it be approved or denied only that its possible. It will require the fog admin to acquire an API key from Dell.
As for the additional fields someone would have to write a custom plugin to extend FOG.

ref: https://gist.github.com/teroka/0720274b87b77fe7171f
ref: https://www.apajove.com/knowledge-base/dell-v5-warranty-api/
re: https://van-gelderen.eu/getting-dell-warranty-info-in-powershell/

@Sebastian-Roth I understand than I was racing my brain on this lol

@george1421 thanks for the info I’ll get that done Monday and I’ll left you know what we find

@darkxeno In the dell firmware switch the disk controller from Raid-on to AHCI mode. Unless you have more than one disk connected in a raid configuration raid-on mode doesn’t help you. There is a document issues between linux and intel controllers in raid-on mode. Once you have imaged with fog you can switch back to raid-on mode or leave it in ahci mode. It doesn’t matter to windows.

thanks man

@Tom-Elliott I seemed to recall this same exact issue in another thread. I’m pretty sure this was the solution then too. I could not find that thread for the life of me, but I know we did see this issue before. As FOG turns 1.3.0 we should get this documented somewhere in a faq that users can find easily.

@darkxeno I see the problem.

You appear to have a node named Downtown, which lists before default. Because downtown is NOT the master of the Downtown group, it is unable to display. I will see about adding a better bit of error checking and have it out put the information regardless of if it’s there is a master or not. The problem is, without a master, you do not have access to upload images to that group/node.

@Tom-Elliott said:

Can you try reupdating your kernels/ and/or re-running the install if you’re running dev version? I’ve updated the kernels to simply remove the qmi_wwan drivers from the mix. From my reading this should essentially keep the GOBI card from loading with the FOG inits.

Hi
same problem for me
using the kernel 4.2.0 of September 14, 2015 doesnt change
When i’m doing a quick registration and inventory (or quick image) it loops on starting wwan0 interface
Any ideas ?

@Wayne-Workman; Hi Wayne. Just installed Kabuntu 14.04 LTS and it worked perfectly. So for my immediate needs, I think I’ll be good to go. On the Mageia side, apparently this issue started in the previous release 4. I looked at the mysql 127.0.0.1 vs localhost issue and sure enough there was a host resolve problem. So #mysql -u root -h 127.0.0.1 -P 3306 would refuse, but #mysql -u root -h localhost -P 3306 worked. So I added the line: ‘bind-address = 0.0.0.0’ to /etc/my.cnf below the ‘skip-networking’ line.
That seemed to let everything in sql work without passwords. That got rid if all of the mysqli error message in the apache error_log. However, It’s still not creating the ‘fog’ database and I have the same blank webpage.
It doesn’t appear to be throwing any exceptions even though the database is never created. So I’m still at a loss. What user is being used for mysql? Is it the ‘fog’ user?

thanks Tom

Just so everyone’s aware I fix this bug in SVN in case anybody doesn’t want to delete their location stuff but still want a functional fog system

Edit your /opt/fog/.fogsettings setting the snmysqluser to root, snmysqlpass to the mysqlpass you set at install time (or just two double quotes if you left it blank) and snmysqlhost to localhost.

For future readers: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

It appears that a reinstall of FOG fixed the issue reported. Please try this first.

I will try that tom and i broke it up for easier reading as well

I wiped and reloaded with Unbuntu 13.04 and have not had any issues at all

i guess it won’t work well

[url]http://www.facebook.com/m2tsconverter[/url]

[media=youtube]Fdoo7yfvKK4[/media]