Re: [gentoo-amd64] initrd

Re: [gentoo-amd64] initrd

[Dmitri Pogosyan]

> On Saturday 29 October 2005 07:16, DR GM SEDDON wrote:
> > my grub.conf:
> > ' default 0
> > timeout     5
> > splashimage=(hd0.0)/grub/splash.xpm.gz
> >
> > title=linux-2.6.13
> > root (hd0.0)
> > kernel /genkernel--x86_64-2.6.13-gentoo-r3 root=/dev/ram0  init=/linuxrc
> > ramdisk-8193 real_root=/dev/hda3 udev
> > initrd /initrd'
> >
> I have the sameconfig and it works ok exept the name of /initrd I 
> have /initramfs-genkernel-x86_64-2.6.13-gentoo-r3. Maybe that is the problem?
> 

Yep, initrd should point to the real initrd or initramfs file in /boot  !

Aso, why is this double dash in /genkernel--x86_64 ? Is it not a mistyping by
any chance ?






--
Dmitri Pogosyan            Department of Physics
Associate Professor        University of Alberta
tel 1-780-492-2150         412 Avadh Bhatia Physics Labs
fax 1-780-492-0714         Edmonton, AB, T6G 2J1, CANADA


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Dmitri Pogosyan]

It is not needed, I believe, with new kernels. Remnants from the earlier 
days, in my case. I am still mostly on 2.6.11 kernel with devfs, actually, 
and am used to combinations udev+nodevfs, devfs+noudev (which had quite 
magical interactions between themselves, BTW) 
 
 
> On Sat, 29 Oct 2005 14:21:52 +0100 
> DR GM SEDDON <gavin.m.seddon@manchester.ac.uk> wrote: 
>  
> > Dmitri Pogosyan wrote: 
> >  
> > >Not really, you can use initramfs in place of initrd. I have in 
> > >grub.conf  
> > >  
> > >title=Gentoo Linux 2.6.13-r3 UDEV  
> > >root (hd0,0)  
> > >kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 ramdisk=16384 
> > >init=/linuxrc real_root=/dev/sda2 vga=3847 udev  
> > >initrd /initramfs-2.6.13-gentoo-r3  
>  
> I've notice that some ppl are putting udev on the kernel line.  I was 
> under the impression that this was not needed to get udev working? 
>  
> -- 
> bruce 
> --  
> gentoo-amd64@gentoo.org mailing list 
 
 
 
 
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Dmitri Pogosyan]

> I've been using gentoo for 3 yrs now and using a grub.conf exactly as follows 
> for all that time.  It has <never> failed to work.  I did not create 
> the /boot dir with mkdir, that was done when I cp'd my bzImage 
> from /usr/src/linux/arch/x86_64/boot/bzImage to /boot, and I did it that way 
> because that's how the docs said to do it.
> 
> tbill@Shooter ~ $ cat /boot/grub/grub.conf
> default 0
> timeout 10
> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> 
> title=Gentoo (linux kernel 2.6.11-gentoo-r10)
> root (hd0,0)
> kernel (hd0,0)/boot/bzImage root=/dev/sda1
> 
> If you, when you installed gentoo in the first place, placed /boot in its own 
> partition, then anything you copy to that partition is going to start with 
> "/boot...".  How else are you going to tell the kernel to copy something to 
> the boot partition when /boot is all you've mounted there?  If you, as root, 
> tell the system to mount the partition where you've installed grub.conf, how 
> else do you specify it except as "mount /boot".  I don't mean to belabor the 
> point, but....
> 
> So tell grub to look on "(hd0,0)/boot/bzImage" for the kernel to boot, 
> only,since you don't have a bzImage but a genkernel, change it accordingly: 
> (hd0,0)/boot/genkernel-*.  I assure you that this <does not> "stop your 
> system from booting fully."
> 
> Also, since you're getting error code 15, what you have in /etc/fstab is 
> completely immaterial.  Grub can't even find your kernel, and grub's interest 
> stops at finding the kernel, so take care of grub's errors first, then worry 
> about whether your fstab is properly set up.
> 

Actually, that reminds me that a year ago on amd64 architecture the compiled
grub did not work for me (it did compile but fail to boot) and I had
to use grub-static-0.93, which worked fine.  I looked now and see that
I still use this version of grub on all my amd64 machines. 



--
Dmitri Pogosyan            Department of Physics
Associate Professor        University of Alberta
tel 1-780-492-2150         412 Avadh Bhatia Physics Labs
fax 1-780-492-0714         Edmonton, AB, T6G 2J1, CANADA


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[William Tetrault]

I too have been on the amd64 platform since early last year, and am still 
using grub-static, although I know that grub now compiles fine for this 
platform (at least, that is what I've heard - I'm still using grub-static).  
But whether one uses grub or grub-static, the installed files are the same, 
and grub works the same regardless of which is chosen.  My grub.conf has not 
changed from when I was using Athlon XP's (although it's no longer called 
grub.lst).

On Sunday 30 October 2005 12:07 pm, Dmitri Pogosyan wrote:
> Actually, that reminds me that a year ago on amd64 architecture the
> compiled grub did not work for me (it did compile but fail to boot) and I
> had to use grub-static-0.93, which worked fine.  I looked now and see that
> I still use this version of grub on all my amd64 machines.
>
>
>
> --
> Dmitri Pogosyan            Department of Physics
> Associate Professor        University of Alberta
> tel 1-780-492-2150         412 Avadh Bhatia Physics Labs
> fax 1-780-492-0714         Edmonton, AB, T6G 2J1, CANADA
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Nuitari]

I finally switched my only grub system to lilo yesterday.

On Sun, 30 Oct 2005, William Tetrault wrote:

> Date: Sun, 30 Oct 2005 13:24:30 -0600
> From: William Tetrault <xcourse97@charter.net>
> Reply-To: gentoo-amd64@lists.gentoo.org
> To: gentoo-amd64@lists.gentoo.org
> Subject: Re: [gentoo-amd64] initrd
> 
> I too have been on the amd64 platform since early last year, and am still
> using grub-static, although I know that grub now compiles fine for this
> platform (at least, that is what I've heard - I'm still using grub-static).
> But whether one uses grub or grub-static, the installed files are the same,
> and grub works the same regardless of which is chosen.  My grub.conf has not
> changed from when I was using Athlon XP's (although it's no longer called
> grub.lst).
>
> On Sunday 30 October 2005 12:07 pm, Dmitri Pogosyan wrote:
>> Actually, that reminds me that a year ago on amd64 architecture the
>> compiled grub did not work for me (it did compile but fail to boot) and I
>> had to use grub-static-0.93, which worked fine.  I looked now and see that
>> I still use this version of grub on all my amd64 machines.
>>
>>
>>
>> --
>> Dmitri Pogosyan            Department of Physics
>> Associate Professor        University of Alberta
>> tel 1-780-492-2150         412 Avadh Bhatia Physics Labs
>> fax 1-780-492-0714         Edmonton, AB, T6G 2J1, CANADA
>
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[DR GM SEDDON]

Hi, if I cannot get grub towork.  How do I go-about making the change to 
lilo?
Thanks
Gavin.


Nuitari wrote:

> I finally switched my only grub system to lilo yesterday.
>
> On Sun, 30 Oct 2005, William Tetrault wrote:
>
>> Date: Sun, 30 Oct 2005 13:24:30 -0600
>> From: William Tetrault <xcourse97@charter.net>
>> Reply-To: gentoo-amd64@lists.gentoo.org
>> To: gentoo-amd64@lists.gentoo.org
>> Subject: Re: [gentoo-amd64] initrd
>>
>> I too have been on the amd64 platform since early last year, and am 
>> still
>> using grub-static, although I know that grub now compiles fine for this
>> platform (at least, that is what I've heard - I'm still using 
>> grub-static).
>> But whether one uses grub or grub-static, the installed files are the 
>> same,
>> and grub works the same regardless of which is chosen.  My grub.conf 
>> has not
>> changed from when I was using Athlon XP's (although it's no longer 
>> called
>> grub.lst).
>>
>> On Sunday 30 October 2005 12:07 pm, Dmitri Pogosyan wrote:
>>
>>> Actually, that reminds me that a year ago on amd64 architecture the
>>> compiled grub did not work for me (it did compile but fail to boot) 
>>> and I
>>> had to use grub-static-0.93, which worked fine.  I looked now and 
>>> see that
>>> I still use this version of grub on all my amd64 machines.
>>>
>>>
>>>
>>> -- 
>>> Dmitri Pogosyan            Department of Physics
>>> Associate Professor        University of Alberta
>>> tel 1-780-492-2150         412 Avadh Bhatia Physics Labs
>>> fax 1-780-492-0714         Edmonton, AB, T6G 2J1, CANADA
>>
>>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[DR GM SEDDON]

I have tried installing lilo, it says it is masked.   So I emerged 
grub-static and found no differenc however I just remembered; do I need 
to do install-grub-static?  Finally, the system will not let me 
'--unmerge grub'.  How do I change grub?
Gavin.



Nuitari wrote:

> I finally switched my only grub system to lilo yesterday.
>
> On Sun, 30 Oct 2005, William Tetrault wrote:
>
>> Date: Sun, 30 Oct 2005 13:24:30 -0600
>> From: William Tetrault <xcourse97@charter.net>
>> Reply-To: gentoo-amd64@lists.gentoo.org
>> To: gentoo-amd64@lists.gentoo.org
>> Subject: Re: [gentoo-amd64] initrd
>>
>> I too have been on the amd64 platform since early last year, and am 
>> still
>> using grub-static, although I know that grub now compiles fine for this
>> platform (at least, that is what I've heard - I'm still using 
>> grub-static).
>> But whether one uses grub or grub-static, the installed files are the 
>> same,
>> and grub works the same regardless of which is chosen.  My grub.conf 
>> has not
>> changed from when I was using Athlon XP's (although it's no longer 
>> called
>> grub.lst).
>>
>> On Sunday 30 October 2005 12:07 pm, Dmitri Pogosyan wrote:
>>
>>> Actually, that reminds me that a year ago on amd64 architecture the
>>> compiled grub did not work for me (it did compile but fail to boot) 
>>> and I
>>> had to use grub-static-0.93, which worked fine.  I looked now and 
>>> see that
>>> I still use this version of grub on all my amd64 machines.
>>>
>>>
>>>
>>> -- 
>>> Dmitri Pogosyan            Department of Physics
>>> Associate Professor        University of Alberta
>>> tel 1-780-492-2150         412 Avadh Bhatia Physics Labs
>>> fax 1-780-492-0714         Edmonton, AB, T6G 2J1, CANADA
>>
>>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Drake Donahue]

   Grub really does work. The problem you are having is that grub can't
find your kernel.

   May I suggest:

    Boot the gentoo install cd:

    At the prompt  -  livecd gentoo #  -  execute the following commands:

mount /dev/hda1 /mnt/gentoo/boot
cd /mnt/gentoo/boot
ls -l
ls kernel* initramfs*

    The output of  "mount /dev/hda1 /mnt/gentoo" will tell you about the
filesystem on the boot partition and should contain no surprises.
    The output of  "ls -l" is the boot file and directory structure that 
grub will
see if  "root (hd0,0)" is in grub.conf.
    The output of  "ls kernel* initramfs*" is the kernel name and the 
initramfs
name that need to appear in grub.conf.
    If a 'No such file or directory' error appears, the kernel and/or the 
initramfs
is not located in /mnt/gentoo/boot and thus is not in (hd0,0)/ as far as 
grub is
concerned. In this case look for a boot -->'something' symbolic link that 
points
 to 'something' as the kernel location. Most likely a boot directory will 
appear
in the "ls -l" output and you should look there for kernel and initramfs. If
mislocated, I think you should move them to /mnt/gentoo/boot and rerun
" ls kernel* initramfs* ".

    I believe that the " ls kernel* initramfs* " output you see will be
"kernel-2.6.13-gentoo-r3   initramfs-genkernel-amd64-2.6.13-gentoo-r3".

    In that case, I believe grub.conf should read:

default 0
timeout 5
splashimage=(hd0,0)/grub/splash.xpm.gz
title=Gentoo Linux 2.6.13
root (hd0,0)
kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 init=/linuxrc ramdisk=8192 
real_root=/dev/hda3 udev
initrd /initramfs-genkernel-amd64-2.6.13-gentoo-r3

    If  " ls kernel* initramfs* " produced other results, then "the other 
kernel name" must be
substituted exactly for 'kernel-2.6.13-gentoo-r3' above and "the other 
initramfs name" for
'initramfs-genkernel-amd64-2.6.13-gentoo-r3' above respectively. Don't lose 
the initial
slashes in the process.

    If you try this and it does not help, posting the results of the 
commands and the grub.conf
may get more help from the smarter than I multitude. 

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[DR GM SEDDON]

Yes, I had missing the initial 'kernel-' from its definition in 
grub.conf.  It is down to me writing it on a pad with other stuff, I was 
ignoring the kernel word.  Extremely xorry.

Now it boots but asksme to
'specifya device to boot' it boots when I enter 'dev/hda3'.  It is 
specified in 'grub.conf' and 'fstab'.  Any ideas?

Also, I get 'dhcpd:required function  'interface _is_up' but networking 
isn't working.  And, I get 'netmount not started'.  Are these issues 
related.  Can you help?
Regards,
Gavin.

Drake Donahue wrote:

>   Grub really does work. The problem you are having is that grub can't
> find your kernel.
>
>   May I suggest:
>
>    Boot the gentoo install cd:
>
>    At the prompt  -  livecd gentoo #  -  execute the following commands:
>
> mount /dev/hda1 /mnt/gentoo/boot
> cd /mnt/gentoo/boot
> ls -l
> ls kernel* initramfs*
>
>    The output of  "mount /dev/hda1 /mnt/gentoo" will tell you about the
> filesystem on the boot partition and should contain no surprises.
>    The output of  "ls -l" is the boot file and directory structure 
> that grub will
> see if  "root (hd0,0)" is in grub.conf.
>    The output of  "ls kernel* initramfs*" is the kernel name and the 
> initramfs
> name that need to appear in grub.conf.
>    If a 'No such file or directory' error appears, the kernel and/or 
> the initramfs
> is not located in /mnt/gentoo/boot and thus is not in (hd0,0)/ as far 
> as grub is
> concerned. In this case look for a boot -->'something' symbolic link 
> that points
> to 'something' as the kernel location. Most likely a boot directory 
> will appear
> in the "ls -l" output and you should look there for kernel and 
> initramfs. If
> mislocated, I think you should move them to /mnt/gentoo/boot and rerun
> " ls kernel* initramfs* ".
>
>    I believe that the " ls kernel* initramfs* " output you see will be
> "kernel-2.6.13-gentoo-r3   initramfs-genkernel-amd64-2.6.13-gentoo-r3".
>
>    In that case, I believe grub.conf should read:
>
> default 0
> timeout 5
> splashimage=(hd0,0)/grub/splash.xpm.gz
> title=Gentoo Linux 2.6.13
> root (hd0,0)
> kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 init=/linuxrc 
> ramdisk=8192 real_root=/dev/hda3 udev
> initrd /initramfs-genkernel-amd64-2.6.13-gentoo-r3
>









>    If  " ls kernel* initramfs* " produced other results, then "the 
> other kernel name" must be
> substituted exactly for 'kernel-2.6.13-gentoo-r3' above and "the other 
> initramfs name" for
> 'initramfs-genkernel-amd64-2.6.13-gentoo-r3' above respectively. Don't 
> lose the initial
> slashes in the process.
>
>    If you try this and it does not help, posting the results of the 
> commands and the grub.conf
> may get more help from the smarter than I multitude.


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Drake Donahue]

    The entry:
"kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 init=/linuxrc ramdisk=8192 
real_root=/dev/hda3 udev"
in grub.conf should be on one line -- sorry --
I see that it was split into two lines at the space between 8192 and 
real_root when it came back to me through the mail list handler and my mail 
client. Probably happened to you also. As " real_root=/dev/hda3 udev " are 
kernel arguments they need to be on the same line as "kernel".
This should solve the first problem.
Make the change above to grub.conf .
Reboot.

    I think the second problem is not related to the first. There is 
probably a problem with the network settings. Page 40 to 46 of the amd64 
gentoo handbook are a good start on the networking problem. Short summary 
follows. My best guess is that adding dhcpcd to rc is necessary and not 
documented.

    May I suggest (presuming your intent was to have the network mount 
automatically and you connect via ethernet):

Run the command:

dir /sbin/dh*

If the response is "/sbin/dhcpcd" then the dhcp client demon is installed. 
If "No such file or directory" error occurs, dhcpcd needs to be emerged. (Or 
you wanted to use some other dhcp client.)

Run the command: (modified if you wanted to use and have emerged some other 
dhcp client.)

rc-update add dhcpcd default

nano -w /etc/conf.d/hostname
        and
(Set the HOSTNAME variable to your hostname)
HOSTNAME="yourcomputername"

nano -w /etc/conf.d/domainname

(Set the DNSDOMAIN variable to your domain name)
DNSDOMAIN="yourhomenetworkname"rc-update add domainname defaultnano -w 
/etc/conf.d/net
 (should be blank or all lines commented)

rc-update add net.eth0 default

/etc/init.d/net.eth0 start


----- Original Message ----- 
From: "DR GM SEDDON" <gavin.m.seddon@manchester.ac.uk>

<snip>

> Now it boots but asksme to
> 'specifya device to boot' it boots when I enter 'dev/hda3'.  It is 
> specified in 'grub.conf' and 'fstab'.  Any ideas?
>
> Also, I get 'dhcpd:required function  'interface _is_up' but networking 
> isn't working.  And, I get 'netmount not started'.  Are these issues 
> related.  Can you help?
> Regards,
> Gavin.

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Drake Donahue]

 oops, another mangle occurred.



 The entry:


"kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 init=/linuxrc ramdisk=8192 
real_root=/dev/hda3 udev"


 in grub.conf should be on one line -- sorry --
 I see that it was split into two lines at the space between 8192 and
 real_root when it came back to me through the mail list handler and my mail
 client. Probably happened to you also. As " real_root=/dev/hda3 udev " are
 kernel arguments they need to be on the same line as "kernel".
 This should solve the first problem.
 Make the change above to grub.conf .
 Reboot.

    I think the second problem is not related to the first. There is
 probably a problem with the network settings. Page 40 to 46 of the amd64
 gentoo handbook are a good start on the networking problem. Short summary
 follows. My best guess is that adding dhcpcd to rc is necessary and not
 documented.

    May I suggest (presuming your intent was to have the network mount
 automatically and you connect via ethernet):

 Run the command:

 dir /sbin/dh*

 If the response is "/sbin/dhcpcd" then the dhcp client demon is installed.
 If "No such file or directory" error occurs, dhcpcd needs to be emerged. 
(Or
 you wanted to use some other dhcp client.)

 Run the command: (modified if you wanted to use and have emerged some other
 dhcp client.)

 rc-update add dhcpcd default

 nano -w /etc/conf.d/hostname
        and
 (Set the HOSTNAME variable to your hostname)
 HOSTNAME="yourcomputername"

 nano -w /etc/conf.d/domainname

 (Set the DNSDOMAIN variable to your domain name)
 DNSDOMAIN="yourhomenetworkname"

rc-update add domainname default

nano -w  /etc/conf.d/net
 (should be blank or all lines commented)

 rc-update add net.eth0 default

 /etc/init.d/net.eth0 start


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[DR GM SEDDON]

Hi,
Yes, this worked for booting.

rc-update add net.rth0 default gave
'already installed in runlevel default'
and
/etc/init.d/net.eth0 start
'dhcpd:missing required function interface_is_up'

The final message is the same as vI receive when booting.
Gavin.


Drake Donahue wrote:

>    The entry:
> "kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 init=/linuxrc 
> ramdisk=8192 real_root=/dev/hda3 udev"
> in grub.conf should be on one line -- sorry --
> I see that it was split into two lines at the space between 8192 and 
> real_root when it came back to me through the mail list handler and my 
> mail client. Probably happened to you also. As " real_root=/dev/hda3 
> udev " are kernel arguments they need to be on the same line as "kernel".
> This should solve the first problem.
> Make the change above to grub.conf .
> Reboot.
>
>    I think the second problem is not related to the first. There is 
> probably a problem with the network settings. Page 40 to 46 of the 
> amd64 gentoo handbook are a good start on the networking problem. 
> Short summary follows. My best guess is that adding dhcpcd to rc is 
> necessary and not documented.
>
>    May I suggest (presuming your intent was to have the network mount 
> automatically and you connect via ethernet):
>
> Run the command:
>
> dir /sbin/dh*
>
> If the response is "/sbin/dhcpcd" then the dhcp client demon is 
> installed. If "No such file or directory" error occurs, dhcpcd needs 
> to be emerged. (Or you wanted to use some other dhcp client.)
>
> Run the command: (modified if you wanted to use and have emerged some 
> other dhcp client.)
>
> rc-update add dhcpcd default
>
> nano -w /etc/conf.d/hostname
>        and
> (Set the HOSTNAME variable to your hostname)
> HOSTNAME="yourcomputername"
>
> nano -w /etc/conf.d/domainname
>
> (Set the DNSDOMAIN variable to your domain name)
> DNSDOMAIN="yourhomenetworkname"rc-update add domainname defaultnano -w 
> /etc/conf.d/net
> (should be blank or all lines commented)
>
> rc-update add net.eth0 default
>
> /etc/init.d/net.eth0 start
>
>
> ----- Original Message ----- From: "DR GM SEDDON" 
> <gavin.m.seddon@manchester.ac.uk>
>
> <snip>
>
>> Now it boots but asksme to
>> 'specifya device to boot' it boots when I enter 'dev/hda3'.  It is 
>> specified in 'grub.conf' and 'fstab'.  Any ideas?
>>
>> Also, I get 'dhcpd:required function  'interface _is_up' but 
>> networking isn't working.  And, I get 'netmount not started'.  Are 
>> these issues related.  Can you help?
>> Regards,
>> Gavin.
>
>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Harm Geerts]

On Wednesday 02 November 2005 13:38, DR GM SEDDON wrote:
> Hi,
> Yes, this worked for booting.
>
> rc-update add net.rth0 default gave
> 'already installed in runlevel default'
> and
> /etc/init.d/net.eth0 start
> 'dhcpd:missing required function interface_is_up'

Triple check your networking config:
nano -w  /etc/conf.d/net

Read the documentation/examples in /etc/conf.d/net.example

All your problems are user errors and have nothing to do with amd64.
Are you sure Gentoo is the right distribution for you?
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[DR GM SEDDON]

William Tetrault wrote:

>I too have been on the amd64 platform since early last year, and am still 
>using grub-static, although I know that grub now compiles fine for this 
>platform (at least, that is what I've heard - I'm still using grub-static).  
>But whether one uses grub or grub-static, the installed files are the same, 
>and grub works the same regardless of which is chosen.  My grub.conf has not 
>changed from when I was using Athlon XP's (although it's no longer called 
>grub.lst).
>
>On Sunday 30 October 2005 12:07 pm, Dmitri Pogosyan wrote:
>  
>
>>Actually, that reminds me that a year ago on amd64 architecture the
>>compiled grub did not work for me (it did compile but fail to boot) and I
>>had to use grub-static-0.93, which worked fine.  I looked now and see that
>>I still use this version of grub on all my amd64 machines.
>>
>>    
>>
Hi, shall I try 'emerge unmerge grub' and 'emerge grub-static'?  Then 
'install-grub' to start the system using the static ver/

This seems v. promising.

Gavin.

>>
>>--
>>Dmitri Pogosyan            Department of Physics
>>Associate Professor        University of Alberta
>>tel 1-780-492-2150         412 Avadh Bhatia Physics Labs
>>fax 1-780-492-0714         Edmonton, AB, T6G 2J1, CANADA
>>    
>>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Dmitri Pogosyan]

> > I wondered, should /boot be ext2?  Or should I use some of the 'default'
> > entries?
> This is my line for the boot partition:
> /dev/hda1               /boot           auto            noauto,noatime,notail 
> 1 1
> It's reiserFS I think. I used "auto" because I wasn't sure what to type for 
> it.
> 
I have

/dev/sda1		/boot		ext3		noatime		1 1
/dev/sda2		/		reiserfs	noatime		0 0

and the rest are reiserfs. Do you, by the way, have reiserfs build into the
kernel or as a module ?



-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Dmitri Pogosyan]

> > I wondered, should /boot be ext2?  Or should I use some of the 'default'
> > entries?
> This is my line for the boot partition:
> /dev/hda1               /boot           auto            noauto,noatime,notail 
> 1 1
> It's reiserFS I think. I used "auto" because I wasn't sure what to type for 
> it.
> 
I have

/dev/sda1		/boot		ext3		noatime		1 1
/dev/sda2		/		reiserfs	noatime		0 0

and the rest are reiserfs. Do you, by the way, have reiserfs build into the
kernel or as a module ?


> -- 
> Karol Krizka



--
Dmitri Pogosyan            Department of Physics
Associate Professor        University of Alberta
tel 1-780-492-2150         412 Avadh Bhatia Physics Labs
fax 1-780-492-0714         Edmonton, AB, T6G 2J1, CANADA


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Karol Krizka]

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

On Sunday 30 October 2005 07:59, Dmitri Pogosyan wrote:
> > > I wondered, should /boot be ext2?  Or should I use some of the
> > > 'default' entries?
> >
> > This is my line for the boot partition:
> > /dev/hda1               /boot           auto           
> > noauto,noatime,notail 1 1
> > It's reiserFS I think. I used "auto" because I wasn't sure what to type
> > for it.
>
> I have
>
> /dev/sda1		/boot		ext3		noatime		1 1
> /dev/sda2		/		reiserfs	noatime		0 0
>
> and the rest are reiserfs. Do you, by the way, have reiserfs build into the
> kernel or as a module ?
>
In kernel, but as I understand from this thread it dosn't matter since it's 
the point of initrd to make sure the modules are loaded. But that's not the 
problem as you need to access /boot before the kernel is loaded. And ext3 is 
almost the same as ext2 but with journaling as I understand it.

-- 
Karol Krizka

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] initrd

[DR GM SEDDON]

Dmitri Pogosyan wrote:

>>>I wondered, should /boot be ext2?  Or should I use some of the 'default'
>>>entries?
>>>      
>>>
>>This is my line for the boot partition:
>>/dev/hda1               /boot           auto            noauto,noatime,notail 
>>1 1
>>It's reiserFS I think. I used "auto" because I wasn't sure what to type for 
>>it.
>>
>>    
>>
>I have
>
>/dev/sda1		/boot		ext3		noatime		1 1
>/dev/sda2		/		reiserfs	noatime		0 0
>
>and the rest are reiserfs. Do you, by the way, have reiserfs build into the
>kernel or as a module ?
>
>No, I use ext3 since rfs involved more 'tweaking' and I have never used it.  Gavin.
>  
>
>>-- 
>>Karol Krizka
>>    
>>
>
>
>
>--
>Dmitri Pogosyan            Department of Physics
>Associate Professor        University of Alberta
>tel 1-780-492-2150         412 Avadh Bhatia Physics Labs
>fax 1-780-492-0714         Edmonton, AB, T6G 2J1, CANADA
>
>
>  
>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Dmitri Pogosyan]

> On 29 Oct 2005, at 14:21, DR GM SEDDON wrote:
> > Dmitri Pogosyan wrote:
> >> Not really, you can use initramfs in place of initrd. I have in  
> >> grub.conf title=Gentoo Linux 2.6.13-r3 UDEV root (hd0,0) kernel / 
> >> kernel-2.6.13-gentoo-r3 root=/dev/ram0 ramdisk=16384 init=/linuxrc  
> >> real_root=/dev/sda2 vga=3847 udev initrd /initramfs-2.6.13-gentoo-r3
> >>
> >>> Dear list, I have just started using Gentoo and up-to-now am  
> >>> impressed.  I have  generated a kernel using 'genkernel' and the  
> >>> kernel is in /boot.   However, I do not have 'initrd' but  
> >>> 'initramfs'.  is this a problem or  should I modify grub  
> >>> appropriately? Gavin. --  gentoo-amd64@gentoo.org mailing list
> >>>
> >>
> >>
> > I noticed your files are in / not /boot where mine  are.  Should I  
> > mv them?
> 
> They're in / only on the boot partition ie they are in the root of  
> (hd0,0).
> 
> If you are specifying your files as living in /boot on the boot  
> partition then this could stop your system booting fully.
> 
Exactly, here is my

#ls -l /boot
-rw-r--r--  1 root root 1050830 Mar 30  2005 System.map-2.6.11-gentoo-r3
-rw-r--r--  1 root root 1050580 May 12 22:42 System.map-2.6.11-gentoo-r7
-rw-r--r--  1 root root 1214233 Oct 11 00:54 System.map-2.6.13-gentoo-r3
-rw-r--r--  1 root root 1019913 Mar  5  2005 System.map-2.6.9-gentoo-r14
-rw-r--r--  1 root root 1219082 Oct 11 17:54 System.map-2.6.13-gentoo-r3
lrwxrwxrwx  1 root root       1 Jan 11  2005 boot -> .
drwxr-xr-x  2 root root    1024 Oct 11 17:27 grub
-rw-r--r--  1 root root  884138 Oct 11 17:57 initramfs-2.6.13-gentoo-r3
-rw-r--r--  1 root root 1044636 Mar 30  2005 initrd-2.6.11-gentoo-r3
-rw-r--r--  1 root root 1035787 May 12 22:45 initrd-2.6.11-gentoo-r7
-rw-r--r--  1 root root 1055316 Mar  5  2005 initrd-2.6.9-gentoo-r14
-rw-r--r--  1 root root 1748333 Mar 30  2005 kernel-2.6.11-gentoo-r3
-rw-r--r--  1 root root 1745664 May 12 22:42 kernel-2.6.11-gentoo-r7
-rw-r--r--  1 root root 1795423 Oct 11 17:54 kernel-2.6.13-gentoo-r3
-rw-r--r--  1 root root 1663290 Mar  5  2005 kernel-2.6.9-gentoo-r14
drwx------  2 root root   12288 Jan 11  2005 lost+found





-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Dmitri Pogosyan]

Not really, you can use initramfs in place of initrd. I have in grub.conf 
 
title=Gentoo Linux 2.6.13-r3 UDEV 
root (hd0,0) 
kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 ramdisk=16384 init=/linuxrc 
real_root=/dev/sda2 vga=3847 udev 
initrd /initramfs-2.6.13-gentoo-r3 
 
 
 
 
> Dear list, 
> I have just started using Gentoo and up-to-now am impressed.  I have  
> generated a kernel using 'genkernel' and the kernel is in /boot.   
> However, I do not have 'initrd' but 'initramfs'.  is this a problem or  
> should I modify grub appropriately? 
> Gavin. 
> --  
> gentoo-amd64@gentoo.org mailing list 
 
 
 
-- 
Dmitri Pogosyan            Department of Physics 
Associate Professor        University of Alberta 
tel 1-780-492-2150         412 Avadh Bhatia Physics Labs 
fax 1-780-492-0714         Edmonton, AB, T6G 2J1, CANADA 
 
 
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Lee Thompson]

Great write-up on initrd here
http://gentoo-wiki.com/HOWTO_fbsplash
very cool stuff

--- Dmitri Pogosyan <pogosyan@phys.ualberta.ca> wrote:

> Not really, you can use initramfs in place of
> initrd. I have in grub.conf 
>  
> title=Gentoo Linux 2.6.13-r3 UDEV 
> root (hd0,0) 
> kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0
> ramdisk=16384 init=/linuxrc 
> real_root=/dev/sda2 vga=3847 udev 
> initrd /initramfs-2.6.13-gentoo-r3 
>  
>  
>  
>  
> > Dear list, 
> > I have just started using Gentoo and up-to-now am
> impressed.  I have  
> > generated a kernel using 'genkernel' and the
> kernel is in /boot.   
> > However, I do not have 'initrd' but 'initramfs'. 
> is this a problem or  
> > should I modify grub appropriately? 
> > Gavin. 
> > --  
> > gentoo-amd64@gentoo.org mailing list 
>  
>  
>  
> -- 
> Dmitri Pogosyan            Department of Physics 
> Associate Professor        University of Alberta 
> tel 1-780-492-2150         412 Avadh Bhatia Physics
> Labs 
> fax 1-780-492-0714         Edmonton, AB, T6G 2J1,
> CANADA 
>  
>  
> -- 
> gentoo-amd64@gentoo.org mailing list
> 
> 



		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[DR GM SEDDON]

Dmitri Pogosyan wrote:

>Not really, you can use initramfs in place of initrd. I have in grub.conf 
> 
>title=Gentoo Linux 2.6.13-r3 UDEV 
>root (hd0,0) 
>kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 ramdisk=16384 init=/linuxrc 
>real_root=/dev/sda2 vga=3847 udev 
>initrd /initramfs-2.6.13-gentoo-r3 
> 
> 
> 
> 
>  
>
>>Dear list, 
>>I have just started using Gentoo and up-to-now am impressed.  I have  
>>generated a kernel using 'genkernel' and the kernel is in /boot.   
>>However, I do not have 'initrd' but 'initramfs'.  is this a problem or  
>>should I modify grub appropriately? 
>>Gavin. 
>>--  
>>gentoo-amd64@gentoo.org mailing list 
>>    
>>
> 
> 
> 
>  
>
I noticed your files are in / not /boot where mine  are.  Should I mv them?
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Craig Webster]

On 29 Oct 2005, at 14:21, DR GM SEDDON wrote:
> Dmitri Pogosyan wrote:
>> Not really, you can use initramfs in place of initrd. I have in  
>> grub.conf title=Gentoo Linux 2.6.13-r3 UDEV root (hd0,0) kernel / 
>> kernel-2.6.13-gentoo-r3 root=/dev/ram0 ramdisk=16384 init=/linuxrc  
>> real_root=/dev/sda2 vga=3847 udev initrd /initramfs-2.6.13-gentoo-r3
>>
>>> Dear list, I have just started using Gentoo and up-to-now am  
>>> impressed.  I have  generated a kernel using 'genkernel' and the  
>>> kernel is in /boot.   However, I do not have 'initrd' but  
>>> 'initramfs'.  is this a problem or  should I modify grub  
>>> appropriately? Gavin. --  gentoo-amd64@gentoo.org mailing list
>>>
>>
>>
> I noticed your files are in / not /boot where mine  are.  Should I  
> mv them?

They're in / only on the boot partition ie they are in the root of  
(hd0,0).

If you are specifying your files as living in /boot on the boot  
partition then this could stop your system booting fully.

Perhaps you could post your grub.conf?

Yours,
Craig
--
Craig Webster | t: +44 (0)131 516 8595 | e: craig@xeriom.net
Xeriom.NET    | f: +44 (0)709 287 1902 | w: http://xeriom.net


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[DR GM SEDDON]

my grub.conf:
' default 0
timeout     5
splashimage=(hd0.0)/grub/splash.xpm.gz

title=linux-2.6.13
root (hd0.0)
kernel /genkernel--x86_64-2.6.13-gentoo-r3 root=/dev/ram0  init=/linuxrc 
ramdisk-8193 real_root=/dev/hda3 udev
initrd /initrd'

I see hoew by saying root (hd0,0) leaves things relative to /boot.  But 
there is no linuxrc in /boot.  I think this is the prob.

The error code is 15. 
Thanks


Craig Webster wrote:

> On 29 Oct 2005, at 14:21, DR GM SEDDON wrote:
>
>> Dmitri Pogosyan wrote:
>>
>>> Not really, you can use initramfs in place of initrd. I have in  
>>> grub.conf title=Gentoo Linux 2.6.13-r3 UDEV root (hd0,0) kernel / 
>>> kernel-2.6.13-gentoo-r3 root=/dev/ram0 ramdisk=16384 init=/linuxrc  
>>> real_root=/dev/sda2 vga=3847 udev initrd /initramfs-2.6.13-gentoo-r3
>>>
>>>> Dear list, I have just started using Gentoo and up-to-now am  
>>>> impressed.  I have  generated a kernel using 'genkernel' and the  
>>>> kernel is in /boot.   However, I do not have 'initrd' but  
>>>> 'initramfs'.  is this a problem or  should I modify grub  
>>>> appropriately? Gavin. --  gentoo-amd64@gentoo.org mailing list
>>>>
>>>
>>>
>> I noticed your files are in / not /boot where mine  are.  Should I  
>> mv them?
>
>
> They're in / only on the boot partition ie they are in the root of  
> (hd0,0).
>
> If you are specifying your files as living in /boot on the boot  
> partition then this could stop your system booting fully.
>
> Perhaps you could post your grub.conf?
>
> Yours,
> Craig
> -- 
> Craig Webster | t: +44 (0)131 516 8595 | e: craig@xeriom.net
> Xeriom.NET    | f: +44 (0)709 287 1902 | w: http://xeriom.net
>
>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Karol Krizka]

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

On Saturday 29 October 2005 07:16, DR GM SEDDON wrote:
> my grub.conf:
> ' default 0
> timeout     5
> splashimage=(hd0.0)/grub/splash.xpm.gz
>
> title=linux-2.6.13
> root (hd0.0)
> kernel /genkernel--x86_64-2.6.13-gentoo-r3 root=/dev/ram0  init=/linuxrc
> ramdisk-8193 real_root=/dev/hda3 udev
> initrd /initrd'
>
I have the sameconfig and it works ok exept the name of /initrd I 
have /initramfs-genkernel-x86_64-2.6.13-gentoo-r3. Maybe that is the problem?

> I see hoew by saying root (hd0,0) leaves things relative to /boot.  But
> there is no linuxrc in /boot.  I think this is the prob.
>
/linuxrc is in the initramfs thing so that's not the problem.

> The error code is 15.
> Thanks
>
> Craig Webster wrote:
> > On 29 Oct 2005, at 14:21, DR GM SEDDON wrote:
> >> Dmitri Pogosyan wrote:
> >>> Not really, you can use initramfs in place of initrd. I have in
> >>> grub.conf title=Gentoo Linux 2.6.13-r3 UDEV root (hd0,0) kernel /
> >>> kernel-2.6.13-gentoo-r3 root=/dev/ram0 ramdisk=16384 init=/linuxrc
> >>> real_root=/dev/sda2 vga=3847 udev initrd /initramfs-2.6.13-gentoo-r3
> >>>
> >>>> Dear list, I have just started using Gentoo and up-to-now am
> >>>> impressed.  I have  generated a kernel using 'genkernel' and the
> >>>> kernel is in /boot.   However, I do not have 'initrd' but
> >>>> 'initramfs'.  is this a problem or  should I modify grub
> >>>> appropriately? Gavin. --  gentoo-amd64@gentoo.org mailing list
> >>
> >> I noticed your files are in / not /boot where mine  are.  Should I
> >> mv them?
> >
> > They're in / only on the boot partition ie they are in the root of
> > (hd0,0).
> >
> > If you are specifying your files as living in /boot on the boot
> > partition then this could stop your system booting fully.
> >
> > Perhaps you could post your grub.conf?
> >
> > Yours,
> > Craig
> > --
> > Craig Webster | t: +44 (0)131 516 8595 | e: craig@xeriom.net
> > Xeriom.NET    | f: +44 (0)709 287 1902 | w: http://xeriom.net

-- 
Karol Krizka

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] initrd

[DR GM SEDDON]

Karol Krizka wrote:

>On Saturday 29 October 2005 07:16, DR GM SEDDON wrote:
>  
>
>>my grub.conf:
>>' default 0
>>timeout     5
>>splashimage=(hd0.0)/grub/splash.xpm.gz
>>
>>title=linux-2.6.13
>>root (hd0.0)
>>kernel /genkernel--x86_64-2.6.13-gentoo-r3 root=/dev/ram0  init=/linuxrc
>>ramdisk-8193 real_root=/dev/hda3 udev
>>initrd /initrd'
>>
>>    
>>
>I have the sameconfig and it works ok exept the name of /initrd I 
>have /initramfs-genkernel-x86_64-2.6.13-gentoo-r3. Maybe that is the problem?
>
>  
>
>>I see hoew by saying root (hd0,0) leaves things relative to /boot.  But
>>there is no linuxrc in /boot.  I think this is the prob.
>>
>>    
>>
>/linuxrc is in the initramfs thing so that's not the problem.
>
>  
>
>>The error code is 15.
>>Thanks
>>
>>Craig Webster wrote:
>>    
>>
>>>On 29 Oct 2005, at 14:21, DR GM SEDDON wrote:
>>>      
>>>
>>>>Dmitri Pogosyan wrote:
>>>>        
>>>>
>>>>>Not really, you can use initramfs in place of initrd. I have in
>>>>>grub.conf title=Gentoo Linux 2.6.13-r3 UDEV root (hd0,0) kernel /
>>>>>kernel-2.6.13-gentoo-r3 root=/dev/ram0 ramdisk=16384 init=/linuxrc
>>>>>real_root=/dev/sda2 vga=3847 udev initrd /initramfs-2.6.13-gentoo-r3
>>>>>
>>>>>          
>>>>>
>>>>>>Dear list, I have just started using Gentoo and up-to-now am
>>>>>>impressed.  I have  generated a kernel using 'genkernel' and the
>>>>>>kernel is in /boot.   However, I do not have 'initrd' but
>>>>>>'initramfs'.  is this a problem or  should I modify grub
>>>>>>appropriately? Gavin. --  gentoo-amd64@gentoo.org mailing list
>>>>>>            
>>>>>>
>>>>I noticed your files are in / not /boot where mine  are.  Should I
>>>>mv them?
>>>>        
>>>>
>>>They're in / only on the boot partition ie they are in the root of
>>>(hd0,0).
>>>
>>>If you are specifying your files as living in /boot on the boot
>>>partition then this could stop your system booting fully.
>>>
>>>Perhaps you could post your grub.conf?
>>>
>>>Yours,
>>>Craig
>>>--
>>>Craig Webster | t: +44 (0)131 516 8595 | e: craig@xeriom.net
>>>Xeriom.NET    | f: +44 (0)709 287 1902 | w: http://xeriom.net
>>>      
>>>
>
>  
>
grub.conf
'default 0
timeout 5
splashimage=(hd0,0)/grub/splash.xpm.gz

title=linux-2.6.13
root (hd0,0)
kernel /genkernel-x86_64-2.6.13-gentoo-r3 root=/dev/ram0 
init=/initramfs-genkernel-x86_64-2.6.13-gentoo-r3 ramdisk=8192
real_boot=/dev/hda3 udev
initrd /initrd'

fstab
'# /etc/fstab: static file system information.
# $Header: /var/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.18.4.1 
2005/01/31 23:05:14 vapier Exp $
#
# noatime turns off atimes for increased performance (atimes normally 
aren't
# needed; notail increases performance of ReiserFS (at the expense of 
storage
# efficiency).  It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# See the manpage fstab(5) for more information.

# <fs>            <mountpoint>    <type>        <opts>        <dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
#/dev/BOOT        /boot        ext2        noauto,noatime    1 2
#/dev/ROOT        /        ext3        noatime        0 1
#/dev/SWAP        none        swap        sw        0 0
#/dev/cdroms/cdrom0    /mnt/cdrom    iso9660        noauto,ro    0 0
#/dev/fd0        /mnt/floppy    auto        noauto        0 0

# NOTE: The next line is critical for boot!
#proc            /proc        proc        defaults    0 0

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
#  use almost no memory if not populated with files)
#shm            /dev/shm    tmpfs        nodev,nosuid,noexec    0 0

#my fstab
/dev/hda1        /boot            ext3    defaults,noatime        1 2
/dev/hda2        none            swap    sw                0 0
/dev/hda3        /            ext3    noatime                0 1

none            /proc            proc    defaults            0 0
none            /dev/shm        tmpfs    nodev,nosuid,noexec        0 0

/dev/cdroms/cdrom0    /mnt/cdrom        auto    noauto,user            0 0
/dev/fd0        /mnt/floppy        auto    noauto,user            0 0
'

I wondered, should /boot be ext2?  Or should I use some of the 'default' 
entries?
Thanks.
I looked at the url mentioned it tells me my error(15) is grub not 
finding my kernel.  How do I tell grub to boot my kernel from the 
command line?  It tells me the kernel needs to be loaded first.
Gavin.



-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Karol Krizka]

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

On Sunday 30 October 2005 01:48, DR GM SEDDON wrote:
> Karol Krizka wrote:
> >On Saturday 29 October 2005 07:16, DR GM SEDDON wrote:
> >>my grub.conf:
> >>' default 0
> >>timeout     5
> >>splashimage=(hd0.0)/grub/splash.xpm.gz
> >>
> >>title=linux-2.6.13
> >>root (hd0.0)
> >>kernel /genkernel--x86_64-2.6.13-gentoo-r3 root=/dev/ram0  init=/linuxrc
> >>ramdisk-8193 real_root=/dev/hda3 udev
> >>initrd /initrd'
> >
> >I have the sameconfig and it works ok exept the name of /initrd I
> >have /initramfs-genkernel-x86_64-2.6.13-gentoo-r3. Maybe that is the
> > problem?
> >
> >>I see hoew by saying root (hd0,0) leaves things relative to /boot.  But
> >>there is no linuxrc in /boot.  I think this is the prob.
> >
> >/linuxrc is in the initramfs thing so that's not the problem.
> >
> >>The error code is 15.
> >>Thanks
> >>
> >>Craig Webster wrote:
> >>>On 29 Oct 2005, at 14:21, DR GM SEDDON wrote:
> >>>>Dmitri Pogosyan wrote:
> >>>>>Not really, you can use initramfs in place of initrd. I have in
> >>>>>grub.conf title=Gentoo Linux 2.6.13-r3 UDEV root (hd0,0) kernel /
> >>>>>kernel-2.6.13-gentoo-r3 root=/dev/ram0 ramdisk=16384 init=/linuxrc
> >>>>>real_root=/dev/sda2 vga=3847 udev initrd /initramfs-2.6.13-gentoo-r3
> >>>>>
> >>>>>>Dear list, I have just started using Gentoo and up-to-now am
> >>>>>>impressed.  I have  generated a kernel using 'genkernel' and the
> >>>>>>kernel is in /boot.   However, I do not have 'initrd' but
> >>>>>>'initramfs'.  is this a problem or  should I modify grub
> >>>>>>appropriately? Gavin. --  gentoo-amd64@gentoo.org mailing list
> >>>>
> >>>>I noticed your files are in / not /boot where mine  are.  Should I
> >>>>mv them?
> >>>
> >>>They're in / only on the boot partition ie they are in the root of
> >>>(hd0,0).
> >>>
> >>>If you are specifying your files as living in /boot on the boot
> >>>partition then this could stop your system booting fully.
> >>>
> >>>Perhaps you could post your grub.conf?
> >>>
> >>>Yours,
> >>>Craig
> >>>--
> >>>Craig Webster | t: +44 (0)131 516 8595 | e: craig@xeriom.net
> >>>Xeriom.NET    | f: +44 (0)709 287 1902 | w: http://xeriom.net
>
> grub.conf
> 'default 0
> timeout 5
> splashimage=(hd0,0)/grub/splash.xpm.gz
>
> title=linux-2.6.13
> root (hd0,0)
> kernel /genkernel-x86_64-2.6.13-gentoo-r3 root=/dev/ram0
> init=/initramfs-genkernel-x86_64-2.6.13-gentoo-r3 ramdisk=8192
> real_boot=/dev/hda3 udev
> initrd /initrd'
>
Try replacing the kernel name with kernel-genkernel-x86_64-2.6.13-gentoo-r3, 
if that dosn't work show us the outpot of ls /boot.

<snip>
>
> I wondered, should /boot be ext2?  Or should I use some of the 'default'
> entries?
This is my line for the boot partition:
/dev/hda1               /boot           auto            noauto,noatime,notail 
1 1
It's reiserFS I think. I used "auto" because I wasn't sure what to type for 
it.

> Thanks.
> I looked at the url mentioned it tells me my error(15) is grub not
> finding my kernel.  How do I tell grub to boot my kernel from the
> command line?  It tells me the kernel needs to be loaded first.
Press e over the kernel you want to boot, then choose the line you want to 
edit and press e again. You can also use d to delete a line. There is 
instructions for more key bindings on the bottom of GRUB.

-- 
Karol Krizka

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] initrd

[William Tetrault]

On Sunday 30 October 2005 03:48 am, DR GM SEDDON wrote:
> Karol Krizka wrote:
> >On Saturday 29 October 2005 07:16, DR GM SEDDON wrote:
> >>my grub.conf:
> >>' default 0
> >>timeout     5
> >>splashimage=(hd0.0)/grub/splash.xpm.gz
> >>
> >>title=linux-2.6.13
> >>root (hd0.0)
> >>kernel /genkernel--x86_64-2.6.13-gentoo-r3 root=/dev/ram0  init=/linuxrc
> >>ramdisk-8193 real_root=/dev/hda3 udev
> >>initrd /initrd'
SNIP
> >
> >>>>I noticed your files are in / not /boot where mine  are.  Should I
> >>>>mv them?
> >>>
> >>>They're in / only on the boot partition ie they are in the root of
> >>>(hd0,0).
> >>>
> >>>If you are specifying your files as living in /boot on the boot
> >>>partition then this could stop your system booting fully.
> >>>
> >>>Perhaps you could post your grub.conf?
SNIP

I've been using gentoo for 3 yrs now and using a grub.conf exactly as follows 
for all that time.  It has <never> failed to work.  I did not create 
the /boot dir with mkdir, that was done when I cp'd my bzImage 
from /usr/src/linux/arch/x86_64/boot/bzImage to /boot, and I did it that way 
because that's how the docs said to do it.

tbill@Shooter ~ $ cat /boot/grub/grub.conf
default 0
timeout 10
splashimage=(hd0,0)/boot/grub/splash.xpm.gz

title=Gentoo (linux kernel 2.6.11-gentoo-r10)
root (hd0,0)
kernel (hd0,0)/boot/bzImage root=/dev/sda1

If you, when you installed gentoo in the first place, placed /boot in its own 
partition, then anything you copy to that partition is going to start with 
"/boot...".  How else are you going to tell the kernel to copy something to 
the boot partition when /boot is all you've mounted there?  If you, as root, 
tell the system to mount the partition where you've installed grub.conf, how 
else do you specify it except as "mount /boot".  I don't mean to belabor the 
point, but....

So tell grub to look on "(hd0,0)/boot/bzImage" for the kernel to boot, 
only,since you don't have a bzImage but a genkernel, change it accordingly: 
(hd0,0)/boot/genkernel-*.  I assure you that this <does not> "stop your 
system from booting fully."

Also, since you're getting error code 15, what you have in /etc/fstab is 
completely immaterial.  Grub can't even find your kernel, and grub's interest 
stops at finding the kernel, so take care of grub's errors first, then worry 
about whether your fstab is properly set up.

Bill Tetrault
Madison, WI
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Drake Donahue]

splashimage=(hd0.0)/grub/splash.xpm.gz should be
    splashimage=(hd0.0)/grub/splash.xpm.gz

root (hd0.0) should be
    root (hd0,0)

i.e. period should be a comma in both lines

sample in the documentation suggests to me:

        boot knoppix, mount hard drive root partion and read the directory:
             /kernel-2.6.13-r3 should be listed if not some other kernel 
should be listed in the directory and should be
             substituted for /kernel-2.6.13-r3 in the kernel line

kernel /genkernel--x86_64-2.6.13-gentoo-r3 root=/dev/ram0  init=/linuxrc 
should be
    kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 init=/linuxrc 
ramdisk=8192 real_root=/dev/hda3 udev


 initrd /initrd' should be         (Maybe --didn't use genkernel and don't 
know it but if it copies kernel direct from cd to ramdisk this:)
    initrd /initramfs-genkernel-amd64-2.6.12-gentoo-r6
                                            (or Maybe --didn't use genkernel 
and don't know it but if it doesn't copy kernel direct from cd this:)
    initrd /initramfs-genkernel-amd64-2.6.13-gentoo-r3


----- Original Message ----- 
From: "DR GM SEDDON" <gavin.m.seddon@manchester.ac.uk>
To: <gentoo-amd64@lists.gentoo.org>
Sent: Saturday, October 29, 2005 10:16 AM
Subject: Re: [gentoo-amd64] initrd


> my grub.conf:
> ' default 0
> timeout     5
> splashimage=(hd0.0)/grub/splash.xpm.gz
>
> title=linux-2.6.13
> root (hd0.0)
> kernel /genkernel--x86_64-2.6.13-gentoo-r3 root=/dev/ram0  init=/linuxrc 
> ramdisk-8193 real_root=/dev/hda3 udev
> initrd /initrd'

 default 0
timeout 30
splashimage=(hd0,0)/grub/splash.xpm.gz

title=Gentoo Linux 2.6.12
root (hd0,0)
kernel /kernel-2.6.12-gentoo-r6 root=/dev/ram0 init=/linuxrc ramdisk=8192 
real_root=/dev/hda3 udev
initrd /initramfs-genkernel-amd64-2.6.12-gentoo-r6 

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Drake Donahue]

oops:

splashimage=(hd0.0)/grub/splash.xpm.gz should be
   splashimage=(hd0,0)/grub/splash.xpm.gz

----- Original Message ----- 
From: "Drake Donahue" <donahue95@comcast.net>
To: <gentoo-amd64@lists.gentoo.org>
Sent: Saturday, October 29, 2005 12:40 PM
Subject: Re: [gentoo-amd64] initrd


> splashimage=(hd0.0)/grub/splash.xpm.gz should be
>    splashimage=(hd0,0)/grub/splash.xpm.gz
>
> root (hd0.0) should be
>    root (hd0,0)
>
> i.e. period should be a comma in both lines
>
> sample in the documentation suggests to me:
>
>        boot knoppix, mount hard drive root partion and read the directory:
>             /kernel-2.6.13-r3 should be listed if not some other kernel 
> should be listed in the directory and should be
>             substituted for /kernel-2.6.13-r3 in the kernel line
>
> kernel /genkernel--x86_64-2.6.13-gentoo-r3 root=/dev/ram0  init=/linuxrc 
> should be
>    kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 init=/linuxrc 
> ramdisk=8192 real_root=/dev/hda3 udev
>
>
> initrd /initrd' should be         (Maybe --didn't use genkernel and don't 
> know it but if it copies kernel direct from cd to ramdisk this:)
>    initrd /initramfs-genkernel-amd64-2.6.12-gentoo-r6
>                                            (or Maybe --didn't use 
> genkernel and don't know it but if it doesn't copy kernel direct from cd 
> this:)
>    initrd /initramfs-genkernel-amd64-2.6.13-gentoo-r3
>
>
> ----- Original Message ----- 
> From: "DR GM SEDDON" <gavin.m.seddon@manchester.ac.uk>
> To: <gentoo-amd64@lists.gentoo.org>
> Sent: Saturday, October 29, 2005 10:16 AM
> Subject: Re: [gentoo-amd64] initrd
>
>
>> my grub.conf:
>> ' default 0
>> timeout     5
>> splashimage=(hd0.0)/grub/splash.xpm.gz
>>
>> title=linux-2.6.13
>> root (hd0.0)
>> kernel /genkernel--x86_64-2.6.13-gentoo-r3 root=/dev/ram0  init=/linuxrc 
>> ramdisk-8193 real_root=/dev/hda3 udev
>> initrd /initrd'
>
> default 0
> timeout 30
> splashimage=(hd0,0)/grub/splash.xpm.gz
>
> title=Gentoo Linux 2.6.12
> root (hd0,0)
> kernel /kernel-2.6.12-gentoo-r6 root=/dev/ram0 init=/linuxrc ramdisk=8192 
> real_root=/dev/hda3 udev
> initrd /initramfs-genkernel-amd64-2.6.12-gentoo-r6
> -- 
> gentoo-amd64@gentoo.org mailing list
>
> 

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[William Tetrault]

On Saturday 29 October 2005 09:16 am, DR GM SEDDON wrote:
> my grub.conf:
> ' default 0
> timeout     5
> splashimage=(hd0.0)/grub/splash.xpm.gz
>
> title=linux-2.6.13
> root (hd0.0)
try "kernel (hd0,0)/boot/genkernel-* ...."  I think the kernel line,without 
the "(hd0,0)/boot" tells grub to look for something which doesn't exist, 
especially if /genkernel is in the /boot directory on (hd0,0).
> kernel /genkernel--x86_64-2.6.13-gentoo-r3 root=/dev/ram0  init=/linuxrc
> ramdisk-8193 real_root=/dev/hda3 udev
> initrd /initrd'
>
> I see hoew by saying root (hd0,0) leaves things relative to /boot.  But
> there is no linuxrc in /boot.  I think this is the prob.
>
> The error code is 15.
> Thanks
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[bruce harding]

On Sat, 29 Oct 2005 14:21:52 +0100
DR GM SEDDON <gavin.m.seddon@manchester.ac.uk> wrote:

> Dmitri Pogosyan wrote:
> 
> >Not really, you can use initramfs in place of initrd. I have in
> >grub.conf 
> > 
> >title=Gentoo Linux 2.6.13-r3 UDEV 
> >root (hd0,0) 
> >kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 ramdisk=16384
> >init=/linuxrc real_root=/dev/sda2 vga=3847 udev 
> >initrd /initramfs-2.6.13-gentoo-r3 


I've notice that some ppl are putting udev on the kernel line.  I was
under the impression that this was not needed to get udev working?

--
bruce
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] initrd

[DR GM SEDDON]

Dear list,
I have just started using Gentoo and up-to-now am impressed.  I have 
generated a kernel using 'genkernel' and the kernel is in /boot.  
However, I do not have 'initrd' but 'initramfs'.  is this a problem or 
should I modify grub appropriately?
Gavin.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Mark Knecht]

On 10/28/05, DR GM SEDDON <gavin.m.seddon@manchester.ac.uk> wrote:
> Dear list,
> I have just started using Gentoo and up-to-now am impressed.  I have
> generated a kernel using 'genkernel' and the kernel is in /boot.
> However, I do not have 'initrd' but 'initramfs'.  is this a problem or
> should I modify grub appropriately?
> Gavin.

Possibly. I don't use an initrd at all and boot just fine, so it's
possible that you can skip the whole issue if you want to.

Cheers,
Mark

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] initrd

[Hemmann, Volker Armin]

On Friday 28 October 2005 16:13, DR GM SEDDON wrote:
> Dear list,
> I have just started using Gentoo and up-to-now am impressed.  I have
> generated a kernel using 'genkernel' and the kernel is in /boot.
> However, I do not have 'initrd' but 'initramfs'.  is this a problem or
> should I modify grub appropriately?
> Gavin.

I touched genkernel only once (when a friend used it, and it made a totally 
useless kernel) and from my experience it builds inadequate kernels.
Plus, if you are not using raid, any initrd/initramfs just adds time and 
overhead to your booting. It is a waste of ressources.
The only ones who 'need' it are distributions, who do want to use a 'one 
kernel fits all' approach and people with / on a raid/dm device.

Just build a kernel by yourself. It is easy.
make menuconfig
mount /boot
make all modules_install install 
and let grub.conf point to vmlinuz and vmlinuz.old.

The install run will create a vmlinuz link to your latest kernel and a 
vmlinuz.old link to the one used.
-- 
gentoo-amd64@gentoo.org mailing list