Unable to pxe boot e6410
Running 3.3, with the latest kbe driver pack. I've even added the drivers into the driver folder directly (both from dell and intel based on the intel gigabit 82577 driver set). Still fails to mount k2000 volume. Seems like it never installs the nic. Machine pulls ip address fine with the stock os.
All of our other models boot fine. Could someone give me a hint as to what to try next?
Thanks :)
All of our other models boot fine. Could someone give me a hint as to what to try next?
Thanks :)
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
dchristian
13 years ago
Try grabbing the win 7 driver from the manufacturer website (make sure you extract the contents if it comes packaged).
After you have the driver ready, add it to the kbe folder, re-cache and rebuild your environment.
hope this helps.
After you have the driver ready, add it to the kbe folder, re-cache and rebuild your environment.
hope this helps.
Posted by:
airwolf
13 years ago
I'm not sure why you're having issues, but I can tell you that the E6410 works fine in our environment. All I've done to the KBE is add the KBE driver pack from DellKACE.
Posted by:
ngbrown24
13 years ago
I've added the specific drivers into the kbe folder from dell, re-cached. Getting the same information:
Error: Unable to determine server ip address from dhcp
Error: Unable to mount K2000 share at \\x.x.x.x\peinst
Think I need to break down and contact support? :) Totally strange, this is a stock e6410, looked at the hardware build sheet and it isn't anything unusual. I might grab another from staging to see if it does the same thing.
Error: Unable to determine server ip address from dhcp
Error: Unable to mount K2000 share at \\x.x.x.x\peinst
Think I need to break down and contact support? :) Totally strange, this is a stock e6410, looked at the hardware build sheet and it isn't anything unusual. I might grab another from staging to see if it does the same thing.
Posted by:
dchristian
13 years ago
Two questions.
1- if you do an ip config do you get an ip address?
2-Did you rebuild the kbe and boot into the newly created environment. The first kbe created becomes the default. Additional kbes for the same architecture will be at the bottom.
1- if you do an ip config do you get an ip address?
2-Did you rebuild the kbe and boot into the newly created environment. The first kbe created becomes the default. Additional kbes for the same architecture will be at the bottom.
Posted by:
ngbrown24
13 years ago
ipconfig, seems like the adapter isn't installed:
host name.... minint-4rkqssf
Primary DNS Suffix ... blank
Node Type: Hybrid
IP Routing Enabled: No
WINS Proxy Enabled: No
only had one kbe boot environment x64, from the latest windows automated installation kit. I built another, booted from it and same result.
host name.... minint-4rkqssf
Primary DNS Suffix ... blank
Node Type: Hybrid
IP Routing Enabled: No
WINS Proxy Enabled: No
only had one kbe boot environment x64, from the latest windows automated installation kit. I built another, booted from it and same result.
Posted by:
ngbrown24
13 years ago
On further investigation it seems like only the latest revision of our e6410 and I also tested a panasonic cf31. Both have new revisions of the 82577LM. We receive these units in the last week. Is there an error log I can get to on the kace appliance to see where the driver load is failing?
e6410 82577LM, hardware id 040A1028&REV_05
CF31 82577LM, hardware id 833810F78&REV_06
e6410 82577LM, hardware id 040A1028&REV_05
CF31 82577LM, hardware id 833810F78&REV_06
Posted by:
ngbrown24
13 years ago
removed all drivers from kbe folder and left only the e6410 drivers I got from dell's site, according to the service tag. no dice.
Posted by:
ngbrown24
13 years ago
oh and i made sure to re-cache the drivers folder before trying :) man this is weird.
Posted by:
cblake
13 years ago
Note that for KBE drivers, after you recache you need to rebuild the boot environment with the media manager tool, then change your default boot environment to your new one. Can you confirm those steps are happening? You only refer to recacheing above.
Posted by:
ngbrown24
13 years ago
so it ended up being a driver conflict. removed the e1k6264 under the kbe -> kace folder and added the new driver. drivers recached and uploaded an new kbe. thank you kase support!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.