matroxfb and 2.6.0-test2

matroxfb and 2.6.0-test2

[Frédéric L. W. Meunier]

The card is a Matrox Millenium G400 M4A32DG (single head).

2.6.0-test2 is the first 2.5.x I try, so I may be missing
something.

During make modules_install I noticed the following warning
(yes, I installed the latest module-init-tools):

if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.6.0-test2; fi
WARNING: /lib/modules/2.6.0-test2/kernel/drivers/video/matrox/matroxfb_crtc2.ko
needs unknown symbol matroxfb_enable_irq

I don't know if it's serious but then I rebooted from 2.4.21.

My init script contains

if lspci | grep -q 'MGA G400'; then
modprobe matroxfb_base
fi

and /etc/modprobe.conf options matroxfb_base vesa=440

After it the screen became corrupted with a dump of my last
shutdown. All commands still worked. I don't use fbset at all.
The logs don't have anything about matroxfb.

With 2.4.21 I get

Jul 28 19:55:14 pervalidus kernel: matroxfb: Matrox G400 (AGP) detected
Jul 28 19:55:14 pervalidus kernel: matroxfb: MTRR's turned on
Jul 28 19:55:14 pervalidus kernel: matroxfb: 1024x768x24bpp (virtual: 1024x5460)
Jul 28 19:55:14 pervalidus kernel: matroxfb: framebuffer at 0xD8000000, mapped to 0xe0866000, size 33554432
Jul 28 19:55:14 pervalidus kernel: Console: switching to colour frame buffer device 128x48
Jul 28 19:55:14 pervalidus kernel: fb0: MATROX VGA frame buffer device

My .config and dmesg are at
http://www.pervalidus.net/tmp/.config-2.6.0-test2.txt
http://www.pervalidus.net/tmp/dmesg-2.6.0-test2.txt
http://www.pervalidus.net/tmp/dmesg-2.6.0-acpi=off+noapic-test2.txt

lspci -vvv returns

01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) (prog-if 00 [VGA])
        Subsystem: Matrox Graphics, Inc. Millennium G400 32Mb SDRAM
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (4000ns min, 8000ns max), cache line size 08
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at d8000000 (32-bit, prefetchable) [size=32M]
        Region 1: Memory at da000000 (32-bit, non-prefetchable) [size=16K]
        Region 2: Memory at db000000 (32-bit, non-prefetchable) [size=8M]
        Expansion ROM at <unassigned> [disabled] [size=64K]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [f0] AGP version 2.0
                Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
                Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x1

Re: matroxfb and 2.6.0-test2

[Petr Vandrovec]

On Mon, Jul 28, 2003 at 08:34:40PM -0300, Frédéric L. W. Meunier wrote:
> The card is a Matrox Millenium G400 M4A32DG (single head).
> 
> 2.6.0-test2 is the first 2.5.x I try, so I may be missing
> something.
> 
> During make modules_install I noticed the following warning
> (yes, I installed the latest module-init-tools):
> 
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.6.0-test2; fi
> WARNING: /lib/modules/2.6.0-test2/kernel/drivers/video/matrox/matroxfb_crtc2.ko
> needs unknown symbol matroxfb_enable_irq

Yes, I'll fix that. Arpi pointed that out to me when I backported
IRQ support to the 2.4.x. Just adding

EXPORT_SYMBOL(matroxfb_enable_irq);

at the end of drivers/video/matrox/matroxfb_base.c does the trick.
 
> I don't know if it's serious but then I rebooted from 2.4.21.
> 
> My init script contains
> 
> if lspci | grep -q 'MGA G400'; then
> modprobe matroxfb_base
> fi
> 
> and /etc/modprobe.conf options matroxfb_base vesa=440
> 
> After it the screen became corrupted with a dump of my last
> shutdown. All commands still worked. I don't use fbset at all.
> The logs don't have anything about matroxfb.

Try building matroxfb into the kernel. I believe that current VT system
does not take over console anymore if fbdev is loaded after fbcon, but
I never tested it myself.
							Petr Vandrovec

Re: matroxfb and 2.6.0-test2

[Frédéric L. W. Meunier]

On Tue, 29 Jul 2003, Petr Vandrovec wrote:

> On Mon, Jul 28, 2003 at 08:34:40PM -0300, Frédéric L. W. Meunier wrote:
> >
> > My init script contains
> >
> > if lspci | grep -q 'MGA G400'; then
> > modprobe matroxfb_base
> > fi
> >
> > and /etc/modprobe.conf options matroxfb_base vesa=440
> >
> > After it the screen became corrupted with a dump of my last
> > shutdown. All commands still worked. I don't use fbset at all.
> > The logs don't have anything about matroxfb.
>
> Try building matroxfb into the kernel. I believe that current VT system
> does not take over console anymore if fbdev is loaded after fbcon, but
> I never tested it myself.

Thanks. It worked (and I don't see any screen corruption).

Maybe I'm missing something, but is there anything wrong with
video=matroxfb:vesa:0x1B5 ? I got

Kernel command line: BOOT_IMAGE=3 root=307 acpi=off noapic video=matroxfb:vesa:0x1B5
Console: colour VGA+ 80x25
matroxfb: Matrox G400 (AGP) detected
matroxfb: MTRR's turned on
matroxfb: 800x600x24bpp (virtual: 800x65536)
matroxfb: framebuffer at 0xD8000000, mapped to 0xe0805000, size 33554432
fb0: MATROX frame buffer device
fb0: initializing hardware
matroxfb: cannot set xres to 800, rounded up to 832
Console: switching to colour frame buffer device 100x37
 /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 p10 >
Console: switching to colour frame buffer device 100x37
matroxfb_crtc2: secondary head of fb0 was registered as fb1

and the monitor was black on part (a few cm) of the left side,
although everything was on the screen.

It worked fine with what I'm used to, 1024x768x32bpp;

Kernel command line: BOOT_IMAGE=3 root=307 acpi=off noapic video=matroxfb:vesa:0x1B8
Console: colour VGA+ 80x25
matroxfb: Matrox G400 (AGP) detected
matroxfb: MTRR's turned on
matroxfb: 1024x768x24bpp (virtual: 1024x65536)
matroxfb: framebuffer at 0xD8000000, mapped to 0xe0805000, size 33554432
fb0: MATROX frame buffer device
fb0: initializing hardware
Console: switching to colour frame buffer device 128x48
 /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 p10 >
Console: switching to colour frame buffer device 128x48
matroxfb_crtc2: secondary head of fb0 was registered as fb1

and with the default:

Kernel command line: BOOT_IMAGE=3 root=307 acpi=off noapic
Console: colour VGA+ 80x25
matroxfb: Matrox G400 (AGP) detected
matroxfb: MTRR's turned on
matroxfb: 640x480x8bpp (virtual: 640x65536)
matroxfb: framebuffer at 0xD8000000, mapped to 0xe0805000, size 33554432
fb0: MATROX frame buffer device
fb0: initializing hardware
Console: switching to colour frame buffer device 80x30
 /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 p10 >
Console: switching to colour frame buffer device 80x30
matroxfb_crtc2: secondary head of fb0 was registered as fb1

BTW, I'm pretty syre I only got the following warning compiling
as a module (GCC 2.95.4):

  CC [M]  drivers/video/matrox/matroxfb_base.o
drivers/video/matrox/matroxfb_base.c:1230: warning: `inverse' defined but not used

Re: matroxfb and 2.6.0-test2

[Wakko Warner]

> > WARNING: /lib/modules/2.6.0-test2/kernel/drivers/video/matrox/matroxfb_crtc2.ko
> > needs unknown symbol matroxfb_enable_irq

I have an old matrox millenium 1 card.  does the matrox fb support this
card?  All I got was a blank screen.  fbcon and matroxfb with support for
I/II cards compiled in.  When I had vga16 compiled in as well, I would get the
console if I switched to vt2 and back to vt1.

I don't know if there's an IRQ being assigned to the card.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

Re: matroxfb and 2.6.0-test2

[James Simmons]

> > After it the screen became corrupted with a dump of my last
> > shutdown. All commands still worked. I don't use fbset at all.
> > The logs don't have anything about matroxfb.
> 
> Try building matroxfb into the kernel. I believe that current VT system
> does not take over console anymore if fbdev is loaded after fbcon, but
> I never tested it myself.

Correct. You need run con2fb if you load a fbdev driver after fbcon.c. 
This maps the framebuffer to the console.

Re: matroxfb and 2.6.0-test2

[Petr Vandrovec]

On 29 Jul 03 at 7:27, Wakko Warner wrote:

> I have an old matrox millenium 1 card.  does the matrox fb support this
> card?  All I got was a blank screen.  fbcon and matroxfb with support for
> I/II cards compiled in.  When I had vga16 compiled in as well, I would get the
> console if I switched to vt2 and back to vt1.

Yes, it supports Millennium1 too. Are you sure that you built fbcon
support into the kernel? And that you have only one fbdev, matroxfb?
>From your description it looks to me like that you are using vesafb
together with matroxfb.
                                                    Petr
                                                    

Re: matroxfb and 2.6.0-test2

[Wakko Warner]

> > I have an old matrox millenium 1 card.  does the matrox fb support this
> > card?  All I got was a blank screen.  fbcon and matroxfb with support for
> > I/II cards compiled in.  When I had vga16 compiled in as well, I would get the
> > console if I switched to vt2 and back to vt1.
> 
> Yes, it supports Millennium1 too. Are you sure that you built fbcon
> support into the kernel? And that you have only one fbdev, matroxfb?

Yes.  This caused a permenant black screen.  fbset did not give me anything
usable.  Monitor did not go into powersave.

> >From your description it looks to me like that you are using vesafb
> together with matroxfb.

I did, but that caused it to give a blank screen until I changed VTs.
I removed both vesafb and vga16 and recompiled to achive the result I stated
above.

I'll try 2.6.0-test2 later on today.  I did not do a make clean between
compiles.  When I compile test2, it will be clean, I never patch dirty
trees.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

Re: matroxfb and 2.6.0-test2

[Petr Vandrovec]

On 29 Jul 03 at 8:53, Wakko Warner wrote:
> > 
> > Yes, it supports Millennium1 too. Are you sure that you built fbcon
> > support into the kernel? And that you have only one fbdev, matroxfb?
> 
> Yes.  This caused a permenant black screen.  fbset did not give me anything
> usable.  Monitor did not go into powersave.

I assume that machine is otherwise OK. Can you capture 'dmesg' from
such boot and post them?
                                            Petr
                                            

Re: matroxfb and 2.6.0-test2

[Wakko Warner]

> > > Yes, it supports Millennium1 too. Are you sure that you built fbcon
> > > support into the kernel? And that you have only one fbdev, matroxfb?
> > 
> > Yes.  This caused a permenant black screen.  fbset did not give me anything
> > usable.  Monitor did not go into powersave.
> 
> I assume that machine is otherwise OK. Can you capture 'dmesg' from
> such boot and post them?

First: 2.6.0-test2 does not come up with a blank screen.
Second: using fbset to set another mode (1024x768-60) causes a blank screen
but changing vts gives me the screen back.  It must be using a different
frequency since the screen is not inthe same place.  setting 680x480-60
makes it look right again.  The actual resolution doesn't appear to change. 
If I have enough written to the screen after issueing the 1024x768, the text
becomes garbled (old text seems to interlace into current.

Any ideas?

Here's my .config (stripped, jsut console/fb stuff)
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y

CONFIG_FB=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
  where did this come from?!
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_FONT_6x11=y
CONFIG_FONT_PEARL_8x8=y
CONFIG_FONT_ACORN_8x8=y
CONFIG_FONT_MINI_4x6=y
CONFIG_FONT_SUN8x16=y
CONFIG_FONT_SUN12x22=y

Here's the FULL dmesg (including modules I loaded later)
Linux version 2.6.0-test2 (root@kingkai) (gcc version 3.3.1 20030626 (Debian prerelease)) #1 Tue Jul 29 15:50:23 EDT 2003
Video mode to be used for restore is f00
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
 BIOS-e820: 000000000fff0000 - 000000000fff3000 (ACPI NVS)
 BIOS-e820: 000000000fff3000 - 0000000010000000 (ACPI data)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
255MB LOWMEM available.
On node 0 totalpages: 65520
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 61424 pages, LIFO batch:14
  HighMem zone: 0 pages, LIFO batch:1
ACPI: RSDP (v000 MSISYS                     ) @ 0x000f7290
ACPI: RSDT (v001 MSISYS MS-6163W 12336.11826) @ 0x0fff3000
ACPI: FADT (v001 MSISYS MS-6163W 12336.11826) @ 0x0fff3040
ACPI: DSDT (v001 MSISYS AWRDACPI 00000.04096) @ 0x00000000
ACPI: BIOS passes blacklist
Building zonelist for node : 0
Kernel command line: BOOT_IMAGE=linux ro root=301
Initializing CPU#0
PID hash table entries: 1024 (order 10: 8192 bytes)
Detected 701.809 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 1388.54 BogoMIPS
Memory: 256432k/262080k available (1475k kernel code, 4920k reserved, 448k data, 108k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
-> /dev
-> /dev/console
-> /root
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU serial number disabled.
CPU:     After generic, caps: 0383f9ff 00000000 00000000 00000040
CPU: Intel Pentium III (Coppermine) stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
Initializing RT netlink socket
PCI: PCI BIOS revision 2.10 entry at 0xfb240, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
BIO: pool of 256 setup, 14Kb (56 bytes/bio)
biovec pool[0]:   1 bvecs: 256 entries (12 bytes)
biovec pool[1]:   4 bvecs: 256 entries (48 bytes)
biovec pool[2]:  16 bvecs: 256 entries (192 bytes)
biovec pool[3]:  64 bvecs: 256 entries (768 bytes)
biovec pool[4]: 128 bvecs: 256 entries (1536 bytes)
biovec pool[5]: 256 bvecs: 256 entries (3072 bytes)
ACPI: Subsystem revision 20030714
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11 12 14 15, disabled)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
matroxfb: Matrox Millennium (PCI) detected
matroxfb: MTRR's turned on
matroxfb: 640x480x8bpp (virtual: 640x65536)
matroxfb: framebuffer at 0xE5000000, mapped to 0xd080d000, size 8388608
fb0: MATROX frame buffer device
fb0: initializing hardware
Console: switching to colour frame buffer device 80x30
pty: 256 Unix98 ptys configured
Enabling SEP on CPU 0
Journalled Block Device driver loaded
Initializing Cryptographic API
Limiting direct PCI/PCI transfers.
ACPI: Power Button (FF) [PWRF]
ACPI: Fan [FAN0] (on)
ACPI: Processor [CPU0] (supports C1 C2, 8 throttling states)
Asus Laptop ACPI Extras version 0.24a
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: WDC AC34000L, ATA DISK drive
Using anticipatory scheduling elevator
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: ATAPI CDROM, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: 7814016 sectors (4001 MB) w/256KiB Cache, CHS=7752/16/63
 hda: hda1 hda2 hda3 hda4
Console: switching to colour frame buffer device 80x30
mice: PS/2 mouse device common for all mice
input: PC Speaker
input: PS/2 Logitech Mouse on isa0060/serio1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
NET4: Linux TCP/IP 1.0 for NET4.0
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 108k freed
EXT3 FS on hda1, internal journal
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
Module md cannot be unloaded due to unsafe usage in include/linux/module.h:483
SCSI subsystem initialized
md: could not lock unknown-block(8,0).
md: could not import unknown-block(8,0)!
md: autostart unknown-block(8,0) failed!
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
uhci-hcd 0000:00:07.2: PCI device 8086:7112
uhci-hcd 0000:00:07.2: irq 11, io base 0000e000
uhci-hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
hub 1-0:0: USB hub found
hub 1-0:0: 2 ports detected
typhoon.c: version 1.5.1 (03/06/26)
eth0: 3Com Typhoon (3CR990SVR97) at 0xd1017000, 00:04:76:e0:9c:7b
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
process `named' is using obsolete setsockopt SO_BSDCOMPAT
process `nd' is using obsolete setsockopt SO_BSDCOMPAT
process `named' is using obsolete setsockopt SO_BSDCOMPAT
process `named' is using obsolete setsockopt SO_BSDCOMPAT
process `named' is using obsolete setsockopt SO_BSDCOMPAT
process `named' is using obsolete setsockopt SO_BSDCOMPAT
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
nfsd: last server has exited
nfsd: unexporting all filesystems
hub 1-0:0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 1-0:0: new USB device on port 2, assigned address 2
hub 1-0:0: debounce: port 1: delay 100ms stable 4 status 0x101
hub 1-0:0: new USB device on port 1, assigned address 3
drivers/usb/core/usb.c: registered new driver usbscanner
drivers/usb/image/scanner.c: 0.4.14:USB Scanner Driver
ppdev: user-space parallel port driver
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP]
parport0: irq 7 detected
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
ppdev0: registered pardevice
ppdev0: unregistered pardevice
lp0: using parport0 (polling).
ppdev0: registered pardevice
ppdev0: unregistered pardevice
ppdev0: registered pardevice
ppdev0: unregistered pardevice
usb 1-1: USB disconnect, address 3
Initializing USB Mass Storage driver...
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

Re: matroxfb and 2.6.0-test2

[Frédéric L. W. Meunier]

On Tue, 29 Jul 2003, Petr Vandrovec wrote:

> On 29 Jul 03 at 2:14, Frédéric L. W. Meunier wrote:
> > On Tue, 29 Jul 2003, Petr Vandrovec wrote:
> > > On Mon, Jul 28, 2003 at 08:34:40PM -0300, Frédéric L. W. Meunier wrote:
> >
> > Thanks. It worked (and I don't see any screen corruption).
> >
> > Maybe I'm missing something, but is there anything wrong with
> > video=matroxfb:vesa:0x1B5 ? I got
>
> I have no idea...
>
> > Kernel command line: BOOT_IMAGE=3 root=307 acpi=off noapic video=matroxfb:vesa:0x1B5
> > Console: colour VGA+ 80x25
> > matroxfb: Matrox G400 (AGP) detected
> > matroxfb: MTRR's turned on
> > matroxfb: 800x600x24bpp (virtual: 800x65536)
> > matroxfb: framebuffer at 0xD8000000, mapped to 0xe0805000, size 33554432
> > fb0: MATROX frame buffer device
> > fb0: initializing hardware
> > matroxfb: cannot set xres to 800, rounded up to 832
> > Console: switching to colour frame buffer device 100x37
> >  /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 p10 >
> > Console: switching to colour frame buffer device 100x37
>
> ... but it looks strange to me that you have two 'switching to...' lines.

I don't have two with your patch.

> Unless it gets proven that it is bug in kernel's matroxfb and not
> in generic fbcon (== if you'll send me a patch, I'll apply it; but do
> not expect that I'll hunt down bugs which do not occur with matroxfb-2.5.72
> addon), I recommend you applying
> ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/matroxfb-2.5.72.gz.
> It reinstates back fbcon layer I understand & trust...

2 other problems went away with your patch. When I reported no
screen corruption I was wrong since it messed everything
returning from XFree86, including getting a dump of a Windows
reboot. The other is the boot logo, which now appears.

Re: matroxfb and 2.6.0-test2

[Frédéric L. W. Meunier]

On Tue, 29 Jul 2003, Petr Vandrovec wrote:

> On 29 Jul 03 at 16:41, Frédéric L. W. Meunier wrote:
> > On Tue, 29 Jul 2003, Petr Vandrovec wrote:
>
> > > Unless it gets proven that it is bug in kernel's matroxfb and not
> > > in generic fbcon (== if you'll send me a patch, I'll apply it; but do
> > > not expect that I'll hunt down bugs which do not occur with matroxfb-2.5.72
> > > addon), I recommend you applying
> > > ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/matroxfb-2.5.72.gz.
> > > It reinstates back fbcon layer I understand & trust...
> >
> > 2 other problems went away with your patch. When I reported no
> > screen corruption I was wrong since it messed everything
> > returning from XFree86, including getting a dump of a Windows
> > reboot. The other is the boot logo, which now appears.
>
> I think that screen corruption is just timming issue, and you
> should see it... On PII/333, with G400, Debian's XF4.2.1-9, if
> I set clocks in Gnome2 to show seconds, hardware is again reprogrammed
> every second by XFree on the background...

Here Athlon XP 1700+, XFree86 4.3.0.1, IceWM 1.2.9. Clocks with
seconds on both window manager and screen, but it happens
without them and if I just startx and close it. As I reported
it doesn't happen with your patch, but I may be seeing the
other "problem" you mentioned at
http://marc.theaimsgroup.com/?l=3Dlinux-kernel&m=3D105908939813118&w=3D2

"BTW, with my patch accented characters works correctly only on
VT1.  I'm not sure how it behaves on Linus tree..."

Same behavior without your patch. Here I use setfont
lat1-16.psfu in my init scripts. All accents work on the first
console but on the others most miss them for capitals.

Re: matroxfb and 2.6.0-test2

[Petr Vandrovec]

On 30 Jul 03 at 11:43, Wakko Warner wrote:
> > I assume that machine is otherwise OK. Can you capture 'dmesg' from
> > such boot and post them?
> 
> First: 2.6.0-test2 does not come up with a blank screen.

What is on screen? Correct 640x480 picture?

> Second: using fbset to set another mode (1024x768-60) causes a blank screen
> but changing vts gives me the screen back.  It must be using a different
> frequency since the screen is not inthe same place.  setting 680x480-60
> makes it look right again.  The actual resolution doesn't appear to change. 
> If I have enough written to the screen after issueing the 1024x768, the text
> becomes garbled (old text seems to interlace into current.

Do you use matroxfb-2.5.72 patch or not? You are not supposed to use
fbset on stock 2.6.x kernel (without patch above), you should use
stty cols & rows to set videomode under 2.6.x kernels (you can try
using fbset -pixclock to set refresh, but never change picture size
through fbset).
                                            Petr Vandrovec