Boot Problem...

[Mehmet Fatih AKBULUT]

hi all.
recompiled kernel and named it to vmlinuz_mehmet.
when when booting from newly created kernel i got a kernel panic error which
says root LABEL cannot be opened or read.
below u can see the grub.conf /*normal and newly created ones*/.

title Fedora Core (2.4.22-1.2115.nptlsmp)
        root (hd0,1)
        kernel /boot/vmlinuz-2.4.22-1.2115.nptlsmp ro root=LABEL=/
hdc=ide-scsi rhgb
        initrd /boot/initrd-2.4.22-1.2115.nptlsmp.img
title Fedora Core-up (2.4.22-1.2115.nptl)
        root (hd0,1)
        kernel /boot/vmlinuz_mehmet ro root=LABEL=/ hdc=ide-scsi rhgb
what should i write or change the bold part (starting from ro ...) ?
any suggestion ?

[Kam Leo]

On 12/4/05, Mehmet Fatih AKBULUT  wrote:
> hi all.
>  recompiled kernel and named it to vmlinuz_mehmet.
>  when when booting from newly created kernel i got a kernel panic error
> which says root LABEL cannot be opened or read.
>  below u can see the grub.conf /*normal and newly created ones*/.
>
> title Fedora Core (2.4.22-1.2115.nptlsmp)
>          root (hd0,1)
>          kernel /boot/vmlinuz-2.4.22-1.2115.nptlsmp ro root=LABEL=/
> hdc=ide-scsi rhgb
>          initrd /boot/initrd-2.4.22-1.2115.nptlsmp.img
>  title Fedora Core-up (2.4.22-1.2115.nptl)
>          root (hd0,1)
>          kernel /boot/vmlinuz_mehmet ro root=LABEL=/ hdc=ide-scsi rhgb

^
              |
Is there an initrd for the new build or did you just omit posting it?
> what should i write or change the bold part (starting from ro ...) ?
>  any suggestion ?

[Mehmet Fatih AKBULUT]

hi Kam.
i noticed that missing part too. but checked  the folder and saw nothing but
old initrds.
however compilation gave no error. why initrd missing then ?
or do we really need that missing line ?
treat me as if i am a newbie :p
cos this is the first time em compiling kernel.
satisfactory help will be greatly appreciated :p
Regards.
Bye

[Kam Leo]

On 12/4/05, Mehmet Fatih AKBULUT  wrote:
> hi Kam.
>  i noticed that missing part too. but checked  the folder and saw nothing
> but old initrds.
>  however compilation gave no error. why initrd missing then ?
>  or do we really need that missing line ?
>  treat me as if i am a newbie :p
>  cos this is the first time em compiling kernel.
>  satisfactory help will be greatly appreciated :p
>  Regards.
>  Bye

You did not perform all required steps. If you are going to build your
own kernel follow directions carefully.  Did you read the README that
came with the kernel source code?

[Amarnath Singireddy]

hello Mehmet,

try using root=/dev/hda? instead of LABEL and ? is ur root partition.

--Amarnath

On 12/5/05, Kam Leo  wrote:
> On 12/4/05, Mehmet Fatih AKBULUT  wrote:
> > hi all.
> >  recompiled kernel and named it to vmlinuz_mehmet.
> >  when when booting from newly created kernel i got a kernel panic error
> > which says root LABEL cannot be opened or read.
> >  below u can see the grub.conf /*normal and newly created ones*/.
> >
> > title Fedora Core (2.4.22-1.2115.nptlsmp)
> >          root (hd0,1)
> >          kernel /boot/vmlinuz-2.4.22-1.2115.nptlsmp ro root=LABEL=/
> > hdc=ide-scsi rhgb
> >          initrd /boot/initrd-2.4.22-1.2115.nptlsmp.img
> >  title Fedora Core-up (2.4.22-1.2115.nptl)
> >          root (hd0,1)
> >          kernel /boot/vmlinuz_mehmet ro root=LABEL=/ hdc=ide-scsi rhgb
>          ^
>           |
>
> Is there an initrd for the new build or did you just omit posting it?
> > what should i write or change the bold part (starting from ro ...) ?
> >  any suggestion ?
>
> --
> fedora-list mailing list
> [e-mail]
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

[Mehmet Fatih AKBULUT]

hi Amarnath.

ro root=LABEL=/ hdc=ide-scsi rhgb

u mean for the line above :

"ro root=LABEL=/dev/hda1" ???

what about rhbg ?
is this something not necessary ?

[Amarnath Singireddy]

hi,
try this {ro root=/dev/hda1 hdc=ide-scsi rhgb} and u may need to edit
{/etc/fstab} file to replace LABEL. I am not sure this works but you can try
it and undo it.
rhgb is a graphical startup and no need to worry about it.
--amarnath

On 12/5/05, Mehmet Fatih AKBULUT  wrote:
> hi Amarnath.
>
> ro root=LABEL=/ hdc=ide-scsi rhgb
>
> u mean for the line above :
>
> "ro root=LABEL=/dev/hda1" ???
>
> what about rhbg ?
> is this something not necessary ?
>
> --
> fedora-list mailing list
> [e-mail]
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

[Kam Leo]

On 12/4/05, Amarnath Singireddy  wrote:
> hi,
>  try this {ro root=/dev/hda1 hdc=ide-scsi rhgb} and u may need to edit
> {/etc/fstab} file to replace LABEL. I am not sure this works but you can try
> it and undo it.
>  rhgb is a graphical startup and no need to worry about it.

rhgb has caused boot problems for various graphics cards/system
configurations.  If you experience display problems try removing this
parameter.
> --amarnath
>
> On 12/5/05, Mehmet Fatih AKBULUT  wrote:
> > hi Amarnath.
> >
> > ro root=LABEL=/ hdc=ide-scsi rhgb
> >
> > u mean for the line above :
> >
> > "ro root=LABEL=/dev/hda1" ???
> >
> > what about rhbg ?
> > is this something not necessary ?

[Amarnath Singireddy]

Thanks for that correction Kam. I want to know, Will rhgb produce kernel
panic?
--amarnath

On 12/5/05, Kam Leo  wrote:
> On 12/4/05, Amarnath Singireddy  wrote:
> > hi,
> >  try this {ro root=/dev/hda1 hdc=ide-scsi rhgb} and u may need to edit
> > {/etc/fstab} file to replace LABEL. I am not sure this works but you can
>
> try
> > it and undo it.
> >  rhgb is a graphical startup and no need to worry about it.
>
> rhgb has caused boot problems for various graphics cards/system
> configurations.  If you experience display problems try removing this
> parameter.
> > --amarnath
> >
> > On 12/5/05, Mehmet Fatih AKBULUT  wrote:
> > > hi Amarnath.
> > >
> > > ro root=LABEL=/ hdc=ide-scsi rhgb
> > >
> > > u mean for the line above :
> > >
> > > "ro root=LABEL=/dev/hda1" ???
> > >
> > > what about rhbg ?
> > > is this something not necessary ?
>
> --
> fedora-list mailing list
> [e-mail]
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

[Kam Leo]

On 12/4/05, Amarnath Singireddy  wrote:
> Thanks for that correction Kam. I want to know, Will rhgb produce kernel
> panic?

No,  rhgb runs after the kernel loads.
> --amarnath

[snip]

[Mehmet Fatih AKBULUT]

hi all.
what the belows mean ?
this time kernel not compiles ???

arch/i386/kernel/kernel.o(.text.init+0x5268): In function
`acpi_parse_lapic':
: undefined reference to `acpi_table_print_madt_entry'
arch/i386/kernel/kernel.o(.text.init+0x52d8): In function
`acpi_parse_lapic_nmi':
: undefined reference to `acpi_table_print_madt_entry'
arch/i386/kernel/kernel.o(.text.init+0x53cf): In function `acpi_boot_init':
: undefined reference to `acpi_table_init'
arch/i386/kernel/kernel.o(.text.init+0x53e7): In function `acpi_boot_init':
: undefined reference to `acpi_table_parse'
arch/i386/kernel/kernel.o(.text.init+0x5412): In function `acpi_boot_init':
: undefined reference to `acpi_table_parse_madt'
arch/i386/kernel/kernel.o(.text.init+0x5447): In function `acpi_boot_init':
: undefined reference to `acpi_table_parse_madt'
arch/i386/kernel/kernel.o(.text.init+0x5465): In function `acpi_boot_init':
: undefined reference to `acpi_table_parse_madt'
make[1]: *** [kallsyms] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.22-1.2199.nptl'
make: *** [vmlinux] Error 2
[root@localhost linux-2.4]#

help please.

[Amarnath Singireddy]

Mehmet,

It means some of the object files are not linked. This may be caused due to
kernel source bugs or due to improper selection of built-in's while make
menuconfig. Check what others say about this.
--amarnath

On 12/5/05, Mehmet Fatih AKBULUT  wrote:
> hi all.
> what the belows mean ?
> this time kernel not compiles ???
>
> arch/i386/kernel/kernel.o(.text.init+0x5268): In function
> `acpi_parse_lapic':
> : undefined reference to `acpi_table_print_madt_entry'
> arch/i386/kernel/kernel.o(.text.init+0x52d8): In function
> `acpi_parse_lapic_nmi':
> : undefined reference to `acpi_table_print_madt_entry'
> arch/i386/kernel/kernel.o(.text.init+0x53cf): In function
> `acpi_boot_init':
> : undefined reference to `acpi_table_init'
> arch/i386/kernel/kernel.o(.text.init+0x53e7): In function
> `acpi_boot_init':
> : undefined reference to `acpi_table_parse'
> arch/i386/kernel/kernel.o(.text.init+0x5412): In function
> `acpi_boot_init':
> : undefined reference to `acpi_table_parse_madt'
> arch/i386/kernel/kernel.o(.text.init+0x5447): In function
> `acpi_boot_init':
> : undefined reference to `acpi_table_parse_madt'
> arch/i386/kernel/kernel.o(.text.init+0x5465): In function
> `acpi_boot_init':
> : undefined reference to `acpi_table_parse_madt'
> make[1]: *** [kallsyms] Error 1
> make[1]: Leaving directory `/usr/src/linux-2.4.22-1.2199.nptl'
> make: *** [vmlinux] Error 2
> [root@localhost linux-2.4]#
>
> help please.
>
> --
> fedora-list mailing list
> [e-mail]
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

[Kam Leo]

On 12/4/05, Mehmet Fatih AKBULUT  wrote:
> hi all.
>  what the belows mean ?
>  this time kernel not compiles ???
>
> arch/i386/kernel/kernel.o(.text.init+0x5268): In function
> `acpi_parse_lapic':
>  : undefined reference to `acpi_table_print_madt_entry'
>  arch/i386/kernel/kernel.o(.text.init+0x52d8): In function
> `acpi_parse_lapic_nmi':
>  : undefined reference to `acpi_table_print_madt_entry'
>  arch/i386/kernel/kernel.o(.text.init+0x53cf): In function
> `acpi_boot_init':
>  : undefined reference to `acpi_table_init'
>  arch/i386/kernel/kernel.o(.text.init+0x53e7): In function
> `acpi_boot_init':
>  : undefined reference to `acpi_table_parse'
>  arch/i386/kernel/kernel.o(.text.init+0x5412): In function
> `acpi_boot_init':
>  : undefined reference to `acpi_table_parse_madt'
>  arch/i386/kernel/kernel.o(.text.init+0x5447): In function
> `acpi_boot_init':
>  : undefined reference to `acpi_table_parse_madt'
>  arch/i386/kernel/kernel.o(.text.init+0x5465): In function
> `acpi_boot_init':
>  : undefined reference to `acpi_table_parse_madt'
>  make[1]: *** [kallsyms] Error 1
>  make[1]: Leaving directory `/usr/src/linux-2.4.22-1.2199.nptl'
>  make: *** [vmlinux] Error 2
>  [root@localhost linux-2.4]#
>
> help please.

The compiler could not find the referenced code.  Your build
environment is getting mixed up with the installed kernel's source
code.  That is not good.  You should read and follow the
recommendations for creating a build environment in the README that is
included with the source code from kernel.org or the recommendations
from here:
http://crab-lab.zool.ohiou.edu/kevin/kernel-compilation-tutorial-en/steps.ht...

[Mehmet Fatih AKBULUT]

title new kernel
    root (hd0,1)
    kernel /boot/vmlinuz_mfa ro root=LABEL=/dev/hda1 hdc=ide-scsi rhgb

this is the kernel i created. but when rebooting, if i select this one got
the error below :
please append a correct label to root to boot from ???

i did what u said i mean add /dev/hda1 but still now boot.
and getting kernel panics ???

[Kam Leo]

On 12/4/05, Mehmet Fatih AKBULUT  wrote:
> title new kernel
>      root (hd0,1)
>      kernel /boot/vmlinuz_mfa ro root=LABEL=/dev/hda1 hdc=ide-scsi rhgb
>
> this is the kernel i created. but when rebooting, if i select this one got
> the error below :
>  please append a correct label to root to boot from ???
>
> i did what u said i mean add /dev/hda1 but still now boot.
>  and getting kernel panics ???

Where is initrd?  You need to create the ram disk image file and
include it in menu.lst.

[Amarnath Singireddy]

let us know ur disk partition details.

On 12/5/05, Kam Leo  wrote:
> On 12/4/05, Mehmet Fatih AKBULUT  wrote:
> > title new kernel
> >      root (hd0,1)
> >      kernel /boot/vmlinuz_mfa ro root=LABEL=/dev/hda1 hdc=ide-scsi rhgb
> >
> > this is the kernel i created. but when rebooting, if i select this one
>
> got
> > the error below :
> >  please append a correct label to root to boot from ???
> >
> > i did what u said i mean add /dev/hda1 but still now boot.
> >  and getting kernel panics ???
>
> Where is initrd?  You need to create the ram disk image file and
> include it in menu.lst.
>
> --
> fedora-list mailing list
> [e-mail]
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

[Mehmet Fatih AKBULUT]

[root@totti boot]# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hda2              5170696   3439344   1468692  71% /
none                    516208         0    516208   0% /dev/shm
[root@totti boot]#

i think ntfs partition not seen here ?

[Amarnath Singireddy]

less /etc/fstab ?

On 12/5/05, Mehmet Fatih AKBULUT  wrote:
> [root@totti boot]# df
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/hda2              5170696   3439344   1468692  71% /
> none                    516208         0    516208   0% /dev/shm
> [root@totti boot]#
>
> i think ntfs partition not seen here ?
>
> --
> fedora-list mailing list
> [e-mail]
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

[Mehmet Fatih AKBULUT]

LABEL=/                 /                       ext3    defaults        1 1
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /proc                   proc    defaults        0 0
none                    /dev/shm                tmpfs   defaults        0 0
/dev/hda3               swap                    swap    defaults        0 0
/dev/cdrom              /mnt/cdrom              udf,iso9660
noauto,owner,kudzu,r
o 0 0
/dev/cdrom1             /mnt/cdrom1             udf,iso9660
noauto,owner,kudzu,r
o 0 0
/dev/fd0                /mnt/floppy             auto    noauto,owner,kudzu 0
0
/etc/fstab (END)

[Amarnath Singireddy]

try this
root (hd0,1)
kernel /boot/vmlinuz_mfa ro root=/dev/hda2 hdc=ide-scsi rhgb
and
edit /etc/fstab file to replace {LABEL=/} with {/dev/hda2}

On 12/5/05, Mehmet Fatih AKBULUT  wrote:
> LABEL=/                 /                       ext3    defaults        1
> 1
> none                    /dev/pts                devpts  gid=5,mode=620  0
> 0
> none                    /proc                   proc    defaults        0
> 0
> none                    /dev/shm                tmpfs   defaults        0
> 0
> /dev/hda3               swap                    swap    defaults        0
> 0
> /dev/cdrom              /mnt/cdrom              udf,iso9660
> noauto,owner,kudzu,r
> o 0 0
> /dev/cdrom1             /mnt/cdrom1             udf,iso9660
> noauto,owner,kudzu,r
> o 0 0
> /dev/fd0                /mnt/floppy             auto    noauto,owner,kudzu
> 0 0
> /etc/fstab (END)
>
> --
> fedora-list mailing list
> [e-mail]
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

[Kam Leo]

On 12/4/05, Amarnath Singireddy  wrote:
> try this
>  root (hd0,1)
>  kernel /boot/vmlinuz_mfa ro root=/dev/hda2 hdc=ide-scsi rhgb
>  and
>  edit /etc/fstab file to replace {LABEL=/} with {/dev/hda2}

Mehmet,

Do the following files exit?

/boot/vmlinuz-2.4.22-1.2115.nptlsmp
/boot/initrd-2.4.22-1.2115.nptlsmp.img
/boot/vmlinuz_mehmet
/boot/initrd_mehmet

Are you still able to boot with the 2.4.22-1.2115.nptlsmp kernel?

[Mehmet Fatih AKBULUT]

no way :p
no one boots any more :(
this is the second pc i have :(
FC1 is dead :(
and have 1.5 hour to submit homework :(

[Jim Cornette]

Mehmet Fatih AKBULUT wrote:
> no way :p
> no one boots any more :(
> this is the second pc i have :(
> FC1 is dead :(
> and have 1.5 hour to submit homework :(

Probably too late for your homework. Instead of recompiling your kernel 
in order to get ntfs support, there are modules available in rpm 
packages for various kernels. I don't know if FC1 kernel modules are 
still available, but most likely they are available somewhere.

Try this site out for ntfs modules for different releases and kernel 
versions.
http://www.linux-ntfs.org/

Jim

[Kam Leo]

On 12/4/05, Mehmet Fatih AKBULUT  wrote:
> hi Amarnath.
>
> ro root=LABEL=/ hdc=ide-scsi rhgb
>
> u mean for the line above :
>
> "ro root=LABEL=/dev/hda1" ???
>
> what about rhbg ?

rhgb invokes Redhat's graphical boot utility.  Delete it and you will
get a text display.  Also remove "quiet" so you can see the output
from the various processes.
> is this something not necessary ?

[Mehmet Fatih AKBULUT]

ok guys.
i'll chance that line and let u know what i'll get.
hold on :)
and thanks till now.
(but i'm not done yet:p)

[Eduardo Dela Rosa]

Mehmet Fatih AKBULUT wrote:
> hi all.
> recompiled kernel and named it to vmlinuz_mehmet.
> when when booting from newly created kernel i got a kernel panic error 
> which says root LABEL cannot be opened or read.
> below u can see the grub.conf /*normal and newly created ones*/.
>
> title Fedora Core (2.4.22-1.2115.nptlsmp)
>         root (hd0,1)
>         kernel /boot/vmlinuz-2.4.22-1.2115.nptlsmp ro root=LABEL=/ 
> hdc=ide-scsi rhgb
>         initrd /boot/initrd-2.4.22-1.2115.nptlsmp.img
> title Fedora Core-up (2.4.22-1.2115.nptl)
>         root (hd0,1)
>         kernel /boot/vmlinuz_mehmet ro root=LABEL=/ hdc=ide-scsi rhgb
> what should i write or change the bold part (starting from ro ...) ?
> any suggestion ?

Hi,

I've had an experience recompiling my kernel (version 2.6.11) to 
activate NTFS support.
When I rebooted my PC, it's got the same errors as yours (kernel 
panic).  So what I did
was to recompile again, but this time using new version (2.6.14) and 
everything worked
perfectly.

Seems to me that there is much more to do than just make (xconfig), make 
&& make modules
&& make modules_install (and mkinitrd) whenever you re-compile same 
kernel version.

---

EDUARDO A. DELA ROSA

[James Wilkinson]

Mehmet Fatih AKBULUT wrote:
> recompiled kernel and named it to vmlinuz_mehmet.
> when when booting from newly created kernel i got a kernel panic error which
> says root LABEL cannot be opened or read.

No-one's clarified this yet for you...

Mounting partitions by label is supposed to be a Good Thing (by Red Hat)
because if you move your hard drive, or if the name of the device
changes (e.g. /dev/hda1 -> /dev/sda1), then the system will still find
the right partition and load properly.

(It's considered a Bad Thing by some because if you ever end up with two
partitions with the same label on the same drive, the system will get
confused).

Partitions can be mounted with the mount command or by the kernel. Only
the mount command knows how to mount by label: the kernel doesn't. This
means that if you want to mount / by label, you need an initrd, which
contains (a version of) the mount command.

An initrd image can be created with the mkinitrd command.

Hope this helps,

James.

[Mehmet Fatih AKBULUT]

hi James.
thanks for ur answers :)
but its too late for homework. [however no limit to learn new things and
broaden horizon about linux environment and architecture :p]
actullay learnt how to do by help of mailing lists and google .
but wish to learn hours ago :))))
now i can compile and change the label according to my disk partion.
and get no error.
progress is a slow process.
missed a few extra credits but not big deal.
second homework will probably be harder than the first one.
hope will do before deadline :)

Regards.
Bye