[gentoo-user] kernel panic on manually built kernel

[gentoo-user] kernel panic on manually built kernel

[dhk]

I've always used the genkernel, but now am trying to make a manual one.
 I think the kernel is alright since all the default setting seemed
reasonable and the build was easy enough.  However, when I boot to it I
get a kernel panic and it complains about the root device /dev/hda3. So
I think the problem has to do with my parameters or syntax in grub.conf.
 Below are three grub menu options.  The first two have the problem and
the third is the genkernel that works fine.  Is there something wrong
with the way the first two are?  Thanks.

# This is a Manually built kernel with default settings.  kernel panic
title Gentoo Linux x86 2.6.34-r12
root (hd0,0)
kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3

# This is a Manually built kernel with default settings.  kernel panic
title Gentoo Linux x86 2.6.34-r12
root (hd0,0)
kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
splash=verbose video=vesafb:mtrr,ywrap udev
# From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85

# This a genkernel and works
title Gentoo Linux x86 2.6.34-r6
root (hd0,0)
kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
video=vesafb:mtrr,ywrap udev
initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6

--dhk

Re: [gentoo-user] kernel panic on manually built kernel

[Dale]

dhk wrote:
> I've always used the genkernel, but now am trying to make a manual one.
>   I think the kernel is alright since all the default setting seemed
> reasonable and the build was easy enough.  However, when I boot to it I
> get a kernel panic and it complains about the root device /dev/hda3. So
> I think the problem has to do with my parameters or syntax in grub.conf.
>   Below are three grub menu options.  The first two have the problem and
> the third is the genkernel that works fine.  Is there something wrong
> with the way the first two are?  Thanks.
>
> # This is a Manually built kernel with default settings.  kernel panic
> title Gentoo Linux x86 2.6.34-r12
> root (hd0,0)
> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
>
> # This is a Manually built kernel with default settings.  kernel panic
> title Gentoo Linux x86 2.6.34-r12
> root (hd0,0)
> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
> splash=verbose video=vesafb:mtrr,ywrap udev
> # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
>
> # This a genkernel and works
> title Gentoo Linux x86 2.6.34-r6
> root (hd0,0)
> kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
> ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
> video=vesafb:mtrr,ywrap udev
> initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
>
> --dhk
>
>
>    

When I get a kernel panic, it's usually because I'm pointing to the 
wrong partition or I forgot to include the file system that the root 
partition uses.  Since the one you made and the genkernel match up, I 
would check to make sure you included the correct file system and it is 
BUILT IN not a module.

Hope that helps or someone else comes up with another idea.

Dale

:-)  :-)

Re: [gentoo-user] kernel panic on manually built kernel

[Alan McKinnon]

Apparently, though unproven, at 18:34 on Thursday 04 November 2010, dhk did 
opine thusly:

> I've always used the genkernel, but now am trying to make a manual one.
>  I think the kernel is alright since all the default setting seemed
> reasonable and the build was easy enough.  However, when I boot to it I
> get a kernel panic and it complains about the root device /dev/hda3. So
> I think the problem has to do with my parameters or syntax in grub.conf.
>  Below are three grub menu options.  The first two have the problem and
> the third is the genkernel that works fine.  Is there something wrong
> with the way the first two are?  Thanks.

Why did you think it a good idea to NOT post the *actual* error? 

Your grub entries are correct.

I'll bet money that you built one or more of your chipset drivers, libata, or 
root filesystem driver as a module.

These must not be modules, they must be built-in (otherwise you need an 
initrd)



> 
> # This is a Manually built kernel with default settings.  kernel panic
> title Gentoo Linux x86 2.6.34-r12
> root (hd0,0)
> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
> 
> # This is a Manually built kernel with default settings.  kernel panic
> title Gentoo Linux x86 2.6.34-r12
> root (hd0,0)
> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
> splash=verbose video=vesafb:mtrr,ywrap udev
> # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
> 
> # This a genkernel and works
> title Gentoo Linux x86 2.6.34-r6
> root (hd0,0)
> kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
> ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
> video=vesafb:mtrr,ywrap udev
> initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
> 
> --dhk

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] kernel panic on manually built kernel

[dhk]

On 11/04/2010 12:52 PM, Alan McKinnon wrote:
> Apparently, though unproven, at 18:34 on Thursday 04 November 2010, dhk did 
> opine thusly:
> 
>> I've always used the genkernel, but now am trying to make a manual one.
>>  I think the kernel is alright since all the default setting seemed
>> reasonable and the build was easy enough.  However, when I boot to it I
>> get a kernel panic and it complains about the root device /dev/hda3. So
>> I think the problem has to do with my parameters or syntax in grub.conf.
>>  Below are three grub menu options.  The first two have the problem and
>> the third is the genkernel that works fine.  Is there something wrong
>> with the way the first two are?  Thanks.
> 
> Why did you think it a good idea to NOT post the *actual* error? 
> 
> Your grub entries are correct.
> 
> I'll bet money that you built one or more of your chipset drivers, libata, or 
> root filesystem driver as a module.
> 
> These must not be modules, they must be built-in (otherwise you need an 
> initrd)
> 
> 
> 
>>
>> # This is a Manually built kernel with default settings.  kernel panic
>> title Gentoo Linux x86 2.6.34-r12
>> root (hd0,0)
>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
>>
>> # This is a Manually built kernel with default settings.  kernel panic
>> title Gentoo Linux x86 2.6.34-r12
>> root (hd0,0)
>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
>> splash=verbose video=vesafb:mtrr,ywrap udev
>> # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
>>
>> # This a genkernel and works
>> title Gentoo Linux x86 2.6.34-r6
>> root (hd0,0)
>> kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
>> ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
>> video=vesafb:mtrr,ywrap udev
>> initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
>>
>> --dhk
> 

Thanks all, I check those suggestions and get back to you.

The reason I didn't include the exact error is that I can't capture it.
 I'd have to write it on paper and then reboot to the working kernel.
By then it doesn't seem to be in any of the logs.  I'll see what I can
do about that.

Thanks again.

--dhk

Re: [gentoo-user] kernel panic on manually built kernel

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 472 bytes --]

On Thu, 04 Nov 2010 13:00:21 -0400, dhk wrote:

> The reason I didn't include the exact error is that I can't capture it.
>  I'd have to write it on paper and then reboot to the working kernel.

Which is a lot less work than trying to fix the problem by guesswork.


-- 
Neil Bothwick

Velilind's Laws of Experimentation:
1. If reproducibility may be a problem, conduct the test only once.
2. If a straight line fit is required, obtain only two data points.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] kernel panic on manually built kernel

[dhk]

On 11/04/2010 01:08 PM, Neil Bothwick wrote:
> On Thu, 04 Nov 2010 13:00:21 -0400, dhk wrote:
> 
>> The reason I didn't include the exact error is that I can't capture it.
>>  I'd have to write it on paper and then reboot to the working kernel.
> 
> Which is a lot less work than trying to fix the problem by guesswork.
> 
> 

I have /boot as ext2 and the rest ext3 with lvm2.

$ df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hda3              8262068    712028   7130344  10% /
udev                     10240       336      9904   4% /dev
/dev/mapper/vg-usr    15481840  12867912   1827496  88% /usr
/dev/mapper/vg-home   51606140  42781428   6203272  88% /home
/dev/mapper/vg-opt     5160576   2635064   2263368  54% /opt
/dev/mapper/vg-var    15481840   2387500  12307908  17% /var
/dev/mapper/vg-tmp     2064208     68708   1890644   4% /tmp
shm                     512572         0    512572   0% /dev/shm

The ext2 wasn't compiled in, so I compiled it in and rebooted.  I got
the same error.

"kernel panic - not syncing : VFS: unable to mount root FS on
unknown-block (2,0)"

This is what I had.
< > Second extended fs support                                   │ │
  │ │    <*> Ext3 journalling file system support
  │ │
  │ │    [ ]   Default to 'data=ordered' in ext3
  │ │
  │ │    [*]   Ext3 extended attributes
  │ │
  │ │    [*]     Ext3 POSIX Access Control Lists
  │ │
  │ │    [*]     Ext3 Security Labels

This is what I added.
<*> Second extended fs support                                   │ │
  │ │    [ ]   Ext2 extended attributes (NEW)
  │ │
  │ │    [ ]   Ext2 execute in place support (NEW)
  │ │
  │ │    <*> Ext3 journalling file system support
  │ │
  │ │    [ ]   Default to 'data=ordered' in ext3
  │ │
  │ │    [*]   Ext3 extended attributes
  │ │
  │ │    [*]     Ext3 POSIX Access Control Lists
  │ │
  │ │    [*]     Ext3 Security Labels
  │ │

Thanks,

--dhk

Re: [gentoo-user] kernel panic on manually built kernel

[covici]

Dale <rdalek1967@gmail.com> wrote:

> dhk wrote:
> > I've always used the genkernel, but now am trying to make a manual one.
> >   I think the kernel is alright since all the default setting seemed
> > reasonable and the build was easy enough.  However, when I boot to it I
> > get a kernel panic and it complains about the root device /dev/hda3. So
> > I think the problem has to do with my parameters or syntax in grub.conf.
> >   Below are three grub menu options.  The first two have the problem and
> > the third is the genkernel that works fine.  Is there something wrong
> > with the way the first two are?  Thanks.
> >
> > # This is a Manually built kernel with default settings.  kernel panic
> > title Gentoo Linux x86 2.6.34-r12
> > root (hd0,0)
> > kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
> >
> > # This is a Manually built kernel with default settings.  kernel panic
> > title Gentoo Linux x86 2.6.34-r12
> > root (hd0,0)
> > kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
> > splash=verbose video=vesafb:mtrr,ywrap udev
> > # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
> >
> > # This a genkernel and works
> > title Gentoo Linux x86 2.6.34-r6
> > root (hd0,0)
> > kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
> > ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
> > video=vesafb:mtrr,ywrap udev
> > initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
> >
> > --dhk
> >
> >
> >    
> 
> When I get a kernel panic, it's usually because I'm pointing to the
> wrong partition or I forgot to include the file system that the root
> partition uses.  Since the one you made and the genkernel match up, I
> would check to make sure you included the correct file system and it
> is BUILT IN not a module.
> 
> Hope that helps or someone else comes up with another idea.
He does not have the ramdisk or initrd in his manual ones.  That would
do it right there.  Be sure to generate the ramdisk as well.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] kernel panic on manually built kernel

[dhk]

On 11/04/2010 02:12 PM, covici@ccs.covici.com wrote:
> Dale <rdalek1967@gmail.com> wrote:
> 
>> dhk wrote:
>>> I've always used the genkernel, but now am trying to make a manual one.
>>>   I think the kernel is alright since all the default setting seemed
>>> reasonable and the build was easy enough.  However, when I boot to it I
>>> get a kernel panic and it complains about the root device /dev/hda3. So
>>> I think the problem has to do with my parameters or syntax in grub.conf.
>>>   Below are three grub menu options.  The first two have the problem and
>>> the third is the genkernel that works fine.  Is there something wrong
>>> with the way the first two are?  Thanks.
>>>
>>> # This is a Manually built kernel with default settings.  kernel panic
>>> title Gentoo Linux x86 2.6.34-r12
>>> root (hd0,0)
>>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
>>>
>>> # This is a Manually built kernel with default settings.  kernel panic
>>> title Gentoo Linux x86 2.6.34-r12
>>> root (hd0,0)
>>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
>>> splash=verbose video=vesafb:mtrr,ywrap udev
>>> # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
>>>
>>> # This a genkernel and works
>>> title Gentoo Linux x86 2.6.34-r6
>>> root (hd0,0)
>>> kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
>>> ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
>>> video=vesafb:mtrr,ywrap udev
>>> initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
>>>
>>> --dhk
>>>
>>>
>>>    
>>
>> When I get a kernel panic, it's usually because I'm pointing to the
>> wrong partition or I forgot to include the file system that the root
>> partition uses.  Since the one you made and the genkernel match up, I
>> would check to make sure you included the correct file system and it
>> is BUILT IN not a module.
>>
>> Hope that helps or someone else comes up with another idea.
> He does not have the ramdisk or initrd in his manual ones.  That would
> do it right there.  Be sure to generate the ramdisk as well.
> 

The documentation doesn't say to use ramdisk or initrd for a manual
kernel, only the genkernel.

Re: [gentoo-user] kernel panic on manually built kernel

[Yohan Pereira]

On Thursday 04 November 2010 11:49:07 pm dhk wrote:

stupid queston but did you select the appropriate sata drivers ?

i ran into a similar problem just about an hr back becuase i forgot to include 
those .

-- 
- Yohan Pereira.

Re: [gentoo-user] kernel panic on manually built kernel

[covici]

dhk <dhkuhl@optonline.net> wrote:

> On 11/04/2010 02:12 PM, covici@ccs.covici.com wrote:
> > Dale <rdalek1967@gmail.com> wrote:
> > 
> >> dhk wrote:
> >>> I've always used the genkernel, but now am trying to make a manual one.
> >>>   I think the kernel is alright since all the default setting seemed
> >>> reasonable and the build was easy enough.  However, when I boot to it I
> >>> get a kernel panic and it complains about the root device /dev/hda3. So
> >>> I think the problem has to do with my parameters or syntax in grub.conf.
> >>>   Below are three grub menu options.  The first two have the problem and
> >>> the third is the genkernel that works fine.  Is there something wrong
> >>> with the way the first two are?  Thanks.
> >>>
> >>> # This is a Manually built kernel with default settings.  kernel panic
> >>> title Gentoo Linux x86 2.6.34-r12
> >>> root (hd0,0)
> >>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
> >>>
> >>> # This is a Manually built kernel with default settings.  kernel panic
> >>> title Gentoo Linux x86 2.6.34-r12
> >>> root (hd0,0)
> >>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
> >>> splash=verbose video=vesafb:mtrr,ywrap udev
> >>> # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
> >>>
> >>> # This a genkernel and works
> >>> title Gentoo Linux x86 2.6.34-r6
> >>> root (hd0,0)
> >>> kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
> >>> ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
> >>> video=vesafb:mtrr,ywrap udev
> >>> initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
> >>>
> >>> --dhk
> >>>
> >>>
> >>>    
> >>
> >> When I get a kernel panic, it's usually because I'm pointing to the
> >> wrong partition or I forgot to include the file system that the root
> >> partition uses.  Since the one you made and the genkernel match up, I
> >> would check to make sure you included the correct file system and it
> >> is BUILT IN not a module.
> >>
> >> Hope that helps or someone else comes up with another idea.
> > He does not have the ramdisk or initrd in his manual ones.  That would
> > do it right there.  Be sure to generate the ramdisk as well.
> > 
> 
> The documentation doesn't say to use ramdisk or initrd for a manual
> kernel, only the genkernel.
But if the configs are the same, you need to do the same things, so
generate your ramdisk and see what happens.  I do this all the time,
just use genkernel to generate the ramdisk and do all other things
manually.  I just make oldconfig when I upgrade and do make Bzimage and
make modules and make modules_install and copy the kernel to the right
place and update my lilo.conf.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] kernel panic on manually built kernel

[Alan McKinnon]

Apparently, though unproven, at 19:00 on Thursday 04 November 2010, dhk did 
opine thusly:

> On 11/04/2010 12:52 PM, Alan McKinnon wrote:
> > Apparently, though unproven, at 18:34 on Thursday 04 November 2010, dhk
> > did
> > 
> > opine thusly:
> >> I've always used the genkernel, but now am trying to make a manual one.
> >> 
> >>  I think the kernel is alright since all the default setting seemed
> >> 
> >> reasonable and the build was easy enough.  However, when I boot to it I
> >> get a kernel panic and it complains about the root device /dev/hda3. So
> >> I think the problem has to do with my parameters or syntax in grub.conf.
> >> 
> >>  Below are three grub menu options.  The first two have the problem and
> >> 
> >> the third is the genkernel that works fine.  Is there something wrong
> >> with the way the first two are?  Thanks.
> > 
> > Why did you think it a good idea to NOT post the *actual* error?
> > 
> > Your grub entries are correct.
> > 
> > I'll bet money that you built one or more of your chipset drivers,
> > libata, or root filesystem driver as a module.
> > 
> > These must not be modules, they must be built-in (otherwise you need an
> > initrd)
> > 
> >> # This is a Manually built kernel with default settings.  kernel panic
> >> title Gentoo Linux x86 2.6.34-r12
> >> root (hd0,0)
> >> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
> >> 
> >> # This is a Manually built kernel with default settings.  kernel panic
> >> title Gentoo Linux x86 2.6.34-r12
> >> root (hd0,0)
> >> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
> >> splash=verbose video=vesafb:mtrr,ywrap udev
> >> # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
> >> 
> >> # This a genkernel and works
> >> title Gentoo Linux x86 2.6.34-r6
> >> root (hd0,0)
> >> kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
> >> ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
> >> video=vesafb:mtrr,ywrap udev
> >> initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
> >> 
> >> --dhk
> 
> Thanks all, I check those suggestions and get back to you.
> 
> The reason I didn't include the exact error is that I can't capture it.
>  I'd have to write it on paper and then reboot to the working kernel.
> By then it doesn't seem to be in any of the logs.  I'll see what I can
> do about that.

The usual error is something like

panic: can't find root filesystem (dev/hda3)

or similar. It's so common when building your own kernel the first time, that 
if you post the gist of the error (doesn't have to be 100% exact), you'll get 
10 replies in an error from folk who've all made the same mistake themselves. 
Some of us more than once...

It's always missing drivers or (more usually) drivers built as modules.


-- 

alan dot mckinnon at gmail dot com

Re: [gentoo-user] kernel panic on manually built kernel

[Alan McKinnon]

Apparently, though unproven, at 19:36 on Thursday 04 November 2010, dhk did 
opine thusly:

> On 11/04/2010 01:08 PM, Neil Bothwick wrote:
> > On Thu, 04 Nov 2010 13:00:21 -0400, dhk wrote:
> >> The reason I didn't include the exact error is that I can't capture it.
> >> 
> >>  I'd have to write it on paper and then reboot to the working kernel.
> > 
> > Which is a lot less work than trying to fix the problem by guesswork.
> 
> I have /boot as ext2 and the rest ext3 with lvm2.
> 
> $ df -k
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/hda3              8262068    712028   7130344  10% /
> udev                     10240       336      9904   4% /dev
> /dev/mapper/vg-usr    15481840  12867912   1827496  88% /usr
> /dev/mapper/vg-home   51606140  42781428   6203272  88% /home
> /dev/mapper/vg-opt     5160576   2635064   2263368  54% /opt
> /dev/mapper/vg-var    15481840   2387500  12307908  17% /var
> /dev/mapper/vg-tmp     2064208     68708   1890644   4% /tmp
> shm                     512572         0    512572   0% /dev/shm
> 
> The ext2 wasn't compiled in, so I compiled it in and rebooted.  I got
> the same error.
> 
> "kernel panic - not syncing : VFS: unable to mount root FS on
> unknown-block (2,0)"
> 
> This is what I had.
> < > Second extended fs support                                   │ │
>   │ │    <*> Ext3 journalling file system support
>   │ │
>   │ │    [ ]   Default to 'data=ordered' in ext3
>   │ │
>   │ │    [*]   Ext3 extended attributes
>   │ │
>   │ │    [*]     Ext3 POSIX Access Control Lists
>   │ │
>   │ │    [*]     Ext3 Security Labels
> 
> This is what I added.
> <*> Second extended fs support                                   │ │
>   │ │    [ ]   Ext2 extended attributes (NEW)
>   │ │
>   │ │    [ ]   Ext2 execute in place support (NEW)
>   │ │
>   │ │    <*> Ext3 journalling file system support
>   │ │
>   │ │    [ ]   Default to 'data=ordered' in ext3
>   │ │
>   │ │    [*]   Ext3 extended attributes
>   │ │
>   │ │    [*]     Ext3 POSIX Access Control Lists
>   │ │
>   │ │    [*]     Ext3 Security Labels
>   │ │
> 
> Thanks,
> 
> --dhk


Is your / partition in or out of the lvm?


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] kernel panic on manually built kernel

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 454 bytes --]

On Thu, 04 Nov 2010 13:36:25 -0400, dhk wrote:

> The ext2 wasn't compiled in, so I compiled it in and rebooted.  I got
> the same error.
> 
> "kernel panic - not syncing : VFS: unable to mount root FS on
> unknown-block (2,0)"

It's saying unknown block, not unknown fs. I suspect you haven't compiled
in the drivers for your hard disk controller.


-- 
Neil Bothwick

Philosophical error: Demonstrate the existence of a key to continue

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] kernel panic on manually built kernel

[Stroller]

On 4/11/2010, at 5:36pm, dhk wrote:
> ...
> This is what I had.
> < > Second extended fs support                                   │ │
>  │ │    <*> Ext3 journalling file system support
>  │ │
>  │ │    [ ]   Default to 'data=ordered' in ext3
>  │ │
>  │ │    [*]   Ext3 extended attributes
>  │ │
>  │ │    [*]     Ext3 POSIX Access Control Lists
>  │ │
>  │ │    [*]     Ext3 Security Labels
> 
> This is what I added.
> <*> Second extended fs support                                   │ │
>  │ │    [ ]   Ext2 extended attributes (NEW)
>  │ │
>  │ │    [ ]   Ext2 execute in place support (NEW)
>  │ │
>  │ │    <*> Ext3 journalling file system support
>  │ │
>  │ │    [ ]   Default to 'data=ordered' in ext3
>  │ │
>  │ │    [*]   Ext3 extended attributes
>  │ │
>  │ │    [*]     Ext3 POSIX Access Control Lists
>  │ │
>  │ │    [*]     Ext3 Security Labels
>  │ │

The kernel configuration is not terribly readable when posted in this format. Might I suggest posting the whole .config file as an attachment, perhaps gzipped? You can transfer it from the non-booting machine to the PC on which you have internet access by using scp from the LiveCD.

Stroller.

Re: [gentoo-user] kernel panic on manually built kernel

[dhk]

On 11/04/2010 03:25 PM, Alan McKinnon wrote:
> Apparently, though unproven, at 19:36 on Thursday 04 November 2010, dhk did 
> opine thusly:
> 
>> On 11/04/2010 01:08 PM, Neil Bothwick wrote:
>>> On Thu, 04 Nov 2010 13:00:21 -0400, dhk wrote:
>>>> The reason I didn't include the exact error is that I can't capture it.
>>>>
>>>>  I'd have to write it on paper and then reboot to the working kernel.
>>>
>>> Which is a lot less work than trying to fix the problem by guesswork.
>>
>> I have /boot as ext2 and the rest ext3 with lvm2.
>>
>> $ df -k
>> Filesystem           1K-blocks      Used Available Use% Mounted on
>> /dev/hda3              8262068    712028   7130344  10% /
>> udev                     10240       336      9904   4% /dev
>> /dev/mapper/vg-usr    15481840  12867912   1827496  88% /usr
>> /dev/mapper/vg-home   51606140  42781428   6203272  88% /home
>> /dev/mapper/vg-opt     5160576   2635064   2263368  54% /opt
>> /dev/mapper/vg-var    15481840   2387500  12307908  17% /var
>> /dev/mapper/vg-tmp     2064208     68708   1890644   4% /tmp
>> shm                     512572         0    512572   0% /dev/shm
>>
>> The ext2 wasn't compiled in, so I compiled it in and rebooted.  I got
>> the same error.
>>
>> "kernel panic - not syncing : VFS: unable to mount root FS on
>> unknown-block (2,0)"
>>
>> This is what I had.
>> < > Second extended fs support                                   │ │
>>   │ │    <*> Ext3 journalling file system support
>>   │ │
>>   │ │    [ ]   Default to 'data=ordered' in ext3
>>   │ │
>>   │ │    [*]   Ext3 extended attributes
>>   │ │
>>   │ │    [*]     Ext3 POSIX Access Control Lists
>>   │ │
>>   │ │    [*]     Ext3 Security Labels
>>
>> This is what I added.
>> <*> Second extended fs support                                   │ │
>>   │ │    [ ]   Ext2 extended attributes (NEW)
>>   │ │
>>   │ │    [ ]   Ext2 execute in place support (NEW)
>>   │ │
>>   │ │    <*> Ext3 journalling file system support
>>   │ │
>>   │ │    [ ]   Default to 'data=ordered' in ext3
>>   │ │
>>   │ │    [*]   Ext3 extended attributes
>>   │ │
>>   │ │    [*]     Ext3 POSIX Access Control Lists
>>   │ │
>>   │ │    [*]     Ext3 Security Labels
>>   │ │
>>
>> Thanks,
>>
>> --dhk
> 
> 
> Is your / partition in or out of the lvm?
> 
> 

The / is out of lvm2 and is ext3, /boot is ext2.

Re: [gentoo-user] kernel panic on manually built kernel

[Alan McKinnon]

Apparently, though unproven, at 11:29 on Friday 05 November 2010, dhk did 
opine thusly:

 
> > Is your / partition in or out of the lvm?
> 
> The / is out of lvm2 and is ext3, /boot is ext2.

Ok, that's the easiest way. Seeing inside lvm at boot-time is no fun.

But I think Niel spotted your real problem already, you do not have chipset 
support built into the kernel.


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] kernel panic on manually built kernel

[dhk]

On 11/04/2010 03:51 PM, Neil Bothwick wrote:
> On Thu, 04 Nov 2010 13:36:25 -0400, dhk wrote:
> 
>> The ext2 wasn't compiled in, so I compiled it in and rebooted.  I got
>> the same error.
>>
>> "kernel panic - not syncing : VFS: unable to mount root FS on
>> unknown-block (2,0)"
> 
> It's saying unknown block, not unknown fs. I suspect you haven't compiled
> in the drivers for your hard disk controller.
> 
> 

All my hard disks are sata except the main one with the os on it that is
ide.  Is a fairly new disk, may be a year old, but should the following
driver be compiled in?
[ ]   Very old hard disk (MFM/RLL/IDE) driver

I went back to ide a few years ago because I had problems with sata.
First, the system would never boot with more than one sata drive
connected.  There's something call Staggered Spin-up Detection which
load balances the power going to the disks.  The bios would error saying
that there weren't any hard disks, when really they weren't powered up
by time the bios finished checking them.  Second, I broke a couple of
motherboard sata connectors.  Apparently the wire connection to the
connector is tighter than the connector's connection to the motherboard,
they pulled right off the board.

Re: [gentoo-user] kernel panic on manually built kernel

[Alan McKinnon]

Apparently, though unproven, at 11:47 on Friday 05 November 2010, dhk did 
opine thusly:

> On 11/04/2010 03:51 PM, Neil Bothwick wrote:
> > On Thu, 04 Nov 2010 13:36:25 -0400, dhk wrote:
> >> The ext2 wasn't compiled in, so I compiled it in and rebooted.  I got
> >> the same error.
> >> 
> >> "kernel panic - not syncing : VFS: unable to mount root FS on
> >> unknown-block (2,0)"
> > 
> > It's saying unknown block, not unknown fs. I suspect you haven't compiled
> > in the drivers for your hard disk controller.
> 
> All my hard disks are sata except the main one with the os on it that is
> ide.  Is a fairly new disk, may be a year old, but should the following
> driver be compiled in?
> [ ]   Very old hard disk (MFM/RLL/IDE) driver

No. Those are the ancient drives that shipped with original PCs way way way 
back in the 80s. Remember those monsters that were never bigger than 32M, were 
about 4 inches tall and had gigantic cables that were sensitive to be sneezed 
around? Those were MFM drives.

These days libata does IDE as well. Think of it as a sort of universal wrapper 
around all drives you can buy today and gives a consistent interface. You do 
still need the driver for the IDE chipset which slots in one level lower.


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] kernel panic on manually built kernel

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]

On Fri, 05 Nov 2010 05:47:42 -0400, dhk wrote:

> > It's saying unknown block, not unknown fs. I suspect you haven't
> > compiled in the drivers for your hard disk controller.
> > 
> >   
> 
> All my hard disks are sata except the main one with the os on it that is
> ide.  Is a fairly new disk, may be a year old, but should the following
> driver be compiled in?
> [ ]   Very old hard disk (MFM/RLL/IDE) driver

It's unlikely, more likely is that you don't have support for your
controller chipset built in. Boot fro the genkernel kernel and run lspci
-k to see which module it uses for the controller, then compile that into
your kernel.

> Second, I broke a couple of
> motherboard sata connectors.  Apparently the wire connection to the
> connector is tighter than the connector's connection to the motherboard,
> they pulled right off the board.

That's happened to me a few times too. Fortunately, they push back on
almost as easily as they pull off.


-- 
Neil Bothwick

WYTYSYDG - What you thought you saw, you didn't get.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] kernel panic on manually built kernel

[dhk]

On 11/05/2010 06:33 AM, Neil Bothwick wrote:
> On Fri, 05 Nov 2010 05:47:42 -0400, dhk wrote:
> 
>>> It's saying unknown block, not unknown fs. I suspect you haven't
>>> compiled in the drivers for your hard disk controller.
>>>
>>>   
>>
>> All my hard disks are sata except the main one with the os on it that is
>> ide.  Is a fairly new disk, may be a year old, but should the following
>> driver be compiled in?
>> [ ]   Very old hard disk (MFM/RLL/IDE) driver
> 
> It's unlikely, more likely is that you don't have support for your
> controller chipset built in. Boot fro the genkernel kernel and run lspci
> -k to see which module it uses for the controller, then compile that into
> your kernel.
> 
>> Second, I broke a couple of
>> motherboard sata connectors.  Apparently the wire connection to the
>> connector is tighter than the connector's connection to the motherboard,
>> they pulled right off the board.
> 
> That's happened to me a few times too. Fortunately, they push back on
> almost as easily as they pull off.
> 
> 
This is what I have.

$ lspci -k
00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1)
	Subsystem: ASUSTeK Computer Inc. K8N-E
	Kernel driver in use: agpgart-amd64
00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)
	Subsystem: ASUSTeK Computer Inc. K8N-E
00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management
(rev a1)
	Subsystem: ASUSTeK Computer Inc. K8N-E
00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
	Subsystem: ASUSTeK Computer Inc. K8N-E
	Kernel driver in use: ohci_hcd
	Kernel modules: ohci-hcd
00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
	Subsystem: ASUSTeK Computer Inc. K8N-E
	Kernel driver in use: ohci_hcd
	Kernel modules: ohci-hcd
00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0
Controller (rev a2)
	Subsystem: ASUSTeK Computer Inc. K8N-E
	Kernel driver in use: ehci_hcd
	Kernel modules: ehci-hcd
00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2)
	Subsystem: ASUSTeK Computer Inc. K8N-E
	Kernel driver in use: forcedeth
	Kernel modules: forcedeth
00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb
AC'97 Audio Controller (rev a1)
	Subsystem: ASUSTeK Computer Inc. K8N-E
	Kernel driver in use: Intel ICH
	Kernel modules: snd-intel8x0

I think this may be the missing one(s).  I can't find it in the
list, but the AMD64/PATA is selected to be compiled in.
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller
(v2.5) (rev a2)
	Subsystem: ASUSTeK Computer Inc. K8N-E
	Kernel driver in use: AMD_IDE
	Kernel modules: pata_acpi, ata_generic, pata_amd
00:0a.0 IDE interface: nVidia Corporation nForce3 Serial ATA Controller
(rev a2)
	Subsystem: ASUSTeK Computer Inc. K8N-E
	Kernel driver in use: sata_nv
	Kernel modules: sata_nv, pata_acpi, ata_generic
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI
Bridge (rev a2)
00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge
(rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV36 [GeForce FX
5700LE] (rev a1)
	Kernel driver in use: nvidia
	Kernel modules: nvidia
02:07.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 61)
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd
02:07.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 61)
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd
02:07.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63)
	Subsystem: VIA Technologies, Inc. USB 2.0
	Kernel driver in use: ehci_hcd
	Kernel modules: ehci-hcd
02:07.3 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE
1394 OHCI Link Layer Controller (rev 46)
	Subsystem: VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link
Layer Controller
	Kernel driver in use: ohci1394
	Kernel modules: ohci1394

--dhk

Re: [gentoo-user] kernel panic on manually built kernel

[Volker Armin Hemmann]

On Thursday 04 November 2010, dhk wrote:
> I've always used the genkernel, but now am trying to make a manual one.
>  I think the kernel is alright since all the default setting seemed
> reasonable and the build was easy enough.  However, when I boot to it I
> get a kernel panic and it complains about the root device /dev/hda3. So
> I think the problem has to do with my parameters or syntax in grub.conf.
>  Below are three grub menu options.  The first two have the problem and
> the third is the genkernel that works fine.  Is there something wrong
> with the way the first two are?  Thanks.
> 
> # This is a Manually built kernel with default settings.  kernel panic
> title Gentoo Linux x86 2.6.34-r12
> root (hd0,0)
> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
> 
> # This is a Manually built kernel with default settings.  kernel panic
> title Gentoo Linux x86 2.6.34-r12
> root (hd0,0)
> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
> splash=verbose video=vesafb:mtrr,ywrap udev
> # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
> 
> # This a genkernel and works
> title Gentoo Linux x86 2.6.34-r6
> root (hd0,0)
> kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
> ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
> video=vesafb:mtrr,ywrap udev
> initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
> 
> --dhk

grub must point to sda3 not hda3

[gentoo-user] Re: kernel panic on manually built kernel

[walt]

On 11/05/2010 04:36 AM, dhk wrote:

> I think this may be the missing one(s).  I can't find it in the
> list, but the AMD64/PATA is selected to be compiled in.

> vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
> 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller
> (v2.5) (rev a2)
> 	Subsystem: ASUSTeK Computer Inc. K8N-E
> 	Kernel driver in use: AMD_IDE
> 	Kernel modules: pata_acpi, ata_generic, pata_amd
> 00:0a.0 IDE interface: nVidia Corporation nForce3 Serial ATA Controller
> (rev a2)
> 	Subsystem: ASUSTeK Computer Inc. K8N-E
> 	Kernel driver in use: sata_nv
> 	Kernel modules: sata_nv, pata_acpi, ata_generic
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The sata_nv driver is driver 'in use' and it's compiled as a module.
Try changing that to compiled-in.

Re: [gentoo-user] kernel panic on manually built kernel

[Coert Waagmeester]

Volker Armin Hemmann wrote:
> On Thursday 04 November 2010, dhk wrote:
>> I've always used the genkernel, but now am trying to make a manual one.
>>  I think the kernel is alright since all the default setting seemed
>> reasonable and the build was easy enough.  However, when I boot to it I
>> get a kernel panic and it complains about the root device /dev/hda3. So
>> I think the problem has to do with my parameters or syntax in grub.conf.
>>  Below are three grub menu options.  The first two have the problem and
>> the third is the genkernel that works fine.  Is there something wrong
>> with the way the first two are?  Thanks.
>>
>> # This is a Manually built kernel with default settings.  kernel panic
>> title Gentoo Linux x86 2.6.34-r12
>> root (hd0,0)
>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
>>
>> # This is a Manually built kernel with default settings.  kernel panic
>> title Gentoo Linux x86 2.6.34-r12
>> root (hd0,0)
>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
>> splash=verbose video=vesafb:mtrr,ywrap udev
>> # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
>>
>> # This a genkernel and works
>> title Gentoo Linux x86 2.6.34-r6
>> root (hd0,0)
>> kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
>> ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
>> video=vesafb:mtrr,ywrap udev
>> initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
>>
>> --dhk
> 
> grub must point to sda3 not hda3
> 
> 

Yes, I had a similar problem.
The device names are different on my machine between genkernel and my 
own kernel.
Make sure to change that in your /etc/fstab as well.

Dont know if this is always the case though.

Regards,
Coert Waagmeester

Re: [gentoo-user] kernel panic on manually built kernel

[dhk]

On 11/08/2010 05:28 AM, Coert Waagmeester wrote:
> Volker Armin Hemmann wrote:
>> On Thursday 04 November 2010, dhk wrote:
>>> I've always used the genkernel, but now am trying to make a manual one.
>>>  I think the kernel is alright since all the default setting seemed
>>> reasonable and the build was easy enough.  However, when I boot to it I
>>> get a kernel panic and it complains about the root device /dev/hda3. So
>>> I think the problem has to do with my parameters or syntax in grub.conf.
>>>  Below are three grub menu options.  The first two have the problem and
>>> the third is the genkernel that works fine.  Is there something wrong
>>> with the way the first two are?  Thanks.
>>>
>>> # This is a Manually built kernel with default settings.  kernel panic
>>> title Gentoo Linux x86 2.6.34-r12
>>> root (hd0,0)
>>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
>>>
>>> # This is a Manually built kernel with default settings.  kernel panic
>>> title Gentoo Linux x86 2.6.34-r12
>>> root (hd0,0)
>>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
>>> splash=verbose video=vesafb:mtrr,ywrap udev
>>> # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
>>>
>>> # This a genkernel and works
>>> title Gentoo Linux x86 2.6.34-r6
>>> root (hd0,0)
>>> kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
>>> ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
>>> video=vesafb:mtrr,ywrap udev
>>> initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
>>>
>>> --dhk
>>
>> grub must point to sda3 not hda3
>>
>>
> 
> Yes, I had a similar problem.
> The device names are different on my machine between genkernel and my
> own kernel.
> Make sure to change that in your /etc/fstab as well.
> 
> Dont know if this is always the case though.
> 
> Regards,
> Coert Waagmeester
> 
> 

I'm booting to an IDE hard disk.  Are you say the device name should
change from /dev/hda3 to /dev/sda3?  If I change it in /etc/fstab and it
doesn't work, I'll have problems, I'll probably have to boot to the livecd.

Thanks,

--dhk

Re: [gentoo-user] kernel panic on manually built kernel

[Coert Waagmeester]

dhk wrote:
> On 11/08/2010 05:28 AM, Coert Waagmeester wrote:
>> Volker Armin Hemmann wrote:
>>> On Thursday 04 November 2010, dhk wrote:
>>>> I've always used the genkernel, but now am trying to make a manual one.
>>>>  I think the kernel is alright since all the default setting seemed
>>>> reasonable and the build was easy enough.  However, when I boot to it I
>>>> get a kernel panic and it complains about the root device /dev/hda3. So
>>>> I think the problem has to do with my parameters or syntax in grub.conf.
>>>>  Below are three grub menu options.  The first two have the problem and
>>>> the third is the genkernel that works fine.  Is there something wrong
>>>> with the way the first two are?  Thanks.
>>>>
>>>> # This is a Manually built kernel with default settings.  kernel panic
>>>> title Gentoo Linux x86 2.6.34-r12
>>>> root (hd0,0)
>>>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
>>>>
>>>> # This is a Manually built kernel with default settings.  kernel panic
>>>> title Gentoo Linux x86 2.6.34-r12
>>>> root (hd0,0)
>>>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
>>>> splash=verbose video=vesafb:mtrr,ywrap udev
>>>> # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
>>>>
>>>> # This a genkernel and works
>>>> title Gentoo Linux x86 2.6.34-r6
>>>> root (hd0,0)
>>>> kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
>>>> ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
>>>> video=vesafb:mtrr,ywrap udev
>>>> initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
>>>>
>>>> --dhk
>>> grub must point to sda3 not hda3
>>>
>>>
>> Yes, I had a similar problem.
>> The device names are different on my machine between genkernel and my
>> own kernel.
>> Make sure to change that in your /etc/fstab as well.
>>
>> Dont know if this is always the case though.
>>
>> Regards,
>> Coert Waagmeester
>>
>>
> 
> I'm booting to an IDE hard disk.  Are you say the device name should
> change from /dev/hda3 to /dev/sda3?  If I change it in /etc/fstab and it
> doesn't work, I'll have problems, I'll probably have to boot to the livecd.
> 
> Thanks,
> 
> --dhk
> 
> 

It has indeed happened to me with an IDE PATA disk.
Try first only to change only your grub config.
Then if you see that the kernel boots fine, you can change /etc/fstab.

If you want you can even use LABELs in fstab.

give your ext{2,3} partitions labels with e2label

and change the device node eg /dev/hda1 in fstab to LABEL=yournewlabel


Regards,
Coert Waagmeester

Re: [gentoo-user] kernel panic on manually built kernel

[Volker Armin Hemmann]

On Monday 08 November 2010, dhk wrote:
> On 11/08/2010 05:28 AM, Coert Waagmeester wrote:
> > Volker Armin Hemmann wrote:
> >> On Thursday 04 November 2010, dhk wrote:
> >>> I've always used the genkernel, but now am trying to make a manual one.
> >>> 
> >>>  I think the kernel is alright since all the default setting seemed
> >>> 
> >>> reasonable and the build was easy enough.  However, when I boot to it I
> >>> get a kernel panic and it complains about the root device /dev/hda3. So
> >>> I think the problem has to do with my parameters or syntax in
> >>> grub.conf.
> >>> 
> >>>  Below are three grub menu options.  The first two have the problem and
> >>> 
> >>> the third is the genkernel that works fine.  Is there something wrong
> >>> with the way the first two are?  Thanks.
> >>> 
> >>> # This is a Manually built kernel with default settings.  kernel panic
> >>> title Gentoo Linux x86 2.6.34-r12
> >>> root (hd0,0)
> >>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
> >>> 
> >>> # This is a Manually built kernel with default settings.  kernel panic
> >>> title Gentoo Linux x86 2.6.34-r12
> >>> root (hd0,0)
> >>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
> >>> splash=verbose video=vesafb:mtrr,ywrap udev
> >>> # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
> >>> 
> >>> # This a genkernel and works
> >>> title Gentoo Linux x86 2.6.34-r6
> >>> root (hd0,0)
> >>> kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
> >>> ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
> >>> video=vesafb:mtrr,ywrap udev
> >>> initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
> >>> 
> >>> --dhk
> >> 
> >> grub must point to sda3 not hda3
> > 
> > Yes, I had a similar problem.
> > The device names are different on my machine between genkernel and my
> > own kernel.
> > Make sure to change that in your /etc/fstab as well.
> > 
> > Dont know if this is always the case though.
> > 
> > Regards,
> > Coert Waagmeester
> 
> I'm booting to an IDE hard disk.  Are you say the device name should
> change from /dev/hda3 to /dev/sda3?  If I change it in /etc/fstab and it
> doesn't work, I'll have problems, I'll probably have to boot to the livecd.
> 
> Thanks,
> 
> --dhk

if you are using libata, you have sdX device names.

Re: [gentoo-user] kernel panic on manually built kernel

[Dale]

Coert Waagmeester wrote:
>
>
> It has indeed happened to me with an IDE PATA disk.
> Try first only to change only your grub config.
> Then if you see that the kernel boots fine, you can change /etc/fstab.
>
> If you want you can even use LABELs in fstab.
>
> give your ext{2,3} partitions labels with e2label
>
> and change the device node eg /dev/hda1 in fstab to LABEL=yournewlabel
>
>
> Regards,
> Coert Waagmeester
>
>

I agree with this 100%.  I switched mine to the new PATA drivers and I 
couldn't figure out what the drive order was.  I used LABELS and it has 
worked ever since.  The funny thing is, I have a card to hook a SATA 
drive up to and it puts it first instead of the drives that are hooked 
directly to the mobo.  I wasn't expecting that and that was why I could 
not get mine to boot with the PATA drives.  Bad thing is, the CD/DVD's I 
have still use the old IDE drivers so I couldn't even test it by booting 
that.

I have not been able to get grub to see the LABELS yet but I'm going to 
post fstab so that you have a example that is known to work and not from 
a guide:

/dev/disk/by-label/boot        /boot        ext2        noatime        1 2
/dev/disk/by-label/root        /        reiserfs    defaults    0 1
/dev/disk/by-label/swap        none        swap        sw        0 0
/dev/disk/by-label/portage    /usr/portage    ext3        defaults    0 1
/dev/disk/by-label/home        /home        reiserfs    defaults    1 1
/dev/disk/by-label/data        /data        reiserfs    defaults    0 1

Now someone post their grub.conf for us both.  I just can't get mine to 
work with grub at all.  I can't even use tab to find the drives in the 
boot menu.

Hope that helps.

Dale

:-)  :-)

Re: [gentoo-user] kernel panic on manually built kernel

[Stroller]

On 8/11/2010, at 5:56pm, Dale wrote:
> ...
> I have not been able to get grub to see the LABELS yet but I'm going to post fstab so that you have a example that is known to work and not from a guide:
> 
> /dev/disk/by-label/boot        /boot        ext2        noatime        1 2
> /dev/disk/by-label/root        /        reiserfs    defaults    0 1
> /dev/disk/by-label/swap        none        swap        sw        0 0
> /dev/disk/by-label/portage    /usr/portage    ext3        defaults    0 1
> /dev/disk/by-label/home        /home        reiserfs    defaults    1 1
> /dev/disk/by-label/data        /data        reiserfs    defaults    0 1

I'm not paying enough attention to know whether your above fastab works or not, but /dev/disk/by-label/* seems a relatively ugly way of doing things. I'm pretty sure it's not intended that you use that format, and I have no idea whether it's supposed to work that way.

All the guides say to use the word "LABEL". That's not a variable or anything - it's the literal word you're supposed to use.

I have no idea why a guide should be considered unreliable, but the below is not fabricated - it is from an actual working system:

$ grep -ve ^# /etc/fstab

LABEL=boot              /boot           ext2            noauto,noatime  1 2
LABEL=/                 /               ext4            noatime         0 1
LABEL=swap              none            swap            sw              0 0
/dev/cdrom              /mnt/cdrom      auto            noauto,ro,users 0 0

LABEL=space             /mnt/space      ext4            noatime         0 3

shm             /dev/shm        tmpfs           nodev,nosuid,noexec     0 0
$ 

To me this seems cleaner than your format, and it's certainly fewer characters!

Stroller.

Re: [gentoo-user] kernel panic on manually built kernel

[Dale]

Stroller wrote:
> On 8/11/2010, at 5:56pm, Dale wrote:
>    
>> ...
>> I have not been able to get grub to see the LABELS yet but I'm going to post fstab so that you have a example that is known to work and not from a guide:
>>
>> /dev/disk/by-label/boot        /boot        ext2        noatime        1 2
>> /dev/disk/by-label/root        /        reiserfs    defaults    0 1
>> /dev/disk/by-label/swap        none        swap        sw        0 0
>> /dev/disk/by-label/portage    /usr/portage    ext3        defaults    0 1
>> /dev/disk/by-label/home        /home        reiserfs    defaults    1 1
>> /dev/disk/by-label/data        /data        reiserfs    defaults    0 1
>>      
> I'm not paying enough attention to know whether your above fastab works or not, but /dev/disk/by-label/* seems a relatively ugly way of doing things. I'm pretty sure it's not intended that you use that format, and I have no idea whether it's supposed to work that way.
>
> All the guides say to use the word "LABEL". That's not a variable or anything - it's the literal word you're supposed to use.
>
> I have no idea why a guide should be considered unreliable, but the below is not fabricated - it is from an actual working system:
>
> $ grep -ve ^# /etc/fstab
>
> LABEL=boot              /boot           ext2            noauto,noatime  1 2
> LABEL=/                 /               ext4            noatime         0 1
> LABEL=swap              none            swap            sw              0 0
> /dev/cdrom              /mnt/cdrom      auto            noauto,ro,users 0 0
>
> LABEL=space             /mnt/space      ext4            noatime         0 3
>
> shm             /dev/shm        tmpfs           nodev,nosuid,noexec     0 0
> $
>
> To me this seems cleaner than your format, and it's certainly fewer characters!
>
> Stroller.
>
>    

Well, it does work since it booted as recent as last night when I 
updated my kernel.  I found that somewhere and just copied that to 
mine.  It may be the long way but it does work.  I may edit it and try 
it your way but since mine works and I don't move things to much, not 
sure it really matters.

I sometimes like to get things from a working system, such as what you 
posted that you use, because sometimes what is in a guide somewhere may 
not apply to what I am using or even my OS.  May be some subtle 
difference that causes me grief.  Since you use Gentoo, yours is a good 
example to go by.  Should have had that a few months ago when I was 
changing mine over.  ;-)   It would have saved me some typing as you 
pointed out.  lol

Wouldn't happen to have LABELS in your grub.conf file would you?

Dale

:-)  :-)

Re: [gentoo-user] kernel panic on manually built kernel

[Stroller]

On 8/11/2010, at 9:34pm, Dale wrote:
> ...
> Wouldn't happen to have LABELS in your grub.conf file would you?

Nope. 

I believe this requires an initramfs - see the February 2009 thread, `Using  "root=LABEL=xxxx" in grub.conf` for more details of that. I seem to rather have an aversion to initramfses.

Stroller.

Re: [gentoo-user] kernel panic on manually built kernel

[Dale]

Stroller wrote:
> On 8/11/2010, at 9:34pm, Dale wrote:
>    
>> ...
>> Wouldn't happen to have LABELS in your grub.conf file would you?
>>      
> Nope.
>
> I believe this requires an initramfs - see the February 2009 thread, `Using  "root=LABEL=xxxx" in grub.conf` for more details of that. I seem to rather have an aversion to initramfses.
>
> Stroller.
>
>    

Yea, I don't like those either.  I think grub2 supports it but I'm not 
sure.  I think that is what I read but it may be just on a todo list or 
something.  Maybe one day.

Dale

:-)  :-)

Re: [gentoo-user] kernel panic on manually built kernel

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 671 bytes --]

On Mon, 08 Nov 2010 15:34:08 -0600, Dale wrote:

> Well, it does work since it booted as recent as last night when I 
> updated my kernel.  I found that somewhere and just copied that to 
> mine.  It may be the long way but it does work.  I may edit it and try 
> it your way but since mine works and I don't move things to much, not 
> sure it really matters.

Labels are stored in the filesystem, so LABEL= should always work.

/dev/disk/by-label/ is created by udev rules, so it won't work if
anything goes wrong with your udev rules or if you have to boot with
init=/bin/sh.


-- 
Neil Bothwick

Tagline stealing is the sincerest form of flattery.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] kernel panic on manually built kernel

[Dale]

Neil Bothwick wrote:
> On Mon, 08 Nov 2010 15:34:08 -0600, Dale wrote:
>
>    
>> Well, it does work since it booted as recent as last night when I
>> updated my kernel.  I found that somewhere and just copied that to
>> mine.  It may be the long way but it does work.  I may edit it and try
>> it your way but since mine works and I don't move things to much, not
>> sure it really matters.
>>      
> Labels are stored in the filesystem, so LABEL= should always work.
>
> /dev/disk/by-label/ is created by udev rules, so it won't work if
> anything goes wrong with your udev rules or if you have to boot with
> init=/bin/sh.
>
>    

Guess I better change that soon then.  While udev has been working 
pretty good here lately, we never know what may happen tomorrow.

Thanks for the heads up.

Dale

:-)  :-)

Re: [gentoo-user] kernel panic on manually built kernel

[Stroller]

On 8/11/2010, at 10:39pm, Neil Bothwick wrote:

> On Mon, 08 Nov 2010 15:34:08 -0600, Dale wrote:
> 
>> Well, it does work since it booted as recent as last night when I 
>> updated my kernel.  I found that somewhere and just copied that to 
>> mine.  It may be the long way but it does work.  I may edit it and try 
>> it your way but since mine works and I don't move things to much, not 
>> sure it really matters.
> 
> Labels are stored in the filesystem, so LABEL= should always work.
> 
> /dev/disk/by-label/ is created by udev rules, so it won't work if
> anything goes wrong with your udev rules or if you have to boot with
> init=/bin/sh.

Thanks! I approximately figured this when I made my original posting, but don't really feel confident enough about /dev and udev rules to express it properly. That's why I just said "I'm not sure the configuration is even supposed to work".

Stroller.