Bug 487619
|
Description
Rodd Clarkson
2009-02-27 02:52:57 UTC
Created attachment 333429 [details]
Xorg.0.log file when using HDMI (Digital) output
Created attachment 333430 [details]
output from lspci
Created attachment 333431 [details]
output from lspci -vv
I'm going to guess that the Xorg.conf isn't complete. Try it without one. I have an Intex GMA X4500HD and it works fine without a Xorg.conf. I'm guessing part of the error is this: (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) I'm no X expert, but since the board doesn't have AGP, when X looks for it, it dies. Not the best behavior, so it may be a bug in X, not the intel driver. Okay, I've tried running without and xorg.conf file and it still doesn't work. I'll post the Xorg.0.log file is it's wanted, but it's essentially the same, except it spews out some stuff about no config and creates one on the fly. Same error still Okay, I've made some headway. It turns out my motherboards bios (it's a Gigabyte GA-EG41MS2H) has some settings in it's advanced chipset features about PAVP. PAVP comes set in Lite Mode with 32MB of memory. If I change this to Paranoid PAVP (and I've set the memory set aside to 256MB) then all of a sudden this problem changes and I think I'm not dealing with something new. X now starts in what seems to be the correct resolution, but it then freezes with no input from the keyboard, but the mouse still moves the cursor. One of the Xorg.0.log files I read early after this change said something about an infinite loop, but every log file since seems to stop part way through the logging process. I'll attach a log for you to log at. Created attachment 333599 [details]
Xorg.0.log file after changing bios to PAVP Paranoid mode
maybe some hints to compare... my board is with an Intel GMA X4500HD. http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2877 me thinks a successor of yours. I have no xorg.conf, nor special bios setting and have no problems with F10 or F11 so far. ll /dev/agpgart crw------- 1 root root 10, 175 2009-02-28 21:15 /dev/agpgart see comment #4 dmesg|grep -i agp Linux agpgart interface v0.103 agpgart-intel 0000:00:00.0: Intel G45/G43 Chipset agpgart-intel 0000:00:00.0: detected 131068K stolen memory agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000 cat /var/log/Xorg.0.log |grep -i agp (II) intel(0): [drm] Initialized kernel agp heap manager, 33554432 PAVP (what ever it is for) has no influence of a working X. Created attachment 333618 [details]
my X log with an homebrewed 2.6.29-rc6 kernel
Created attachment 333619 [details]
my X log with an homebrewed 2.6.29-rc6 kernel
Rodd, Could you attach dmesg as well ? Could you check you are using the latest BIOS ? Is there anything ressembling GART size, or memory size for integrated video, in BIOS ? Thank you --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Created attachment 333629 [details]
dmesg output
I've tried enabling 'xaa' by adding it to the small xorg.conf file I'm using.
Section "Device"
Identifier "Videocard0"
Driver "intel"
Option "AccelMethod" "XAA"
EndSection
and xorg seems to go future. I've run it once as root and I actually got to ask the system to poweroff (using the GUI) but something hung during shutdown.
and I've run it one as a user and the desktop partially loaded before it locked.
I'll attach both the Xorg.0.log files for these two attempts.
Created attachment 333630 [details]
Xorg.0.log file after enabling 'xaa' in xorg.conf and running startx as root
Created attachment 333631 [details]
Xorg.0.log file after enabling 'xaa' in xorg.conf and running startx as a statndard user
Created attachment 333632 [details]
my dmesg with an 2.6.27.15-170.2.24.fc10.i686 kernel
maybe it's helpfull
I've just changed to the BIOS to use PAVP in lite mode, instead of in Paranoid mode and I've set up PAVP Lite to use 256MB memory, instead of the 32 its comes configured to use by default. xorg works like this. I've also changed the monitor from the DVI-D (or what I've been calling the digital) port to the D-Sub (or what I've been calling the analogue port) and now xorg seems to work without issue (well, so far at least). I can now log in, log out and do stuff in the middle. I'm currently letting it run mythtv for a while to see how things go. 1. So PAVP mode settings don't seem important. 2. Assigning more than 32MB of memory does (and maybe this is something that xorg should be aware of. It occurs to me that 32MB probably isn't anywhere near enough to run 1680x1050x32Bit) 3. Using the D-Sub works, but DVI-D seems to have issues. The mother board documentation seems to suggest that they are slightly different interfaces and the DVI-D is linked to the HDMI output (but I don't have a HDMI cabable screen to test this with). What else would you like to know? Also, two questions regarding the driver package. There's a xorg-x11-drv-i810-2.5.0-5.fc10 build in koji. It this worth trying, or won't it make any difference? Also, intel has released 2.6.0 and I noticed that this has been built for f11. Can this be back-ported to f10 (even if just in koji) for testing? Please add dmesg and Xorg.0.log of a working attempt for comparison purposes. You can try the build in Koji as well. --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Right, I might have got a little carried away. While it's true that I did manage to get x working and that I can confirm it worked for at least 10 minutes, it locked up at some point after that and then my attempt to reboot saw x locking up before the desktop had even loaded, so while things are better, they are by no means useable and I'm not sure that the dmesg I post now would be any different to the dmesg I've already posted. I'll see if I can get into an x session and out tomorrow and then post that xorg.0.log file. Okay, I've installed rawhide to try and see what difference there are. Install went fine. the x in the installer ran fine and had no issues. First start starts and and you can step through that, but the x restart after first start sees x no longer working (strange). After running firstboot and then powering off and restarting firstboot started again. I managed to get inittab set to runlevel 3 (which is kind of important when trying to figure out what's wrong with x and having to reboot all the time) I then ran yum update and am now current. There's initially no X configuration and X doesn't work. Strangle, it seems it doesn't try to load either i810 or intel as drivers. I then added a very basic xorg.conf file to set the driver as intel. Now X seems to work at some level, but switching to compiz sees a white screen until it times out and then works again. I'll attach relevant log files and dmesg for this box. Created attachment 334238 [details]
Xorg.0.log file with no xorg.conf file (using rawhide)
Created attachment 334239 [details]
dmesg output (using rawhide)
Created attachment 334240 [details]
Xorg.0.log file with very limited xorg.conf file to require 'intel' driver (using rawhide)
All of this testing using rawhide is using the DVI-D connection. If you want, I'll try D-SUB too. Okay, I've tried D-SUB and while x starts a little differently it still doesn't start compiz correctly. When you try to run Desktop Effects, the screen goes white (but moving the mouse around sees the pointer change presumably as it moves over different elements on the screen). If you wait, it automatically times out desktop effects. I'm currently using: xorg-x11-drv-intel-2.6.0-14.fc11.i586 xorg-x11-server-utils-7.4-7.fc11.i586 xorg-x11-server-common-1.6.0-9.fc11.i586 xorg-x11-server-Xorg-1.6.0-9.fc11.i586 compiz-0.7.8-14.fc11.i586 kernel-2.6.29-0.207.rc7.fc11.i586 Oaky, I've just tested without an xorg.conf file (in rawhide) and X now recognized that the intel driver exists (along with the i810 driver) and it appears it is using it. This is a vaste improvement on f10 but there are still a few annoying things. 1. compiz doesn't appear to work out of the box. (as mentioned above). Maybe it is possible to throw some setting in xorg.conf, but what I don't know (and haven't tried anything) 2. x doesn't seem to kill too well. if I start in run level 5 and then switch to a terminal, log in as root and run `init 3` it appears to work, but switching to vt1 (or vt7) sees the display go blank and while the keyboard still works, you have to reboot to get the monitor showing something again. 3. I'm not sure if I'm talking to myself, or if someone is actually interested in any of this. I haven't seen a single input from any staff from redhat (according to email address/logins above) and I would had thought a few prompts of what to try wouldn't be out of the question. Created attachment 334428 [details]
Xorg.0.log file with no xorg.conf file (using rawhide) 20090307
maybe to 2. see my grub.conf currently don't how the orginal grub.conf looks like, but see parameter's: - vga=0x318 - none rhgb quiet X is on VT1 (CRTL+ALT+F1) not VT7 means switching X <=> VTn works with this grub.conf to 1. compiz works with my homebrewed 2.6.29.rc7 kernel cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VG_OS/root # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz # hiddenmenu # kernel ... rhgb quiet console=tty0 console=tty1 console=ttyS0,115200n8 selinux=0 audit=0 vga=0x318 # acpi.debug_layer=0xffffffff acpi.debug_level=0xfff # title Fedora (2.6.29-rc7_0-00003-g559595a) root (hd0,0) kernel /vmlinuz-2.6.29-rc7_0-00003-g559595a ro root=/dev/VG_OS/root audit=0 selinux=0 vga=0x318 initrd /initrd-2.6.29-rc7_0-00003-g559595a.img title Fedora (2.6.27.19-170.2.35.fc10.i686) root (hd0,0) kernel /vmlinuz-2.6.27.19-170.2.35.fc10.i686 ro root=/dev/VG_OS/root audit=0 selinux=0 vga=0x318 initrd /initrd-2.6.27.19-170.2.35.fc10.i686.img I've added vga=0x318, and while I now see fancy startup, it's not noticably changed anything in X. I still can't use compiz for example. Okay, I'm all up-to-date with rawhide and I still don't have compiz working, good (acceptable) 3d performance, a graphical boot or any of the other things I would have thought should just work with this graphics card. I'm using the 2.7.0 intel driver. Should I just give up and expect that this card won't work? It would be lovely if I had heard from one of the redhat developers about this bug, even if just to know that they are aware of it, that work is being done (somewhere) and that I'm not wasting my time supplying information. Perhaps bug #493307 is related to your problem. What a shame one of the xorg developers couldn't have just popped up and said that there's known issues with the g41 chipset and maybe pointed me to somewhere where I could have helped with testing. *** This bug has been marked as a duplicate of bug 493307 *** (In reply to comment #34) > What a shame one of the xorg developers couldn't have just popped up and said > that there's known issues with the g41 chipset and maybe pointed me to > somewhere where I could have helped with testing. The problem is that there are just so many xorg developers and that many bugs. I am sorry, but we are dancing as fast as we can. |