Forum Replies Created
15. Januar 2020 at 16:49 #47931
Hi, it is not really necessary to provide IP via dhcp, manual ip assignment is just another way to do this.
When I tested network boot with max2play it was allmost running but after e specific time it allways stopped working.
Maybe m2p was changed/improved meanwhile, so I dont know if it is running well now.
Meanwhile I switched over to a bare raspian installation with my own functionality, which fits more to my purposes.
My installation with network boot (without any SD card) from my PXE Server including snips (voice recognition), webcam via motioneye, mjpstreamer, MPD & yMPD (MPD Webinterface), TTS (text2Speech engine), USB redirector Server (used for CUL connection for my FHEM and ioBroker installation) a.s.o. So I left M2P some time time ago. Maybe I will retry in future …8. Mai 2017 at 12:12 #28744
Hi @ all
FYI: the way I described is working also with MPD. So if you are planning to use MPD also, better disable onboard sound … 🙂 makes live at this point much more easier. You will loose hdmi sound but you dont need it any more if there is a sound path via soundcard.
michael4. Mai 2017 at 18:57 #28710
its somehow misleading that they call it for „RPi3“, it just disables buitin driver for BCM chip, which is used for HDMI. An that is working on all kind of rpi.
Concering a solved button I cannot help. Seems to be a simple worpress site. If there is any ticket mechanism like „github or co“ I dont know …4. Mai 2017 at 15:52 #28707
very easy: Goto page „Raspberry Einstellungen“ and enable checkbox at „Deaktiviere integriertes Audio bei RPi3“.
this is working fine on my raspi3 with kodi. took some time to get that 😉
ignore that hdmi configuration, does not affect anything. the problem ist, that kodi uses first soundcard, which is rpi builtin bcm. Disable that and your soundcard will become the first in system and become visible for kodi.
enjoy!4. Mai 2017 at 15:43 #28706
Just for info:
meanwhile I tried to add a bridge to max2play manually like on raspian jessie:
auto lo iface lo inet loopback iface eth0 inet dhcp # WLAN # auto wlan0 # allow-hotplug wlan0 iface wlan0 inet static address 192.168.2.1 netmask 255.255.255.0 auto br0 iface br0 inet dhcp bridge_ports eth0 wlan0 gateway 192.168.1.xxx
and adding the bridge to hostapd.conf:
# Bridge-Betrieb bridge=br0 # Ländercode country_code=DE interface=wlan0 ...
The result was somehow instable. After installation it was running fine, after reboot the problems started.
So I fear that I do not know enough of max2play architecture and its services an their startup mechanisms so far.
I suppose, that during startup some network configuration is done my max2play that will cause the problems, maybe …4. Mai 2017 at 15:26 #28705
until max2play will do that, we can create some own project to realize that 😉
My project at home has some kind of Raspberry Nodes without any webinterface beside webmin (administration) or mjpg streamer (raspi or usb cam streaming server for my zoneminder VM).
I realized the following functionality allready:
1. raspbian jessie light with pixel (desktop) and Cairo dock (Menu)
2. mjpg streamer experimental (supports also raspi cam)
3. shairport-sync (supports synced streaming)
4. MPD Server (used for FHEM automation and MPD clients on smartphones and tablets)
5. pico2wave (text to speach engine)
6. hostapd (WLAN APs in all rooms, bidged to get all shairport servers on my smartphone/tablets)
7. openelec network boot (running xstream, logan, aluc, with different user management profiles on my server)
There are still some TODOs, but I will use my thin installation in parallel for some clients and my own development.
Its much more easy to return to a snapshot which is stable on my nfs server running as VM on my citrix server (6.5 free edition). I can use xencenter (free) or similar (scripted) to create or return to snaphots. And because homeautomation is a living thing this is the most usefull functionality when some updates/upgrades/development are causing problems.
Hope that may2play will take up that aspect some day 🙂18. April 2017 at 11:23 #28319
meanwhile I tested also another cmdline.txt version with fixed ip definition instead og ip=dhcp, not working … 🙁
root=/dev/nfs rootfstype=nfs nfsroot=192.168.1.104:/nfs-server/max2play,udp,vers=3 smsc95xx.turbo_mode=N rw ip=192.168.1.151::192.168.1.200:255.255.255.0::eth0:off rootwait elevator=deadline
Is there any way to create a max2play on a clean/pure jessie installation?
Maybe I can create a netboot capable version of max2play by using a working network bootable version of raspbian.
By the way, max2play should be able to reproduce this in their lab. You just need a second raspi working as a nfs server in the first step, which is very easy to realize.
With that you can boot the image from sd card and just boot root filesystem from network via cmdline.txt
In a second step you might also implement a boot tftp server, which does not need some sd card on client anymore.
You can share on big sd card for all of your max2play installations or you might place the shared folders on a usb stick or hdd/ssd.
So I really would like to implement network boot with max2play. Please let me know, if you like, I will support you on that and we will do that close together. I am not familiar enough with max2play to do that by my own.
Michael12. April 2017 at 14:54 #28169
I don#t think that is a nfs server related issue. My debian jessie installations and even some Kodi installations are running well on my setup.
Even max2play is running. I can see max2play allready booting from nfs with my configuration created within max2play formerly on SD card.
Maybe some community member will try do this …
Here is some quik instruction:
On nfs server (mine is debian):
(m2p_image_241.img is image created with Win32DiskImager)
fdisk -l m2p_image_241.img
this will show partition start for offset calculation:
Disk m2p_image_241.img: 4025 MB, 4025483264 bytes 255 heads, 63 sectors/track, 489 cylinders, total 7862272 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x34e4b02c Device Boot Start End Blocks Id System m2p_balkon_241.img1 8192 131071 61440 c W95 FAT32 (LBA) m2p_balkon_241.img2 131072 7462272 3665600+ 83 Linux m2p_balkon_241.img3 7462273 7862271 199999+ 83 Linux
root partition starts at 131072 * 512 = 67108864
mount -v -o loop,offset=<strong>67108864 </strong>m2p_image_241.img /mnt/m2p/
now make a full copy of sd card root partition to nfs server:
rsync -arv /mnt/m2p/ /nfs-server/max2play/
On NFS Server I made some export within /etc/exports:
/srv/nfs/jessie_light/ *(rw,sync,no_subtree_check,no_root_squash) /nfs-server/pixel/ *(rw,sync,no_subtree_check,no_root_squash) /tftpboot/22bddc11.elec *(rw,sync,no_subtree_check,no_root_squash) /nfs-server/hifi.elec *(rw,sync,no_subtree_check,no_root_squash) /nfs-server/hifi.pix *(rw,sync,no_subtree_check,no_root_squash) /nfs-server/max2play *(rw,sync,no_subtree_check,no_root_squash)
and restarted nfs server
Configuration on max2play sd card s described above …
Now I can see the raspi booting and making a ping on it shows that he is there on network for quite some seconds.
Then he stops working, no reaction on keyboard a.s.o.
hope that was helpful
PS: hope this reply will not disappear again, got some problems on editing …11. April 2017 at 17:54 #28108
sorry, but I do not get logfiles, because I can#t access the pi anymore before it stops working.
I just can see a only a few wanrings on the monitor connected to the pi.
What I have done so far is
root=/dev/nfs rootfstype=nfs nfsroot=192.168.1.104:/nfs-server/max2play,udp,vers=3 smsc95xx.turbo_mode=N rw ip=dhcp rootwait elevator=deadline init=/bin/systemd
tried that with and without init=/bin/systemd as discussed in a forum.
removed sd card mounts in fstab:
# proc /proc proc defaults 0 0 # /dev/mmcblk0p1 /boot vfat defaults 0 2 # /dev/mmcblk0p2 / ext4 defaults,noatime 0 1 proc /proc proc defaults 0 0 # /dev/mmcblk0p1 /boot vfat defaults 0 2 # /dev/mmcblk0p2 / ext4 defaults,noatime 0 1 tmpfs /tmp tmpfs defaults,noatime,nosuid,size=200m 0 0 tmpfs /var/tmp tmpfs defaults,noatime,nosuid,size=60m 0 0 tmpfs /var/log tmpfs defaults,noatime,nosuid,mode=0755,size=200m 0 0 tmpfs /var/run tmpfs defaults,noatime,nosuid,mode=0755,size=20m 0 0 ##USERMOUNT # a swapfile is not a swap partition, no line here # use dphys-swapfile swap[on|off] for that
on nfs server side a made a copy with rsync of the / (root partition) to my nfs server.
So this nfs mount is booting, but not working.
Maybe you can make a simple test with one of your nfs server by your own?
Would be a great feature to have at least the root file system on a central server.
With Pi3 you can even boot without any SD card inside with a simple tftp boot server, which was quite simple.
Mine is running as a VM within a (Citrix) XEN server. I take snapshots within a second of all of my pi installations or automaticly backup (rotating) the complete OS of all my raspis.
Michael6. April 2017 at 20:55 #28020
after reboot I could see that shairport device on m2p from my iphone 🙂
but not the other shairport-sync installations on my other raspians.
„Standalone“ seems not to be an option to my setup here at home, because I got problems on mounting nfs(lost my mp3 for MPD). So i will try to modify network/interface and add a bridge there.
Are you expecting any conflicts within m2p setup? Did not complete went throug this …
Need some workaround until m2p supports bridged mode …