@jap

The problem is GRUB can't find the kernel. Here is a guide that might help you out. Wish I had had it when I was screwing around with Gentoo... In my case, I had a typo in my "grub.conf" or the kernel's filename (take your pick). There was an underscore where a dash should have been (or vice versa). I didn't see it until I'd recompiled the kernel and saw both files listed.

_________________
Unless otherwise explicitly stated, this message is not meant to affirm nor deny, defend nor offend any faction within the 'Amiga' Community.

@ShadesOfGrey: Thank you for the advice (I get the same error). The problem is, that recompiling the kernel is too complicated for a linux-newbie like me. So I have to wait for an update

_________________
AmigaOne X5000/40, 2.2 Ghz, 4 GB RAM, Radeon R9 280X, M-Audio Revolution 5.1, 240 GB SSD

@TrevorDick

The installer doesn't touch your existing grub configuration. It creates its own grub.conf file in /mnt/xamiga/boot/grub - if you copy these lines to your existing grub.conf and add an option to boot X-Amiga, it ought to work OK.

I had to compromise a bit - really didn't want the installer messing up people's systems!

On the other hand, if it's installed all by itself on a hard drive (disk 1, partition 1), it should boot up straight away.

Hope that helps!

Amir

(BTW, sorry there's not more info on the website - this was released in a slight rush before I had to leave the country for a week! I'll update the instructions as soon as I'm back.)

@Petah

Hmm... I was wondering when someone was going to ask this...

The kernel takes up the most space (about 18MB), because it needs to contain drivers for as much hardware as possible. If you are willing/able to configure your own, that would be reduced to ~2MB - a huge difference. For instance, the kernel for my own computer is 1.8MB.

For general use, some tools had to be installed. 'sudo' is essential for security, otherwise you'd be running the system as a root user. Networking tools are optional, of course. 'e3' is a basic text editor - pretty useful if you're dropped out of the emulation and need to quickly edit your E-UAE configuration. Not all the ALSA utilities are necessary. Getting rid of 'alsamixer' would allow you to also cut out 'ncurses' library, which would free up another 1-2MB. (However, ncurses is essential if you need to re-install GRUB for any reason).

Doing all this would leave a system ~20MB in size.

You could go further and squash read-only files (using squashfs), which would reduce their size by 2/3. Quick estimate: I think it may be possible to do the whole thing in under 10MB.

However, I figured that the difference between 20MB and 40MB was inconsequential for multi-gigabyte hard drives so I left it as is. It provides a fair balance between size and utility, but can be easily hacked if one wishes.

Amir

Last edited by Fractallyte on 10-Nov-2007 at 01:45 PM.

@jap

Can you please send me your installer log file and and grub configuration? (Be patient for a reply as I can't check my email until next week.) I tested this exhaustively, it worked every time for me. Unless a typo crept in at the last moment...

Amir

I've been using the beta release and have been experiencing problems installing.

Some background, logical partition ready in all cases (500mb and 1Gb) formatted ext2 on KT133 and Intel ZX and based machines.

Under the console route, it detects the hardware but there seems to be no install option at the end, there could be but it passes through too quickly, for me to register.

Under loadwb, everything is installed but I have to adjust the grub entry from vmlinux to kernel (this could be because of the existing grub setup) and during the bootup routine it gets to two ACPI entries, the screen blanks, and shutdown routine is invoked. Leaving me with a shutdown machine.
I have tried kernel options - noacpi and acpi=off, but they don't work.

Has anyone had any success, and how did you do it?

Last edited by Jeff2 on 10-Nov-2007 at 04:27 PM.
Last edited by Jeff2 on 10-Nov-2007 at 04:25 PM.

I had a message saying like "Failed to load Operating System" after installation (not even the bootloader was shown)!

@AP

Uh, I think you may have misunderstood. The problem I experienced was due to a typo in my grub.conf pointing to a kernel image that wasn't present or the name I gave the kernel (depending on how you look at it). Since they didn't match, GRUB blew up. I realized the error after a recompile because I used the exact 'spelling' of the kernel's file name from grub.conf. When I listed the /boot directory, I could see both files and identify whay GRUB was confused.

The document I linked to offers solutions to common GRUB errors. None of them require a recompile. However, they do say it can't hurt to recompile. If you follow the Gentoo Handbook, compiling your own kernel isn't all that difficult... Just time consuming.


Anyway, it looks like Fractallyte's posts in this thread may resolve the GRUB issues.

Last edited by ShadesOfGrey on 10-Nov-2007 at 09:22 PM.
Last edited by ShadesOfGrey on 10-Nov-2007 at 09:20 PM.

_________________
Unless otherwise explicitly stated, this message is not meant to affirm nor deny, defend nor offend any faction within the 'Amiga' Community.

Second try, and I'd say "Mission Impossible", won't try it again !

@martinalexander

Looks like GRUB is causing problems for everyone... I'll re-examine this, perhaps give an option for syslinux as an alternative bootloader.

Post your installer log file to me please! (Send me a pm, rather than email)

Yes, but then on the other hand I cant create a part. as "/root", but only gets the weird options like "boot, hidden, lba, lvm, palo, prep, raid" !

Any bootloader, just if it works good...

Here's the GRUB fix, tested and working in qemu:


Boot from the X-Amiga CD. (There's no need to 'loadwb'.)

Type the following:

mkdir /mnt/xamiga
mount /dev/hda1 /mnt/xamiga
grub-install --root-directory=/mnt/xamiga /dev/hda
cd /mnt/xamiga/boot/grub
ln -s grub.conf menu.lst
cd /
umount /mnt/xamiga

Then reboot


I'm putting it up on the website asap.

1 Question: IS this the reason it says "Failed to load operating system" !?

@martinalexander

Um... I think so...

Normally that kind of message pops up if the hard drive is blank or disconnected. I guess it might also appear if there's no bootloader. Since everyone seems to be having similar grub problems, I think the above fix will work for you too.

Hehe, hope so or it will be the third time to reinstall XP since friday !

Quote:

Boot from the X-Amiga CD. (There's no need to 'loadwb'.) Type the following: mkdir /mnt/xamiga mount /dev/hda1 /mnt/xamiga grub-install --root-directory=/mnt/xamiga /dev/hda cd /mnt/xamiga/boot/grub ln -s grub.conf menu.lst

Should this be done BEFORE you install X-Amiga, and won't Grub be overwritten when choosing boot-loader during installation then (or should I simply do this first and choose "no boot-loader" during installation) ?

And how about the harddrive, should I create an empty Ext2/Ext3-partition with the boot-flag (root-flag is not available) before doing this???

Last edited by martinalexander on 12-Nov-2007 at 04:53 PM.