Jump to content
XPEnology Community

kurara0726

Rookie
  • Posts

    4
  • Joined

  • Last visited

Posts posted by kurara0726

  1. 5 hours ago, IG-88 said:

    i'm pretty sure its the nic, you kind of confirmed that the i217 is not working

    i'm sure its not vt-d, my C2550 i tested does not have this, if you want to make guesses look for differences in gen3 vs. gen4 intel core cpu's, sandy and ivy bridge cpu's are not working with 918+ and if you add the C2550 to that instruction comparison ...

     

    Thank you for reply. I tryed some more times, and I'm sure the i217(i217-LM) is not working. I noticed that when I connected the lan to i217 nic, the led lighted after booting, while when I connected the lan to i210, the led didn't light. The 3 nic's works ok if I install win10 to the server.

    Look forward to your new driver package.:12_slight_smile:

  2. 15 hours ago, redmilk said:

     

    Now...Test again and it will not work.It is not visible on the network after booting.

    i3-4130, Asrock b85m Pro4(intel i217v)

     

    add..

    i7-7700T, J3455 work fine

    Can you please try install the i5-4670t CPU to the Asrock b85m Pro4 motherboard and see if it works? So we can see if it's the problem with the motherboard or with the CPU (instructions library missing? maybe vt-d or Intel Trusted Execution Technology is needed for dsm to work?).

  3. 9 hours ago, IG-88 said:

     

    strange, the driver for the nic would be e1000e and thats inside the image and the platform haswell works for others

    maybe we can come back to this later when we have a driver package and have divers compiled from intel source, maybe a driver problem and not th cpu

     

    I have an Acer C100F3 server with i3-4150T CPU and two I210 NIC and one I217 NIC. When I use jun's loader 1.02b, it is not visible on the network after booting. I have tried the loader with or without your driver package, and it's the same result. (When I try XPEnoboot 5.2, it can be detected on the network)

    And I tried loader 1.03a2, it's not visible on the network either.

     

    And I noticed that when I boot the server with jun's loader 1.02b, the led of nic is not lighted, so I think the nic is not working. But when I edit the grub.cfg file, from 

    initrd $img/rd.gz $img/$extra_initrd

    to

    initrd $img/$extra_initrd $img/rd.gz

    and boot the server with the edited loader,  the led of nic is lighted, but the server is still not visible on the network.

×
×
  • Create New...