I signed the fglrx driver with sudo /usr/src/linux-headers-$(uname --kernel-release)/scripts/sign-file sha256 fglrx_private_key.priv fglrx_x509.der $(modinfo --filename fglrx-updates)
I then reinstalled 3.13.0-92 with 'sudo apt-get install linux-signed-image-generic' as instructed. Since this created a new fglrx_updates.ko at /lib/modules/3.13.0-92-generic/updates/dkms/fglrx_updates.ko, I signed that too, with sudo /usr/src/linux-headers-3.13.0-92-generic/scripts/sign-file sha256 fglrx_private_key.priv fglrx_x509.der /lib/modules/3.13.0-92-generic/updates/dkms/fglrx_updates.ko It appears the module is indeed signed: $ hexdump -C /lib/modules/3.13.0-92-generic/updates/dkms/fglrx_updates.ko | tail -n 5 00f7c5b0 4d 6f 64 75 6c 65 20 73 69 67 6e 61 74 75 72 65 |Module signature| 00f7c5c0 20 61 70 70 65 6e 64 65 64 7e 0a | appended~.| And the key is listed by mokutil --list-enrolled. And yet, I still have the same symptom: if I boot to 3.13.0-92 rather than 3.13.0-91, I can get tty1, but Ctrl+Alt+F7 gives me a black screen with a blinking cursor. I never heard of debconf before today. Google tells me that debconf is related to answering configuration questions while installing packages. Is that related? There weren't any questions when installing linux- signed-image-generic. Were there supposed to be? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603655 Title: After update, xorg will not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
