[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Something's not right in FC10 land. Redhat Bugzilla errors 478815and 481761
- To: silug-discuss@silug.org
- Subject: Something's not right in FC10 land. Redhat Bugzilla errors 478815and 481761
- From: fbceachday <fbceachday@yahoo.com>
- Date: Mon, 02 Feb 2009 18:56:23 -0600
- DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=T9bNAJy1jqtGry4qVPOa5L3R842XS/nx64FbxyyDEyBwqrN5gjcgPiW2I2hHEB7j84axxb2S8qY8z7S7vagWD6Xxf+IZWxmlvs5J9elbPXm1t1GPNbWncwEXEXUGwuKl/xLFXDPVeP87cQOwVQ/aPA3gr5HCRJH9RqWotOqPvZI= ;
- Organization: Southern Illinois Linux Users Group
- Reply-To: silug-discuss@silug.org
- Sender: silug-discuss-owner@silug.org
- User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
Between the Nvidia issue I'm stuck with and now this boot bug in two out
of the three kernels I have, I am rather stumped.
Fedora (2.6.27.12-170.2.5.fc10.x86_64) is a classroom example of
481761. So no joy there. At least not yet.
Fedora (2.6.27.9-159.fc10.x86_64), mentioned in 478815 and for me just
passing the great black screen with blinky curser (Nvidia strikes
again) No joy there either.
Fedora (2.6.27.7-134.fc10.x86_64) does boot. Yeah. But, there's always
one of those...
The Nvidia driver doesn't work, so I am using vesa in the xorg.conf file
and it rewrites itseslf everytime I reboot.
So here I sit with a mostly working FC10 install using my one working
kernel. Sigh. I did say I liked using cutting edge stuff. ;).
Is there a way to neatly back out of the kernel upgrade that set all
this mayhem off? Will that fix the booting issue with 27.9-159, which
did work before the upgrade. Or am I just stuck until this bug dies a
natural death?
Other question. The Nvidia issue started at the same time the upgrade
started it's own parade, so I'm not sure what happened.
The Nvidia issue has to do with the kernel mod not loading or being an
API mismatch. I've had both. I tried uninstalling the drivers and
reloading the driver. No joy. I have to edit the xorg.conf and change
the driver to vesa to get a screen. Otherwise the log basically tells me
there are no useable screens.
Otherwise, the weather is wonderful. :) Suggestions and snide comments
are welcome.
Bonnie
-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.