beta2

[mk01]

@xraxor no it is not.

I installed Frodo back after 2h. The non-working stuff was fixed (like ff/rw with different speeds, video controls like zoom, 4:3 etc) and others. But there are many small glitches and no added value for my usage (comparing to the Frodo 12.2 with backports we use). So I lost patience with it.

But in general it will do what you expect. So it will play a movie for instance A month ago it was a lot worse. As finest solution up to date looks the Frodo nightly from Beta2 repo + Amber Skin unfortunately not the one adapted for XBian but the actual 1.0.8 from pecinko git or via XBian Addon repo in XBMC (zip installer at http://ivka57.dyndns-ip.com/xbian-xbmc-repository/repository.xbian.xbmc.repository/repository.xbian.xbmc.repository.zip) … the only problem is that I'm not successful in updating Fred's patches to this new version - Fred did it for 0.5.x - so xbian-config is broken there. not totally, but is missing from settings menu and if started as program, spin control is not visible but is there and one more texture. Maybe Brantje would be able to help ? Don't know.

---

(15th Oct, 2013 05:53 AM)Dizzy Wrote:  

Code:

#
#
#
/dev/mmcblk0p1        /boot                   xbian   rw                              0       1
/dev/root             /home                   xbian   subvol=home/@,noatime           0       0
/dev/root             /lib/modules            xbian   subvol=modules/@,noatime        0       0
none            /run/shm                        tmpfs                   noauto                  0       0
none            /run/user                       tmpfs                   noauto                  0       0
none            /sys/kernel/debug               debugfs                 noauto                  0       0
none            /sys/kernel/security            securityfs              noauto                  0       0
10.0.0.1://home/_Movies /home/xbian/nfs/Movies nfs rw,hard,intr,noatime,_netdev,comment=systemd.automount  0      0

any ideas?

actually yes. I have it on candidate list to wiki which must be up with release of Beta2. looks like your NFS server is nfs4 (or the expots under this paths are defined as NFS4), but you have "nfs" in fstab (which assumes NFS2/3 - and no nfsvers= in mount options to make this clear for mount helper program).

so XBian assumes NFS2/3, starts rpcbind and statd instead of gssd and required idmapd. there are two ways how to correct this scenario
1) change fstpe to nfs4
2) edit /etc/default/nfs-common and set NEEDS_GSSD=yes and NEEDS_IDMAPD=yes

both will do the job. the same issue was there http://forum.xbian.org/thread-1430-post-16136.html#pid16136 .

I opened now "man nfs" just to be sure about Beta2 logic and found that i'm a bit behind:
" To mount an export using NFS version 2, use the nfs file system type and specify the nfsvers=2 mount option. To mount using NFS version 3, use the nfs
file system type and specify the nfsvers=3 mount option. To mount using NFS version 4, use either the nfs file system type, with the nfsvers=4 mount
option, or the nfs4 file system type."

and few lines back:

"nfs4 FILE SYSTEM TYPE
The nfs4 file system type is an old syntax for specifying NFSv4 usage. It can still be used with all NFSv4-specific and common options, excepted the
nfsvers mount option"


that means, nfs4 is no more required - but still accepted and for exports with NFS2/3 support a well as NFS4 combination fstype=nfs AND mount option "vers=4". So I have to adapt Beta2 then.

Looks like I didn't help you much ) so just open nfs-common and force start of IDMAPD and GSSD.

My homework would be keeping nfs4 for compatibility but accepting nfsvers=4 param in fstab even if fstype is nfs (not nfs4).

---

Please report back then.