Re: X bother consoles
On 06/21/2011 04:00 PM, Camaleón wrote:
On Tue, 21 Jun 2011 15:37:21 +0200, maderios wrote:
On 06/21/2011 01:27 PM, Camaleón wrote:
I would be nice that you tell us what piece of hardware did you change.
I can guess it's the VGA card but it can be a fan or your sata dvd
recorder, who knows :-P
I changed everything (P8P67 motherboard, Intel CoreI7, ....) except
keyboard, mouse and screen
Oh... more items than I thought.
You mean that nouveau driver works fine?
It works fine with KMS, but it doesnt when KMS is disabled.
When you disabled KMS, what driver was loading the X server?
"Nouveau" driver
So let's recap.
You want to use nvidia closed driver and get it to work on terminal
consoles, right?
As you already have found the culprit (nvidia driver) and given that
this closed driver is completey up to nvidia, I would start by using
the most up-to-date version (275.09.07) and search in Google about
similar cases, like these, to find a possible workaround:
http://askubuntu.com/questions/45929/virtual-terminals-messed-up-with-proprietary-nvidia-graphics-driver
Giving a whirl to Xorg logs may also help.
As I said above, I tested also with a Matrox P690 PCIe (+vesa driver)
Why vesa? Matrox cards should have their own set of X drivers.
The P690 matrox driver story is an old and famous story ... Matrox
provided out of date (2009 may) driver source on his site. It doesnt
work with recent kernels.
Mga driver (free matrox driver) worked perfectly with my old G550/AGP
Matrox card + "old" motherboard.
I changed this hardware and the problems came......
New hardware: MB sandy bridge + Intel Core I7 + GC nvidia quadro 600
graphic card and I got exactly same display problem => the problem is
not with the nvidia driver
The problem can be present with both, vesa and nvidia.
The problem is present with vesa, nouveau, nvidia and matrox...
My monitor is a LCD (EIZO SX2462W). I tested with another monitor, an
old CRT and I got same problem.
Nothing useful at logs?
The syslog seems "normal", no error message
May be something wrong at the end of the Xorg.0.log with Wheezy ?
With Squeeze, I got the same message "ACPI: failed to connect to the
ACPI event"
99.915] (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/input/input5/event5"
[ 99.915] (II) XINPUT: Adding extended input device "Logitech
Logitech USB Keyboard" (type: KEYBOARD)
[ 99.915] (**) Option "xkb_rules" "evdev"
[ 99.915] (**) Option "xkb_model" "evdev"
[ 99.915] (**) Option "xkb_layout" "fr"
[ 99.915] (**) Option "xkb_variant" "oss"
[ 99.915] (EE) Logitech Logitech USB Keyboard: failed to initialize
for relative axes.
[ 99.915] (II) Logitech Logitech USB Keyboard: initialized for
absolute axes.
[ 99.915] (**) Logitech Logitech USB Keyboard: (accel) keeping
acceleration scheme 1
[ 99.915] (**) Logitech Logitech USB Keyboard: (accel) acceleration
profile 0
[ 99.915] (**) Logitech Logitech USB Keyboard: (accel) acceleration
factor: 2.000
[ 99.915] (**) Logitech Logitech USB Keyboard: (accel) acceleration
threshold: 4
[ 99.916] (II) config/udev: Adding input device PC Speaker
(/dev/input/event3)
[ 99.916] (II) No input driver/identifier specified (ignoring)
[ 104.015] (WW) NVIDIA(GPU-0): Eizo SX2462W (DFP-2): Failed to set
DisplayPort power state
[ 18285.080] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
[ 18285.108] (WW) NVIDIA(GPU-0): Eizo SX2462W (DFP-2): Failed to set
DisplayPort power state
[ 18285.212] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event
daemon; the daemon
[ 18285.212] (II) NVIDIA(0): may not be running or the
"AcpidSocketPath" X
[ 18285.212] (II) NVIDIA(0): configuration option may not be set
correctly. When the
[ 18285.212] (II) NVIDIA(0): ACPI event daemon is available, the
NVIDIA X driver will
[ 18285.212] (II) NVIDIA(0): try to use it to receive ACPI event
notifications. For
[ 18285.212] (II) NVIDIA(0): details, please see the
"ConnectToAcpid" and
[ 18285.212] (II) NVIDIA(0): "AcpidSocketPath" X configuration
options in Appendix B: X
[ 18285.212] (II) NVIDIA(0): Config Options in the README.
[ 29821.023] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
[ 29821.054] (WW) NVIDIA(GPU-0): Eizo SX2462W (DFP-2): Failed to set
DisplayPort power state
[ 29821.164] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event
daemon; the daemon
[ 29821.164] (II) NVIDIA(0): may not be running or the
"AcpidSocketPath" X
[ 29821.164] (II) NVIDIA(0): configuration option may not be set
correctly. When the
[ 29821.164] (II) NVIDIA(0): ACPI event daemon is available, the
NVIDIA X driver will
[ 29821.164] (II) NVIDIA(0): try to use it to receive ACPI event
notifications. For
[ 29821.164] (II) NVIDIA(0): details, please see the
"ConnectToAcpid" and
[ 29821.164] (II) NVIDIA(0): "AcpidSocketPath" X configuration
options in Appendix B: X
[ 29821.164] (II) NVIDIA(0): Config Options in the README.
Greetings
Maderios
Reply to: