Asus EEE PC Imaging Errors
-
I t should be a standard defaults install. Where can i check this and/or change it. Is it inside the tftp info?
-
@EAHarvey For most people, it’s their DHCP option 067.
For some people, it’s their dnsmasq ltsp.conf file and the corresponding symbolic link.
just depends on how you have fog set up.
See this article for more info: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP
There is stuff in there about DHCP and a link for dnsmasq. You will only have one or the other, not both.
-
@Wayne-Workman Quick question, So do i need to run the SVN up or the git pull each day to update? or do i just use one or the other?
-
@EAHarvey said:
@Wayne-Workman Quick question, So do i need to run the SVN up or the git pull each day to update? or do i just use one or the other?
Neither.
I would never recommend updating everyday to anyone unless you just want to be the best FOG Beta tester that we’ve ever seen lol.
Most times, I tell people to update when there is a need. Be that need a feature, a bug fix, support for hardware, etc. And with using FOG Trunk, you will find needs occasionally.
SVN and GIT are simply two different methods to get the Same Thing. It makes no sense to use both at the same time.
-
@Wayne-Workman Roger that, thats what i was thinking but i wanted to ask the experts.
-
So new error I have found. Just wanted you guys to be aware. So the Asus EEE PC that i have been having trouble will eventually not time out and get the pxe image and boot all the way into fog and work. It seems to take multiple;e reboots and/or attempts to connect to the server then it goes right through., Not sure if maybe it’s some type of delay but i’m looking into it and trying to figure out what exactly is going on.
-
@EAHarvey said:
So new error I have found. Just wanted you guys to be aware. So the Asus EEE PC that i have been having trouble will eventually not time out and get the pxe image and boot all the way into fog and work. It seems to take multiple;e reboots and/or attempts to connect to the server then it goes right through., Not sure if maybe it’s some type of delay but i’m looking into it and trying to figure out what exactly is going on.
Do you have Dual DHCP ?
Can you look for a potential IP conflict issue with the client and the fog server?
-
@Wayne-Workman the ip of the server is 172.29.2.250 and DHCP is giving an address of .2.25 so seems ok as duplicate addresses. I have dual NICS in the machine. One is my FOG network and the other is standard 192.x.x.x ATT network. I wonder if for some reason it’s trying to grab DHCP from the ATT? If it was though, you would think it would be a issue with all the machines and not just these netbooks. Food for thought.
-
@EAHarvey said:
@Wayne-Workman the ip of the server is 172.29.2.250 and DHCP is giving an address of .2.25 so seems ok as duplicate addresses. I have dual NICS in the machine. One is my FOG network and the other is standard 192.x.x.x ATT network. I wonder if for some reason it’s trying to grab DHCP from the ATT? If it was though, you would think it would be a issue with all the machines and not just these netbooks. Food for thought.
To clarify, your FOG server has two NICs? The netbooks only have one, right?
-
@Wayne-Workman Yes that is correct.
-
@EAHarvey have you changed the bootfile to undionly.kkpxe as suggested?
-
@Wayne-Workman Was that changing the 0.0.0.0:67 or 69 and trying it? If that is waht you mean then yes i have tried on each setting.
-
@EAHarvey Nope. This is done in your DHCP settings (usually).
-
@Wayne-Workman Ok let me double check…
-
@Wayne-Workman Yes both of my servers are set to filename “undionly.kpxe”;.
-
@EAHarvey We are suggesting that you change them to undionly.kkpxe
Note the extension.
-
@Wayne-Workman oh crap. lol my bad. checking now.
-
@EAHarvey Ok that worked like a champ. I did a little digging and found out that the kkpxe allows the machine to use its Manufacturer. Booted straight up when i did that. Going to do some more testing but it’s looking good. I should have my backup machine finished today or tomorrow.
-
@EAHarvey So is there a way to have a debug in place in 1.2 so i can see why my uploads for a single disk are erroring out and rebooting?
-
@EAHarvey Yeah but it’s not really user friendly or easily implemented… If you want to debug, I’d suggest moving to FOG Trunk. It’s built right into the deployment window as you see below:
Here are instructions and information on FOG Trunk, I suggest you read through it before you buy.
https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
