Cannot add Kahel on Grub « Kahel OS Forum

Kahel OS Forum » General Forum » Newbie Corner

Cannot add Kahel on Grub

(21 posts) (4 voices)

Started 1 month ago by Sybelius
Latest reply from fplolz

Tags:

Sybelius
Member

Hi All :)

Recently I have been discovering Kahel and installing it on my computer desktop, but it is not starting at boot; I have been not installing Kahel's Grub, thinking to add it on my Grub (Grub, not Grub2) already installed on my machine.
I have been adding all distros of mine to Grub using this formula:

title Slackware 13.0
root (hd0,"x-1") [x-1 = dev partition -1]
kernel /boot/vmlinuz ro root=/dev/sda"x" [x = dev partition number]

it is working fine, just about Chakra (Arch Linux based) the right formula is:

title Chakra Alpha 4 -New Age-
root (hd0,13)
kernel /boot/vmlinuz26 root=/dev/sda14 ro
initrd /boot/kernel26.img

both of them are not good for Kahel. Please, could you suggest me the right formula to add Kahel on Grub?
I am Italian and I know that my English language is not fluent; please, apologize me for that.

Best Regards from Botswana :)

Posted 1 month ago #
Fenrin
Member

hi Sybelius,

just mount your /boot partition of KahelOS from your installed Slackware and then compare the menu.lst file from the KahelOS partition with the grub configuration file of Slackware and add the entry from KahelOS.

thats my entry for KahelOS:
# (0) Kahel OS (Desktop Edition)
title Kahel OS (Desktop Edition)
root (hd0,7)
kernel /vmlinuz26 root=/dev/disk/by-uuid/95b3511f-8b3c-46af-872f-6e4104d00330 rootfstype=ext3 resume=/dev/sda11 fastboot ro quiet splash
initrd /kernel26.img

Posted 1 month ago #
Sybelius
Member

Hi Fenrin,

Thank you very much for your kind help, I have been trying to follow your teaching but something is wrong; maybe I dont understand you properly. So, now I go to explain to you the procedure I did:
- After to be getting the UUID number about the partition where Kahel is installed, I have been adding on Grub menu.lst the following data:

#(0) Kahel OS Desktop 25.XII.2009
title Kahel OS Desktop 25.XII.2009
root (hd0,11) (>> Kahel is on part. nr. 12)
kernel /vmlinuz26 root=/dev/disk/by-uuid/107a00d1-2b86-426a-8b23-3c870e8eb26e rootfstype=ext4
resume=/dev/sda6 fastboot ro quiet splash (>> Grub is on part. nr.6)
initrd /kernel26.img

At reboot, selecting Kahel from Grub, the following warning comes out:

Booting 'Kahel OS Desktop 25.XII.2009'

Root (hd0,11)
Filesystem type is ext2fs, partition type 0x83
Kernel /vmlinuz26 root=/dev/disk/by-uuid/107a00d1-2b86-426a-8b23-3c870e8eb26e rootfstyle=ext4

ERROR 15: file not found

Press any key to continue...

Ciao :)

Posted 1 month ago #
Fenrin
Member

no problem :)

I think your new entry works almost. The resume=/dev/sda11 command is probably not necessary. If you use it, you should put your swap partition here I think.

If you don't use a seperate boot partition for KahelOS, you have to use "initrd /boot/kernel26.img" instead of "initrd /kernel26.img"

If thats not the reason why it doesnt find the file, try the following under your Slackware:
1. mount your KahelOS partition (for example with "mkdir /media/KahelOS" and "mount /dev/sda12 /media/KahelOS" in the terminal under root; it has to be the partition of KahelOS with the grub configuration file so either / of KahelOS or if you made a seperate /boot at the installation of KahelOS the boot partition)
2. then use nano or gedit to see the menu.lst file ("nano /media/KahelOS/boot/grub/menu.lst" or "nano /media/KahelOS/grub/menu.lst" if you have a seperate boot partition)
3. modify your /boot/grub/menu.lst file of Slackware Linux with the correct entry.

I hope this helps.

Ciao ;)

Posted 1 month ago #
Sybelius
Member

Hi Fenrin,

Plesa apologize me because due my lack of experience, I am afraid to disturb you; I have been trying to follow your last teaching but I did mistake, I suppose, because I have been changing Kahel's record under Slackware using "nano", but I dont know how to use this editor, so I am afraid that I did not been giving the right command to save the change.
Now, I am a bit confused, let me to explain you that Grub is not on Slackware, but on Sabayon 5.1 Gnome, mounted on /sda6.
Today I have been trying to use the commands you have been suggesting me on Sabayon, but menu.lst comes out blank; if I type on terminal (root) the command "sudo gedit /boot/grub/menu.lst" comes out this one:

# grub.conf generated by the Sabayon Linux Installer
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,5)
# kernel /boot/kernel-genkernel real_root=/dev/sda6
# initrd /boot/initramfs-genkernel
### AUTOMAGIC BOOT DEVICE DETECTION -- DO NOT REMOVE ###
#boot=sda
### AUTOMAGIC BOOT DEVICE DETECTION END ###
default=0
timeout=10
splashimage=(hd0,5)/boot/grub/splash.xpm.gz

title Sabayon Linux (kernel-genkernel-x86-2.6.31-sabayon)
root (hd0,5)
kernel /boot/kernel-genkernel-x86-2.6.31-sabayon root=/dev/ram0 ramdisk=8192 real_root=/dev/sda6 dolvm init=/linuxrc splash=silent,theme:sabayon vga=791 console=tty1 quiet resume=swap:/dev/sda5 real_resume=/dev/sda5
initrd /boot/initramfs-genkernel-x86-2.6.31-sabayon
savedefault

title Sabayon Linux (kernel-genkernel-x86-2.6.31-sabayon) (safe mode)
root (hd0,5)
kernel /boot/kernel-genkernel-x86-2.6.31-sabayon root=/dev/ram0 ramdisk=8192 real_root=/dev/sda6 dolvm init=/linuxrc console=tty1 resume=swap:/dev/sda5 real_resume=/dev/sda5 nox gentoo=nox acpi=off ide=nodma vga=normal
initrd /boot/initramfs-genkernel-x86-2.6.31-sabayon
savedefault

title Other Operating System - Microsoft Windows
rootnoverify (hd1,0)
chainloader +1
savedefault

title Absolute 13.0.4
root (hd0,6)
kernel /boot/vmlinuz ro root=/dev/sda7

title Chakra Alpha 4 -New Age-
root (hd0,13)
kernel /boot/vmlinuz26 root=/dev/sda14 ro
initrd /boot/kernel26.img

#(0) Kahel OS Desktop 25.XII.2009
title Kahel OS Desktop 25.XII.2009
root (hd0,11)
kernel /vmlinuz26 root=/dev/disk/by-uuid/107a00d1-2b86-426a-8b23-3c870e8eb26e rootfstype=ext4
resume=/dev/sda6 fastboot ro quiet splash
initrd /boot/kernel26.img

title Mint 8 Helena
uuid 6567051c-476e-4a79-b3e8-96e66da964e9
kernel /boot/vmlinuz-huge-smp-2.6.31-smp root=/dev/sda15
savedefault
boot

title Salix 13.0.2a
root (hd0,9)
kernel /boot/vmlinuz ro root=/dev/sda10

title Slackware 13.0
root (hd0,7)
kernel /boot/vmlinuz ro root=/dev/sda8

title Slackware 13.0 64 Bit
root (hd0,8)
kernel /boot/vmlinuz ro root=/dev/sda9

title Vector Linux 6.0 Standard Edition Gold
root (hd0,10)
kernel /boot/vmlinuz ro root=/dev/sda11

title Zenwalk 6.2
root (hd0,12)
kernel /boot/vmlinuz ro root=/dev/sda13

If I try to use one of these two commands "nano /media/KahelOS/boot/grub/menu.lst" or "nano /media/KahelOS/grub/menu.lst", "menu.lst" comes out blank.
Now I am really confused, so I am writing to you showing the present Grub/menu.lst without adding other clues, just explaining that I manage Grub under Sabayon.
Thank you very much again, for your kind attention.

Mabuhay :) (this is the Tagalog word to say "ciao", I suppose).

Posted 1 month ago #
Fenrin
Member

ok really no problem I was also a linux noob a few years ago ;)

I forgot to tell you that you have put /boot before the /vmlinuz26, if you dont use a seperate /boot for KahelOS. So try it with "/boot/vmlinuz26" instead of "/vmlinuz26".

If you dont know how to use nano, you can use gedit instead. If you want to see the menu.lst file of KahelOS you have to mount the correct partition first. You can open a filebrowser (e.g. Nautilus or the filebrowser of kde4) to check if the correct partition with a folder /boot is mounted.

If sda5 is your swap partition you can replace the "resume=/dev/sda6" with "resume=/dev/sda5".

ciao

Posted 1 month ago #
Sybelius
Member

Dear Fenrin,

I have been working on the file menù.lst using Gedit from Sabayon; these are the Kahel's data now:

#(0) Kahel OS Desktop 25.XII.2009
title Kahel OS Desktop 25.XII.2009
root (hd0,11)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/107a00d1-2b86-426a-8b23-3c870e8eb26e rootfstype=ext4
resume=/dev/sda5 fastboot ro quiet splash
initrd /boot/kernel26.img

Something has been changing, selecting Kahel at boot, now the monitor starts to flash :) and to move forward, I have to use control>alt>cancel (reboot).

Well, something new, today ! My Best Regards for You. Ciao

Posted 1 month ago #
Fenrin
Member

Hey Sybelius,

If the screen goes black its maybe a kernel mode setting problem. If you have a radeon card you can add "radeon.modeset=0" to the line "kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/107a00d1-2b86-426a-8b23-3c870e8eb26e rootfstype=ext4 resume=/dev/sda5 fastboot ro quiet splash". If you still have problems try it with "nomodeset" instead.

Other commands which can help to succesfully boot up: acpi=off, pci=routerirq, nosmp

Ciao

Posted 1 month ago #
Sybelius
Member

Ciao Fenrin :)

It seems never reaching the end of this issue :)
I have been changing the menu.lst doing attempts with:
1- radeon.modeset=0
2- radeon.nomodeset
3- Adding on both options: acpi=off, pci=routerirq, nosmp
Nothing changed; exctly, the screen does not going black: selecting Kahel on Grub, it is starting now, showing text's mode, but after some seconds, it disappear and the screen assume blue color (or another color, depend about the various changes I make in the menu.lst formula); after that, to go forward, I have to use control>alt>cancel to reboot.
This one is the present Grub's formula:

#(0) Kahel OS Desktop 25.XII.2009
title Kahel OS Desktop 25.XII.2009
root (hd0,11)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/107a00d1-2b86-426a-8b23-3c870e8eb26e rootfstype=ext4 radeon.nomodeset
resume=/dev/sda5 fastboot ro quiet splash
initrd /boot/kernel26.img
acpi=off
pci=routerirq
nosmp

Ciao :)

Posted 1 month ago #
Fenrin
Member

Ciao Sybelius :)

try it with "nomodeset" instead of "radeon.nomodeset". Its better not to use the commands acpi=off,
pci=routerirq, nosmp if they dont help.

Does It load the gdm daemon? Or what else is the last text message you see at the boot process?

Ciao

Posted 1 month ago #
Sybelius
Member

Ciao Fenrin,

I did, but has been changing just the color of disappeared monitor -lol-
Sorry, I dont know what is "gdm daemon"; now, I am going to try the boot's process:
- After selecting Kahel on Grub, it is starting like the "verbose mode" common to all Linux distros, but after few seconds, the words on the monitor are disappearing and the screen become almost light blue with some spots down side (like when you see "snow's effect" on tv when any channel is working).
I am unable to read what is flowing on the monitor, because it is too much fast.

Ciao :)

P.S.
You are from Philippines, do you like aquarium fish (freshwater or seawater)?
Aquarium is an other passion of mine and I remember when I was in Italia, many aquarium fish was imported from Philippines

Posted 1 month ago #
Fenrin
Member

Ciao Sybelius,

GDM is the graphical login manager of the gnome desktop. Maybe the issues starting after loading GDM or at a certain kernel module, I dont know.

You can also try it with the following entry. But if it works, it would not load the graphical user interface.

title Kahel OS Desktop 25.XII.2009 (Safe Mode)
root (hd0,11)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/107a00d1-2b86-426a-8b23-3c870e8eb26e rootfstype=ext4 radeon.nomodeset resume=/dev/sda5 ro single
initrd /boot/kernel26-fallback.img

If it boots up succesfully, it will ask for the root passwort, enter it. Then you could type "su username" and your userpassword. Then try the commands "startx" or "gnome-session". It will probably not load the GUI but maybe you can read a error message.

I hope anyone else can help you here, because I dont know what else could solve your issue, sorry. I have experience in linux as a user for a few years, but im not an linux expert or developer.

Ciao :)

P.S.
Im from Central Europe and im not very interested in aquarium fishes.

Posted 1 month ago #
Sybelius
Member

Ciao Fenrin,

Please, apologize me for my mistake, I was sure you writing me from Philippines, not from Europe, sorry.
Talking about Kahel, after the new Grub formula, nothing is changed. Dont worry, I will keep it on my computer still for sometime, waiting for the right solution, if nothing comes out, I will remove it. Maybe a new release comes out and I will be trying again.

Thank you very much for your concern. Ciao :)

Posted 1 month ago #
Fenrin
Member

Hey,

ok no problem :)

Maybe anyone else can help you with this boot problem.

Ciao

Posted 1 month ago #
joelbryan
Member

the "root (hdx,y)" line is where grub should look for your installed kernel, and grub starts counting from 0, so (hd0,0) is equivalent to /dev/sda1.

If you are using the most recent filesystems like btrfs, ext4 and nilfs2, you should make sure that grub can read your kernel, the default Kahel OS with automatic partition has a separate /boot partition formatted as ext2, allowing grub to read it so it would be possible to mount these newer filesystems.

Another way to do this is to copy your KahelOS's kernel26.img, vmlinuz26, System.map26 on a directory under your other's OS's /boot, example your grub is installed on debian, and it boots fine with it, so just mkdir /boot/kahel on your debian's /boot partition then copy the KahelOS's files, then on your menu.lst, reference your KahelOS's files as /kahel/.. and the root=/dev/by-uuid/... line in your kernel should be the the exact Kahel's / root partition, so /dev/sda3 in the default KahelOS's install with automatic partitioning.

Posted 1 month ago #
Sybelius
Member

Hi Joelbryan,

Thank you very much for your concern, but due my lack of experience, I am unable to get you.
I can say that I have been doing manual partition and that having ten different distros installed, I am unable to reconaize the partition where Kahel is (missing the partition label); I know that Grub is on Sabayon, which is on /dev/sda6. (All distros mounted on "/" only; no "/home", no "/boot").
Was coming to my mind this idea: it is right if I install Kahel again, with his own Grub adding manually the distros which it is not automatically adding on menu.lst ?

Ciao

Posted 1 month ago #
fplolz
Member

i might not really understand with what you're are saying
but please be patient with me .
I presume , from reading earlier post , is that you already have Sabayon on your computer and you want to install Kahel OS along side with it

Reading what you have said , your boot partition is merged together with your root partition
Therefore the grub menu config ( assuming you are using Grub and not grub 2 ) is in /boot/grub/menu.lst ...

UUIDs are a way of identify your partitions instead of the standard /dev/sdax ..which unlike UUID ...the standard /dev/sdax can change according to the situation ..
Therefore , it all depends on where you have installed you have installed your grub to

The MBR ? or the root parition of Sabayon

There are quite a number of easy ways to multi boot 2 or more distros simultaniously..
If you have installed Grub on to the MBR , than choose installing Kahel without grub
After that , find Kahel's root partition...You should know which parition you installed to ...and add it to the menu.lst

Or ...if you have installed Kahel first , than install the other distro with out grub or grub to root partition of that distro ...Than add the distro's kernel location to Kahel's menu.lst..

Hope it goes well :)

Posted 1 month ago #
Sybelius
Member

Hi Fplolz,

Thank you for your concern, I try to explain: Sabayon is the first OS I have been installed and grub is with it; looking at GParted, I see that Sabayon has the flag "boot".
After that, I can tell you that as you can see in the thread, I have been triyng many formulas to put Kahel (which is already installed as other distros manually added on Grub menu.lst and just Kahel is not starting) on Grub menu.lst, using the UUID or not, no way ! :) Kahel does not starting.
Maybe I have to tray installing Kahel again with his own Grub, I am not decided yet because I am afraid to get problems with other distros; maybe I will do it, and could install Grub again if nothing starting :)

Ciao

Posted 1 month ago #
fplolz
Member

Have you tried installing Kahel without its own grub ?
That way , you would just have Kahel's kernel in the /boot folder of the root partition

than , in your grub menu ,

title Kahel OS (Desktop Edition)
root (hd0,X)
kernel /boot/vmlinuz26 root=/dev/sdaX rootfstype=ext4 resume=/dev/sdaX fastboot ro quiet splash
initrd /boot/kernel26.img

The X in as shown up there are to be replaced by the partition where you have stored and installed kahel's kernel to...If you have gave kahel a boot partition of its own , than remove the /boot from the /boot/X
where X is the term/file you are definding

and change the root filesystem type accordingly to the file system you are using...

Which partition have you installed Kahel to ? May i know ? :) ..

Posted 1 month ago #
Sybelius
Member

Dear Fplolz,

Please, allow me to tank you for your kind concern; I have been trying the new suggested formula and about Kahel the menu.lst is this one now:

title Kahel OS Desktop Edition 25.XII.2009
root (hd0,11)
kernel /boot/vmlinuz26 root=/dev/sda12 rootfstype=ext4 resume=/dev/sda12 fastboot ro quiet splash
initrd /boot/kernel26.img

Something has been changing indeed :)
Before, Kahel was starting showing the verbose mode and after few seconds the screen starting flashing.
Now, clicking on Kahel's Grub link, comes out the screen without flashing and with a nice orange color :)
I am thinking to give up; maybe you understood that Kahel has been installed on a "school_boat_machine" and it was on the last free one partition; now, I have just discovered a new distro Slackware based (Kongoni) and I am wishing to discover it.
About Kahel, due my lack of experience, better if I am waiting for a new release, maybe I got that problem because it is so young and for that reason, so delicate :)
Answering to that question of yours, Kahel is installed on logical partition (/sda12), on 320 GiB Sata disk; the disk has an extended partition fitting it totally; the extended partition has ten (+1) logical partition almost 30 GiB each (+ 2 GiB for swap partition).

My Best Greetings for You :)

Posted 1 month ago #
fplolz
Member

hm..i hope you dont give up ..:o
Experience is gained when you try something harder :)

Posted 1 month ago #

RSS feed for this topic

Reply

You must log in to post.