Mailing List Archive

Installing a new kernel
I've been suspicious that reconfiguring, recompiling, and reinstalling
my kernel is not taking effect on my local machine, and I'm just
booting to the old configuration. To test it, I removed agpgart
support from the kernel configuration, recompiled it with "make dep &&
make bzImage" and issued "make install", but dmesg still seems to load
agpgart on boot up. I have also tried manually copying over the
bzImage and System.map, but rebooting still seems to load agpgart
judging by the dmesg output. I'm using grub, but I shouldn't need to
reconfigure that since I'm using the same kernel right?

- Grant

--
gentoo-user@gentoo.org mailing list
Re: Installing a new kernel [ In reply to ]
On Mon, 13 Sep 2004 21:47:51 +0000, Grant <emailgrant@gmail.com> wrote:
> I've been suspicious that reconfiguring, recompiling, and reinstalling
> my kernel is not taking effect on my local machine, and I'm just
> booting to the old configuration. To test it, I removed agpgart
> support from the kernel configuration, recompiled it with "make dep &&
> make bzImage" and issued "make install", but dmesg still seems to load
> agpgart on boot up. I have also tried manually copying over the
> bzImage and System.map, but rebooting still seems to load agpgart
> judging by the dmesg output. I'm using grub, but I shouldn't need to
> reconfigure that since I'm using the same kernel right?
>
> - Grant
Just to double check that your not making the same error as me...
Are you mounting your boot partition then copying the kernel over your
old kernel then umount the boot partition??



--
Zen is total BS. When you realize that fact, you have mastered Zen.

--
gentoo-user@gentoo.org mailing list
Re: Installing a new kernel [ In reply to ]
On Tue, 14 Sep 2004 05:52:06 +0800, Senectus . <senectus@gmail.com> wrote:
>
>
> On Mon, 13 Sep 2004 21:47:51 +0000, Grant <emailgrant@gmail.com> wrote:
> > I've been suspicious that reconfiguring, recompiling, and reinstalling
> > my kernel is not taking effect on my local machine, and I'm just
> > booting to the old configuration. To test it, I removed agpgart
> > support from the kernel configuration, recompiled it with "make dep &&
> > make bzImage" and issued "make install", but dmesg still seems to load
> > agpgart on boot up. I have also tried manually copying over the
> > bzImage and System.map, but rebooting still seems to load agpgart
> > judging by the dmesg output. I'm using grub, but I shouldn't need to
> > reconfigure that since I'm using the same kernel right?
> >
> > - Grant
> Just to double check that your not making the same error as me...
> Are you mounting your boot partition then copying the kernel over your
> old kernel then umount the boot partition??

Should I mount my /boot partition before doing what I described?
Without doing any manual mounting after boot up:

bash-2.05b# mount
/dev/hda3 on / type ext3 (rw,noatime)
none on /dev type devfs (rw)
none on /proc type proc (rw)
none on /dev/shm type tmpfs (rw)

- Grant

--
gentoo-user@gentoo.org mailing list
Re: Installing a new kernel [ In reply to ]
Grant wrote:
> Should I mount my /boot partition before doing what I described?

Yes.

Regards,
Norberto

--
gentoo-user@gentoo.org mailing list
Re: Installing a new kernel [ In reply to ]
On Mon, 13 Sep 2004 22:00:01 +0000, Grant <emailgrant@gmail.com> wrote:
>
>
> On Tue, 14 Sep 2004 05:52:06 +0800, Senectus . <senectus@gmail.com> wrote:
> >
> >
> > On Mon, 13 Sep 2004 21:47:51 +0000, Grant <emailgrant@gmail.com> wrote:
> > > I've been suspicious that reconfiguring, recompiling, and reinstalling
> > > my kernel is not taking effect on my local machine, and I'm just
> > > booting to the old configuration. To test it, I removed agpgart
> > > support from the kernel configuration, recompiled it with "make dep &&
> > > make bzImage" and issued "make install", but dmesg still seems to load
> > > agpgart on boot up. I have also tried manually copying over the
> > > bzImage and System.map, but rebooting still seems to load agpgart
> > > judging by the dmesg output. I'm using grub, but I shouldn't need to
> > > reconfigure that since I'm using the same kernel right?
> > >
> > > - Grant
> > Just to double check that your not making the same error as me...
> > Are you mounting your boot partition then copying the kernel over your
> > old kernel then umount the boot partition??
>
> Should I mount my /boot partition before doing what I described?
> Without doing any manual mounting after boot up:
>
> bash-2.05b# mount
> /dev/hda3 on / type ext3 (rw,noatime)
> none on /dev type devfs (rw)
> none on /proc type proc (rw)
> none on /dev/shm type tmpfs (rw)
>
Its been a while since I've done this but I remember feeling very
silly after making the same mistake..
From memory normal systems never mount your boot partition as a part
of the system startup, so after you've made the new kernel you need to
mount the boot partition then copy the kernel over the top of the old
one (make a copy of the old one first). There is a way of using
multiple kernels and just choosing the one you want at the grub boot
menu, but I've not done this before so ask around a bit.
If you re-read the last few steps in the gentoo install handbook it
should be a little clearer.


--
Zen is total BS. When you realize that fact, you have mastered Zen.

--
gentoo-user@gentoo.org mailing list
Re: Installing a new kernel [ In reply to ]
> On Mon, 13 Sep 2004 22:00:01 +0000, Grant <emailgrant@gmail.com> wrote:
> >
> >
> > On Tue, 14 Sep 2004 05:52:06 +0800, Senectus . <senectus@gmail.com> wrote:
> > >
> > >
> > > On Mon, 13 Sep 2004 21:47:51 +0000, Grant <emailgrant@gmail.com> wrote:
> > > > I've been suspicious that reconfiguring, recompiling, and reinstalling
> > > > my kernel is not taking effect on my local machine, and I'm just
> > > > booting to the old configuration. To test it, I removed agpgart
> > > > support from the kernel configuration, recompiled it with "make dep &&
> > > > make bzImage" and issued "make install", but dmesg still seems to load
> > > > agpgart on boot up. I have also tried manually copying over the
> > > > bzImage and System.map, but rebooting still seems to load agpgart
> > > > judging by the dmesg output. I'm using grub, but I shouldn't need to
> > > > reconfigure that since I'm using the same kernel right?
> > > >
> > > > - Grant
> > > Just to double check that your not making the same error as me...
> > > Are you mounting your boot partition then copying the kernel over your
> > > old kernel then umount the boot partition??
> >
> > Should I mount my /boot partition before doing what I described?
> > Without doing any manual mounting after boot up:
> >
> > bash-2.05b# mount
> > /dev/hda3 on / type ext3 (rw,noatime)
> > none on /dev type devfs (rw)
> > none on /proc type proc (rw)
> > none on /dev/shm type tmpfs (rw)
> >
> Its been a while since I've done this but I remember feeling very
> silly after making the same mistake..
> From memory normal systems never mount your boot partition as a part
> of the system startup, so after you've made the new kernel you need to
> mount the boot partition then copy the kernel over the top of the old
> one (make a copy of the old one first). There is a way of using
> multiple kernels and just choosing the one you want at the grub boot
> menu, but I've not done this before so ask around a bit.
> If you re-read the last few steps in the gentoo install handbook it
> should be a little clearer.
>
>

The boot partition will be mounted on boot if it is listed in /etc/fstab.
It is not usual practice to mount the boot partition though, unless
you're actually doing something to it (security reasons), such as putting
another kernel there. What you need to do is mount the boot partition,
compile your kernel, move bzIamge and System.map to /boot.

If you want to have the option of booting to multiple kernels, simply copy
your new bzImage to a file with a different name, such as
kernel-new-version, same with System.map, and then add another entry in
grub.conf, similar to the one that is already there, but with the kernel
parameter referring to your new kernel file.

--
gentoo-user@gentoo.org mailing list
Re: Installing a new kernel [ In reply to ]
On Mon, 13 Sep 2004, Tom Erik Stower wrote:

>
> > On Mon, 13 Sep 2004 22:00:01 +0000, Grant <emailgrant@gmail.com> wrote:
> > >
> > >
> > > On Tue, 14 Sep 2004 05:52:06 +0800, Senectus . <senectus@gmail.com> wrote:
> > > >
> > > >
> > > > On Mon, 13 Sep 2004 21:47:51 +0000, Grant <emailgrant@gmail.com> wrote:
> > > > > I've been suspicious that reconfiguring, recompiling, and reinstalling
> > > > > my kernel is not taking effect on my local machine, and I'm just
> > > > > booting to the old configuration. To test it, I removed agpgart
> > > > > support from the kernel configuration, recompiled it with "make dep &&
> > > > > make bzImage" and issued "make install", but dmesg still seems to load
> > > > > agpgart on boot up. I have also tried manually copying over the
> > > > > bzImage and System.map, but rebooting still seems to load agpgart
> > > > > judging by the dmesg output. I'm using grub, but I shouldn't need to
> > > > > reconfigure that since I'm using the same kernel right?
> > > > >
> > > > > - Grant
> > > > Just to double check that your not making the same error as me...
> > > > Are you mounting your boot partition then copying the kernel over your
> > > > old kernel then umount the boot partition??
> > >
> > > Should I mount my /boot partition before doing what I described?
> > > Without doing any manual mounting after boot up:
> > >
> > > bash-2.05b# mount
> > > /dev/hda3 on / type ext3 (rw,noatime)
> > > none on /dev type devfs (rw)
> > > none on /proc type proc (rw)
> > > none on /dev/shm type tmpfs (rw)
> > >
> > Its been a while since I've done this but I remember feeling very
> > silly after making the same mistake..
> > From memory normal systems never mount your boot partition as a part
> > of the system startup, so after you've made the new kernel you need to
> > mount the boot partition then copy the kernel over the top of the old
> > one (make a copy of the old one first). There is a way of using
> > multiple kernels and just choosing the one you want at the grub boot
> > menu, but I've not done this before so ask around a bit.
> > If you re-read the last few steps in the gentoo install handbook it
> > should be a little clearer.
> >
> >
>
> The boot partition will be mounted on boot if it is listed in /etc/fstab.

I'm sorry, it will not be mounted at boot if it has the noauto option in
/etc/fstab. My mistake.

--
gentoo-user@gentoo.org mailing list
Re: Installing a new kernel [ In reply to ]
Bill Davidson wrote:
> make modules_install doesn't remove
> entries from your /lib/modules directory.

Are you absolutely sure?

--
gentoo-user@gentoo.org mailing list
Re: Installing a new kernel [ In reply to ]
On 21:47 Mon 13 Sep , Grant wrote:
> I've been suspicious that reconfiguring, recompiling, and reinstalling
> my kernel is not taking effect on my local machine, and I'm just
> booting to the old configuration. To test it, I removed agpgart
> support from the kernel configuration, recompiled it with "make dep &&
> make bzImage" and issued "make install", but dmesg still seems to load
> agpgart on boot up. I have also tried manually copying over the
> bzImage and System.map, but rebooting still seems to load agpgart
> judging by the dmesg output. I'm using grub, but I shouldn't need to
> reconfigure that since I'm using the same kernel right?

Was agpgart originally as a module? make modules_install doesn't remove
entries from your /lib/modules directory. It will only add them.

Bill

--
gentoo-user@gentoo.org mailing list
Re: Installing a new kernel [ In reply to ]
On 22:36 Mon 13 Sep , Norberto Bensa wrote:
> Bill Davidson wrote:
> > make modules_install doesn't remove
> > entries from your /lib/modules directory.
>
> Are you absolutely sure?

No. I was told that and it's wrong:( Sorry.

I looked at the Makefile and it removes the /lib/modules/version/kernel
directory and then it recreates it. Sorry about that.

Bill

--
gentoo-user@gentoo.org mailing list
Re: Installing a new kernel [ In reply to ]
> Its been a while since I've done this but I remember feeling very
> silly after making the same mistake..
> From memory normal systems never mount your boot partition as a part
> of the system startup, so after you've made the new kernel you need to
> mount the boot partition then copy the kernel over the top of the old
> one (make a copy of the old one first). There is a way of using
> multiple kernels and just choosing the one you want at the grub boot
> menu, but I've not done this before so ask around a bit.
> If you re-read the last few steps in the gentoo install handbook it
> should be a little clearer.

Thank you! I am able to install a new kernel now that I mount the
/boot partition before installing. A couple questions though:

Manually copying the bzImage works great after mounting /boot, but
make install never works for me. What could be the problem there?

Can I delete everything in /boot when /dev/hda1 is NOT mounted?

- Grant

--
gentoo-user@gentoo.org mailing list
Re: Installing a new kernel [ In reply to ]
On 14 Sep 2004, at 10:06, Grant wrote:
> Manually copying the bzImage works great after mounting /boot, but
> make install never works for me. What could be the problem there?

You have to write a kernel installer script yourself. Read the Makefile.
Re: Installing a new kernel [ In reply to ]
Bill Davidson wrote:
> I looked at the Makefile and it removes the /lib/modules/version/kernel
> directory and then it recreates it. Sorry about that.

Don't worry. I knew modules_install removed everything, but I also thought
something could had change since 2.4.x; then I looked into the Makefile :-)

Best regards,
Norberto

--
gentoo-user@gentoo.org mailing list
Re: Installing a new kernel [ In reply to ]
On Tue, 14 Sep 2004 17:06:00 +0000, Grant <emailgrant@gmail.com> wrote:

> Can I delete everything in /boot when /dev/hda1 is NOT mounted?

If you have a /boot partition, there should be nothing in /boot if the
/boot partition is not mounted. Yes, if the boot partition is not
mounted, you can delete anything in the /boot (the mountpoint) in the
/ partition. Just be damn sure that /boot is not mounted (use 'df')
before you try this.

HTH,

--
/\/\
(CR) Collins Richey
\/\/ "I hear you're single again." "Spouse 2.0 had fewer bugs than
Spouse 1.0, but the maintenance ... was too much for my OS."
- Glitch (tm)

--
gentoo-user@gentoo.org mailing list