[Ubuntu-x-swat] [Bug 368187] Re: [HD3650] Kubuntu: garbage screen
I compared again all the logs from hardy, jaunty and karmic and indeed the only differences are about AGP aperture. Even though size and address are detected correctly in dmesg (and iomem/ioports are in line with WinXP), ... [0.004000] Checking aperture... [0.004000] Node 0: aperture @ e000 size 64 MB [0.480127] agpgart-amd64 :00:00.0: AGP bridge [1106/0204] [0.483619] agpgart-amd64 :00:00.0: AGP aperture is 64M @ 0xe000 ... the resource allocation fails. Hardy [ 31.135720] PCI: Using ACPI for IRQ routing [ 31.135723] PCI: If a device doesn't work, try pci=routeirq. If it helps, post a report [ 31.135735] PCI: Cannot allocate resource region 0 of device :00:00.0 Jaunty [0.470669] PCI: Using ACPI for IRQ routing [0.470681] pci :00:00.0: BAR 0: can't allocate resource Karmic [0.120980] PCI: Using ACPI for IRQ routing [0.120997] pci :00:00.0: BAR 0: address space collision on of device [0xe000-0xe3ff] [0.121059] pci :00:00.0: BAR 0: can't allocate resource Jaunty with acpi=off option in grub's menu.lst [0.261932] ACPI: Interpreter disabled. [0.264037] pci :00:00.0: BAR 0: can't allocate resource So this is probably why drm fails later on [ 30.201734] [drm] Can't use AGP base @0xe000, won't fit Pureblood, you have the same drm error, can you check if you also have the allocation error before that in your dmesg? As for the Xorg.0.log, the only error I found is with aperture size detection (32M instead of 64M) (II) RADEON(0): [agp] 32768 kB allocated with handle 0x0001 I tried Option GARTSize 64 but although 64M get allocated, it still results in a black screen, probably because the issue happens before. So, is this enough information to determine in which part of the code the bug lies? If it's really due to xserver-xorg-video-ati (Ubuntu), can we assign the appropriate people now? If not, should another bug be opened in the correct bug tracker? Would that be bugs.freedesktop.org? bugzilla.kernel.org? -- [HD3650] Kubuntu: garbage screen https://bugs.launchpad.net/bugs/368187 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 368187] Re: [HD3650] Kubuntu: garbage screen
Thanks Pauli, I was recommended this option some time ago and indeed it restores display (forgot to mention it on this thread). This problem appeared when I changed motherboard. I was able to access xorg.conf of my installation of Jaunty with Ctrl+Alt+F1. But the issue is that I don't think it's possible to edit xorg.conf with a live CD, so this means no fresh install for me. Moreover, a number of 3D programs/applications fail and I suspect it comes from this workaround situation. Do you mean it's a bug in the BIOS? Any reason why Windows is not suffering from this? -- [HD3650] Kubuntu: garbage screen https://bugs.launchpad.net/bugs/368187 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 368187] Re: [HD3650] Kubuntu: garbage screen
Pauli, Unfortunately there's no such setting in my BIOS (GA-K8VM800M Rev1.x) Now I'm confused about which memory area you are refering to. iomem/ioports give the following memory areas (same in WinXP) d000-dfff : PCI Bus :01 d000-dfff : :01:00.0 d000-dfff : radeon e000-e3ff : GART e000-e3ff : aperture e400-e5ff : PCI Bus :01 e400-e401 : :01:00.0 e500-e500 : :01:00.0 e500-e500 : radeon e501-e5013fff : :01:00.1 e501-e5013fff : ICH HD audio 03c0-03df : vga+ 9000-9fff : PCI Bus :01 9000-90ff : :01:00.0 9000-90ff : radeon And early in Xorg.0.log, I can see (--) PCI:*(0...@1:0:0) ATI Technologies Inc RV635 PRO AGP [Radeon HD 3650] rev 0, Mem @ 0xd000/268435456, 0xe500/65536, I/O @ 0x9000/256, BIOS @ 0x/131072 So the 64M (e000-e3ff) is the AGP aperture, while the 256M (d000-dfff) is a different area that seems to be called video RAM or framebuffer according to these lines (II) RADEON(0): Detected total video RAM=524288K, accessible=262144K (PCI BAR=262144K) (II) RADEON(0): [drm] framebuffer handle = 0xd000 Nevertheless, you mention a conflict between agpgart and acpi, and the allocation error happens after Using ACPI for IRQ routing, even with acpi=off option. So does this mean the bug is in acpi? Can we point the relevant devs to this thread for comments/solution? Thanks for your time -- [HD3650] Kubuntu: garbage screen https://bugs.launchpad.net/bugs/368187 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 368187] Re: [HD3650] Kubuntu: garbage screen
Further to the above tests, I wanted to check if Karmic would solve the issue but it's actually even worse. I tried the live CD of Karmic Alpha5 for AMD64 and not only the screen stays black, but there seems to be an init sequence repeating over and over (from observing cursor changes) and if you let a few sequences run, Ctrl+Alt+F1 is no longer responsive. On the second try, I pressed quicker and was able to copy the logs (in attachment). A difference of interest with Karmic is this one additional dmesg line that I noticed since it also appeared on screen just before the black screen: [0.120997] pci :00:00.0: BAR 0: address space collision on of device [0xe000-0xe3ff] This same address space is mentioned towards the end when drm fails: [ 96.398561] [drm] Can't use AGP base @0xe000, won't fit Then, I took my old hardy CD (AMD64), did the same try and everything worked (logs attached as well). So I don't know what differences were introduced since hardy but it could be worth looking into the diffs for extra information. For the sake of comparison, I captured the ressources tabs of WinXP SP3 device manager, where I saw that the particular [0xe000-0xe3ff] was used by three devices: the HD3650 AGP, CPU to AGP Ctlr and PCI bus. I'm not sure what else I can do to give this bug more importance. One thing for sure is with my hardware, I cannot do fresh install of either jaunty or karmic, so this is a pretty severe bug for me, and since it worked with hardy, it's actually a regression. I'm no expert but since the address space collision happens this early in the log, isn't it more a kernel bug than a ati driver bug? Let me know if I can help... ** Attachment added: karmic_etc.tar.gz http://launchpadlibrarian.net/31745806/karmic_etc.tar.gz -- [HD3650] Kubuntu: garbage screen https://bugs.launchpad.net/bugs/368187 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 368187] Re: [HD3650] Kubuntu: garbage screen
I've been experimenting with the r6xx rewrite OSS drivers under development and I still get the same display problem, except that the display is now completely black. http://www.phoronix.com/forums/showthread.php?t=18072 The keyboard is still responsive though, as I was able to type commands (in the dark) and generate the attached logs. I still get the welcome sound so Ubuntu is loading fine, except for the display. Hope this helps to identify any commonalities/differences ** Attachment added: 18-08-2009 tests.tar.gz http://launchpadlibrarian.net/30692740/18-08-2009%20tests.tar.gz -- [HD3650] Kubuntu: garbage screen https://bugs.launchpad.net/bugs/368187 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 368187] Re: [HD3650] Kubuntu: garbage screen
I'm having the exact same problem as described by pureblood. Also using HD3650 AGP. It's not Kubuntu Jaunty specific as I experienced it on Ubuntu 9.04 Amd64 fresh install, Mythbuntu 9.04 Amd64 fresh install and Ubuntu 9.04 live CD. Each time, fglrx is not enabled. Interestingly, this problem only appeared when I replaced my motherboard from Asus K8N (NVIDIA nForce3) to Gigabyte GA-K8VM800M Rev1.x (VIA K8M800). But it doesn't seem to be related to the mainboard since pureblood is on an intel configuration. Option DRI off did indeed restore desktop display but it's more a workaround than a solution. Option AGPMode 8 did not help, and unfortunately my BIOS does not let me change any AGP settings (except voltage which is on default). The on board video is supposedly disabled by the BIOS in the presence of an AGP card, but I'm not sure if linux correctly ignores it or not always completely... dmesg, xorg.conf, Xorg.0.log and lspci -vvnn generated with Mythbuntu are in the attachment. ** Attachment added: bug_368187.tar http://launchpadlibrarian.net/29788459/bug_368187.tar -- [HD3650] Kubuntu: garbage screen https://bugs.launchpad.net/bugs/368187 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
