We tried the easy way, and the kernel images are stripped so mkvmlinuz will not handle them properly.

I tried compiling them myself to get a full kernel image (and make some modifications to reduce size and redundancy - kill off all the inbuilt Mac drivers etc.) but the Ubuntu toolchain has something REALLY weird going on with it (on a clean system with working gcc and binutils it tells me I need binutils 2.12.1 or higher - I am running 6.06.1 with the latest binutils and everything updates automatically. This is ridiculous.

We are in contact with Ubuntu staff directly on this, there has to be a cute, automated way to get these kernels and support Pegasos users, and some documented reason why I can't build a kernel myself from a clean install of 6.06.1

_________________
Matt Sealey

Sorry, I must admit, that I never used mkvmlinuz myself. I'm not familiar with Debian / Ubuntu package management, and was happy with the SUSE script anyway All my concern was to make Ubuntu install as smooth as possible.

The 'mkvmlinuz' script included in Ubuntu is broken. A working version is available in Debian testing. AFAIK, it was documented a few times here in the forum.

czanik@ubuntu:~$ uname -a
Linux ubuntu 2.6.15-26-powerpc #1 Thu Aug 3 02:53:39 UTC 2006 ppc GNU/Linux

_________________
CzP
http://czanik.blogs.balabit.com/

Ok, so what's the fix here? Install 5.10 using ubuntu_d_inst, boot it with ubuntu_d_boot, upgrade to 6.06.1, then make a new kernel boot image?

--
moto

No. I expected, that those two files from /install/powerpc will be uploaded right after my post. Now I see, that I have to download 700MB

_________________
CzP
http://czanik.blogs.balabit.com/

I can upload the files when I get home. I have a 6.06.1 CD on my desk.

--
moto

I'm just writing the CD. The install kernel is ready, I just need to test it, if it really works.

_________________
CzP
http://czanik.blogs.balabit.com/

That's great! So what will be the result, a new ubuntu_d_inst and ubuntu_d_boot?

--
moto

OK, tested succesfully. I'll upload a ubuntu_d_inst1 to genesi.hu. The URL will be: http://genesi.hu/ubuntu/ubuntu_d_inst1 and available within a few minutes.

I won't upload a 'desktop' specific boot kernel, as the 'alternate' should work fine (at least worked fine with the original release), and I can't install 'desktop' at the moment to dig out the supplied kernel files.

To start the Ubuntu installer, you need to start it with the following command line: Have fun!

_________________
CzP
http://czanik.blogs.balabit.com/

Nice one - cheers! So I use ubuntu_d_inst1 to install it, then ubuntu_a_boot to boot the installed system, right?

--
moto

Yes. Boot it with: Where X=letter for the HDD and Y=partition number

_________________
CzP
http://czanik.blogs.balabit.com/

Well czp, you totally rock Your new ubuntu_d_inst1 image works perfectly for booting the install environment from the CD and carrying out the install, and ubuntu_a_boot1 boots the installed system without a hitch. I'm posting this from Firefox under Ubuntu 6.06.1 on my PegII Next challenge - GRUB

Many *many* thanks!

--
moto

motorollin

What kernel is installed? Are you using an FFS partition for the boot image? Why do you need to use GRUB if the second question answer is yes?

magnetic

Not sure what kernel it installed. I would imagine it's whatever Ubuntu installs. The boot image is on an SFS partition (I'm using OpenFirmware 1.2 which can read SFS partitions).

You don't need GRUB to boot Linux. You can either manually type a boot command in OF or change the env variables to auto-boot the Linux boot image. However, I want a boot menu to choose between MorphOS and Linux. So you create a GRUB boot image with options for the Linux and MorphOS boot images, and then specify the GRUB image as the OF boot image.

--
moto

After installing the boot menu, I found that it isn't actually GRUB. It's just a Forth script for OpenFirmware. I downloaded BootCreator, modified one of the examples to match my MorphOS and Ubuntu installations, and then used BootCreator to create a boot script called "bootmenu". I then changed my OpenFirmware boot-file variable to "bootmenu", and now when I boot my PegII I get a nice menu asking me to choose between MorphOS and Ubuntu

--
moto

that's a well known process, most morphos users use bootmenu which is available for Linux and MorphOS.
My Ubuntu entry in bootmenu launches grub2 so i can have several options for loading ubuntu and don't need to worry about kernel upgrades as it always boot the last kernel (it boots the symlink actually).
By booting ubuntu directly through bootmenu you may experience problems when an ubuntu kernel update is available.