Re: Ctrl+alt+Fn not showing consoles

rudu wrote:
Le 26/04/2010 20:55, Hugo Vanwoerkom a écrit :

rudu wrote:
Le 26/04/2010 19:43, Hugo Vanwoerkom a écrit :

rudu wrote:
Running squeeze on AMD64 arch, my system recently stopped to let me
get my consoles after I hit the ctrl+alt+Fn keys (n = 1 to 6).

When did it stop?

I can't be sure but that may coincide with that kernel*-trunk thing, when I had to go back to the nv driver as I couldn't get the proprietary Nvidia driver to compile with my new kernel.
FWIW, a few more details :
$ uname -a
Linux birdynam 2.6.32-3-amd64 #1 SMP Wed Feb 24 18:07:42 UTC 2010 x86_64 GNU/Linux
$ lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce 9400 GT] (rev a1)

So are you still running nv?

and what was the driver that wouldn't compile?
I run x86-195.36.15 on the latest Sid kernel and it compiles just fine, but I don't (yet) have a AMD64 system.

Excerpt from /var/log/nvidia-installer.log :
Using: nvidia-installer ncurses user interface
WARNING: Skipping the runlevel check (the utility `runlevel` failed to run).
-> License accepted.
-> Installing NVIDIA driver version 195.36.15.
-> Performing CC sanity check with CC="cc".
-> Performing CC version check with CC="cc".
-> The CC version check failed:

The compiler used to compile the kernel (gcc 4.3) does not exactly match the
current compiler (gcc 4.4). The Linux 2.6 kernel module loader rejects kern
el modules built with a version of gcc that does not exactly match that of t
he compiler used to build the running kernel.

If you know what you are doing and want to ignore the gcc version check, sel
ect "No" to continue installation. Otherwise, select "Yes" to abort install
ation, set the CC environment variable to the name of the compiler used to c
ompile your kernel, and restart installation. Abort now? (Answer: Yes)
ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find suggestions
on fixing installation problems in the README available on the Linux
driver download page at

Indeed. Forget this if it is beating a dead horse, but did you have gcc-4.3 + gcc-4.4 both installed? I did and I set the symlink gcc to gcc-4.3 and that got rid of the message.

Alternatively you can set CC to gcc-4.3 and it will compile.
195.36.15 is a lot better than nv and I am pretty sure will get rid of your problems.
I haven't tried nouveau.


To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • [RFC][PATCH-2.6] Clean up and merge compiler-*.h
    ... the kernel headers in include/linux to include/linux-abi. ... * Common definitions for all gcc versions go here. ... -/* Some compiler specific definitions are overwritten here ...
  • [rfc] built-in native compiler for Linux?
    ... Perhaps we should fork off gcc and ship Linux with its own ... This way we can optimize it for the kernel and not worry ... I didnt suggest forking GCC. ... What i think makes sense is to build a _new_ precompiler / compiler ...
  • Re: [RFC] Stupid tracepoint ideas
    ... gcc forbids jumping outside of inline assembly statements. ... but for some reason no kernel developer I know seems to be ... There are some kernel developers who are also GCC developers - but i ... I think the solution is obvious: the kernel needs its own compiler. ...
  • Re: Use of C99 int types
    ... the compiler. ... > Except the kernel wants to be optimized and work and use what features ... And where exactly are linux and libc when compiling code for an ... Just to make the bloody point GCC is not dependent on Linux in any way ...
  • [-mm patch] more updates for the gcc >= 3.2 requirement
    ... - - Make sure you have gcc 2.95.3 available. ... - some parts of the kernel, ... -The Red Hat gcc 2.96 compiler subtree can also be used to build this tree. ... -extern inline void prefetch ...