On Wed, 4 Jun 2003, Dave Myers wrote: > Well our ramacs are not working. > There is no dasd or 3990 info in /proc/subchannels after the dasd is > loaded from yast.
The contents of /proc/subchannels should not change unless something to the hardware I/O changes, there should be also no 3990 info then before you start yast, e.g. when you select "No network" at the first menu. As long there is no line containing the dasd device and control unit type in /proc/subchannels, no rmmod, modprobes, no dasd driver, no yast, no mkmod can change anything, the dasd driver is given nothing by the I/O subsystem which it could handle, thus the status "unknown". This is a more lower level issue then. I say S/390 I/O Subsystem - Hardware, cabling, online/offline, IOCDs, Microcode, or Linux S/390 lowlevel I/O code, specifically the subchannel scanning executed at IPL. You could add "cio_msg=yes" to the kernel parameters when IPLing it for installation and look for the early S/390 HW detection messages then: "Detected device ... on subchannel .... PIM ... PAM ... POM ..." (these and around there) Bernd Kaindl > /proc/dasd/devices shows the 3380 with an "unknown status". > No insmods, rmmods modprobes etc. change that symptom. > mknod comes back with a message indicating that the 94:0 is already > registered..but the linux console messages say otherwise!! > > > I am wondering if 3990-13 might be the problem??? > Do you use mod 13 controllers on your ramac?? > > > Dave Myers > Denver Solutions Group > Senior Systems Engineer > Office Phone: (303) 996-7112 > Cellular Phone: (303) 619-0782 > Home Office: (303) 948-0027 > Fax: (303) 706.1713 > e-mail: [EMAIL PROTECTED] > > > > > Tom Duerbusch > <[EMAIL PROTECTED] To: [EMAIL PROTECTED] > scity.com> cc: > Sent by: Linux on Subject: Re: SLES8 dasdfmt problem > 390 Port > <[EMAIL PROTECTED] > ST.EDU> > > > 06/04/2003 08:33 > AM > Please respond to > Linux on 390 Port > > > > > > > Don't worry about the Ramacs. I have Suse 8 loaded on both 3380 and > 3390 Ramac Dasd Subsystems, as well as MP3000 internal dasd. > > I haven't had to add disk. Mine were added durning installation. > > I assume that you went to the Suse website. There is a paper on adding > S390 dasd to a running Linux system. That worked for me when I added > dasd to Linux 7. > > Tom Duerbusch > THD Consulting > > >
