Xorg dosn't support i810 driver. With dri USE flag gives out a black screen. Can't do anything after that not even normal ttys are visible. With dri USE flag shows graphical interface but no mouse. And the graphical interface is not interactive or usable. Works with VESA driver at the cost of low compatibilty, ============= lspci output: 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) ================================================================= emerge --info: Portage 2.1_pre7-r5 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.4-r1, 2.6.16-gentoo-r2 i686) ================================================================= System uname: 2.6.16-gentoo-r2 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz Gentoo Base System version 1.12.0_pre17 ccache version 2.4 [enabled] dev-lang/python: 2.4.2-r1 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -O3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.gentoo.gr.jp http://gentoo.gg3.net/ ftp://gg3.net/pub/linux/gentoo/ " LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" LINGUAS="en si" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X aac aalib alsa apache2 apm avi berkdb bitmap-fonts cdparanoia cdr cli cpudetection crypt ctype cups dba dri dts dvd dvdread eds emboss encode expat fastbuild firefox flac foomaticdb force-cgi-redirect fortran ftp gd gdbm gif gnome gpm grammar gstreamer gtk gtk2 i8x0 imlib ipv6 isdnlog jpeg libg++ libwww mad math memlimit mikmod mmx mozilla mp3 mpeg ncurses nls nptl nptlonly nsplugin ogg opengl pam pcre pdf pdflib perl pic png posix pppd python quicktime readline real sdl session simplexml soap sockets spell spl sse sse2 ssl svg tagwriting tcpd theora thesaurus tokenizer truetype truetype-fonts type1-fonts udev unicode vorbis win32codecs wmf xml xsl xv xvid zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux linguas_en linguas_si userland_GNU video_cards_i810 video_cards_i915 video_cards_i910 video_cards_vga video_cards_vesa" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, PORTDIR_OVERLAY
Created attachment 84580 [details] Xorg.0.log without DRI use flag Xorg.0.log with DRI use flag Gives out non-interactive non-usable messy GUI.
Created attachment 84581 [details] Xorg.0.log with DRI use flag Gives out a black screen.
Comment on attachment 84580 [details] Xorg.0.log without DRI use flag Xorg.0.log without DRI use flag Gives out a non-usable GUI with no mouse support.
Similar to these bugs on other distros... https://launchpad.net/distros/ubuntu/+source/xserver-xorg-driver-i810/+bug/29880 http://lists.freedesktop.org/archives/xorg/2005-December/011912.html http://www.webservertalk.com/archive291-2006-2-1409316.html
One of those bugs suggests it might be a GCC problem. Try compiling xorg-server, mesa, and xf86-video-i810 with -O2 instead of -O3. In any case, I've been using i810 with X 7.0 without an issue, so it's either a bug with your specific hardware or a configuration problem.
(In reply to comment #5) > One of those bugs suggests it might be a GCC problem. Try compiling > xorg-server, mesa, and xf86-video-i810 with -O2 instead of -O3. > > In any case, I've been using i810 with X 7.0 without an issue, so it's either a > bug with your specific hardware or a configuration problem. > As you said I tried emerging xorg-xserver, mesa & xf86-video-i810 with -O2 CFLAG. But still it produces the same results. For more info. check my next Xorg.0.log.
Created attachment 84837 [details] Xorg.0.log with xorg-x11 modules compiled with -O2 CFLAG Xorg.0.log produced by xorg-server, mesa & xf86-video-i810 compiled using -O2 CFLAG.
What version of each package (i810, server, and mesa) are you using?
(In reply to comment #8) > What version of each package (i810, server, and mesa) are you using? > x11-base/xorg-server-1.0.2-r3 media-libs/mesa-6.4.2-r2 x11-drivers/xf86-video-i810-1.4.1.3
I can confirm this bug. It appeared right after I upgraded to xorg-7.0 yesterday, before it was working flawlessly.
There's already an upstream bug for this, we'll track it there.
Their is a patch available to fix Intel bridges. Consider adding that patch to related ebuild. Bug : <https://bugs.freedesktop.org/show_bug.cgi?id=6750> Patch : <https://bugs.freedesktop.org/attachment.cgi?id=5478>
That patch is in 1.0.99.902, please try it. You'll need to unmask it along with all the drivers you're using.
Only inp(In reply to comment #13) > That patch is in 1.0.99.902, please try it. You'll need to unmask it along with > all the drivers you're using. > Only improvement is now it gives me the color screen instead of blackscreen. Still no mouse. and it isn't usable... i can start some apps by Keyboard shortcuts but gives out a messy input... pls. check my Xorg.0.log
Created attachment 85806 [details] Xorg.0.log with masked ebuilds I unmasked xorg-server, mesa, and i810, keyboard and mouse drivers...
I have a similar problem with my today update to xorg modular : X doesn't use all my screen, only a part, about 2/3, with a big black border around. Is it a known issue please ?
Christophe, could you add x11-base/xorg-server, x11-drivers/xf86-video-i810, and your input drivers to /etc/portage/package.keywords and try the ~arch versions?
Donnie: same thing :-( I don't understand, because, on time, I tested with vesa driver and X -config xorg.conf (generated by Xorg --configure), and I had all my screen used. But now, it gives me the same issue than with i810 (new version xorg-server).
(In reply to comment #18) > Donnie: same thing :-( > I don't understand, because, on time, I tested with vesa driver and X -config > xorg.conf (generated by Xorg --configure), and I had all my screen used. But > now, it gives me the same issue than with i810 (new version xorg-server). What if you power off your machine, wait 10 seconds, start it back up and try vesa (without ever trying i810 on that boot)? A restart is not good enough.
(In reply to comment #19) > > What if you power off your machine, wait 10 seconds, start it back up and try > vesa (without ever trying i810 on that boot)? A restart is not good enough. > Well, it work with vesa. I just forgot to update vesa driver. But, when I kill X (xdm stop), all my consoles are black (CTRL+ALT+Fn). PS : I didn't know the trick about restart.
No new idea ? Here what I get while booting my gentoo : http://www.novazur.fr/local/gentoo_boot_xorg_modular.jpg and what I get when kdm starts : http://www.novazur.fr/local/gentoo_kdm_i810_xorg_modular.jpg My laptop is not usable like that. media-libs/mesa-6.5-r3 x11-base/xorg-server-1.1.0-r1 x11-drivers/xf86-video-i810-1.6.0 x11-drivers/xf86-video-fbdev-0.3.0 x11-drivers/xf86-input-mouse-1.1.1 x11-drivers/xf86-input-keyboard-1.1.0 x11-drivers/xf86-video-vesa-1.2.1 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03) (prog-if 00 [VGA]) Subsystem: Uniwill Computer Corp Unknown device 9000 Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at d0000000 (32-bit, prefetchable) [size=128M] Memory at dff80000 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] Power Management version 1
That's very strange. One time, I had it working, with the same xorg configuration, by unloading/loading i915, but : - without dri - when I tried to restart X, I only had a black screen, and had to reboot. When I reboot, my first problem came back, only a part of my screen is used, but dri is active, then : - /etc/init.d/xdm stop - modprobe -r i915 - modprobe i915 - chvt 1 (I'm connected by ssh) - /etc/init.d/xdm start and now, all the screen is used, without DRI ( (EE) AIGLX: Screen 0 is not DRI capable ), and if I switch to another console, or if I stop xdm, I have a blank screen. It seems working on vesa driver when I restart X after unloading/loading i915 : # grep 810 /var/log/Xorg.0.log # grep vesa /var/log/Xorg.0.log (II) LoadModule: "vesa" (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so (II) Module vesa: vendor="X.Org Foundation" (II) VESA: driver for VESA chipsets: vesa (--) Chipset vesa found I have AGP and DRM in the kernel : CONFIG_AGP=y CONFIG_AGP_INTEL=y CONFIG_DRM=y CONFIG_DRM_I915=m should I modify something somewhere in my system ? or emerge another package ?
Christophe, please attach your xorg.conf and Xorg.0.log.
Created attachment 90737 [details] my xorg.conf which always worked well
Created attachment 90738 [details] my actual xorg.0.log I'm always trying to find a solution, so this log is with all modular in kernel : CONFIG_AGP=m CONFIG_AGP_INTEL=m CONFIG_DRM=m CONFIG_DRM_I915=m DRI doesn't actually work. But My problem is always here. And the second time I start X that's vesa which is taken. Another thing, I can unload i915 and drm (X of course stopped), but impossible to unload intel_agp and agpgart. May be that's a part of the problem. I'm going to try kernel 2.6.17 (actual 2.6.16-gentoo-r9).
Created attachment 90739 [details] my second Xorg.0.log Xorg.0.log when I start X once again without rebooting, with same config.
Created attachment 90972 [details] Xorg.log (working, clone mode) Similar problem here. I get an almost black screen with some green boxes on it when trying to use dual head. Seems that the display goes to some sort of text mode which changes when there would be output on the console (e.g. when I hit some keys or reboot using Ctrl-Alt-Del). Clone mode is no problem however. The same setup worked fine with the previous stable x.org version. Will attach Xorg.log of dual head mode tonight. If you need any other input, let me know.
Created attachment 91021 [details] Xorg.log (non-working, dual head mode) Here's the version that crashes. Note that a normal reboot is sufficient to get the system back into a normal state.
Created attachment 91022 [details] xorg.conf Here's the xorg.conf I use. For enabling dual head, I just uncommented the second screen line in the ServerLayout section and the MonitorLayout line in the Device section.
(In reply to comment #28) > Created an attachment (id=91021) [edit] > Xorg.log (non-working, dual head mode) > > Here's the version that crashes. Note that a normal reboot is sufficient to get > the system back into a normal state. > I also see the same error (Vesa BIOS not detected) in xorg with a dual head configuration using a I855 video chipset. When I start X in a dualhead configuration, both of the screens go red then turn back to the console with a `inverted' color scheme. After attempting to start a dualhead configuration, the single head configuration does not work unless I reboot.
I got the same Problem with a 855GM Card, using the i810 Driver and a Xinerama setup. Here also a well working xorg.conf (similar to the others posted here), doesn't work for dual screen configuration. 2nd Screen just stays black.
(In reply to comment #31) > I got the same Problem with a 855GM Card, using the i810 Driver and a Xinerama > setup. Here also a well working xorg.conf (similar to the others posted here), > doesn't work for dual screen configuration. 2nd Screen just stays black. > It works with xorg-server-1.1.0-r1. I suppose this bug can be marked as FIXED.
(In reply to comment #32) > It works with xorg-server-1.1.0-r1. > I suppose this bug can be marked as FIXED. Partly confirmed. After upgrading to xorg-server-1.1.0-r1 (and upgrading all x.org drivers and mesa along the way), and after some fiddling with the MonitorLayout, one problem still remains for me. The driver doesn't seem to recognize any video modes except for 640x480 on the external CRT. So while I usually have 1024x768 on both screens, now I'm stuck with 1024x768 on the laptop and 640x480 on the CRT. Any suggestions?
(In reply to comment #33) > (In reply to comment #32) > > It works with xorg-server-1.1.0-r1. > > I suppose this bug can be marked as FIXED. > > Partly confirmed. For me, the same xorg.conf works as before. (pre 7). I'll attach mine.
(In reply to comment #34) I don't think it's a configuration problem. It worked before using the same config, and it seems no vital configuration options have changed. I rather think it's some problem with the Video BIOS, because I get this line in the log: (II) I810(1): Not using mode "1024x768" (no mode of this name)
(In reply to comment #35) > (In reply to comment #34) > I rather think it's some problem with the Video BIOS, because I get this line > in the log: > > (II) I810(1): Not using mode "1024x768" (no mode of this name) > You're probably partially right. The driver is somewhat strapped by the BIOS of these chips. I think it's time to file a new bug at https://bugs.freedesktop.org with this problem. Search around first, of course ;) You should also file a new bug here, and refer to this bug and the freedesktop bug. Kesara's problem seems to be different from yours, and so this bug got quite sidetracked ;) Kesara, if you're still with us, please update us on the status of your problem.
(In reply to comment #36) > (In reply to comment #35) > > (In reply to comment #34) > > I rather think it's some problem with the Video BIOS, because I get this line > > in the log: > > > > (II) I810(1): Not using mode "1024x768" (no mode of this name) > > > > You're probably partially right. The driver is somewhat strapped by the BIOS > of these chips. > > I think it's time to file a new bug at https://bugs.freedesktop.org with this > problem. Search around first, of course ;) > > You should also file a new bug here, and refer to this bug and the freedesktop > bug. Kesara's problem seems to be different from yours, and so this bug got > quite sidetracked ;) > > Kesara, if you're still with us, please update us on the status of your > problem. > Well I went back to XOrg-X11(In reply to comment #36) > (In reply to comment #35) > > (In reply to comment #34) > > I rather think it's some problem with the Video BIOS, because I get this line > > in the log: > > > > (II) I810(1): Not using mode "1024x768" (no mode of this name) > > > > You're probably partially right. The driver is somewhat strapped by the BIOS > of these chips. > > I think it's time to file a new bug at https://bugs.freedesktop.org with this > problem. Search around first, of course ;) > > You should also file a new bug here, and refer to this bug and the freedesktop > bug. Kesara's problem seems to be different from yours, and so this bug got > quite sidetracked ;) > > Kesara, if you're still with us, please update us on the status of your > problem. > Well, I went back to xorg-x11-6.9 after trying all the patches... Now I don't want to get into trouble by upgrading without knowing that those issues are fixed or not for certain.
Alright, please file a new bug at https://bugs.freedesktop.org and post the link to it here. There definitely seems to be some issues still hanging around.
I have i810 chipset and Xorg7 works. How could I help?
Filed a bug at https://bugs.freedesktop.org/show_bug.cgi?id=7576
Status should be set to 'FIXED'
(In reply to comment #41) Yup, my problem is solved. Sorry. Mislead by the error message, I wasn't looking into the right direction. For the record: You might need to enter the monitor's frequency ranges even though it might have worked without in the past ...
Kesara's problem is not. I'm waiting for Kesara to post a bug at freedesktop so that they can try to track that problem down.
Kesara, please reopen when you reply.
