You should increase your BIOS AGP apperture sizes to see if it helps. The PCI error looks like some conflict in how acpi wants to handle card in PCI mode which causes problems because agpgart has already reserved the memory area. (PCI bar is usually defaulting to 256M which is a lot more than 64M agp setting you have.)
On Wed, Sep 16, 2009 at 11:02 AM, pvautrin <pvaut...@yahoo.com> wrote: > 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 @ e0000000 size 64 MB > [ 0.480127] agpgart-amd64 0000:00:00.0: AGP bridge [1106/0204] > [ 0.483619] agpgart-amd64 0000:00:00.0: AGP aperture is 64M @ 0xe0000000 > > ... 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 > 0000:00:00.0 > Jaunty > [ 0.470669] PCI: Using ACPI for IRQ routing > [ 0.470681] pci 0000:00:00.0: BAR 0: can't allocate resource > Karmic > [ 0.120980] PCI: Using ACPI for IRQ routing > [ 0.120997] pci 0000:00:00.0: BAR 0: address space collision on of > device [0xe0000000-0xe3ffffff] > [ 0.121059] pci 0000: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 0000: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 @0xe0000000, 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 0x00000001 > > 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 direct subscriber > of the bug. > -- [HD3650] Kubuntu: garbage screen https://bugs.launchpad.net/bugs/368187 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
