Asus EEE PC Imaging Errors
-
@EAHarvey https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
I recommend the SVN method. You should fully update your system before doing this, and backup your data beforehand also. There are steps in the article at the bottom for backing up your data.
-
Ahh ok, so this is like the currently developing version of FOG. More like a beta.
-
@EAHarvey Yup. But, it’s referred to in historical threads and sites abroad as “FOG Trunk”, so I call it that in order to keep those historical references accurate. But yeah, it’s beta. It’s all I use at work and at home. It’s MOST safely used with virtualization, but three of my organization’s fog servers are not virtualized and they are doing fine - we just don’t update those as often.
-
@Wayne-Workman beta implies that it has reached a point where it is being tested to be considered a release candidate, trunk is simply the development trunk. the central repo of all changes that have been brought into the mainline. while we try to keep the development trunk stable, it is not a finalized form and hasn’t necessarily been tested much at all, depending on how much has been committed to it on a given day.
I prefer to recommend upgrades to specific versions of the trunk if I can. an upgrade from 1.2.0 to svn revision 3652 should be pretty painless and has most of the new features that most users would notice. -
Ok awesome. I have it installed and running. Going to start some testing. I’ll let you guys know. Thanks so much for the great help.
-
lol now that i have updated my tftp sever is timing out,… Oh my.
-
what distro and version of Linux are you running fog on?
-
Ubuntu Server 14.04. I think it has to do with these eee pc netbooks. They have the atheros boot stuff. It seems to work on all my others. I’m going to keep testing. I have a working setup going so I’m not down production wise.
-
Everything is working properly so far except these little Asus EEE PC. I have also ran the single disk option for uploading and it works great. I guess i am going to have to figure out a sort of external imaging for the EEE PC. I don’t want to mess up my production server just for a few old netbooks. Thank you all for all your help.
-
I don’t believe you’ve mentioned what network boot file you’re using, but I’m going to assume it’s the default undionly.kpxe
sometimes the undionly.kkpxe works better, especially on buggy bios/pxe implementations. I’d give that a try before giving up on it. -
@Junkhacker said:
I don’t believe you’ve mentioned what network boot file you’re using, but I’m going to assume it’s the default undionly.kpxe
sometimes the undionly.kkpxe works better, especially on buggy bios/pxe implementations. I’d give that a try before giving up on it.@EAHarvey I would have suggested the exact same thing.
-
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?