Note de ce sujet :
  • Moyenne : 0 (0 vote(s))
  • 1
  • 2
  • 3
  • 4
  • 5
Linknx sur un NAS QNAP.
#18
Le message "segmentation fault" n'est pas bon signe pour ton programme.
Cela signifie que ton application ait "crashé"
Je ne connais pas encore ton OS. Mais en général sous Linux, tu peux
utiliser la commande "ldd </CHEMIN DU PROGRAMME/NOM DU PROGRAMME>" afin
de vérifier que tu ais toutes les dépendances.
Bon courage
piliman

Chrystof wrote:
> Ah voilà j'ai installé libcurl, j'avais oublier !!!
>
> Ca fonctionne, ensin ca note :
>
> Segmentation fault
>
> Donc j'imagine que ca fonctionne.
>
> Super merci beaucoup, reste juste à trouver comment starter eibd et
> linknx automatiquement.
>
> Merci encore.
>
> Chrystof
>
> On 23 juin, 21:01, Chrystof <i...@accessnight.ch> wrote:
>
>> Salut,
>>
>> J'ai mon Ts-109 de QNAP, j'ai tout installé et voici ma config :
>>
>> [/] # dmesg
>> 0 pages, LIFO batch:1
>> HighMem zone: 0 pages, LIFO batch:1
>> Built 1 zonelists
>> Kernel command line: console=ttyS0,115200n8 root=/dev/ram rw
>> initrd=0x800000,0x3fffff
>> PID hash table entries: 2048 (order: 11, 32768 bytes)
>> Console: colour dummy device 80x30
>> Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
>> Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
>> Memory: 128MB 128MB 0MB 0MB = 256MB total
>> Memory: 251904KB available (2941K code, 447K data, 104K init)
>> Calibrating delay loop... 332.59 BogoMIPS (lpj=1662976)
>> Mount-cache hash table entries: 512
>> CPU: Testing write buffer coherency: ok
>> checking if image is initramfs...it isn't (no cpio magic); looks like
>> an initrd
>> Freeing initrd memory: 4095K
>> NET: Registered protocol family 16
>>
>> CPU Interface
>> -------------
>> SDRAM_CS0 ....base 00000000, size 128MB
>> SDRAM_CS1 ....base 10000000, size 128MB
>> SDRAM_CS2 ....disable
>> SDRAM_CS3 ....disable
>> PEX0_MEM ....base e0000000, size 128MB
>> PEX0_IO ....base f2000000, size 1MB
>> PCI0_MEM ....base e8000000, size 128MB
>> PCI0_IO ....base f2100000, size 1MB
>> INTER_REGS ....base f1000000, size 1MB
>> DEVICE_CS0 ....no such
>> DEVICE_CS1 ....base f4000000, size 16MB
>> DEVICE_CS2 ....no such
>> DEV_BOOCS ....base ff800000, size 8MB
>> CRYPTO ENG ....base f0000000, size 64KB
>>
>> Marvell Development Board (LSP Version 1.10.3_DB_NAS)-- RD-88F5182-
>> NAS-2 Soc: 88F5182 A2
>>
>> Detected Tclk 166666667 and SysClk 166666667
>> Marvell USB EHCI Host controller #0: c0573560
>> Marvell USB EHCI Host controller #1: c0573460
>> mvPexTargetWinEnable: Win 1 should be in bar boundries
>> mvPexInit: Can't enable window =1
>> pci_init:Error calling mvPciIfInit for pciIf 0
>> PCI: bus0: Fast back to back transfers enabled
>> PCI: bus1: Fast back to back transfers enabled
>> SCSI subsystem initialized
>> usbcore: registered new driver usbfs
>> usbcore: registered new driver hub
>> QNAP RTC initializing....
>> Initializing RTC is completed.
>> Detected Tclk 166666667, BASE_BAUD 10416666, Baud divisor 542
>> qnap_pic_init: succeed to register misc device
>> tsinfo: create proc systemp successfully
>> tsinfo: create proc systemp successfully
>> Use the XOR engines (offloading) for enhancing the following
>> functions:
>> o RAID 5 Xor calculation
>> o kernel memcpy
>> o kenrel memzero
>> o copy user to/from kernel buffers
>> Number of XOR engines to use: 2
>> cesadev_init(c0011b30)
>> Fast Floating Point Emulator V0.9 © Peter Teichmann.
>> inotify device minor=63
>> VFS: Disk quotas dquot_6.5.1
>> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
>> Installing knfsd (copyright © 1996 o...@monad.swb.de).
>> Initializing Cryptographic API
>> Serial: 8250/16550 driver $Revision: 1.1.1.1 $ 4 ports, IRQ sharing
>> disabled
>> ttyS0 at MMIO 0x0 (irq = 3) is a 16550A
>> io scheduler noop registered
>> io scheduler anticipatory registered
>> io scheduler deadline registered
>> io scheduler cfq registered
>> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
>> loop: loaded (max 8 devices)
>> Marvell Gigabit Ethernet Driver 'egiga':
>> o Ethernet descriptors in DRAM
>> o DRAM SW cache-coherency
>> o Checksum offload enabled
>> o Marvell ethtool proc enabled
>> o Loading network interface 'eth0'
>> STRIP: Version 1.3A-STUART.CHESHIRE (unlimited channels)
>> Intergrated Sata device found
>> Wait 15 seconds to initialize mvAdapter.
>> Spin up ...
>> scsi0 : Marvell SCSI to SATA adapter
>> scsi1 : Marvell SCSI to SATA adapter
>> Vendor: SAMSUNG Model: HD250HJ Rev: FH10
>> Type: Direct-Access ANSI SCSI revision: 03
>> SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
>> SCSI device sda: drive cache: write back
>> SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
>> SCSI device sda: drive cache: write back
>> sda: sda1 sda2 sda3 sda4
>> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
>> Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
>> physmap flash device: 800000 at ff800000
>> phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
>> Intel/Sharp Extended Query Table at 0x0031
>> Using buffer write method
>> cfi_cmdset_0001: Erase suspend on write enabled
>> 0: offset=0x0,size=0x20000,blocks=64
>> cmdlinepart partition parsing not available
>> RedBoot partition parsing not available
>> Using physmap partition definition
>> Creating 6 MTD partitions on "phys_mapped_flash":
>> 0x00780000-0x00800000 : "U-Boot"
>> 0x00000000-0x00200000 : "Kernel"
>> 0x00200000-0x00600000 : "RootFS1"
>> 0x00600000-0x00700000 : "RootFS2"
>> 0x00760000-0x00780000 : "U-Boot Config"
>> 0x00700000-0x00760000 : "NAS Config"
>> ehci_platform ehci_platform.4523: EHCI Host Controller
>> ehci_platform ehci_platform.4523: new USB bus registered, assigned bus
>> number 1
>> ehci_platform ehci_platform.4523: irq 17, io mem 0x00000000
>> ehci_platform ehci_platform.4523: park 0
>> ehci_platform ehci_platform.4523: USB 0.0 initialized, EHCI 1.00,
>> driver 10 Dec 2004
>> hub 1-0:1.0: USB hub found
>> hub 1-0:1.0: 1 port detected
>> ehci_platform ehci_platform.16781: EHCI Host Controller
>> ehci_platform ehci_platform.16781: new USB bus registered, assigned
>> bus number 2
>> ehci_platform ehci_platform.16781: irq 12, io mem 0x00000000
>> ehci_platform ehci_platform.16781: park 0
>> ehci_platform ehci_platform.16781: USB 0.0 initialized, EHCI 1.00,
>> driver 10 Dec 2004
>> hub 2-0:1.0: USB hub found
>> hub 2-0:1.0: 1 port detected
>> ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver
>> (PCI)
>> USB Universal Host Controller Interface driver v2.2
>> usb 2-1: new high speed USB device using ehci_platform and address 2
>> hub 2-1:1.0: USB hub found
>> hub 2-1:1.0: 4 ports detected
>> qh_schedule: frame=255, uframe=0, cmask=0x0, smask=0x1, period=256,
>> u_period=2048
>> usbcore: registered new driver usblp
>> drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
>> usbcore: registered new driver hiddev
>> usbcore: registered new driver usbhid
>> drivers/usb/input/hid-core.c: v2.01:USB HID core driver
>> mice: PS/2 mouse device common for all mice
>> NET: Registered protocol family 2
>> IP: routing cache hash table of 2048 buckets, 16Kbytes
>> TCP established hash table entries: 16384 (order: 5, 131072 bytes)
>> TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
>> TCP: Hash tables configured (established 16384 bind 16384)
>> NET: Registered protocol family 1
>> NET: Registered protocol family 17
>> NET: Registered protocol family 5
>> RAMDISK: Compressed image found at block 0
>> VFS: Mounted root (ext2 filesystem).
>> Freeing init memory: 104K
>> kjournald starting. Commit interval 5 seconds
>> EXT3-fs warning: maximal mount count reached, running e2fsck is
>> recommended
>> EXT3 FS on sda1, internal journal
>> EXT3-fs: mounted filesystem with ordered data mode.
>> kjournald starting. Commit interval 5 seconds
>> EXT3-fs warning: maximal mount count reached, running e2fsck is
>> recommended
>> EXT3 FS on sda1, internal journal
>> EXT3-fs: mounted filesystem with ordered data mode.
>> kjournald starting. Commit interval 5 seconds
>> EXT3 FS on sda4, internal journal
>> EXT3-fs: mounted filesystem with ordered data mode.
>> sysinfo: Module loaded.
>> Initializing USB Mass Storage driver...
>> usbcore: registered new driver usb-storage
>> USB Mass Storage support registered.
>> create proc entry succeed!
>> fuse init (API version 7.8)
>> fuse distribution version: 2.7.3
>> eth0: mac address changed
>> kjournald starting. Commit interval 5 seconds
>> EXT3-fs warning: maximal mount count reached, running e2fsck is
>> recommended
>> EXT3 FS on sda1, internal journal
>> EXT3-fs: mounted filesystem with ordered data mode.
>> Adding 530136k swap on /dev/sda2. Priority:-1 extents:1
>> kjournald starting. Commit interval 5 seconds
>> EXT3 FS on sda3, internal journal
>> EXT3-fs: mounted filesystem with writeback data mode.
>> EXT3-fs: file extents enabled
>> scsi: unknown opcode 0x0c
>> eth0: link down
>> eth0: link up<5>, full duplex<5>, speed 1 Gbps<5>
>> rule type=0, num=0
>>
>> Ensuite sur le QNAP TS-109 j'ai le message suivant quand je démarre
>> linknx :
>>
>> [/] # linknx
>> linknx: error while loading shared libraries: libssl.so.0.9.8: cannot
>> open shared object file: No such file or directory
>>
>> Une idée ?
>>
>> Chrystof
>>
>
>


Messages dans ce sujet
Linknx sur un NAS QNAP. - par Chrystof - 19/06/2009, 13:19:10
Linknx sur un NAS QNAP. - par jef2000 - 20/06/2009, 08:53:47
Linknx sur un NAS QNAP. - par Chrystof - 21/06/2009, 16:42:20
Linknx sur un NAS QNAP. - par jef2000 - 21/06/2009, 22:35:21
Linknx sur un NAS QNAP. - par Chrystof - 22/06/2009, 06:40:06
Linknx sur un NAS QNAP. - par jef2000 - 22/06/2009, 08:19:36
Linknx sur un NAS QNAP. - par Chrystof - 22/06/2009, 08:51:29
Linknx sur un NAS QNAP. - par jef2000 - 22/06/2009, 15:05:04
Linknx sur un NAS QNAP. - par Chrystof - 22/06/2009, 18:02:03
Linknx sur un NAS QNAP. - par jef2000 - 22/06/2009, 19:43:39
Linknx sur un NAS QNAP. - par Chrystof - 22/06/2009, 21:04:41
Linknx sur un NAS QNAP. - par jef2000 - 22/06/2009, 21:56:03
Linknx sur un NAS QNAP. - par jef2000 - 22/06/2009, 22:57:46
Linknx sur un NAS QNAP. - par Chrystof - 23/06/2009, 12:53:40
Linknx sur un NAS QNAP. - par jef2000 - 23/06/2009, 15:19:20
Linknx sur un NAS QNAP. - par Chrystof - 23/06/2009, 20:01:51
Linknx sur un NAS QNAP. - par Chrystof - 23/06/2009, 20:08:56
Linknx sur un NAS QNAP. - par Vincent Aaron - 23/06/2009, 20:51:39
Linknx sur un NAS QNAP. - par Chrystof - 23/06/2009, 21:07:44
Linknx sur un NAS QNAP. - par Chrystof - 24/06/2009, 05:51:38
Linknx sur un NAS QNAP. - par jef2000 - 24/06/2009, 08:48:21
Linknx sur un NAS QNAP. - par Chrystof - 24/06/2009, 12:58:41
Linknx sur un NAS QNAP. - par jef2000 - 24/06/2009, 20:05:12
Linknx sur un NAS QNAP. - par Chrystof - 24/06/2009, 20:38:55
Linknx sur un NAS QNAP. - par jef2000 - 24/06/2009, 22:11:52
Linknx sur un NAS QNAP. - par Chrystof - 25/06/2009, 05:59:23
Linknx sur un NAS QNAP. - par Chrystof - 25/06/2009, 07:30:27
Linknx sur un NAS QNAP. - par Chrystof - 29/06/2009, 17:15:27
Linknx sur un NAS QNAP. - par jef2000 - 30/06/2009, 21:45:20
Linknx sur un NAS QNAP. - par Chrystof - 01/07/2009, 06:10:50
Linknx sur un NAS QNAP. - par jef2000 - 01/07/2009, 08:31:28
Linknx sur un NAS QNAP. - par Chrystof - 01/07/2009, 14:32:40
Linknx sur un NAS QNAP. - par jef2000 - 02/07/2009, 12:31:26
Linknx sur un NAS QNAP. - par Chrystof - 02/07/2009, 16:46:00
Linknx sur un NAS QNAP. - par Chrystof - 06/07/2009, 08:05:03
Linknx sur un NAS QNAP. - par jef2000 - 06/07/2009, 19:13:15
Linknx sur un NAS QNAP. - par seb@leon - 31/07/2009, 06:35:26
Linknx sur un NAS QNAP. - par Chrystof - 31/07/2009, 07:02:33

Atteindre :


Utilisateur(s) parcourant ce sujet : 1 visiteur(s)