<SOLVE> Mylivecd No longer works

[Newlife]

Well, I have changed nothing but keep updated....
BUT, my copy no longer will boot.  Just hangs telling me there is an error or loop something....
Never had this problem until the updates starting in Jan 2011.... what is wrong???

newlife

[Linuzoid]

I had to install the draklive-install rpm, so Mylivecd would work, just today as a matter of fact. One of the updates removed that rpm and it's required for Mylivecd.

Peace

[AS]

Hello,

Well, I have changed nothing but keep updated....
BUT, my copy no longer will boot.  Just hangs telling me there is an error or loop something....
Never had this problem until the updates starting in Jan 2011.... what is wrong???

newlife

probably the default compression "xz" actually used from mylivecd, compared to the running kernel. You must specify --lzma option if you are using kernel older than 2.6.37.x

# mylivecd --help

  --lzma                          Use with kernels older than 2.6.37
   --gzip                          Use gzip compression for the image
   --xz                            Use xz compression for the image

also search the forum for additional info about different compression results.

AS

[YouCanToo]

I had to install the draklive-install rpm, so Mylivecd would work, just today as a matter of fact. One of the updates removed that rpm and it's required for Mylivecd.

Peace

Mylivecd will not even run if it is missing the draklive-install rpm. This does not sound like the issue he is having though.

[wedgetail]

Newlife
How are you trying to boot your re-mastered LiveCD?

What is the chance you kept a record of myliveCD process that generated the remaster?

[Newlife]

Thanks All...

Seemed easiest to upgrade the kernel so that's what I did and now all is OK.

I wonder why the upgraded kernel is not included in upgrades, etc.
n

[djohnston]

I wonder why the upgraded kernel is not included in upgrades, etc.

New kernels are not installed as part of the normal update process. You have to manually select the desired kernel in Synaptic, then mark it for installation. After installing a new kernel and rebooting, the last kernel installed becomes the default one.

[wayne1932]

I wonder why the upgraded kernel is not included in upgrades, etc.

New kernels are not installed as part of the normal update process. You have to manually select the desired kernel in Synaptic, then mark it for installation. After installing a new kernel and rebooting, the last kernel installed becomes the default one.

I don't believe all of  this is true.   I chose to  upgrade my kernel yesterday to 2.6.38-8  and it was added as the final option on the grub menu but not the default.  The default stayed as it was.  Becoming default may have been true for a short while, but I think that the original behavior was to add it as another option, but not default.  

[djohnston]

I don't believe all of  this is true.   I chose to  upgrade my kernel yesterday to 2.6.38-8  and it was added as the final option on the grub menu but not the default.  The default stayed as it was.  Becoming default may have been true for a short while, but I think that the original behavior was to add it as another option, but not default.  

Yes, it is true. You can verify it for yourself. If you chose the default option in the GRUB boot menu, then open a terminal and enter uname -r. It will show the kernel version last installed.

The reason is that /boot/vmlinuz is a soft link to the default kernel. In my case, it would be vmlinuz-2.6.38.7-pclos1.a64. To find which one is default on your system, open a terminal and enter:

ls -l /boot/vmlinuz

You can see, in my case, which file is pointed to by the vmlinuz link.

lrwxrwxrwx 1 root root 27 Jun  4 09:54 /boot/vmlinuz -> vmlinuz-2.6.38.7-pclos1.a64

When you install a new kernel in Synaptic, the vmlinuz soft link is updated to point to the kernel just installed.