Mark, There are about 40 unresolved symbols in each module. It doesn't matter whether tape390 is already inserted or not, whether the insmod happens through modprobe or insmod itself: the result is the same. Like you, I would have figured modprobe to do it all; but I guess there's nothing it can do if the modules are just plain out of sync with the kernel.
I found out from another source that the -107 (SLES8 SP3) kernel binaries are messed up. The -127 update is reputed to fix this problem. I guess that's what we're doing next. Thanks for your input! --Jim-- James S. Tison Senior Software Engineer TPF Laboratory / Architecture IBM Corporation "If dogs don't go to heaven, then, when I die, I want to go where they do." -- Will Rogers "Post, Mark K" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 05/20/2004 11:30 Please respond to Linux on 390 Port To [EMAIL PROTECTED] cc Subject Re: SuSE SLES 8 SP3 (kernel 2.4.21-107) What are the unresolved symbols that are reported? What happens when you insmod tape390 first? The modprobe command is supposed to figure out all this stuff, so I would have thought that just doing a "modprobe tape_3590" or "modprobe tape_3590_mod" would be the way to go. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of James Tison Sent: Thursday, May 20, 2004 12:15 AM To: [EMAIL PROTECTED] Subject: SuSE SLES 8 SP3 (kernel 2.4.21-107) We just upgraded from base SLES 8 (kernel 2.4.19-3) to SP3. We noted is the tape module configuration change. We hand- wrote a sysinit script to modprobe tape390, and now an implicit insmod for tape_3590 fails. Sure enough, the new modules.dep lists two modules: tape_3590 and tape_3590_mod with the "main" tape driver (kernel/drivers/s390/char/tape390.o) as the sole dependency for each. True to form, lsmod shows nothing so named as loaded, and an attempt to attach a 3590 fails to register the device. No I/Os issued against /dev/ntibm0 work when we attach a 3590, but all I/Os (and the contents of /proc/tapedevices) work for 3490 devices. When I try to cd into the directory with tape_3590.o and tape_ 3590_mod.o in it and issue insmod against either or both, I get flooded with "unrecognized symbol" messages ... I guess these don't match the kernel. The new initrd doesn't have/load any modules that would affect the tape* chain. Any ideas where I might be bumping my head? Fix? TIA, --Jim-- James S. Tison Senior Software Engineer TPF Laboratory / Architecture IBM Corporation "If dogs don't go to heaven, then, when I die, I want to go where they do." -- Will Rogers ---------------------------------------------------------------------- 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
