Bug 118000 - mkinitrd and sata_via problem when upgrading to 2.6.3
mkinitrd and sata_via problem when upgrading to 2.6.3
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: mkinitrd (Show other bugs)
1
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-03-10 17:24 EST by Piotrek
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-04-14 23:09:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Piotrek 2004-03-10 17:24:53 EST
When upgrading from standard Fedora Core 1 for AMD64 to kernel 2.6.3 
on machine with via 8237 chipset (sata) 'make install' says:
sh /usr/src/linux-2.6.3/arch/x86_64/boot/install.sh 2.6.3 
arch/x86_64/boot/bzImage System.map ""
No module sata_via found for kernel 2.6.3, aborting.
mkinitrd failed
make[1]: *** [install] Error 1
make: *** [install] Error 2
No mather if the module is compiled into the kernel. 

Adding sata_via module to PRESCSIMODS in mkinitrd script solved the 
problem:
PRESCSIMODS="scsi_mod sd_mod unknown sata_via"
Comment 1 Jeremy Katz 2004-03-10 17:53:28 EST
Did you build sata_via as a module?
Comment 2 Piotrek 2004-03-10 18:11:23 EST
No, i tried to build it into the kernel, so it was really strange 
that mkinitrd was looking for a module. The same thing happend with 
raid0 (also build into the kernel). After adding this 2 modules to 
PRESCSIMODS in mkinitrd i managed to build and install everything (of 
course raid0 and sata_via where compiled into the kernel) and it 
works fine. 
Comment 3 Jeremy Katz 2004-04-14 23:09:20 EDT
mkinitrd assumes that all of the modules in /etc/mod{ules,probe}.conf
are built as a module for your kernel.  If you're not doing this, then
--omit-scsi-mods is the workaround to use.

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