Hi there,
My Thinkpad T61 Laptop comes with the following nVidia GPU:
lenz@thebe:~> lspci | grep -i nvidia
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1)
According to the README and the online docs, this chip is not a "legacy GPU"
yet and it should be supported by the latest driver (180.29)
http://www.nvidia.com/object/IO_18897.html (supported GPUs for the 180.29 driver)
http://www.nvidia.com/object/IO_32667.html (legacy GPUs)
However, the following driver is currently installed:
lenz@thebe:~> rpm -qa | grep nvidia
nvidia-gfxG01-kmp-pae-173.14.16_2.6.25.20_0.1-2.1
x11-video-nvidiaG01-173.14.16-2.1
According to http://www.nvidia.com/object/unix.html this is a "legacy GPU"
driver. I tried to install the 180.29 driver instead (nvidia-gfxG02), but that
one fails to load:
Mar 17 11:00:13 thebe kernel: NVRM: The NVIDIA probe routine was not called
for 1 device(s).
Mar 17 11:00:13 thebe kernel: NVRM: This can occur when a driver such as
rivafb, nvidiafb or
Mar 17 11:00:13 thebe kernel: NVRM: rivatv was loaded and obtained ownership
of the NVIDIA
Mar 17 11:00:13 thebe kernel: NVRM: device(s).
Mar 17 11:00:13 thebe kernel: NVRM: Try unloading the rivafb, nvidiafb or
rivatv kernel module
Mar 17 11:00:13 thebe kernel: NVRM: (and/or reconfigure your kernel without
rivafb/nvidiafb
Mar 17 11:00:13 thebe kernel: NVRM: support), then try loading the NVIDIA
kernel module again.
Mar 17 11:00:13 thebe kernel: NVRM: No NVIDIA graphics adapter probed!
I had to revert to the nvidia-gfxG01 driver to return to a functional
configuration.
So I am confused now. Shouldn't the Quadro NVS 140M be supported by the 180.29
driver series, as the documentation and README states? Or am I missing something?
As I am using KDE4, I would like to be able to use the latest driver as this
one supposedly fixes some of the screen update performance issues that I am
experiencing.
Any help would be appreciated. Thanks!
Bye,
LenZ
--
------------------------------------------------------------------
Lenz Grimmer <lenz(a)grimmer.com> -o)
[ICQ: 160767607 | Jabber: LenZGr(a)jabber.org] /\\
http://www.lenzg.org/ V_V
Dear Henrique,
thanks for your help!!
>
> It might, but we have to be careful.
>
> So, first question: you do know that the X40 has two brightness ramps, one
> which is active while on AC, and the other, much darker, which becomes
> active while on battery, right? Are you sure what you were looking at was
> a third brightness ramp, even darker than the usual "darker" ramp?
>
yes
> Did the system let you go back to that way-too-dark level by pressing the
> less-bright button?
>
>
no
--
To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org
HI,
Another observation I had with my X40 was that suddenly I was able to
darken the screen much further than before by pressing the illumination
intensity buttons. Actually the illumination of the screen seemed to
have made a jump to very dark. While I thought that the screen had died
again, I quickly pressed the #brighter# button, and one button press of
the "brighterrr" button was sufficient to but it back to the lowest
normal level which I was used to.
That is not normal either, is it?
Does it give a clue of what is happening?
I have experienced that only once since the upgrade to suse 11.1.
best,
Volker
Volker Krueger wrote:
> Dear all,
>
> thanks for the information so far.
>
> As a matter of fact, I do not use compiz.
>
> I have posted my email also on the suse forum. Let's see what they will
> say about this.
>
> So far I couldn't imagine that a software bug could indeed distroy the
> screen like this...
>
> best,
> Volker
>
>
> Henrique de Moraes Holschuh wrote:
>
>> On Tue, 10 Mar 2009, Karsten König wrote:
>>
>>
>>> A google search does turn up alot about this, for example compiz / general
>>> composite seems to blame sometimes, I just set it back on and could resume
>>> fine, don't know about the time it didn't work for me.
>>>
>>>
>> Don't get normal "screen doesn't come up on resume" bug reports mixed with
>> "screen harware was destroyed on resume" ;-) The first class is annoying
>> but expected. The later is *extremely* grave and has happened at least once
>> in the past.
>>
>>
>>
>>> The system itself is not dead, not even the graphics driver it looks like,
>>> just the screen power or something.
>>> http://forums.fedoraforum.org/showthread.php?t=205270
>>>
>>>
>> Yeah, it looks like it does something Bad to the backlight PWM control,
>> since it hits LEDs (inverter-less) and CCFL (inverter-based) boxes alike.
>>
>>
>>
>>> Looks like a very confusing issue =(
>>>
>>>
>> That it is, that it is...
>>
>>
>>
--
To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org
So.. i can't update my system (xorg-*, libdrm, mesa packages) through
Yast - http://download.opensuse.org/repositories/X11%
3a/XOrg/openSUSE_11.1/
because i get black screen after boot...
who can help me?
ps. in february and earlier i update my system and it was O.K... but now
(since marth) i have this trouble..
----
i use openSUSE 11.1 x86_64 and Intel X3100...
--
To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org
Hi,
I have an observation which worries me big-time!!
I have bough in January a Thinkpad X200s. On that machine, the LED-based
illumination of the LCD died last friday for the third time. So far, I
was thinking that this is a HW issue.
HOWEVER, while the X200s is not working I am now using my X40 again. I
have upgraded to suse 11.1 and ... guess what: After standby the
illumination of the screen remained black!!!!!! This problem is totally
random: I had it on standby with 11.1 before and it woke up fine...
I was more than glad that it lit again after reboot, but I have NEVER
experienced that before on the X40!!!
While the X200s has even on-site support the X40 would be dead for good,
if the screen dies, and i would be very sad...
Is there someone else who has experienced something similar with the
X40? Since when does that happen? Has it anything to do with the
thinkpad_acpi?
If I am the only one with opensuse and noone else has these problems, I
guess it'll be time to switch to a different distribution...
thanks a whole lot in advance,
Volker
--
To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org
Hello,
For almost a week now, the updates in the Xorg repo
[http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_11.1/] do not
work for me. When applied, X will not start up - the screen flashes and the
system is unresponsive.
In order to get X to work again, I need to downgrade to the following packages
(from the openSUSE OSS repo I believe):
xorg-x11-driver-input-7.4-11.5@i586
xorg-x11-server-7.4-17.3@i586
Once I downgrade, X works perfectly.
I have been experiencing this with two different systems, both using openSUSE
11.1 with KDE 4.2 (also from the openSUSE repo):
1. Custom built AMD Ahtlon64 X2 6000+ using a nVidia 8600GT
2. MacbookPro using a ATI X1600
The following is the only (EE) line that appears in the Xorg.0.log:
(II) LoadModule: "freetype"
(WW) Warning, couldn't open module freetype
(II) UnloadModule: "freetype"
(EE) Failed to load module "freetype" (module does not exist, 0)
The rest of the log appears to be similar to the log file generated from a
successful X session.
I believe that in the past, with other repos, that this problem is caused by a
refactoring of the RPMs? Is that the case here? If so, what new rpms do I need
to have installed? Below is the list of all xorg-x11 rpms I have installed on
my system:
xorg-x11-7.4-17.10@i586
xorg-x11-devel-7.4-21.9@i586
xorg-x11-driver-input-7.4-11.5@i586
xorg-x11-driver-video-7.4-62.2@i586
xorg-x11-driver-video-radeonhd-1.2.4_121202_4e89726-6.28@i586
xorg-x11-driver-video-unichrome-20081229-5.26@i586
xorg-x11-fonts-7.4-1.32@noarch
xorg-x11-fonts-core-7.4-1.32@noarch
xorg-x11-fonts-devel-7.4-1.23@i586
xorg-x11-libICE-7.4-4.1@i586
xorg-x11-libICE-devel-7.4-4.1@i586
xorg-x11-libSM-7.4-1.26@i586
xorg-x11-libSM-devel-7.4-1.26@i586
xorg-x11-libX11-7.4-12.1@i586
xorg-x11-libX11-devel-7.4-12.1@i586
xorg-x11-libXau-7.4-1.23@i586
xorg-x11-libXau-devel-7.4-1.23@i586
xorg-x11-libXdmcp-7.4-1.23@i586
xorg-x11-libXdmcp-devel-7.4-1.23@i586
xorg-x11-libXext-7.4-4.8@i586
xorg-x11-libXext-devel-7.4-4.8@i586
xorg-x11-libXfixes-7.4-1.24@i586
xorg-x11-libXfixes-devel-7.4-1.24@i586
xorg-x11-libXmu-7.4-1.26@i586
xorg-x11-libXmu-devel-7.4-1.26@i586
xorg-x11-libXp-7.4-1.25@i586
xorg-x11-libXp-devel-7.4-1.25@i586
xorg-x11-libXpm-7.4-1.27@i586
xorg-x11-libXpm-devel-7.4-1.27@i586
xorg-x11-libXprintUtil-7.4-1.26@i586
xorg-x11-libXprintUtil-devel-7.4-1.26@i586
xorg-x11-libXrender-7.4-1.24@i586
xorg-x11-libXrender-devel-7.4-1.24@i586
xorg-x11-libXt-7.4-1.26@i586
xorg-x11-libXt-devel-7.4-1.26@i586
xorg-x11-libXv-7.4-1.25@i586
xorg-x11-libXv-devel-7.4-1.25@i586
xorg-x11-libfontenc-7.4-1.23@i586
xorg-x11-libfontenc-devel-7.4-1.23@i586
xorg-x11-libs-7.4-21.9@i586
xorg-x11-libxcb-7.4-7.2@i586
xorg-x11-libxcb-devel-7.4-7.2@i586
xorg-x11-libxkbfile-7.4-1.25@i586
xorg-x11-libxkbfile-devel-7.4-1.25@i586
xorg-x11-proto-devel-7.4-10.1@i586
xorg-x11-server-7.4-17.3@i586
xorg-x11-util-devel-7.4-1.22@i586
xorg-x11-xauth-7.4-17.10@i586
xorg-x11-xtrans-devel-7.4-5.1@i586
x11-tools-0.1-167.7@noarch
x11-video-nvidiaG02-180.29-0.1@i586
Cheers,
Alvin
--
To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org
On Mar 09, 09 14:24:02 +0300, Pavel Lepeev wrote:
> hm.. can you give me link to this bug?
>
> > On Mar 07, 09 13:46:27 +0300, Pavel Lepeev wrote:
> > > So.. what should I do with x3100? Every time i get black screen ^(
> > > Any sugguestions?
> >
> > radeonhd? Bug #483244
https://bugzilla.novell.com/show_bug.cgi?id=483244
So what driver do you have (check xorg.conf, "Device" section).
Matthias
--
Matthias Hopf <mhopf(a)suse.de> __ __ __
Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat(a)mshopf.de
Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de
--
To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org
So.. what should I do with x3100? Every time i get black screen ^(
Any sugguestions?
--
To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org
Doesn't work with Intel X3100 (openSUSE 11.1-x86_64 + all
updates from X11:XOrg repo).
After update - i get black screen after system boot. :(
--
To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org
On March 5, 2009 11:20:44 am Matthias Hopf wrote:
> On Mar 04, 09 13:28:48 -0400, Alvin Beach wrote:
> > > > For almost a week now, the updates in the Xorg repo
> > > > [http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_11.1/]
> > > > do not work for me. When applied, X will not start up - the screen
> > > > flashes and the system is unresponsive.
> > > >
> > > > In order to get X to work again, I need to downgrade to the following
> > > > packages (from the openSUSE OSS repo I believe):
> >
> > As requested, I have attached the Xorg.0.log.old from the failed attempt.
> > The only error I see relates to freetype. Perhaps, there is something
> > else though that I am missing.
>
> I'm not seeing any crash in the log. Sure you had the right one attached?
>
> Matthias
I believe so. What X fails to start, I see the busy cursor and nvidia logo,
then the screen flickers and the busy cursor and logo appear again. This cycle
simply continues over and over.
Sometimes, if I repeated and quickly press Ctrl+Alt+Del I can get the system
to reboot cleanly. Otherwise, I have to hit the reboot button.
I will update the RPMs again and try to capture a new Xorg.0.log.old file. I
believe the .old files is the one you want. When I reboot and go to runlevel 3
and manually downgrade the offending RPMs, When I switch to init 5 I believe
the failed Xorg.0.log gets renamed to Xorg.0.log.old, correct?
Alvin
--
To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org