Yes, i have one.
Must be
insmod tape390 tape=290
T390:IBM S/390 Tape Device Driver (v1.01).
kernel: T390:(C) IBM Deutschland Entwicklung GmbH, 2000
kernel: T390:character device frontend : built in
kernel: T390:block device frontend : built in
kernel: T390:support for 3480 compatible : built in
kernel: T390:support for 3490 compatible : built in
kernel: T390:Using ranges supplied in parameters, disabling autoprobe mode.
kernel: T390:using devno 0290 with discipline 3480 on irq 176 as tape
device 0 !!!!!!!!!!
kernel: TCHAR:<3> tape gets major 254 for character device
kernel: TBLOCK:<3> tape gets major 254 for block device
Your system didn't find any tapes.
May be, try to detach/attach tapes in VM. I had problem like this.
WBR, Sergey
"Wolfe, Gordon W"
<gordon.w.wolfe@b To: [EMAIL PROTECTED]
oeing.com> cc:
Sent by: Linux on Subject: Re: ipl tape
390 Port
<[EMAIL PROTECTED]
IST.EDU>
13.03.02 23:55
Please respond to
Linux on 390 Port
I decided to use this as a basis for experimenting with tapes since we
haven't got to that yet. Using SuSE SLES7, I had a running system.
>From another VM userid on the same system,
VMTAPE MOUNT SCRATCH DSN Linux.tape.test ( retpd 5 label nl
CP GIVE 181 to LINUXSRV 181
Then, from root on the linux machine
insmod tape390 tape=181 Using
/lib/modules/2.4.7-SuSE-SMP/kernel/drivers/s390/char/tape390.o
>From the 3270 console of the server, I see
T390:IBM S/390 Tape Device Driver (v1.01).
T390:(C) IBM Deutschland Entwicklung GmbH, 2000
T390:character device frontend : built in
T390:block device frontend : built in
T390:support for 3480 compatible : built in
T390:support for 3490 compatible : built in
T390:Using ranges supplied in parameters, disabling autoprobe mode.
TCHAR:<3> tape gets major 254 for character device
TBLOCK:<3> tape gets major 254 for block device cd /devmknod ntibm1
c 254 1 (Confirmed /dev/ntibm1 really is there)cd
/hometar -cvf /dev/ntibm1 ./patchestar: /dev/ntibm1: Cannot open: No
such devicetar: Error is not recoverable: exiting
nowroot@linuxsrv-/home # (no additional messages on
the console)
Obviously, I'm doing something wrong. Any idea what?
"You do not need a parachute to skydive. You only need a parachute to
skydive twice." -Motto of the Darwin Society
Gordon W. Wolfe, Ph.D. (425) 865-5940
VM Technical Services, The Boeing Company
> ----------
> From: Sergey Korzhevsky
> Reply To: Linux on 390 Port
> Sent: Wednesday, March 13, 2002 5:58 AM
> To: [EMAIL PROTECTED]
> Subject: I made it (Was: ipl tape)
>
>
> 12.03.2002 15:29:24 Linux on 390 Port ???????(?):
>
> Hello Jim!
>
> You are almost right. I look at source code and found, that
>
> minor number 0 for rewinding,
> minor number 1 for non-rewinding. For the same device, of course.
>
> For second device, I thing, it will be 2&3.
>
> Now, I can describe all the way.
>
> 1) insmod tape390 tape=<address>
>
> Driver uses major number 254 (in my case)
>
> 2) cd /dev; mknod ntibm1 c 254 1
>
> 3) mt -f /dev/ntibm1 rewind
>
> 4) dd if=image of=/dev/ntibm1 bs=1024 # write kernel
> image
> mt -f /dev/ntibm1 eof 1
> #
> write EndOfFile mark
>
> dd if=parmfile of=/dev/ntibm1 bs=1024 # write parmfile
> mt -f /dev/ntibm1 eof 1
> #
> write EndOfFile mark
>
> dd if=initrd of=/dev/ntibm1 bs=1024 # write
> ramdisk
> image
> mt -f /dev/ntibm1 eof 2
> #
> write EndOfFile mark twice - for sure :)
>
>
> 5) mt -f /dev/ntibm1 rewind
>
> You have the correct tape. Easy :)
>
>
> >Sergey,
> >
> >I don't have the source for tape390.o, but if it's modeled after SCSI
> tape
> >support, the minor device number should be 128+n for a non-rewinding
> >device, just 128 in your case. Minors between 0-127 all rewind.
> >
>
>
