Mark, That is correct. I just tried it and when I rebooted the TAPE_ statements are gone from the end of dmesg and /proc/tapedevices is not there. I am not sure how but I am pretty sure that I rebooted and I still had TAPE_CHAR and TAPE_BLOCK. It may have been before I was using the chccwdev command and used the mknod command that was causing them to remain.
Also, I tried running mkinitrd and zipl, but I still have to run modprobe and chccwdev after a reboot. Any idea why? Thanks, Ryan Stewart Indian River Community College -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Saturday, February 03, 2007 6:13 PM To: [email protected] Subject: Re: Linux and 3490 tapes Hmm. I would have thought that after restarting your system, you would have to reissue the modprobe command, as well as the chccwdev command. Unless you re-ran mkinitrd and zipl after the modprobe. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Ryan Stewart Sent: Thursday, February 01, 2007 8:34 AM To: [email protected] Subject: Linux and 3490 tapes Good Morning, I have a question about getting Linux to recognize 3490 tape drives. I have read a lot of the previous posts that I could find on the issue and have gotten somewhere but I think that I may be stuck. Here is what I have so far: 1. I added the mt-st package. 2. I dedicated the tape drive to the Linux guest. 3. I used modprobe tape_34xx and this gets Linux to recognize the drive but not to the extent I thought it would. a. dmesg shows: TAPE_CHAR: tape gets major 254 for character devices TAPE_BLOCK: tape gets major 252 for block device TAPE_CORE: tape device 0.0.0181 found (at this point I thought I was getting somewhere) ....but if I do not logoff and log back on when shutting down and restarting the TAPE_CORE line is gone from dmesg and although now I have a /proc/tapedevices file, there are no entries. 4. I use mknod: mknod /dev/ntibm0 c 254 0 mknod /dev/rtibm0 c 254 1 ..still no entry in /proc/tapedevices. 5. using mt -f /dev/ntibm0 status I get mt: /dev/rtibm0: No such device or address -snip- ---------------------------------------------------------------------- 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
