SCIENTIFIC-LINUX-USERS Archives

March 2006

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Bly, MJ (Martin)" <[log in to unmask]>
Reply To:
Bly, MJ (Martin)
Date:
Wed, 1 Mar 2006 08:44:53 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (112 lines)
Hi,

Surely the key is this: from your lspci:

00:0d.0 SCSI storage controller: Initio Corporation 360P (rev 02)
	Subsystem: Unknown device 9292:0202
                               ^^^^^^^^^^

	Flags: bus master, medium devsel, latency 32, IRQ 11
	I/O ports at c800 [size=256]
	Memory at d9001000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at <unassigned> [disabled] [size=32K]
 
And Connie's list of 'known devices':

1101  Initio Corporation
        1060  INI-A100U2W
        9100  INI-9100/9100W
        9400  INI-940
        9401  INI-950
        9500  360P
        9502  Initio INI-9100UW Ultra Wide SCSI Controller INIC-950P
chip

Basically, the driver doesn't recognise your card even though it *may*
support it because the device id number is not known.  You would have to
munge the pcitable file in the install image to allow it to associate
the driver with the device automagically.  Even then there is no
guarantee the driver will actually work...

The other problem can be this: the driver module must match exactly the
kernel in use for the boot install - if it doesn't it won't load.  I've
been down that track with device drivers before and it's a big source of
bruises to the forehead.

'Lspci -n' should tell you exactly what device id number the controller
card is - they you can check if the driver supports it and try munging
the pcitable file.

Martin. 


> -----Original Message-----
> From: [log in to unmask] 
> [mailto:[log in to unmask]] On 
> Behalf Of Dushan Mitrovich
> Sent: 01 March 2006 07:00
> To: [log in to unmask]
> Cc: [log in to unmask]
> Subject: Re: can't install SL 4.2 - no CD-ROM driver
> 
> Ioannis Vranos <[log in to unmask]> wrote:
> >> It's a Plextor PX-32TS, and it's working fine with OS/2.
> >
> > May you send the exact error message and text that is displayed?
> 
> Here are the steps I tried and messages I got.  I won't 
> describe them all
> because they all lead to the same problem, of being unable to 
> satisfy the
> installer's request for a scsi device driver.
> 
> 1 - Started computer with CD#1 in the drive, and at the first 
> Linux screen
>     was presented with 4 choices.  I hit [F2] for options, 
> which gave me
> 
> 2 - the 2nd screen with several options;  I typed in 'linux 
> noprobe dd' and
> 
> 3 - got a blue screen with a gray message box asking 'Do you 
> have a driver
>     disc?'
> 
> 4 - If I answer 'Yes', a message asks me to choose the device 
> on which the
>     driver will be found.  Regardless whether I choose 'fd0' 
> (on which I'd
>     copied the Initio scsi adapter driver) or 'hdb' (the hard 
> disk with the
>     existing RedHat 7.2 on it), a message box tells me either
>     (a) 'Insert the driver disk into /dev/fd0' and press "OK" 
> to continue'
>         - and the box re-appears over and over without seeing 
> any driver,
>  or (b) after navigating on 'hdb' to 
> /usr/arc/linux-2.4.7-10/drivers/scsi
>         and picking any of the five related driver files for 
> the Initio
>         scsi adapter:   ini9100u.c      ini9100u.h      ini9100u.o
>                         ini9100u.o.flags                initio.o ,
>         the message said the driver 'failed to load'
> 
> 4a- If I answer 'No', I get the 'Choose a Language' screen, 
> etc., up to
>     the 'Installation Method' screen.  There I choose 'From 
> CD-ROM' and get
>     the message 'No driver found' and two choices: 'Select a 
> driver' and
>     'Use a driver disk'.  In the first case no Initio adapter 
> drivers are
>     listed, and in the second it reverts to the same problem 
> as described
>     above.
> 
> When the installer asks for a driver disk, I guess I don't 
> know what exact-
> ly what it's looking for, which files.
> 
> - Dushan
> 

ATOM RSS1 RSS2