Re: Using biosdevname by default?
On Thu, Aug 23, 2012 at 04:23:53PM +0100, Colin Watson wrote: > On Tue, Feb 07, 2012 at 01:50:19AM +, Colin Watson wrote: > > 2) At UDS, consider defaulting to biosdevname=1 for 12.10. Presumably > > by that point we would have reasonably substantial experience with > > it as a result of 1). > biosdevname is now enabled by default on 12.10 alternate/server > installs. This will cause some machines to use different (and more > stable across reboots) network interface names. Thanks, Colin! Are we expecting this to be enabled for the desktop image as well, for consistency? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Using biosdevname by default?
On Tue, Feb 07, 2012 at 01:50:19AM +, Colin Watson wrote: > 2) At UDS, consider defaulting to biosdevname=1 for 12.10. Presumably > by that point we would have reasonably substantial experience with > it as a result of 1). biosdevname is now enabled by default on 12.10 alternate/server installs. This will cause some machines to use different (and more stable across reboots) network interface names. If you see network configuration failures during installation and you're doing preseeded installations, check whether you've hardcoded the previous network interface name in your preseed file. If that's the case, you can try one of the following: * Use "IPAPPEND 2" in your pxelinux.cfg, and remove any netcfg/choose_interface preseeding. This will cause pxelinux to pass a BOOTIF= parameter to the installer corresponding to the interface used for PXE-booting, which d-i will use to select the same network interface for use during installation. * If you are not using pxelinux, or if you need to select a different interface for use during installation, you may preseed netcfg/choose_interface to a hardware MAC address in the form aa:bb:cc:dd:ee:ff to use an interface with that hardware address. * Find out the biosdevname-generated name for your network interface (remove the preseeding for netcfg/choose_interface and you should be shown a list of the available network interfaces; or use 'ip link show' after biosdevname has done its work) and use that instead. * As a last resort, pass the "biosdevname=0" boot parameter to return to the previous scheme for naming network interfaces. -- Colin Watson [cjwat...@ubuntu.com] -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Unity Going Forward
On 20 August 2012 19:20, Colin Law wrote: > On 20 August 2012 00:30, Jason Warner wrote: >> Hi Colin - >> >> On Sat, Aug 18, 2012 at 6:08 AM, Colin Law wrote: >>> >>> On 17 August 2012 01:51, Jason Warner wrote: >>> > ... >>> > But there is a cost to this decision. Unity 2D fit a very specific use >>> > case >>> > in very low-end and non-GPU accelerated hardware. By consolidating to >>> > Unity >>> > using LLVMpipe for this specific use case we expect to see some >>> > regressions >>> > in systems supported. This means that a certain class of hardware will >>> > no >>> > longer be supported to run Unity. Unity will run on all GPUs that >>> > support >>> > OpenGL 2.0. The earliest GPUs that meet this requirement are at least 5 >>> > years old[1]. Even so, we know some subset of cards and hardware that >>> > could >>> > previously run Unity 2D will no longer be able to run Unity. >>> >>> A heads up to make sure that the case of dual monitors with i945 >>> graphics chipset (and possibly others) has been considered. That >>> chipset will only run 3d if the virtual desktop is less than 2048 >>> pixels wide so when an external monitor is plugged in only unity-2d >>> will run at the moment. If the external monitor is not plugged in >>> then 3d is ok. Having removed unity-2d the software will have to cope >>> with plugging in the external monitor in some way. Note that this is >>> an issue for laptops made only a few years ago (Toshiba Satellite for >>> example). >> >> >> Is there an bug for this? if not, please file one so we can track it. >> Thanks. > > https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1039051 That bug has been marked as a duplicate of #824099, Max GL texture size can break multi-head [1], which is marked Won't Fix. Can anyone explain why this capability will not be provided by llvmpipe on Quantal? [1] https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/824099 Colin -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Unity Going Forward
Colin Watson [2012-08-23 13:12 +0100]: > On Fri, Aug 17, 2012 at 10:21:18AM +0930, Jason Warner wrote: > > [2] - We know Unity is showing some graphical corruption inside a VM. Work > > to correct this has been done but not landed yet. > > Do you have a bug reference for this? I'm unable to work on ubiquity in > KVM right now, which is my normal working environment for installer > development, and I'd like to know what bug report I should keep an eye > on. I think that's https://bugs.launchpad.net/compiz/+bug/1021104 Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Unity Going Forward
On Fri, Aug 17, 2012 at 10:21:18AM +0930, Jason Warner wrote: > [2] - We know Unity is showing some graphical corruption inside a VM. Work > to correct this has been done but not landed yet. Do you have a bug reference for this? I'm unable to work on ubiquity in KVM right now, which is my normal working environment for installer development, and I'd like to know what bug report I should keep an eye on. -- Colin Watson [cjwat...@ubuntu.com] -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
