Driver manquant pour Ds413j

[nerissonParticipant]

A priori je n’ai pas le driver pour mon Ds413j.

Voici le log d’installation:

admin@DiskStation:/$ more /var/packages/PulseStation/target/log/install.log
06/18/16-10:41:35 Installation started
06/18/16-10:41:39 PulseStation's web interface installed.
06/18/16-10:41:39 DSM Major version : 6.
06/18/16-10:41:40 DSM6 -> Default PulseStation's services installed.
06/18/16-10:41:40 Configuration done.
06/18/16-10:41:41 Shortcut created.
06/18/16-10:41:42 Script to restart application after reboot done.
06/18/16-10:41:42 No drivers for this DSM version - 6.0-7393. You'll not be able to use the Zwave/EnOcean functionnalities. Please contact the Pulse Station team.
admin@DiskStation:/$

Ce qui est curieux puisque cela fonctionnait avant que j’essaye de ré-installer PulseStation.

[Miss LauraModérateur]

Le service zwave, est-ce qu’il voi le clé usb du zwave / enocean?
Car si ça fonctionne, tu peut ignorer le message pendant l’installation.

Have fun,
Laura

[nerissonParticipant]

Non, je n’ai rien pour choisir le port USB sur lequel est branché est la clé.

Par contre je vois bien, en ligne de commande Linux, la clé qui est branchée mais sans driver associé.

[K.RensAdmin bbPress]

Can you put your command and the linux output here?
Please also reach out to us when you see the live chat on the right online, so we can have a look together.

Kind regards,
K.Rens

[nerissonParticipant]

Here is the output:

admin@DiskStation:/$ cat /proc/bus/usb/devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  1, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 2.06
S:  Manufacturer=Linux 2.6.32.12 ehci_hcd
S:  Product=Marvell Orion EHCI
S:  SerialNumber=orion-ehci.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 4
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=05e3 ProdID=0608 Rev=77.63
S:  Product=USB2.0 Hub
S:  SerialNumber=d6a3ebcbfbd5e7a5f6a3
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms

T:  Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  3 Spd=12   MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=10c4 ProdID=ea60 Rev= 1.00
S:  Manufacturer=Silicon Labs
S:  Product=CP2102 USB to UART Bridge Controller
S:  SerialNumber=0001
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
admin@DiskStation:/$

[Miss LauraModérateur]

That’s the usb port, but not the usb device, right?
No specialist here.

The command we normally use to check whether the usb key is detected is following:
dmesg | grep tty

Can you share that output?

Have fun,
Laura

[nerissonParticipant]

It seems that my USB key is not found:

admin@DiskStation:/$ dmesg | grep tty
[    0.000000] Kernel command line: console=ttyS0,115200 ip=off initrd=0x00800040,8M root=/dev/md0 rw syno_hw_version=DS413jv10 ihd_num=4 netif_num=1 flash_size=8
[    5.190000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    5.200000] console [ttyS0] enabled
[    5.200000] serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A

Maybe a bug in DSM 6 ? It worked before

[Miss LauraModérateur]

This is the output you should be getting:
admin@DiskStation:/$ dmesg | grep tty
[ 0.000000] console [ttyS0] enabled
[ 5.517988] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 5.545027] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 102.507682] cdc_acm 7-2:1.0: ttyACM0: USB ACM device

As far as I can see from your output, the usb key itself is no longer recognized by your DSM.
Try unplugging it and plugging it in again and running the same command.
Or try rebooting.
Or try a different USB port.
Or check in the settings whether maybe you disabled the usb port (can you even do that?)

Does the light on the usb key still light up when you plugin the usb key?
Also: there is no need to install additional drivers or packages. PulseStation itself should be sufficient.
Since there are some other packages out there that claim to make your usb key work. 😉

Have fun,
Laura

[nerissonParticipant]

The light on my USB key is light up.
Rebooting don’t help, as changing the USB port.
The key is working fine if I plug it on my computer…

Some people have the same problem after upgrading to DSM 6:
https://forum.synology.com/enu/viewtopic.php?f=12&t=106984

Well, it’s not a PulseStation problem. I’ll contact the Synology support.
Thanks for the help.

[Miss LauraModérateur]

Ok, a long shot here.
We may be able to force your system to support the drivers.
Please execute following commands:

sudo mkdir /var/packages/PulseStation/target/modules/DSM_6.0-7393/
sudo cp -R /var/packages/PulseStation/target/modules/DSM_6.0-7321/* /var/packages/PulseStation/target/modules/6.0-7393/
sudo sh /var/packages/PulseStation/scripts/postinst

No clue whether this will work or not, but please share the output.

Other users: do not try this at home 🙂

• Cette réponse a été modifiée le il y a 1 an et 10 mois par  Miss Laura.

Have fun,
Laura

[nerissonParticipant]

Well well well 🙂

admin@DiskStation:/$ dmesg | grep tty
[    0.000000] Kernel command line: console=ttyS0,115200 ip=off initrd=0x00800040,8M root=/dev/md0 rw syno_hw_version=DS413jv10 ihd_num=4 netif_num=1 flash_size=8
[    5.190000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    5.200000] console [ttyS0] enabled
[    5.200000] serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
[  151.920000] usb 1-1.2: cp210x converter now attached to ttyUSB0
admin@DiskStation:/$

And the USB key is available in PulseStation, my Zwave service is OK.

BUT to make it work: I have to update the installation script because it cannot be launched under ‘root’, some environnement variables are not available (SYNOPKG_DSM_VERSION_MAJOR, SYNOPKG_DSM_VERSION_MINOR, SYNOPKG_DSM_VERSION_BUILD, SYNOPKG_DSM_ARCH). Maybe you can add some checks at the start of the script, because it has created some files/folders at a wrong place).

Big thanks !

[K.RensAdmin bbPress]

What did you precisely change?
Then we can do that for others as well.

Glad we pointed you in the right direction and at the same time found some improvement options.

Kind regards,
K.Rens

[nerissonParticipant]

I’ve added this lines at the top of “postinst” script:

SYNOPKG_DSM_VERSION_MAJOR=6
SYNOPKG_DSM_VERSION_MINOR=0
SYNOPKG_DSM_VERSION_BUILD=7393
SYNOPKG_DSM_ARCH=88f6281

Of course they are specifics to my Syno.

[Auteur]

Messages