Royce, I'm not sure what's happening to your posts. I see them on the archive, but they're not showing up in my email. Oh well...
Your problem is that the tape driver is built as a module, and not compiled into the kernel. As such, the driver will not get loaded unless an explicit insmod/modprobe command gets issued, or the device is referenced in a command, and there is an entry in /etc/modules.conf aliasing the module name to that device. For example: alias ntibm0 tape alias rtibm0 tape You can "fix" this problem by recompiling your kernel with the driver selected to be compiled in, and not as a module. But, in this case I don't know that that is worth your time, unless you want to use it as a learning exercise. Mark Post -----Original Message----- From: Royce Wolf <[EMAIL PROTECTED]> Sent: Tue, 11 Jun 2002 18:06:11 -0400 To: Linux on 390 Port <[EMAIL PROTECTED]> Subject: SuSE Kernel 2.4.7 Tapes SuSE L/390 SLES7 (31 bint) running under VM 2.4.0. I have the following parameters line in the /etc/zipl.conf file, but the = attached tape drive is not recognized at boot time. parameters=3D"dasd=3D0290,0300-324 tape=3D181-182 dasd_force_diag=3D290,300= -324 root=3D/dev/dasda1 noinitrd" The command: insmod tape=3D181-182 does work to load the driver and find the drive. /var/log/boot.msg shows: Kernel command line: dasd=3D0290,0300-324 tape=3D181-182 dasd_force_diag=3D= 290,300-324 root=3D/dev/dasda1 noinitrd Why doesn't the kernel respond to the tape definition in the parmfile?
