So 2.6.34 is stable, aye?

[SlowJet]

Did that come down from the BP off-shore testing group?

www.kernel.org

$ rpm -qa kernel-PAE
kernel-PAE-2.6.33.3-85.fc13.i686
kernel-PAE-2.6.33.3-83.fc13.i686
kernel-PAE-2.6.33.3-84.fc13.i686
kernel-PAE-2.6.34-0.49.rc7.git0.fc14.i686

SJ

[SlowJet]

Well, it seems to be working ok.

$ uname -a
Linux Ruthie-07.WinProxy 2.6.34-2.fc14.i686.PAE #1 SMP Mon May 17 03:51:24 UTC 2010 i686 i686 i386 GNU/Linux
[darwinhwebb@Ruthie-07 ~]$ rpm -qa kernel\*
kernel-PAE-devel-2.6.34-2.fc14.i686
kernel-headers-2.6.34-2.fc14.i686
kernel-PAE-2.6.34-0.49.rc7.git0.fc14.i686
kernel-PAE-2.6.34-2.fc14.i686

SJ

[SlowJet]

Kernel-PAE-2.6.34-11 stop crashing Gnome/xorg.
So far so ggod.

SJ

[jvillain]

2.6.34 has been a champ over here.

[Dr.Diesel]

Most excellent for me as well.

[dd_wizard]

Working well for me as well.

dd_wizard

[kyryder]

A yup +1

Ky

[SlowJet]

2.6.34-14 works for nouveau but intel (915=> 865) = no kms drv's found, no screen
vesa works (however f14 intel looks older than f13 intel?)

2.6.34-18 - compiling now looks like a fix.

SJ

---------- Post added at 10:29 AM CDT ---------- Previous post was at 09:51 AM CDT ----------

No change for 18.
nouveau works but gets a kernel crash on Pent III 800

intel crashes kernel, still no kms drv's found.

vesa with xorg.conf init3 startx works as before.

SJ

[kyryder]

2.6.34-18.fc14.i686.PAE up and running here (not very long yet) seems ok so far.

Ky

[SlowJet]

2.6.34-18.fc14.i686.PAE up and running here (not very long yet) seems ok so far.

Ky

Are you using xorg-x11-drv-nouveau for a nvidia card?

SJ

[dd_wizard]

2.6.34-14 works for nouveau but intel (915=> 865) = no kms drv's found, no screen
vesa works (however f14 intel looks older than f13 intel?)

You're right about that:
[gene@Mobile-PC exaile]$ yum list xorg-x11-drv-intel
Loaded plugins: fastestmirror, presto, refresh-packagekit, remove-with-leaves, show-leaves,
: verify
Installed Packages
xorg-x11-drv-intel.x86_64 2.11.0-4.fc13 @/xorg-x11-drv-intel-2.11.0-4.fc13.x86_64/13
Available Packages
xorg-x11-drv-intel.i686 2.10.0-5.fc14 rawhide

Kernel 14 works fine on my Intel 945GM graphics, I'm about to try 18.

dd_wizard

[SlowJet]

You're right about that:

Kernel 14 works fine on my Intel 945GM graphics, I'm about to try 18.

dd_wizard

Yes, 14 was ok for many.
The stange thing I observered was the vesa (on an intel) is much more stable for f13 and CentOS-5.5 running in VBox-320 (They use vesa also.).

I may revert back to 14 and f13 intel drv if they can't figure out the 35 patch stuff. It's too iffy and looks like guess work.

SJ

[kyryder]

Are you using xorg-x11-drv-nouveau for a nvidia card?

SJ

No, I am using intel:
[kyryder@localhost ~]$ rpm -qa|grep xorg-x11-drv-intel*
xorg-x11-drv-intel-2.11.0-4.fc13.i686

Ky

[SlowJet]

No, I am using intel:
[kyryder@localhost ~]$ rpm -qa|grep xorg-x11-drv-intel*
xorg-x11-drv-intel-2.11.0-4.fc13.i686

Ky

You are also using the f13 drv.
What model of intel graphics do you have?

SJ

[kyryder]

You are also using the f13 drv.
What model of intel graphics do you have?

SJ

i915GM in laptop

Ky

[SlowJet]

i915GM in laptop

Ky

Humm, a mixed bag of bugs.
I'll give the f13 intel drv a shot on 18.

SJ

[dd_wizard]

The first boot after updating to 18 crashed (as in the machine rebooted itself between the login screen and gnome/openbox) after logging in. It may have been related to this log message:
Jun 1 12:02:57 localhost kernel: gnome-panel[2398]: segfault at 390a24c500 ip 000000390a24c500 sp 00007fffb51c1c08 error 4 in libgnome-desktop-2.so.17.1.1[390ae00000+28000]
Jun 1 12:02:57 localhost kernel: Process 2398(gnome-panel) has RLIMIT_CORE set to 0
Jun 1 12:02:57 localhost kernel: Aborting core

The second try worked, though. So I'm not sure how stable 18 is even with the F13 Intel drivers.

dd_wizard

[SlowJet]

The first boot after updating to 18 crashed (as in the machine rebooted itself between the login screen and gnome/openbox) after logging in. It may have been related to this log message:

The second try worked, though. So I'm not sure how stable 18 is even with the F13 Intel drivers.

dd_wizard

I just tried f13 intel drv with the 18 and got the same no kms drv's found.
So I think you're correct.
What is really funny is the test-list discussion about getting 34 for f13 and iit is not even at 34.1 yet.
How soon they forget. Or never knew in the first place.

kernel-2.6.35-rc2 anyone? :)

SJ

[dd_wizard]

This section of the change log for kernel 20 makes me think there are problems with 18:
Changelog
* Wed Jun 02 2010 Kyle McMartin <kyle@redhat.com> 2.6.34-19
- Enable -debug flavour builds, until we branch for 2.6.35-rcX.

* Wed Jun 02 2010 Kyle McMartin <kyle@redhat.com>
- revert writeback fixes for now, there appear to be dragons lurking there still.

* Tue Jun 01 2010 Kyle McMartin <kyle@redhat.com> 2.6.34-18
- fix mismerge in i915_gem.c, drm_gem_object_alloc is now i915_gem_alloc_object.
- add a hunk to rcu_read{,un}lock in sched_fair too.

* Tue Jun 01 2010 Kyle McMartin <kyle@redhat.com> 2.6.34-17
- backport writeback fixes from Jens until stable@ picks them up.

Gnome-shell did crash once on me with the 20 kernel yesterday, though.

dd_wizard