14800JackOfAll wrote:
> 'CSOS-Wandboard-Dual-R4-20130509-1.img.7z'
> (http://www.communitysqueeze.org/images/wandboard/CSOS/CSOS-Wandboard-Dual-R4-20130509-1.img.7z)
> (587MB)
>
> EDIT: With reference to the 'avahi/bonjour/mDNS'
> (http://forums.slimdevices.com/showthread.php?98544-Community-Squeeze-OS-R3&p=746291&viewfull=1#post746291)
> post by dsdreamer, can you guys running W$ or Mac check that
> wandboard.local is visible from them. You don't need to install or
> configure anything on the WB. There should also be services announced
> and visible: ssh/22, http/80, slimhttp/9000. Can you see them?
>
> Can you also check that Samba file shares are visible?
> "\\WORKGROUP\WANDBOARD\files" is the writable one, mapped to "/storage"
> on the WB filesystem.
>
>
I installed the new R4 image this evening.
1) Booted right up into Jivelite at the skin selection menu, which I
duly selected as 1280x1024. But I was never asked which language I would
prefer, it seems to be pre-configured to use English. If this is
official, my contributed kickstart guide is wrong. If not, then this is
a bug.
2) I avoided connecting up the Ethernet interface assuming that I could
just enter my WiFi password in the Jivelite configuration screen and
have my Wandboard appear on the network. This worked, except that
Jivelite froze as soon as it successfully joined the wireless network.
By this time I could ssh in to it from a Macbook and had to sudo killall
-9 jivelite-cs to get it to restart. An ordinary kill was not enough,
kill -9 (SIGKILL) was needed.
3) The select player menu now showed two identically named SqueezeWand
players (probably one for each interface eth0 and wlan0). It is hard to
guess which one is the real one in this situation.
4) I was able to select my preferred USB DAC from the JiveLite menu and
play music.
5) I edited /boot/udev/uEnv.txt to conform to my screen resolution
video=mxcfb0:dev=hdmi,1280x1080M@60,if=RGB24 just so that the screen
comes on earlier in the boot process rather than waiting for Jivelite to
change the resolution.
6) I edited fstab to add my Vortexbox CIFS filesystem as follows
Code:
--------------------
//vortexbox.local/files /storage cifs
nofail,sec=ntlmv2,user=WORKGROUP\guest,pass=,iocharset=utf8,file_mode=0777,dir_mode=0777
0 0
--------------------
After a sudo mount -a, I could update to Logitech Media Server
Version: 7.8.0 - 1368018400 @ Thu May 9 20:03:10 BST 2013, and scan my
music collection (across a wireless network connection mounted as
above).
7) mDNS is working well as far as my Macbook is concerned (see image
below). I can see two services advertised from the Wandboard
[image: http://i.imgur.com/J5RdwQf.png]
8) From the Mac OS X Finder, the file services offered by Wandboard are
visible and when clicked automatically mount themselves. Due to the CIFS
mount already mentioned above, it is actually my Vortexbox files that
are being re-distributed by the Wandboard, which is quite inefficient
but works.
Apart from the inital Jivelite crash and the appearance of two
identically named SqueezeWand players after the wireless connection came
up, all seems very well with R4.
I'd like to know how I can get logging information from Jivelite to
better understand the crash, assuming I can reproduce it.
------------------------------------------------------------------------
dsdreamer's Profile: http://forums.slimdevices.com/member.php?userid=12588
View this thread: http://forums.slimdevices.com/showthread.php?t=98544
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
