Why would 'CTRL+ALT+F1' lock up Lucid x_64?

[TheBigAmbulance]

I just put my new rig together (noted in my profile). Lucid 10.4 x64 went in fairly well. Had some struggles with the Nvidia driver, but finally got it. The did a 'apt-get update ; apt-get upgrade -y ; apt-get dist-upgrade -y'. So I'm at the latest and greatest available for Lucid right now.

When I press 'CTRL+ALT+F1', my system stops responding.

Anyone have a recommendation on where I can start checking? I can bring the system up to a normal kdm session, but I can't start a new terminal.

[dibl]

Re: Why would 'CTRL+ALT+F1' lock up Lucid x_64?

When I press 'CTRL+ALT+F1', my system stops responding.

What do you mean "stops responding"? The expected behavior, on Ctrl-Alt-F1, is for the system to switch from console 7, which is the X display, to console #1, which is a tty console, which should be showing a login prompt where you can log in. Ctrl-Alt-F7 should take you back to the X display.

Tell more -- what are you seeing?

[oshunluvr]

Re: Why would 'CTRL+ALT+F1' lock up Lucid x_64?

This is usually caused by Plymouth (the blue boot screen) and the video drivers. Search the forum, there's several how-to's. I wrote one a while ago and there's a couple later ones. Once you have it working right you'll have a hi-res terminal and the boot graphics will be hi-res too.

[TheBigAmbulance]

Re: Why would 'CTRL+ALT+F1' lock up Lucid x_64?

The system comes up fully running kdm and I get a Kubuntu screen. But let's say I want to manually install the Nvidia drivers. I need to switch to a console screen and stop the kdm service. When I press C+A+F1, the system becomes unresponsive (i.e. no mouse, no keyboard, no nothing) requiring a reboot.

I'm using Nvidia 256.44 x64 drivers...

[TheBigAmbulance]

Re: Why would 'CTRL+ALT+F1' lock up Lucid x_64?

@oshunluvr,

Is this the procedure your talking about?

Step 1: install v86d
sudo apt-get install v86d

Step 2: edit /etc/default/grub as "root"
- Replace the following line (line number 9):

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

with this one (matching resolution appropriate to my screen):

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap"

- Replace the following line (line number 18):

#GRUB_GFXMODE=640x480

with this one:

GRUB_GFXMODE=1280x1024

Save the file and close it!

Step 3: edit /etc/initramsfs-tools/modules as root
Add the following line at the end of the file:

uvesafb mode_option=1280x1024-24 mtrr=3 scroll=ywrap

Save the file and close it!

Step 4: Run in terminal:

echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
sudo update-grub2
sudo update-initramfs -u

Then reboot....

This give Plymouth and the console the proper screen resolution for a monitor.