[prev in list] [next in list] [prev in thread] [next in thread] 

List:       suse-sparc
Subject:    RE: [suse-sparc] Suse 7.1 on Sun Enterprise 3500
From:       "Michael Asher" <michael_asher () colonialbank ! com>
Date:       2001-04-27 16:44:04
[Download RAW message or body]

Here is the output from dmesg:

	socal.c: SOC+ driver v1.1.9/Feb/99 Jakub Jelinek (jj@ultra.linux.cz)
	socal0 port B: ONLINE
	FCAL: Total of 1 Sun Enterprise Network Array (A5000 or EX500) channels
found
	scsi2 : Fibre Channel Arbitrated Loop
	scsi : 3hosts


Here is the /proc/scsi/fcal/2 information:

	Sun Enterprise Network Array (A5000 or E?500) on socal0 B PRPM node
f00e48bc
	Initiator AL-PA:	01

	Attached devices: none
		[AL-PA: e8] Not responded to PLOGI
		[AL-PA: ef] Not responded to PLOGI

Here is /proc/partitions

	major minor #blockes name

Any ideas on where to go from here?

-Michael


-----Original Message-----
From: Thorsten Kukuk [mailto:kukuk@suse.de]
Sent: Friday, April 27, 2001 1:12 AM
To: Michael Asher
Cc: suse-sparc@suse.com
Subject: Re: [suse-sparc] Suse 7.1 on Sun Enterprise 3500


On Thu, Apr 26, Michael Asher wrote:

> I was able to get the fc4 and socal modules loaded. However it doesn't
find
> my drives. Is there a way to get these modules loaded at boot time and
then
> try the hw detect similar to what can be done with lilo? (linux
> hde=ide-scsi, etc?)

I'm not sure, when YaST makes his hw detection, but it should have
now problems. What does dmesg say after you include the modules ?
Does it find your harddisks ? Which devices are used ?
What does cat /proc/partitions say ?

I don't know about a FAQ for this hardware.

  Thorsten

--
Thorsten Kukuk       http://www.suse.de/~kukuk/        kukuk@suse.de
SuSE GmbH            Schanzaeckerstr. 10             90443 Nuernberg
--------------------------------------------------------------------
Key fingerprint = A368 676B 5E1B 3E46 CFCE  2D97 F8FD 4E23 56C6 FB4B


[prev in list] [next in list] [prev in thread] [next in thread]