Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Users / Raspberry Pi v3 as media director - slow nfs speed
« Last post by G.I.R. on August 17, 2016, 03:24:36 pm »
Hy,

i had some time and tried to use a new RPiB 3 as a media director.
the installation went fine and the md boots flawlessly.
But whenever i try to watch some media or listen to some music the only thing i can see or hear is a short fraction of the media and then it ends.

i have found this error in /var/log/syslog on the md:
Code: [Select]
Aug 17 14:43:12 moon97 kernel: [19352.261755] nfs: server 192.168.80.1 not responding, timed out
I did some speedtest with iperf and that looks good:
Code: [Select]
root@moon97:~# iperf -c 192.168.80.1
------------------------------------------------------------
Client connecting to 192.168.80.1, TCP port 5001
TCP window size: 43.8 KByte (default)
------------------------------------------------------------
[  3] local 192.168.80.4 port 42484 connected with 192.168.80.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec   112 MBytes  94.3 Mbits/sec

so i tried to copy a file with scp from the router to the md and got 10.0MB/s.

and now it becomes really strange.
if i mount the nfs shares in this way:

Code: [Select]
root@moon97:~# mount -v -t nfs 192.168.80.1:/home/ /test/                                                         
mount.nfs: timeout set for Wed Aug 17 14:44:36 2016
mount.nfs: trying text-based options 'vers=4,addr=192.168.80.1,clientaddr=192.168.80.4'

the speed of copying a file is really really slow.

if i do it like that:
Code: [Select]
root@moon97:~# mount -v -t nfs 192.168.80.1:/home/public/data/videos/2.00\ TB\ \(sda1\)\ WDC_WD30EFRX-68\ \[58\]/TV/Family_Guy/ /test/
mount.nfs: timeout set for Wed Aug 17 14:46:19 2016
mount.nfs: trying text-based options 'vers=4,addr=192.168.80.1,clientaddr=192.168.80.4'
mount.nfs: mount(2): No such file or directory
mount.nfs: trying text-based options 'addr=192.168.80.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.80.1 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.80.1 prog 100005 vers 3 prot UDP port 52139

the speed is normal and i can copy a 100mb file in a few seconds.

the zotac zbox which is my standard md in that room has no problems dealing with any media.
i also switched the network cable without success.

Does anybody has a hint what i am doing wrong or what i can do better?
Maybe it is time to call an exorcist?  :)

LinuxMCE Version: 2.0.0.47.201607240235+899786ab
LMCE 14.04
12
Installation issues / Re: Does the WebDT 366 work with 1404?
« Last post by cafedumonde on August 17, 2016, 03:29:15 am »

That did it. I just daisy-chained another access point to a port on my 802.11n router which is configured as an access point on the internal network. Its great to have all of my old gear back in action. Thanks.

CDM
13
Installation issues / Re: Denon Receiver Control over Ethernet
« Last post by phenigma on August 17, 2016, 01:54:41 am »
As soon as I have a moment to I will have a look.

Sent from my Nexus 5 using Tapatalk

14
Installation issues / Re: Denon Receiver Control over Ethernet
« Last post by cafedumonde on August 17, 2016, 01:35:22 am »

Phenegma,

Please follow up on your comment regarding $?. Please check the file for this script in your installation. I did not change this.

After many days, the detection script has not run. Is there a way to trigger?

CDM
15
Installation issues / Re: Does the WebDT 366 work with 1404?
« Last post by posde on August 15, 2016, 04:52:50 am »
Works for me on 1404 with the same image that runs since forever. Make sure you have 802.11b
16
Installation issues / Does the WebDT 366 work with 1404?
« Last post by cafedumonde on August 14, 2016, 03:55:11 pm »

I have a WebDT 366 loaded with the webpad orbiter image, previously associated with my old 810 system. It has not been used in years. I have revived it but it is not seen by my new 1404 installation. Following the instructions on the wiki, I have updated the wireless settings but still no luck. Questions are:

1. Should this work?
2. Is there an updated version of the image that should work?
3. Following the link on the wiki, the image is no longer posted. Is it still available?
4. What are suggested next steps?

Currently, the pad is charged, boots the old image without errors and stops with the LMCE splash screen and an X Windows cursor that responds to the touch pad.

Thanks,

CDM
17
Installation issues / Re: Denon Receiver Control over Ethernet
« Last post by phenigma on August 13, 2016, 10:41:18 pm »
You're issue $? incorrectly.  I'm on my phone an really unable to respond more than that.  I'll try to elaborate whenever I get home.

Sent from my Nexus 5 using Tapatalk

18
Installation issues / Re: Zoom & Aspect Controls In Xine Not Working
« Last post by phenigma on August 13, 2016, 10:37:41 pm »
I believe this is an issue in libxine.  The orbiter controls are passed to the player but only work with certain video types.

Sent from my Nexus 5 using Tapatalk

19
Installation issues / Re: Video Quality & Sound with Intel Drivers
« Last post by phenigma on August 13, 2016, 10:36:28 pm »
Glad to here it!  Have fun!

Sent from my Nexus 5 using Tapatalk

20
Installation issues / Re: Denon Receiver Control over Ethernet
« Last post by cafedumonde on August 13, 2016, 09:32:22 pm »

More progress but still no prize...

I modified the Denon detection script /usr/pluto/pnp/20_DenonReceiver.sh to create a tool for testing the detection. I found that it only works intermittently on my machine. The detection depends on the contents of "$?" in the script after sending a command over the serial port to the Denon.

The test script, DenonPNPTest.sh

Code: [Select]

#!/bin/bash                                                                                                                             

echo "Denon Detection script queue $2"
echo "Arg1=$1 Arg2=$2 Arg3=$3 Arg4=$4"
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 9600 -t "PWSTANDBY\r\s500mPWON\r" -i 1 -s "MON\r"
if [[ "$?" -ne 0 ]]; then
echo "It's not a Denon Receiver Resp=$?"
# /usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 0                                                               
else
echo "It is a Denon Receiver Resp=$?"
# /usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 71                                                               
fi


 And the output of several runs, with lines added in between for readability....

Code: [Select]

root@dcerouter:/usr/pluto/pnp# ./DenonPNPTest.sh foo foo /dev/ttyS5 foo
Denon Detection script queue foo
Arg1=foo Arg2=foo Arg3=/dev/ttyS5 Arg4=foo
It's not a Denon Receiver Resp=!!0

root@dcerouter:/usr/pluto/pnp# !!
./DenonPNPTest.sh foo foo /dev/ttyS5 foo
Denon Detection script queue foo
Arg1=foo Arg2=foo Arg3=/dev/ttyS5 Arg4=foo
PWSTANDBY\rZMOFF\rZ2OFF\rPWON\rZMON\rZ2ON\r
It is a Denon Receiver Resp=1

root@dcerouter:/usr/pluto/pnp# !!
./DenonPNPTest.sh foo foo /dev/ttyS5 foo
Denon Detection script queue foo
Arg1=foo Arg2=foo Arg3=/dev/ttyS5 Arg4=foo
It's not a Denon Receiver Resp=0

root@dcerouter:/usr/pluto/pnp# !!
./DenonPNPTest.sh foo foo /dev/ttyS5 foo
Denon Detection script queue foo
Arg1=foo Arg2=foo Arg3=/dev/ttyS5 Arg4=foo
It's not a Denon Receiver Resp=0

root@dcerouter:/usr/pluto/pnp# !!
./DenonPNPTest.sh foo foo /dev/ttyS5 foo
Denon Detection script queue foo
Arg1=foo Arg2=foo Arg3=/dev/ttyS5 Arg4=foo
It's not a Denon Receiver Resp=0

root@dcerouter:/usr/pluto/pnp#


Could it be that the command is somehow taking too long to populate "$?"  ???

I am not a bash scripter but could I just capture the string returned directly from the serial port test and decide the detection on that? It is frustrating that "$?" does not work reliably given that it is a standard bash scripting feature.

Feedback from developers would be appreciated. Thanks.

CDM
Pages: 1 [2] 3 4 ... 10