On Saturday 16 May 2009 17:33:28 Florian Kulzer wrote: > > > > > On Fri, May 15, 2009 at 14:33:32 -0400, Ed Jabbour wrote: > > > > > > On Friday 15 May 2009 13:34:45 Florian Kulzer wrote: > > > > > > > > > On Thu,14.May.09, 20:57:29, Ed Jabbour wrote: > > > > > > > > > > I can't get to a console from X. I.e., alt-ctrl-f1, 2 > > > > > > > > > > .... get me only a black screen with no prompt. The same > > > > > > > > > > thing happens if I try "console login" from kdm. inittab > > > > > > > > > > is the default. Graphics driver NVidia 173.14.09. Any > > > > > > > > > > hints, pointers, appreciated. > > > > [snip] > > > > > > > grep -Ei 'vesa|nvidia|frame|buffer' /var/log/syslog > > [...] > > > OK. I rebooted and ran it again. Not sure it's relevant, but: > > > > May 16 16:45:32 Ajax kernel: [ 0.000000] ACPI: FACP 7BF649BA, 00F4 (r3 > > NVIDIA MCP67-M 6040000 PTL_ F4240) > > May 16 16:45:32 Ajax kernel: [ 0.000000] ACPI: DSDT 7BF5C13A, 880C (r1 > > NVIDIA MCP67 6040000 MSFT 3000000) > > May 16 16:45:32 Ajax kernel: [ 0.084002] Security Framework > > initialized May 16 16:45:45 Ajax kernel: [ 26.584309] NVRM: loading > > NVIDIA UNIX x86 Kernel Module 173.14.09 Wed Jun 4 23:43:17 PDT 2008 > > Which kernel do you run? You do not seem to have any active framebuffer; > with standard Debian kernels you should see something like this: [snip] > > Do you see any framebuffer devices at all? > > $ ls -l /dev/fb* > crw-rw---- 1 root video 29, 0 2009-05-16 19:43 /dev/fb0
Nope. No fb anything in /dev. [snip] > > If you rolled your kernel then you have to watch out for vesafb and > nvidiafb; for comparison, here are the settings for the standard > 2.6.29-2-amd64 Debian kernel: > > $ grep -E 'VESA|NVIDIA' /boot/config-$(uname -r) > CONFIG_FB_BOOT_VESA_SUPPORT=y > CONFIG_FB_UVESA=m > CONFIG_FB_VESA=y > CONFIG_FB_NVIDIA=m > # CONFIG_FB_NVIDIA_I2C is not set > # CONFIG_FB_NVIDIA_DEBUG is not set > CONFIG_FB_NVIDIA_BACKLIGHT=y > CONFIG_BACKLIGHT_MBP_NVIDIA=m I haven't rolled my own since my gentoo days. I run 2.6.26-2-686. It looks like yours but for CONFIG_FB_BOOT_VESA_SUPPORT, which is not an option at all. Not that it's not set - it doesn't exist in the kernel. If you look at Joel Roth's post, it doesn't seem to be in his, either, and he's facing the same problem. Is it that config that generates the fb*? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org