After recent updates, X will no longer start with the Nvidia driver on maverick (related to "pat"/"nopat" kernel option)

i just discovered that adding "nopat" to the kernel command line causes this problem to go away. Using PAT before didn't cause a problem, though, so there must be a bug somewhere.

Please read this thread:

https://patchwork.kernel.org/patch/120327/

This apparently has landed in 2.6.32.2 (commit http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.36.y.git;a=commit;h=57cbe30dcafee32ac897b5313008fe9ee4c33b2b), I will see if I can remove "nopat" after building+upgrading.

@Daniel
I guess in message #7 it should 2.6.36.2 instead of 2.6.32.2

@Manfred, yes you're right: I was talking about 2.6.36.2.

However, the patch on its own did not help. I had to change:
GRUB_GFXPAYLOAD_LINUX=keep
to
GRUB_GFXPAYLOAD_LINUX=1280x1024
in /etc/default/grub and re-run update-grub.

Somehow "keep" was also causing the virtual consoles to not be available (apart from VT7 where kdm was running).

Using 1280x1024 explicitly fixed it for me, although I am using GRUB_GFXMODE=1280x1024 anyway.

Michael Marley, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]