Bug 15701 - weird mess in /boot after install
weird mess in /boot after install
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Michael Fulbright
Depends On:
  Show dependency treegraph
Reported: 2000-08-08 00:41 EDT by Michal Jaegermann
Modified: 2008-05-01 11:37 EDT (History)
0 users

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

Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2000-08-08 00:41:02 EDT
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 00:56:47 EDT
The via module does not work for you?
Comment 2 Erik Troan 2000-08-08 11:07:42 EDT
Fixed for RC1

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