Re: Problem with matrox framebuffer in 2.6.23.x
On Thursday 13 December 2007 13:28:25 Dirk Heinrichs wrote: > ... and the fb boot options for all kernels are: video=matroxfb:vesa:0x105. Got a hint via p.m. to change the above to video=matroxfb:[EMAIL PROTECTED] for the 2.6.23.x kernels. And it works fine. Bye... Dirk -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Problem with matrox framebuffer in 2.6.23.x
On Thursday 13 December 2007 13:28:25 Dirk Heinrichs wrote: ... and the fb boot options for all kernels are: video=matroxfb:vesa:0x105. Got a hint via p.m. to change the above to video=matroxfb:[EMAIL PROTECTED] for the 2.6.23.x kernels. And it works fine. Bye... Dirk -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Problem with matrox framebuffer in 2.6.23.x
Hello, I apologize if this is not the right place to ask, but I wanted to check if there is a mistake from my side before I open a new report in bugzilla. The problem I have is that with 2.6.23.[89], the screen turns black immediately after switching into framebuffer mode. This doesn't happen with 2.6.22.12. All kernels have been compiled with GCC 4.1.3 on an Ubuntu box with a K6-3 cpu and the fb boot options for all kernels are: video=matroxfb:vesa:0x105. The config files for the working and non-working kernels are attached in gzipped form. I don't see anything in the configs that would trigger the problem, but maybe somebody here on the list does. Many thanks in advance... Dirk config-2.6.22.12.gz Description: GNU Zip compressed data config-2.6.23.9.gz Description: GNU Zip compressed data signature.asc Description: This is a digitally signed message part.
Problem with matrox framebuffer in 2.6.23.x
Hello, I apologize if this is not the right place to ask, but I wanted to check if there is a mistake from my side before I open a new report in bugzilla. The problem I have is that with 2.6.23.[89], the screen turns black immediately after switching into framebuffer mode. This doesn't happen with 2.6.22.12. All kernels have been compiled with GCC 4.1.3 on an Ubuntu box with a K6-3 cpu and the fb boot options for all kernels are: video=matroxfb:vesa:0x105. The config files for the working and non-working kernels are attached in gzipped form. I don't see anything in the configs that would trigger the problem, but maybe somebody here on the list does. Many thanks in advance... Dirk config-2.6.22.12.gz Description: GNU Zip compressed data config-2.6.23.9.gz Description: GNU Zip compressed data signature.asc Description: This is a digitally signed message part.
[PATCH] [311/2many] MAINTAINERS - MATROX FRAMEBUFFER DRIVER
Add file pattern to MAINTAINER entry Signed-off-by: Joe Perches <[EMAIL PROTECTED]> diff --git a/MAINTAINERS b/MAINTAINERS index ce9418a..f200501 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2998,6 +2998,8 @@ P:Petr Vandrovec M: [EMAIL PROTECTED] L: [EMAIL PROTECTED] (subscribers-only) S: Maintained +F: drivers/video/matrox/matroxfb_* +F: include/linux/matroxfb.h MAX6650 HARDWARE MONITOR AND FAN CONTROLLER DRIVER P: Hans J. Koch - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH] [311/2many] MAINTAINERS - MATROX FRAMEBUFFER DRIVER
Add file pattern to MAINTAINER entry Signed-off-by: Joe Perches [EMAIL PROTECTED] diff --git a/MAINTAINERS b/MAINTAINERS index ce9418a..f200501 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2998,6 +2998,8 @@ P:Petr Vandrovec M: [EMAIL PROTECTED] L: [EMAIL PROTECTED] (subscribers-only) S: Maintained +F: drivers/video/matrox/matroxfb_* +F: include/linux/matroxfb.h MAX6650 HARDWARE MONITOR AND FAN CONTROLLER DRIVER P: Hans J. Koch - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel warning from Matrox Framebuffer in 2.6.20.1
Ondrej Zary wrote: On Saturday 24 February 2007 14:08, Chris Rankin wrote: Hi, I have just booted 2.6.20.1 on my Pentium 3 machine, which has a G400 MAX graphics card. This machine uses the Matrox framebuffer and TV-OUT modules, and I have found these warnings in the kernel log: **WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical device; fix it! **WARNING** I2C adapter driver [DDC:fb0 #1] forgot to specify physical device; fix it! **WARNING** I2C adapter driver [MAVEN:fb0] forgot to specify physical device; fix it! I'm seeing something like that since installing 2.6.20.1 yesterday: matroxfb: Matrox Mystique (PCI) detected PInS memtype = 0 matroxfb: MTRR's turned on matroxfb: 1024x768x8bpp (virtual: 1024x4096) matroxfb: framebuffer at 0xE100, mapped to 0xcc88, size 4194304 Console: switching to colour frame buffer device 128x48 fb0: MATROX frame buffer device **WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical device; fix it! Can you try current git tree? I believe that it is already fixed by Jean Delvare checkin from Feb 13th (thanks Jean!) Petr - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel warning from Matrox Framebuffer in 2.6.20.1
On Saturday 24 February 2007 14:08, Chris Rankin wrote: > Hi, > > I have just booted 2.6.20.1 on my Pentium 3 machine, which has a G400 MAX > graphics card. This machine uses the Matrox framebuffer and TV-OUT modules, > and I have found these warnings in the kernel log: > > **WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical > device; fix it! **WARNING** I2C adapter driver [DDC:fb0 #1] forgot to > specify physical device; fix it! **WARNING** I2C adapter driver [MAVEN:fb0] > forgot to specify physical device; fix it! I'm seeing something like that since installing 2.6.20.1 yesterday: matroxfb: Matrox Mystique (PCI) detected PInS memtype = 0 matroxfb: MTRR's turned on matroxfb: 1024x768x8bpp (virtual: 1024x4096) matroxfb: framebuffer at 0xE100, mapped to 0xcc88, size 4194304 Console: switching to colour frame buffer device 128x48 fb0: MATROX frame buffer device **WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical device; fix it! > The relevant kernel modules seem to be: > > matroxfb_maven 13228 0 > i2c_matroxfb4064 0 > i2c_algo_bit6312 1 i2c_matroxfb > > Cheers, > Chris -- Ondrej Zary - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Kernel warning from Matrox Framebuffer in 2.6.20.1
Hi, I have just booted 2.6.20.1 on my Pentium 3 machine, which has a G400 MAX graphics card. This machine uses the Matrox framebuffer and TV-OUT modules, and I have found these warnings in the kernel log: **WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical device; fix it! **WARNING** I2C adapter driver [DDC:fb0 #1] forgot to specify physical device; fix it! **WARNING** I2C adapter driver [MAVEN:fb0] forgot to specify physical device; fix it! The relevant kernel modules seem to be: matroxfb_maven 13228 0 i2c_matroxfb4064 0 i2c_algo_bit6312 1 i2c_matroxfb Cheers, Chris ___ All New Yahoo! Mail Tired of unwanted email come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Kernel warning from Matrox Framebuffer in 2.6.20.1
Hi, I have just booted 2.6.20.1 on my Pentium 3 machine, which has a G400 MAX graphics card. This machine uses the Matrox framebuffer and TV-OUT modules, and I have found these warnings in the kernel log: **WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical device; fix it! **WARNING** I2C adapter driver [DDC:fb0 #1] forgot to specify physical device; fix it! **WARNING** I2C adapter driver [MAVEN:fb0] forgot to specify physical device; fix it! The relevant kernel modules seem to be: matroxfb_maven 13228 0 i2c_matroxfb4064 0 i2c_algo_bit6312 1 i2c_matroxfb Cheers, Chris ___ All New Yahoo! Mail Tired of unwanted email come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel warning from Matrox Framebuffer in 2.6.20.1
On Saturday 24 February 2007 14:08, Chris Rankin wrote: Hi, I have just booted 2.6.20.1 on my Pentium 3 machine, which has a G400 MAX graphics card. This machine uses the Matrox framebuffer and TV-OUT modules, and I have found these warnings in the kernel log: **WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical device; fix it! **WARNING** I2C adapter driver [DDC:fb0 #1] forgot to specify physical device; fix it! **WARNING** I2C adapter driver [MAVEN:fb0] forgot to specify physical device; fix it! I'm seeing something like that since installing 2.6.20.1 yesterday: matroxfb: Matrox Mystique (PCI) detected PInS memtype = 0 matroxfb: MTRR's turned on matroxfb: 1024x768x8bpp (virtual: 1024x4096) matroxfb: framebuffer at 0xE100, mapped to 0xcc88, size 4194304 Console: switching to colour frame buffer device 128x48 fb0: MATROX frame buffer device **WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical device; fix it! The relevant kernel modules seem to be: matroxfb_maven 13228 0 i2c_matroxfb4064 0 i2c_algo_bit6312 1 i2c_matroxfb Cheers, Chris -- Ondrej Zary - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel warning from Matrox Framebuffer in 2.6.20.1
Ondrej Zary wrote: On Saturday 24 February 2007 14:08, Chris Rankin wrote: Hi, I have just booted 2.6.20.1 on my Pentium 3 machine, which has a G400 MAX graphics card. This machine uses the Matrox framebuffer and TV-OUT modules, and I have found these warnings in the kernel log: **WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical device; fix it! **WARNING** I2C adapter driver [DDC:fb0 #1] forgot to specify physical device; fix it! **WARNING** I2C adapter driver [MAVEN:fb0] forgot to specify physical device; fix it! I'm seeing something like that since installing 2.6.20.1 yesterday: matroxfb: Matrox Mystique (PCI) detected PInS memtype = 0 matroxfb: MTRR's turned on matroxfb: 1024x768x8bpp (virtual: 1024x4096) matroxfb: framebuffer at 0xE100, mapped to 0xcc88, size 4194304 Console: switching to colour frame buffer device 128x48 fb0: MATROX frame buffer device **WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical device; fix it! Can you try current git tree? I believe that it is already fixed by Jean Delvare checkin from Feb 13th (thanks Jean!) Petr - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Matrox framebuffer dualhead and utilities
German Gomez Garcia wrote: > I'm trying to set the Matrox framebuffer to dualhead or TV output, > but the utilities mentioned in the docs seem to be outdated (ioctl failed > with incorrect command). Any idea about where to get up to date tools? > I'm using kernel 2.4.2-ac20 (quite stable 5 days uptime with heavy DRI > testing and heavy disk working). matroxset-0.3 is latest one. You are probably doing something wrong: (1) With fbset you are trying to use 8bpp or 24bpp color depth. Secondary head supports only 16/32bpp. (2) You did not insmod all needed modules if you compiled matroxfb as modular (you should compile everything into the kernel...) (3) You are trying to do some illegal thing, like connecting both /dev/fb0 and /dev/fb1 into same output... Petr Vandrovec [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Matrox framebuffer dualhead and utilities
Hello, I'm trying to set the Matrox framebuffer to dualhead or TV output, but the utilities mentioned in the docs seem to be outdated (ioctl failed with incorrect command). Any idea about where to get up to date tools? I'm using kernel 2.4.2-ac20 (quite stable 5 days uptime with heavy DRI testing and heavy disk working). Thanks - german PS: Please CC to me as I'm not subscribed to the list. - German Gomez Garcia | "This isn't right. This isn't even wrong." <[EMAIL PROTECTED]> | -- Wolfgang Pauli - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Matrox framebuffer dualhead and utilities
Hello, I'm trying to set the Matrox framebuffer to dualhead or TV output, but the utilities mentioned in the docs seem to be outdated (ioctl failed with incorrect command). Any idea about where to get up to date tools? I'm using kernel 2.4.2-ac20 (quite stable 5 days uptime with heavy DRI testing and heavy disk working). Thanks - german PS: Please CC to me as I'm not subscribed to the list. - German Gomez Garcia | "This isn't right. This isn't even wrong." [EMAIL PROTECTED] | -- Wolfgang Pauli - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Matrox framebuffer dualhead and utilities
German Gomez Garcia wrote: I'm trying to set the Matrox framebuffer to dualhead or TV output, but the utilities mentioned in the docs seem to be outdated (ioctl failed with incorrect command). Any idea about where to get up to date tools? I'm using kernel 2.4.2-ac20 (quite stable 5 days uptime with heavy DRI testing and heavy disk working). matroxset-0.3 is latest one. You are probably doing something wrong: (1) With fbset you are trying to use 8bpp or 24bpp color depth. Secondary head supports only 16/32bpp. (2) You did not insmod all needed modules if you compiled matroxfb as modular (you should compile everything into the kernel...) (3) You are trying to do some illegal thing, like connecting both /dev/fb0 and /dev/fb1 into same output... Petr Vandrovec [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Matrox framebuffer
On 10 Oct 00 at 15:33, Daniel Podlejski wrote: > I have problem with Matrox G400 framebuffer. After turn > on computer, kernel freez durning boot with snow on my monitor. > When I start it with options video=matrox:disbled, and run XFree86 > 4.0.1 with official drivers from Matrox web page, and reboot my > computer again - everything works fine. Strange. > 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) >(prog-if 00 [VGA]) > Subsystem: Matrox Graphics, Inc. Millennium G400 16Mb SGRAM > Flags: medium devsel, IRQ 11 > Memory at 4200 (32-bit, prefetchable) [size=32M] > Memory at 4080 (32-bit, non-prefetchable) [size=16K] > Memory at 4000 (32-bit, non-prefetchable) [size=8M] These addresses looks suspicious to me. Do you have Phoenix BIOS? Or did Linux kernel assign them to device? Can you try 'video=matrox:init,sgram', eventually 'video=matrox:init,sgram,memtype:X', where X is 0,1,2 or 4 ? (see Documentation/fb/matroxfb.txt for memtype explanation; if your G400 is expandable to 32MB, it is type 0 or 4; if it is not expandable, it is memtype 1 or 2) Best regards, Petr Vandrovec [EMAIL PROTECTED] - 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/
Re: Matrox framebuffer
On 10 Oct 00 at 15:33, Daniel Podlejski wrote: I have problem with Matrox G400 framebuffer. After turn on computer, kernel freez durning boot with snow on my monitor. When I start it with options video=matrox:disbled, and run XFree86 4.0.1 with official drivers from Matrox web page, and reboot my computer again - everything works fine. Strange. 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) (prog-if 00 [VGA]) Subsystem: Matrox Graphics, Inc. Millennium G400 16Mb SGRAM Flags: medium devsel, IRQ 11 Memory at 4200 (32-bit, prefetchable) [size=32M] Memory at 4080 (32-bit, non-prefetchable) [size=16K] Memory at 4000 (32-bit, non-prefetchable) [size=8M] These addresses looks suspicious to me. Do you have Phoenix BIOS? Or did Linux kernel assign them to device? Can you try 'video=matrox:init,sgram', eventually 'video=matrox:init,sgram,memtype:X', where X is 0,1,2 or 4 ? (see Documentation/fb/matroxfb.txt for memtype explanation; if your G400 is expandable to 32MB, it is type 0 or 4; if it is not expandable, it is memtype 1 or 2) Best regards, Petr Vandrovec [EMAIL PROTECTED] - 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/
Matrox framebuffer
I have problem with Matrox G400 framebuffer. After turn on computer, kernel freez durning boot with snow on my monitor. When I start it with options video=matrox:disbled, and run XFree86 4.0.1 with official drivers from Matrox web page, and reboot my computer again - everything works fine. >From dmesg: matroxfb: Matrox unknown G400 (AGP) detected matroxfb: MTRR's turned on matroxfb: cannot set xres to 800, rounded up to 832 matroxfb: cannot set xres to 800, rounded up to 832 matroxfb: 800x600x8bpp (virtual: 832x20160) matroxfb: framebuffer at 0x4200, mapped to 0xc8805000, size 16777216 Console: switching to colour frame buffer device 100x37 fb0: MATROX VGA frame buffer device And lspci -v: 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) (prog-if 00 [VGA]) Subsystem: Matrox Graphics, Inc. Millennium G400 16Mb SGRAM Flags: medium devsel, IRQ 11 Memory at 4200 (32-bit, prefetchable) [size=32M] Memory at 4080 (32-bit, non-prefetchable) [size=16K] Memory at 4000 (32-bit, non-prefetchable) [size=8M] Expansion ROM at [disabled] [size=64K] Capabilities: [dc] Power Management version 2 Capabilities: [f0] AGP version 2.0 uname -a Linux random 2.4.0-test9 #1 Tue Oct 10 15:05:22 CEST 2000 i686 unknown -- Daniel Podlejski <[EMAIL PROTECTED]> ... When you're through with life and all hope is lost, Hold out your hand cos right till the end - friends will be friends ... - 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/
Matrox framebuffer
I have problem with Matrox G400 framebuffer. After turn on computer, kernel freez durning boot with snow on my monitor. When I start it with options video=matrox:disbled, and run XFree86 4.0.1 with official drivers from Matrox web page, and reboot my computer again - everything works fine. From dmesg: matroxfb: Matrox unknown G400 (AGP) detected matroxfb: MTRR's turned on matroxfb: cannot set xres to 800, rounded up to 832 matroxfb: cannot set xres to 800, rounded up to 832 matroxfb: 800x600x8bpp (virtual: 832x20160) matroxfb: framebuffer at 0x4200, mapped to 0xc8805000, size 16777216 Console: switching to colour frame buffer device 100x37 fb0: MATROX VGA frame buffer device And lspci -v: 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) (prog-if 00 [VGA]) Subsystem: Matrox Graphics, Inc. Millennium G400 16Mb SGRAM Flags: medium devsel, IRQ 11 Memory at 4200 (32-bit, prefetchable) [size=32M] Memory at 4080 (32-bit, non-prefetchable) [size=16K] Memory at 4000 (32-bit, non-prefetchable) [size=8M] Expansion ROM at unassigned [disabled] [size=64K] Capabilities: [dc] Power Management version 2 Capabilities: [f0] AGP version 2.0 uname -a Linux random 2.4.0-test9 #1 Tue Oct 10 15:05:22 CEST 2000 i686 unknown -- Daniel Podlejski [EMAIL PROTECTED] ... When you're through with life and all hope is lost, Hold out your hand cos right till the end - friends will be friends ... - 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/
