Page 1 of 2

Posted: Thu 08 Feb 2007, 15:53
by can8v
prralex,

You need to add a line to your menu.lst file. It should look something like this:

#Linux bootable partition begin
title Linux on (on /dev/hda3)
root (hd0,2)
kernel /boot/vmlinuz root=/dev/hda3 ro vga=normal
initrd /boot/initrd.gz
#Linux bootable partition end

That is assuming you have an option 1 (normal) install
If you are attempting a coexist (option 2) the try something like this:


#Linux bootable partition begin
title Linux on (on /dev/hda3)
root (hd0,2)
kernel /boot/vmlinuz root=/dev/ram0 pmedia=idehd
initrd /boot/initrd.gz
#Linux bootable partition end

Good Luck
CAn8v

alright! get around the supply "init= "thingy!

Posted: Thu 15 Feb 2007, 06:58
by prralex
ok, after... you've done yer file install in muppy linux and yer grub config... what you have to do is mount the muppyinstall cd. and copy initrd.gz from the / folder to the /boot folder on your newly installed partition (whereever that might be... :)

then! unzip the thing.
then! rename the thing 'init'
then! copy a copy to the /boot/grub/ folder
(prob not nessesary to do this, but i like to
be sure... :)


annoying as hell, but what'cha gonna do.
this works with muppy 211.

thnx,
love 'dis 'ting!

l8r/ra
:lol:

heh, ok re-installed to test my theory nope!!! now what!!

Posted: Fri 16 Feb 2007, 00:09
by prralex
well, then i had a thought that saving the
personal config file onto the freashly created
muppy install. in my case, /dev/hda8.

... you know the one it creates for you somewhere
between 32m and 512m? believe it or not
it is actually good for something.

so i rebooted and of course ... no kernel panic.

let this be a lesson to us all so quick to
make the short cuts at all the wrong
places ...

:lol:

'k, now how do i install the muppy.212.sfv package now?

ok, for sure this time....:)

Posted: Mon 19 Feb 2007, 23:54
by prralex
i did a re-install and the idea of save files plus extra mupp_212 package and all and it still didn't boot. so then i got the idea of doing the copy initrd.gz to root folder and in boot folder, unzipped, copied and named init... then drop copies of each in boot and /boot/grub. then it seemed to work. sigh.

anyhoo. l8r/ra and i hope this has turned out instructive.

right now i'm extracting m2v from a ffmpeg offa divx of some latest cool looking movie. had to do this by hand, and the audio extraction seems to work ... i'll see if i can get the re-multiplex option going and post results to here.

ffmpeg -i gr.mpg -target ntsc-dvd -aspect 16:9 -an -y gr.m2v

finally!!! fixed/ working

Posted: Tue 27 Feb 2007, 18:39
by prralex
heh, added another 128meg ram stick to the beasty 'puter, and muppy212 installs no problem.

so happy! was betting... oh it's gonna do the kernel panic thing again... and this time... not!

total ram in 'puter 256megs.

oh!my!god! yet again!

Posted: Tue 27 Feb 2007, 21:11
by prralex
so i'm looking at it again wondering what on earth i did to deserve this... then i figured out that maybe if i ran an upgrade on the new partition maybe that would solve it... seemingly it seemed that some essential folders were missing in the / ... like sbin.

so once again into the install..
after choosing the hard drive,
pick 'normal', then instead of
wipe, choose 'upgrade'.

i think this dumps the
first part of muppy on
the drive.

and maybe if yer lucky
you'll see something other
than 'kernel panic: please
pass the init code.'

l8r/ra
luvu

bla!

Posted: Tue 27 Feb 2007, 21:13
by prralex
bla-bla!