Your message dated Sun, 06 Jun 2010 10:48:23 +0200
with message-id <[email protected]>
and subject line Re: nvidia-kernel-2.6.26-1-amd64: Doesn't do suspend to ram
with 4GB RAM
has caused the Debian Bug report #499151,
regarding nvidia-kernel-2.6.26-1-amd64: Doesn't do suspend to ram with 4GB RAM
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
499151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499151
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Reportbug-Version: 3.45
X-Debbugs-Cc: [email protected]
Package: nvidia-kernel-2.6.26-1-amd64
Version: 173.14.09-5+2.6.26-5
Severity: normal
The currently installed modules don't work with software suspend.
On activating via
echo mem > /sys/power/state
the screen goes dark, the fan slows down a bit, then runs again normally;
only the screen keeps dark.
Num-Lock doesn't work; SysRq-SAK works to kill the X server, then I can
go (blindly) to a tty and login to shutdown and similar.
Xorg.0.log says:
(WW) NVIDIA(GPU-0): Failed to determine GPU name
(EE) NVIDIA(GPU-0): Failed to determine chip capabilities
(II) UnloadModule: "nvidia"
(II) UnloadModule: "wfb"
(II) UnloadModule: "fb"
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
Booting with mem=3200M works, so it seems to be some 4GB addressing#
problem in the driver.
I don't expect much help, as this is a proprietary module; but maybe
others find this message and see what can be done.
Part of my dmesg:
Command line: root=/dev/md0 ro mem=3200M
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e5000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000abfb0000 (usable)
BIOS-e820: 00000000abfb0000 - 00000000abfbe000 (ACPI data)
BIOS-e820: 00000000abfbe000 - 00000000abff0000 (ACPI NVS)
BIOS-e820: 00000000abff0000 - 00000000ac000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000150000000 (usable)
If there's some other help, so that the RAM can be used, I'd like to hear it.
Thank you.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/1 CPU core)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages nvidia-kernel-2.6.26-1-amd64 depends on:
ii nvidia-kernel-common 20080825+1 NVIDIA binary kernel module common
Versions of packages nvidia-kernel-2.6.26-1-amd64 recommends:
ii linux-image-2.6.26-1-amd64 2.6.26-5 Linux 2.6.26 image on AMD64
nvidia-kernel-2.6.26-1-amd64 suggests no packages.
-- no debconf information
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
--- End Message ---
--- Begin Message ---
tags 499151 - moreinfo + unreproducible
thanks
Philipp Marek wrote:
> I'm sorry.
> I can't test that anymore, as the graphics subsystem was replaced.
No problem, I'm closing the bug now as unreproducible. If you run across
the problem again, feel free to reopen or open a new report.
Andreas
--- End Message ---
