Bug 15701 - weird mess in /boot after install
Summary: weird mess in /boot after install
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-08-08 04:41 UTC by Michal Jaegermann
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-08-08 15:07:44 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Michal Jaegermann 2000-08-08 04:41:02 UTC
After installation of "everything" one ends up in /boot with
both "regular" and "enterprise" kernels, but:
  a) /boot/module-info is a link pointing towards a non-existent file
  b) there is no 'initrd' which corresponds to "enterprise" kernel
     so this one is unbootable without runnnig 'mkinitrd' first
     (at least when one boots from a SCSI disk)
  c) what needs over 3 Megs of uncompressed kernels in /boot
     while exactly the same information is contained in gzipped
     "vmlinuz" kernels also in the same location; the later are
     really used
  d) AC97 VIA soundcard does not work with any of those kernels
     and their modules (but this is another story and yes, the card
     does work with Linux and Mandrake 7.0 supports it "straight out
     of the box").


Comment 1 Bill Nottingham 2000-08-08 04:56:47 UTC
The via module does not work for you?

Comment 2 Erik Troan 2000-08-08 15:07:42 UTC
Fixed for RC1

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