At 08:54 PM 5/11/2008, Novembre wrote:
On Sun, May 11, 2008 at 5:42 PM, Derek Ragona
<<mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED]> 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: <ACPI PCI bus> on pcib0
agp0: <VIA 862x (CLE266) host to PCI bridge> mem 0xe0000000-0xe0ffffff at
device 0.0 on pci0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
7.0-RELEASE:
pci0: <ACPI PCI bus> on pcib0
agp0: <VIA 862x (CLE266) host to PCI bridge> 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: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
vgapci0: <VGA-compatible display> 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>http://pastebin.com/f12c0ff27
7.0-RELEASE dmesg
: <http://pastebin.com/f3e6809c6>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 <http://www.mailscanner.info/>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.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
