Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
ke, 2011-09-21 kello 18:29 -0500, Jonathan Nieder kirjoitti: Tomi Leppänen wrote: Didn't make any difference. Here is dmesg now: [...] [0.144739] pci :01:00.0: BAR 0: trying firmware assignment [mem 0xd000-0xdfff pref] [0.144764] pci :01:00.0: BAR 0: [mem 0xd000-0xdfff pref] conflicts with PCI Bus :00 [mem 0x2000-0xffef] [0.144784] pci :01:00.0: BAR 0: can't assign mem pref (size 0x1000) Thanks, Tomi. If you still have time to work on this, please report it upstream to linux-...@vger.kernel.org (no subscription needed, since the convention is to always reply-to-all there) and either cc us or let us know the Message-ID so we can follow the resulting discussion. What subject should I use? Upstream will probably want to know a few things (so it can be good to use a few attachments): - which versions you have tested and what happened with each - dmesg output from a recent (ideally a mainline kernel or 3.1-rc4 from experimental) right after boot, just like you sent here You mean that I should try with Debian experimental kernel? This guide is probably correct to install it: http://wiki.debian.org/DebianExperimental - lspci -vvx or even lspci -vvxxx output (see the lspci manpage for a warning about the latter) So my biggest worry with -xxx is that my computer may crash? With this test setup it shouldn't be any problem. Thanks and good luck, Jonathan -- 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/1316698084.3792.6.camel@tomppeli-laptop
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
Tomi Leppänen wrote: Jonathan Nieder kirjoitti: Thanks, Tomi. If you still have time to work on this, please report it upstream to linux-...@vger.kernel.org (no subscription needed, since the convention is to always reply-to-all there) and either cc us or let us know the Message-ID so we can follow the resulting discussion. What subject should I use? You can choose one. ;-) (I am fond of subject lines starting with [bug?] but that's just a personal affectation.) There is a mailing list archive at [1] if you want to look around and blend in. The file [2] also has some advice. The ver_linux script it mentions is at [3]. [1] http://news.gmane.org/gmane.linux.kernel.pci [2] http://repo.or.cz/w/linux-2.6.git/blob_plain/HEAD:/REPORTING-BUGS [3] http://repo.or.cz/w/linux-2.6.git/blob_plain/HEAD:/scripts/ver_linux [...] - dmesg output from a recent (ideally a mainline kernel or 3.1-rc4 from experimental) right after boot, just like you sent here You mean that I should try with Debian experimental kernel? This guide is probably correct to install it: http://wiki.debian.org/DebianExperimental Yep, that guide looks right. BTW, 3.1-rc6 just hit experimental, though the autobuilders haven't finished building it yet: https://buildd.debian.org/status/package.php?p=linux-2.6suite=experimental - lspci -vvx or even lspci -vvxxx output (see the lspci manpage for a warning about the latter) So my biggest worry with -xxx is that my computer may crash? With this test setup it shouldn't be any problem. Excellent. -- 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/20110922193213.GF8656@elie
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
Tomi Leppänen wrote: Didn't make any difference. Here is dmesg now: [...] [0.144739] pci :01:00.0: BAR 0: trying firmware assignment [mem 0xd000-0xdfff pref] [0.144764] pci :01:00.0: BAR 0: [mem 0xd000-0xdfff pref] conflicts with PCI Bus :00 [mem 0x2000-0xffef] [0.144784] pci :01:00.0: BAR 0: can't assign mem pref (size 0x1000) Thanks, Tomi. If you still have time to work on this, please report it upstream to linux-...@vger.kernel.org (no subscription needed, since the convention is to always reply-to-all there) and either cc us or let us know the Message-ID so we can follow the resulting discussion. Upstream will probably want to know a few things (so it can be good to use a few attachments): - which versions you have tested and what happened with each - dmesg output from a recent (ideally a mainline kernel or 3.1-rc4 from experimental) right after boot, just like you sent here - lspci -vvx or even lspci -vvxxx output (see the lspci manpage for a warning about the latter) Thanks and good luck, Jonathan -- 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/20110921232928.GB23011@elie
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
On Son, 2011-09-18 at 11:38 +0300, Tomi Leppänen wrote: la, 2011-09-17 kello 06:10 -0700, Will Set kirjoitti: Saturday, September 17, 2011 6:49 AM Tomi Leppänen wrote: pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder kirjoitti: Hi Tomi, Tomi Leppänen wrote: [0.073485] PCI: Ignoring host bridge windows from ACPI; if necessary, use pci=use_crs and report a bug I was hoping it would be that. Does adding pci=use_crs to the kernel command line help? Thanks, Jonathan Didn't make any difference. Here is dmesg now: If you turn modesetting off you should be able to get the xserver running again. radeon.modeset=0 didn't seem to affect anything. Xorg.0.log: http://pastebin.com/3JKs85PP dmesg: http://pastebin.com/fZehesaK with radeon.modeset=0 There's just no way the GPU can be used properly if its PCI resources aren't properly set up. I wonder why my grub is just some colorful crap on bottom of my screen. I can't really edit anything on fly but I have to always make changes to /etc/default/grub and then issue update-grub. That may have something to do with this bug. It's further indication that the problem may stem from the BIOS, or possibly even the hardware itself. I also noticed that all of my memory is LOWMEM. Though graphics card doesn't change that (tried with ATI Rage 128VR that has trouble with DRI on Debian 6). Does that card basically work though? Do you also get PCI related errors in dmesg with it? -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- 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/1316429594.8237.26.camel@thor.local
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
ma, 2011-09-19 kello 12:53 +0200, Michel Dänzer kirjoitti: On Son, 2011-09-18 at 11:38 +0300, Tomi Leppänen wrote: la, 2011-09-17 kello 06:10 -0700, Will Set kirjoitti: Saturday, September 17, 2011 6:49 AM Tomi Leppänen wrote: pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder kirjoitti: Hi Tomi, Tomi Leppänen wrote: [0.073485] PCI: Ignoring host bridge windows from ACPI; if necessary, use pci=use_crs and report a bug I was hoping it would be that. Does adding pci=use_crs to the kernel command line help? Thanks, Jonathan Didn't make any difference. Here is dmesg now: If you turn modesetting off you should be able to get the xserver running again. radeon.modeset=0 didn't seem to affect anything. Xorg.0.log: http://pastebin.com/3JKs85PP dmesg: http://pastebin.com/fZehesaK with radeon.modeset=0 There's just no way the GPU can be used properly if its PCI resources aren't properly set up. That's what I thought. I wonder why my grub is just some colorful crap on bottom of my screen. I can't really edit anything on fly but I have to always make changes to /etc/default/grub and then issue update-grub. That may have something to do with this bug. It's further indication that the problem may stem from the BIOS, or possibly even the hardware itself. If it helps, I have a Nvidia GeForce 2 MX (AGP) and it seems to work completely. (though that card doesn't support interlacing) I can get dmesg for that too if needed but it takes probably a bit longer. I also noticed that all of my memory is LOWMEM. Though graphics card doesn't change that (tried with ATI Rage 128VR that has trouble with DRI on Debian 6). Does that card basically work though? Do you also get PCI related errors in dmesg with it? Yes, it does work. I've been using it because Radeon doesn't work, but Rage's XVideo is broken when using interlaced output (already reported). The DRI thing just requires to disable dri and I don't need 3D so I don't know about that part. dmesg didn't have anything except (AFAIK) that there is something on line 140 and below, but I'm not quite sure if this is an error: [0.068060] pci_root PNP0A03:00: host bridge window [io 0x-0x0cf7] (ignored) full dmesg with Rage 128VR (PCI): pastebin.com/j9YVk9xj -- 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/1316436903.3683.16.camel@tomppeli-laptop
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
On Mon, 2011-09-19 at 15:55 +0300, Tomi Leppänen wrote: ma, 2011-09-19 kello 12:53 +0200, Michel Dänzer kirjoitti: On Son, 2011-09-18 at 11:38 +0300, Tomi Leppänen wrote: la, 2011-09-17 kello 06:10 -0700, Will Set kirjoitti: Saturday, September 17, 2011 6:49 AM Tomi Leppänen wrote: pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder kirjoitti: I wonder why my grub is just some colorful crap on bottom of my screen. I can't really edit anything on fly but I have to always make changes to /etc/default/grub and then issue update-grub. That may have something to do with this bug. It's further indication that the problem may stem from the BIOS, or possibly even the hardware itself. If it helps, I have a Nvidia GeForce 2 MX (AGP) and it seems to work completely. (though that card doesn't support interlacing) I can get dmesg for that too if needed but it takes probably a bit longer. I don't think that'll buy anything at this point. I also noticed that all of my memory is LOWMEM. Though graphics card doesn't change that (tried with ATI Rage 128VR that has trouble with DRI on Debian 6). Does that card basically work though? Do you also get PCI related errors in dmesg with it? Yes, it does work. Then it seems most likely that the problem is with the BIOS or the card. At this point I don't see many options left other than trying if the card works in another machine or with another OS, or maybe trying to re-flash the ROM image on the card if that's possible. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- 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/1316438338.8237.35.camel@thor.local
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
Monday, September 19, 2011 9:18 AM Michel Dänzer wrotew: On Mon, 2011-09-19 at 15:55 +0300, Tomi Leppänen wrote: ma, 2011-09-19 kello 12:53 +0200, Michel Dänzer kirjoitti: On Son, 2011-09-18 at 11:38 +0300, Tomi Leppänen wrote: la, 2011-09-17 kello 06:10 -0700, Will Set kirjoitti: Saturday, September 17, 2011 6:49 AM Tomi Leppänen wrote: pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder kirjoitti: I wonder why my grub is just some colorful crap on bottom of my screen. I can't really edit anything on fly but I have to always make changes to /etc/default/grub and then issue update-grub. That may have something to do with this bug. It's further indication that the problem may stem from the BIOS, or possibly even the hardware itself. If it helps, I have a Nvidia GeForce 2 MX (AGP) and it seems to work completely. (though that card doesn't support interlacing) I can get dmesg for that too if needed but it takes probably a bit longer. I don't think that'll buy anything at this point. Problem iirc, both your other video cards -- ATI Rage 128VR and Nvidia GeForce 2 MX (AGP) -- have less than 64 MB of VRAM. I've found with my old AGP cards, 64MBs VRAM to be a minimum for mode switching as a general rule. Mobos with video onboard have different limits. I'm starting to see other pentium 4 limits with the newer 3.0.0 kernels, so I'm not really surprised having troubles trying 3.0.0 kernels And the PCI card is IMHO way to new to be used in the PCI slot of that old mobo. The video card has almost as much processing power as the mobo does. I'll bet the mobo's chipset can't access even half that Radeon 9200SE's resources. I also noticed that all of my memory is LOWMEM. Though graphics card doesn't change that (tried with ATI Rage 128VR that has trouble with DRI on Debian 6). Does that card basically work though? Do you also get PCI related errors in dmesg with it? Yes, it does work. Then it seems most likely that the problem is with the BIOS or the card. At this point I don't see many options left other than trying if the card works in another machine or with another OS, or maybe trying to re-flash the ROM image on the card if that's possible. I agree, especially if the BIOS is not being changed to reflect the PCI socket is being used for video instead of the mobos AGP slot. http://www.gigabyte.lv/products/mb/specs/ga-6bxe.html?print_page=1 I'd suggest using a Debian Live CD while testing, especially with older and oddly mixed hardware. http://cdimage.debian.org/cdimage/release/current-live/i386/iso-hybrid/ -- 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/1316443018.87530.yahoomail...@web35607.mail.mud.yahoo.com
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
la, 2011-09-17 kello 06:10 -0700, Will Set kirjoitti: Saturday, September 17, 2011 6:49 AM Tomi Leppänen wrote: pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder kirjoitti: Hi Tomi, Tomi Leppänen wrote: [0.073485] PCI: Ignoring host bridge windows from ACPI; if necessary, use pci=use_crs and report a bug I was hoping it would be that. Does adding pci=use_crs to the kernel command line help? Thanks, Jonathan Didn't make any difference. Here is dmesg now: If you turn modesetting off you should be able to get the xserver running again. radeon.modeset=0 didn't seem to affect anything. Xorg.0.log: http://pastebin.com/3JKs85PP dmesg: http://pastebin.com/fZehesaK with radeon.modeset=0 see from your initial Xorg.0.log file http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641176 (II) Primary Device is: PCI 01@00:00:0 (II) [KMS] drm report modesetting isn't supported. [...] (EE) RADEON(0): No valid linear framebuffer address [...] (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found If you have a newer mobo to test with this video card it might be interesting to see if it handles modeswitching with a newer than ( Intel 440BX ) chipset and a pentium 4 processor. I don't. This is the only AGP mobo I have (others are PCI-E or PCI only). And it's running VIA C3 (Nehemiah-core) processor. It doesn't support P4 but only P3 and P2 (Slot 1 or Socket 370 with Slotket as I use it). I wonder why my grub is just some colorful crap on bottom of my screen. I can't really edit anything on fly but I have to always make changes to /etc/default/grub and then issue update-grub. That may have something to do with this bug. I also noticed that all of my memory is LOWMEM. Though graphics card doesn't change that (tried with ATI Rage 128VR that has trouble with DRI on Debian 6). -- 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/1316335136.6369.10.camel@tomppeli-laptop
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder kirjoitti: Hi Tomi, Tomi Leppänen wrote: [0.073485] PCI: Ignoring host bridge windows from ACPI; if necessary, use pci=use_crs and report a bug I was hoping it would be that. Does adding pci=use_crs to the kernel command line help? Thanks, Jonathan Didn't make any difference. Here is dmesg now: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.0.0-1-486 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 Sat Aug 27 15:56:48 UTC 2011 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - 1fff (usable) [0.00] BIOS-e820: 1fff - 1fff3000 (ACPI NVS) [0.00] BIOS-e820: 1fff3000 - 2000 (ACPI data) [0.00] BIOS-e820: - 0001 (reserved) [0.00] Notice: NX (Execute Disable) protection missing in CPU! [0.00] DMI 2.1 present. [0.00] DMI:/i440BX-8671, BIOS 4.51 PG 02/06/01 [0.00] e820 update range: - 0001 (usable) == (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] last_pfn = 0x1fff0 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C7FFF write-protect [0.00] C8000-F7FFF uncachable [0.00] F8000-FBFFF write-through [0.00] FC000-F uncachable [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask FE000 write-back [0.00] 1 disabled [0.00] 2 disabled [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] PAT not supported by CPU. [0.00] initial memory mapped : 0 - 0180 [0.00] Base memory trampoline at [c009c000] 9c000 size 12288 [0.00] init_memory_mapping: -1fff [0.00] 00 - 40 page 4k [0.00] 40 - 001fc0 page 2M [0.00] 001fc0 - 001fff page 4k [0.00] kernel direct mapping tables up to 1fff @ 17fb000-180 [0.00] RAMDISK: 1777b000 - 18034000 [0.00] ACPI: RSDP 000f6ee0 00014 (v00 GBT ) [0.00] ACPI: RSDT 1fff3000 00028 (v01 GBTAWRDACPI 42302E31 AWRD ) [0.00] ACPI: FACP 1fff3040 00074 (v01 GBTAWRDACPI 42302E31 AWRD ) [0.00] ACPI: DSDT 1fff30c0 02629 (v01 GBTAWRDACPI 1000 MSFT 010C) [0.00] ACPI: FACS 1fff 00040 [0.00] 0MB HIGHMEM available. [0.00] 511MB LOWMEM available. [0.00] mapped low ram: 0 - 1fff [0.00] low ram: 0 - 1fff [0.00] Zone PFN ranges: [0.00] DMA 0x0010 - 0x1000 [0.00] Normal 0x1000 - 0x0001fff0 [0.00] HighMem empty [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 - 0x009f [0.00] 0: 0x0100 - 0x0001fff0 [0.00] On node 0 totalpages: 130943 [0.00] free_area_init_node: node 0, pgdat c13b2ae8, node_mem_map dfbef200 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 3951 pages, LIFO batch:0 [0.00] Normal zone: 992 pages used for memmap [0.00] Normal zone: 125968 pages, LIFO batch:31 [0.00] Using APIC driver default [0.00] ACPI: PM-Timer IO Port: 0x4008 [0.00] No local APIC present or hardware disabled [0.00] APIC: disable apic facility [0.00] APIC: switched to apic NOOP [0.00] nr_irqs_gsi: 16 [0.00] PM: Registered nosave memory: 0009f000 - 000a [0.00] PM: Registered nosave memory: 000a - 000f [0.00] PM: Registered nosave memory: 000f - 0010 [0.00] Allocating PCI resources starting at 2000 (gap: 2000:dfff) [0.00] Booting paravirtualized kernel on bare hardware [0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [0.00] pcpu-alloc: [0] 0 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129919 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-1-486 root=UUID=7f4075cc-5b16-4fe4-a51b-ee8f697feac1 ro quiet pci=use_crs [0.00] PID hash table entries: 2048 (order: 1,
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
to, 2011-09-15 kello 16:35 -0500, Jonathan Nieder kirjoitti: Hi, Tomi Leppänen wrote: 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.090632] pnp 00:00: disabling [mem 0x0010-0x1ffe] because it overlaps :01:00.0 BAR 0 [mem 0x-0x0fff pref] [0.144712] pci :01:00.0: BAR 0: trying firmware assignment [mem 0xd000-0xdfff pref] [0.144737] pci :01:00.0: BAR 0: [mem 0xd000-0xdfff pref] conflicts with PCI Bus :01 [mem 0xd800-0xe7ff pref] [0.144757] pci :01:00.0: BAR 0: can't assign mem pref (size 0x1000) [0.144776] pci :01:00.0: BAR 6: assigned [mem 0xd800-0xd801 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. Please attach full dmesg output from right after bootup. Thanks, Jonathan Here: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.0.0-1-486 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 Sat Aug 27 15:56:48 UTC 2011 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - 1fff (usable) [0.00] BIOS-e820: 1fff - 1fff3000 (ACPI NVS) [0.00] BIOS-e820: 1fff3000 - 2000 (ACPI data) [0.00] BIOS-e820: - 0001 (reserved) [0.00] Notice: NX (Execute Disable) protection missing in CPU! [0.00] DMI 2.1 present. [0.00] DMI:/i440BX-8671, BIOS 4.51 PG 02/06/01 [0.00] e820 update range: - 0001 (usable) == (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] last_pfn = 0x1fff0 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C7FFF write-protect [0.00] C8000-F7FFF uncachable [0.00] F8000-FBFFF write-through [0.00] FC000-F uncachable [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask FE000 write-back [0.00] 1 disabled [0.00] 2 disabled [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] PAT not supported by CPU. [0.00] initial memory mapped : 0 - 0180 [0.00] Base memory trampoline at [c009c000] 9c000 size 12288 [0.00] init_memory_mapping: -1fff [0.00] 00 - 40 page 4k [0.00] 40 - 001fc0 page 2M [0.00] 001fc0 - 001fff page 4k [0.00] kernel direct mapping tables up to 1fff @ 17fb000-180 [0.00] RAMDISK: 1777b000 - 18034000 [0.00] ACPI: RSDP 000f6ee0 00014 (v00 GBT ) [0.00] ACPI: RSDT 1fff3000 00028 (v01 GBTAWRDACPI 42302E31 AWRD ) [0.00] ACPI: FACP 1fff3040 00074 (v01 GBTAWRDACPI 42302E31 AWRD ) [0.00] ACPI: DSDT 1fff30c0 02629 (v01 GBTAWRDACPI 1000 MSFT 010C) [0.00] ACPI: FACS 1fff 00040 [0.00] 0MB HIGHMEM available. [0.00] 511MB LOWMEM available. [0.00] mapped low ram: 0 - 1fff [0.00] low ram: 0 - 1fff [0.00] Zone PFN ranges: [0.00] DMA 0x0010 - 0x1000 [0.00] Normal 0x1000 - 0x0001fff0 [0.00] HighMem empty [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 - 0x009f [0.00] 0: 0x0100 - 0x0001fff0 [0.00] On node 0 totalpages: 130943 [0.00] free_area_init_node: node 0, pgdat c13b2ae8, node_mem_map dfbef200 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 3951 pages, LIFO batch:0 [0.00] Normal zone: 992 pages used for memmap [0.00] Normal zone: 125968 pages, LIFO batch:31 [0.00] Using APIC driver default [0.00] ACPI: PM-Timer IO Port: 0x4008 [0.00] No local APIC present or hardware disabled [0.00] APIC: disable apic facility [0.00] APIC: switched to apic NOOP [0.00] nr_irqs_gsi: 16 [
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
Hi Tomi, Tomi Leppänen wrote: [0.073485] PCI: Ignoring host bridge windows from ACPI; if necessary, use pci=use_crs and report a bug I was hoping it would be that. Does adding pci=use_crs to the kernel command line help? Thanks, Jonathan -- 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/20110916204332.GC4683@elie
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
Hi, Tomi Leppänen wrote: 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.090632] pnp 00:00: disabling [mem 0x0010-0x1ffe] because it overlaps :01:00.0 BAR 0 [mem 0x-0x0fff pref] [0.144712] pci :01:00.0: BAR 0: trying firmware assignment [mem 0xd000-0xdfff pref] [0.144737] pci :01:00.0: BAR 0: [mem 0xd000-0xdfff pref] conflicts with PCI Bus :01 [mem 0xd800-0xe7ff pref] [0.144757] pci :01:00.0: BAR 0: can't assign mem pref (size 0x1000) [0.144776] pci :01:00.0: BAR 6: assigned [mem 0xd800-0xd801 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. Please attach full dmesg output from right after bootup. Thanks, Jonathan -- 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/20110915213503.GA32610@elie
Processed: Re: Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
Processing commands for cont...@bugs.debian.org: tags 641176 - moreinfo Bug #641176 [linux-2.6] xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M Removed tag(s) moreinfo. # probably 3.0.0-3, but whatever :) found 641176 linux-2.6/3.0.0-1 Bug #641176 [linux-2.6] xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M Bug Marked as found in versions linux-2.6/3.0.0-1. End of message, stopping processing here. Please contact me if you need assistance. -- 641176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13161225688735.transcr...@bugs.debian.org
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
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 :01:00.0: BAR 0: no parent found for of device [0xd000-0xdfff] [0.120504] pci :01:00.0: BAR 0: can't allocate resource [0.125917] pnp 00:00: mem resource (0xcd000-0xc) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.125939] pnp 00:00: mem resource (0xf-0xf7fff) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.125960] pnp 00:00: mem resource (0xf8000-0xfbfff) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.125982] pnp 00:00: mem resource (0xfc000-0xf) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.126003] pnp 00:00: mem resource (0x0-0x9) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.126024] pnp 00:00: mem resource (0x10-0x1ffe) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.173856] pci :01:00.0: BAR 0: can't allocate mem resource [0xe000-0xe7ff] [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-0x000c] because it overlaps :01:00.0 BAR 0 [mem 0x-0x0fff pref] [0.090534] pnp 00:00: disabling [mem 0x000f-0x000f7fff] because it overlaps :01:00.0 BAR 0 [mem 0x-0x0fff pref] [0.090559] pnp 00:00: disabling [mem 0x000f8000-0x000fbfff] because it overlaps :01:00.0 BAR 0 [mem 0x-0x0fff pref] [0.090583] pnp 00:00: disabling [mem 0x000fc000-0x000f] because it overlaps :01:00.0 BAR 0 [mem 0x-0x0fff pref] [0.090607] pnp 00:00: disabling [mem 0x-0x0009] because it overlaps :01:00.0 BAR 0 [mem 0x-0x0fff pref] [0.090632] pnp 00:00: disabling [mem 0x0010-0x1ffe] because it overlaps :01:00.0 BAR 0 [mem 0x-0x0fff pref] [0.144712] pci :01:00.0: BAR 0: trying firmware assignment [mem 0xd000-0xdfff pref] [0.144737] pci :01:00.0: BAR 0: [mem 0xd000-0xdfff pref] conflicts with PCI Bus :01 [mem 0xd800-0xe7ff pref] [0.144757] pci :01:00.0: BAR 0: can't assign mem pref (size 0x1000) [0.144776] pci :01:00.0: BAR 6: assigned [mem 0xd800-0xd801 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
Re: Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
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 :01:00.0: BAR 0: no parent found for of device [0xd000-0xdfff] [0.120504] pci :01:00.0: BAR 0: can't allocate resource [0.125917] pnp 00:00: mem resource (0xcd000-0xc) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.125939] pnp 00:00: mem resource (0xf-0xf7fff) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.125960] pnp 00:00: mem resource (0xf8000-0xfbfff) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.125982] pnp 00:00: mem resource (0xfc000-0xf) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.126003] pnp 00:00: mem resource (0x0-0x9) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.126024] pnp 00:00: mem resource (0x10-0x1ffe) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.173856] pci :01:00.0: BAR 0: can't allocate mem resource [0xe000-0xe7ff] [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 -- 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/20110912185753.gb5...@radis.liafa.jussieu.fr
Processed: Re: Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
Processing commands for cont...@bugs.debian.org: reassign 641176 linux-2.6 2.6.32-35 Bug #641176 [xserver-xorg-video-radeon] xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M Bug reassigned from package 'xserver-xorg-video-radeon' to 'linux-2.6'. Bug No longer marked as found in versions xserver-xorg-video-ati/1:6.13.1-2+squeeze1. Bug #641176 [linux-2.6] xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M There is no source info for the package 'linux-2.6' at version '2.6.32-35' with architecture '' Unable to make a source version for version '2.6.32-35' Bug Marked as found in versions 2.6.32-35. kthxbye Stopping processing here. Please contact me if you need assistance. -- 641176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.131585388911433.transcr...@bugs.debian.org
