Description: Everything refresh slow, when minimize and maximize windows. The Motherboard is ASRock G41M-LE, Intel G41 Chipset and Intel GMA X4500 video: http://www.asrock.com/mb/overview.asp?Model=G41M-LE&s=775 , and the problem is: *ERROR* Detected broken video BIOS with 262140/262144kB of video memory stolen. I boot with i915.modeset=0 in GRUB. If no this option kernel can't boot. I don't have xorg.conf file. Update to last BIOS version(1.90). Additional info: * package version(s) kernel26 - 2.6.32.3-1 Try and kernel26-2.6.33-rc4 problem is still there xf86-video-intel - 2.9.1-1 intel-dri - 7.7-1 Everything up-to-date... * config and/or log files etc. [xxxx@xxxx ~]$ dmesg | grep drm [drm] Initialized drm 1.1.0 20060810 [drm] MTRR allocation failed. Graphics performance may suffer. [drm:i915_driver_load] *ERROR* Detected broken video BIOS with 262140/262144kB of video memory stolen. [drm:i915_driver_load] *ERROR* Disabling GEM. (try reducing stolen memory or updating the BIOS to fix). [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 [xxxx@xxxx ~]$ lspci 00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03) 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) 00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller (rev 01) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01) 03:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) [xxxx@xxxx ~]$ cat /proc/mtrr reg00: base=0x000000000 ( 0MB), size= 4096MB, count=1: write-back reg01: base=0x100000000 ( 4096MB), size= 512MB, count=1: write-back reg02: base=0x120000000 ( 4608MB), size= 256MB, count=1: write-back reg03: base=0x0d0000000 ( 3328MB), size= 256MB, count=1: uncachable reg04: base=0x0e0000000 ( 3584MB), size= 512MB, count=1: uncachable reg05: base=0x0bfe00000 ( 3070MB), size= 2MB, count=1: uncachable reg06: base=0x0c0000000 ( 3072MB), size= 256MB, count=1: uncachable Found this old things on internet but don't know wath to do? http://lists.freedesktop.org/archives/intel-gfx/2009-July/003180.html http://bugs.archlinux.org/task/11875 http://ubuntuforums.org/showthread.php?t=1367907
Created attachment 24594 [details] dmesg
Created attachment 24595 [details] Xorg.0.log
Created attachment 24596 [details] lsmod
Will you please add the boot option of "nomodeset" and attach the output of "lspci -vxxx"? thanks.
Hi, Kras can you change the size of stolen memory in BIOS option and see whether the system can be booted? thanks.
Thank you for replay Yakui. As I write here: http://ubuntuforums.org/showthread.php?t=1367907 I change in BIOS --> Advanced Screen --> PAVP Mode(Disabled) and Primary Graphics Adapter = Onboard and Share Memory = 128MB, Remove i915.modeset=0 from GRUB and with this configuration of BIOS everything is OK, even compiz work. But with Share Memory = 256MB error is still here.(*ERROR* Detected broken video BIOS with 262140/262144kB of video memory stolen. ...) My video card is Intel GMA X4500 and have max 256MB memory, even under 64-bit OS Max. shared memory 1759MB(see http://www.asrock.com/MB/overview.asp?Model=G41M-LE) but I use 32-bit Archlinux and 64-bit Ubuntu 10.04 Alpha2(for testing) and I will be happy to use 256MB of Video Memory. I look in this files /drivers/char/agp/intel-agp.c and /drivers/gpu/drm/i915/i915_dma.c from kernel 2.6.33-rc4 but I'm not a programmer and don't understand what to do...
Created attachment 24636 [details] lspci -vxxx with nomodeset in GRUB
Created attachment 24637 [details] lspci -vxxxx with nomodeset in GRUB just in case
Created attachment 24638 [details] lspci -vxxx with i915.modeset=0 in GRUB
Now I boot with 128MB of video memory and everything is OK here is output from dmesg: [xxxx@xxxx ~]$ dmesg | grep drm [drm] Initialized drm 1.1.0 20060810 [drm] MTRR allocation failed. Graphics performance may suffer. [drm] set up 127M of stolen space [drm] DAC-6: set mode 1280x1024 24 [drm] TMDS-8: set mode 1360x768 28 fb0: inteldrmfb frame buffer device [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 [drm] DAC-6: set mode 1024x768 2a [drm] TMDS-8: set mode 1024x768 2b But as I mention will be happy to use all my video memory - 256MB. Thank you for your time!
Hi, Kras You mix the two concepts related with gfx memory. One is the total gfx memory that can be used by BIOS and OS. From the lspci info the memory size is 256M. The second is the gfx stolen memory, which is initialized by BIOS. The BIOS option only means the size of stolen memory. In fact this stolen memory size must be less than the total gfx memory. Otherwise the gfx driver will have no available memory. Of course it can't work. So IMO this is not bug. Instead we misunderstand the gfx memory concepts(total memory, stolen memory).
Yeah, marking as invalid. You only need 8M or so of stolen memory to set up FBC and a few other small things. Really we should be able to handle large stolen memory areas by just returning them to the OS, but that's a feature we haven't added yet.