| View previous topic :: View next topic |
| Author |
Message |
aCOSwt
Bodhisattva
Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space
|
 Posted: Wed Jan 13, 2010 2:07 pm Post subject: X unable to set a MTRR |
 |
|
Hello,
1/ Mother board ASUS P5P43TD + 4G RAM + nVidia 9800GT 1G
Memory remapping enabled in BIOS
2/ Kernel (2.6.31.r6)
- MTRR features enabled + MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 1 + MTRR_SANITIZER_ENABLE_DEFAULT = 1
- Only the vesa frame buffer enabled.
3/ output of cat /proc/mtrr :
reg00, reg01, reg02, reg03, reg04 : write-back
reg05 base = 0x0fb000000 (4016MB) Size=8MB Count 1 write-combining
4/ xorg-server (1.6.5.r1) (xorg hal ipv6 nptl)+ vesa driver only, shutsdown after :
mtrr : base (0xfb000000) is not aligned on a size (0xe00000) boundary
mtrr : No mtrr for fb000000,e00000 found
5/ As far as mttr are concerned, maybe I should add that I append
"video=vesafb:mtrr:3,ywrap"
In my boot manager configuration file
where is the problem ? |
|
| Back to top |
|
 |
Mike Hunt
Watchman
Joined: 19 Jul 2009
Posts: 5287
|
| Posted: Wed Jan 13, 2010 5:31 pm Post subject: |
|
|
Can you pastebin your /usr/src/linux/.config
 http://pastebin.com
and paste the URL here please.
BTW, you don't need those video=vesafb:mtrr:3,ywrap things in your grub.conf. |
|
| Back to top |
|
|
aCOSwt
Bodhisattva
Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space
|
| Posted: Wed Jan 13, 2010 9:20 pm Post subject: |
|
|
| Mike Hunt wrote: | | BTW, you don't need those video=vesafb:mtrr:3,ywrap things in your grub.conf. |
BTW... it is not grub... 
 well... you are definitely right but... for my first gentoo install... I thought that I would better follow the handbook to the letter...
Here is for my .config : http://pastebin.com/m551ab532
Thank you Mike Hunt for your assistance.
P.S. : from the boot log, I deduce that 0xfb000000 is the start address of the frame buffer. |
|
| Back to top |
|
|
Mike Hunt
Watchman
Joined: 19 Jul 2009
Posts: 5287
|
| Posted: Wed Jan 13, 2010 9:46 pm Post subject: |
|
|
One thing I'm noticing is you don't need CONFIG_DRM=y for nVidia.
Here is what I have on an nVidia graphics box (via chipset) - (using the Gentoo Linux nVidia Guide): | Code: | # egrep '^[^#].*(MTRR|FB|DRM|AGP)' /usr/src/linux/.config
CONFIG_MTRR=y
CONFIG_AGP=m
CONFIG_AGP_VIA=m
CONFIG_FB=y
CONFIG_FB_BOOT_VESA_SUPPORT=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_VESA=y
|
Also do you have x11-drivers/nvidia-drivers-190.53-r1 - which is keyword masked? |
|
| Back to top |
|
|
aCOSwt
Bodhisattva
Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space
|
| Posted: Thu Jan 14, 2010 10:17 am Post subject: |
|
|
| Mike Hunt wrote: | | One thing I'm noticing is you don't need CONFIG_DRM=y for nVidia. |
You are right. I even do not need it with vesa.
Removed it.
Same mtrr problem.
| Mike Hunt wrote: | CONFIG_AGP=m
CONFIG_AGP_VIA=m
|
You get an AGP bus ?
As mine is an intel PCIe, I did not set the support for intel AGP.
I even realize that I should even not need CONFIG_AGP that I had stupidly left to y.
I will remove it and retry.
| Mike Hunt wrote: | | Also do you have x11-drivers/nvidia-drivers-190.53-r1 - which is keyword masked? |
Not yet. I have always made so X works with the vesa drivers before integrating much more uselessly sophisticated drivers...
Doing so seems still nvidia's recommendation anyway.
By the way, I had initially planed to stick to 185.18.36 however, if you recommend 190.53, I will infringe my mask policy... |
|
| Back to top |
|
|
Mike Hunt
Watchman
Joined: 19 Jul 2009
Posts: 5287
|
| Posted: Thu Jan 14, 2010 7:29 pm Post subject: |
|
|
... well, you shouldn't have to unmask, but if it's the only way ...
| Code: | # grep AGP /var/log/Xorg.0.log
(II) NVIDIA(0): Detected AGP rate: 4X |
Post your emerge --info please. |
|
| Back to top |
|
|
aCOSwt
Bodhisattva
Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space
|
| Posted: Fri Jan 15, 2010 11:51 am Post subject: |
|
|
Hmmm... Well...
1/ Could not disable CONFIG_AGP because CONFIG_GART_IOMMU depends on it ! 
2/ My mtrr troubles appear more and more related to some conflict between xorg and vesafb.
I will try the uvesafb instead to see if something changes.
3/ Do you mean you recommend 190.53.r1 over 185.18.36 ?
I understand that 190.53.r1 is quality approved by NVIDIA however, as you mentioned it, it's still ~ in portage and I am not that happy about the idea of mixing arch and ~arch things on a same system. |
|
| Back to top |
|
|
Mike Hunt
Watchman
Joined: 19 Jul 2009
Posts: 5287
|
| Posted: Fri Jan 15, 2010 2:52 pm Post subject: |
|
|
I'm not exactly certain what the problem is, but it's possible that there are kernel/xorg-server/nvidia-drivers version incompatibilities.
You may need a version roll back for one and/or the other of these. It happens
Which version of kernel/xorg-server/nvidia-drivers are currently installed?
BTW, you need CONFIG_AGP |
|
| Back to top |
|
|
aCOSwt
Bodhisattva
Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space
|
| Posted: Fri Jan 15, 2010 2:56 pm Post subject: |
|
|
| Mike Hunt wrote: | | Which version of kernel/xorg-server/nvidia-drivers are currently installed? |
None yet !
I am trying to make xorg work in a vesa only configuration.
And when it works, I will emerge the nvidia stuff. |
|
| Back to top |
|
|
|
Desktop Environments
