Seth:
It was with the "working" kernel - set #9 in this bug report, actually - the kernel with your commit reverted.
I tried with the broken one, both by ssh-ing and connecting it to an external monitor, but had no luck: could not ssh into the machine and the external monitor displayed a black screen with the ubuntu logo (the splash screen that usually hides the boot messages)
I am now in a 3.0.0-14 boot and right now/proc/cmdline has
I confirmed these are the same options as I see in Grub in the broken 15 kernel.
I've also just grep-ed i915 in modprobe.d/* but no file has any reference to it. I suppose these files wouldn't be changed based on the kernel that you choose on startup (would they?), so the broken 3.0.0-15 that is installed probably doesn't have them either.
What else can be done so we can figure out what is wrong?
Seth:
It was with the "working" kernel - set #9 in this bug report, actually - the kernel with your commit reverted.
I tried with the broken one, both by ssh-ing and connecting it to an external monitor, but had no luck: could not ssh into the machine and the external monitor displayed a black screen with the ubuntu logo (the splash screen that usually hides the boot messages)
I am now in a 3.0.0-14 boot and right now/proc/cmdline has
BOOT_IMAGE= /boot/vmlinuz- 3.0.0-14- generic root=UUID= 6ab741a0- 9959-4edd- ba60-0cdc28c819 de ro quiet splash acpi_backlight= vendor vt.handoff=7
I confirmed these are the same options as I see in Grub in the broken 15 kernel.
I've also just grep-ed i915 in modprobe.d/* but no file has any reference to it. I suppose these files wouldn't be changed based on the kernel that you choose on startup (would they?), so the broken 3.0.0-15 that is installed probably doesn't have them either.
What else can be done so we can figure out what is wrong?
Cheers