headers
Rance Hall | 6 Jul 01:51

Fedora 9 install problem

I downloaded and verified a fedora 9 net install cd. I burned the cd
and verified the cd from the built in verify function.

I then installed fedora 9 on a test box and liked it and decided to
migrate my real working box to it.

The graphical install fails on the new box, Anaconda starts auto
detects the video card properly, then within 10 seconds the box locks
up tight, only a hard reboot will work.

A text mode install was successful, but the text based first time boot
wizards graphic configuration locks the system up.

I restarted the box in text mode (runlevel 3) and noticed the following:

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 adapter.

Can someone point me in the right direction please, I just wanna get
this installed.

Thanks.

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
(Continue reading)

Permalink | Reply |
headers
bruce | 6 Jul 02:07

RE: Fedora 9 install problem


ummm..

what kind of system/board/drive/monitor/etc...

-----Original Message-----
From: fedora-list-bounces <at> redhat.com
[mailto:fedora-list-bounces <at> redhat.com]On Behalf Of Rance Hall
Sent: Saturday, July 05, 2008 4:54 PM
To: fedora-list <at> redhat.com
Subject: Fedora 9 install problem

I downloaded and verified a fedora 9 net install cd. I burned the cd
and verified the cd from the built in verify function.

I then installed fedora 9 on a test box and liked it and decided to
migrate my real working box to it.

The graphical install fails on the new box, Anaconda starts auto
detects the video card properly, then within 10 seconds the box locks
up tight, only a hard reboot will work.

A text mode install was successful, but the text based first time boot
wizards graphic configuration locks the system up.

I restarted the box in text mode (runlevel 3) and noticed the following:

X based config tools work fine.  but startx fails and locks up the system.
As does system-config-display.
(Continue reading)

Permalink | Reply |
headers
Sam Varshavchik | 6 Jul 02:34

Re: Fedora 9 install problem

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 adapter.
> 
> 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:

http://fedoraforum.org/forum/printthread.php?t=192362

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.

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.

3) Reboot. Make sure that that openchrome xorg driver is installed. Edit 
xorg.conf, and force the openchrome driver into xorg's configuration, see
(Continue reading)

Permalink | Reply |
headers
Rance Hall | 6 Jul 06:06

Re: Fedora 9 install problem

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
>> adapter.
>>
>> 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
stuff.

> http://fedoraforum.org/forum/printthread.php?t=192362
>
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
(Continue reading)

Permalink | Reply |
headers
Jim Cornette | 6 Jul 04:31

Re: Fedora 9 install problem

Rance Hall wrote:
> I downloaded and verified a fedora 9 net install cd. I burned the cd
> and verified the cd from the built in verify function.
> 
> I then installed fedora 9 on a test box and liked it and decided to
> migrate my real working box to it.
> 
> The graphical install fails on the new box, Anaconda starts auto
> detects the video card properly, then within 10 seconds the box locks
> up tight, only a hard reboot will work.
> 
> A text mode install was successful, but the text based first time boot
> wizards graphic configuration locks the system up.
> 
> I restarted the box in text mode (runlevel 3) and noticed the following:
> 
> 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 adapter.
> 
> Can someone point me in the right direction please, I just wanna get
> this installed.
> 
> Thanks.
> 

The best way in my opinion would be to pass xdriver=vesa at the command 
prompt so you could take advantage of a graphical first boot.
I believe hitting the tab will open a commandline where
(Continue reading)

Permalink | Reply |
headers
Rance Hall | 6 Jul 05:58

Re: Fedora 9 install problem

On Sat, Jul 5, 2008 at 9:31 PM, Jim Cornette <fc-cornette <at> wowway.com> wrote:
> Rance Hall wrote:
>> The graphical install fails on the new box, Anaconda starts auto
>> detects the video card properly, then within 10 seconds the box locks
>> up tight, only a hard reboot will work.
>>
>> A text mode install was successful, but the text based first time boot
>> wizards graphic configuration locks the system up.
>>
>> I restarted the box in text mode (runlevel 3) and noticed the following:
>>
>> 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
>> adapter.
>>
>> Can someone point me in the right direction please, I just wanna get
>> this installed.
>>
>> Thanks.
>>
>
> The best way in my opinion would be to pass xdriver=vesa at the command
> prompt so you could take advantage of a graphical first boot.
> I believe hitting the tab will open a commandline where
> linux xdriver=vesa
> could be entered.
>
> Afterward you can try to straighten out the driver problem the VIA graphics
(Continue reading)

Permalink | Reply |
headers
Rance Hall | 6 Jul 16:21

Re: Fedora 9 install problem

On Sat, Jul 5, 2008 at 9:31 PM, Jim Cornette <fc-cornette <at> wowway.com> wrote:
>
> The best way in my opinion would be to pass xdriver=vesa at the command
> prompt so you could take advantage of a graphical first boot.
> I believe hitting the tab will open a commandline where
> linux xdriver=vesa
> could be entered.
>
> Jim
>

Jim:

I got a graphical install to come up with xdriver=vesa boot option, is
there a similar boot hint for the KDE Live CD?  I tried xdriver=vesa
but that diidnt work.

Honestly I didn't expect it to work, thats an anaconda boot option,
anaconda doesn't have to be on a LIVE CD

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Permalink | Reply |
headers
Jim Cornette | 7 Jul 03:34

Re: Fedora 9 install problem

Rance Hall wrote:
> On Sat, Jul 5, 2008 at 9:31 PM, Jim Cornette <fc-cornette <at> wowway.com> wrote:
>> The best way in my opinion would be to pass xdriver=vesa at the command
>> prompt so you could take advantage of a graphical first boot.
>> I believe hitting the tab will open a commandline where
>> linux xdriver=vesa
>> could be entered.
>>
>> Jim
>>
> 
> Jim:
> 
> I got a graphical install to come up with xdriver=vesa boot option, is
> there a similar boot hint for the KDE Live CD?  I tried xdriver=vesa
> but that diidnt work.
> 
> Honestly I didn't expect it to work, thats an anaconda boot option,
> anaconda doesn't have to be on a LIVE CD
> 

I have not tried out any live CD versions but expect that you would need 
to boot into runlevel 3 and edit the Xorg.conf file or copy it from 
another media like a USB flash or hard drive before starting X.

I am glad the xdriver=vesa option worked for you to get a normal 
install. Just for information, you can specify different drivers other 
than vesa if proper detection during install is the problem. (ati, 
intel, mga, nv or whatever it may be for your machine.)
(Continue reading)

Permalink | Reply |

Gmane