G400 behavior different, 2.2.18->2.4.0 (was: matroxfb on 2.4.0 / PCI: Failed to allocate...)

2001-01-16 Thread Chad Miller
(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:

Re: matroxfb on 2.4.0 / PCI: Failed to allocate...

2001-01-16 Thread Petr Vandrovec
On 16 Jan 01 at 13:22, Chad Miller wrote: > On Tue, Jan 16, 2001 at 05:56:34PM +, Petr Vandrovec wrote: > > What does 'lspci -v' say? > > #00:01.0 PCI bridge: VIA Technologies, Inc. VT8371 [KX133 AGP] (prog-if 00 \ > #[Normal decode]) > #Flags: bus master, 66Mhz, medium devsel,

Re: matroxfb on 2.4.0 / PCI: Failed to allocate...

2001-01-16 Thread Chad Miller
On Tue, Jan 16, 2001 at 05:56:34PM +, Petr Vandrovec wrote: > What does 'lspci -v' say? Hi, Petr. I'm sorry for the verbosity, all. Here it is: #00:00.0 Host bridge: VIA Technologies, Inc. VT8371 [KX133] (rev 02) #Flags: bus master, medium devsel, latency 0 #Memory at

Re: matroxfb on 2.4.0 / PCI: Failed to allocate...

2001-01-16 Thread Petr Vandrovec
On 15 Jan 01 at 19:22, Chad Miller wrote: > I worry about some PCI initialization output (from dmesg): > > # PCI: Probing PCI hardware > # Unknown bridge resource 0: assuming transparent > # PCI: Using IRQ router VIA [1106/0686] at 00:07.0 > # PCI: Cannot allocate resource region 0 of device

Re: matroxfb on 2.4.0 / PCI: Failed to allocate...

2001-01-16 Thread Petr Vandrovec
On 15 Jan 01 at 19:22, Chad Miller wrote: I worry about some PCI initialization output (from dmesg): # PCI: Probing PCI hardware # Unknown bridge resource 0: assuming transparent # PCI: Using IRQ router VIA [1106/0686] at 00:07.0 # PCI: Cannot allocate resource region 0 of device 01:00.0

Re: matroxfb on 2.4.0 / PCI: Failed to allocate...

2001-01-16 Thread Chad Miller
On Tue, Jan 16, 2001 at 05:56:34PM +, Petr Vandrovec wrote: What does 'lspci -v' say? Hi, Petr. I'm sorry for the verbosity, all. Here it is: #00:00.0 Host bridge: VIA Technologies, Inc. VT8371 [KX133] (rev 02) #Flags: bus master, medium devsel, latency 0 #Memory at

Re: matroxfb on 2.4.0 / PCI: Failed to allocate...

2001-01-16 Thread Petr Vandrovec
On 16 Jan 01 at 13:22, Chad Miller wrote: On Tue, Jan 16, 2001 at 05:56:34PM +, Petr Vandrovec wrote: What does 'lspci -v' say? #00:01.0 PCI bridge: VIA Technologies, Inc. VT8371 [KX133 AGP] (prog-if 00 \ #[Normal decode]) #Flags: bus master, 66Mhz, medium devsel, latency 0

G400 behavior different, 2.2.18-2.4.0 (was: matroxfb on 2.4.0 / PCI: Failed to allocate...)

2001-01-16 Thread Chad Miller
(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:

matroxfb on 2.4.0 / PCI: Failed to allocate...

2001-01-15 Thread Chad Miller
Hi, all. I'm trying to get matroxfb running on a G400Max (dualhead). Of course, I have i2c bit-banging on and the relevant Matrox options turned on (as modules or compiled-in), and I don't see the expected `framebuffer: blah' after the `matroxfb: Matrox Millennium G400 MAX (AGP) detected'. I

matroxfb on 2.4.0 / PCI: Failed to allocate...

2001-01-15 Thread Chad Miller
Hi, all. I'm trying to get matroxfb running on a G400Max (dualhead). Of course, I have i2c bit-banging on and the relevant Matrox options turned on (as modules or compiled-in), and I don't see the expected `framebuffer: blah' after the `matroxfb: Matrox Millennium G400 MAX (AGP) detected'. I