FC4 White screen on install ? - Page 4

easi · #46 1st December 2005, 01:39 PM

I have a Toshiba Portégé R100 and that works for me

easi · #47 1st December 2005, 02:46 PM

I have another question, the vga=791 3 and xorg.conf fix works, but how to end installation ? if i install Fedora on another computer, i can see that there is a second phase on installation where i valid licence, create a user account, set the firewall etc.

There is a possibility to launch the second phase installation in text mode ? or to launch it after the video fix ?

Astral · #48 2nd December 2005, 09:00 AM

can some1 please send me the libvgahw.a file from fedora 3? the link from the ftp://~mharris/ thingy is broken, the file is missing.. just send it to

goldwyntagud@yahoo.com

i think im desperate for this, iv also got a Trident CyberbladeXP... i managed to install fc4 through txt mode, but startup gives me the white screen of life... fbdev doesnt work for me..

jazzaddict · #49 6th January 2006, 09:28 AM

this might sound stupid but, how do i use editing tool in CLI? i'm pretty much new to linux, depends alot on X

easi · #50 6th January 2006, 09:50 AM

Quote:

Originally Posted by jazzaddict

this might sound stupid but, how do i use editing tool in CLI? i'm pretty much new to linux, depends alot on X

In terminal mode you can use 'nano' for editing files.

jazzaddict · #51 9th January 2006, 02:31 AM

Quote:

Originally Posted by easi

In terminal mode you can use 'nano' for editing files.

hi easi!

thanks for the nano thingy, but unfortunately X complains that it cannot start with the new config...yum is working, with yum update still doen'st work, is there a command to yum update X11?

EclipseAgent · #52 9th January 2006, 05:44 AM

You guys shouldn't have to change ANYTHING except the entry in /etc/X11/xorg.conf (This is an X issue, and not a Linux Kernel issue).

Do the following:

Start the machine in text / failsafe mode
log in as root
vi /etc/X11/xorg.conf
Scroll down until you find the following similar section:
Section "Device"
BoardName "CyberBlade/xp4"
BusID "1:0:0"
Driver "trident"
Identifier "Device[0]"
Screen 0
VendorName "Trident"
EndSection
Press a (to enter Insert mode)
change the Driver "trident" to Driver "vesa"
hit "Esc" (to exit Insert Mode")
Hold shift click ZZ, type reboot and you should be able to log into X without an issue.
I have seen this issue on just about all trident drivers.

Hopefully it'll be fixed soon

jazzaddict · #53 9th January 2006, 06:01 AM

Quote:

Originally Posted by EclipseAgent

You guys shouldn't have to change ANYTHING except the entry in /etc/X11/xorg.conf (This is an X issue, and not a Linux Kernel issue).

Do the following:

Start the machine in text / failsafe mode
log in as root
vi /etc/X11/xorg.conf
Scroll down until you find the following similar section:
Section "Device"
BoardName "CyberBlade/xp4"
BusID "1:0:0"
Driver "trident"
Identifier "Device[0]"
Screen 0
VendorName "Trident"
EndSection
Press a (to enter Insert mode)
change the Driver "trident" to Driver "vesa"
hit "Esc" (to exit Insert Mode")
Hold shift click ZZ, type reboot and you should be able to log into X without an issue.
I have seen this issue on just about all trident drivers.

Hopefully it'll be fixed soon

wow! this works! next i'm gonna patch gcc to 4.01 right? i read that gcc complier is the source of the problem

lilliz · #54 13th February 2006, 05:14 PM

Quote:

Originally Posted by delaosa

me too, i have a toshiba tecra 8200 with Trident CyberbladeXp and i can't get x works. Also /dev/fb0 doesn't exist.

Hi there have you found a workaround yet ? I'm on a Toshiba Satellite Pro 4600 with the same Trident CyberbladeXP driver that doesnt work.

/LilliZ

EclipseAgent · #55 13th February 2006, 07:14 PM

Quote:

Originally Posted by lilliz

Hi there have you found a workaround yet ? I'm on a Toshiba Satellite Pro 4600 with the same Trident CyberbladeXP driver that doesnt work.
/LilliZ

Read 2 posts above you. I have posted a solution.

mekon · #56 21st February 2006, 10:39 PM

Quote:

Originally Posted by EclipseAgent

You guys shouldn't have to change ANYTHING except the entry in /etc/X11/xorg.conf (This is an X issue, and not a Linux Kernel issue).

Do the following:

Start the machine in text / failsafe mode
log in as root
vi /etc/X11/xorg.conf
Scroll down until you find the following similar section:
Section "Device"
BoardName "CyberBlade/xp4"
BusID "1:0:0"
Driver "trident"
Identifier "Device[0]"
Screen 0
VendorName "Trident"
EndSection
Press a (to enter Insert mode)
change the Driver "trident" to Driver "vesa"
hit "Esc" (to exit Insert Mode")
Hold shift click ZZ, type reboot and you should be able to log into X without an issue.
I have seen this issue on just about all trident drivers.

Hopefully it'll be fixed soon

Hi. Thank you so much for this. I'm licking your boots at this moment. I have many distro's running on this machine. FC1,2,and3. Debian Sarge, and Debian Sarge/Etch. Slackware 10,0, and Gentoo. Gentoo gave me some X problems that were due to mousedev, and psmouse not being loaded, and running xorgconfog in FC4, and it telling me the mouse wasn't detected, I was thinking again that it was a mouse problem. this is about 15 reinstalls later. More than it took me to get Gentoo, as a relative newbie to get Gentoo installed. Anyway. it's all good practice on the command line. I'm not used to vi. Gentoo uses nano, and I sort of got used to that, but thanks for the vi commands. Nigel.

EclipseAgent · #57 22nd February 2006, 09:53 PM

Quote:

Originally Posted by mekon

Hi. Thank you so much for this. I'm licking your boots at this moment. I have many distro's running on this machine. FC1,2,and3. Debian Sarge, and Debian Sarge/Etch. Slackware 10,0, and Gentoo. Gentoo gave me some X problems that were due to mousedev, and psmouse not being loaded, and running xorgconfog in FC4, and it telling me the mouse wasn't detected, I was thinking again that it was a mouse problem. this is about 15 reinstalls later. More than it took me to get Gentoo, as a relative newbie to get Gentoo installed. Anyway. it's all good practice on the command line. I'm not used to vi. Gentoo uses nano, and I sort of got used to that, but thanks for the vi commands. Nigel.

Glad this helped you out.

Someone above posted that is may be an issue with GCC.. I am going to try to update, then remake the changes to see if it will fix it.

Also, don't lick the boots.. my cat runs on them and i don't wipe her butt. j/k

The problem started with FC4

-Lawless · #58 24th February 2006, 02:07 PM

Quote:

Originally Posted by RahulSundaram

Boot into run level 3 and run the following command

#yum update

wait till it finishes (can take a long time on first run) and reboot.

This actually fixes the WSOD.

It takes several hours to download and run updates but it finnaly works.
Thanks.

lilliz · #59 24th February 2006, 09:50 PM

Quote:

Originally Posted by -Lawless

This actually fixes the WSOD.

It takes several hours to download and run updates but it finnaly works.
Thanks.

Actually it fixes the X thing but leaves the text mode unresolved, well parts at least, If I don't press fn + F1 to lock screen I can't see the text base shut down sequence.

/LilliZ

-Lawless · #60 24th February 2006, 10:05 PM

Actually I'm not sure what you mean. If you enter level 3 like mentioned and update, the next time you reboot it works fine as far the white screen of death is concerned.