Fedora 9 install problem
ranceh at gmail.com
Sun Jul 6 04:06:08 UTC 2008
2008/7/5 Sam Varshavchik <mrsam at courier-mta.com>:
> Rance Hall writes:
>> X based config tools work fine. but startx fails and locks up the system.
>> As does system-config-display.
>> I have an MSI K9VGM-V mobo that uses an integrated VIA chrome9 graphic
>> Can someone point me in the right direction please, I just wanna get
>> this installed.
> Google often points people in the right direction, in situations like that.
> Next time, always try your luck with Google. A brief Google search found the
> following likely course of action:
Sam: I know your work, and I've used courier on email servers in the
past, yes I Googled first, but my search terms were off, I was
searching for mobo specific stuff rather than video card specific
Thanks for the pointer, I read it and gleaned what I could from it.
> Based on that thread, I suggest the following course of action:
> 1) Boot with a VESA console. Add "vga=791" to the kernel boot command line.
> At the grub prompt, press enter, then 'E' to edit the kernel boot command
> line, append "vga=791" to the end, then press enter and 'B' to boot. The
> kernel should boot up with a fairly safe 1024x768x16 VESA framebuffer.
passing any vga mode I want works fine, I in fact had tried that to
see where exactly my problem was.
> 2) You should now be able now to run system-config-display and set up
> VESA-based X. VESA X is very slow, and is only good enough for a basic,
> non-accelerated desktop. Your only goal here to get system-config-display to
> give you a working xorg.conf file.
nope, system-config-display locks up the box. a little bit of
research suggests that there are a number of updated packages since 9
was released, perhaps I wait till after I get those downloaded and
installed before I try system-config-display again.
> 3) Reboot. Make sure that that openchrome xorg driver is installed. Edit
> xorg.conf, and force the openchrome driver into xorg's configuration, see
> the fedoraforum thread for info. Start X, cross your fingers, and hope that
> the openchrome driver knows what to do.
> If it doesn't work, post your /var/log/Xorg.0.log and the output of the
> "lspci -v" command to the xorg mailing list:
Thanks for the hint on what information to include with any followups I need.
> And hopefully someone will be able to point you in the right direction.
> If it works, file a bug in Bugzilla to get your video card autodetected in
> the future, and include the same Xorg.0.log and lspci -v output in your bug
Thanks again, Sam.
More information about the fedora-list