Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 12/06/2017 in all areas

  1. my approach for 4.1 was (priority highest to lowest): - my driver from external source if they where proofed to do better then jun's and dsm's (r8152 and tg3 for now) - jun's driver (he might have used newer source the whats inside dsm or if he used his own/newer driver instead of using one from dsm there might be a reason i dont know about) - driver from dsm - newly compiled driver from synology kernel source dsm 6.1.3 (15152) there is a version conflict in all this (fixed) loader + dsm approach jun's loader comes with kernel and drivers for dsm 6.1.0 (15047) when you boot up the first time, on installing you overwrite the original dsm 6.1.0 booting kernel with the dsm version you are installing, but the drivers in the extra.lzma are still the same so after installing dsm you use dsm 6.1.3/4 with drivers for 6.1.0 my extra.lzma will mixing in drivers compiled with the source for dsm 6.1.3 (15152), when looking to the resulting system after installation (dsm 61.3/4) better suited but they can be in conflict with the kernel in jun's 1.02b (dsm 6.1.0) that is used for 1st boot to install dsm also there is was and is the risk that drivers for dsm 6.1.0 do work on 1st boot, land in /lib/modules/update and will be used with the newer installed dsm version and fail with the newer dsm version (same main version of kernel but differences in code as they have a newer revision 15047 -> 15152). there are ways to deal with it 1. leave it that way, i can't remember a case where someone had a working nic/storage on 1st boot (6.1.0) and failed booting after installation of dsm (6.1.1/2/3/4) 2. compiling additional drivers with source for dsm 6.1.0 (15047) and stay on the road of jun's loader 3. compiling with the newest source (6.1.3 atm) and not just replacing extra.lzma on jun's loader, also replacing zImage and rd.gz from the newest dsm (even it its 6.1.4, the source of 6.1.3 is "closer" to 6.1.4 then the source of 6.1.0) on a original synology system that problem does not exist, on versions with a new kernel revision there is always a complete dsm file (200MB) with boot kernel and all drivers, the kernel is written to the usb boot device and dsm is installed to disk, no conflict at all as i have seen differences in loading divers i compiled from synology source and the same drivers jun provided (presuming he also used the synology source v15047) , i will need to do some testing to see if the difference comes from the kernel revision number or something else (any differences in how the drivers where compiled like kernel options) as 3. seems to be the cleanest (and easy) way when providing a complete loader with extended extra.lzma and newest kernel from dsm, i will not do this for legal reasons, providing compiled drivers from source code that is available for everyone is not really a problem, but releasing code that is owned by synology (like taking the compiled kernel out of dsm and re releasing it with jun's hack to get into dsm) is a different matter and i don't want to get in a situation to spend money on lawyers to deal with the legal division of a company that has much more money to spent then one person (legal hard working and tax paying) can afford so my way would still be just releasing a extra.lzma as i do it now as 3. is just an additional step to 1. and also can be solved by adding steps to the howto for installing xpenology/dsm, atm there is no justification for such additional steps that will make the hurdle to install xpenology/dsm even higher so i as long as i can't find any gain in using older source it will be 1. and 3. is a option that can be used ps: sorry if i don't answer every pm, some of them are kind of answered with the information in this thread and new released extra.lzma, the time i can spare is limited so i have to share it between writing text (writing so everyone can read is preferable to pm, on long term there is more gain to expect if more people can read it) and working on newer extra.lzma and improving linux skills
    1 point
  2. вы о чём вообще? в первом поле выбираем в качестве провайдера ovh во втором поле 'ваше имя'.s50.online и сообщить в личку за данными 3 и 4 поля в личку в итоге ваш внешний доступ будет выглядеть примерно так или так: File Station, Video Station, MailPlus, Calendar
    1 point
×
×
  • Create New...