You can insmod the IBM drivers with the new kernel. We're doing it, and it works fine.
You have to use the '-f' option though, but only because SuSE changed the ID string for the kernel. The 'new' kernel is still 2.4.7, just with a few fixes. > -----Original Message----- > From: Michael MacIsaac [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 29, 2002 9:22 AM > To: [EMAIL PROTECTED] > Subject: Re: Red Hat 7.2 - install by tape? > > > > can someone tell me what > > it means to not be "able to insmod the qdio/qeth driver"? > > As I understand it ... > There are a number of ways to do networking on Linux on zSeries. > Ususally the driver is a Linux module. Linux modules are often > added to the Linux kernel via the insmod command. In order to > "insmod" a module, it needs to be compatible. If the module > is built at a different level than the kernel and contains no > unresolved external symbols, the module can still be > "insmod"ed with the -f (force) flag. If there are > unresolved symbols (data or code areas referenced, but not > present), then the module simply will not "insmod", and therefore > cannot be used. This is the case with an upgraded Red Hat > 2.4.9-31 kernel and the qdio/qeth modules at the 2.4.9-17 level > available on IBM developerWorks. Therefore, if you want to upgrade > the kernel, you cannot use the qdio/qeth drivers which are used for > the OSA-Express in QDIO mode (TYPE=OSD) and for hipersockets. > > > > -Mike MacIsaac, IBM [EMAIL PROTECTED] (845) 433-7061 >
