|
intel i820 agpgart xorg.conf onboard pci video card problem x crashes
K major updates so if you read this before ... go ahead and check out the new info, got home and recovered the system so I have more details.
Problem: OK intel i810 video chipset is being detected even though it is disabled, its detected by agpgart and says something to the effect "agpgart: Detected an Intel(R) i810, but could not find the secondary device." Again... in BIOS I have it disabled!!! It works fine when booted into run level 3, and using my custom xorg.conf for the PCI radeon 7000 card. I will log in root at run lvl 3, then type, init 5 and it works great!. (and im getting the agpgart error still so maybe this is not the real issue?) Initialy when I installed fedora core everything worked fine. The radeon was the only detected card and install/first boot went perfectly! I was impressed... Second boot, failure. The disabled intel card was scanned, agpgart complained about no secondary device, and X crashed the system. Technical info... Intel graphics adapter is on PCI bus 1:1:1 (this is an onboard card... dunno how the bus archicture is on the mobo... looks to use a PCI bus..) Here I post an lspci Code:
00:00.0 Host bridge: Intel Corporation 82810E DC-133 GMCH [Graphics Memory Controller Hub] (rev 03)As you can see I disabled it in the BIOS and lspci does not detect the Intel i810 at PCI:01:00.0 even though agpgart seems too... I guess my question and the answer/s I would like are... Is there some kinda of script FC5 runs everytime it goes init 5 (graphical) to check if video cards have changed, can I disable it? or disable the part that checks graphics adapters? Is this a problem with xorg or agpgart or neither? I checked all my xorg logs under /var/logs and they say nothing about intel chips Im not new to linux... I am new to fedora core though, and I do not know much about how the init scripts work for it, and I was wondering if someone might have some inside info so I do not have to search every line of code to find the line to comment out =P... maybe theres a trick with SeLinux? It doesn't look like something I can force in my xorg.conf file, as I already tried this and it achived nothing, I used knoppix live CD to fix the init lvls, boot into init 3, then go init 5 from the root login prompt... Most people say for duel head/onboard video card systems... to use xorg.conf or disable in BIOS, neither worked here... so I am wondering if its even a configuration issue? It seems to REALY be an issue reguarding init-3 to init-5 scripts during boot up, maybe because im using the graphical login? (framebuffer) device?! I may be calling it a framebuffer when its realy X thats showing the system initialization... is it a framebuffer or a pre-X X shell? I know under slack and suse, anything before the X login screen is a tried and true frame buffer device, maybe I just need to blacklist the framebuffer module and fix my grub options?! So the only diffrence here is booting with framebuffer support going to init 5 crash. Booting with init 3, no graphical support prior to starting X, we are fine. This is realy stumpin me! Any ideas would be great... I love Fedora core, and this box is great once it boots into X! - this is just for personal use/demonstration purposes and I wan't to be able to give this box to someone else and let them use it without the hassle! |
This is what init 5 spewed when it wen't init 5 from 3...
Code:
X Window System Version 7.0.0Hmmm even more info now on this:... When the system is initizalizing and gets to the portmap service it "blanks" When the system starts the login script for run level 3 and brings up the login prompt the screen "blanks" and reapears again as soon as I press the "return key entering the password" i.e. the monitor looses signal, goes completely black, and comes back" It looks like everytime I get this crash, I get corrupt Xorg.0.log files, as I had to do a thourough fsck and i noticed some of the files it was mentioning in fixing inodes, (most were other system lock files and such) ... but many files associated with X, X11... etc... so appearently when it crashes its writing either random data to the log files, or I keep having to reboot with the files not properly saved out to the disk/filesystem" The file /tmp/tmpl3CTbfxorg.config is gone!!! so I have no idea why it tried to use that instead of /etc/X11/xorg.conf! I also tried it without any frame-buffer device at all... and still no luck. It seems that the frame buffer is not the cause of the problem. If the system goes directly into init 5, it crashes hard. |
Well, here's what fixed it:
Disabling dri, and glx. I commented out the "dri" and "glx" lines in modules section, and the DRI section in xorg.conf. Appearantly the radeon 7000 doesn't support those libraries reliably. No biggy, this is not a hot-rod-machine, now I can run X though! =P and still pretty smooth with only 2D. For those interested and might have the same problem. Code:
Section "Module"I probly could leave in glx module... but im tired... lazy... and don't want to go through more fsck's! |
Quote:
at the Fedora booth at OSCON in Portland told me. I turned off DRI. My system: Dell Precision 650. Dual Xeon processors. ATI Radeon 7000. FC5. 2.6.17-1.2157_FC5smp kernel. System booted OK into run level 3. Then I logged in, did a startx, system would hang either when bringing up the menu bar, or when I tried to do something in X. This was a solid system hang, control-alt-delete and sysrq did not do anything. I had to power cycle. Problem only occurred when booting with an SMP kernel. Problem did NOT occur with non-SMP kernel. I commented the line: Code:
# Load "dri"don't have the system crashing. |
Hey, I was able to get DRI running by updating to the latest x-org something like 7.014 and the latest DRI package, by doing a #yum update off of livna.org and regular fedora repositories, you probly could just do a
yum list xorg* yum list *dri* yum list *radeon* and install the packages you find doing a yum update packagename saves compiling =P xorg and dri source off their pages hehehe... With the latest dri driver and xorg driver, i renabled dri and glx, and rebooted, it worked great =)... I'll go home and find the exact packages for ya later! Don't have my machine up atm. Happy quake deathmatching =) Well heres the packages that worked for me via rpm... xorg-x11-drv-ati 6.5.8.0-1 xorg-x11-apps 7.0-1 xorg-x11-xdm 1:1.0.1-2 xorg-x11-server-Xorg 1.0.1-9.fc5.5 |
| All times are GMT -5. The time now is 03:53 PM. |