Rick, Again, I'm not sure what's going on with you and 2.4.24. It built just fine for me, but we might be using different configuration options.
Wait, I just remembered reporting that the 2.4.23/2.4.24 patches did _not_ include some fixes that were in the 2.4.21 series. (At least one of which was from one of my problem reports.) What was the compile error? I can probably tell you how to fix it. Yes, running depmod against kernel modules that don't exactly match the version _and configuration options_ of the currently running kernel can produce a lot of nasty messages that don't show up when booting the new kernel. The only way that I can see to avoid that would be to have the ability to point depmod to the new kernel, and have it figure things out from there. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Richard Troth Sent: Wednesday, February 04, 2004 2:32 PM To: [EMAIL PROTECTED] Subject: Re: Kernel 2.4.24 qeth.o - unresolved symdol show_trace > I don't know what you're doing wrong (using --dry-run perhaps?), but when I > applied the patches that were intended for 2.4.23 against 2.4.24, I got no > such errors. When I apply the 2.4.21 patches, I get no messages at all. Phase II of my report on fixing my self-inflicted problems. Yesterday, after re-stamping the .diff files for 2.4.23, they applied cleanly to 2.4.24. But now that kernel won't build. HOWEVER, I re-stamped the 2.4.21 patches and applied them to the generic kernel of the same release. Clean patch, clean build, and she's up and running right now. This is the one with IUCV and DCSS stuff in it. KEEPING IT ON TOPIC: I am also having trouble with qeth. Perhaps this kernel (and the qeth.o from it) will work. That is a step for a little later, perhaps tomorrow. I DID FIND that while running 2.4.21 and having just built a fresh 2.4.21 with the corrected patch order, 'depmod' spewed numerous errors about unresolved symbols. After rebooting and coming up on the new kernel, 'depmod' ran without complaint. A bit of a "catch 22" on that? -- R;
