Messages

The existing MBR I installed with my previous (FAT32 sda3, a la USB Flash) process to point at that old 0704 menu.lst with 0710 added as an option, and I hadn't edited that menu.lst to fix the bug (thinking, like you, that it wasn't in the critical path). I fixed the sda1 menu.lst, booted into it, and now it works! 0710 loaded, and is now sitting at the AV Wizard Step 0. Thanks for all the help, mostly just correcting my boneheaded mistakes.

The net instructions I'm following now don't specify how to make the MBR point at the 0710 installer partition's menu.lst , even though that's the clean way to do this. If I have that MBR instruction, I'll revise and post this complete, tested process in the wiki.

That's why I choose to have a common /boot partition mounted by all my linux installations on this system. This sda1 (/boot) partition hold the MBR and the GRUB menu.lst. From there it points to different / (root) partition depending on the system to boot. And I can modify the menu.lst from any linux version I boot.

can you run (when you are stuck in initrd/initramfs):

Code Select Expand

# cat /proc/cmdline

This is just to check your parmeters.

Also can you mount sda3 "by hand" then?

Then I edited the partition's boot/grub/menu.lst:

Code Select Expand


title           Ubuntu 7.10, kernel 2.6.22-14-generic
root            (hd0,2)
kernel          /boot/vmlinuz-2.6.22-14-generic root=UUID=78785b3c-875f-4e35-8529-09f0e63d96ccro quiet splash
initrd          /boot/initrd.img-2.6.22-14-generic
quiet

title           Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root            (hd0,2)
kernel          /boot/vmlinuz-2.6.22-14-generic root=UUID=78785b3c-875f-4e35-8529-09f0e63d96cc ro single
initrd          /boot/initrd.img-2.6.22-14-generic


and the old menu.lst on /dev/sda1 (the 0704 active root partition mounted on /):

Code Select Expand


### END DEBIAN AUTOMAGIC KERNELS LIST

title           Ubuntu 7.10, kernel 2.6.22-14-generic
root            (hd0,2)
kernel          /boot/vmlinuz-2.6.22-14-generic root=UUID=78785b3c-875f-4e35-8529-09f0e63d96ccro quiet splash
initrd          /boot/initrd.img-2.6.22-14-generic
quiet


Is this a typo in your post or are you really missing a space between "78785b3c-875f-4e35-8529-09f0e63d96cc" and "ro" in your menu.lst?

Then edited the sda1 /etc/fstab:

Code Select Expand


# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# /dev/sda1
UUID=eae0e501-b376-42a3-991c-9f6f81a148c7 /               ext3    defaults,errors=remount-ro,user_xattr 0       1
# /dev/sdb1
UUID=1b6d32f8-21f0-4c8c-9252-0ba4175bfdce /media/sdb1     ext3    defaults,user_xattr 0       2
# /dev/sdc1
UUID=aeb4d8bd-d55d-417e-b0fc-cde3267d954b /media/sdc1     ext3    defaults,user_xattr 0       2
# /dev/sda5
UUID=39fa5a1b-76ae-405e-b87b-945965e2fdda none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0


When I reboot, I get the menu.lst that's in sda1, and boot the "Ubuntu 7.10" that I just added. As usual, it boots into only initrd and stops. Mount shows that this time, there isn't even an sda3 mounted anywhere when it grinds to a halt.

Did you change the /etc/fstab file on /dev/sda3 to match the partition UUID of your linuxmce system. Once you are booted on sda3 the fstab in sda1 is not used anymore. I am not even sure why you edited it.

The DVD installer will still wipe the drive you install to just as the current DVD installs do.

That's too bad ...

It is obviously not "required" as shown by the install procedure proposed by Zaerc previously ...

Why is it not just an option?

I downloaded kubuntu-linuxmce-0710-i386-beta-2.iso locally. But when I mounted the iso to take peek inside it I see the following in isolinux.cfg

" Install LinuxMCE 0710 for I386 ".

I hope this doesn't means that I can't install on my amd64 machine? As in the past installers have given me this problem...

Thanks in advance..

I installed kubuntu-linuxmce-0710-i386-beta-2.iso on an amd64 system without trouble.

JC

[exactly]

What is "the required tweaking in the GRUB config file" exactly? I've posted my menu.lst section that fails - what does it need to be, exactly, to work? Is there some kind of taboo against specifically quoting your grub configs in public or something 

Hello Matthew,

No there is nothing secret in the menu.lst file. But its content will depend on some choices you do at install time.

For example, on my system, I have mythbuntu (7.10) installed with the following partitionning:

/dev/sda1 -> /boot
/dev/sda2 -> swap
/dev/sda3 -> / (with the mythbuntu 7.10 install)

So using mythbuntu I decided to install linuxmce on /dev/sda4. My idea was to keep the mythbuntu install and add linuxmce on /dev/sda4 while having both linuxmce and mythbuntu sharing the same /boot (/dev/sda1) and swap (/dev/sda2). This allows to share the menu.lst and the kernels between the 2 systems.

So in the end, here is what I have in my menu.lst file:

Code Select Expand

# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default         2

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout         3

...

## ## End Default Options ##

title           Mythbuntu 7.10, kernel 2.6.22-14-generic
root            (hd0,0)
kernel          /vmlinuz-2.6.22-14-generic root=UUID=10e3ce7b-53ca-4090-ac60-c3c59617d9a4 ro quiet splash
initrd          /initrd.img-2.6.22-14-generic
quiet

title           Mythbuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root            (hd0,0)
kernel          /vmlinuz-2.6.22-14-generic root=UUID=10e3ce7b-53ca-4090-ac60-c3c59617d9a4 ro single
initrd          /initrd.img-2.6.22-14-generic

title           LINUXMCE 7.10, kernel 2.6.22-14-generic
root            (hd0,0)
kernel          /vmlinuz-2.6.22-14-generic root=UUID=41d0b807-e90d-446a-944c-9aff3a82ce03 ro quiet splash
initrd          /initrd.img-2.6.22-14-generic
quiet

title           LINUXMCE 7.10, kernel 2.6.22-14-generic (recovery mode)
root            (hd0,0)
kernel          /vmlinuz-2.6.22-14-generic root=UUID=41d0b807-e90d-446a-944c-9aff3a82ce03 ro single
initrd          /initrd.img-2.6.22-14-generic

title           Ubuntu 7.10, memtest86+
root            (hd0,0)
kernel          /memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

It is not necessarily the best solution but it works for me and I am happy with it so far.

The fact is that in the end the GRUB tweaking depends on your system and what you want to achieve. I don't think there is a single recipe.

Note: the above setting means I have done a bit more customization in /etc/fstab than Zaerc did in order to allow the /boot partition to be mounted by linuxmce. But it should be relatively trivial to deduce.

BTW, for people without an american/qwerty keyboard, don't forget to run "dpkg-reconfigure console-setup" after the first reboot to adapt your keyboard setting accordingly.

I hope it helps.

JC

Here is how I installed the beta2 ISO manually to a partition, without burning a DVD. 

...

Everything is done as the root user, and you will need to replace /dev/sdaX and /dev/sdaY with the partitions you created or want to use.  You will also need to configure a bootloader to start your partition, I used the existing GRUB install on another partititon and added extra targets to its /boot/grub/menu.lst.

No guarantees that this will give you a properly working system, but so far everything seems to work fine for me.

Thanks for sharing this ... It did work for me with the required tweaking in the GRUB config file.

So far the new install seems to be working OK.

JC

If you have not done it already, to reconfigure your system to use the closed source ATI video driver you might have to run:

# dpkg-reconfigure xserver-xorg

It will certainly default to the "vesa" driver and you might need to force it to ATI/radeon.

I hope it helps

Also something kind of related seems to be in the plan already:

http://wiki.linuxmce.com/index.php/Upcoming_Features

It looks like it is more or less in the plan already:

http://wiki.linuxmce.com/index.php/Upcoming_Features

I guess there is already a solution:

http://www.mythtv.org/wiki/index.php/FreeBox

I'll look into it ...

I am sure there are ways to hack this arround.

But I believe it would be nice to get this as some kind of configuration option somewhere (this is the  Feature requests & roadmap forum).

OK, I have not tried the TV yet.

But I assume it means the "director" knows how to switch off the TV (either through serial or with an IR transceiver).

If my TV is an unknown type and I have no IR tranceiver (yet), shouldn't it be possible for linuxmce to act as if it was a monitor and put the TV in "sleep" mode throught the video cable.

If I switch to the "normal" ubuntu desktop (ctrl alt 7) the monitor will go in sleep mode.

What is the rational that prevent linuxmce to do the same (at least as an option)?

I understand, but what need would I have to add one more equipement in my home setup when any PC out there (including the core) should be able to stream internet radio.

What would be the added benefit of Squeezebox compared to having a list of my favorite radio somewhere in the media menu of all the "directors" in my house? Do I miss something?

Beside Squeezebox is not distributed in France (or so it seems).