Sponsored Content
Full Discussion: Linux Kernel upgrade
Top Forums UNIX for Dummies Questions & Answers Linux Kernel upgrade Post 34921 by oombera on Friday 21st of March 2003 12:26:06 PM
Old 03-21-2003
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..
 

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 (1 Reply)
Discussion started by: prashant_ohol
1 Replies

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... (2 Replies)
Discussion started by: 915086731
2 Replies

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... (3 Replies)
Discussion started by: jao_madn
3 Replies

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... (3 Replies)
Discussion started by: Rockyc3400
3 Replies

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... (0 Replies)
Discussion started by: jegaraman
0 Replies
pki-upgrade(8)							 PKI Upgrade Tool						    pki-upgrade(8)

NAME
pki-upgrade - Tool for upgrading system-wide configuration for Certificate System. SYNOPSIS
pki-upgrade [OPTIONS] DESCRIPTION
There are two parts to upgrading Certificate System: upgrading the system configuration files used by both the client and the server pro- cesses and upgrading the server configuration files. When upgrading Certificate System, the existing system configuration files (e.g. /etc/pki/pki.conf) may need to be upgraded because the content may have changed from one version to another. The configuration upgrade is executed automatically during RPM upgrade. However, in case there is a problem, the process can also be run manually using pki-upgrade. The system upgrade process is done incrementally using upgrade scriptlets. The upgrade process and scriptlet execution is monitored in upgrade trackers. A counter shows the latest index number for the most recently executed scriptlet; when all scriptlets have run, the com- ponent tracker shows the updated version number. The scriptlets are stored in the upgrade directory: /usr/share/pki/upgrade/<version>/<index>-<name> The version is the system version to be upgraded. The index is the script execution order. The name is the scriptlet name. During upgrade, the scriptlets will back up all changes to the filesystem into the following folder: /var/log/pki/upgrade/<version>/<index> The version and index values indicate the scriptlet being executed. A copy of the files and folders that are being modified or removed will be stored in oldfiles. The names of the newly-added files and folders will be stored in newfiles. The system upgrade process is tracked using this file: /etc/pki/pki.version The file stores the current configuration version and the last successful scriptlet index. OPTIONS
General options --silent Upgrade in silent mode. --status Show upgrade status only without performing the upgrade. --revert Revert the last version. -X Show advanced options. -v, --verbose Run in verbose mode. -h, --help Show this help message. Advanced options The advanced options circumvent the normal component tracking process by changing the scriptlet order or changing the tracker information. WARNING: These options may render the system unusable. --scriptlet-version <version> Run scriptlets for a specific version only. --scriptlet-index <index> Run a specific scriptlet only. --remove-tracker Remove the tracker. --reset-tracker Reset the tracker to match the package version. --set-tracker <version> Set the tracker to a specific version. OPERATIONS
Interactive mode By default, pki-upgrade will run interactively. It will ask for a confirmation before executing each scriptlet. % pki-upgrade If there is an error, it will stop and show the error. Silent mode The upgrade process can also be done silently without user interaction: % pki-upgrade --silent If there is an error, it will stop and show the error. Checking upgrade status It is possible to check the status of a running upgrade process. % pki-upgrade --status Troubleshooting If there is an error, rerun the upgrade in verbose mode: % pki-upgrade --verbose Check the scriptlet to see which operations are being executed. Once the error is identified and corrected, the upgrade can be resumed by re-running pki-upgrade. It is possible to rerun a failed script by itself, specifying the instance and subsystem, version, and scriptlet index: % pki-upgrade --scriptlet-version 10.0.1 --scriptlet-index 1 Reverting an upgrade If necessary, the upgrade can be reverted: % pki-upgrade --revert Files and folders that were created by the scriptlet will be removed. Files and folders that were modified or removed by the scriptlet will be restored. FILES
/usr/sbin/pki-upgrade AUTHORS
Ade Lee <alee@redhat.com>, Ella Deon Lackey <dlackey@redhat.com>, and Endi Dewata <edewata@redhat.com>. pki-upgrade was written by the Dogtag project. COPYRIGHT
Copyright (c) 2013 Red Hat, Inc. This is licensed under the GNU General Public License, version 2 (GPLv2). A copy of this license is avail- able at http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt. version 1.0 Jul 22, 2013 pki-upgrade(8)
All times are GMT -4. The time now is 03:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy