On Tue, Jul 31, 2012 at 02:53:49PM -0000, Alberto Milone wrote: > > debian/grub.d/11_custom_cmdline: this is NIHing the grub-gfxpayload > > blacklist handling already implemented in grub via /usr/share/grub- > > gfxpayload-lists/blacklist. Instead of shipping a file under > > /etc/grub.d which hard-codes disabling of vt handoff even when the > > hardware is not present, please add a blacklist file to this directory > > like the ones in the grub-gfxpayload-lists package and call 'update- > > grub-gfxpayload' (instead of update-grub') from your package's postinst > > and postrm (on remove/purge only, and guarded with || true). Creating > > the blacklist should be straightforward, you're already processing a > > list of PCI IDs in debian/rules.
> > You should add a dependency on grub-gfxpayload-lists for this. > The main reason why I didn't use this was that it gives us a black > screen until we get a 1 or 2 seconds plymouth screen and then we get to > the lightdm screen. At least this is what happens on our machines. Ok. When you do it the other way, manually disabling vt.handoff but leaving gfxmode=keep, what do you see instead / what do you expect to see? I guess that you might see a *purple* screen for a few seconds, followed by a flicker and plymouth, followed by lightdm. But if this difference between purple and black is important, please file a bug against the grub2 package to discuss. This combination of gfxmode=keep + no vt_handoff is not tested in Ubuntu, and I don't think it should be introduced in a hardware-specific way. > > debian/lightdm.conf: why is this necessary? including this file in the > > package means that merely installing the driver package causes unity3d > > to stop working out of the box, even if this video hardware is not > > present. (The same reason not to hard-disable vt.handoff.) Does the > > Unity auto-detection of 3D support not work correctly on this hardware > > for some reason? If it's *really* confirmed to be needed, then ok; but > > we should definitely use the autodetection if possible. > The driver's OpenGL implementation is, well, partial ;). This means that > Unity will start (as the driver passes the Unity's tests) but you won't > see anything useful on your screen. Right, understood... :) > > - debian/copyright references http://dep.debian.net/deps/dep5/, which is > > an obsolete draft. This should ideally be updated to conform to > > copyright-format 1.0 (http://www.debian.org/doc/packaging-manuals > > /copyright-format/1.0/). > Ok, I'm attaching the new diff with your changes (thanks for all your > work, BTW) and mine. Looks good to me. Please reupload. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025720 Title: Package cedarview-drm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1025720/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
