From owner-freebsd-stable Thu Aug 17 18:56: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.129.65]) by hub.freebsd.org (Postfix) with ESMTP id E5CB937BEC4 for ; Thu, 17 Aug 2000 18:51:34 -0700 (PDT) Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.66.63.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id D33E16E4039 for ; Thu, 17 Aug 2000 13:57:11 -0700 (PDT) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id NAA89178; Thu, 17 Aug 2000 13:55:39 -0700 (PDT) (envelope-from richw) Date: Thu, 17 Aug 2000 13:55:39 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: Memory sizing, AGP video card Message-ID: <200008172087162.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just installed 4.1-RELEASE on a Dell OptiPlex GX300. This system has (amongst other things) 128 MB of ECC RAM, and an "NVidia Riva Ultra Vanta TNT2 graphics accelerator" AGP video card. The documentation from Dell claims the video card has 32 MB of memory, but the card doesn't appear to have any on-board memory, so I suspect it's really using the top 32 MB of the system's RAM. When I first tried bringing up 3.5-RELEASE on this machine, it kept hanging during boot (locked up immediately after outputting the copy- right banners). After a lot of fiddling, I finally got it to boot by limiting memory size to 96 MB (via the older kludge of specifying "iosiz 98304" on the "device npx0" configuration line). Anything larger than 96 MB, and it would hang during boot. When I reinstalled from scratch with 4.1-RELEASE, the kernel detected (almost) 128 MB, and everything seemed to run OK. However, after a couple of mysterious userland crashes, I started getting suspicious that maybe the kernel wasn't handling the video card memory properly. So I built a new kernel with MAXMEM="(96*1024)". Presumably, an ideal kernel would know what was going on with the video card and adjust its handling of RAM accordingly. Or, perhaps 4.1-RELEASE was doing this already (!), in which case my mysterious userland crashes were caused by something else entirely. Any thoughts? Rich Wales richw@webcom.com http://www.webcom.com/richw/ ======================================================================== Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-RELEASE #2: Thu Aug 17 08:31:06 PDT 2000 root@wyattearp.stanford.edu:/misc/4.1/usr/src/sys/compile/WYATTEARP Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 794662252 Hz CPU: Pentium III/Pentium III Xeon/Celeron (794.66-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 100663296 (98304K bytes) avail memory = 94253056 (92044K bytes) Preloaded elf kernel "kernel" at 0xc0386000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 9 pcib2: at device 30.0 on pci0 pci2: on pcib2 adv0: port 0xec00-0xecff mem 0xfafffc00-0xfafffcff irq 9 at device 7.0 on pci2 adv0: AdvanSys Ultra SCSI Host Adapter, SCSI ID 7, queue depth 240 pcm0: port 0xe8e0-0xe8ff irq 10 at device 8.0 on pci2 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xe800-0xe87f mem 0xfafff800-0xfafff87f irq 5 at device 12.0 on pci2 xl0: Ethernet address: 00:b0:d0:24:25:4d miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xff80-0xff9f irq 11 at device 31.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port 1 power on failed, IOERROR uhub0: port 2 power on failed, IOERROR pci0: (vendor=0x8086, dev=0x2413) at 31.3 irq 10 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, unlimited logging DUMMYNET initialized (000608) IP Filter: v3.4.8 initialized. Default = pass all, Logging = enabled ata0-master: DMA limitted to UDMA33, non-ATA66 compliant cable ad0: 14324MB [29104/16/63] at ata0-master using UDMA33 ad1: 9617MB [19540/16/63] at ata0-slave using UDMA33 acd0: CDROM at ata1-master using PIO4 afd0: 96MB [32/64/96] at ata1-slave using PIO0 Waiting 15 seconds for SCSI devices to settle sa0 at adv0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 8) pass0 at adv0 bus 0 target 3 lun 0 pass0: Fixed Scanner SCSI-2 device pass0: 3.300MB/s transfers Mounting root from ufs:/dev/ad0s2a cd0 at adv0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present ======================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message