alirz1

Members
  • Content Count

    74
  • Joined

  • Last visited

Everything posted by alirz1

  1. Im actually not using my second nic. Im still on dsm 6.1 for my ds3716 based xpenology, where only one of my nic works. The only time my second Nic worked was when i tested the DS918 build with 6.2 and the 1.03 loader.
  2. Sorry i have no experience using MAC OS so cant help you there.
  3. Hi, Well i was testing the DS918+ and your extra ramdisk, and i see a new driver in that one. My post#160: For ds3617, dsm 6.1.x, Please update Intel(R) PRO/1000 Network Driver" driver to 3.4.0.2-NAPI. The current driver in the loader 3.3.4. Due to this one of my nics does not work. The only place i found the new driver is in the extra ramdisk that @ig-88 compiled for DS918+ to use with Jun's 1.0.3a2 loader and dsm 6.2. I test booted with that loader/extra ramdisk and confirmed that both my nics work with that (Intel AT1219 and 1211). Im still puzzled though, why my NIC works with the 918+ loader and your extra ram file but doesnt work under the dsm 3617.
  4. Perhaps your sata port map config is incorrect? Is this a new install or are you changing boards etc?
  5. Hi, Well i was testing the DS918+ and your extra ramdisk, and i see a new driver in that one. My post#160: For ds3617, dsm 6.1.x, Please update Intel(R) PRO/1000 Network Driver" driver to 3.4.0.2-NAPI. The current driver in the loader 3.3.4. Due to this one of my nics does not work. The only place i found the new driver is in the extra ramdisk that @ig-88 compiled for DS918+ to use with Jun's 1.0.3a2 loader and dsm 6.2. I test booted with that loader/extra ramdisk and confirmed that both my nics work with that (Intel AT1219 and 1211). One of those nics uses the igb module and the other uses e1000. under dsm 6.1.x the nic using the igb module works, but the other doesnt. If it helps, my motherboard did come with the linux drivers for that and it has source files in there also. intel e1000e 3.4.0.2 driver LINUX.zip
  6. Anyway of getting updated modules for intel e1000e and igb NIC for ds3617, dsm 6.1.x? While i can compile drivers using synology's source and toolchain. It still gives me the older dirver and i cant figure out how to "INJECT" new drivers into that build. Even though i have the source files for the drivers. i.e the "c files".
  7. For ds3617, dsm 6.1.x, Please update Intel(R) PRO/1000 Network Driver" driver to 3.4.0.2-NAPI. The current driver in the loader 3.3.4. Which doesnt seem to support some newer intel nics.
  8. alirz1

    DSM 6.2 Loader

    If im looking at the below link correctly. Ds3617, which is Broadwell based, seems to still have the 3.10 kernel in DSM 6.2? while some other models, e.g DS918 are up at the 4.4 kernel. https://sourceforge.net/projects/dsgpl/files/DSM 6.2 Tool Chains/
  9. So im trying to know why would one choose to build a xpenology box, lets say, using DS3617xs as the model vs DS918+ ? I ask because, using loaders,extra ramdisk and dsm 6.1.x etc for ds3617, one of my NICs doesnt work. Whereas if i boot up the same hardware using loader,extra ramdisk, dsk 6.2 fo4 DS918. both my Nics work. So the question is what would i lose if switched over to the DS918+? Will all my data migrate from my dsm3617 xpenolgy to ds918+. Do i simply lose the number of HDDs supported as ds918 seems to be a 4 bay NAS? Thanks
  10. For ds3617, dsm 6.1.x, Please update Intel(R) PRO/1000 Network Driver" driver to 3.4.0.2-NAPI. The current driver in the loader 3.3.4. Due to this one of my nics does not work. The only place i found the new driver is in the extra ramdisk that @ig-88 compiled for DS918+ to use with Jun's 1.0.3a2 loader and dsm 6.2. I test booted with that loader/extra ramdisk and confirmed that both my nics work with that.
  11. one thing i dont know myself is that why some folks choose to use ds3617 vs other models like DS918+ etc... What is the difference? Is it simply because of the number disks supported? I mention because based on my testing, using the 1.03 loader for ds918+ and the v4.8 extra.lmza file you would have better luck. See if you can try that.
  12. 1219 is working fine for me for 3617, using 1.02 load and @ig-88's extra ramdisk. im on dsm 6.1.7 though. Are you on DSM 6.2? By the way, you're likely not going to get much help on this forum.
  13. While this forum seems to be dead beat ill ask again hoping to get some answer. Im still trying to figure out why my compiled driver for Intel "e1000e" module is not working. I i have a in i3 8100 based baremetal box that works jsut fine wih jun's 1.02 loader, 6.1.7. however just one NIC works. When compiling im using the guide from the link i pastes above, however as im compiling for ds3617, im using the source package"linux-3.10.x.txz" for "broadwell" from https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/15047branch/broadwell-source/ I compile everything successfuly. However to test, i only use the relevant .ko modules that i know apply to my Intel 1211AT card. i.e i only use igb.ko and e1000e.ko. however when i boot with those modules, none of my Nic works. I know for a fact that my NIC1 (intel 1219) uses the igb.ko module and the 1211 is supposed to use the e1000e module. but im having no luck. Am i doing something wrong? Compiling using the wrong source/ wrong platform etc..? please if anyone know, let me know.Thanks
  14. Anyone know the answer to above the question? Is it correct to compile drivers for the BROARDWELL platform to use on a xpenology ds3617 based on intel i3 cpu?
  15. so i followed the guide at https://xpenology.club/compile-drivers-xpenology-with-windows-10-and-build-in-bash/ that guide uses " to compile NIC drivers for Intel "igb" and "e1000e" modules for my ds3617 (BROADWELL platform). Then only inserted the compiled igb.ko and e1000e.ko into @ig-88 extra.lmza file. Booted from it, but now none of my two NICs come online. I dont know what could be wrong here. Seemed pretty straightforward. I think i give up now. Ill just live with the one working NIC using @ig-88 extra ram disk file. Unfortunately i wasnt able to get any help on this forum. EDIT: Just to confirm I should have used platform "broadwell" correct? My xpenology is based on an 8th gen intel i3-8100 cpu, Using juns 1.02b loader for ds3617
  16. Anyway of getting updated modules for intel e1000e and igb NIC for ds3617, dam 6.1.x? thanks.
  17. ok so i tested. To aovid messing up my ds3617 xpenology disk, i unplugged them just to test booting off the DS918+ loader to test my two lan nics. This is what i observed: - with the stock 1.03a2 jun loader for Ds918+, the functional NIC is the intel 1211 and the intel 1219 DOESNT work. (on my ds3617 1.02b loader, the 1219 works but the 1211 does not) -with the 1.03a2 jun loader for Ds918+ with the extra ram disk lzma included. Both my NICs work. So obviously the ram disk for the ds918+ has some additional drivers that the 3617 ram disk does not!. I think the extra ram disk for the ds3617 needs a new driver module for "igb" because that module seems to be responsible for the intel 1211 NIC.
  18. in 1.03b with the extra ram disk for the DS918+? or does it also work for Ds3716 with 1.02b loader?
  19. oh sorry. well im still on 6.1.7. Just trying to get a driver added so that i can make my intel 1211AT adapter work, but having no luck so far.
  20. But what about the one you reference to in the first post at Isn't that applicable to the 3617?
  21. well darn it, i found it myself right after i posted this question. Create and add in /root/.bashrc. That works for the "ash" shell, which is the default in dsm6.
  22. I moved form DSM 5 to DSM 6.1.x recently. I've looked and looked but i cannot figure out where to set the path, add aliases, and also set the shell prompt to show the current directory path, like it was in DSM 5. Under dsm 6, im looking to set those values for the root user. i.e once i've Sudo su" to root, thats when i would like my environment variables to kick in. Would anyone know this? i've tried updating /root.profile, /etc.defaults/profile, /etc/profile. but none of those seem to have any affect. I even tried chaging the shell for root user to be "bash" instead og ash but even with that i could find out where to put the env variables. Thanks/