Royce, Device detection is only done automatically at system startup time. If you want to dynamically add devices to a 2.4 system later, you either have to tell the chandev layer to reprobe for devices, or tell it specifically what you want to add. According to the "Device Drivers and Installation Commands" manual on IBM's DeveloperWorks web site, tape devices are not supported by chandev, so it sounds like to need to make sure your tape drives are attached when you boot your Linux system. You can find the manual that talks about this at http://www10.software.ibm.com/developerworks/opensource/linux390/docu/l390dd 08.pdf You'll want to look at Chapter 1, "Common device support" and Chapter 8, "Linux for zSeries Channel device layer."
Mark Post -----Original Message----- From: Royce Wolf [mailto:[EMAIL PROTECTED]] Sent: Friday, June 28, 2002 5:43 PM To: [EMAIL PROTECTED] Subject: Re: SuSE Kernel 2.4.7 Tapes I have more, refined information about this problem I'm having. 1. If the tape drive is attached before boot time, and a subsequent modprobe tape390 command is issued, I see the following result: 1. the file /proc/tapedevices is created 2. in the tapedevices file the attached drive is listed 3. I can successfully issue an mt command to the tape drive 2. If the tape drive is attached after boot time, and a subsequent modprobe tape390 command is issued, I see the following results: 1. the file /proc/tapedevices is created 2. in the tapedevices file NO tape drives are listed 3. the mt command fails Any clues...anybody?
