Launchpad has imported 52 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=650949.
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 2010-11-08T13:26:25+00:00 Jan wrote: Description of problem: Find smolt profile of this machine at: http://www.smolts.org/client/show/pub_01375d10-2b7a-4d39-a71e- 89d7f4789d55 Version-Release number of selected component (if applicable): xorg-x11-drv-nouveau-0.0.16-11.20100826git065576d.fc14.x86_64 How reproducible: Always Steps to Reproduce: 1. Try to boot Fedora 14 x86_64 2. Watch funny distorted graphics 3. That's it Actual results: No normal function Expected results: working graphics Additional info: The new Macbook Air3,1,1 is based on nVidia MCP89 chipset. Some other problems too, in separate BZs. I also tried booting with 'nomodeset' to no avail. I am not interested in 3D graphics ATM, just plain simple 2D. According to nouveau pages the chip in question should work. So either Apple made some special stuff or there is a bigger problem hidden here. Booting with vesa works, but cannot use the native display resolution of 1366x768 so screen looks ugly. Using the nvidia proprietary drivers from rpmfusion seems to work a bit better. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/0 ------------------------------------------------------------------------ On 2010-11-08T22:48:17+00:00 Ben wrote: Can you please update to xorg-x11-drv- nouveau-0.0.16-13.20101010git8c8f15c.fc14 (http://koji.fedoraproject.org/koji/buildinfo?buildID=199899) as this problem *should* probably be fixed. If it's still not after that, can you fetch me your dmesg output after the "funny" graphics appear please. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/1 ------------------------------------------------------------------------ On 2010-11-09T08:14:06+00:00 Jan wrote: OK, tried that version. Short summary of findings. When using modeset, garbled screen (like broken TV). With nomodeset, boots into VESA resolution 1024x768, so does not recognize/use native resolution of screen, X.org.0.log attached. Will go back to garbled screen and get you a clean dmesg in a few hours. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/2 ------------------------------------------------------------------------ On 2010-11-09T08:15:40+00:00 Jan wrote: Created attachment 459028 X.org.0.log - using nouveau on a MBA3,1,1 - using VESA not native resolution Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/3 ------------------------------------------------------------------------ On 2010-11-09T08:56:30+00:00 Jan wrote: Using xorg-x11-drv-nouveau-0.0.16-13.20101010git8c8f15c.fc14 with nomodeset breaks the resume part of suspend/resume. This does work when using the proprietary nvidia driver from rpmfusion. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/4 ------------------------------------------------------------------------ On 2010-11-09T09:58:20+00:00 Jan wrote: Using xorg-x11-drv-nouveau-0.0.16-13.20101010git8c8f15c.fc14 with modeset enabled in grub results in garbled screen (also console is garbled). I took two pictures that show console ,mode and X with garbled screen. I also took dmesg and X.org.0.log form the garbled setup and added them here. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/5 ------------------------------------------------------------------------ On 2010-11-09T09:59:46+00:00 Jan wrote: Created attachment 459060 The X.org.0.log of the MBA311 running with modeset resulting in garbled screen Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/6 ------------------------------------------------------------------------ On 2010-11-09T10:00:19+00:00 Jan wrote: Created attachment 459061 dmesg of the MBA311 running with modeset resulting in garbled screen Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/7 ------------------------------------------------------------------------ On 2010-11-09T10:02:47+00:00 Jan wrote: Created attachment 459063 Screenshot of garbled console when using nouveau on MBA311 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/8 ------------------------------------------------------------------------ On 2010-11-09T10:03:27+00:00 Jan wrote: Created attachment 459065 Screenshot of garbled X when using nouveau on MBA311 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/9 ------------------------------------------------------------------------ On 2010-11-09T11:58:16+00:00 Jan wrote: Also noticed that with nouveau running (albeit in VESA 1024x768 mode only) seems to really heat up the MBA. The fan starts spinning at top speed after a few minutes of simply having the box sitting nest to me, with no load or applications running - not even a screensaver. This does not happen with the proprietary nvidia drivers. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/10 ------------------------------------------------------------------------ On 2010-11-09T13:37:12+00:00 Jan wrote: WRT suspend/resume breakage with nouveau - I followed the steps in http://fedoraproject.org/wiki/KernelCommonProblems#Suspend.2FResume_failure and came up with: [ 1.052877] hash matches drivers/base/power/main.c:562 Again, when using the prorietary nvidia drivers by installing kmod- nvidia from rpmfusion suspend/resume Just Works. Should this be seperated into a new Bugzilla or is it related to nouveau? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/11 ------------------------------------------------------------------------ On 2010-11-16T11:57:02+00:00 Jan wrote: I have updated to kernel-2.6.35.8-59.fc14.x86_64 from koji, which fixes backlight control and a few other thing, see BZ #651019 for more details. So ATM I only have two problems with nouveau on MBA3: - No support of native resolution (seems to fallback to VESA) - nouveau breaks the resume part of suspend/resume Should I try rawhide version next? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/12 ------------------------------------------------------------------------ On 2010-11-16T21:20:28+00:00 Ben wrote: To clarify, you are *not* using nouveau if you use "nomodeset. And suspend/resume is *not* going to work with VESA. Ok. Can i get a dmesg log of booting with "drm.debug=14 nouveau.reg_debug=0x0200 log_buf_len=1M", and also the vbios image. While running nouveau it can be retrieved from /sys/kernel/debug/dri/0/vbios.rom, you may need to mount debugfs (mount -t debugfs none /sys/kernel/debug) first. I suspect nouveau has some issue with the eDP panel. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/13 ------------------------------------------------------------------------ On 2010-11-17T09:51:11+00:00 Jan wrote: OK. Done that. Note however I could only do it in runlevel 1. X doesn't start, screen is blank and I cannot switch to a VT in runlevel 5. Attached both dmesg and vbios image. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/14 ------------------------------------------------------------------------ On 2010-11-17T09:51:55+00:00 Jan wrote: Created attachment 461031 dmesg with nouveau debug Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/15 ------------------------------------------------------------------------ On 2010-11-17T09:52:23+00:00 Jan wrote: Created attachment 461032 vbios rom file Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/16 ------------------------------------------------------------------------ On 2010-12-14T13:52:22+00:00 Marcus wrote: Hi all. I have tried out the provided nouveau updated but the screen resolution is still not detected correctly. Kind Regards Marcus Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/17 ------------------------------------------------------------------------ On 2010-12-14T13:53:28+00:00 Marcus wrote: Created attachment 468611 edid information retreived from nvidia-settings on a macbook air 3.1 11.6' Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/18 ------------------------------------------------------------------------ On 2010-12-20T13:02:38+00:00 Jan wrote: So now we are 1.5 months later, we have provided all info asked for and this bus is still on status NEW and no progress to be seen. What can I do to help, speed things up? Send my MBA to someone willing to fix? I *want* to use Fedora, but this is a showstopper. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/19 ------------------------------------------------------------------------ On 2011-02-21T16:26:38+00:00 Rob wrote: Hi, I'm experiencing this as well. I have a macbook air and am located in the Raleigh office. I've been working with different modesettings, and have had a bit of progress. The fact that everything seems to work reasonably well with nomodeset configured makes me wonder if a different modeset would work correctly. The nvidia drive does work, but kills quite a bit of functionality (regarding external displays. I plan to use this for presentation purposes when possible). If anybody in the raleigh office would like to take a look, please let me know. Also if you're in westford I'll be up there next month. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/20 ------------------------------------------------------------------------ On 2011-02-22T15:34:09+00:00 Matěj wrote: *** Bug 662735 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/21 ------------------------------------------------------------------------ On 2011-02-22T15:53:20+00:00 Rob wrote: Created attachment 480163 Updated fedora-gfx-test-week build /var/log/messages Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/22 ------------------------------------------------------------------------ On 2011-02-22T15:53:57+00:00 Rob wrote: Created attachment 480164 Updated fedora-gfx-test-week build Xorg.0.log Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/23 ------------------------------------------------------------------------ On 2011-04-29T19:13:06+00:00 Matěj wrote: Isn't this actually a duplicate of bug 650949? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/34 ------------------------------------------------------------------------ On 2011-04-29T19:45:19+00:00 Matthew wrote: Given that this *is* bug 650949... Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/35 ------------------------------------------------------------------------ On 2011-04-30T22:35:07+00:00 Chris wrote: I don't see a clear indicator that any of these are EFI-based boot attempts, but rather CSM BIOS. This is disconcerting because I've already found EFI booting on Apple hardware to be nearly a dead end with all but newer hardware, and even with newer hardware it can be problematic. So if the CSM BIOS isn't adequate either on newer hardware, then we're really screwed. I'm frustrated that Apple has not abandoned their proprietary Intel EFI 1.10 + GOP (UEFI 2.x) + some Apple stuff, in favor of full UEFI 2.x support. From my perspective this is more their domain and responsibility to fix. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/36 ------------------------------------------------------------------------ On 2011-05-10T19:16:42+00:00 Papadeas wrote: Is there anything that we can do in order to have this fixed? (provide any more info etc?) It is really sad to have proprietary drivers loaded. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/37 ------------------------------------------------------------------------ On 2011-05-10T20:13:16+00:00 Chris wrote: I'd like to be wrong and see this work, but I remain suspicious that this is Apple's responsibility to provide adequate hardware information in their CSM BIOS, which they may not, therefore nouveau can't do the right thing. Or Apple needs to move to a standard implementation of UEFI with UEFI drivers which they may not be able to do depending on their licensing with Nvidea, or their own priorities - running anything other than Mac OS on Apple hardware I perceive to be a rather low priority for Apple. They tend to do the minimum required. But it's an interesting point that the CSM BIOS is adequate for Windows Vista and 7 to get the necessary information in order to support this same hardware. *shrug* Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/38 ------------------------------------------------------------------------ On 2011-05-10T20:19:09+00:00 Papadeas wrote: Chris is there anyway we can be sure it is our lack of info for CSM BIOS that is blocking this? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/39 ------------------------------------------------------------------------ On 2011-05-10T20:27:30+00:00 Matthew wrote: Nobody's worked out what the problem is, so assigning it to Apple's CSM implementation is premature. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/40 ------------------------------------------------------------------------ On 2011-05-10T20:32:51+00:00 Chris wrote: Need to hear from Ben Skeggs, or someone who knows what nouveau needs and what it's not getting. I know enough to get into trouble. There may be just enough info in the BIOS for the proprietary Windows Nvidia driver to function correctly, whereas it wouldn't surprise me if nouveau needs more information because it's not in as much a position to make assumptions about hardware as either Apple or Nvidia. Pure speculation on my part. But it is consistent with Apple's minimalist approach to supporting Windows, UEFI and even BIOS. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/41 ------------------------------------------------------------------------ On 2011-05-10T20:37:47+00:00 Papadeas wrote: So does it makes sense to assign that to Ben, or flag that as "info needed" from him? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/42 ------------------------------------------------------------------------ On 2011-05-10T20:45:02+00:00 Chris wrote: Not my area. Appears to already be assigned to Ben. Honestly at this point I'd consider downloading F15 beta and see if the problem is reproducible there, if anything has changed behavior wise, and then report back. Or wait for F15 final and test it there. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/43 ------------------------------------------------------------------------ On 2011-05-10T22:02:18+00:00 Ben wrote: The status currently on these is that in an EFI boot, we can't even detect the display (Matthew Garrett confirmed recently the NVIDIA binary driver can't either). With a BIOS boot, it ends up garbled. It's likely I could fix the latter if I had physical access to one, the problem hasn't been obvious to me from logs and traces however. It'd be a lot of trial and error to find the cause before fixing it. As for the former problem, my guess is it can be solved somehow, might be tricky not being able to see how NVIDIA manage it, because, they can't :) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/44 ------------------------------------------------------------------------ On 2011-05-11T12:54:22+00:00 Papadeas wrote: Ben, I am willing to be the guinea pig for testing it :) So far the latter is the only thing I managed to have. Please let me know what I can provide more on test results. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/45 ------------------------------------------------------------------------ On 2011-12-02T21:00:17+00:00 Adam wrote: *** Bug 751147 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/46 ------------------------------------------------------------------------ On 2011-12-02T23:54:53+00:00 Peter wrote: You might be interested in https://bugs.launchpad.net/ubuntu/+source /xserver-xorg-video-nouveau/+bug/898784 which also affects Fedora 16. With the 320M there has been two steps forward; resume from suspend and external monitor now works, and one step backward; the laptop display is now corrupted. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/47 ------------------------------------------------------------------------ On 2011-12-06T00:56:43+00:00 Adam wrote: Is there any newer news on this, Ben? Any prospect of support for these Macs in F17? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/48 ------------------------------------------------------------------------ On 2011-12-06T01:30:03+00:00 Chris wrote: I think the title change is very confusing. I am only having problems with MacbookPro 4,1, (Nvidia Geforce 8600M GT) with EFI boot. I do not have problems with CSM/BIOS boot (except for the limitations that come with CSM/BIOS booting which is another matter). Also, in the EFI boot case, at least the kernel is booting, and functioning so the title is misleading in that regard as well. It's just that when nouveau loads, the computer becomes (unintentionally) headless. But ssh works. While the manifestation is different on the Macbook Pro 8,2 (this is a 2011 model with both Intel HD Graphics 3000 and AMD Radeon HD 6490M or 6750M), there is also a problem with EFI boot on this hardware, while CSM/BIOS boot appears to function as expected. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/49 ------------------------------------------------------------------------ On 2011-12-06T01:32:25+00:00 Chris wrote: Oops, I got this bug confused with another one. Disregard complaint about title changing. Still, it needs to be more clear because my MBP4,1 is not experiencing garbled video with CSM/BIOS booting. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/50 ------------------------------------------------------------------------ On 2011-12-06T01:42:52+00:00 Adam wrote: chris: well, the bug actually initially reported here is the corrupted video when booted CSM: "Steps to Reproduce: 1. Try to boot Fedora 14 x86_64 2. Watch funny distorted graphics 3. That's it" the issue with EFI booting only appears later. So if we were to treat them as separate bugs, if anything, this bug would be for the corruption-with-CSM-boot and we'd need a separate bug for EFI-boot- fails. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/51 ------------------------------------------------------------------------ On 2011-12-06T02:00:36+00:00 Chris wrote: If we are constraining the bug to that of the original poster, the hardware is a MacBookAir 3,1 which has Nvidia GeForce 320M graphics, and the boot method is CSM/BIOS. I have a MacBookPro 4,1 (Nvidia Geforce 8600M GT graphics) which is listed in the title of this bug, and I do not experience distorted graphics when booting CSM/BIOS. I cannot vouch for the MacBookPro 3,1 but Wikipedia's extensive listing of specs says it too has Nvidia Geforce 8600M GT graphics. FWIW, these are three completely distinct Apple models: MacBook 3,1 MacBookPro 3,1 MacBookAir 3,1 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/52 ------------------------------------------------------------------------ On 2011-12-06T02:46:17+00:00 Matthew wrote: Please separate these issues by GPU (vendor and model). The NVAF issue on the Macbook Air 3,1 and 3,2 is now fixed - there may be different issues with different models. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/53 ------------------------------------------------------------------------ On 2011-12-07T17:32:31+00:00 Adam wrote: Okay. I'll un-dupe the other bug and make that the one for 8600M. So: if you have a system with the GeForce 320M graphics - which we believe covers the Macbook Air 3,1,1 and 3,2 - stay with this bug (and mjg believes there's a fix in Rawhide?) If you have a system with 8600M GT graphics - appears to include Macbook Pro 3,1 and Macbook Pro 4,1 - please go to https://bugzilla.redhat.com/show_bug.cgi?id=751147 . Sorry for the confusion. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/54 ------------------------------------------------------------------------ On 2012-01-20T17:17:27+00:00 Peter wrote: Now that I could finally boot a live CD of F17 I must unfortunately report that the screen corruption on GeForce 320M (MacBook Air 3,2) is still there. For a photo of what it looks like see comment 4 in this bug report https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+bug/898784. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/55 ------------------------------------------------------------------------ On 2012-03-12T16:38:00+00:00 Mads wrote: F16 with 3.2.9-1.fc16.x86_64 on MacBookAir3,1 "NVIDIA NVaf" booted with EFI and grub2 now works for me - both graphics and wireless. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/58 ------------------------------------------------------------------------ On 2012-04-19T16:01:57+00:00 Peter wrote: For me this bug is fixed in kernel 3.3, but has reappeared in kernel 3.4-rc3. Upstream report is at https://bugzilla.kernel.org/show_bug.cgi?id=42984. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/59 ------------------------------------------------------------------------ On 2012-06-28T11:34:32+00:00 Maarten wrote: Fixed is backported from 3.5rc to 3.4.3+ and 3.2.21+ Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/60 ------------------------------------------------------------------------ On 2013-04-03T18:30:30+00:00 Fedora wrote: This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/61 ------------------------------------------------------------------------ On 2015-01-09T16:25:17+00:00 Fedora wrote: This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/65 ------------------------------------------------------------------------ On 2015-02-17T13:27:43+00:00 Fedora wrote: Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746174/comments/66 ** Changed in: nouveau-kernel-source (Fedora) Status: Unknown => Won't Fix ** Changed in: nouveau-kernel-source (Fedora) Importance: Unknown => High ** Bug watch added: Red Hat Bugzilla #751147 https://bugzilla.redhat.com/show_bug.cgi?id=751147 ** Bug watch added: Linux Kernel Bug Tracker #42984 https://bugzilla.kernel.org/show_bug.cgi?id=42984 -- 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/746174 Title: 10de:08a2 Screen corruption on Macbook Air (Nvidia 320M) Status in Linux: Invalid Status in linux package in Ubuntu: Invalid Status in nouveau-kernel-source package in Fedora: Won't Fix Bug description: Binary package hint: xorg I just got a Macbook Air and tried to install Ubuntu on it. Booting up the main install disk resulted in some crazy screen corruption, and the left inch and a half or so was completely useless, since it did not appear to update other than randomly moving bits (described below). It is hard to describe. It looked as if I had a normal desktop, but overlayed on top of it was a series of 3cm vertical 'bands'. There was a staircasing effect between bands, as a small horizontal line connected them but fell between successive bands. On top of all this, pixels seemed to 'move' awkwardly, like they were dancing around after too many beers. If I had to guess, I would say my video card and display device disagreed on the resolution, and on top of that somebody Snow Crashed my desktop. Switching back to the console via ctrl-alt-f1 does not fix the problem; my console was messed up in similar ways, though it looks more like just plain Snow Crash then. There was no color in the console, of course, so I guess it just must be hard to see any banding artifacts, even if they are still there. I guess is the wrong place to mention it, but as a side note: the xorg folks semi-recently made "DontZap" the default, i.e. disabled ctrl- alt-backspace. Please make it the default on Ubuntu, it's a real pain to debug this kind of thing when you can't kill X. The fix is simple: remove "quiet splash" from the grub boot lines. Everything works then -- with both the nvidia proprietary drivers and nouveau. It might be important to note that my screen seemed fine until X started up, so it seems to be some poor interaction between the splash screen (I guess) and X's KMS? This is 10.10, maverick. I didn't try an update after installing from the CD, because it was too difficult to see what I was typing. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xorg 1:7.5+6ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.06 Mon Sep 13 04:29:19 PDT 2010 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) Architecture: amd64 Date: Wed Mar 30 19:54:28 2011 DkmsStatus: bcmwl, 5.60.48.36+bdcom, 2.6.35-28-generic, x86_64: installed bcmwl, 5.60.48.36+bdcom, 2.6.35-22-generic, x86_64: installed nvidia-current, 260.19.06, 2.6.35-28-generic, x86_64: installed nvidia-current, 260.19.06, 2.6.35-22-generic, x86_64: installed InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Apple Inc. MacBookAir3,1 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic root=UUID=f2123c85-84bb-45ca-93f3-61e22edb3523 ro ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xorg Symptom: display dmi.bios.date: 11/18/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA31.88Z.0061.B01.1011181342 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-942452F5819B1C1B dmi.board.vendor: Apple Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942452F5819B1C1B dmi.modalias: dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B01.1011181342:bd11/18/10:svnAppleInc.:pnMacBookAir3,1:pvr1.0:rvnAppleInc.:rnMac-942452F5819B1C1B:rvr1.0:cvnAppleInc.:ct10:cvrMac-942452F5819B1C1B: dmi.product.name: MacBookAir3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. system: distro: Ubuntu codename: maverick architecture: x86_64 kernel: 2.6.35-28-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/746174/+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
