View Full Version : Fedora Core 3 XFree problem
durwin
2004-12-04, 07:58 PM CST
I have a motherboard d845gebv2. After upgrading to FC3, startx blacks out screen and I see nothing. There are no messages in /var/log/messages. I can't find an XFreeConfig to configrure Xwin. I hope there is help out there.
Thank you,
Durwin
Jman
2004-12-06, 12:51 AM CST
XFreeConfig has been renamed to xorg.conf in the move to xorg.
Try booting into rescue mode, running setup and setting up X again.
durwin
2004-12-06, 11:32 AM CST
Thanks for the tip. But does it have to be booted into rescue mode? I boot to console (I do not enter runlevel 5). Also JFYI, I can get a desktop via VNC and it shows the correct driver for adapter when I run the sysconfig-display (what ever the name is). But you are saying to run "setpup"? Is that going to be in my normal path? Or does the setup come from the CD when booted into rescue mode?
Many thanks,
Durwin
durwin
2004-12-06, 06:00 PM CST
Ok, I performed those steps. Ran xconfig fron rescue mode. Still same thing. It will printout a screen full of stuff, then blank out and thats all she wrote. I can't even ALT-<F2> to get another console to log in can kill it. I need to SSH and reboot. This would not be this hard if I caould get SOME error messages logged somewhere.
Each time Fedora Core comes out with a new version, SOMETHING breaks. Last time my sound would not work. Now I have sound, but Desktop is broke. I do appreciate the hard work that goes into this, but they must put in something we can trouble shoot with. And a link to CURRENT documentation.
I still hope for a solution. And thank all for their time.
Durwin
james_in_denver
2004-12-06, 06:37 PM CST
sounds like you will have to boot into console mode and run setup.
You might try the "generic" vesa driver for your xwindows card just to get it running.
Also the output from "X" is in the file "/var/log/Xorg.0.log"
That will give you a better idea of why "X" is crashing....
(bad/wrong driver is my guess)
You might also reply with your Video card model and video memory, and attach your "/etc/X11/xorg.conf" file as well...
durwin
2004-12-06, 08:38 PM CST
Thanks. Did not see the new log file in /var/log
Here it is. God knows it's greek to me!
As for the Video, it is the onboard video on the d845gebv2 motherboard. Called Intel Extreme Graphics Controller. Driver that FC3 sees is Intell 845.
Looking at the bottom I am just noticing the message
If you encounter this problem please add
Option "DisplayInfo" "FALSE"
to the Device section of your XF86Config file.
So, I will try that, but to the xorg.conf, right?
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 0.1.0
ABI class: X.Org Video Driver, version 0.7
(**) I810(0): Depth 24, (--) framebuffer bpp 32
(==) I810(0): RGB weight 888
(==) I810(0): Default visual is TrueColor
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
(II) I810(0): initializing int10
(WW) I810(0): Bad V_BIOS checksum
(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: Brookdale-G 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: Brookdale-G Graphics Controller
(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) I810(0): Integrated Graphics Chipset: Intel(R) 845G
(--) I810(0): Chipset: "845G"
(--) I810(0): Linear framebuffer at 0xF0000000
(--) I810(0): IO registers at addr 0xFFA80000
(II) I810(0): 1 display pipe available.
(II) I810(0): detected 892 kB stolen memory.
(II) I810(0): I830CheckAvailableMemory: 448508 kB available
(II) I810(0): Will attempt to tell the BIOS that there is 12288 kB VideoRAM
(WW) I810(0): Extended BIOS function 0x5f11 not supported.
(II) I810(0): Before: SWF1 is 0x00000101
(II) I810(0): After: SWF1 is 0x00000108
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
(II) I810(0): initializing int10
(WW) I810(0): Bad V_BIOS checksum
(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: 8000 kB
(II) I810(0): VESA VBE OEM: Brookdale-G 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: Brookdale-G Graphics Controller
(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) I810(0): BIOS now sees 8000 kB VideoRAM
(--) I810(0): Pre-allocated VideoRAM: 892 kByte
(**) I810(0): VideoRAM: 16384 kByte
(==) I810(0): video overlay key set to 0x101fe
(**) I810(0): page flipping disabled
(==) I810(0): Using gamma correction (1.0, 1.0, 1.0)
(II) I810(0): BIOS Build: 2759
(==) I810(0): Device Presence: disabled.
(==) I810(0): Display Info: enabled.
(II) I810(0): Broken BIOSes cause the system to hang here.
If you encounter this problem please add
Option "DisplayInfo" "FALSE"
to the Device section of your XF86Config file.
(II) I810(0): Display Info: CRT: attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Display Info: TV: attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Display Info: DFP (digital flat panel): attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Display Info: LFP (local flat panel): attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Display Info: CRT2 (second CRT): attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Display Info: TV2 (second TV): attached: FALSE, present: FALSE, size: (0,0)
"Xorg.0.log" 402L, 18703C
durwin
2004-12-07, 04:22 PM CST
Ok, doing the DisplayInfo option did not help. But Vesa driver works. Just not enough resolution. Is there a newer Intel 845 video driver available?
And Thank you,
Durwin
james_in_denver
2004-12-07, 07:53 PM CST
well, that's an onboard video device isn't?, on the motherboard I mean?....
It looks like it's only configured (via BIOS I am assuming) for 16 Meg memory???
<i>(**) I810(0): VideoRAM: 16384 kByte</i> (<----from your xorg log file)
You might want to increase that if possible to at least 32 Meg, preferably 64 Meg... (using your BIOS setup function, look for something like "shared video memory")
Also, towards the bottom of your /etc/X11/xorg.conf file, you will see a "Depth 24" line....
That is the "Color Depth", with only 16 meg of memory, you can't run at very high resolutions AND keep the same color depth. (you simply don't have enough video memory for allocated for your video card)...
You might try changing the "Depth 24" line to "Depth 16" or even, very drastically "Depth 8"(though the graphics will suffer a LOT from only 8 bit color depth...)
Hope these posts are helping you...
james
durwin
2004-12-07, 08:28 PM CST
I did not have many choices for video in the BIOS. I changed what I thought would increase Video RAM with no luck.
I have a few other video cards laying around. I think I'll use one of those to see if I can get better resolution.
You helped me localize the problem, thanks. I figure it's a driver issue for this MB.
Durwin
james_in_denver
2004-12-08, 12:47 PM CST
I wouldn't nescessarily give up yet, The BIOS sheet I read for that MOBO says it can use up to 64 Meg of shared memory, I don't have the actual motherboard manual in front of me but this
http://www.intel.com/design/motherbd/bv2/bv2_inst.htm#13.5
shows that you can set the onboard video to use up to 64 meg of memory.
That should be more than enough to run at higher resolutions and color depth...
james_in_denver
2004-12-08, 02:45 PM CST
On second thought, if you have a decent video card lying around that is supported under Linux, I would just go with that. I have seen a lot of posts with people have problems with Intel's onboard video card.
durwin
2004-12-09, 09:50 AM CST
Well, the bad news is, I tried one PCI and one AGP video card. Setup could not configure either. Selecting it manually gave same black screen. I can't even get 640x480 256 color mode to work. Only thing that DOES work is the VESA you sugested. I am at a loss. It all worked under FC2 (but sound did not), now I have sound, just no desktop.
My BIOS is current. and I set the values under video to 64M and 8M (can't remember the setting name), one was frame buffer I think, other emplied memory for video.
If you have any other suggestions, I welcome them, if not, thanks very much for your help.
Durwin
james_in_denver
2004-12-09, 09:59 AM CST
yeah, 64 meg and 8 meg look appropriate from the MOBO documentation I read at IBM's site.
You know this is probably a stupid question, but do you have a copy of your old "/etc/X11/xorg.conf" saved anywhere? if so, then just do something like "cd /etc/X11/xorg.conf", "cp xorg.conf xorg.conf.backup", "cp youroldxorg.conf ./xorg.conf". If it was working fine before, then there is absolutely no reason it shouldn't be working fine now...wish I had a similar MOBO handy.....
durwin
2004-12-09, 10:38 AM CST
Well, wasn't FC2 using XFree? I have an XF86Config file. Would it be the same? Can I just rename it to xorg.conf? I looked for a xorg.conf file in the backup I have, but there are none.
durwin
2004-12-23, 10:52 AM CST
I have another thought. I will test my idea tonight. But I have a KVM on my system. Could this be the cause for my video issue? The only driver that works is the vesa at 800x600. If this is the problem, how can I determine which new KVM will work for me?
Durwin
vBulletin® v3.8.1, Copyright ©2000-2009, Jelsoft Enterprises Ltd.