[Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+]

also unable to connect to use synology ddns. but it may be normal ...

[Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+]

@IG-88I again copy the extra and extra2 but the problem remains the same.
all goes well for a while and crashes.
and I still have this Docker residue on my desktop while the application is completely uninstalled.

 

I reinstalled it there.

[Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+]

@IG-88   I took the extra and extra2 files from the extra918plus_v0.8_syno.zip file.

and I'm in this version there. the 918 avec le pat DSM_DS918+_24922.pat file.

[[Reseau] chargement en boucle]

J'ai l'impression qu'il y a des conflits de versions entre les différentes versions du système par rapport au moment ou j'avais la 6.1.7.

j'ai désinstallé plusieurs fois docker sur la 6.2.2 mais un raccourci conteneur apparaît toujours sur le bureau, alors que l'application est vierge et n'a plus aucun conteneur.

 

Même sur la 6.1.7 j'avais déjà eu des soucis avec docker, il avait fallu que j'installe une ancienne version pour après pouvoir l'upgrader. celle d'origine ne s'installait pas.

 

Je viens de tester un nettoyage des données via le gestionnaire de sauvegarde et là encore il me met "la connexion a échoué, vérifiez vos paramètres réseau" et l'interface graphique est freezé.

il faut que je recharge la page pour de nouveau avoir la main.

[[Reseau] chargement en boucle]

[[Reseau] chargement en boucle]

Salut,

 

Bon désolé je n'ai pas trouvé de titre plus explicite.

Donc suite à l'installation de dsm 6.2.2 avec le loader 1.04b 918+ j'ai enfin pu démarrer le système mis à part qu'au bout d'un moment il m'indique un problème de réseau alors que je me connecte très bien à l'interface.

dsm semble fonctionner correctement pendant 2 ou 3 min puis plante en particulier si je rentre dans docker.

si je recharge la page il me redemande de confirmer mon certificat et me demande de me reconnecter, même en cocher la case garder session ouverte.

à chaque fois que je démarre et que je vais dans le gestionnaire de paquet je dois revalider les cgu.

 

dans le fichier kern.log je peut voir 

 

2020-02-12T23:34:10+01:00 ServeurNAS kernel: [   27.647745] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
2020-02-12T23:34:10+01:00 ServeurNAS kernel: [   27.647753] e1000: Copyright (c) 1999-2006 Intel Corporation.

et dans le dmesg

 

[   28.852914] bna: QLogic BR-series 10G Ethernet driver - version: 3.2.25.1
[   28.897851] usbcore: registered new interface driver cx82310_eth
[   29.039685] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[   29.039691] e100: Copyright(c) 1999-2006 Intel Corporation
[   29.070578] enic: Cisco VIC Ethernet NIC Driver, ver 2.3.0.20

 

alors que c'est un Broadcom BCM57781 IC

 

si je me connecte en ssh, aucun pb, je ping google ...

 

 

[Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+]

I may have spoken too quickly, the network is very unstable. the network, exterior side.
I access the package center at startup but after 5 min, it remains in load.

 

 

2020-02-11T16:05:07+01:00 ServeurNAS cloud-control: [ERROR] service-ctrl.cpp(127): UserHome is not enabled
2020-02-11T16:05:08+01:00 ServeurNAS cloud-control: [ERROR] engine/sqlite_engine.cpp:88 sqlite3_exec error: no such table: config_table (1)
2020-02-11T16:05:08+01:00 ServeurNAS cloud-control: [ERROR] engine/sqlite_engine.cpp:88 sqlite3_exec error: no such table: config_table (1)
2020-02-11T16:05:08+01:00 ServeurNAS cloud-control: [ERROR] service-ctrl.cpp(1245): first time installation, add default application privilege
2020-02-11T16:05:09+01:00 ServeurNAS cloud-control: [ERROR] sdk-cpp.cpp(1637): SYNOShareGet(homes): -1 Error code: 5120
2020-02-11T16:05:13+01:00 ServeurNAS cloud-cleand: [ERROR] engine/sqlite_engine.cpp:88 sqlite3_exec error: no such table: config_table (1)
2020-02-11T16:05:13+01:00 ServeurNAS cloud-cleand: [ERROR] engine/sqlite_engine.cpp:88 sqlite3_exec error: no such table: config_table (1)
2020-02-11T16:09:05+01:00 ServeurNAS syncd: [ERROR] db-api.cpp:726 Init repo (/volume1/@cloudstation/@sync).
2020-02-11T16:11:55+01:00 ServeurNAS synoscgi_SYNO.CloudStation.Server.DBUsage_1_get[22042]: [ERROR] dbusage/get.cpp(28): Failed to get cached db usage
2020-02-11T16:11:55+01:00 ServeurNAS synoscgi_SYNO.CloudStation.Server.DBUsage_1_get[22042]: [ERROR] request-handler.cpp(432): failed to handle API 'SYNO.CloudStation.Server.DBUsage.get
2020-02-11T16:19:02+01:00 ServeurNAS synoscgi_SYNO.CloudStation.Server.DBUsage_1_get[22632]: [ERROR] dbusage/get.cpp(28): Failed to get cached db usage
2020-02-11T16:19:02+01:00 ServeurNAS synoscgi_SYNO.CloudStation.Server.DBUsage_1_get[22632]: [ERROR] request-handler.cpp(432): failed to handle API 'SYNO.CloudStation.Server.DBUsage.get
2020-02-11T16:59:21+01:00 ServeurNAS synoabk-ctl: [ERROR] sdkcpp.cpp:1504(29511,139787460995072) SYNOShareGet(ActiveBackupforBusiness): -1, Error code 5120
2020-02-11T16:59:21+01:00 ServeurNAS synoabk-ctl: [ERROR] sdkcpp.cpp:1504(29511,139787460995072) SYNOShareGet(ActiveBackupforBusiness): -1, Error code 5120
2020-02-11T16:59:21+01:00 ServeurNAS synoabk-ctl: SYSTEM:       Last message '[ERROR] sdkcpp.cpp:1' repeated 1 times, suppressed by syslog-ng on ServeurNAS
insmod: ERROR: could not insert module /lib/modules/update/crc-ccitt.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/crc-itu-t.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/dca.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/e1000e.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/igb.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/be2net.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ixgbe.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/i40e.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/tn40xx.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/r8168.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/atlantic.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/mdio.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/libcrc32c.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/bnx2x.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/libcrc32c.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/crc-itu-t.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/crc-ccitt.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/dca.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/mii.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/mdio.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/libphy.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/atl1.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/atl1e.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/atl1c.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/alx.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/uio.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ipg.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/jme.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/skge.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/sky2.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ptp_pch.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/pch_gbe.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/qla3xxx.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/qlcnic.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/qlge.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/netxen_nic.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/sfc.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/e1000.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/pcnet32.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/vmxnet3.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/bnx2.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/libcrc32c.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/bnx2x.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/e1000e.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/igb.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/igbvf.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ixgbe.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ixgbevf.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/r8101.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/r8125.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/r8169.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/r8168.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/tg3.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/usbnet.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ax88179_178a.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/button.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/evdev.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ohci-hcd.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ehci-hcd.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ehci-pci.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/atl2.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/e100.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/igbvf.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ixgb.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/forcedeth.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/tn40xx.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/be2net.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/cxgb.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/cxgb3.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/cxgb4.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/atlantic.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/bna.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/vxge.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/aqc111.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/asix.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/cx82310_eth.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/et131x.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/i40e.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/i40evf.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/mcs7830.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/pegasus.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/plusb.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/r8152.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/rtl8150.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/s2io.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/xgmac.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ehci-hcd.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ehci-pci.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ohci-hcd.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/crc-ccitt.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/crc-itu-t.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/dca.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/igb.ko: Unknown symbol in module
insmod: ERROR: could not insert module /lib/modules/update/be2net.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ixgbe.ko: Unknown symbol in module
insmod: ERROR: could not insert module /lib/modules/update/i40e.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/tn40xx.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/atlantic.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/igb.ko: Unknown symbol in module
insmod: ERROR: could not insert module /lib/modules/update/ixgbe.ko: Unknown symbol in module
insmod: ERROR: could not insert module /lib/modules/update/r8101.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/evdev.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/crc-ccitt.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/crc-itu-t.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/dca.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/igb.ko: Unknown symbol in module
insmod: ERROR: could not insert module /lib/modules/update/be2net.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/ixgbe.ko: Unknown symbol in module
insmod: ERROR: could not insert module /lib/modules/update/i40e.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/tn40xx.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/atlantic.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/igb.ko: Unknown symbol in module
insmod: ERROR: could not insert module /lib/modules/update/ixgbe.ko: Unknown symbol in module
insmod: ERROR: could not insert module /lib/modules/update/r8101.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/update/evdev.ko: Invalid module format
insmod: ERROR: could not insert module /lib/modules/syno_hddmon.ko: Operation not permitted
insmod: ERROR: could not insert module /lib/modules/syno_hddmon.ko: Operation not permitted
insmod: ERROR: could not insert module /lib/modules/syno_hddmon.ko: Operation not permitted
2020-02-12T20:13:34+01:00 ServeurNAS synoabk-hook: [ERROR] dsmcache-ipc.cpp:86(24138,139850923961216) connect to '/run/synoabk/synoabk-dsmcache.sock' failed
2020-02-12T20:13:34+01:00 ServeurNAS synoabk-hook: [ERROR] dsmcache-ipc.cpp:232(24138,139850923961216) Failed to notify hook: app_privilege_set_hook
2020-02-12T20:13:35+01:00 ServeurNAS synoabk-hook: [ERROR] dsmcache-ipc.cpp:86(24141,139830965214080) connect to '/run/synoabk/synoabk-dsmcache.sock' failed
2020-02-12T20:13:35+01:00 ServeurNAS synoabk-hook: [ERROR] dsmcache-ipc.cpp:232(24141,139830965214080) Failed to notify hook: app_privilege_set_hook

 

in fact, even the icons in the control panel are no longer displayed.

 

when i try to open the file station or any other application i get the message "operation failed".

or the windows don't even open.

 

the only access i have is ssh.

it would be useful to have the root password.

[DSM in place of ADM.]

it's good, it seems to work. thank you 

[Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+]

it's good, it seems to work. thank you

[Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+]

il y a 3 minutes, IG-88 a dit :

 

maybe try loader 1.04b (supports uefi) for 918+ and try the 0.8 recovery extra/extra2 (+ zImage, rd.gz from 918+ 24922 *.pat file)

 

 

 

the version for the 918+ detected my nas well but there is no serial generator for this model. I can take the same sn as the 3615 or how to do it?

[[Octoprint] Démarrage impossible]

dans :

 

"devices" : [
      {
         "CgroupPermissions" : "rwm",
         "PathInContainer" : "/dev/ttyACM0",
         "PathOnHost" : "/dev/bus/usb/001/005"
      }
   ],

 

c'est bien "rwm" ou "rwx"  ?

[[Octoprint] Démarrage impossible]

je l'ai mis à jour et j'ai un autre message :

 

Connecting to: /dev/ttyACM0 Changing monitoring state from "Offline" to "Error: Connection error, see Terminal tab" Unexpected error while connecting to serial port: /dev/ttyACM0 SerialException: 'Could not configure port: (25, 'Inappropriate ioctl for device')' @ comm.py:_openSerial:2661 (hook default)

[[Octoprint] Démarrage impossible]

Re,

 

alors c'est pas mal, sauf que quand je veux connecter l'imprimante il me met :

 

Changing monitoring state from "Offline" to "Detecting serial port"Serial port list: ['/dev/ttyACM0']Connecting to: /dev/ttyACM0Changing monitoring state from "Detecting serial port" to "Error: Connection error, see Terminal tab"Unexpected error while connecting to serial port: AUTO SerialException: '[Errno 13] could not open port /dev/ttyACM0: [Errno 13] Permission denied: '/dev/ttyACM0'' @ comm.py:_openSerial:2469 (hook default)

 

J'ai bien mis mon /dev/bus/usb/001/002 en chmod 777 -R

[Question sauvegarde]

C'est bon ça fonctionne merci

[[Octoprint] Démarrage impossible]

Quel con, je l'ai fais en plus, mais j'ai pas vue qu'il y avait une ligne device :s j'étais tellement naz aussi ...

[Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+]

I was wrong, I took the pat for the 3615 but it does not work.

[DSM in place of ADM.]

Well, I did a little cleaning in my files and resumed the procedure with the loader 1.03b.
I took the infos from 1.02b (vid, pid, sn and mac) to put them in 1.03b on the first partition, and on the second, I put the modified extra.lzma file and the zimage files and rd.gz from the version 6.2 pat file for the 3615, and it still doesn't work.

[DSM in place of ADM.]

I tried putting the extra.lzma file and the zimage and rd.gz files, but I actually got the wrong pat file. I did not understand the post of IG-88.
I try again.

[DSM in place of ADM.]

but it is functional !!
I'm just looking to be able to update it or reinstall a newer version, that's it.

[DSM in place of ADM.]

suddenly, the fact of adding the file extra.lzma (modified) in the loader 1.02b can bring me what?

[DSM in place of ADM.]

This time, 1.02b with the extra.lzma no longer starts.

[DSM in place of ADM.]

No, I installed the 3615, I'm just mentioning the message from IG-88.
and I know very well what I did, no worries.
Ah, the extra.lzma, I add it directly in 1.02b, right? and with that I could try an update in 6.2?
As for double posts, it is not exactly the same people who created these topics and therefore, if more people are able to help me, it will only be more productive.
I also posted a message in the IG-88 thread.

that is problematic ?

[Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+]

Hi,

 

Here, I can't install a version higher than 6.1.7, my machine is an old nas asustor 3104T (https://www.kitguru.net/professional/networking/simon-crisp/asustor-as3104t-4 -Bay-nas-review/3/).
I tried with the original 1.03b loader, but my station is not detected.
So, I also tried to follow your procedure, by taking the file extra.lzma and the zimage and rd.gz files of the DSM_DS918 + _24922.pat file, but my station is still not detected at startup.

[DSM in place of ADM.]

so, I tried putting the extra.lzma file, found in the first link, as well as the zimage and rd.gz files of the DSM_DS918+_24922.pat file, but my station is still not detected.
Knowing that I already have a version 6.1.7 installed, I don't know if I have to put the 6.2.2 kernels anyway.

[DSM in place of ADM.]

on the other hand, in the page that you showed me, it indicates that there are 2 extra.lzma and extre2.lzma files, except that in the first zip file, for 3615, there is only the extra .lzma and and in the second zip file, which is normally for 3617, the file is no longer available for download.
I continue reading.