Tag Info

New answers tagged

3

Here are the data sheets for the two drives: Intel S3500 LiteOn basically the LiteOn drive is slightly less performant, lower numbers in IOPS and Read/Write. Also I don't see write lifetime for the LiteOn, but the Intel is rated at 275TBW. Generally the Intel looks like a slightly better drive. That said, if you where expecting Intels and got Liteons ...


-1

I solved this problem by upgrade my system kernel from 13.13 to 13.17.4 In another machine, I did not get the same issue with 13.13 kernel with docker. That was strange


0

Did you try making a Selection Profile and selecting the driver(s) with it? You can select the selection profile in the deployment share properties under the Windows PE -> Drivers and Patches. This will integrate the drivers into your PE image so that i can load them without needing to connect to the network. Now this does directly integrate the driver ...


3

Final solution was resetting the BIOS settings to "Fail-Safe Defaults" as suggested by Brian.


0

The required NIC driver "MUST" be either off-line injected and loaded by loaddrv at boot or on-line injected (Dism) in your Boot.wim file. Off course if the NIC driver is not properly loaded you will never see the MDT repository that means no access to anything MDT has to offer using its shares. I think PE is detecting the NIC but your driver is not ...


1

I'm going to assume you're deploying Windows 7. I ran into a similar issue on newest Intel wired NIC chipsets. Check the Kernel Mode Driver Framework for an update. Windows 7 launched with version 1.9 per TechNet, and this needs to be injected into the image as a task in MDT. Windows 8 certified hardware will likely target KMDF 1.11 This Post explains ...


1

Those lines in first backtrace look like a kernel bug: Nov 24 15:21:30 shisoft-idc kernel: [25672.210093] [<ffffffff81727aa8>] general_protection+0x28/0x30 Nov 24 15:21:30 shisoft-idc kernel: [25672.224652] [<ffffffff816f6ff2>] ? in6_dev_finish_destroy+0x62/0xf0 Nov 24 15:21:30 shisoft-idc kernel: [25672.238830] [<ffffffff8122a099>] ? ...


1

Based on this line : Nov 24 15:21:49 shisoft-idc kernel: [25700.486840] BUG: soft lockup - CPU#20 stuck for 22s! [irqbalance:1544] which more or less means you managed to crash your cpu for at least 22 seconds . . . I think the problem is your intel CPU , if the CPU is not dead or dying, it could just be bugged, get a look at the microcode update ( the ...



Top 50 recent answers are included