Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test

2016-03-11 Thread Ronny Peine
Hello Evergreen Team,

the update to the new 3.12 kernel went fine here on different intel
machines with different intel generations and one with fglrx driver. No
problems experienced so far and everything seems fine.
Big thank you for your good work:)

Kind regards,
Ronny

Am 26.02.2016 um 14:47 schrieb Marcus Meissner:
> Hi,
> 
> The 3.12 kernel version upgrade prepared by Michal is ready for testing:
> 
> http://download.opensuse.org/repositories/openSUSE:/Maintenance:/4624/openSUSE_13.1_Update/
> 
> We will wait for positive feedback.
> 
> Ciao, Marcus
> ___
> Evergreen mailing list
> Evergreen@lists.rosenauer.org
> http://lists.rosenauer.org/mailman/listinfo/evergreen
> 
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen


Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test

2016-03-11 Thread Carlos E. R.
On 2016-03-11 08:24, Patrick Schaaf wrote:

> Now, when updating (zypper dup) with the 3.12 update, zypper tells me
> that in addition to kernel-vanilla, kernel-pae needs to be installed.
> I don't even have kernel-pae in my repo mirrors, because I exclude all
> the non-x86_64 stuff there.

When the package manager wants to install a 32 bit package on a 64 bit
installation it typically is because it doesn't find a 64 bit solution.
Some wanted 64 bit rpm does not exist on the repos.

-- 
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)



signature.asc
Description: OpenPGP digital signature
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen


Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test

2016-03-10 Thread Patrick Schaaf
I noticed an issue that somebody might want to look into (or not).

On our production kvm virtual machines, we really run a self built
kernel provided by the kvm host system; the installed kernel in the
virtual machine is dormant. A long time ago I tried to uninstall
kernel-default, but was forced by dependencies to install another
kernel-*. Finally I arrived at having kernel-vanilla installed on all
the VMs.

Now, when updating (zypper dup) with the 3.12 update, zypper tells me
that in addition to kernel-vanilla, kernel-pae needs to be installed.
I don't even have kernel-pae in my repo mirrors, because I exclude all
the non-x86_64 stuff there.

I can workaround this with "zypper in kernel-default -kernel-vanilla",
after that, the kernel-pae is no longer required.

Maybe I'll have a close look at the dependencies, and build myself an
empty kernel-dummy RPM. Any hints on what dependencies such a package
would need to declare (so that the published kernel-* packages would
no longer be required?)

best regards
  Patrick
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen


Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test

2016-03-08 Thread Michal Kubecek
On Mon, Mar 07, 2016 at 02:20:36PM +0100, Marcus Meissner wrote:
> 
> negative points were:
> NVIDIA - That "hard way" is needed is to be expected.

Yes, any third party module needs to be rebuilt. On the other hand, once
it is built for the 3.12 kernel, there should be no need for further
rebuilds on future updates.

> aacraid - Not many people use it and it did not clearly turn out to be
> a regression.

I'm going to ask SCSI guys for an opinion; what is confusing is the
driver is the same as in SLE12-SP1 and almost the same as in mainline
4.4 kernel. It might be something trivial - and it might also be a bug
affecting SLE12-SP1.

There is also bsc#966831 but that is not a regression either. It's going
to be fixed with next update.

> Otherwise it seemed all good.
> 
> I just released the kernel update to 3.12.53.

Thank you.

A general note: if anybody is going to report a bug for the 3.12 kernel,
please add me to Cc (my bugzilla account is mkube...@suse.com).

 Michal Kubecek

___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen


Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test

2016-03-07 Thread Marcus Meissner
On Fri, Mar 04, 2016 at 07:29:55PM +0100, Carlos E. R. wrote:
> 
> On Friday, 2016-02-26 at 14:47 +0100, Marcus Meissner wrote:
> 
> >The 3.12 kernel version upgrade prepared by Michal is ready for testing:
> >
> >http://download.opensuse.org/repositories/openSUSE:/Maintenance:/4624/openSUSE_13.1_Update/
> >
> >We will wait for positive feedback.
> >
> >Ciao, Marcus
> 
> On nvidia with propietary driver, easy method (rpm), I get a
> display, but not by nvidia (trying startx)
> 
> Initializing built-in extension DRI2
> Loading extension GLX
> FATAL: Module nvidia not found.
> FATAL: Module nvidia_uvm not found.
> sh: cat: command not found
> /usr/bin/mknod: missing operand after 0
> Try '/usr/bin/mknod --help' for more information.
> sh: chown: command not found
> sh: chown: command not found
> FATAL: Error running install command for nvidia
> The XKEYBOARD keymap compiler (xkbcomp) reports:
> 
> 
> I guess that installing the driver the "hard way" would work,
> perhaps I'll try later.
> 
> On text mode console, I get some weird effects with redrawing the
> screen with Alpine (it is what I'm using to compose this), but 'mc'
> seems fine.

Yes, with the kernel currently only "hard way" for NVIDIA will work, as
the KMPs are built against the old kernel.

Ciao, Marcus
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen


Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test

2016-03-06 Thread Bruno Friedmann
On vendredi, 4 mars 2016 10.09:59 h CET Bruno Friedmann wrote:
> On vendredi, 4 mars 2016 08.52:27 h CET Michal Kubecek wrote:
> > On čtvrtek 3. března 2016 19:47 Bruno Friedmann wrote:
> > > 
> > > But on two machines : having an adaptec raid controleur 6805 I'm
> > > getting a kernel backtrace (sorry no time until today to report it
> > > correctly)
> > > Which is curious, I was using during a certain time a kernel 4x series
> > > on them Not a big deal for myself, but can be really tricky to
> > > recover from ...
>  
> > Do you remember what was the last working version? The aacraid has been 
> > backported for SLE12-SP1 so that the version in the evergreen 13.1 
> > kernel differs from current mainline only in 2 or 3 commits which do not 
> > seem very important.
> 
> On one of them I've this history of kernel used (during a time I was using
> kernel:standard) before switching back to evergreen.
> 
> 2014-04-17 
> 22:24:57|kernel-default|3.11.6-4.1|x86_64|root@clochette.disney.interne|openSUSE-13.1-1.10
> 2014-04-17 23:13:36|kernel-default|3.11.10-7.1|x86_64||updates
> 2014-04-18 
> 00:32:55|kernel-default|3.14.1-1.1.geafcebd|x86_64|root@clochette|kernel-stable
> 2014-05-06 18:17:35|kernel-default|3.14.2-1.1.g1474ea5|x86_64||kernel-stable
> 2014-05-20 18:30:49|kernel-default|3.11.10-11.1|x86_64||updates
> 2014-05-20 18:35:06|kernel-default|3.14.4-1.1.gbebeb6f|x86_64||kernel-stable
> 2014-06-06 17:15:46|kernel-default|3.14.4-2.1.g0de0f93|x86_64||kernel-stable
> 2014-07-01 17:38:11|kernel-default|3.15.2-1.1.gfb7c781|x86_64||kernel-stable
> 2014-07-01 17:41:17|kernel-default|3.11.10-17.2|x86_64||updates
> 2014-07-10 18:47:49|kernel-default|3.15.4-1.1.g2b59ae6|x86_64||kernel-stable
> 2014-07-29 18:28:29|kernel-default|3.15.6-2.1.gedc5ddf|x86_64||kernel-stable
> 2014-08-01 17:21:02|kernel-default|3.15.7-1.1.g972d9a6|x86_64||kernel-stable
> 2014-08-13 19:27:38|kernel-default|3.11.10-21.1|x86_64||updates
> 2014-08-13 19:28:49|kernel-default|3.15.8-2.1.g258e3b0|x86_64||kernel-stable
> 2014-09-12 17:56:36|kernel-default|3.16.2-1.1.gdcee397|x86_64||kernel-stable
> 2014-09-30 11:15:49|kernel-default|3.16.3-1.1.gd2bbe7f|x86_64||kernel-stable
> 2014-10-17 18:07:46|kernel-default|3.17.0-1.1.gc467423|x86_64||kernel-stable
> 2014-12-03 17:53:49|kernel-default|3.17.4-2.1.g2d23787|x86_64||kernel-stable
> 2015-01-06 
> 17:54:51|kernel-default|3.18.1-1.1.g5f2f35e|x86_64|root@clochette|kernel-stable
> 2015-01-20 17:59:23|kernel-default|3.18.2-2.1.g88366a3|x86_64||kernel-stable
> 2015-02-03 17:44:26|kernel-default|3.18.5-1.1.gf378da4|x86_64||kernel-stable
> 2015-03-03 17:57:05|kernel-default|3.19.0-4.1.g7f0e735|x86_64||kernel-stable
> 2015-03-11 18:07:01|kernel-default|3.19.1-2.1.gc0946e9|x86_64||kernel-stable
> 2015-03-21 09:05:51|kernel-default|3.19.2-1.1.gf2f9797|x86_64||kernel-stable
> 2015-04-02 17:00:19|kernel-default|3.19.3-1.1.gf10e7fc|x86_64||kernel-stable
> 2015-04-17 19:04:27|kernel-default|3.19.4-1.1.g74c332b|x86_64||kernel-stable
> 2015-05-13 18:15:53|kernel-default|4.0.2-1.1.ga425d38|x86_64||kernel-stable
> 2015-06-02 18:18:37|kernel-default|4.0.4-4.1.gad54361|x86_64||kernel-stable
> 2015-06-16 18:13:00|kernel-default|4.0.5-2.1.g0e899eb|x86_64||kernel-stable
> 2015-07-14 17:59:47|kernel-default|4.1.1-2.1.gcac28b3|x86_64||kernel-stable
> 2015-07-29 13:56:16|kernel-default|4.1.3-5.1.ga0f869c|x86_64||kernel-stable
> 2015-08-11 11:26:26|kernel-default|4.1.4-1.1.ga37e14f|x86_64||kernel-stable
> 2015-08-15 10:53:25|kernel-default|4.1.5-2.1.g83fbd4e|x86_64||kernel-stable
> 2016-02-02 
> 18:25:21|kernel-default|4.4.0-8.1.g9f68b90|x86_64|root@clochette|kernel-stable
> 2016-02-17 
> 18:45:43|kernel-default|3.12.51-2.1|x86_64|root@clochette|kernel-evergreen
> 2016-02-17 19:37:15|kernel-default|3.11.10-34.2|x86_64|root@sysresccd|updates
> 2016-03-01 17:52:16|kernel-default|3.12.53-1.1|x86_64||kernel-evergreen
> 
> The last high number was 4.4.0, and the first working > 3.11 was 3.14.1
> 
> this is how arcconf tools see the controler and system on a pure
> 3.11.10-34-default 
>
>Controller Version Information 6805
>
>BIOS : 5.2-0 (19147)
>Firmware : 5.2-0 (19147)
>Driver   : 1.2-0 (30200)
>Boot Flash   : 5.2-0 (19147)
> 
> 
> 
> On another one which has a different controleur but working 3.12.53
>
>Controller Version Information 5805
>
>BIOS : 5.2-0 (18948)
>Firmware : 5.2-0 (18948)
>Driver   : 1.2-1 (40709)
>Boot Flash   : 5.2-0 (18948)
> 
> We saw the driver get an update 1.2-0 to 1.2-1 
> 

Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test

2016-03-04 Thread Jens Grabinger
Hi everyone!

Date: Wed, 2 Mar 2016 11:27:13 +0100
> From: Marcus Meissner <meiss...@suse.de>
> To: Axel Braun <axel.br...@gmx.de>
> Cc: evergreen@lists.rosenauer.org
> Subject: Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1
>     level) ready for test
> Message-ID: <20160302102712.gb6...@suse.de>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Feb 26, 2016 at 03:22:20PM +0100, Axel Braun wrote:
> > Hi Markus,
> >
> > > Gesendet: Freitag, 26. Februar 2016 um 14:47 Uhr
> > > Von: "Marcus Meissner" <meiss...@suse.de>
> > > An: evergreen@lists.rosenauer.org
> > > Betreff: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level)
> ready for test
> > >
> > > The 3.12 kernel version upgrade prepared by Michal is ready for
> testing:
> > >
> > >
> http://download.opensuse.org/repositories/openSUSE:/Maintenance:/4624/openSUSE_13.1_Update/
> > >
> > > We will wait for positive feedback.
> >
> > Applied the upgrade together wih all other open patches to my 13.1
> VirtualBox, rebooted, tested postgres and ERP server...everything worked
> fine so far.
>
> Have other people tried it in the meantime?
>

I have tried the 3.12 kernel on two machines. One machine is a desktop box
with an Intel Core i5-4670 CPU and AMD fglrx driver installed. Have been
working on this machine all day yesterday without any problems. The other
machine is an Acer laptop with an i5-4200 and Intel graphics. On this
machine the 3.12 kernel actually works better than the 3.11 kernel. Intel
graphics driver is much better, no graphics glitches under GNOME and even
backlight control works now.

Regards,
Jens Grabinger
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen