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

2001-01-15 Thread Chad Miller
0 [matroxfb_crtc2 matroxfb_maven \ i2c-matroxfb matroxfb_base matroxfb_DAC1064 matroxfb_accel] agpgart13536 0 (unused) ...but... cmiller@canard:~$ cat /proc/fb cmiller@canard:~$ Ideas? Pointers? I'm available for questions and flames.

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

2001-01-16 Thread Chad Miller
#x27; matroxfb option, but...) (1) is true. (2) is true, AFAICT, but I'm no BIOS expert. I once success- fully used matroxfb on this machine under 2.2.~17, but haven't tried it again before 2.4 . - chad -- Chad Miller <[EMAIL PROTECT

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
/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: htt

Re: G400 behavior different, 2.2.18->2.4.0

2001-01-16 Thread Chad Miller
On Tue, Jan 16, 2001 at 10:40:51PM +, Petr Vandrovec wrote: > [X] Output under 2.2.x is correct: '/25' for 32MB range. I have no idea > why X complains about region D600-D7FF - can you look at > '... regions behind bridge' when you boot 2.2.x (they are on 0:01.0 > device, AFAIK) ? Unde