kernel-2.6.31 52 worst than 46

[SlowJet]

Hang at Plymouth with no mouse.
If no rhgb nomodeset noquiet level 3 then it
kills avahi
hangs hal

ctrl-C at hal get to logon prompt
then keeps going
bang, crash
services start failing
and system shut things down and reboots.

48 work for fall back with all the 52 parts and the new updates such as
libselinux, libsemanage, Plymouth,

SJ

[diamond_ramsey]

Hang at Plymouth with no mouse.
If no rhgb nomodeset noquiet level 3 then it
kills avahi
hangs hal

ctrl-C at hal get to logon prompt
then keeps going
bang, crash
services start failing
and system shut things down and reboots.

48 work for fall back with all the 52 parts and the new updates such as
libselinux, libsemanage, Plymouth,

SJ

SlowJet, have you tried the 2.6.31-1-56.fc12.i686 kernel?

FYI, I have not tried the the 2.6.31-1-52.fc12.i686 kernel.

Fedora 12 (Constantine) alpha kernels, which I have tried -

* 2.6.31-0.125.4.2.rc5.git2.fc12.i686
* 2.6.31-0.167.4.2.rc6.git2.fc12.i686
* 2.6.31-0.174.4.2.rc7.git2.fc12.i686
* 2.6.31-0.190.rc8.fc12.i686
* 2.6.31-0.204.rc9.fc12.i686
* 2.6.31-2.fc12.i686
* 2.6.31-12.fc12.i686
* 2.6.31-14.fc12.i686
* 2.6.31-33.fc12.i686
* 2.6.31-1-48.fc12.i686.PAE
* 2.6.31-1-56.fc12.i686.PAE

As always, on the forums, share your wealth of knowledge and we will all be empowered. ;)

=
* Fedora 9 (Sulphur) kernel - vmlinuz-2.6.27.25-78.2.56.fc9.i686
* Fedora 10 (Cambridge) kernel - vmlinuz-2.6.27.30-170.2.82.fc10.i686
* Fedora 11 (Leonidas) kernels - vmlinuz-2.6.30.5-43.fc11.i586 and vmlinuz-2.6.30.5-43.fc11.i686.PAE
* Fedora 12 (Constantine) kernels - vmlinuz-2.6.31-33.fc12.i686 and vmlinuz-2.6.31.1-56.fc12.i686.PAE
With eight (8) x86_64 computing cores, 16 GB of RAM and SATA Seagate 7200.12 500 GB harddisk.
=

[SlowJet]

Yes, it works and so does the 58.
However it is best to update dacut and policy and selinux packages along with these.

I have f12 on a Pent IV and a Pent III and it is running very smooth.
I have an f12 VBox rpm from a test page dated sep 23rd. (It only has src additions and drmmodule blows the kms, mouse and kbd, so I can't use it.)

I used two F12's and one F11.
The only issue there is the mouse driver.
Sessions is clobbered by an access denied from SELinux for some xdp to gdm-geeter-wor
Hence, the mouse is not available with enforcing=1 but with enforcing=0 the vbox will grab the mouse after logon screen.

SJ