Re: 2 problems and 1 solution with modules (ncr53c8xx.o and loop.o)

["Jose M. Sanchez" <opjose ex-pressnet com>]

Hola Julian!

Check Redhat's site for updated Installation/Boot images...

I JUST received this announcement:

-JMS
opjose ex-pressnet com

--------------- CUT -------------------
New installation images that correct several Red Hat Linux 6.0
installation problems are now available.  The following problems
are solved by this release:

   o  ICP Vortex RAID controller driver module missing (bug #2535)
   o  VIA-Rhine ethernet card driver module missing (bug #2830)
   o  Kickstart installs recrypts passwords even if "--iscrypted"
      is given (bug #2460)
   o  SPARC/UltraSPARC serial installs (bug #2602)
   o  Problems obtaining complete DHCP replies from Windows NT DHCP servers
   o  Foreign language installs using the hard drive install method
   o  Hard drive installs from partitions that will be mounted in
      the installed system

New features in this boot release:

   o  Expert mode gives the opportunity to select a SMP kernel (bug #2253)
   o  Added a "smp" option to kickstart to allow manual specification
      of SMP capable motherboards

Problems that will be addressed in a future image release:

   o  Adaptec SCSI negotiation infinite loops
   o  AMD MegaRAID driver updates to support newer cards
   o  Installation from various parallel port devices including Backpack
      CD-Roms (bug #2701)

Instructions for use
====================

Intel
-----

ftp://ftp.redhat.com/pub/redhat/updates/6.0/images/i386/boot.img
ftp://ftp.redhat.com/pub/redhat/updates/6.0/images/i386/bootnet.img
ftp://ftp.redhat.com/pub/redhat/updates/6.0/images/i386/supp.img
ftp://ftp.redhat.com/pub/redhat/updates/6.0/images/i386/modules.img

Three disks are needed for Intel based computers: "boot.img" or
"bootnet.img", "supp.img", and "modules.img".  Choose "boot.img" for
local installs (CD-Rom, hard drive) or "bootnet.img" for network
installs (NFS, FTP, HTTP).  Copy the three images to 1.44 MB floopy
disks using "dd if=file.img of=/dev/fd0 bs=72k" under Linux or
"rawrite.exe" under DOS or Windows.

After preparing the disk images, insert the appropriate boot disk and
boot the computer.  At the boot prompt type "linux supp" and press
Enter.  This tells the installer to load changes from the supplimental
and modules disks.  The installer will prompt the user to insert the
supplemental disk and modules disk during the installation process.


Alpha
-----

ftp://ftp.redhat.com/pub/redhat/updates/6.0/images/alpha/ramdisk.img

Copy "ramdisk.img" to a floppy disk using "dd" or "rawrite.exe" then
proceed with the instructions in the installation guide.


SPARC/UltraSPARC
----------------

ftp://ftp.redhat.com/pub/redhat/updates/6.0/images/sparc/ramdisk.img
ftp://ftp.redhat.com/pub/redhat/updates/6.0/images/sparc/tftp32.img
ftp://ftp.redhat.com/pub/redhat/updates/6.0/images/sparc/tftp64.img

If booting from floppy copy "ramdisk.img" image to a floppy disk using
"dd" or "rawrite.exe", then proceed with the instructions in the
installation guide.

If booting from the network using TFTP, choose the appropriate boot
image.  Use "tftp32.img" for SPARC based computers or "tftp64.img" for
UltraSPARC based computers.  Copy the image to the proper place on the
tftp server then proceed with the instructions in the installation
guide.

----- Original Message -----
From: Julian Esteves <julian kerbero sapnet com mx>
To: RedHat Instal list <redhat-install-list redhat com>
Sent: Friday, May 28, 1999 3:56 PM
Subject: 2 problems and 1 solution with modules (ncr53c8xx.o and loop.o)


> Hi all,
>
> We're trying to install RedHat 6.0 from scratch (I mean: not upgrading
> from 5.2) in one of our servers.  We're performing the installation via
> FTP (with the more recent images, since there aren't updates in
> updates.redhat.com).
>
> Our first problem was that the installation program in RedHat 6.0 (we
> don't see the problem if we boot with the RedHat 5.2 CD!) couldn't detect
> properly the devices attached to a SCSI card controlled by a NCR53c8xx.
> During the installation process a message saying that 'insmod' failed for
> module /modules/ncr53c8xx can be seen.
>
> If (in console 2) is issued the command
>  # insmod /modules/ncr53c8xx.o
> the more detailed error message
>  /tmp/ncr53c8xx.o: kernel-module version mismatch
>    /tmp/ncr53c8xx.o was compiled for kernel version 2.2.5-14BOOT
>    while this kernel is version 2.2.5-4BOOT
> is seen.
>
> We finally went around this problem issuing the command
>  # insmod /modules/ncr53c8xx.o -f
> just before partition our SCSI hard disks not without the complain:
>  Warning: /tmp/ncr53c8xx.o: kernel-module version mismatch
>    /tmp/ncr53c8xx.o was compiled for kernel version 2.2.5-14BOOT
>    while this kernel is version 2.2.5-4BOOT
>
> Only then we were able to set our file systems and to install the packages
> we needed.
>
> After that, the other (similar and no yet solved) problem arose: when we
> were trying to make the bootdisk (and later, when trying to install LILO)
> we found that 'insmod' had failed again, this time on /modules/loop.o. We
> tried a
>  # insmod /modules/loop.o -f
> as before, but it didn't work. This time the error message reads:
>  Warning: /tmp/ncr53c8xx.o: kernel-module version mismatch
>    /tmp/ncr53c8xx.o was compiled for kernel version 2.2.5-15
>    while this kernel is version 2.2.5-4BOOT
>
>  /tmp/loop.o: unresolved symbol end_that_request_first_Rbcb2fdc8
>  /tmp/loop.o: unresolved symbol end_that_request_last_R46f71e93
>
> So, if you can drop any idea of why is this happening and (of course) how
> can we go around it, we'll appreciate very much to hear it.
>
>  Thanks in advance,
>           Juli\'an
>
>
> --
>   PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com http://archive.redhat.com
>          To unsubscribe: mail redhat-install-list-request redhat com with
>                        "unsubscribe" as the Subject.
>