Date: Tue, 30 Mar 1999 09:16:25 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Alexander Leidinger <netchild@wurzelausix.cs.uni-sb.de> Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Bug with VESA? Message-ID: <199903300016.JAA01403@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Mon, 29 Mar 1999 22:41:14 %2B0200." <199903292041.WAA01387@vodix.aremorika> References: <199903292041.WAA01387@vodix.aremorika>
next in thread | previous in thread | raw e-mail | index | archive | help
>cvsup 7pm CET.
>
>I'm not able to switch to 132x60 anymore. Last cvsup was around feb 1999.
Please check the revision of /sys/i386/isa/vesa.c. Is it 1.18 or
1.19?
I committed fix for a palette loading problem in vesa.c at 7am PST.
This is the latest revision (1.19). The modification has nothing to
do with the VESA BIOS initialization and shouldn't be causing this
sort of problem. But,...
>dmesg:
>VESA: v0.40, 40960k memory, flags:0x74610000, mode table: 0xc08de022 (280c000)
~~~~~ ~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
> ^^^^^ seems to be wrong (4096k)
They all look wrong ;-<
>VESA: Matrox Graphics Inc.
> (it's a Mystique 220)
Right. I think I can find one around here.
>vga0: <Matrox MGA 1024SG/1064SG/1164SG graphics accelerator> rev 0x03 int a ir
>q
>11 on pci0.12.0
>sc0: flags 0x6 on isa
>sc0: VGA color <16 virtual consoles, flags=0x6>
>
>More (dmesg/...) on request via private mail.
Please give the '-v' option at the boot loader prompt when starting
the kernel. and send me the complete dmesg output and your kernel
configuration file.
Thank you for your cooperation.
Kazu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903300016.JAA01403>