Hello all, I was fiddling with the fglrx driver, trying to get suspend to work, and I used the ati/amd installer instead of rpmfusion. Big mistake. Since then my system has been broken. I have reverted to radeon, and fglrx from rpmfusion, but always the same symptoms:
boot starts OK, with the sun, on plymouth until gdm should take over and offer log in possibilites. That step is black on black. I know it is working, because I can log in, but even after log in the display stays black-on-black. [I can check that I logged in via ssh] I have replaced gdm/xorg/compiz/other rpms but no change.
Can anyone suggest how to fix this please? Sorry .... Bill
On Fri, Apr 24, 2009 at 2:34 PM, Murray, WJ (Bill) bill.murray@stfc.ac.ukwrote:
Hello all, I was fiddling with the fglrx driver, trying to get suspend to work, and I used the ati/amd installer instead of rpmfusion. Big mistake. Since then my system has been broken. I have reverted to radeon, and fglrx from rpmfusion, but always the same symptoms:
boot starts OK, with the sun, on plymouth until gdm should take over and offer log in possibilites. That step is black on black. I know it is working, because I can log in, but even after log in the display stays black-on-black. [I can check that I logged in via ssh] I have replaced gdm/xorg/compiz/other rpms but no change.
Can anyone suggest how to fix this please? Sorry .... Bill -- Scanned by iCritical.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
If you have xorg.conf you may want to rename it, at least temporarily. That'll tell you if fglrx changed it.
Murray, WJ (Bill) wrote:
Hello all, I was fiddling with the fglrx driver, trying to get suspend to work, and I used the ati/amd installer instead of rpmfusion. Big mistake. Since then my system has been broken. I have reverted to radeon, and fglrx from rpmfusion, but always the same symptoms:
boot starts OK, with the sun, on plymouth until gdm should take over and offer log in possibilites. That step is black on black. I know it is working, because I can log in, but even after log in the display stays black-on-black. [I can check that I logged in via ssh] I have replaced gdm/xorg/compiz/other rpms but no change.
Can anyone suggest how to fix this please? Sorry .... Bill
Hmmm, whenever I get strange things such as toolbars showing up in the middle of the screen or wrong screen resolution, etc. I usually end up mucking around in the .gconf* trees. I've actually made fixes there that stuck. Trying to fix these with the GUI seems to fix some things temporarily but the evil returns on next login.
Since you can't see what you're doing in runlevel 5 try typing "ctrl alt f2" (actually, depending on version of fedora, f1 through f5). This will give you a runlevel 3 (non-graphical) login prompt.
If you're feeling curious, brave, insane, etc. start digging through your home directory's .gconf* directories looking for things related to color, *or* you could do what I've seen recommended on this list before, and delete the .gconf* directories, which should be rebuilt for you automatically on next login. Your existing display management settings will be hosed but you probably won't be looking at black on black.
Hope that helps, :m)
Thanks for the suggestions. I should have said I checked the xorg.conf many times..I am using one that worked fine a few days ago. I also deleted the whople thing - no help.
Thansk for the alt-ctrl-f2 tip, very useful. As far as the gconf is concerned - good idea, but the black-on-black starts at the facebrowser point, which is before any gnome/kde choice has been made - and my account has not been selected. I tried i, bit it didn't help...
Any more thoughts? Thank you so much...this is really stupid. Bill
-----Original Message----- From: Murray, WJ (Bill) Sent: Fri 24/04/2009 20:34 To: fedora-list@redhat.com Subject: gdm black on black
Hello all, I was fiddling with the fglrx driver, trying to get suspend to work, and I used the ati/amd installer instead of rpmfusion. Big mistake. Since then my system has been broken. I have reverted to radeon, and fglrx from rpmfusion, but always the same symptoms:
boot starts OK, with the sun, on plymouth until gdm should take over and offer log in possibilites. That step is black on black. I know it is working, because I can log in, but even after log in the display stays black-on-black. [I can check that I logged in via ssh] I have replaced gdm/xorg/compiz/other rpms but no change.
Can anyone suggest how to fix this please? Sorry .... Bill
-----Original Message----- From: Murray, WJ (Bill) Sent: Fri 24/04/2009 21:18 To: Murray, WJ (Bill); fedora-list@redhat.com Subject: RE: gdm black on black
Thanks for the suggestions. I should have said I checked the xorg.conf many times..I am using one that worked fine a few days ago. I also deleted the whople thing - no help.
Thansk for the alt-ctrl-f2 tip, very useful. As far as the gconf is concerned - good idea, but the black-on-black starts at the facebrowser point, which is before any gnome/kde choice has been made - and my account has not been selected. I tried i, bit it didn't help...
Any more thoughts? Thank you so much...this is really stupid. Bill
-----Original Message----- From: Murray, WJ (Bill) Sent: Fri 24/04/2009 20:34 To: fedora-list@redhat.com Subject: gdm black on black
Hello all, I was fiddling with the fglrx driver, trying to get suspend to work, and I used the ati/amd installer instead of rpmfusion. Big mistake. Since then my system has been broken. I have reverted to radeon, and fglrx from rpmfusion, but always the same symptoms:
boot starts OK, with the sun, on plymouth until gdm should take over and offer log in possibilites. That step is black on black. I know it is working, because I can log in, but even after log in the display stays black-on-black. [I can check that I logged in via ssh] I have replaced gdm/xorg/compiz/other rpms but no change.
Can anyone suggest how to fix this please? Sorry .... Bill
Oops..the facebrowser thingy is not gdb. Which process is it anyway? I probabaly need to fix that...
Ach.. I had not run the ati uninstaller. I tried to do it by hand, When I ran that, all was well. Bill