From owner-freebsd-questions@FreeBSD.ORG Mon May 12 20:30:37 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 36A4B1065670 for ; Mon, 12 May 2008 20:30:37 +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 DBB978FC12 for ; Mon, 12 May 2008 20:30:36 +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 m4CKUSMQ064009; Mon, 12 May 2008 15:30:29 -0500 (CDT) (envelope-from derek@computinginnovations.com) Message-Id: <6.0.0.22.2.20080512153043.0265baf8@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Mon, 12 May 2008 15:32:16 -0500 To: Novembre From: Derek Ragona In-Reply-To: <3b47caa90805111854p113ae306la272de6adb27aea8@mail.gmail.co m> References: <3b47caa90805111217n557e977ese6b31b71130f79ff@mail.gmail.com> <6.0.0.22.2.20080511174125.02661810@mail.computinginnovations.com> <3b47caa90805111854p113ae306la272de6adb27aea8@mail.gmail.com> Mime-Version: 1.0 X-Antivirus: avast! (VPS 080512-0, 05/12/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: m4CKUSMQ064009 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: FreeBSD Questions Subject: Re: {Spam?} 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: Mon, 12 May 2008 20:30:37 -0000 At 08:54 PM 5/11/2008, Novembre wrote: >On Sun, May 11, 2008 at 5:42 PM, Derek Ragona ><derek@computinginnovations.com> wrote: >>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. > > >Hi, > >It could be a possibility, but I haven't touched anything in the BIOS. >I've just upgraded my 6.2-RELEASE-p9 to 7.0-RELEASE from source. Besides, >I was not geting that error when using 6.2. Apparently, it's something >related to FreeBSD rather than my BIOS. > >Thanks :) While you may not have changed anything, I would verify the setting in your BIOS and possibly try a different setting. Most BIOS allow only for 2-3 settings. It may be you have a non-standard setting and the loader is seeing that as 0. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.