8:23 a.m.
I'm not seeing this exact issue, apologies if I missed it
I installed NVidia drivers from Livna on a working FC6
On reboot, it gets all the way to the second X start and the
screen then just goes black and nothing happens
I tried booting into runlevel 3 the old way by typing "a" when the
splash screen came up, and typing "3" at the prompt - that didn't
work
Next time I typed "runlevel3" at the prompt, and that led to same
result as above, but in a much shorter boot time - just a black
screen
Tried booting into runlevel1 with the same result
Anyone else encountered this?
--
Claude Jones
Brunswick, MD, USA
9:08 a.m.
On Sun, 2006-10-29 at 09:23 -0500, Claude Jones wrote:
I'm not seeing this exact issue, apologies if I missed it
I installed NVidia drivers from Livna on a working FC6
On reboot, it gets all the way to the second X start and the
screen then just goes black and nothing happens
I tried booting into runlevel 3 the old way by typing "a" when the
splash screen came up, and typing "3" at the prompt - that didn't
work
Next time I typed "runlevel3" at the prompt, and that led to same
result as above, but in a much shorter boot time - just a black
screen
Tried booting into runlevel1 with the same result
Try 'init 3' Ric
--
================================================
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256 Sign up at: http://counter.li.org/
http://www.sourceforge.net/projects/oar
http://www.wayward4now.net
================================================
9:30 a.m.
On Sun October 29 2006 10:08 am, Ric Moore wrote:
On Sun, 2006-10-29 at 09:23 -0500, Claude Jones wrote:
> I'm not seeing this exact issue, apologies if I missed it
> I installed NVidia drivers from Livna on a working FC6
> On reboot, it gets all the way to the second X start and the
> screen then just goes black and nothing happens
> I tried booting into runlevel 3 the old way by typing "a"
> when the splash screen came up, and typing "3" at the prompt
> - that didn't work
> Next time I typed "runlevel3" at the prompt, and that led to
> same result as above, but in a much shorter boot time - just
> a black screen
> Tried booting into runlevel1 with the same result
Try 'init 3' Ric
It's getting worse. Now, it chokes on X on the first try, right
after the kernel messages, when it tries to go into the splash
screen with the progress bar for the boot process - it's just
going black and stalling - there's a little LED hard drive
activity, but it doesn't go anywhere - just the black void...
--
Claude Jones
Brunswick, MD, USA
9:48 a.m.
On 10/29/06, Claude Jones <claude_jones(a)levitjames.com> wrote:
On Sun October 29 2006 10:08 am, Ric Moore wrote:
> On Sun, 2006-10-29 at 09:23 -0500, Claude Jones wrote:
> > I'm not seeing this exact issue, apologies if I missed it
> > I installed NVidia drivers from Livna on a working FC6
> > On reboot, it gets all the way to the second X start and the
> > screen then just goes black and nothing happens
> > I tried booting into runlevel 3 the old way by typing "a"
> > when the splash screen came up, and typing "3" at the prompt
> > - that didn't work
> > Next time I typed "runlevel3" at the prompt, and that led to
> > same result as above, but in a much shorter boot time - just
> > a black screen
> > Tried booting into runlevel1 with the same result
>
> Try 'init 3' Ric
It's getting worse. Now, it chokes on X on the first try, right
after the kernel messages, when it tries to go into the splash
screen with the progress bar for the boot process - it's just
going black and stalling - there's a little LED hard drive
activity, but it doesn't go anywhere - just the black void...
Is this problem specific to Livna's repackaging of the NVIDIA driver,
or is it also present in the official driver package from NVIDIA's
website?
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama(a)gmail.com
LlamaLand http://netllama.linux-sxs.org
10:10 a.m.
On Sun October 29 2006 10:48 am, Lonni J Friedman wrote:
Is this problem specific to Livna's repackaging of the NVIDIA
driver, or is it also present in the official driver package
from NVIDIA's website?
I don't know, because I didn't try the official NVIDIA package.
I'm booted into rescue mode now, and I've got a prompt, but I'm
sort of flailing around - I tried "yum remove
kmod-nvidia-(etc..)" but it's choking on the updates mirrors - I
suppose things are still pretty busy on the mirrors.
--
Claude Jones
Brunswick, MD, USA
10:14 a.m.
On 10/29/06, Claude Jones <claude_jones(a)levitjames.com> wrote:
On Sun October 29 2006 10:48 am, Lonni J Friedman wrote:
> Is this problem specific to Livna's repackaging of the NVIDIA
> driver, or is it also present in the official driver package
> from NVIDIA's website?
I don't know, because I didn't try the official NVIDIA package.
I'm booted into rescue mode now, and I've got a prompt, but I'm
sort of flailing around - I tried "yum remove
kmod-nvidia-(etc..)" but it's choking on the updates mirrors - I
suppose things are still pretty busy on the mirrors.
If by 'rescue mode' you mean single user mode, there's no networking
in that runlevel, so yum is expected to fail for anything that
requires internet connectivity.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama(a)gmail.com
LlamaLand http://netllama.linux-sxs.org
10:20 a.m.
On Sun October 29 2006 11:14 am, Lonni J Friedman wrote:
If by 'rescue mode' you mean single user mode, there's
no
networking in that runlevel, so yum is expected to fail for
anything that requires internet connectivity.
Hmmm - that doesn't jive with what I just experienced. I thought
I'd give yum update a try in that mode, and it went out and
visibly downloaded the repo lists, checked dependencies, and
finally choked on an unresolved dependency for totem. After a few
tries at excluding the offending package, it started returning
errors about the updates repo - tha'ts when I tried to remove the
kmod-nvidia#### and that also returned updates repo errors.
--
Claude Jones
Brunswick, MD, USA
10:36 a.m.
On Sun October 29 2006 11:14 am, Lonni J Friedman wrote:
If by 'rescue mode' you mean single user mode, there's
no
networking in that runlevel, so yum is expected to fail for
anything that requires internet connectivity.
I realize now, you're obviously mistaken - I'd forgotten that when
I went into rescue mode, it actually asked if I wanted to start
networking, to which I replied yes. Maybe this is a feature
addition...
Anyway, I tried again to remove the Livna Nvdia stuff in rescue
mode, after doublechecking what Tim was saying, and this time,
running "yum remove kmod-nvidia-..." succeeded. Upon reboot, all
is now well. I guess I need to file a bug over on Livna.
--
Claude Jones
Brunswick, MD, USA
11:30 a.m.
On Sun, 2006-10-29 at 10:30 -0500, Claude Jones wrote:
On Sun October 29 2006 10:08 am, Ric Moore wrote:
> On Sun, 2006-10-29 at 09:23 -0500, Claude Jones wrote:
> > I'm not seeing this exact issue, apologies if I missed it
> > I installed NVidia drivers from Livna on a working FC6
> > On reboot, it gets all the way to the second X start and the
> > screen then just goes black and nothing happens
> > I tried booting into runlevel 3 the old way by typing "a"
> > when the splash screen came up, and typing "3" at the prompt
> > - that didn't work
> > Next time I typed "runlevel3" at the prompt, and that led to
> > same result as above, but in a much shorter boot time - just
> > a black screen
> > Tried booting into runlevel1 with the same result
>
> Try 'init 3' Ric
It's getting worse. Now, it chokes on X on the first try, right
after the kernel messages, when it tries to go into the splash
screen with the progress bar for the boot process - it's just
going black and stalling - there's a little LED hard drive
activity, but it doesn't go anywhere - just the black void...
--
Claude Jones
Brunswick, MD, USA
Try removing the rhgb from the kernel line.
10:07 a.m.
On Sun, 2006-10-29 at 09:23 -0500, Claude Jones wrote:
I tried booting into runlevel 3 the old way by typing "a"
when the
splash screen came up, and typing "3" at the prompt - that didn't
work
Not sure what you're doing by 'typing "3" at the prompt'. Just to
be
sure that you're doing what we expect - to boot into runlevel 3, I'd add
a 3 on the end of the kernel line.
You'd get to the point that you can see the stanza that GRUB is going to
use while booting, in the edit mode (by pressing the "e" key, I thought,
while in the GRUB boot menu screen). Then you'd see something somewhat
*like* the following.
title Fedora Core (2.6.17-1.2142_FC4)
root (hd0,0)
kernel /vmlinuz-2.6.17-1.2142_FC4 ro root=LABEL=/
initrd /initrd-2.6.17-1.2142_FC4.img
And you'd modify the kernel line to look like:
kernel /vmlinuz-2.6.17-1.2142_FC4 ro root=LABEL=/ 3
Then you'd try and boot (the "b" key, if I recall correctly).
--
(Currently testing FC5, but still running FC4, if that's important.)
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
10:16 a.m.
On Sun October 29 2006 11:07 am, Tim wrote:
Not sure what you're doing by 'typing "3" at the
prompt'.
Presumably, because you're still running FC4 - things are a bit
different, now.
Just
to be sure that you're doing what we expect - to boot into
runlevel 3, I'd add a 3 on the end of the kernel line.
I got a three appended to the end of the kernel line, just to make
this short. It doesn't work - it won't even start the first
instance of X now, it just goes to a black screen and stalls
after the initial Selinux and kernel messages.
--
Claude Jones
Brunswick, MD, USA
3:42 a.m.
On Sun, 29 Oct 2006 09:23:28 -0500, Claude Jones wrote:
I'm not seeing this exact issue, apologies if I missed it I
installed
NVidia drivers from Livna on a working FC6 On reboot, it gets all the
way to the second X start and the screen then just goes black and
nothing happens I tried booting into runlevel 3 the old way by typing
"a" when the splash screen came up, and typing "3" at the prompt -
that
didn't work Next time I typed "runlevel3" at the prompt, and that led to
same result as above, but in a much shorter boot time - just a black
screen Tried booting into runlevel1 with the same result Anyone else
encountered this?
It's a known problem with the beta drivers. You need this:
modprobe -r eeprom
as root, before X starts. How, exactly, you do this with your setup is
something else. I always boot to the command line and start X myself.
4:36 a.m.
Roo schrieb:
On Sun, 29 Oct 2006 09:23:28 -0500, Claude Jones wrote:
> I'm not seeing this exact issue, apologies if I missed it I installed
> NVidia drivers from Livna on a working FC6 On reboot, it gets all the
> way to the second X start and the screen then just goes black and
> nothing happens I tried booting into runlevel 3 the old way by typing
> "a" when the splash screen came up, and typing "3" at the prompt
- that
> didn't work Next time I typed "runlevel3" at the prompt, and that led
to
> same result as above, but in a much shorter boot time - just a black
> screen Tried booting into runlevel1 with the same result Anyone else
> encountered this?
It's a known problem with the beta drivers. You need this:
modprobe -r eeprom
as root, before X starts.
Is it that bad that we (livna developers) should integrate that into the
package? Anyone interested in doing that?
CU
thl
9:06 a.m.
>>>> "TL" == Thorsten Leemhuis
<fedora(a)leemhuis.info> writes:
TL> Is it that bad that we (livna developers) should integrate that
TL> into the package? Anyone interested in doing that?
I recall seeing a patch on the nvnews.net forum that obviated the need
to remove the module.
But this is only an issue with the 9xxx beta drivers; I didn't think
Livna shipped those in any case.
- J<
9:07 a.m.
On 10/31/06, Thorsten Leemhuis <fedora(a)leemhuis.info> wrote:
Roo schrieb:
> On Sun, 29 Oct 2006 09:23:28 -0500, Claude Jones wrote:
>
>> I'm not seeing this exact issue, apologies if I missed it I installed
>> NVidia drivers from Livna on a working FC6 On reboot, it gets all the
>> way to the second X start and the screen then just goes black and
>> nothing happens I tried booting into runlevel 3 the old way by typing
>> "a" when the splash screen came up, and typing "3" at the
prompt - that
>> didn't work Next time I typed "runlevel3" at the prompt, and that
led to
>> same result as above, but in a much shorter boot time - just a black
>> screen Tried booting into runlevel1 with the same result Anyone else
>> encountered this?
>
> It's a known problem with the beta drivers. You need this:
>
> modprobe -r eeprom
>
> as root, before X starts.
Is it that bad that we (livna developers) should integrate that into the
package? Anyone interested in doing that?
It would prolly make alot more sense to integrate the driver patch
which fixes the bug:
http://www.nvnews.net/vbulletin/showpost.php?p=996233&postcount=20
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama(a)gmail.com
LlamaLand http://netllama.linux-sxs.org
4:24 a.m.
Lonni J Friedman schrieb:
On 10/31/06, Thorsten Leemhuis <fedora(a)leemhuis.info> wrote:
>
> Roo schrieb:
>> On Sun, 29 Oct 2006 09:23:28 -0500, Claude Jones wrote:
>>
>>> I'm not seeing this exact issue, apologies if I missed it I installed
>>> NVidia drivers from Livna on a working FC6 On reboot, it gets all the
>>> way to the second X start and the screen then just goes black and
>>> nothing happens I tried booting into runlevel 3 the old way by typing
>>> "a" when the splash screen came up, and typing "3" at the
prompt - that
>>> didn't work Next time I typed "runlevel3" at the prompt, and
that led to
>>> same result as above, but in a much shorter boot time - just a black
>>> screen Tried booting into runlevel1 with the same result Anyone else
>>> encountered this?
>> It's a known problem with the beta drivers. You need this:
>>
>> modprobe -r eeprom
>>
>> as root, before X starts.
> Is it that bad that we (livna developers) should integrate that into the
> package? Anyone interested in doing that?
It would prolly make alot more sense to integrate the driver patch
which fixes the bug:
http://www.nvnews.net/vbulletin/showpost.php?p=996233&postcount=20
Done, updated kmod should be out in lvn-testing soon. The main packages
were also updated -- aiglx *shold* simply work after installing now.
There should be no need to modify the xorg.conf manually anymore.
CU
thl
6387
days inactive
6390
days old
15 comments
8 participants
participants (8)
-
Claude Jones -
Jason L Tibbitts III -
Jeff Vian -
Lonni J Friedman -
Ric Moore -
Roo -
Thorsten Leemhuis -
Tim