From owner-freebsd-current Mon Dec 4 6:17: 5 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 4 06:17:01 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id E40A737B400; Mon, 4 Dec 2000 06:16:56 -0800 (PST) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id QAA06410; Mon, 4 Dec 2000 16:16:51 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 6387; Mon Dec 4 16:16:26 2000 Sender: gram@citadel.cequrux.com Message-ID: <3A2B8ED4.CEA4D76@cequrux.com> Date: Mon, 04 Dec 2000 14:32:20 +0200 From: Graham Wheeler Reply-To: gramster@bigfoot.com Organization: Cequrux Technologies X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Cc: freebsd-current@freebsd.org Subject: ATI Rage Mobility and VESA driver Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again With regard to my earlier message, I mentioned: > My laptop has an ATI Rage Mobility AGP card in it. According to ATI rech > support, this card is VESA-compliant - but FreeBSD doesn't recognise it > as such. > I searched the mailing list archives, and found >> /usr/src/sys/i386/isa/vesa.c, line 680: >> if ((vmode.v_modeattr & (V_MODEOPTINFO | V_MODENONVGA)) >> != (V_MODEOPTINFO)) >> continue; >> >> The v_modeattr returned by ATI VESA bios has V_MODENONVGA bit set, >> so all the vesa modes are ommited... >so I hacked this code to ignore the V_MODENONVGA flag. This was only >partially successful: I now get some VESA stuff being printed upon boot, >but still can't use any of the VESA modes. I noticed that vesa.c 1.34 has this change in it (4.2-stable is still using vesa.c 1.32). This does buy me some progress, in that I get some better dmesg output: VESA: v2.0, 8128k memory, flags:0x0, mode_table:0xc02b6f62 (1000022) VESA: ATI MACH64 However, using vidcontrol and attempting to set any VESA modes still produces "operation not supported by device". I guess the next step is to get all the debug output from vesa.c, and see if it finds any usable VESA modes at all. [I'm cross-posting this to freebsd-current, as it seems to be relevant to the latest vesa.c changes] gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message