Messages

Wow, after hours and hours, thre different NICs, blood and tears.......

the solution was that easy.....
thanks a lot Zaerc
and of course, even if a little too late... *g* tkmedia.....

augalex

You should post that solution in the Wiki for the next person

Perhaps I'm missing something but arn't the updates updating packages and scripts and bring us up to date so we don't need to re-install

The last time I had to wipe out a Linux system was due to a major GCC change which doesn't happen that often.

Or is it that linuxmce is so complex and alpha (no insult intended)  that update scripts are not available.

As I have splurged (is that a word) on fiire, I can't just wipe it out as I would lose my pro II drivers.

I'll ask fiire and see what they say as well.

Assuming they use the standard Ubuntu upgrade process for linux, you do not need to wipe out the machine. GCC with Gentoo one of the reasons I dumped it a while ago.

Ouch, not good. You should lower people's expectations with alpha blending...

Hi..

Now i have done that a couple of times.. When I restart, the driver is still vesa. Hmmm . After editing, I reboot.
Hmmm , i am still trying..

Did you follow:

"LinuxMCE keeps reconfiguring my display settings
Add a line containing exit to the top of the /usr/pluto/bin/Xconfigure.sh file."

or I just like to chmod 000 /usr/pluto/bin/Xconfigure.sh

Using mdadm and lvm2 I assume? I'd go with Kubuntu alternative.

Hmm, are you able to compile it on the core? Looking around it seems that the realtek driver isn't very good and people are having a lot of problems with it.

I have terrabytes of data and one of the main reason's I'm migrating form mythtv is the vastly superior media browser in linuxmce.

Try the modules section. I think when I was trying to get the intel driver working the same thing happened to me and I needed to make sure my custom xorg.conf had all the modules in it.

The r1000 or any other card with the appropriate driver should work just the same as long as a module was compiled for it on that stock image. Just add it in the modules file instead of sky2.

You can check what drivers were compiled against the stock image in the /usr/pluto/diskless/xx/lib/modules/2.xxx/kernel/drivers/net/ directory. The xx's will change over time.

The wiki has been updated. http://wiki.linuxmce.org/index.php/Automatic_diskless_boot_of_media_directors There's a few other things that I think have changed in the previous section of that wiki as well that I'll fix next time work on my mce machine.

I'm in a similar position. I've been running mythtv since version .6 and have 3TB of movies etc. What I'm doing is dropping in a new 250GB SATA HD and installing linuxmce on it. While I'm working on all the issues with mce, I can easily pull the HD and reboot back to myth. You can mount up your media directories and mce can see them and catalog them (you'll keep your videos and music). I'm still working (fighting) with some issues on the integration to get it running the way I want so back to myth for another week...

The following in the procedure I used to enable network booting from my Marvell Gigabit diskless MD.

Things you need to know: The driver name for your network card (for my nic its the 'sky2' driver) and the the device name assigned for your diskless machine (described later).

Follow the normal diskless installation http://wiki.linuxmce.org/index.php/PXE until you get to the remote machine starting the boot process, but then fails with it unable to find eth0. This is happening because the initrd image that was compiled did not have the driver for your network card compiled in statically. This is normal as compiling in every network card becomes unruly and the image building process does allow for additional network modules to be loaded during the boot process. The installer that linuxmce uses builds this image from a base copy of the operating system (ubuntu) that is untar'd during the diskless setup process. It puts this into it's own directory that serves as a virtual harddrive for your diskless machine. In the /usr/pluto/diskless directory you should have a list of device numbers that correspond to your diskless machines. In my case '45' was the number for my diskless machine. Edit the file /usr/pluto/diskless/###/etc/initramfs-tools/modules and add on your nic's module. In my case I edit  /usr/pluto/diskless/45/etc/initramfs-tools/modules and added sky2. Then run the /usr/pluto/bin/Diskless_InstallKernel.sh script with the device number (directory name) of your diskless machine. In my case "/usr/pluto/bin/Diskless_InstallKernel.sh 45". This script builds the initrd image and puts it in the proper place (symlinks it actually).

Reboot your diskless machine and it should come fine now.

Hopefully this will help people before they go out and purchase extra cards for their diskless machines that they don't really need. Perhaps the developers can support this in the future.