Date: Tue, 02 Sep 2003 11:59:49 +1000 From: Iain Templeton <iain.templeton@cisra.canon.com.au> To: David Gilbert <dgilbert@dclg.ca> Cc: freebsd-mobile@freebsd.org Subject: Re: Intel 810 chipset has 892_KB_ of memory? Message-ID: <20030902020005.DCFAA98E7D@blow.research.canon.com.au> In-Reply-To: <16211.62515.278331.521009@canoe.velocet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
G'day David, --Original Message--: >I'm including the relative log files, but it seems to all come down to >something strange with VESA et. al. I have a Dell Inspirion 1100 that >I'm working on. It has a 32M intel 845 (i810 XFree86 driver) in it. >When I run X on it, X is convinced that a small region of this (892kb) >is all there is by some BIOS (?!?) call. > >If you're looking at the logs below, you probably want to search for >'Maximum space available' and start there ... and work back. > >892kb is only enough for 1024x768 in 8 bit colour ... which is really >ugly (nobody programms for 8 bit colour any more). So the unit is >only barely usable. Help? > I have an i830M chipset which does the same thing, but don't have any troubles with it. I have a line in my XF86Config that tells it I have more memory, and I can happily run 1024x768 in 24/32 bits (it a laptop, so there isn't much point to run any higher). If you look below though, X claims to have told the card it has more memory... [ Snip ] >(II) I810(0): initializing int10 >(==) I810(0): Write-combining range (0xa0000,0x20000) was already clear >(==) I810(0): Write-combining range (0xc0000,0x40000) was already clear >(II) I810(0): Primary V_BIOS segment is: 0xc000 >(==) I810(0): Write-combining range (0x0,0x1000) was already clear >(II) I810(0): VESA BIOS detected >(II) I810(0): VESA VBE Version 3.0 >(II) I810(0): VESA VBE Total Mem: 832 kB >(II) I810(0): VESA VBE OEM: Intel(r)845G/845GL/845GE/845GV Graphics Chip Accelerated VGA BIOS >(II) I810(0): VESA VBE OEM Software Rev: 1.0 >(II) I810(0): VESA VBE OEM Vendor: Intel Corporation >(II) I810(0): VESA VBE OEM Product: Intel(r)845G/845GL/845GE/845GV Graphics Controller >(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0 >(II) I810(0): Integrated Graphics Chipset: Intel(R) 845G >(--) I810(0): Chipset: "845G" >(--) I810(0): Linear framebuffer at 0xE0000000 >(--) I810(0): IO registers at addr 0xF6F80000 >(==) I810(0): Write-combining range (0xf6f80000,0x80000) was already clear >(II) I810(0): detected 892 kB stolen memory. >(II) I810(0): I830CheckAvailableMemory: 450560 kB available >(II) I810(0): Will attempt to tell the BIOS that there is 12288 kB VideoRAM Well, that is a little bit more memory here... >(WW) I810(0): Extended BIOS function 0x5f11 not supported. >(II) I810(0): Before: SWF1 is 0x00000001 >(II) I810(0): After: SWF1 is 0x00000008 >(==) I810(0): Write-combining range (0x0,0x1000) was already clear >(II) Loading sub module "int10" >(II) LoadModule: "int10" >(II) Reloading /usr/X11R6/lib/modules/libint10.a >(II) I810(0): initializing int10 >(==) I810(0): Write-combining range (0xa0000,0x20000) was already clear >(II) I810(0): Primary V_BIOS segment is: 0xc000 >(==) I810(0): Write-combining range (0x0,0x1000) was already clear >(II) I810(0): VESA BIOS detected >(II) I810(0): VESA VBE Version 3.0 >(II) I810(0): VESA VBE Total Mem: 832 kB >(II) I810(0): VESA VBE OEM: Intel(r)845G/845GL/845GE/845GV Graphics Chip Accelerated VGA BIOS >(II) I810(0): VESA VBE OEM Software Rev: 1.0 >(II) I810(0): VESA VBE OEM Vendor: Intel Corporation >(II) I810(0): VESA VBE OEM Product: Intel(r)845G/845GL/845GE/845GV Graphics Controller >(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0 >(II) I810(0): BIOS now sees 832 kB VideoRAM >(--) I810(0): Pre-allocated VideoRAM: 892 kByte >(==) I810(0): VideoRAM: 32768 kByte Hello, this is even more video ram... [ SNIP ] >(--) I810(0): Maximum space available for video modes: 832 kByte Ah, but this is less again, hmm this is strange. Do you have a line in your XF86Config specifying the amount of Video Ram? I have one and haven't had any trouble with it at all (other than the acceleration being broken and causing all sorts of problems on virtual console switching - I've been meaning to try a newer version). Not a particularly helpful answer I suspect. Maybe try the XFree86 people, I think it is more likely to be them than FreeBSD. Iain
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030902020005.DCFAA98E7D>