LiquidSnake30
Technical User
Model - P1515
Image lay type - PXE boot (image on BoH)
Image type - WIM
Symptom:
When imaging a P1515 model Radiant Systems POS terminal, well after OS image lay down, sometimes (not all the time) the NIC will cease to pass traffic with no link light activity thus not able to locate BoH to start file sync. This is occurring on multiple POS models of this type in a lab environment thus different Ethernet cables. I can image a POS and all is working correctly. Then image the same POS another time and the NIC will crap out. The Realtek PCIe GBE Family Controller appears fine in device manager when this does occur and a ping to localhost responds fine. The current work-around is to power down POS, remove power supply cable from POS itself, then upon immediately re-seating power cable at POS the NIC is back alive and happy passing data. It is almost as if a kernel or other low level system driver isn't getting loaded up and fired off. I am curious if anyone else has seen this particular behavior before.
Keep in mind that it does not happen all the time during a POS image stage. Just seems to randomly happen.
Image lay type - PXE boot (image on BoH)
Image type - WIM
Symptom:
When imaging a P1515 model Radiant Systems POS terminal, well after OS image lay down, sometimes (not all the time) the NIC will cease to pass traffic with no link light activity thus not able to locate BoH to start file sync. This is occurring on multiple POS models of this type in a lab environment thus different Ethernet cables. I can image a POS and all is working correctly. Then image the same POS another time and the NIC will crap out. The Realtek PCIe GBE Family Controller appears fine in device manager when this does occur and a ping to localhost responds fine. The current work-around is to power down POS, remove power supply cable from POS itself, then upon immediately re-seating power cable at POS the NIC is back alive and happy passing data. It is almost as if a kernel or other low level system driver isn't getting loaded up and fired off. I am curious if anyone else has seen this particular behavior before.
Keep in mind that it does not happen all the time during a POS image stage. Just seems to randomly happen.