Launchpad has imported 13 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=857300.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-09-14T04:35:34+00:00 Adam wrote: This bug splits off the problem described in comments #12 through #20 of https://bugzilla.redhat.com/show_bug.cgi?id=848305 . After plymouth was updated to 0.8.7 - partly to fix that bug - a serious issue showed up with several NVIDIA adapters: when booting normally to a desktop, runlevel '5', plymouth enabled, all as normal, either the DM doesn't really appear at all (though it claims to be running), or it appears but somewhat corrupted; if you can get through the DM to the desktop, it will also be corrupted. Booting to runlevel 3 and starting the DM service manually, or dropping 'rhgb' from the kernel parameters, acts as a workaround. airlied says he has found the fix for this: https://patchwork.kernel.org/patch/1455231/ . He plans to run it by Ben and then submit it upstream. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/14 ------------------------------------------------------------------------ On 2012-09-14T04:38:18+00:00 Adam wrote: Proposing as Beta blocker (conditional infringement of the 'live must boot' and 'installed system must boot' criteria in the case of certain NVIDIA adapters. We should commonbugs this for Alpha, as Alpha has the bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/15 ------------------------------------------------------------------------ On 2012-09-14T06:02:37+00:00 Xavier wrote: Created attachment 612728 F18 Alpha Live KDE, loading sessiion Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/16 ------------------------------------------------------------------------ On 2012-09-14T06:04:34+00:00 Xavier wrote: Created attachment 612729 F18 Alpha Live KDE, session ready (Device notifier offering usb stick) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/17 ------------------------------------------------------------------------ On 2012-09-14T06:45:58+00:00 Xavier wrote: Captures made on Asus V1S laptop with GeForce 8600M GT (512MB VRAM). Alpha (RC3) is the first of GNOME/KDE Live TCs/RCs to run plymouth charge correctly on this hardware (bug 855557), despite leading to the present defect. Dropping 'rhgb' from the kernel parameters, acts as a workaround as you mentioned (raw tty messaging instead of any animation, then no graphic corruption, KDE loads fine and Desktop Effects are enabled by default). Safe graphics (vesa) acts as yet another workaround, loading plymouth text animation. All other routes -- except vesa -- lead to extreme slowness (bug 855560) on this hardware, for both GNOME and KDE Live spins. LXDE Live Alpha (RC3) just works as default, without any workaround, running plymouth charge. Is the present defect, only affecting desktop acceleration ? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/18 ------------------------------------------------------------------------ On 2012-09-14T17:54:50+00:00 Patrick wrote: I had this issue when installing TC5 and could not make heads of tails of it. I stumbled on a fix when I installed F17 and then "upgraded" to F18. When I boot with the old F17 kernel (3.5.3-1.fc17.x86_64) everything works perfectly, but with the F18 3.6 kernels I am lucky to get to a GDM and if I do it is a horrid mess. Booting to runlevel 3 and then launching the GDM did not help. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/19 ------------------------------------------------------------------------ On 2012-09-14T18:48:54+00:00 Adam wrote: I've tested airlied's fix and it works for me. The scratch build I used to test is here: http://koji.fedoraproject.org/koji/taskinfo?taskID=4482706 feel free to grab it before it expires and check that it works for you too. thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/20 ------------------------------------------------------------------------ On 2012-09-16T13:13:12+00:00 Josh wrote: Patch is picked up in kernel-3.6.0-0.rc5.git3.1.fc18 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/23 ------------------------------------------------------------------------ On 2012-09-17T08:59:35+00:00 Kamil wrote: On an installed system I never reproduced the graphics corruption, the system froze instead after login. kernel-3.6.0-0.rc5.git3.1.fc18 fixed the issue for me. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/24 ------------------------------------------------------------------------ On 2012-09-17T19:28:16+00:00 Fedora wrote: kernel-3.6.0-0.rc6.git0.2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kernel-3.6.0-0.rc6.git0.2.fc18 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/27 ------------------------------------------------------------------------ On 2012-09-18T19:21:21+00:00 Fedora wrote: Package kernel-3.6.0-0.rc6.git0.2.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.6.0-0.rc6.git0.2.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14273/kernel-3.6.0-0.rc6.git0.2.fc18 then log in and leave karma (feedback). Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/46 ------------------------------------------------------------------------ On 2012-09-23T05:03:35+00:00 Fedora wrote: kernel-3.6.0-0.rc6.git0.2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/49 ------------------------------------------------------------------------ On 2012-10-22T18:30:02+00:00 Xavier wrote: May I confirm too, this is fixed on the hardware I reported. Tested Fedora-18-Beta-TC6-x86_64-Live-KDE.iso Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/73 ** Changed in: linux Status: Unknown => Fix Released ** Changed in: linux Importance: Unknown => High ** Bug watch added: Red Hat Bugzilla #848305 https://bugzilla.redhat.com/show_bug.cgi?id=848305 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1043518 Title: live cd is unusable due to video degradation with the splash boot option enabled Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Invalid Status in linux source package in Quantal: Fix Released Status in plymouth source package in Quantal: Invalid Bug description: All images after 08/15 have become unusable, either to install from or to use a live session. Images from 08/15 & earlier work fine as does the install itself. Attached are 2 possible screens which seem to vary depending on which partition grub is configured on in a multi-boot system (12.04 & 12.10 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0 Uname: Linux 3.5.0-9-generic x86_64 ApportVersion: 2.5.1-0ubuntu3 Architecture: amd64 Date: Wed Aug 29 16:21:08 2012 InstallCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120813.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CasperVersion: 1.323 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth DistroRelease: Ubuntu 12.10 LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120912) MachineType: Dell Inc. XPS M1330 Package: plymouth 0.8.4-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz -- ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz -- ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Tags: quantal running-unity TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 3.5.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1043518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
