[opensuse] SuSE-13.1 and older kernels - no go
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? Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Mark, There are several reasons that it might fail: 1) AFAIK, libc can be built with support from a specific Kernel upwards. This means that, if who decides at openSUSE, choose to build libc with support only for kernel 3.11+, you could experience this problem. Is your case, I'm not sure if a libc compiled for kernel 3.11+ would affect 3.4. You could check libc documentation. 2) udev also has upper and lower restrictions on Kernel versions. You might want to check if that affects you. 3) Last but not least, did you compile your own kernel ? Or used one from an earlier openSUSE distro ? An openSUSE distro Kernel might be more generic (hardware related) Regards, Rui On 06-12-2013 12:28, Mark Hounschell wrote:
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?
Thanks Mark
-- Rui Santos http://www.ruisantos.com/ Veni, vidi, Linux! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 06/12/13 10:24, Rui Santos escribió:
Hi Mark,
There are several reasons that it might fail:
1) AFAIK, libc can be built with support from a specific Kernel upwards. This means that, if who decides at openSUSE, choose to build libc with support only for kernel 3.11+, you could experience this problem. Is your case, I'm not sure if a libc compiled for kernel 3.11+ would affect 3.4. You could check libc documentation.
Yes, but it is currently built with 2.6.32 as a requirement in x86_64 and 2.6.16 in other archs, in anycase, this glibc<->kernel version requirement cannot currently go beyond kernel 3.1.
2) udev also has upper and lower restrictions on Kernel versions. You might want to check if that affects you.
Systemd and udev have as base requirement kernel 3.0 (or kernel 3.8 if smack is enabled which is not the case of openSUSE) plus glibc 2.14 or later. this will almost certainly change in the future. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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... Dx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 2013-12-08 07:00 (GMT-0500) Mark Hounschell composed:
Mark Hounschell composed:
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.
Done how, retrofitting 3.4 to a 13.1 installation, or zypper dup'ing a 12.2 system through 12.3 into 13.1 with the kernel locked? If you've only tried the former, try the latter, using chattr +i on the initrd and/or keeping kernel, initrd and drivers in place outside the package management system if necessary.
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.
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. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/2013 08:33 AM, Felix Miata wrote:
On 2013-12-08 07:00 (GMT-0500) Mark Hounschell composed:
Mark Hounschell composed:
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.
Done how, retrofitting 3.4 to a 13.1 installation, or zypper dup'ing a 12.2 system through 12.3 into 13.1 with the kernel locked? If you've only tried the former, try the latter, using chattr +i on the initrd and/or keeping kernel, initrd and drivers in place outside the package management system if necessary.
The kernel is being built from source on a fresh 13.1 install. Haven't even got to those drivers yet. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 09/12/13 06:15, Mark Hounschell escribió:
The kernel is being built from source on a fresh 13.1 install. Haven't even got to those drivers yet.
Oh, so your own custom built kernel does not boot ... I thought you were using an old package.. the quickest solution will probably be to cloneconfig, then modify it to include your drivers and boot it. However the most productive approach will be to assist kernel developers in the inclusion of the needed drivers into the main tree.. (task not for the faint-hearted though) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 08/12/13 08:28, Mark Hounschell escribió:
that these 3rd party vendors are unable to keep up with. They have basically given up.
Yes, that's a consequence of doing it wrong..if you decide to keep drivers out of tree for your device and submit them "later" well.. it is already too late..attempting to correct course is going to "sting" a little. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Cristian Rodríguez -
Dylan -
Felix Miata -
Mark Hounschell -
Rui Santos