On Montag 20 Juli 2009, Mark Knecht wrote: > On Sun, Jul 19, 2009 at 7:00 PM, Mark Knecht<markkne...@gmail.com> wrote: > > On Sun, Jul 19, 2009 at 6:24 PM, Mark Knecht<markkne...@gmail.com> wrote: > > <SNIP> > > > >> myth12 mythtv # cat /var/log/Xorg.0.log | grep EE > >> Current Operating System: Linux myth12 2.6.29-gentoo-r5 #4 PREEMPT Fri > >> Jun 26 09:51:45 PDT 2009 i686 > >> (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > >> (II) Loading extension MIT-SCREEN-SAVER > >> (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM > >> myth12 mythtv # > >> > >> > >> myth12 linux # dmesg | tail -n 5 > >> [ 17.486289] usb 1-0:1.0: uevent > >> [ 19.612246] eth0: setting full-duplex. > >> [ 30.350021] eth0: no IPv6 routers present > >> [ 433.541492] pci 0000:01:05.0: PCI INT A -> Link[LNKA] -> GSI 11 > >> (level, low) -> IRQ 11 > >> [ 435.609192] mtrr: no MTRR for e8000000,4000000 found > > > > myth12 linux # cat /proc/mtrr > > reg00: base=0x000000000 ( 0MB), size= 256MB, count=1: write-back > > reg01: base=0x00c000000 ( 192MB), size= 64MB, count=1: uncachable > > myth12 linux # > > > > Seems that maybe this machine really doesn't have an MTRR at e8000000. > > > > Are MTRR's necessary? This machine ran a much older kernel - circa > > 2.6.19 - until I tried to upgrade the xorg server. Possibly I was > > never using MTRR and having it turned on at all is a mistake? > > > > Thanks, > > Mark > > OK, I have it at least partially working. For some reason it was > unhappy (VERY) with my .xinitrc file left over from the old days. Go > figure?!?! > > I erased the .xinitrc file and just type startx and it work. Three > terminals on the screen. xclock. Everything looks normal. > > I am still getting messages about the MTRR but it doesn't stop X from > coming up. > > I get back on this tomorrow and see if I can get fluxbox running. > > Thanks, > Mark
yes, you 'need' mtrr. Not having working mtrr is like driving a car while constantly stepping on the brakes and gas at the same time. There is lots of stuff about that in Documentation/ - use grep to find it.
