From owner-freebsd-questions@FreeBSD.ORG Sun May 11 22:40:39 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EECDD1065674 for ; Sun, 11 May 2008 22:40:38 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from betty.computinginnovations.com (mail.computinginnovations.com [64.81.227.250]) by mx1.freebsd.org (Postfix) with ESMTP id A944A8FC18 for ; Sun, 11 May 2008 22:40:38 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from p28.computinginnovations.com (dhcp-10-20-30-100.computinginnovations.com [10.20.30.100]) (authenticated bits=0) by betty.computinginnovations.com (8.14.2/8.14.2) with ESMTP id m4BMeSbl041780; Sun, 11 May 2008 17:40:29 -0500 (CDT) (envelope-from derek@computinginnovations.com) Message-Id: <6.0.0.22.2.20080511174125.02661810@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Sun, 11 May 2008 17:42:19 -0500 To: Novembre , "FreeBSD Questions" From: Derek Ragona In-Reply-To: <3b47caa90805111217n557e977ese6b31b71130f79ff@mail.gmail.co m> References: <3b47caa90805111217n557e977ese6b31b71130f79ff@mail.gmail.com> Mime-Version: 1.0 X-Antivirus: avast! (VPS 080511-0, 05/11/2008), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: ClamAV 0.93/6806/Wed Apr 16 15:50:16 2008 on betty.computinginnovations.com X-Virus-Status: Clean X-ComputingInnovations-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: m4BMeSbl041780 X-ComputingInnovations-MailScanner: Found to be clean X-ComputingInnovations-MailScanner-From: derek@computinginnovations.com X-Spam-Status: No Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: agp problems in 7.0-RELEASE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2008 22:40:39 -0000 At 02:17 PM 5/11/2008, Novembre wrote: >Hi all, > >I have upgraded my home desktop (1.4GHz P-IIIS) machine from 6.2-RELEASE-p9 >to 7.0-RELEASE some time ago. When comparing the two dmesg outputs from 6.2 >and 7.0, I realized that some things aren't the same anymore. > >Probing agp gives the following messages >---------- >6.2-RELEASE-p9: >pci0: on pcib0 >agp0: mem 0xe0000000-0xe0ffffff at >device 0.0 on pci0 >pcib1: at device 1.0 on pci0 >pci1: on pcib1 >pci1: at device 0.0 (no driver attached) > >7.0-RELEASE: >pci0: on pcib0 >agp0: on hostb0 >agp0: Invalid aperture setting 0x0agp0: Invalid aperture setting 0x0agp0: >bad aperture size >agp0: Invalid aperture setting 0x0agp0: Invalid aperture size (0Mb) >device_attach: agp0 attach returned 12 >pcib1: at device 1.0 on pci0 >pci1: on pcib1 >vgapci0: mem >0xd8000000-0xdbffffff,0xde000000-0xdeffffff >at device 0.0 on pci1 >---------- > >So what are the errors "agp0: Invalid aperture setting 0x0" and "agp0: bad >aperture size (0Mb)" and "device_attach: agp0 attach returned 12" that I see >in 7.0-RELEASE? I assume that agp driver is not attached, so there's >something wrong with its implementation in 7.0, right? > >I have uploaded the complete dmesg's to >6.2-RELEASE dmesg : http://pastebin.com/f12c0ff27 >7.0-RELEASE dmesg : http://pastebin.com/f3e6809c6 > >Thanks a lot :) The agp aperture size is usually set in the BIOS. Check your BIOS. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.