G400 behavior different, 2.2.18->2.4.0 (was: matroxfb on 2.4.0 / PCI: Failed to allocate...)
(CC'd to lkml) On Tue, Jan 16, 2001 at 07:31:33PM +, Petr Vandrovec wrote: > There is something wrong with your hardware. First region for G400 should > be 32MB, not 16MB (even if you have 16MB G400, which I doubt). Ooo! Here's an edited diff of 'lspci -v' under 2.2.18 versus 2.4.0: 36,41c37,42 < Flags: bus master, VGA palette snoop, medium devsel, latency 32, IRQ 10 < Memory at d600 (32-bit, prefetchable) < Memory at d400 (32-bit, non-prefetchable) < Memory at d500 (32-bit, non-prefetchable) < Capabilities: [dc] Power Management version 2 < Capabilities: [f0] AGP version 2.0 --- > Flags: bus master, VGA palette snoop, medium devsel, latency 64, IRQ 10 > Memory at d800 (32-bit, prefetchable) [size=16M] > Memory at d400 (32-bit, non-prefetchable) [size=16K] > Memory at d500 (32-bit, non-prefetchable) [size=8M] > Expansion ROM at [disabled] [size=64K] > Capabilities: Change in latency and base address. Interesting, eh? Do you think any configuration parameters could affect this? (I haven't paid as much attention to the evolution from 2.2 to 2.4 as I should've.) Here's the diff of X' output, from 2.2.18 to 2.4.0: 43c43 < (--) PCI:*(1:0:0) Matrox MGA G400 AGP rev 5, Mem @ 0xd600/25, 0xd400/14, 0xd500/23 --- > (--) PCI:*(1:0:0) Matrox MGA G400 AGP rev 5, Mem @ 0xd600/24, 0xd400/14, >0xd500/23 72,73d71 < (WW) INVALID MEM ALLOCATION b: 0xd600 e: 0xd7ff correcting < (EE) Cannot find a replacement memory range Ideas? - chad -- Chad Miller <[EMAIL PROTECTED]> URL: http://web.chad.org/ (GPG) "Any technology distinguishable from magic is insufficiently advanced". First corollary to Clarke's Third Law (Jargon File, v4.2.0, 'magic') - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
G400 behavior different, 2.2.18-2.4.0 (was: matroxfb on 2.4.0 / PCI: Failed to allocate...)
(CC'd to lkml) On Tue, Jan 16, 2001 at 07:31:33PM +, Petr Vandrovec wrote: There is something wrong with your hardware. First region for G400 should be 32MB, not 16MB (even if you have 16MB G400, which I doubt). Ooo! Here's an edited diff of 'lspci -v' under 2.2.18 versus 2.4.0: 36,41c37,42 Flags: bus master, VGA palette snoop, medium devsel, latency 32, IRQ 10 Memory at d600 (32-bit, prefetchable) Memory at d400 (32-bit, non-prefetchable) Memory at d500 (32-bit, non-prefetchable) Capabilities: [dc] Power Management version 2 Capabilities: [f0] AGP version 2.0 --- Flags: bus master, VGA palette snoop, medium devsel, latency 64, IRQ 10 Memory at d800 (32-bit, prefetchable) [size=16M] Memory at d400 (32-bit, non-prefetchable) [size=16K] Memory at d500 (32-bit, non-prefetchable) [size=8M] Expansion ROM at unassigned [disabled] [size=64K] Capabilities: available only to root Change in latency and base address. Interesting, eh? Do you think any configuration parameters could affect this? (I haven't paid as much attention to the evolution from 2.2 to 2.4 as I should've.) Here's the diff of X' output, from 2.2.18 to 2.4.0: 43c43 (--) PCI:*(1:0:0) Matrox MGA G400 AGP rev 5, Mem @ 0xd600/25, 0xd400/14, 0xd500/23 --- (--) PCI:*(1:0:0) Matrox MGA G400 AGP rev 5, Mem @ 0xd600/24, 0xd400/14, 0xd500/23 72,73d71 (WW) INVALID MEM ALLOCATION b: 0xd600 e: 0xd7ff correcting (EE) Cannot find a replacement memory range Ideas? - chad -- Chad Miller [EMAIL PROTECTED] URL: http://web.chad.org/ (GPG) "Any technology distinguishable from magic is insufficiently advanced". First corollary to Clarke's Third Law (Jargon File, v4.2.0, 'magic') - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
