Fiio X3 II - QNAP 251a

Please post your questions about using the web-based Photo, Music, Video Stations here.
clementBoissy
New here
Posts: 9
Joined: Wed Jan 11, 2017 1:51 am

Fiio X3 II - QNAP 251a

Postby clementBoissy » Wed Jan 11, 2017 2:20 am

Hi !

I own a Fiio X3 II for portable music and this one can also be used as DAC. I hacve seen that the Fiio E18 can be used as well with my NAS 251a. I try but it doesn't work. However, I tried a lsusb to see if the NAS see the Fiio. The return is :

[~] # lsusb
Bus 001 Device 002: ID 2972:0003
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

The Fiio is seenable as 2972:0003 but that it.

Does anyone can help ?

User avatar
OneCD
Experience counts
Posts: 3050
Joined: Sun Aug 21, 2016 10:48 am
Location: over there, behind that sofa...

Re: Fiio X3 II - QNAP 251a

Postby OneCD » Wed Jan 11, 2017 2:27 am

clementBoissy wrote:The Fiio is seenable as 2972:0003 but that it.

Which probably means it's unsupported. ;)

How does your dmesg log look when you connect your device?

Clear it first:

Code: Select all

dmesg -c > /dev/null

then connect your device, wait a few seconds, and check it again.

Code: Select all

dmesg

I've switched to pure Debian on my production NAS (TS-569 Pro), with the backup NAS (TS-559 Pro+) to follow, so I'll no longer be able to use or support QNAP's firmware. This means no more closed-source software, "Malware Removers", etc ... If you have the means, I highly recommend it. Powerup/poweroff times are < 1 minute. :D

one.cd.only@gmail.com

clementBoissy
New here
Posts: 9
Joined: Wed Jan 11, 2017 1:51 am

Re: Fiio X3 II - QNAP 251a

Postby clementBoissy » Wed Jan 11, 2017 2:49 am

and the return :

Code: Select all

[   47.161380] md9: detected capacity change from 0 to 542769152
[   48.184935]  md9: unknown partition table
[   48.258842] kjournald starting.  Commit interval 5 seconds
[   48.266199] EXT3-fs (md9): using internal journal
[   48.270980] EXT3-fs (md9): mounted filesystem with ordered data mode
[   48.374458] md: md13 stopped.
[   48.381094] md: bind<sda4>
[   48.385439] md/raid1:md13: active with 1 out of 24 mirrors
[   48.391117] created bitmap (1 pages) for device md13
[   48.396263] md13: bitmap initialized from disk: read 1 pages, set 7 of 8 bits
[   48.488610] md13: detected capacity change from 0 to 469893120
[   48.616108] qnap_power_pin qnap_power_pin: powerup rtl8153::powerup value reads back 1
[   59.911313] md: bind<sda2>
[   59.915013] md/raid1:md256: active with 1 out of 2 mirrors
[   59.920610] created bitmap (1 pages) for device md256
[   59.925768] md256: bitmap initialized from disk: read 1 pages, set 9 of 9 bits
[   59.936546] md256: detected capacity change from 0 to 542834688
[   59.959375]  md256: unknown partition table
[   59.988528] Adding 530108k swap on /dev/md256.  Priority:-1 extents:1 across:530108k
[   60.084484] md: md1 stopped.
[   60.092865] md: bind<sda3>
[   60.096536] md/raid1:md1: active with 1 out of 1 mirrors
[   60.101996] md1: detected capacity change from 0 to 1990205046784
[   60.116571]  md1: unknown partition table
[   60.365192] drbd r1: Starting worker thread (from drbdsetup-84 [3389])
[   60.371934] block drbd1: disk( Diskless -> Attaching )
[   60.377345] drbd r1: Method to ensure write ordering: flush
[   60.382924] block drbd1: Adjusting my ra_pages to backing device's (32 -> 1024)
[   60.390227] block drbd1: drbd_bm_resize called with capacity == 3887118136
[   60.397234] block drbd1: resync bitmap: bits=3796014 words=59313 pages=116
[   60.404097] block drbd1: size = 1854 GB (1943559068 KB)
[   60.421680] block drbd1: recounting of set bits took additional 1 jiffies
[   60.428459] block drbd1: 1854 GB (3796014 bits) marked out-of-sync by on disk bit-map.
[   60.436374] block drbd1: Suspended AL updates
[   60.440744] block drbd1: disk( Attaching -> UpToDate )
[   60.445967] block drbd1: attached to UUIDs 29520CA68BC49127:0000000000000004:0000000000000000:0000000000000000
[   60.465386] drbd r1: conn( StandAlone -> Unconnected )
[   60.470650] drbd r1: Starting receiver thread (from drbd_w_r1 [3390])
[   60.477138] drbd r1: receiver (re)started
[   60.481188] drbd r1: conn( Unconnected -> WFConnection )
[   61.505206] drbd r1: conn( WFConnection -> Disconnecting )
[   61.505220] drbd r1: Discarding network configuration.
[   61.515991] drbd r1: Connection closed
[   61.519803] drbd r1: conn( Disconnecting -> StandAlone )
[   61.525202] drbd r1: receiver terminated
[   61.529142] drbd r1: Terminating drbd_r_r1
[   61.536644] block drbd1: role( Secondary -> Primary )
[   61.687363]  md13: unknown partition table
[   64.186507] flashcache flashcache_ctr
[   64.190396] flashcache flashcache_ctr end slot id 1 dev /dev/mapper/vg288-lv1
[   65.387072] EXT4-fs (dm-0): Mount option "noacl" will be removed by 3.5
[   65.387072] Contact linux-ext4@vger.kernel.org if you think we should keep it.
[   65.387072]
[   65.469458] ext4_init_reserve_inode_table0: dm-0, 14680
[   65.474696] ext4_init_reserve_inode_table2: dm-0, 14680, 0, 0, 4096
[   65.483080] EXT4-fs (dm-0): recovery complete
[   65.487468] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,jqfmt=vfsv0,user_xattr,data=ordered,delalloc,noacl
[   66.571766] Adding 16777212k swap on /share/CACHEDEV1_DATA/.swap/qnap_swap.  Priority:-2 extents:16 across:17899516k
[   68.810771] EXT2-fs (mmcblk0p1): error: can't find an ext2 filesystem on dev mmcblk0p1.
[   68.904153] EXT2-fs (mmcblk0p1): error: can't find an ext2 filesystem on dev mmcblk0p1.
[   79.848337] EXT2-fs (mmcblk0p1): error: can't find an ext2 filesystem on dev mmcblk0p1.
[   79.940228] EXT2-fs (mmcblk0p1): error: can't find an ext2 filesystem on dev mmcblk0p1.
[   80.238853] kjournald starting.  Commit interval 5 seconds
[   80.337250] EXT3-fs (md13): using internal journal
[   80.342060] EXT3-fs (md13): mounted filesystem with ordered data mode
[   90.848944] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[   90.856098] iTCO_wdt: Found a Braswell SoC TCO device (Version=3, TCOBASE=0x0460)
[   90.864042] iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
[   90.886487] fnotify: Load file notify kernel module.
[   90.891884] fnotify: Launch the fnotify thread: 18446612134340354064
[   91.941872] snd_usb_audio: unknown parameter 'qnap_start_index' ignored
[   91.952731] usb 1-2: 0:2 : does not exist
[   91.959755] usbcore: registered new interface driver snd-usb-audio
[   91.969684] usbcore: registered new interface driver snd-usb-caiaq
[   91.984047] usbcore: registered new interface driver uvcvideo
[   91.989807] USB Video Class driver (1.1.1)
[   92.030677] 8021q: 802.1Q VLAN Support v1.8
[  118.623707] eth0: 0xffffc9000031a000, 24:5e:be:02:a8:11, IRQ 319
[  118.668473] eth1: 0xffffc9000035e000, 24:5e:be:02:a8:12, IRQ 320
[  118.716581] eth2: 0xffffc90000376000, 24:5e:be:02:af:e1, IRQ 321
[  121.673986] r8168: eth0: link up
[  126.884786] IPv6: Loaded, but administratively disabled, reboot required to enable
[  126.913733] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[  126.937104] Bridge firewalling registered
[  127.045477] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
[  127.051847] MII link monitoring set to 100 ms
[  127.685242] r8168: eth0: link down
[  130.318723] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[  130.326640] NFSD: starting 90-second grace period (net ffffffff81bea540)
[  131.719632] r8168: eth0: link up
[  135.646489] nfsd: last server has exited, flushing export cache
[  137.018980] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[  137.026831] NFSD: starting 90-second grace period (net ffffffff81bea540)
[  140.887144] fbdisk: module loaded, major number = 252.
[  140.892292] fbdisk: module loaded, major number = 251.
[  141.656355] Loading iSCSI transport class v2.0-870.
[  141.670654] iscsi: registered transport (tcp)
[  176.502301] capability: warning: `proftpd' uses 32-bit capabilities (legacy support in use)
[  178.489581] Bluetooth: Core ver 2.20
[  178.498744] NET: Registered protocol family 31
[  178.503223] Bluetooth: HCI device and connection manager initialized
[  178.509635] Bluetooth: HCI socket layer initialized
[  178.522077] Bluetooth: L2CAP socket layer initialized
[  178.530982] Bluetooth: SCO socket layer initialized
[  178.558881] usbcore: registered new interface driver btusb
[  229.904398] PPP generic driver version 2.4.2
[  229.951637] tun: Universal TUN/TAP device driver, 1.6
[  229.956708] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[  229.957164] PPP MPPE Compression module registered
[  229.974279] PPP BSD Compression module registered
[  229.993662] PPP Deflate Compression module registered
[  233.875035] nfsd: last server has exited, flushing export cache
[  239.783928] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[  239.792421] NFSD: starting 90-second grace period (net ffffffff81bea540)
[  240.988661] Set msys_nodify as 6300
[  254.837282] usbcore: registered new interface driver cdc_acm
[  254.842952] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[  256.099857] systemd-udevd[19823]: starting version 204
[  256.370264] udevd[20968]: could not open moddep file '/lib/modules/3.19.8/modules.dep.bin'
[  256.725083] udevd[20611]: could not open moddep file '/lib/modules/3.19.8/modules.dep.bin'

User avatar
OneCD
Experience counts
Posts: 3050
Joined: Sun Aug 21, 2016 10:48 am
Location: over there, behind that sofa...

Re: Fiio X3 II - QNAP 251a

Postby OneCD » Wed Jan 11, 2017 3:08 am

OK, remove your device, clear the dmesg log and try again. ;)

I've switched to pure Debian on my production NAS (TS-569 Pro), with the backup NAS (TS-559 Pro+) to follow, so I'll no longer be able to use or support QNAP's firmware. This means no more closed-source software, "Malware Removers", etc ... If you have the means, I highly recommend it. Powerup/poweroff times are < 1 minute. :D

one.cd.only@gmail.com

clementBoissy
New here
Posts: 9
Joined: Wed Jan 11, 2017 1:51 am

Re: Fiio X3 II - QNAP 251a

Postby clementBoissy » Wed Jan 11, 2017 3:34 am

I don't understand why, but, if I want the device recognize as DAC, I need to restart the NAS...

User avatar
OneCD
Experience counts
Posts: 3050
Joined: Sun Aug 21, 2016 10:48 am
Location: over there, behind that sofa...

Re: Fiio X3 II - QNAP 251a

Postby OneCD » Wed Jan 11, 2017 3:46 am

clementBoissy wrote:I don't understand why, but, if I want the device recognize as DAC, I need to restart the NAS...

I don't understand why you're restarting the NAS - unless you're saying that this fixed the problem?

I suggested you clear the dmesg log. And I gave you the command to do that. I never suggested restarting the NAS. ;)

I've switched to pure Debian on my production NAS (TS-569 Pro), with the backup NAS (TS-559 Pro+) to follow, so I'll no longer be able to use or support QNAP's firmware. This means no more closed-source software, "Malware Removers", etc ... If you have the means, I highly recommend it. Powerup/poweroff times are < 1 minute. :D

one.cd.only@gmail.com

clementBoissy
New here
Posts: 9
Joined: Wed Jan 11, 2017 1:51 am

Re: Fiio X3 II - QNAP 251a

Postby clementBoissy » Wed Jan 11, 2017 3:52 am

Yes, I know ! But without restarting (which is fixing the problem for the recognition) the dmesg is empty...

User avatar
OneCD
Experience counts
Posts: 3050
Joined: Sun Aug 21, 2016 10:48 am
Location: over there, behind that sofa...

Re: Fiio X3 II - QNAP 251a

Postby OneCD » Wed Jan 11, 2017 3:56 am

clementBoissy wrote:Yes, I know ! But without restarting (which is fixing the problem for the recognition) the dmesg is empty...

OK, so let's recap:

  1. You unplugged your Fiio X3 II device from your NAS,
  2. You cleared the dmesg log,
  3. You then connected your Fiio X3 II device to the NAS,
  4. You then waited a few seconds,
  5. You then check the dmesg log,
  6. and you're saying the dmesg log is still empty.
Is this correct?

I've switched to pure Debian on my production NAS (TS-569 Pro), with the backup NAS (TS-559 Pro+) to follow, so I'll no longer be able to use or support QNAP's firmware. This means no more closed-source software, "Malware Removers", etc ... If you have the means, I highly recommend it. Powerup/poweroff times are < 1 minute. :D

one.cd.only@gmail.com

clementBoissy
New here
Posts: 9
Joined: Wed Jan 11, 2017 1:51 am

Re: Fiio X3 II - QNAP 251a

Postby clementBoissy » Wed Jan 11, 2017 4:18 am

Totally. In fact, usually, when the Fiio is acting like a DAC the screen change and now it don't. I found some issue with Linux distrib. (UBUNTU)

http://askubuntu.com/questions/544843/i ... untu-14-04

It seems that alsa need to be restart or something like that.

User avatar
OneCD
Experience counts
Posts: 3050
Joined: Sun Aug 21, 2016 10:48 am
Location: over there, behind that sofa...

Re: Fiio X3 II - QNAP 251a

Postby OneCD » Wed Jan 11, 2017 4:43 am


I've switched to pure Debian on my production NAS (TS-569 Pro), with the backup NAS (TS-559 Pro+) to follow, so I'll no longer be able to use or support QNAP's firmware. This means no more closed-source software, "Malware Removers", etc ... If you have the means, I highly recommend it. Powerup/poweroff times are < 1 minute. :D

one.cd.only@gmail.com

clementBoissy
New here
Posts: 9
Joined: Wed Jan 11, 2017 1:51 am

Re: Fiio X3 II - QNAP 251a

Postby clementBoissy » Wed Jan 11, 2017 4:54 am

Ok. I understood that it can work (eventually), but do you think it could with the NAS ? I know a bit Linux (as user) but not NAS systems...

clementBoissy
New here
Posts: 9
Joined: Wed Jan 11, 2017 1:51 am

Re: Fiio X3 II - QNAP 251a

Postby clementBoissy » Wed Jan 11, 2017 4:58 am

An thanks for your help

User avatar
OneCD
Experience counts
Posts: 3050
Joined: Sun Aug 21, 2016 10:48 am
Location: over there, behind that sofa...

Re: Fiio X3 II - QNAP 251a

Postby OneCD » Wed Jan 11, 2017 4:59 am

clementBoissy wrote:Ok. I understood that it can work (eventually), but do you think it could with the NAS ? I know a bit Linux (as user) but not NAS systems...

Couldn't say. The NAS seems to be derived from Ubuntu, but QNAP modify it a lot. So, it's no longer a regular Linux system. Which makes sense as all QNAP needed was an embedded OS.

Best to create a support ticket with QNAP and ask them. :geek:

I've switched to pure Debian on my production NAS (TS-569 Pro), with the backup NAS (TS-559 Pro+) to follow, so I'll no longer be able to use or support QNAP's firmware. This means no more closed-source software, "Malware Removers", etc ... If you have the means, I highly recommend it. Powerup/poweroff times are < 1 minute. :D

one.cd.only@gmail.com

clementBoissy
New here
Posts: 9
Joined: Wed Jan 11, 2017 1:51 am

Re: Fiio X3 II - QNAP 251a

Postby clementBoissy » Wed Jan 11, 2017 5:02 am

Ok, I will. Thanks

tmp_911
Starting out
Posts: 13
Joined: Tue Jan 26, 2016 10:07 pm

Re: Fiio X3 II - QNAP 251a

Postby tmp_911 » Wed Oct 11, 2017 2:19 am

clementBoissy wrote:Ok, I will. Thanks


hello, could you please tell if you created that ticket? what was the answer? did you managed to make fiio x3 work with qnap NAS?


Return to “Photo Station, Music Station, Video Station”

Who is online

Users browsing this forum: No registered users and 1 guest