Your message dated Wed, 25 Aug 2010 05:53:46 +0200
with message-id <[email protected]>
and subject line Re: nvidia-graphics-drivers in experimental (version
1.0.9746-2) crashes console
has caused the Debian Bug report #409202,
regarding nvidia-graphics-drivers in experimental (version 1.0.9746-2) crashes
console
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.)
--
409202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409202
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nvidia-glx
Version: 1.0.9746-2
Package: nvidia-kernel-source
Version: 1.0.9746-2
with the new nvidia binary driver in experimental i experienced
problems with the console. i have a laptop with a
nVidia Corporation NV43 [GeForce Go 6600] (rev a2) graphic card,
and until 1.0.9631-1 everything works perfect (compiz too), but
when using latest driver, the console shows some interesting
colours when switching back from X11. there is
absolutely nothing readable, just nice colors. i tried with kernel
2.6.19.1 and 2.6.19.2, with vesa framebuffer and the nvidia kernel
framebuffer, without fb, all the same.
CPU: Intel(R) Pentium(R) M processor 1.73GHz
Linux gusti 2.6.19.2 #1 Wed Jan 31 20:24:03 CET 2007 i686 GNU/Linux
ii nvidia-glx 1.0.9746-2
NVIDIA binary XFree86 4.x driver
ii nvidia-kernel-2.6.19.2 1.0.9746-2+2.6.19.2-10.00.Custom
NVIDIA binary kernel module for Linux 2.6.19
ii nvidia-kernel-common 20051028+1
NVIDIA binary kernel module common files
ii nvidia-kernel-source 1.0.9746-2
NVIDIA binary kernel module source
ii nvidia-settings 1.0+20060516-3
Tool of configuring the NVIDIA graphics driv
lspci -vv
01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce Go 6600]
(rev a2) (prog-if 00 [VGA])
Subsystem: Wistron Corp. Unknown device 2073
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at a0000000 (32-bit, non-prefetchable) [size=64M]
Region 1: Memory at c0000000 (64-bit, prefetchable) [size=128M]
Region 3: Memory at 90000000 (64-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at c8000000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Express Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <512ns, L1 <4us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0
Link: Latency L0s <256ns, L1 <4us
Link: ASPM L0s L1 Enabled RCB 128 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x16
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting
thanx&bye...masc.
--
_______________________________________________
Search for products and services at:
http://search.mail.com
Powered by Outblaze
--- End Message ---
--- Begin Message ---
Hi,
this bug was reported against a very old version of the
nvidia-graphics-drivers package in Debian. We asked some months ago whether
this problem is still reproducible in the current version of the driver, but
didn't get any new information. Therefore, I assume the problem has been
solved by a new upstream release and/or packaging updates and I'll close this
report now.
If you are still able to reproduce this problem with current versions of the
driver, kernel and X.Org, feel free to provide additional information and
reopen this report.
Andreas
--- End Message ---
