No, I don't want to do that kind of stuff! I just thought the Gentoo distribution might be something I could get up and running without too much pain. The TAO Linux/390 distribution was faily easy. One has to thank the person who did that port!
If I'm running into a brick wall because of a bug in the 2.6.5 kernel then I don't want to spend anymore time on it. OTOH, if it's just a matter of getting the config right I want to continue. >>> [EMAIL PROTECTED] 05/19/04 03:56PM >>> They will, eventually. SLES9 will be based on 2.6. RHEL4 will most likely (almost undoubtedly). Being developers, system integrators, etc., is what they get paid to do. Doing it on your own can be painful, unless you like learning an awful lot, very fast. (I do, which is why I do that sort of thing. A lot of people don't.) There are probably easier places to start than with kernel patching and compiling, but if that's what you want to do, then read up on all that and give it a try. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Richard Pinion Sent: Wednesday, May 19, 2004 2:09 PM To: [EMAIL PROTECTED] Subject: Re: lcs problem under 2.6 Because it's there! Also, won't the others migrate to kernel-2.6.5? >>> [EMAIL PROTECTED] 05/19/04 01:34PM >>> Ok, so now the question becomes, why are you wanting to run Gentoo? Debian for S/390 is current, known to work, and not on the bleeding edge of kernels. Then there's Tao Linux (based on RHEL3), etc. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Richard Pinion Sent: Wednesday, May 19, 2004 11:12 AM To: [EMAIL PROTECTED] Subject: Re: lcs problem under 2.6 According to the Gentoo install doc, "The only kernel that is currently supported by Gentoo's S/390 port is 2.6.5 development-sources. If you want to you can try a different kernel by adding the s390 keyword to the ebuild. To install the kernel source all you need to do is emerge them". Perhaps this is a problem within the kernel or lcs driver???? I can live with that, but if it's a setup problem I would like to learn what needs to be done. >>> [EMAIL PROTECTED] 05/19/04 11:04AM >>> That would be a patch to the kernel source. If you're still new enough at this that you don't know what to do with it, you're in for a real, ummm, learning experience as they say. I have to ask why you want so much to be working with 2.6? Is there something there you really need for your particular business situation? Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Richard Pinion Sent: Wednesday, May 19, 2004 10:55 AM To: [EMAIL PROTECTED] Subject: Re: lcs problem under 2.6 Yes I did. I've downloaded the kernel-2.6.5 May 18, 2004 tar file. I have to admit I don't know what to do with this? Is this kernel source or executables??? >>> [EMAIL PROTECTED] 05/19/04 10:53AM >>> To the person who was having lcs problems with 2.6. Did you see this on the latest code drop on Developerworks? Description:lcs: LCS interface cannot be initialized. Symptom:System hangs during startup when initializing a LCS interface. Problem:When IP multicast addresses are registered, the lcs card's lock was used for synchronization. The scope of this lock is too large. Solution:Don't use card->lock. Introduced card->ipm_lock to synchronize multicast lists. Problem-ID:- Description:lcs: net_device reference counting problem. Symptom:Trying to do an rmmod lcs or ungrouping an lcs device results in a hanging session with messages "waiting for ... to become free" displayed. Problem:An in_dev_put was missing in multicast address list handling. Solution:Added the missing in_dev_put. Problem-ID:- Description:lcs: null-pointer dereference failure after unsuccessful set_online. Symptom:If setting an LCS card online fails, the next try to set the card online results in a null-pointer dereference. Problem:Card's IO buffers are freed if lcs_detect returns an error. Solution:Do not call lcs_cleanup_card in case of errors in lcs_new_device. This allows for trying to set an LCS card online multiple times. lcs_cleanup_card is called in lcs_remove_device which is sufficient for freeing allocated memory. Neale Ferguson ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
