Bug 33972 - problems upgrading to kernel 2.2.17-14 on smp machine using promise ide raid
Summary: problems upgrading to kernel 2.2.17-14 on smp machine using promise ide raid
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact: Brock Organ
Keywords: Security
Depends On:
TreeView+ depends on / blocked
Reported: 2001-03-29 23:06 UTC by Need Real Name
Modified: 2007-04-18 16:32 UTC (History)
0 users

Clone Of:
Last Closed: 2001-03-29 23:06:10 UTC

Attachments (Terms of Use)

Description Need Real Name 2001-03-29 23:06:06 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

when I try to initialize the ramdisk when upgrading the kernel. the system 
says no module ft for kernel-2.2.17-14***(tried single smp and enterprise) 
I installed the system using a driver disk I downloaded from promise, and 
it runs fine using the exsisting kernel. But I need to keep my kernel 
updated for security reasons. I am assuming the module ft is for the 
fasttrack controler. any ways to initialize the ramdisk getting around 
this module. I am on a smp machine and have availability to both driver 
disks (uniproc and smp)

Reproducible: Always
Steps to Reproduce:
1.mkinitrd /boot/initrd-2.2.17-14smp.img 2.2.17-14smp
2.or mkinitrd /boot/initrd-2.2.17-14.img 2.2.17-14
3.or mkinitrd /boot/initrd-2.2.17-14enterprise.img 2.2.17-14enterprise

Actual Results:  No module ft found for kernel 2.2.17-14smp

does the same thing on the other two statements using the coresponding 
kernel label

Expected Results:  initrd should have made the ramdisk
so I can finish upgrading my kernel

modules.conf has listed modules 

alias scsi_hostadapter ft
alias eth0 rtl8139
alias paraport_lowlevel paraport_pc
alias usb-controller usb-uhci

Comment 1 Arjan van de Ven 2001-03-29 23:08:42 UTC
The "ft" module is not open source and we therefore cannot support it.
We really would like to, but you have to ask Promise for support on this one,
not us.

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