Michael, If you do an insmod -f /lib/lcs.o, you should be able to get it to load. It will still complain (as I recall), but it should load. (An lsmod command will show you if it did or not.) The reason why it complains is because of Red Hat's kernel naming convention. Not being satisfied with labeling their kernel "2.4.7" they instead name it "2.4.7-6.1BOOT." I would not expect IBM to create an lcs.o module with that label inside it. Ever. Mark Post -----Original Message----- From: Michael K Lambert [mailto:mlambe7@lsu.edu] Sent: Monday, September 17, 2001 12:04 PM To: redhat-s390-list@redhat.com Subject: [Redhat-s390-list] No LCS module found after following README instructions >After attempting to load again, we got a different error >message stating: > >" /lib/lcs.o was compiled for kernel version 2.4.7 >while this kernel is >version 2.4.7-6.1BOOT > /lib/lcs.o unresolved symbol tasklet_hi_schedule " > >and then proceeded to spit out the usual messages about no >device found. > >Well, this sent us running to the IBM site to see if >perhaps they had some >other version that we had missed. Lo and behold, we saw >that they had >updated just this afternoon to lcs-2.4.7-s390-1.o. > >Hopefully this will resolve our problems, but we don't >have a chance to >experiment today (our only CD burner is being used). We'll >try Monday >morning. It's Monday morning and the lastest IBM drivers have yielded exactly the same results. I have emailed IBM, asking for compatible modules, but I'm not holding my breath. Although I know that Red Hat does not provide support for IBM's proprietary mods, I was hoping that someone would at least have a suggestion as to how we could workaround this problem. Michael Lambert _______________________________________________ Redhat-s390-list mailing list Redhat-s390-list@redhat.com https://listman.redhat.com/mailman/listinfo/redhat-s390-list
