Just one little word, (or phrase).... When I went to the download site for the new tape_3590 code, I saw the header for SLES9 with SP1 and a second file, which I didn't bother looking at assumming that it was S390X support code.
So, anyway, I have been downloading and trying to use the wrong code. The 145 code is for SP1 with security update (which I don't have). When I use the 139 code, everything works. I just assummed that the 145 code was a later release of the 3590 code, which is what I wanted. So I didn't pay much attention to having a 145 identifier when everything else said 139. But it is all up and running and my 3590 drives are working fine. lsmod doesn't show the 34xx drives either. Now to reboot to verify that the driver will be installed at startup time and/or to make changes to make sure it is installed at boot time. Thanks Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 06/06/05 11:16 AM >>> Just to check for sure: -. is the module there? find /lib/modules/<kernel> -name tape_3590.ko -ls There must be a module in the tree for your currently running kernel. - does it work after a 'depmod -a'? (Yes, the tape_34xx still gets forced in. Unfortunately you can't do that for the OCO part without annoying messages whenever it is not there.) Stefan SW Linux on zSeries Development & Services [EMAIL PROTECTED] ---------------------------------------------------------------------------------- When all other means of communication fail, try words. Tom Duerbusch <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 06.06.2005 17:56 Please respond to Linux on 390 Port To [email protected] cc Subject Re: tape_34xx Something doesn't seem right. I reboot, to start off with a clean slate. 'lsmod' shows no tape modules loaded 'modprobe tape_3590' 'lsmod' now show tape_34xx loaded. However, when I look at the resulting directory structure, I find: linux23:/sys/bus/ccw/drivers # dir total 0 drwxr-xr-x 7 root root 0 Jun 6 10:10 . drwxr-xr-x 4 root root 0 Jun 6 10:10 .. drwxr-xr-x 2 root root 0 Jun 6 10:10 3215 drwxr-xr-x 2 root root 0 Jun 6 10:10 3270 drwxr-xr-x 2 root root 0 Jun 6 10:10 dasd-eckd drwxr-xr-x 2 root root 0 Jun 6 10:10 dasd-fba drwxr-xr-x 2 root root 0 Jun 6 10:21 tape_34xx Jun 6 10:21 would be the right time frame, but I would have thought the resulting directory structure would have been "tape_3590" and not "tape_34xx". That, along with lsmod showing: linux23:/sys/bus/ccw/drivers # lsmod Module Size Used by tape_34xx 31236 0 tape 66328 1 tape_34xx tape_class 12548 1 tape And the chccwdev still fails to bring the device online: linux23:/sys/bus/ccw/devices/0.0.05b0 # chccwdev -e 0.0.05b0 Setting device 0.0.05b0 online Failed linux23:/sys/bus/ccw/devices/0.0.05b0 # I think I'm missing something else that needs to be done before the modprobe command is issued. Any suggestions? Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 06/06/05 3:53 AM >>> Yes, the way modules reference dependencies has been changed slightly. For 2.6 kernels you have to modprobe the discipline you want to use and the base modules will be automatically loaded. So if you want to use a 3590 tape device you have to: - modprobe tape_3590 (must be installed spearately but you mentioned doing so). - Set the device online (chccwdev -e <bus_id>). This will also reserve the tape unit for exclusive use by your host. - Now lstape should show the device online and you can access it via /dev/[rnb]tibm<x>. x is the tape numer that lstape shows. Tape numbers will be re-used so better check lstape output. - After using the tape you should set if offline (chccwdev -d <bus_id> so other hosts may access the device. Regards, Stefan SW Linux on zSeries Development & Services [EMAIL PROTECTED] ---------------------------------------------------------------------------------- When all other means of communication fail, try words. "Ledbetter, Scott E" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 06.06.2005 04:12 Please respond to Linux on 390 Port To [email protected] cc Subject Re: tape_34xx It just occurred to me that you need the OCO tape_3590 driver, not tape_34xx to talk to 3590 drives. I don't know if SuSE includes this, but you can download it here: http://awlinux1.alphaworks.ibm.com/developerworks/linux390/april2004_rec ommended.shtml I haven't used it, but it is also covered in the Device Drivers manual. Scott Ledbetter StorageTek -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Saturday, June 04, 2005 3:15 PM To: [email protected] Subject: Re: tape_34xx Thanks That didn't quite do it. Something else is needed. I rebooted Linux to get rid of my previous "tests". Then attached the drive to Linux. lsmod didn't show any tape modprobe tape_34xx which seemed to work lsmod now shows: > Module Size Used by > tape_34xx 31236 0 > tape 66328 1 tape_34xx > tape_class 12548 1 tape but I can't seem to bring the device online: > linux23:~ # chccwdev -e 0.0.5b0 > Setting device 0.0.05b0 online > Failed > linux23:~ # chccwdev -d 0.0.5b0 > Device already is offline > linux23:~ # chccwdev -e 0.0.5b0 > Setting device 0.0.05b0 online > Failed The console messages showed: "from the 'attach 5b0 linux23' command" > crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=1, erc=4, > rsid=B "from the modprobe command" > TAPE_CHAR: tape gets major 254 for character devices > TAPE_BLOCK: tape gets major 252 for block device > crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=1, erc=4, > rsid=B "from a detach and attach tape drive command" > crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=1, erc=4, > rsid=B Thanks for the pointer for the device driver manual. I'll look at it when I get back in my office. In my case these are IBM 3590B11 drives escon attached to z/VM 4.2 and operate in 3590 mode. Tom Duerbusch THD Consulting Ledbetter, Scott E wrote: > Here is what I have done to get tape_34xx to work with SLES9: > > modprobe tape_34xx > chccwdev -e 0.0.addr (where addr is the address of the drive) This > command puts the drive 'online' to Linux. The -d option takes it > 'offline' to Linux. > > You should see a message in the syslog displayed via the dmesg command > when the driver is loaded and the drive is online. You can look > through the /sys/bus/ccw/drivers/tape_34xx directory structure for > various information, but most if not all is displayed via the lstape > command. > > The Device Drivers manual for 2.6 has most of this info. I've been > using this on SLES 9 SP1 for about a month with no problems. I am > using 3490 mode drives. > > Scott Ledbetter > StorageTek > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Tom Duerbusch > Sent: Friday, June 03, 2005 4:27 PM > To: [email protected] > Subject: tape_34xx > > > All my mainframe tape documentation refers to tape390 and also, is > prior to SLES9 (which changed a lot of the I/O stuff with autodetect). > > Has there been any newer documentation published for 3590 tape drives > and SLES9 (udev support)? > > I see the presentation "exploiting udev in SLES9 and RHEL4", but it > doen't mention tapes. > > After doing the: > > rpm -Fvh s390_oco-2.6.5-7.145.s390.rpm > > looked like it worked. But I expected some documentation with it. > lsmod > shows: > > tape_34xx size 31236 used by 0 > tape size 66328 used by 1 tape_34xx > tape_class size 12548 used by 1 tape > > But anytime I try using it, it fails > > mt -f /dev/rtibm0 rewind > mt: /dev/rtibm0: No such device or address > > but a dir /dev/rt* shows: > > crw-r--r-- 1 root toot 254, 0 Jun 3 16:31 rtibm0 > > looks there to me. > > BTW where I have tape operational on SLES7 and SLES8, this is the > first attempt on SLES9 with SP1. > > Thanks for any pointers > > Tom Duerbusch > THD Consulting > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit http://www.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
