Jump to content
XPEnology Community
  • 0

Juns Loaders support : Asrock C2550D4I ?


renegadeBE

Question

Hi,

A simple question: is the ASROCK C2550D4I motherboard supported by Jun loader?
Feedback with loader V1.02 and V1.02a?
It uses an intel i210 network interface. It does not appear in the Polanskiman tutorial.


Thanks

Edited by renegadeBE
Link to comment
Share on other sites

Recommended Posts

  • 0
1 hour ago, IG-88 said:

hi,

 

it does

1.02a, DS3615xs, 6.1.1 15101 U4

all 12 sata ports working, onboard nic also working

 

Is that through VM or Bare Metal?

 

If the 2550 is working then the 2750 is also working. SWEEETTTTT!!!!

Link to comment
Share on other sites

  • 0

bare metal with just the extra.lzma that comes with jun's loader 1.02a, i only added a evdev.ko for acpi button shutdown (now a availible as part of a spk package someone made for that purpose)

btw. you could haven known earlier, i already reported this in april, the search function can be useful

 

 

Edited by IG-88
Link to comment
Share on other sites

  • 0

just replaced my usb image jun 1.02a with jun 1.02b (had to repair with synology assistant after first boot, took a few seconds, boot after this was ok) and then updated from 6.1.1 u4 to 6.1.2, no problems (as expected, the kernel/drivers are still the same, the problem that rhe drivers in /lib/modules/update are not loaded should be fixed with 1.02b - seems to work for me)

  • Like 2
Link to comment
Share on other sites

  • 0

So, after many frustrated hours trying to get this working...

 

Everything should be set up properly... but... Synology assistant cannot for find it. It was able to see it earlier, a few days back, but the install wouldn't work. So I played around with things and now I cannot even get that far.

 

I am fairly confident the USB device is set up properly, so I suspect now that maybe it's the UEFI settings that I have screwed up.

 

Would someone be so kind as to help me try to figure out what's going on...

 

Thanks

Link to comment
Share on other sites

  • 0

reset the bios to defaults, then disable all unnecessary peripherals, set to boot from usb and disable all other boot options. try booting with no drives attached first to see if the nas appears on the network. also try your usb boot loader in another machine as a check that your image/grub settings are good

  • Like 1
Link to comment
Share on other sites

  • 0
13 hours ago, sbv3000 said:

reset the bios to defaults, then disable all unnecessary peripherals, set to boot from usb and disable all other boot options. try booting with no drives attached first to see if the nas appears on the network. also try your usb boot loader in another machine as a check that your image/grub settings are good

Thanks sbv3000. I was almost going to give up... I'll let you know if I have any success.

 

Do you have the same board?

Link to comment
Share on other sites

  • 0

So no joy... I did everything you asked except boot off the USB on another computer. I will try that tomorrow.

It is quite a mystery to me...

Any other thoughts?

I'm completely stumped... it is doing my head in... if other people hadn't had success with this board then I wouldn't persist so...

Thanks again for trying


Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

  • 0
On 06/07/2017 at 9:33 PM, sbv3000 said:

reset the bios to defaults, then disable all unnecessary peripherals, set to boot from usb and disable all other boot options. try booting with no drives attached first to see if the nas appears on the network. also try your usb boot loader in another machine as a check that your image/grub settings are good

 

So I tried everything now. Interestingly enough I was able to see the Xpenology in find.synology.com on another machine.

 

I also installed freenas on this machine to see if the NIC was working properly and it was. I may have to go down the freenas road, but I'd prefer not too. DSM is far easier to use and stuff just seems to work with it better.

 

I'm not sure what the problem would be. Can anyone give me any ideas?

Link to comment
Share on other sites

  • 0

try using the synology assistant not the url finder.

freenas will work as I suspect all the drivers are included, remember that xpe is a 'bespoke' boot loader/build containing restricted device drivers, however everything on this board is known to work.

also, its not 'good practice' but try setting your mac addresses to 'blank' so that the native ones are used for networking. if that works and you can install, then edit grub to match the onboard macs. I suggest this because I have a dual intel embedded nic board and mac 1 and 2 were not in the same order as xpe/dsm so I was forcing mac 1 to be mac 2 and this was causing problems. also just try one network connection to start in case of other conflicts

Link to comment
Share on other sites

  • 0

Thanks again,

 

I did try Synology Assistant - side by side with the url. Same result.

 

I know from previous experience that this board is complicated in terms of NICs. The physical onboard ethernet ports total three, one IPMI and two supposed standard ports. But the IPMI has two mac address and using ipconfig (equlivent, can't remember the linux command, in Ubuntu Live) gives another two. So a total of four mac address accross three phsycal ports. I personally don't know how that works... I guess this may be similar to your board with it's "dual intel embedded nic"

 

So I just installed FreeNas again and I want to determine the Mac it uses to connect to my router. Then atleast I could be more confident what mac that physical NIC port is using.

 

After that I'll try to to leave the mac address blank. And what do you mean by just trying one connection to start? Do you mean try removing the IPMI cable, or what?

 

I'll report back my findings...

 

Thanks for your persistence, much appreciated!

 

Link to comment
Share on other sites

  • 0

It might be that the IPMI and embedded nics are conflicting with the mac and netif settings in the grub menu (check Polanskimans tutorial for info)

I'm not an expert on IPMI but a quick google tells me its used by HP ILO and Dell DRAC server management systems and my experience of these is that they are server console management ports, not 'standard' nics. That makes sense as the nic might have two mac addresses similar to a vswitch/virtual nics in ESX so it can run different protocols/services over a single interface, in itself not an issue, but could be causing 'conflicts' between your dhcp server and xpe/dsm. Can you try disabling ALL the nics in the bios, then enable one  of the standard ones and try and boot from that with a basic grub config. if that works then enable the other standard one, then finally the IPMI one, you might need to edit your grub menu each time you change the settings. My guess would be the IPMI nic is not used for 'network traffic' so you will end up disabling it or leaving it unconnected.

Link to comment
Share on other sites

  • 0

Hi sbv,

There is no way to disable the NICs in the BIOS. I instead tried to set the IPMI to static addresses. I thought that might help to stop a conflict. I cannot disable it, neither in the BIOS nor in the IPMI.

 

Getting tired of all this... It is surely a strange scenario. No one else is struggling with this board.

 

If any thing else comes to you please let me know.

 

Thanks for the help otherwise!

 

 

Link to comment
Share on other sites

  • 0

I'm not sure if some of this might help, found some documents about the board series

 

try setting up the ipmi from this guide so that you can manage the board, that will eliminate the settings from the XPE/DSM issue

 

http://www.asrockrack.com/support/IPMI.pdf

 

And check the bios advanced settings plx8608 to to manage the nics

 

ftp://europe.asrock.com/manual/C2750D4I.pdf

 

if you have a basic setting of just one nic and single mac grub settings (blank or matching the enabled nic) then you might have some success.

 

I have a couple of Aliexpress unbranded mobos with dual onboard intel i221 nics that work fine with XPE/DSM 5.2 and 6.1 loaders (not 6.0) and I think the i210 nics on the asrock board are the same family/drivers so should be ok

 

Have you tried the 5.2 loader as a test?

Link to comment
Share on other sites

  • 0

5.2 worked fine. But it's getting old now and I don't want to use it as a security concern.

I have to get up for work now. I'll check out the articles. And see what I can find.

You said that 6.0 didn't work. So can I install 6.1 directly? Actually I tried that and was able to see the Xpen but when I tried an install it failed. After a few times like that now I haven't been able to see it at all. Mind you I've been trying predominantly with 6.0. So just setup a 6.1 with 1.2b Jun? Is that enough?

Anyway, when I get time to sit at a computer...

Thanks for keeping up. I was almost ready to throw in the towel. You've gumption that's for sure!

There is a really great tech support guy at Asrock I will try to write to him too.

I did find one problem with the BMC/IPMI. One of the two mac addresses were not showing in the bios. I reflashed the BMC and that fixed it. I was hoping this would solve it, but alas.

I'll report back, thanks again.


Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

  • 0

When I tried the 6.0.2 loader with the mobo with the dual embedded intel 221 nics it didnt show up in Assistant.

When I tried with the 6.1 loaders (a or b) it worked

Also, from the dmesg output from this mobo this is the network driver loaded so I suspect the asrock would use the same ones

 

 30.023361] e1000e: Intel(R) PRO/1000 Network Driver - 3.3.4-NAPI
[   30.023369] e1000e: Copyright(c) 1999 - 2016 Intel Corporation.
[   30.155941] Intel(R) Gigabit Ethernet Network Driver - version 5.3.5.3
[   30.155948] Copyright (c) 2007-2015 Intel Corporation.
[   30.156534] igb 0000:03:00.0: irq 106 for MSI/MSI-X
[   30.156549] igb 0000:03:00.0: irq 107 for MSI/MSI-X
[   30.201118] igb 0000:03:00.0: added PHC on eth0
[   30.201126] igb 0000:03:00.0: Intel(R) Gigabit Ethernet Network Connection
[   30.201130] igb 0000:03:00.0: eth0: (PCIe:2.5GT/s:Width x1) 
[   30.201135] igb 0000:03:00.0 eth0: MAC: xx.xx.xx.xx.xx.xx. (edited for privacy reasons)
[   30.201142] igb 0000:03:00.0: eth0: PBA No: Unknown
[   30.201155] igb 0000:03:00.0: LRO is disabled
[   30.201159] igb 0000:03:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
[   30.201707] igb 0000:04:00.0: irq 108 for MSI/MSI-X
[   30.201721] igb 0000:04:00.0: irq 109 for MSI/MSI-X
[   30.241859] igb 0000:04:00.0: added PHC on eth1
[   30.241866] igb 0000:04:00.0: Intel(R) Gigabit Ethernet Network Connection
[   30.241892] igb 0000:04:00.0: eth1: (PCIe:2.5GT/s:Width x1) 
[   30.241897] igb 0000:04:00.0 eth1: MAC: xx.xx.xx.xx.xx.xx.  (edited for privacy reasons)
[   30.241903] igb 0000:04:00.0: eth1: PBA No: Unknown
[   30.241916] igb 0000:04:00.0: LRO is disabled
[   30.241920] igb 0000:04:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

  • Like 1
Link to comment
Share on other sites

  • 0
When I tried the 6.0.2 loader with the mobo with the dual embedded intel 221 nics it didnt show up in Assistant.
When I tried with the 6.1 loaders (a or b) it worked
Also, from the dmesg output from this mobo this is the network driver loaded so I suspect the asrock would use the same ones
 
 30.023361] e1000e: Intel® PRO/1000 Network Driver - 3.3.4-NAPI
[   30.023369] e1000e: Copyright© 1999 - 2016 Intel Corporation.
[   30.155941] Intel® Gigabit Ethernet Network Driver - version 5.3.5.3
[   30.155948] Copyright © 2007-2015 Intel Corporation.
[   30.156534] igb 0000:03:00.0: irq 106 for MSI/MSI-X
[   30.156549] igb 0000:03:00.0: irq 107 for MSI/MSI-X
[   30.201118] igb 0000:03:00.0: added PHC on eth0
[   30.201126] igb 0000:03:00.0: Intel® Gigabit Ethernet Network Connection
[   30.201130] igb 0000:03:00.0: eth0: (PCIe:2.5GT/s:Width x1) 
[   30.201135] igb 0000:03:00.0 eth0: MAC: xx.xx.xx.xx.xx.xx. (edited for privacy reasons)
[   30.201142] igb 0000:03:00.0: eth0: PBA No: Unknown
[   30.201155] igb 0000:03:00.0: LRO is disabled
[   30.201159] igb 0000:03:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
[   30.201707] igb 0000:04:00.0: irq 108 for MSI/MSI-X
[   30.201721] igb 0000:04:00.0: irq 109 for MSI/MSI-X
[   30.241859] igb 0000:04:00.0: added PHC on eth1
[   30.241866] igb 0000:04:00.0: Intel® Gigabit Ethernet Network Connection
[   30.241892] igb 0000:04:00.0: eth1: (PCIe:2.5GT/s:Width x1) 
[   30.241897] igb 0000:04:00.0 eth1: MAC: xx.xx.xx.xx.xx.xx.  (edited for privacy reasons)
[   30.241903] igb 0000:04:00.0: eth1: PBA No: Unknown
[   30.241916] igb 0000:04:00.0: LRO is disabled
[   30.241920] igb 0000:04:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

I'm a bit preoccupied to play around the last day or two. I have a one year old.

I been in contact a Asrock support guy. He has helped before. He has asked for some more info which I provided this morning. I'll see what he comes back with and report back.

Thanks for the persistence.

So can I ask. Did you then install 6.0.2 - and then upgrade, or 6.1 directly?


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites

  • 0
On 11/07/2017 at 6:33 PM, sbv3000 said:

When I tried the 6.0.2 loader with the mobo with the dual embedded intel 221 nics it didnt show up in Assistant.

When I tried with the 6.1 loaders (a or b) it worked

Amazing - I was initially trying to install with 6.1 loader but with a newer version of DSM to go with it. It would crash. Then for weeks trying to get it working with the old loader no luck...

 

Everything appears to be running now. SBV3000 you is the man!

 

I neglected to use the extra izma file. Should it be ok for this system?

 

Now just to see if everything is working ok...

Link to comment
Share on other sites

  • 0

well its good its working at last

 

6.0.2 did not work for me with that board/nics, so I did a straight 6.1 install (with the matching .pat file).

I've not added the additional lzma as my installs seem to be ok as is, but I guess if you find things are not working then it might be needed on that board

 

enjoy :smile:

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...