Messages

2191

Installation issues / Re: My own install logging

« on: July 31, 2007, 04:07:22 am »

I think maybe you should set the second one to 192.168.80.1 instead.

2192

Users / Re: Things that are safe to do and not to do? Like compiling a kernel?

« on: July 31, 2007, 01:12:39 am »

Cool, and good luck on both counts.  Looking forward to those instructions...

2193

Installation issues / Re: My own install logging

« on: July 30, 2007, 11:52:03 pm »

Now I'm trying to configure my mobile settings. I have a phone with windows mobile 2003. I went to the page wizard->devices->orbiters and then to the orbiter download page. I don't seem to in an appropriate file to download.

Thanks in advance

Turn on (or connect it using) Bluetooth, the orbitter should ask you what to do with it.  Which sometimes happens to me several times a day as I live near a busy intersection. 

EDIT:

I just looked at your ifconfig and routes.  And I can't find much difference between the network setup before and after.  Seems like a bit of an odd setup you have with 192.168.1.2 assigned to eth0 and 192.168.1.4 to eth1 though. 

2194

Users / Re: Things that are safe to do and not to do? Like compiling a kernel?

« on: July 30, 2007, 10:58:41 pm »

I have recompiled the kernel on my hybrid, the same version Kubuntu uses with a small patch.  I haven't tested everything there is but so far I have only noticed that this will break adding new Media Directors.  Which is easily fixed by copying vmlinuz-2.6.20-16-generic and initrd.img-2.6.20-16-generic from another MD into the "/usr/pluto/diskless/<device-number-of-MD>/boot/" directory (and changing the symlinks).

you should recompile a new kernel and then boot with it. then, run  /usr/pluto/bin/Diskless_InstallKernel.sh to install the current kernel into md image.

Thank you for that piece of the puzzel, I'll give it a try. 

And I think I should have mentioned that I'm not using mythtv at all at the moment, so I can't really tell whether recompiling or upgrading wil specifically break that.

2195

Feature requests & roadmap / Re: Wii Remote Support

« on: July 30, 2007, 04:47:15 pm »

Well it seems that nobody minds untarring wmd by hand and starting it from the command-line everytime they want to use the wiimote, so I guess we're done here.

2196

Installation issues / Re: System Settings Obliterated

« on: July 30, 2007, 04:27:32 pm »

I was happy to have finally got MCE installed on my fresh Kubuntu install.
But, after the installation, I found all of my system settings had been obliterated, and none were backed up by the MCE installation program!
All my samba shares were deleted(not too big of a deal). But, somehow, MCE somehow mangled SWAT, so now I have to do everything with samba on the command line.
Also, my x.org config was obliterated so that I was stuck in a 640x400 screen. Luckily, I had a backup of my original and I safely merged the two.

As it stands now, I have to reformat and install Kubuntu again just to undo the damage caused by MCE. I don't think I'll be installing MCE again...

So let me get this straight, LMCE just ruined your fresh Kubuntu install, and now you have to reinstall Kubuntu simply because you can't access SWAT anymore?

2197

Installation issues / Re: RC1 attempt1: Failed install

« on: July 30, 2007, 04:06:13 pm »

Oh, stupid me. I had the packages CD mounted on /mnt (I did this with beta 2 aswell!)

The installer should really check for this stupidity, like try creating /mnt/devices or whatever the required folder is before even trying to install!!

Good idea, but I think breathalyzer devices aren't supported yet!

(and I sure hope you can take a joke)

2198

Installation issues / Re: Media files

« on: July 30, 2007, 04:02:27 pm »

I'm just guessing here, but I suspect you could just remove the corresponding device (like "Internal HDD/CORE (...)") from the core, that way it should never be used for storing media.

2199

Users / Re: hardware recommendation for MediaDirector miniPC

« on: July 30, 2007, 03:52:08 pm »

Sounds like you're looking for one of these: FiireStation, and with a bit of luck they should be available in a few days.

2200

Installation issues / Re: My own install logging

« on: July 30, 2007, 01:13:12 am »

- Thanks for the tip cckrobinson..will check that out verry soon

- Ok, my experience with mce keeps up untill I manage to configure everything.
- I noticed 2 problems here. First is that I can't access the network when I boot. I have to bring the interface down and up again.
- Second, the workaround I used with beta2 to have video, music and pictures didn't work right as it only founds half a duzen videos, one song and no pictures. The covers for the found movies are not there either.

   I REALLY NEED SOME HELP IN THIS SUBJECT.

- Well, moving ahead...can't seem to find a way to get text-to speech to work...can anyone tell how?

Thanks

Could you post the output of the "ifconfig" and route -n commands?  Both before and after the network restart if you will.

And I'm curious to learn more about the text-to-speech functionality as well.

2201

Compatible Products & Services / Re: WIIl this work??

« on: July 29, 2007, 08:47:57 pm »

Yes it wiil!  Actually it already does, just not out of the box yet.  See: http://forum.linuxmce.com/index.php?topic=1246.0

2202

Installation issues / Re: Media files

« on: July 28, 2007, 08:41:05 pm »

If you have set up your LMCE machine (core or hybrid) to be the main DHCP server on your network and have the windows machine obtain it's network settings automaticly then it should get detected by LMCE which will ask you what to do with each share.  Depending on the choices you make you might have to move the actual files around a bit.

This is my understanding of how it's supposed to work, I could be wrong. 

2203

Installation issues / Re: Starting CORE software automatically. Beta1.1

« on: July 28, 2007, 04:09:16 pm »

I installed the new beta version and set it up to boot into LMCE core.  Now I cannot get into a KDE desktop!

The buttons work to take me to the LMCE launch manager, but I cannot get to the entire KDE desktop. 

I tried to CTRL + ALT + F2, becoming root, and running KDE at the command line.  It starts to load but then just hangs.

I'm almost ready to reinstall to fix this, which is disappointing considering the install time....

By "new beta" you mean RC1?

I usually do this from the command line: "DISPLAY=:0 xterm" that should give you an xterm from which you can start the apps you want manually, it's far from ideal but it works.

2204

Users / Re: Things that are safe to do and not to do? Like compiling a kernel?

« on: July 28, 2007, 03:56:44 pm »

I have recompiled the kernel on my hybrid, the same version Kubuntu uses with a small patch.  I haven't tested everything there is but so far I have only noticed that this will break adding new Media Directors.  Which is easily fixed by copying vmlinuz-2.6.20-16-generic and initrd.img-2.6.20-16-generic from another MD into the "/usr/pluto/diskless/<device-number-of-MD>/boot/" directory (and changing the symlinks). 

I haven't really looked into the reason of this faillure yet, but I'm pretty sure the 44Meg initial ramdisk the automatic build created isn't helping.

2205

Users / Re: LinuxMCE 0704 RC1 Released

« on: July 28, 2007, 03:36:53 pm »

>> but is that version jump really necessary?  What's the point in trailing the ubuntu versions when the goal is to run on other distro's as well?  ...  Or do we have a marketting department as well now?

No marketing   The most common problem with the beta 1/2 was that people were installing it on the wrong Ubuntu version.  So I figured syncing the versions would be better and make it clearer that this only works with 0704, and the next release for Kubuntu will be 0710, etc.  As far as other distros, what I was thinking of doing was making all the versions trail the respective distros.  So the Kubuntu version could be KU-0704 and KU-0710.  If, in June, there's a release for, say SuSe 20, then the LinuxMCE that goes with it would be LinuxMCE SU-20.

This isn't ideal.  But since LinuxMCE is an add-on and not yet included in the distros, I was trying to find a way to prevent people from using the wrong version of LinuxMCE for their distro, or using the LinuxMCE for Kubuntu on Fedora, etc.  Any other suggestions are welcome.

You're right, though, that 1.0 shouldn't have been 1.0, and should have been a 0.9 or something.

Fair enough, I still think it's a bad idea tho, how are people going to know which is the latest version?  Impossible to tell with KU-0704 vs SU-20 etc.  Why not just append that so we'll get "1.1 KU0704", "1.1 SU20", at least that way it's clear that it's all version 1.1 and that there should be no major differences between them, it also leaves room for a possible 1.2 version.

I'm going to do a change-log and post the sources next week when the final one is released.  There is a new update mechanism.  And also a backup/restore.  The beta 1/2 and RC1 won't likely cleanly upgrade because all upgrades will assume you're starting with the final release as a base.  the beta 1/2 and rc1 are for tests to confirm it's all ok.  but once the release is out, it will keep updating itself.  This has been tested a lot.

That is great, shame that the new upgrade mechanism won't be able to upgrade from RC1 already, would have been a good incentive to switch I reckon.  Thanks for putting in all that hard work, despite my whining I really appreciate what you guys are doing.