beta2

[thenork]

(12th Oct, 2013 12:48 PM)mk01 Wrote:  

(12th Oct, 2013 12:01 PM)thenork Wrote:  I also checked the "Shares should be world writeable" for smb, but the problem is still there. I can actually connect to xbian home folder just fine, and it's writeable (didn't test that before). However for my usb drive, I can connect with xbian but not with guest. If I try with guest I get this in the mac console (xbian.local/Fantom is my usb drive):

can you check that /etc/usbmount/usbmount.conf has SHARERW=yes ? if yes, can you provide output of

Code:

sudo net conf list

when the usb is mounted? and if you connect with xbian, can you write?

---

@thenork

I found a small bug in usbmount, I will issue a fix. can you test xbian-package-usbmount version 1.0.4-7 please?

After update I can now connect to my usb drive and write to it. However, guest still has error and cannot connect to it. Guest can connect to xbian home folder and write to it. Here is my net conf list

Terminal

[xbmc-backup]
path = /xbmc-backup
read only = no
guest ok = yes
force user = root
browseable = yes

[Fantom]
path = /media/Fantom
guest ok = yes
read only = no
force user = xbian
browseable = yes

Also my usb drive is ext4, will that affect anything?

[mk01]

(13th Oct, 2013 06:23 AM)thenork Wrote:  After update I can now connect to my usb drive and write to it. However, guest still has error and cannot connect to it. Guest can connect to xbian home folder and write to it. Here is my net conf list

Terminal

[Fantom]
path = /media/Fantom
guest ok = yes
read only = no
force user = xbian
browseable = yes

Also my usb drive is ext4, will that affect anything?

hm. what is output of

Code:

ls -la /media ; ls -la /media/Fantom; mount | grep Fantom

?

[BartOtten]

(12th Oct, 2013 02:29 PM)mk01 Wrote:  

(9th Oct, 2013 06:20 AM)Dave400 Wrote:  Bad news.. I installed the lirc update (along with 5 other packages) and now my remote is behaving how it was before, I've rolled back using a snapshot and will install the other updates again but leave out lirc for the time being...

@Dave400

is it possible that xbian-update put lirc_rpi into /etc/modules and by removing it you restore previous functionality?

while looking into /etc/lirc/hardware.conf, first RC which is looked up is lirc_rpi. all others are "else if" so won't never override the lirc RC found as first.

can you report back please?

Removing it fixed my remote What line should I remove for ssh? (as now it hangs after asking for the password)

*edit* Guess it was the same line

[thenork]

(13th Oct, 2013 06:30 AM)mk01 Wrote:  hm. what is output of

Code:

ls -la /media ; ls -la /media/Fantom; mount | grep Fantom

?

Code:

root@xbian:~# ls -la /media ; ls -la /media/Fantom; mount | grep Fantom
total 8
drwxr-xr-x  1 root root   20 Oct 12 14:57 .
drwxr-xr-x  1 root root  192 Sep 17 01:19 ..
drwxrwxrwx 10 root root 4096 Sep 14 14:58 Fantom
lrwxrwxrwx  1 root root   13 Oct 12 14:57 usb0 -> /media/Fantom
total 576
drwxrwxrwx 10 root  root    4096 Sep 14 14:58 .
drwxr-xr-x  1 root  root      20 Oct 12 14:57 ..
drwxrwxrwx  2 xbian xbian   4096 Aug 22 11:26 downloads
-rwxr--r--  1 root  root    4096 Aug 14 22:03 ._.DS_Store
-rwxr--r--  1 root  root   15364 Sep  5 10:41 .DS_Store
drwx------  2 root  root   16384 Aug 10 19:03 lost+found
drwxrwxrwx  5 xbian xbian   4096 Oct 12 14:38 movies
drwxrwxrwx 43 xbian xbian   4096 Oct 12 13:44 TV
drwxrwxrwx  3 root  root    4096 Sep 15 22:12 xbian-home-backup
/dev/sda1 on /media/Fantom type ext4 (rw,nodev,noexec,noatime,nodiratime,sync,data=ordered)

[mk01]

@thenork

do a

Code:

sudo chown -Rc xbian:xbian /media/Fantom

[belese]

Could be reload xbmc a little bit less hard.
i can't reproduce again, but it's happen, when i reload xbmc, addon was not stopped(xbian-config), it's still post log in new xbmc session and i can see screen on overlay when xbmc is stop.

maybe send TERM, wait 2 sec and send KILL, addon should have time to stop, or at least keep the signal to stop and died after.
or more hard and kill all xbmc subprocess with KILL.

[mk01]

reload will never be nicer as "reload xbmc" is defined by upstard design as sending SIGHUP to the process. second part is what the process does about this.

"restart xbmc" can be controlled. as this is the standard workflow as from pre-start until post-stop. if you call "stop xbmc" or "restart xbmc" xbmc is going to be stopped by TERM signal, wait 10s and kill.

btw: for the blocked python threads I'm keeping a list of PIDs (of xbian-config CLI) which were called from within xbmc. so instead of stopping / waiting / crashing xbian-config-xbmc (python inside xbmc), you can just do "kill $(cat /run/lock/xbian-config)". this will send TERM to running processes and python threads will finish immediatelly.

[mk01]

(12th Oct, 2013 07:35 PM)namtih Wrote:  @2)
Thanks, good to hear that I'm not alone with this issue.
Let's see if Koenkk perhaps will find the fix/commit.

http://forum.stmlabs.com/showthread.php?tid=10868 but looks like you was first but nobody followed

[xraxor]

followed instructions by @mk01 changed etc/usbmount/usbmount.conf SHARERW=yes and reboot the Pi, now I can read/write/rename to my external EXT4 HDD

xbian@xbian ~ $ sudo net conf list
[sudo] password for xbian:
[xbmc-backup]
path = /xbmc-backup
read only = no
guest ok = yes
force user = root
browseable = yes

[avMedia01]
path = /media/avMedia01
guest ok = yes
read only = no
force user = xbian
browseable = yes

Edit:
had to run this line of code and reboot as well
sudo chown -Rc xbian:xbian /media/avMedia01

now all perfect . can't wait, now xbmc seems to be giving more attention to the Pi

[CurlyMo]

In my case Lirc now works at boot time. It only doesn't work in my specific cause. Probably because my /etc/lirc folder contains various symlinks to a samba share.

[mk01]

@CurlyMo

add condition "stopped xbian-net" to lirc.conf .

when xbian-net is stopped, eth0/wlan should be up and nfs/nfs4/cifs mounts from fstab should have been mounted.

---

(13th Oct, 2013 08:12 PM)xraxor Wrote:  followed instructions by @mk01 changed etc/usbmount/usbmount.conf SHARERW=yes and reboot the Pi, now I can read/write/rename to my external EXT4 HDD

thanks for confirming

[CurlyMo]

@mk01, the problem is that it also doesn't work when starting Lirc through SSH.

[mk01]

(13th Oct, 2013 08:34 PM)CurlyMo Wrote:  In my case Lirc now works at boot time. It only doesn't work in my specific cause. Probably because my /etc/lirc folder contains various symlinks to a samba share.

Can you not mount /etc/lirc as a whole folder?

There are "test -f" statements which will obviously fail on symlink. That's why sometimes is better just test -e.

[CurlyMo]

Didn't work either.

[mk01]

then put a "set -x" to hardware.conf and follow output in /var/log/upstart/lirc.conf