Andrei Popescu wrote:
> Michał Wróbel <[EMAIL PROTECTED]> wrote:
>> Anyway, I wanted to report that I am using nvidia-glx-legacy and
>> after I have upgraded my Debian Sid today, my Xorg refused to start
>> up after reboot. The log message was exactly the same as quoted below.
> Do you have any sp
Michał Wróbel <[EMAIL PROTECTED]> wrote:
> Anyway, I wanted to report that I am using nvidia-glx-legacy and
> after I have upgraded my Debian Sid today, my Xorg refused to start
> up after reboot. The log message was exactly the same as quoted below.
Do you have any special reason for using the l
First of all, I'd like to emphasize that I haven't read all the posts
related to this problem thoroughly, since there is probably more than one
reason of such behavior.
Anyway, I wanted to report that I am using nvidia-glx-legacy and after I
have upgraded my Debian Sid today, my Xorg refused to st
On Mon, Apr 23, 2007 at 05:30:57 +0800, John Verhoeven wrote:
>On Mon, 23 Apr 2007, Mauro Sacchetto wrote:
>> Ron Johnson wrote:
>> > # NVIDVER=1.0-9755
>> > # sh NVIDIA-Linux-x86-$NVIDVER-pkg1.run \
>> > --x-module-path=`X -showDefaultModulePath 2>&1 | cut -d, -f1` \
>> > --x-library-path=
Ron Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/23/07 04:30, Hugo Vanwoerkom wrote:
[snip]
The reason is explained:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419943
Ah. I compile my own kernel on a system and disable PARAVIRT.
The reason for its presence, to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/23/07 04:30, Hugo Vanwoerkom wrote:
[snip]
> The reason is explained:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419943
Ah. I compile my own kernel on a system and disable PARAVIRT.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/23/07 04:00, Magnus Therning wrote:
> On Mon, Apr 23, 2007 at 05:30:57 +0800, John Verhoeven wrote:
>> On Mon, 23 Apr 2007, Mauro Sacchetto wrote:
>>> Ron Johnson wrote:
# NVIDVER=1.0-9755
# sh NVIDIA-Linux-x86-$NVIDVER-pkg1.run \
Curt Howland wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 22 April 2007, Mauro Sacchetto <[EMAIL PROTECTED]>
was heard to say:
Ron Johnson wrote:
# NVIDVER=1.0-9755
# sh NVIDIA-Linux-x86-$NVIDVER-pkg1.run \
--x-module-path=`X -showDefaultModulePath 2>&1 | cut -d, -f1`
\
On Mon, Apr 23, 2007 at 05:30:57 +0800, John Verhoeven wrote:
>On Mon, 23 Apr 2007, Mauro Sacchetto wrote:
>> Ron Johnson wrote:
>> > # NVIDVER=1.0-9755
>> > # sh NVIDIA-Linux-x86-$NVIDVER-pkg1.run \
>> > --x-module-path=`X -showDefaultModulePath 2>&1 | cut -d, -f1` \
>> > --x-library-path=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/22/07 17:32, Curt Howland wrote:
> On Sunday 22 April 2007, Mauro Sacchetto <[EMAIL PROTECTED]>
> was heard to say:
>> Ron Johnson wrote:
>>> # NVIDVER=1.0-9755
>>> # sh NVIDIA-Linux-x86-$NVIDVER-pkg1.run \
>>> --x-module-path=`X -showDefaul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 22 April 2007, Mauro Sacchetto <[EMAIL PROTECTED]>
was heard to say:
> Ron Johnson wrote:
> > # NVIDVER=1.0-9755
> > # sh NVIDIA-Linux-x86-$NVIDVER-pkg1.run \
> > --x-module-path=`X -showDefaultModulePath 2>&1 | cut -d, -f1`
> > \ --x-li
On Mon, 23 Apr 2007, Mauro Sacchetto wrote:
> Ron Johnson wrote:
> > # NVIDVER=1.0-9755
> > # sh NVIDIA-Linux-x86-$NVIDVER-pkg1.run \
> > --x-module-path=`X -showDefaultModulePath 2>&1 | cut -d, -f1` \
> > --x-library-path=`X -showDefaultLibPath 2>&1`
>
> I had the same trouble. In any case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/22/07 15:41, Mauro Sacchetto wrote:
> Ron Johnson wrote:
>> # NVIDVER=1.0-9755
>> # sh NVIDIA-Linux-x86-$NVIDVER-pkg1.run \
>> --x-module-path=`X -showDefaultModulePath 2>&1 | cut -d, -f1` \
>> --x-library-path=`X -showDefaultLibPath 2>&1
Ron Johnson wrote:
> # NVIDVER=1.0-9755
> # sh NVIDIA-Linux-x86-$NVIDVER-pkg1.run \
> --x-module-path=`X -showDefaultModulePath 2>&1 | cut -d, -f1` \
> --x-library-path=`X -showDefaultLibPath 2>&1`
I had the same trouble. In any case, I think
it's a not normal situation... It's a bug!
M.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/21/07 21:40, Hueseyin Koese wrote:
> Curt Howland schrieb:
>> Magnus Therning <[EMAIL PROTECTED]> wrote:
>>
Still wondering why the nvidia module isn't being detected.
>>> I can report the same problem on one of my systems. I'm holding off
On Sat, Apr 21, 2007 at 20:03:08 -0400, Curt Howland wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Magnus Therning <[EMAIL PROTECTED]> wrote:
>
>> >Still wondering why the nvidia module isn't being detected.
>
>> I can report the same problem on one of my systems. I'm holding off
>> o
El Diumenge 22 Abril 2007, Curt Howland va escriure:
> Someone else wrote earlier that he had to downgrade xserver-xorg-core,
> but he wasn't absolutely clear that it fixed the problem.
In my case seems clear: after downgrade xorg works :)
xserver-xorg-core 2:1.3.0.0.dfsg-1 -> 2:1.1.1-21
Before
Curt Howland schrieb:
> Magnus Therning <[EMAIL PROTECTED]> wrote:
>
>>> Still wondering why the nvidia module isn't being detected.
>
>> I can report the same problem on one of my systems. I'm holding off
>> on updating my other system until there are reports of this being
>> solved.
>
> S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Magnus Therning <[EMAIL PROTECTED]> wrote:
> >Still wondering why the nvidia module isn't being detected.
> I can report the same problem on one of my systems. I'm holding off
> on updating my other system until there are reports of this being
> s
On Sat, Apr 21, 2007 at 15:48:51 -0400, Curt Howland wrote:
>>(II) LoadModule: "nvidia"
>>(WW) Warning, couldn't load module nvidia
>>(II) UnloadModule: "nvidia"
>>(EE) Failed to load module "nvidia" (module does not exist, 0)
>
>Ron Johnson, Jr. suggested:
>/usr/lib/xorg/modules/drivers
>
>Ok, I l
(II) LoadModule: "nvidia"
(WW) Warning, couldn't load module nvidia
(II) UnloadModule: "nvidia"
(EE) Failed to load module "nvidia" (module does not exist, 0)
Ron Johnson, Jr. suggested:
/usr/lib/xorg/modules/drivers
Ok, I looked there and found nvidia_drv.o
All the rest of the files are *.so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Curt Howland wrote:
> On 4/21/07, BartlebyScrivener <[EMAIL PROTECTED]> wrote:
>> But I had a similar issue after a routine Etch update. I found the
>> answer by following this:
>>
>> http://forums.debian.net/viewtopic.php?t=10812
>>
>> error message
On Sat, Apr 21, 2007 at 14:13:08 -0400, Curt Howland wrote:
> On 4/21/07, BartlebyScrivener wrote:
>> But I had a similar issue after a routine Etch update. I found the
>> answer by following this:
>>
>> http://forums.debian.net/viewtopic.php?t=10812
>>
>> error message was FATAL module Nvidia not
El Dissabte 21 Abril 2007, Curt Howland va escriure:
> Any ideas where to look?
I've downgraded:
xserver-xorg-core 2:1.3.0.0.dfsg-1 -> 2:1.1.1-21
(but in my case «nv» driver work :?)
--
Benjamí
http://blog.bitassa.cat
.
On 4/21/07, BartlebyScrivener <[EMAIL PROTECTED]> wrote:
But I had a similar issue after a routine Etch update. I found the
answer by following this:
http://forums.debian.net/viewtopic.php?t=10812
error message was FATAL module Nvidia not found
The problem is that it worked this morning, but
On Apr 21, 12:20 pm, "Curt Howland" <[EMAIL PROTECTED]> wrote:
> So this morning I made certain that apt wouldn't remove anything this
> time, and everything looked fine. It seemed that Sid had gotten over
> the initial "OHMYGOD" that happens after a stable is released.
>
> There were lots of KDE u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/21/07 12:02, Curt Howland wrote:
> So this morning I made certain that apt wouldn't remove anything this
> time, and everything looked fine. It seemed that Sid had gotten over
> the initial "OHMYGOD" that happens after a stable is released.
>
>
So this morning I made certain that apt wouldn't remove anything this
time, and everything looked fine. It seemed that Sid had gotten over
the initial "OHMYGOD" that happens after a stable is released.
There were lots of KDE updates again, so I closed X and did the update
from the console.
Xorg
28 matches
Mail list logo
