(1st Jul, 2013 02:38 AM)Pawlisko Wrote: [ -> ] (29th Jun, 2013 02:28 PM)f1vefour Wrote: [ -> ] (29th Jun, 2013 08:50 AM)Pawlisko Wrote: [ -> ]What about iptables?
Still I do not see any solutions.
Have you tried:
sudo modprobe ipt_masquerade
xbian@xBian ~ $ sudo modprobe ipt_masquerade
[sudo] password for xbian:
FATAL: Module ipt_masquerade not found.
Whats next?
It appears masquerade has not been included in the current kernel.
(1st Jul, 2013 06:55 AM)f1vefour Wrote: [ -> ] (1st Jul, 2013 02:38 AM)Pawlisko Wrote: [ -> ] (29th Jun, 2013 02:28 PM)f1vefour Wrote: [ -> ] (29th Jun, 2013 08:50 AM)Pawlisko Wrote: [ -> ]What about iptables?
Still I do not see any solutions.
Have you tried:
sudo modprobe ipt_masquerade
xbian@xBian ~ $ sudo modprobe ipt_masquerade
[sudo] password for xbian:
FATAL: Module ipt_masquerade not found.
Whats next?
It appears masquerade has not been included in the current kernel.
In that case - xBian developers - PLEASE include it in next kernel.
I don't want to sound repetitive, but I can confirm, after 2 clean installs, that 1.0B1 has issues with SMB shares:
As soon as I try to browse for SMB shares in the gui, it returns the error:
Code:
Error 2: Share not available
That could mean everything,were not for the fact that, mounting the share from SSH:
Terminal
mount -t cifs //192.168.0.101/Mount_Points /mnt/cifs -o username=xxx,password=xxx
works flawlessly.
I can replicate this in 1.0B1, in 1.0A5 (both used and cleand install) it always works, both in gui and in cli.
So definitely 1.0B1 introduced some issue with SMB.. can someone please tell me how to proceed?
(1st Jul, 2013 04:56 PM)ilgrank Wrote: [ -> ]
Code:
Error 2: Share not available
That could mean everything,were not for the fact that, mounting the share from SSH:
Terminal
mount -t cifs //192.168.0.101/Mount_Points /mnt/cifs -o username=xxx,password=xxx
can you post "lsmod", and "dmesg | tail" immediately after the mount command? what is the server (windows version)?
(1st Jul, 2013 12:18 PM)Pawlisko Wrote: [ -> ]In that case - xBian developers - PLEASE include it in next kernel.
compiling
(1st Jul, 2013 10:40 PM)reab Wrote: [ -> ]try adding security:
mount -t cifs //192.168.0.101/Mount_Points /mnt/cifs -o username=xxx,password=xxx,sec=ntlm
Thanks but I think you misunderstood me: using mount (even without security) DOES always work.
What DOES NOT work is browsing smb shares from the XMBC gui in 1.0B1, while it does work in previous versions.
Oh sorry.
I had to add that to make it work on my Pi.
I have no security on the samba server (-o guest) but still I had to add that to make it work.
(1st Jul, 2013 10:45 PM)ilgrank Wrote: [ -> ]Thanks but I think you misunderstood me: using mount (even without security) DOES always work.
What DOES NOT work is browsing smb shares from the XMBC gui in 1.0B1, while it does work in previous versions.
are you try to browse via "windows network smb" browser, or is it already created smb source ?
xbmc is not using the standard system tools, but can you some system libraries. what is in the xbmc.log at the time you get error on screen?
(29th Jun, 2013 03:49 PM)rikardo1979 Wrote: [ -> ] (29th Jun, 2013 01:55 AM)f1vefour Wrote: [ -> ]I think having a select group of testers which have shown they are both knowledgeable of the system being tested and good at debugging/resolving issues is a great idea before future releases.
Most of the major issues could be avoided and the rest of the Xbian users can then help iron out the smaller issues once a general beta release has been produced.
Once again just my opinion.
we have a bunch of Testers who were testing Beta1 before we push it public. None of the issues were found and reported as otherwise we would not release it.
So what I trying to say is that you would need a team of 100's of people to be able to spot every issue an even than it would not be 100% 
So now issues are here,reported thanks to you all and we can sort all out, thats what is all this community work about.
That's a pretty huge generalisation. Didn't I read elsewhere that you said, of all the testers, nobody tested the upgrade method? If that's the case, then the testing simply wasn't managed properly.
I think there's room, even in an unpaid community, to acknowledge disappointing errors of procedures. It's not the end of the world to admit faults. The important thing is to admit them, learn from them, and not repeat them.
Regarding the SMB issues, I eventually worked around this painful bug by going to "Add network location..." and manually adding my drobo NAS's details. That worked fine where trying to browse the exact same NAS box/share after selecting "Windows network (SMB)" continually failed with the now infamous
Error 2: Share not available
On a second setup, pointing to a QNAP NAS, there was no problem.
Both times I was using standard ethernet via a Billion routers.
Hello again. In relation to the slowness of the navigation in Xbmc, I've to say that I have tried another sd card and now (finally) it works fine :-) Both of them are class 10 8Gb but the Trascend works and the Patriot doen't. Strange...
My problem now is that the system freezes (and I have to restore an image) while updating (apt-get) when it arrives to xbian-package-initramfs-tools. Any idea or workaround?
Thanks in advance
use the one from git, install with dpkg -i ...
then run the update
just for info, do you have modelA or B (256 or 512mb ram)?
Unfortunately I have to add another issue to the list. I've never had any audio issues but now I do. I'm getting all sorts of issues, including:
- Audio randomly fails to play from when videos start, then by simply stopping and restarting the same video, the audio plays
- Audio sometimes blurred - actors sounds like they're in slow motion when the video is playing at normal speed and I've not played with any audio offsetting
- Pops! I think I'm hearing what other people have heard for ages: sound blips every once in a while, sounding to me like the audio stream is being interupted momentarily and then catching up it gets mixed up with the audio that should be playing at that time.
I can't see anything in the log that sheds any light on this, though I'm not an expert at reading them.
hopefully you doesn't installed any update on top of beta1? there is one firmware version in testing branch of xbian-package-firmware (very fresh from upstream), but I was experiencing similar issues.
beta1 has the same firmware and xbmc version as alpha5 + xbmc 12.2 update, so should work (at least with no such problems)
(2nd Jul, 2013 02:46 AM)mk01 Wrote: [ -> ]hopefully you doesn't installed any update on top of beta1? there is one firmware version in testing branch of xbian-package-firmware (very fresh from upstream), but I was experiencing similar issues.
beta1 has the same firmware and xbmc version as alpha5 + xbmc 12.2 update, so should work (at least with no such problems)
I'm not too sure what versions I'm running. Can I check that by querying apt for the package information that is not obvious from within XBMC?
(1st Jul, 2013 11:20 PM)mk01 Wrote: [ -> ] (1st Jul, 2013 10:45 PM)ilgrank Wrote: [ -> ]Thanks but I think you misunderstood me: using mount (even without security) DOES always work.
What DOES NOT work is browsing smb shares from the XMBC gui in 1.0B1, while it does work in previous versions.
are you try to browse via "windows network smb" browser, or is it already created smb source ?
xbmc is not using the standard system tools, but can you some system libraries. what is in the xbmc.log at the time you get error on screen?
The tail of XBMC.log follows (it's very short, that's why I'm not using pastebin btw)
Code:
01:00:28 T:2874405952 NOTICE: UDP: Listening on port 9777
01:00:29 T:2841859136 NOTICE: Thread Jobworker start, auto delete: true
01:00:29 T:2924737600 NOTICE: -->Python Interpreter Initialized<--
18:49:59 T:3042304000 NOTICE: Samba is idle. Closing the remaining connections
18:50:22 T:2841859136 NOTICE: Thread Jobworker start, auto delete: true
18:50:32 T:2924737600 NOTICE: Previous line repeats 2 times.
18:50:32 T:2924737600 NOTICE: Thread Background Loader start, auto delete: false
18:50:47 T:2933126208 NOTICE: Previous line repeats 2 times.
18:50:47 T:2933126208 ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://'
unix_err:'2' error : 'No such file or directory'
nothing of interest in dmesg or /var/log/messages btw.
Since there's an hotfix running, I'm upgrading the setup and test more.