RE: A SCSI problem

From: Mike Westkamper (mjwestkamper_at_weiinc.com)
Date: 01/23/04

  • Next message: Ben Stringer: "Re: gnome settings" 
    To: <fedora-list@redhat.com>
Date: Fri, 23 Jan 2004 09:31:16 -0500

    I seemingly am unable to make this work at boot time.
    I believe I followed Alexanders instructions correctly, however the system
    still does not find the adapter nor mount the drives at boot time.

    Furthermore, I cannot mount the drives after I do a manual modprobe aix*.
    fdisk list all 8 drives correctly after the modproble, however a number of
    attempts to mount them fail.
    The drives were configured as a softraid by RedHat Linux 7.2.

    I copied the raidtab from the 7.2 version and updated the fstab to the
    Fedora version and it still does not seem to work.

    Thanks in advance for any direction...

    Mike

    -----Original Message-----
    From: fedora-list-admin@redhat.com
    [mailto:fedora-list-admin@redhat.com]On Behalf Of Alexander Dalloz
    Sent: Thursday, January 22, 2004 1:24 AM
    To: fedora-list@redhat.com
    Subject: RE: A SCSI problem

    Am Do, den 22.01.2004 schrieb Mike Westkamper um 00:22:
    > An update, some progress,
    >
    > On a lark I did a modprobe for aic7770
    > It listed the controller and attached drives.

    You probably mean the aic7xxx.o kernel module. A module with name
    aic7770.o is not known on my FC1. I even never heard of a SCSI module by
    that name.

    > Hmmmm

    If you type in as root "modinfo aic7xxx" you will get some information
    about optional module parameters you can pass when loading the module.
    Maybe even the example line for EISA/VLB system is interesting for you

    > How do I make this work routinely? And how can I tell if it loaded the new
    > sequencer code?

    Load the module and create a new ram disk using command mkinitrd.
    "mkinitrd --help" will show you how to use the command. Move the newly
    created initrd.img file to /boot and be sure it is called in
    /etc/grub.conf. Edit the /etc/modules.conf with a line

    alias scsi_hostadapter aic7xxx

    maybe followed by a line like

    options aic7xxx 'aic7xxx=probe_eisa_vl.tag_info:{{}.{.10}}.seltime:1'

    whatever parameters you are passing to the module.

    > To me this is mindless hacking extraordinaire. I have no idea why it
    worked
    > nor where to go from here.
    >
    > Mike

    HTH

    Alexander 

    --
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416  14CD E197 6E88 ED69 5653
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Ben Stringer: "Re: gnome settings"

    Relevant Pages

    • RE: A SCSI problem
      ... > still does not find the adapter nor mount the drives at boot time. ... You made a ramdisk initrd.img which contains the scsi module? ... Looking for deps of module scsi_mod ... Alexander Dalloz | Enger, Germany ...
      (Fedora)
    • Re: mpt problems. (Re: Dell hardware raid 0 (sas5ir) or gmirror?)
      ... The error messages from mpt are attached in the file called 'messages'. ... The kernel probe boot time log is attached as dmesg.log. ... at boot time both drives report that they have 255 tag ... drives to anything 120 or above the drive controller complains under ...
      (freebsd-stable)
    • Execute program upon cd insertion
      ... react to Audio CD insertion. ... executed each time a CD is inserted into each of the drives. ... seem to be invoked only at boot time and never when I insert a CD after ...
      (alt.os.linux.suse)
    • Re: Unusual slow star-up - advice requested.
      ... minutes to your boot time. ... Adobe products loading on system start-up and to a lesser extent the ... diagnosis is correct by installing Autoruns and disabling (not ... mirrored pair of 250 Gb Sata II drives. ...
      (microsoft.public.windowsxp.perform_maintain)
    • Re: Drive errors on boot
      ... Other similar drives dont error and are setup the same ... failed to force tx and rx to idle state ... The driver tried to force the transmitter and receiver to be "idle" ... happens at boot time, whether it happens after an underrun or overrun, ...
      (freebsd-questions)