Bug 81788 - Kernel install issues
Summary: Kernel install issues
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel
Version: 1.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-01-14 00:25 UTC by Need Real Name
Modified: 2007-04-18 16:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-01-14 16:53:26 UTC


Attachments (Terms of Use)

Description Need Real Name 2003-01-14 00:25:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
2.4.20-2.13 fails to install cleanly from the kernel-2.4.20-2.13.i686.rpm or the
kernel-source-2.4.20-2.13.i386.rpm:

[root@f1j 2.4.20-2.13]# rpm -Uvh kernel-*
Preparing...                ########################################### [100%]
   1:kernel-source          ########################################### [ 50%]
   2:kernel                 ########################################### [100%]
depmod: *** Unresolved symbols in
/lib/modules/2.4.20-2.13/kernel/arch/i386/oprofile/oprofile.o.gz
depmod:         cpu_possible
depmod: *** Unresolved symbols in
/lib/modules/2.4.20-2.13/kernel/drivers/net/wireless/orinoco_pci.o.gz
depmod:         orinoco_proc_dev_cleanup
depmod:         orinoco_proc_dev_init
depmod: *** Unresolved symbols in
/lib/modules/2.4.20-2.13/kernel/drivers/net/wireless/orinoco_plx.o.gz
depmod:         orinoco_proc_dev_cleanup
depmod:         orinoco_proc_dev_init


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install the kernel and source
2.
3.
    

Actual Results:  The above description tells all.

Expected Results:  No unresolved symbols

Additional info:

Comment 1 Need Real Name 2003-01-14 16:53:26 UTC
2.4.20-2.15 fixes the unresolved symbols issues


Note You need to log in before you can comment on or make changes to this bug.