• Content Count

  • Joined

  • Last visited

  • Days Won


IG-88 last won the day on November 5

IG-88 had the most liked content!

Community Reputation

214 Excellent

About IG-88

  • Rank
    Guru Master

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. yes, i'd suggest to install first to a single empty disk to make sure everything is working after this you can disconnect the disk and use the same usb with out old disks, it will suggest to migrate if you want you can also test loader 1.04b and 918+ with a single disk, 918+ has kernel 4.4.59 as base for your board: nic is realtek (r8169), sata should work as ahci (at least with the right bios settings)
  2. IG-88

    PC Nas Server probleme

    wie man die vid/pid vom usb ermittelt und in der grub.cfg einträgt wird im tutorial für die installtion erklärt https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ ich habe für den controller nachgesehen, in deinem link war dazu nichts aber ich habe dann noch mal ein paar minuten nach dem namen des controllers gesucht und eine seite schrieb marvell 9215, das ist ein 4port controller und sollte problemlos gehen
  3. it seems that removing jun's newer drivers in favor of the original drivers (that then will be loaded) might break it for other people needs more data collection on why ist fails on some systems and works on others, in theory it should depend an the processor generation, containing different gpu cores that will have to wait until 3615/17 is in a usable state and has a tutorial
  4. try to the extra/extra2 with the originals fro m jun and reboot you might also try to remove the e10g18-t1 (btw thats a aquantia aqc107 based card, driver is atlantic.ko) if it worked before and you hat a synology natively supported nic, why did you use my extra/extra2 at all? my suggestion is to install it for testing on a single empty disk and if that works with the hardware then it might be ok to use it with a active installation containing data
  5. wait for the next iteration, i will work on this in december when i'm done with 3615/17 i think i know how to get things right/better in your case the driver is igb and the driver in the 1st post's list is commented with latest crashed so it uses the synology default driver and that one seems to be to old for your hardware can you provide a lspci vendor id of the nic hardware?
  6. IG-88

    PC Nas Server probleme

    karte rein, platten dran, usb mit xpenology loader booten (vid/pid muss angepasst sein) und das war's. wenn es ein marvell 9215 ist dann ist es ahci und funktioniert einfach so da es für die oboard 's keinen treiber gibt sollten die auch nirgends auftauchen
  7. delete the old extra.lzma before copying the new the 2nd partition has 30MB, zImage and rd.gz is about 9MB, one extra.lzma is about 4-6MB afaik you can't the part of unpacking and packing it ist just nor mal linux stuff, you can read about it here and for just unpacking, packing you can boot up a live linux in virtualbox on windows and nowdays windows 10 even can have a linux installed (but a vm und a cd image in virtualbox is easier to get rid of after wards https://xpenology.com/forum/topic/7187-how-to-build-and-inject-missing-drivers-in-jun-loader-102a/ https://xpenology.club/compile-drivers-xpenology-with-windows-10-and-build-in-bash/
  8. ok, with the grep we only see the line with the driver and not the info about the pcie device "lspci -k" and then the two sections with e1000e would be something like this (in my case here for tn40xx) 0000:07:00.0 Class 0200: Device 1fc9:4024 Subsystem: Device 1fc9:3015 Kernel driver in use: tn40xx result for dmesg might look like this, e1000e in this case is jaust loaded but no hardware present, if the hardware is present there will be more (like tn40xx in my example) [ 37.134864] e1000e: Intel(R) PRO/1000 Network Driver - 3.3.4-NAPI [ 37.134868] e1000e: Copyright(c) 1999 - 2016 Intel Corporation. ... [ 37.160143] tn40xx low_mem_msg proc entry initialized [ 37.160147] tn40xx low_mem_counter proc entry initialized [ 37.160150] tn40xx debug_msg proc entry initialized [ 37.160151] tn40xx: Tehuti Network Driver, [ 37.160247] tn40xx: tn40xx [ 37.160252] tn40xx: srom 0x0 HWver 16 build 0 lane# 4 max_pl 0x0 mrrs 0x2 [ 37.160378] tn40xx 0000:07:00.0: irq 48 for MSI/MSI-X [ 37.681009] tn40xx: PHY detected on port 28 ID=1405896 - MV88X3120 10Gbps 10GBase-T
  9. update package 4, 918+, files inside: "linux-4.4.x-apollolake-bin_4.4.15-24922-s4_all.deb", package with new kernel drivers, does not contain a new e1000e.ko driver and there is only "flashupdate_6.2-24922-s3_all.deb" no "s4", that flashupdate could contain a new rd.gz with a new driver usually a new driver would be in "linux-4.4.x-apollolake-bin_4.4.15-24922*" and "flashupdate*" and there is no e1000e.ko in all updates whatever you did its not coming from the dsm updat4 e1000e.ko inside rd.gz u3, version 3.3.4 e1000e. ko in initial 6.2.2, version 3.3.4 so nothing to support your claim that u4 is the reason i also checked 6.2.0 (v23739), e1000e.ko version 3.3.4 either it worked all the time and you did not noticed it or you introduced a new driver like from my extra.lzma (contains version 3.6.0) please check log on console with "dmesg" to see whats written to the log, when starting the driver, there should be a version number for the driver in use also please check with " lspci -k | grep 'Kernel driver' " what vendor- and product-id your i217-lm nic has, that can usually be checked against a driver (source) to see if a device is supported
  10. maybe, there are a lot of N54L around here and its not a typical problem (like the c2e setting in bios to install xpenology) you can look around here https://xpenology.com/forum/topic/22482-dsm-622-24922-update-4/page/2/?tab=comments#comment-125926 and message one or the other what bios they use and about the settings maybe the hint about acpi 1.0 is enough? - Outcome of the update: SUCCESSFUL - DSM version prior update:DSM 6.2.2-24922-3 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP N54L gen7 + Intel NIC - Additional comment: Reboot required, restart + shutdown OK / Extra Intel NIC, ACPI Bios configured to Version 1.0.
  11. there can be cable issues too, you can shutdown unplug and replug the cable in question, maybe replace it as long as you don't touch the good disks there should be no additional risk
  12. write down serial number from dsm storage manager of your failed disk and check on that when replacing the disk
  13. on my two test systems (baremetal install) used for testing new extra.lzma's for 3515/17 with 6.2.2 i dont have problems like this both intel based and extremely old