> last 2 lines in dmesg output: > mtrr: 0xd8000000,0x2000000 overlaps existing 0xd8000000,0x1000000 > mtrr: 0xd8000000,0x2000000 overlaps existing 0xd8000000,0x1000000 both *fb fbcon drivers and xfree 4 try to setup mtrr ranges, which are the same for the video card => mtrr complains because the entry is already there. Gerd -- Get back there in front of the computer NOW. Christmas can wait. -- Linus "the Grinch" Torvalds, 24 Dec 2000 on linux-kernel - 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/
- [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on init Bryan Mayland
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on ini... Alan Cox
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on... Chris Kloiber
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.... Steven Walter
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.... David Wragg
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.... Gerd Knorr
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on... Bryan Mayland
- Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.... Alan Cox
- Re: [PATCH] VESA framebuffer w/ MTRR locks ... Gerd Knorr
- Re: [PATCH] VESA framebuffer w/ MTRR l... Bryan Mayland
- Re: [PATCH] VESA framebuffer w/MTRR locks 2.4.0 on ... David Wragg
- Re: [PATCH] VESA framebuffer w/MTRR locks 2.4.0... Bryan Mayland
- Re: Framebuffer as a module Bryan Mayland
- Re: Framebuffer as a module Bryan Mayland