I have been trying to figure out why my RAID1 NAS (NAS4220-B) never spins down and I have spotted lots of hits in the samba log on the NAS. Looks like the dcerouter is hitting the NAS (samba login) every six seconds.

I've thought it might be the 5 second ping option in linux web admin but it is disabled. The windows-share is a child of the file-server device.

Anyone know how I can change this behaviour?
Barney
<edit>Changed title to make sense</edit>

Thanks Hari,
Much better!
Barney

Figured this out.

There seems to be a four letter minimum word length on the wiki search terms ... so:
asus eee box
only gets searches for:
asus
However, searching for:
asus b202
works fine!
So it's not a fault. The page is just buried in the results. Probably to do with the mysql ft_min_word_len variable for fulltext searches.

Anyone else think it's worth changing to three letters? It might help folks find valuable info ... but then again, would it create a big performance hit?

I added a new page to the wiki for the asus eee box b202. When I search using logical words it doesn't show in the results.

Is there a search index which needs updating or have I missed something?
Barney

<edit>Modified title</edit>

Hi thedaver,
I think if you search the forums you'll find the general consensus is that 32bit has fewer issues and is more stable and that the benefits of 64bit are outweighed by this. This might change with the new version in development though.

I have two 64bit computers running 32bit linuxmce 710. It's rock solid ... so I recommend it!

Got to agree with colinjones about the NIC. I tried to run linuxmce with one nic and it took months for me to realise it was a mistake.

Looks like you're getting a challenge with that motherboard too. A lot of issues in the wiki.
Whatever mainboard you get install i386 over 64 bit. It's generally more stable.

Good luck with your first steps into linuxmce. Stick with the tested good hardware and have fun.
Barney

Hi nosebreaker,

The only time I've seen both kernel panic and eth0: link down is with the r8168 issue.

Might be worth following the wiki guide in detail again. I'm pretty sure this is your problem. Colinjones detailed explanation in post 5 covers everything you need to know.
Hope this helps
Barney

Fixed now. Should have edited this page.
LinuxMCE Admin Website-->Device tree-->CORE-->Generic Web Device-->Device Data
NOT
Wizard-->Devices-->Orbiters
Now working perfectly. Thanks for the assistance!
(added to wiki web orbiter page)

Thanks jondecker76. I tried that but it didn't work for me. In fact I regenerated all orbiters yesterday and screwed my main md which has the r8168 issue. Still the web orbiter is defaulting to the core. Did you get the default room to change OK in web admin then?

Yeah! That works. Good solution. Thanks colinjones!

I'll give that a try. Thanks for the advice!

I've installed a web orbiter by following the wiki.

I installed it to control the md in my living room but it is linked to my hybrid/core in another room. I can't get it to change the md it is linked to even though it says 'living room' on the orbiter page. Is this a known bug or have I missed something?

Apologies. I just realised I missed a step within step 6 of the walkthrough.

The step was to edit /usr/pluto/diskless/<moon #>/etc/initramfs-tools/modules to include the r8168 module.

Now added to the wiki.
Barney

@wrotruck

Did you re-run the avwizard after you changed to the intel driver? It should allow you to select the higher resolutions once you've changed this setting.
Glad you got it working though! How's it running? Any lock-ups?
Barney

Just added the ASUS eee box b202 page to the wiki.
http://wiki.linuxmce.org/index.php/Asus_eee_box_b202
and a walkthrough:
http://wiki.linuxmce.org/index.php/ASUS_eee_box_b202_setup
Hope it is of use. Please dive in if I've made any stupid mistakes.
Barney