On 12/08/2013 06:47 AM, Dylan wrote:
On 08/12/13 11:28, Mark Hounschell wrote:
On 12/06/2013 12:43 PM, Cristian Rodríguez wrote:
El 06/12/13 09:28, Mark Hounschell escribió:
I have a need to run a 3.4.x flavor kernel on a 13.1 box. No problem on 12.3 but on 13.1 the same kernel faults immediately. I haven't put a serial console on to see the oops message but is there any reason it "shouldn't" work?
This is a completely unsupported scenario and is no wonder it does not work.
Why do you need to do such thing in the first place?
I have a requirement that uses 3rd party GPL out of kernel drivers (serial). As of kernel 3.5 and continuing today, the serial subsystem is undergoing major changes that these 3rd party vendors are unable to keep up with. They have basically given up. These GPL drivers, as of a few months ago, are slowly being added to the kernel by the linuxdevel people (Greg KH). It's a slow process though. Until they are completed and functional I need to use a 3.4 kernel.
Fair enough, but why is it necessary to do this on oS13.1? Particularly since you had it working correctly on an earlier version...
I like to stay as current as possible. We also have our own GPL out of kernel drivers. There are always some issues keeping current. Such as changes to gcc, glibc, systemd, and udev. Often, skipping releases, such as waiting for SuSE-14, just compounds these issues and makes it more difficult to "catch up". Freezing at a particular SuSE version is not an option. Even though I'm stuck for now with the 3.4 kernel, our GPL out of kernel drivers are kept building and working on the very latest kernels as they appear. Regards Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org