Linux Kernel upgrade Post: 34921

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Linux Kernel upgrade Post 34921 by oombera on Friday 21st of March 2003 12:26:06 PM

03-21-2003

Registered User

I don't know anything about this, but I found a few similar situations on google. Here's a mailing list that had a few recommendations.

Quote:

[Tfug] Newbie question
Tue Jan 28 11:21:01 2003

Previous message: [Tfug] Newbie question
Next message: [Tfug] Another question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

--------------------------------------------------------------------------------

You may want to try an AA patch.

ftp://ftp.kernel.org:/pub/linux/kern....4.18rc4aa1.gz

From /home/scott/junk/linux/linux:
gunzip ../2.4.18rc4aa1.gz && patch -Np1 -i ../2.4.18rc4aa1

AA patch is a pretty comprehensive patch. Includes many of my favorite
patches including PTE and Himem. Even if it doesn't work. It's a
must-have patch.

Aside from that though, looks like you may have conflicts with your
kernel optimizations and the libc you are using. You could do a few
things in this case.

Copy include/linux to /usr/include or find out what your CFLAGS are at
compile time. Is Dev86 installed?

-Leo Przybylski

>Hello all,
>
>I am running Redhat 8.0 on my laptop using a 2.4.18 kernel. In the interest
>of learning more about Linux, I decided to compile my own Kernel. I downloaded
>2.4.20 from Kernel.org and did a "make xconfig" "make clean" "make depend"
>which went fine. When I got to 'make bzImage' I got the following error
>message:

Code:

>/home/scott/junk/linux/linux/include/asm/system.h:148:9: warning: multi-line
>str
>ing literals are deprecated
>timer.c:35: conflicting types for `xtime'
>/home/scott/junk/linux/linux/include/linux/sched.h:537: previous declaration
>of
>`xtime'
>make[2]: *** [timer.o] Error 1
>make[2]: Leaving directory `/home/scott/junk/linux/linux/kernel'
>make[1]: *** [first_rule] Error 2
>make[1]: Leaving directory `/home/scott/junk/linux/linux/kernel'
>make: *** [_dir_kernel] Error 2

>Of course it shut down after that. Could someone explain how I am getting
>a conflicting 'xtime' error.
>
>Also, all the books I am reading state that I need to softlink this to Lilo
>using Liloconfig. The problem is that I am using Grub2 for this computer
>so running liloconfig is not an option. There is no grubconfig that I can
>find but I only used the "whereis" and "which" command to try and find it.
>
>FYI: I am using grub2 not only to load different kernels but also to load
>Win2K if that makes a difference.
>
>Any suggestions??
>
>Scott

Last edited by oombera; 02-16-2004 at 02:33 PM..

oombera

View Public Profile for oombera

Find all posts by oombera

5 More Discussions You Might Find Interesting

1. Red Hat

How to upgrade kernel form 2.4 to 2.6

Hello, How to upgrade kernel from 2.4 to 2.6. Currently i am using rhel3 i want to upgrade it to 2.6 Please provide me the steps. Prashant

2. Red Hat

Kernel can not boot after upgrade on Fedora OS 15.

Hello, everyone. I am using Fedora 15, and want to upgrade to version 16. I follow the official link Upgrading Fedora using yum - FedoraProject to upgrade my OS by the following command: yum update kernel* --releasever=16 yum groupupdate Base --releasever=16 reboot After reboot, OS...

3. Hardware

kernel upgrade turn amd video graphics experience sluggish

Hi, I would like to ask related to video graphics driver specifically the AMD (radeon HD 7000 series) or had someone with the same experience or problem that im currently experiencing and willing to share some info. I understand that the kernel is self contain it will not affect the installed...

4. Solaris

LU upgrade for kernel

Hi Guys, I am getting into patching activity now a days. I had already done kernel upgrade through LU. My doubt is if i had to install 3 patches to get my system to current available patch level, can i directly patch one by one on an inactive LU and once done i can activate it later on or...

5. Red Hat

Kernel Upgrade

Dear All , I want upgrade my kernel version from kernel-2.6.18-164.el5 to kernel-2.6.18-199.el5. We have RED HAT Linux Server Red Hat Enterprise Linux Server release 5.4 (Tikanga). Kindly let me know where we can download this particular RPM. if we want to download from RHN , pl let...

LEARN ABOUT PLAN9

dh_systemd_start

DH_SYSTEMD_START(1)						     Debhelper						       DH_SYSTEMD_START(1)

NAME

       dh_systemd_start - start/stop/restart systemd unit files

SYNOPSIS

       dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]

DESCRIPTION

       dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
       sysv init script is available.

       As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
       which case it will only be restarted after the upgrade).  This logic is not used when there is a corresponding SysV init script because
       invoke-rc.d performs the stop/start/restart in that case.

OPTIONS

       --restart-after-upgrade
	   Do not stop the unit file until after the package upgrade has been completed.  This is the default behaviour in compat 10.

	   In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.

	   This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
	   will not get confused by the package being upgraded while it's running before using this option.

       --no-restart-after-upgrade
	   Undo a previous --restart-after-upgrade (or the default of compat 10).  If no other options are given, this will cause the service to
	   be stopped in the prerm script and started again in the postinst script.

       -r, --no-stop-on-upgrade, --no-restart-on-upgrade
	   Do not stop service on upgrade.

       --no-start
	   Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
	   corresponding init script).

NOTES

       Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
       Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.

       Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
       in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.

SEE ALSO

       debhelper(7)

AUTHORS

       pkg-systemd-maintainers@lists.alioth.debian.org

11.1.6ubuntu2							    2018-05-10						       DH_SYSTEMD_START(1)