ma, 2011-09-12 kello 20:57 +0200, Julien Cristau kirjoitti: > reassign 641176 linux-2.6 2.6.32-35 > kthxbye > > On Mon, Sep 12, 2011 at 10:27:21 +0200, Michel Dänzer wrote: > > > On Son, 2011-09-11 at 10:37 +0300, Tomi Leppänen wrote: > > > Package: xserver-xorg-video-radeon > > > Version: 1:6.13.1-2+squeeze1 > > > Severity: important > > > Tags: upstream > > > > > > This bug prevents me from using X because it won't start with this > > > graphics card. > > > I also have these lines in my dmesg, they may be important. > > > [ 0.120429] pci 0000:01:00.0: BAR 0: no parent found for of device > > > [0xd0000000-0xdfffffff] > > > [ 0.120504] pci 0000:01:00.0: BAR 0: can't allocate resource > > > [ 0.125917] pnp 00:00: mem resource (0xcd000-0xcffff) overlaps > > > 0000:01:00.0 BAR 0 (0x0-0xfffffff), disabling > > > [ 0.125939] pnp 00:00: mem resource (0xf0000-0xf7fff) overlaps > > > 0000:01:00.0 BAR 0 (0x0-0xfffffff), disabling > > > [ 0.125960] pnp 00:00: mem resource (0xf8000-0xfbfff) overlaps > > > 0000:01:00.0 BAR 0 (0x0-0xfffffff), disabling > > > [ 0.125982] pnp 00:00: mem resource (0xfc000-0xfffff) overlaps > > > 0000:01:00.0 BAR 0 (0x0-0xfffffff), disabling > > > [ 0.126003] pnp 00:00: mem resource (0x0-0x9ffff) overlaps > > > 0000:01:00.0 BAR 0 (0x0-0xfffffff), disabling > > > [ 0.126024] pnp 00:00: mem resource (0x100000-0x1ffeffff) overlaps > > > 0000:01:00.0 BAR 0 (0x0-0xfffffff), disabling > > > [ 0.173856] pci 0000:01:00.0: BAR 0: can't allocate mem resource > > > [0xe0000000-0xe7ffffff] > > > [ 7.488362] [drm] Detected VRAM RAM=0M, BAR=0M > > > Though these are probably related to Linux itself. > > > > Indeed, looks like a kernel (or possibly BIOS) PCI failure. This should > > probably be reassigned to the kernel, and you might want to try newer > > kernels. > > > Reassigning with this message. Tomi, can you check if a newer kernel > fixes this, or if there are BIOS updates available for your machine? > > Cheers, > Julien
I tried with 3.0.0-1-486 (from wheezy) but it didn't work much better, but at least something changed: dmesg |grep BAR [ 0.090510] pnp 00:00: disabling [mem 0x000cd000-0x000cffff] because it overlaps 0000:01:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref] [ 0.090534] pnp 00:00: disabling [mem 0x000f0000-0x000f7fff] because it overlaps 0000:01:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref] [ 0.090559] pnp 00:00: disabling [mem 0x000f8000-0x000fbfff] because it overlaps 0000:01:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref] [ 0.090583] pnp 00:00: disabling [mem 0x000fc000-0x000fffff] because it overlaps 0000:01:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref] [ 0.090607] pnp 00:00: disabling [mem 0x00000000-0x0009ffff] because it overlaps 0000:01:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref] [ 0.090632] pnp 00:00: disabling [mem 0x00100000-0x1ffeffff] because it overlaps 0000:01:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref] [ 0.144712] pci 0000:01:00.0: BAR 0: trying firmware assignment [mem 0xd0000000-0xdfffffff pref] [ 0.144737] pci 0000:01:00.0: BAR 0: [mem 0xd0000000-0xdfffffff pref] conflicts with PCI Bus 0000:01 [mem 0xd8000000-0xe7ffffff pref] [ 0.144757] pci 0000:01:00.0: BAR 0: can't assign mem pref (size 0x10000000) [ 0.144776] pci 0000:01:00.0: BAR 6: assigned [mem 0xd8000000-0xd801ffff pref] [ 10.883325] [drm] Detected VRAM RAM=128M, BAR=0M But still X won't start. Log seems to be the same (I can post it if needed). There are no newer BIOS updates for that motherboard (Gigabyte GA-6BXE with Intel 440BX) and I've updated it once already. Although I could try Coreboot (I may do it just for fun), because it seems to support this motherboard and I've got a spare BIOS chip from another broken GA-6BXE. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1315934082.24839.10.camel@tomppeli-laptop
