Desperately grasping at straws, I did and emerge -e world over night, and things now work differently, but I am still not there.  I am including a snippet of the Xorg.0.log and the output that comes to my screen after I use ctrl-alt-backspace to terminate X -config xorg.conf.new.  I apologize in advance for the size of this post, but like I said, I am desperate.
 
Here is a snippet of the /var/log/Xorg.0.log having to do with the I810 driver.

(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/modules/linux/libint10.a
(II) I810(0): initializing int10
(II) I810(0): Primary V_BIOS segment is: 0xc000
(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): Before: SWF1 is 0x00001801
(II) I810(0): After: SWF1 is 0x00001808
(==) I810(0): Default visual is TrueColor
(II) I810(0): Allocated 128 kB for the ring buffer at 0x0
(II) I810(0): Allocating at least 768 scanlines for pixmap cache
(II) I810(0): Initial framebuffer allocation size: 2496 kByte
(II) I810(0): Allocated 4 kB for HW cursor at 0x7fff000
(II) I810(0): Allocated 16 kB for HW (ARGB) cursor at 0x7ffb000
(II) I810(0): Allocated 4 kB for Overlay registers at 0x7ffa000 (0x05d8c000).
(II) I810(0): Allocated 64 kB for the scratch buffer at 0x7fea000
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) I810(0): [drm] DRM interface version 1.2
(II) I810(0): [drm] created "i915" driver at busid "pci:0000:00:02.0"
(II) I810(0): [drm] added 8192 byte SAREA at 0xc8877000
(II) I810(0): [drm] mapped SAREA 0xc8877000 to 0xb7d0a000
(II) I810(0): [drm] framebuffer handle = 0xf0020000
(II) I810(0): [drm] added 1 reserved context for kernel
(II) I810(0): Allocated 960 kB for the back buffer at 0x7e00000.
(II) I810(0): Allocated 960 kB for the depth buffer at 0x7d00000.
(II) I810(0): Allocated 32 kB for the logical context at 0x7cf8000.
(II) I810(0): Allocated 28032 kB for textures at 0x6198000
(II) I810(0): Updated framebuffer allocation size from 2496 to 2568 kByte
(II) I810(0): Updated pixmap cache from 768 scanlines to 804 scanlines
(II) I810(0): 0x86567f8: Memory at offset 0x00020000, size 2568 kBytes
(II) I810(0): 0x8327e28: Memory at offset 0x07fff000, size 4 kBytes
(II) I810(0): 0x83a2d80: Memory at offset 0x07ffb000, size 16 kBytes
(II) I810(0): 0x862122c: Memory at offset 0x00000000, size 128 kBytes
(II) I810(0): 0x8656838: Memory at offset 0x07fea000, size 64 kBytes
(II) I810(0): 0x8621260: Memory at offset 0x07ffa000, size 4 kBytes
(II) I810(0): 0x8656888: Memory at offset 0x07e00000, size 960 kBytes
(II) I810(0): 0x86568a8: Memory at offset 0x07d00000, size 960 kBytes
(II) I810(0): 0x86568e8: Memory at offset 0x07cf8000, size 32 kBytes
(II) I810(0): 0x86568c8: Memory at offset 0x06198000, size 28032 kBytes
(II) I810(0): Activating tiled memory for the back buffer.
(II) I810(0): Activating tiled memory for the depth buffer.
(II) I810(0): [drm] Registers = 0xff680000
(II) I810(0): [drm] Back Buffer = 0xf7e00000
(II) I810(0): [drm] Depth Buffer = 0xf7d00000
(II) I810(0): [drm] ring buffer = 0xf0000000
(II) I810(0): [drm] textures = 0xf6198000
(EE) I810(0): I830 Dma Initialization Failed
(II) I810(0): [drm] dma control initialized, using IRQ -1007
(EE) I810(0): [drm] Failed to initialized agp heap manager
(II) I810(0): [dri] visual configs initialized
(==) I810(0): Write-combining range (0xf0000000,0x8000000)
(II) I810(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) I810(0): xf86BindGARTMemory: bind key 8 at 0x000df000 (pgoffset 223)
(II) I810(0): xf86BindGARTMemory: bind key 0 at 0x07fff000 (pgoffset 32767)
(II) I810(0): xf86BindGARTMemory: bind key 1 at 0x07ffb000 (pgoffset 32763)
(II) I810(0): xf86BindGARTMemory: bind key 3 at 0x07fea000 (pgoffset 32746)
(II) I810(0): xf86BindGARTMemory: bind key 2 at 0x07ffa000 (pgoffset 32762)
(II) I810(0): xf86BindGARTMemory: bind key 4 at 0x07e00000 (pgoffset 32256)
(II) I810(0): xf86BindGARTMemory: bind key 5 at 0x07d00000 (pgoffset 32000)
(II) I810(0): xf86BindGARTMemory: bind key 6 at 0x07cf8000 (pgoffset 31992)
(II) I810(0): xf86BindGARTMemory: bind key 7 at 0x06198000 (pgoffset 24984)
(WW) I810(0): PGTBL_ER is 0x00000049
(II) I810(0): Before: SWF1 is 0x00001808
(II) I810(0): After: SWF1 is 0x00001808
(WW) I810(0): Extended BIOS function 0x5f05 failed.
(WW) I810(0): Failed to set refresh rate to 72Hz.
(II) I810(0): Display plane A is enabled and connected to Pipe A.
(II) I810(0): Enabling plane A.
(II) I810(0): Display plane A is now enabled and connected to Pipe A.
(II) I810(0): PIPEACONF is 0x80000000
(WW) I810(0): Correcting plane A stride (640 -> 1024)
(II) I810(0): Mode bandwidth is 18 Mpixel/s
(II) I810(0): maxBandwidth is 1152 Mbyte/s, pipe bandwidths are 48 Mbyte/s, 0 Mbyte/s
(WW) I810(0): Extended BIOS function 0x5f61 not supported.
(II) I810(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Horizontal and Vertical Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
29 128x128 slots
7 256x256 slots
(==) I810(0): Backing store disabled
(==) I810(0): Silken mouse enabled
(II) I810(0): Initializing HW Cursor
(II) I810(0): X context handle = 0x00000001
(II) I810(0): [drm] installed DRM signal handler
(II) I810(0): [DRI] installation complete
(II) I810(0): direct rendering: Enabled
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(**) Option "Protocol" "auto"
(**) Mouse0: Device: "/dev/mouse"
(**) Mouse0: Protocol: "auto"
(**) Option "CorePointer"
(**) Mouse0: Core Pointer
(**) Option "Device" "/dev/mouse"
(==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
(==) Mouse0: Buttons: 3
(**) Mouse0: SmartScroll: 1
(**) Option "CoreKeyboard"
(**) Keyboard0: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) Keyboard0: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xc8877000 at 0xb7d0a000
(WW) I810(0): Successfully set original devices
(WW) I810(0): Setting the original video mode instead of restoring
the saved state
(II) I810(0): xf86UnbindGARTMemory: unbind key 8
(II) I810(0): xf86UnbindGARTMemory: unbind key 0
(II) I810(0): xf86UnbindGARTMemory: unbind key 1
(II) I810(0): xf86UnbindGARTMemory: unbind key 3
(II) I810(0): xf86UnbindGARTMemory: unbind key 2
(II) I810(0): xf86UnbindGARTMemory: unbind key 4
(II) I810(0): xf86UnbindGARTMemory: unbind key 5
(II) I810(0): xf86UnbindGARTMemory: unbind key 6
(II) I810(0): xf86UnbindGARTMemory: unbind key 7

Here is what I see on the screen after exiting.  (It used to be so garbled that I was not even aware there was text on it.)

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/clwsapp08:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 6.8.0
Release Date: 8 September 2004
X Protocol Version 11, Revision 0, Release 6.8
Build Operating System: Linux 2.6.10-gentoo-r6 i686 [ELF]
Current Operating System: Linux clwsapp08 2.6.10-gentoo-r6 #2 Wed Feb 23 16:37:57 EST 2005 i686
Build Date: 24 February 2005
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 25 11:07:51 2005
(++) Using config file: "xorg.conf.new"
Using vt 7
(EE) I810(0): I830 Dma Initialization Failed
(EE) I810(0): [drm] Failed to initialized agp heap manager

All suggestions are welcome.

-----Original Message-----
From: Dennis Taylor
Sent: Wednesday, February 23, 2005 5:23 PM
To: [EMAIL PROTECTED]
Subject: RE: [gentoo-user] Xorg and Gnome or KDE on Gentoo

I have made some observations with regard to my garbled monitor after exiting the test run of the xorg X server.
 
My on-board graphics chipset is an 82845G/GL[Brookdale-G].  When I built the kernel, I selected that driver instead of the i810.  I just noticed a "Driver = "i810"" line in my automatically generated configuration file.  Would this be probable cause?  Any guess as to whether I could/should rip the drivers and just use a VESA driver instead?
 
TIA.
Dennis
-----Original Message-----
From: Dennis Taylor
Sent: Monday, February 21, 2005 12:03 PM
To: [EMAIL PROTECTED]
Subject: RE: [gentoo-user] Xorg and Gnome or KDE on Gentoo

Thanks to all who have responded.
 
The  fix_lib_tool_files.sh script did not do it for me, but emerge did.  Now I have successfully emerged Gnome.
 
I still do not have X11 properly configured.  I was able to get Knoppix to run X-11 OK, but was unsuccessful at adapting its XFree86 configuration file to xorg.  I have tried the SLAX Live CD that reportedly uses xorg, but it is unable to start X on my hardware. :-(
 
As time permits, I will study the details of how to configure xorg to work on my monitor.
-----Original Message-----
From: ME [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 19, 2005 1:29 PM
To: [EMAIL PROTECTED]
Subject: Re: [gentoo-user] Xorg and Gnome or KDE on Gentoo

Maybe I am wrong on that, but your emerge problem could be due to the libtool config.

There is a manual fix to run after updating gcc, from a previous message:

>Probably upgraded gcc recently? Try fix_libtool_files.sh 3.3.4 as root. >If that doesn't work try emerging libtool again, perhaps with emerge >-1 libtool.

This is sort of a recurring emerge problem that you see many people having in the mailing list. It happened to me with a similar "No such file" errors in the gcc-lib, the fix_libtool worked, but I am no wiz, somebody can comment on that?

Mrc




Dennis Taylor wrote:
Thanks to all who have responded,

I am going to try the Knoppix later today to see if I can get a better X config file.  I suspect that the probing done to get the configuration for the monitor did not work quite right.  I can probably dig some more and figure out how to get it to use a lower refresh rate or something like that to get it going if Knoppix does not happen to configure it right.  More on that later.

Meanwhile, I was not surprised that X is a requirement for the Window managers.  I thought I remembered it that way, but it has been 10 years since I played with X.  I still cannot get Gnome to emerge properly.  Does anyone have an insight into what causes the following error?  I think I have included enough of the output from the emerge to find the top most error. :-)

-----------------------------------------

libtool --mode=compile i686-pc-linux-gnu-gcc -O2 -march=i686 -pipe -fomit-frame-pointer  -I. -c ./wrjpgcom.c
 i686-pc-linux-gnu-gcc -O2 -march=i686 -pipe -fomit-frame-pointer -I. -c ./rdjpgcom.c  -fPIC -DPIC -o .libs/rdjpgcom.o
 i686-pc-linux-gnu-gcc -O2 -march=i686 -pipe -fomit-frame-pointer -I. -c ./rdjpgcom.c -o rdjpgcom.o >/dev/null 2>&1
 i686-pc-linux-gnu-gcc -O2 -march=i686 -pipe -fomit-frame-pointer -I. -c ./wrjpgcom.c  -fPIC -DPIC -o .libs/wrjpgcom.o
libtool --mode=link i686-pc-linux-gnu-gcc -o libjpeg.la jcapimin.lo jcapistd.lo jctrans.lo jcparam.lo jdatadst.lo jcinit
.lo jcmaster.lo jcmarker.lo jcmainct.lo jcprepct.lo jccoefct.lo jccolor.lo jcsample.lo jchuff.lo jcphuff.lo jcdctmgr.lo
jfdctfst.lo jfdctflt.lo jfdctint.lo jdapimin.lo jdapistd.lo jdtrans.lo jdatasrc.lo jdmaster.lo jdinput.lo jdmarker.lo jd
huff.lo jdphuff.lo jdmainct.lo jdcoefct.lo jdpostct.lo jddctmgr.lo jidctfst.lo jidctflt.lo jidctint.lo jidctred.lo jdsam
ple.lo jdcolor.lo jquant1.lo jquant2.lo jdmerge.lo jcomapi.lo jutils.lo jerror.lo jmemmgr.lo jmemnobs.lo \
        -rpath /usr/lib -version-info 62
 i686-pc-linux-gnu-gcc -O2 -march=i686 -pipe -fomit-frame-pointer -I. -c ./wrjpgcom.c -o wrjpgcom.o >/dev/null 2>&1
libtool --mode=link i686-pc-linux-gnu-gcc  -o rdjpgcom rdjpgcom.lo
i686-pc-linux-gnu-gcc -o rdjpgcom .libs/rdjpgcom.o
libtool --mode=link i686-pc-linux-gnu-gcc  -o wrjpgcom wrjpgcom.lo
i686-pc-linux-gnu-gcc -o wrjpgcom .libs/wrjpgcom.o
g++ -shared -nostdlib /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/../../../crti.o /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/
crtbeginS.o  .libs/jcapimin.o .libs/jcapistd.o .libs/jctrans.o .libs/jcparam.o .libs/jdatadst.o .libs/jcinit.o .libs/jcm
aster.o .libs/jcmarker.o .libs/jcmainct.o .libs/jcprepct.o .libs/jccoefct.o .libs/jccolor.o .libs/jcsample.o .libs/jchuf
f.o .libs/jcphuff.o .libs/jcdctmgr.o .libs/jfdctfst.o .libs/jfdctflt.o .libs/jfdctint.o .libs/jdapimin.o .libs/jdapistd.
o .libs/jdtrans.o .libs/jdatasrc.o .libs/jdmaster.o .libs/jdinput.o .libs/jdmarker.o .libs/jdhuff.o .libs/jdphuff.o .lib
s/jdmainct.o .libs/jdcoefct.o .libs/jdpostct.o .libs/jddctmgr.o .libs/jidctfst.o .libs/jidctflt.o .libs/jidctint.o .libs
/jidctred.o .libs/jdsample.o .libs/jdcolor.o .libs/jquant1.o .libs/jquant2.o .libs/jdmerge.o .libs/jcomapi.o .libs/jutil
s.o .libs/jerror.o .libs/jmemmgr.o .libs/jmemnobs.o  -L/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4 -L/usr/lib/gcc-lib/i686-
pc-linux-gnu/3.3.4/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/crtendS.o /usr/lib/gcc-lib
/i686-pc-linux-gnu/3.3.4/../../../crtn.o  -Wl,-soname -Wl,libjpeg.so.62 -o .libs/libjpeg.so.62.0.0
g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/../../../crti.o: No such file or directory
g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/crtbeginS.o: No such file or directory
g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/crtendS.o: No such file or directory
g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/../../../crtn.o: No such file or directory
make: *** [libjpeg.la] Error 1

!!! ERROR: media-libs/jpeg-6b-r4 failed.
!!! Function src_compile, Line 43, Exitcode 2
!!! make failed
!!! If you need support, post the topmost build error, NOT this status message.

clwsapp08 root #

-----Original Message-----
From: Thomas Mayer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 17, 2005 4:17 PM
To: [EMAIL PROTECTED]
Subject: Re: [gentoo-user] Xorg and Gnome or KDE on Gentoo


On Thursday 17 February 2005 21:41, Dennis Taylor wrote:
  
I have read the DOCs, but I am missing something.  I want to run X-windows
on my Gentoo box (2.6.10-gentoo-r6), but so far have been unsuccessful.  It
is unclear to me whether Gnome or KDE need me to first install Xorg. When
    

... xorg is a dependency of KDE and Gnome, just a graphics server...  and what 
is the error are you encountering when emerging Gnome or KDE?

  
Gnome would not emerge without error, I tried first emerging/configuring
Xorg-X11, but it will not configure correctly for me.  When I run X
-config, it produces a file with an extra horizontal synch line that is all
corrupted.  When I remove it, then X -config /root/xorg.conf.new will start
and show a "dotted" background like I remember from years ago using
XFree86.  The mouse works because moving it around moves the mouse pointer
(X).  I can only get out of it with Ctrl-Alt-Backspace, and that leaves my
monitor unreadable.
    

... this somewhat indicates that X server is somewhat (sic!) working.  Did you 
go through the configure procedure, keyboard mouse, monitor, graphics card, 
hsync, vsync, do you have all the information needed ready, especially about 
hsync, vsync supported by your display?  However, the choice of the windows 
manager should not affect the success of an emerge unless something else is 
wrong.

  
Do I need the X server for Gnome and/or KDE?  If so, any ideas?
    

.. your call, depends on whether you prefer Gnome or KDE as a desktop 
environment...

  
My use flags are as follows:

USE="gtk gnome qt kde dvd alsa cdr nptl nptlonly"
    

... this is very basic and does not matter whether you will be emerging Gnome 
or KDE later on, IMHO, it just creates overhead installing both, although it 
is an individual choice (of course)...

  
I did an emerge --sync last week.
    

.. this doesn't matter much, either and will not take the decision away from 
you about which window manager you want, and ahh, yes, there are others, too.  
Follow the instructions about installing the desktop environment in the 
Gentoo Desktop Guide.

  
Dennis Taylor

    

TM ;-)

  
--
gentoo-user@gentoo.org mailing list
    

--
gentoo-user@gentoo.org mailing list




--
gentoo-user@gentoo.org mailing list


  
-- gentoo-user@gentoo.org mailing list

Reply via email to