Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - G.I.R.

Pages: [1] 2 3
1
Users / Timed Events / Play Media via Raspberry Pi
« on: December 02, 2016, 11:26:06 am »
Hello,

now as i got this silent and fabulous media director doing his job, the next step would be using it for timed events.

I used the commands "Load Playlist" and "MH Set Volume" with Media Plug-in for my zotac zbox.

It seems that this is not working with the Raspberry.

Then i thought using the OMX Player Plugin would be the right way but i am a little bit confused about the configuration and cannot get it to work.
I have looked into the DCErouter.log if i can find something usefull when i start playing media with an orbiter but i cannot figure out what to use.

Can somebody give me a hint?
Is this possible?


2
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: December 02, 2016, 10:22:07 am »
phenigma, You were right, sorry!
it had been a problem with a/my router/switch...

i have changed my thread to "solved".
https://forum.linuxmce.org/index.php?topic=14392.msg103522#msg103522

mea culpa....sorry


3
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 25, 2016, 07:10:25 pm »
good news!   :D
i made a fresh installation today and there it works perfectly.
I can even see the rainbow now at the start.  :)

i could only found pluto-boot-scripts. is that the right one?

i compared the version of the new installation
https://paste.ubuntu.com/23230006/

with my "old" installation:
https://paste.ubuntu.com/23230134/

don`t know whats wrong with my old installation...

now i only have my old problems with my new installation, that i cannot listen to any music or see any video from my hybrid/core.
i think it is again the low nfs-speed.
will investigate that problem now. ( will try to watch something from another location than my media hd in my core )

So thank You very much for You help and Your work!
Q.E.D. It works!  :)


Shall i provide any more information or should i just switch to my new installation?



4
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 25, 2016, 01:32:58 pm »
hey, then there is hope on the horizont! :)

i did a

Code: [Select]
apt-get update
apt-get dist-upgrade

and then i ran DHCP_Config.sh:

Code: [Select]
dcerouter_1047514:/home/linuxmce# /usr/pluto/bin/DHCP_config.sh
2
20282 So 25. Sep 13:07:01 CEST 2016 WaitLock 'PlutoDHCP' (PlutoDHCP_config)
20282 So 25. Sep 13:07:01 CEST 2016 WaitLock 'PlutoDHCP' (PlutoDHCP_config) success
Device 1 has bad mac address
isc-dhcp-server stop/waiting
isc-dhcp-server start/running, process 20466
20282 So 25. Sep 13:07:01 CEST 2016 Unlock 'PlutoDHCP' (PlutoDHCP_config)
20282 So 25. Sep 13:07:01 CEST 2016 Unlock 'PlutoDHCP' (PlutoDHCP_config) success

is the warning about the mac adress normal?

but dhcpd.conf looks exactly the same:
http://paste.ubuntu.com/23228904/

there were no lmce packets shown to update.
maybe there is something wrong with my sources list?
https://paste.ubuntu.com/23228881/


5
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 24, 2016, 08:21:56 am »
good morning!

this is /etc/dhcp/dhcpd.conf
http://paste.ubuntu.com/23223444/

and this is the output of tcpdump:

Code: [Select]
dcerouter_1047514:/home/linuxmce# tcpdump -i eth1 -vv | grep "tftp"
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
    0.0.0.0.49153 > 0.0.0.0.tftp: [no cksum]  35 RRQ "71638953/start.elf" octet tsize 0
    0.0.0.0.49154 > 0.0.0.0.tftp: [no cksum]  29 RRQ "autoboot.txt" octet tsize 0
    0.0.0.0.49155 > 0.0.0.0.tftp: [no cksum]  27 RRQ "config.txt" octet tsize 0
    0.0.0.0.49156 > 0.0.0.0.tftp: [no cksum]  29 RRQ "recovery.elf" octet tsize 0
    0.0.0.0.49157 > 0.0.0.0.tftp: [no cksum]  26 RRQ "start.elf" octet tsize 0
    0.0.0.0.49158 > 0.0.0.0.tftp: [no cksum]  26 RRQ "fixup.dat" octet tsize 0
          file "/tftpboot/pxelinux.0"

sorry, need to figure out howto use pastebinit with tcpdump...


6
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 23, 2016, 11:21:48 pm »
hmm, sorry no luck.

just to be sure not to make any stupid mistakes somewhere:
i installed the linux-image-default-raspbian-jessie_4.4.17-v7+-lmce5_all.deb with dpkg -i.
then i made a new diskless image.
i copied the diskless image to the sdcard:
Code: [Select]
dd bs=4M if=2016-09-20-netboot-lmce.img of=/dev/sdbstarted the raspberry.
it boots, doing the programming things and then it reboots (sdcard still inside).
but all i can see at this time is "no signal".

tcpdump i showing this:
Code: [Select]
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
    192.168.80.198.49153 > 0.0.0.0.tftp: [no cksum]  35 RRQ "71638953/start.elf" octet tsize 0
    192.168.80.198.49154 > 0.0.0.0.tftp: [no cksum]  29 RRQ "autoboot.txt" octet tsize 0
    192.168.80.198.49155 > 0.0.0.0.tftp: [no cksum]  27 RRQ "config.txt" octet tsize 0
    192.168.80.198.49156 > 0.0.0.0.tftp: [no cksum]  29 RRQ "recovery.elf" octet tsize 0
    192.168.80.198.49157 > 0.0.0.0.tftp: [no cksum]  26 RRQ "start.elf" octet tsize 0
    192.168.80.198.49158 > 0.0.0.0.tftp: [no cksum]  26 RRQ "fixup.dat" octet tsize 0

Should the other files You had in Your tcpdump and that gets transferred be also in the /tftboot/ folder?

I will try to install a shiny new linuxmce system on sunday on my old 12.04 partition.
maybe i wrecked something else...

thanks again!

7
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 23, 2016, 10:09:04 am »
okay thanks.

the last boot attempts i was using the sdcard from the wiki.

but  it didn`t show the rainbow. my lcd is just saying "no signal".

i will try to reinstall the default image and report back.

there must be away.... :)

8
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 22, 2016, 10:31:26 am »
Hello,

i tried the sd card provided by the wiki.
But with no luck.

And i run DHCP_config.sh and restarted the service.
It just won`t boot.

I did a tcpdump again.
Searching with wireshark for DHCP, this is what i found:

Code: [Select]
1081 24.256112 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
1167 29.594817 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
1201 30.596061 192.168.80.1 192.168.80.143 DHCP 342 DHCP Offer    - Transaction ID 0x26f30339
1300 35.592479 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
1319 36.593282 192.168.80.1 192.168.80.144 DHCP 342 DHCP Offer    - Transaction ID 0x26f30339
1390 40.592633 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
1421 41.594131 192.168.80.1 192.168.80.145 DHCP 342 DHCP Offer    - Transaction ID 0x26f30339
1908 45.592694 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
2003 46.593630 192.168.80.1 192.168.80.146 DHCP 342 DHCP Offer    - Transaction ID 0x26f30339


Edit:
Found this, filtering for the raspberrys mac:

Code: [Select]
1328 43.276709 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
1344 44.278321 192.168.80.1 192.168.80.140 DHCP 342 DHCP Offer    - Transaction ID 0x26f30339
1458 48.276786 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
1474 49.278368 192.168.80.1 192.168.80.141 DHCP 342 DHCP Offer    - Transaction ID 0x26f30339
1558 54.276634 192.168.80.141 0.0.0.0 TFTP 77 Read Request, File: 71638953/start.elf, Transfer type: octet, tsize=0
1583 55.293906 192.168.80.141 0.0.0.0 TFTP 71 Read Request, File: autoboot.txt, Transfer type: octet, tsize=0
1609 56.294059 192.168.80.141 0.0.0.0 TFTP 69 Read Request, File: config.txt, Transfer type: octet, tsize=0
1627 57.294111 192.168.80.141 0.0.0.0 TFTP 71 Read Request, File: recovery.elf, Transfer type: octet, tsize=0
1640 58.294142 192.168.80.141 0.0.0.0 TFTP 68 Read Request, File: start.elf, Transfer type: octet, tsize=0
1666 59.913080 192.168.80.141 0.0.0.0 TFTP 68 Read Request, File: fixup.dat, Transfer type: octet, tsize=0

Destination/Source is the mac-address of my raspberry.

I hope this is of any help. i am definitly in no way an expert.
just playing around.

Thanks for Your time!


9
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 21, 2016, 06:28:25 pm »
thanks for the quick reply.

here is the pastebin (ls -lah /tftpboot/)

http://paste.ubuntu.com/23211976/

and this is /tftboot/rpi

http://paste.ubuntu.com/23211995/

i deleted the manually created device (moon142) via webadmin.

is it okay that there is still this link:
Code: [Select]
boot -> /usr/pluto/diskless/142/boot
i tried booting with a sdcard only having bootcode.bin on it.
but i will try that one from the wiki, when i am at home.

would doing a tcpdump again help?

Thanks for Your help!


10
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 21, 2016, 02:57:51 pm »
Absolut fantastic work!
Thank You very much! A dream comes true! :)
It is near to that point that i would label this whole linuxmce thing as magical...
Affortable and noiseless md for every room. fantastic!

I am already trying to get it working.

Using a raspberry pi model 3b.

Updated and upgraded my linuxmce 14.04 system to the newest available point:
i386 - 201609172308+325de35d (besides the webadmin and the weborbiter are showing older version numbers)

Prepared the raspberry for network/usb booting (it is showing 0x3020000a).
I have not used the sdcard mentioned in the wiki. I used the way it was described there:
https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md
Should be the same result?

Installed the default netboot kernel package.

Changed the TARGET_TYPE. (Do i need to change it back after i have created the tarball?)

The raspberry didn`t get recognized. So i even tried to add the template manually, providing a mac address and an ip address.

it won`t boot.

I made a tcpdump on the core/hybrid and all i could find is this:

Code: [Select]
13:48:52.061106 IP moon142.49154 > 0.0.0.0.tftp: 29 RRQ "autoboot.txt" octet tsize 0
13:48:53.061145 IP moon142.49155 > 0.0.0.0.tftp: 27 RRQ "config.txt" octet tsize 0
13:48:54.061306 IP moon142.49156 > 0.0.0.0.tftp: 29 RRQ "recovery.elf" octet tsize 0
13:48:55.061453 IP moon142.49157 > 0.0.0.0.tftp: 26 RRQ "start.elf" octet tsize 0
13:48:56.061562 IP moon142.49158 > 0.0.0.0.tftp: 26 RRQ "fixup.dat" octet tsize 0

I copied something via tft to the core and vice versa without any problem.

I don`t know what i can do. Maybe reinstall everything? Did the netboot kernel package changed since last week? Is it a good idea to reinstall that?

I would really like to have a noiseless raspberry as md.
And i really would be very thankfull for any idea/suggestion/hint!

But again thanks!




11
Installation issues / Re: "PXE-E77: Bad or missing discovery server list".
« on: September 16, 2016, 06:52:03 am »
Hello,

i had the same problem after updating. (Version: 2.0.0.47.201607240235+899786ab)
I also tried the new diskless raspberry pi method before this happened.
So i don`t know what confused my system.

With the provided dhcpd.conf.tmpl and with running  /usr/pluto/bin/DHCP_config.sh, it is working again.

Thanks for the solution!!

12
Users / Re: Raspberry Pi v3 as media director - slow nfs speed
« on: August 22, 2016, 07:32:50 pm »
Thank You for Your response!

Do You use the diskless MD or the disked one?

I have some time tomorrow, i can and will try a few things ... :)


13
Users / Raspberry Pi v3 as media director - slow nfs speed [solved]
« 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


update:

shame on me and really sorry for bothering!!!

Quote
I usually attribute this to bad cabling or switches.

The Problem was a router called TL-WDR3600.
I thought that the switch of this router would be no problem cause the zotac box had no network problems with that configuration and the possible weak point would be the cable but ...
Now i am using a D-Link switch and everything works great.

Again SORRY and thanks for this perfect mediadirector!

have to write a list for myself:
try turning it off and on again
change the hardware
listen to people
...

14
Installation issues / Re: net install of 14.04 is currently broken
« on: February 02, 2016, 10:01:57 pm »
Hy,

i just did a successful 14.04 net install.

I had problems with fresh 12.04 and 14.04 getting audio via hdmi to work in the past.
But now it is working out of the box!
The whole installation went totally smooth.

Will "customize" the new installation later.

Big thank You! Great Work!

edit:
p.s.:

this is my graphic card:

Code: [Select]
GF119 [GeForce GT 520]
using it in the hybrid...

15
Users / Re: Mediatomb and logitech mediaserver
« on: September 27, 2015, 01:00:51 pm »
Hello,

i found out doing this:
Code: [Select]
in /etc/init/mediatomb.conf

change this line

start on (local-filesystems and net-device-up IFACE!=l0)

to

start on (started mysql and local-filesystems and net-device-up IFACE!=l0)

like suggested here:
http://ubuntuforums.org/showthread.php?t=1971040

helped me in getting to start mediatomb again.

don`t know if this helps, cause i just had the "cannot connect to mysql" error...



Pages: [1] 2 3