Unable to login after latest FC10 updates (i386 on Dell GX270)

[Al Dunsmuir]

I'm running FC10 on 3 systems - 2x 32-bit (DELL GX260, D810 laptop)
and 1x 64-bit (AMD quad).

After applying all the recent updates, the D810 and AMD box are fine.

Unfortunately, on the GX260 I can no longer log on - the Gnome logon
panel appears to have all buttons in the bottom row and my user ID
button displayed (low intensity) and inactive.

This is my DNS, DHCP and Samba server, and these services continue to
work in the background. Recommendations as to the appropriate bugzilla
component for reporting the problem, and any first-pass problem
resolution advice would be appreciated.  I've checked the mailing list,
but nothing popped up as relevant.

Al

[Janez Košmrlj]

Al Dunsmuir wrote:
>  Waleed, on Friday, December 26, 2008, 2:36:39 PM, you wrote:
>
>    
> > Try reinstall the driver for your ATI. Then change the driver
> > name in xorg.conf file from VESA to ATIXXXX < driver name.
> > After that switch to level 5 via init 5 command.
> >
> > -----------------------------------------------------------------------
> > Yours,
> > Waleed Harbi
> >     
>
>  The whole point is that for both the Intel and ATI device-specific
>  drivers, the latest X-org is badly broken for many folks.  The
>  generic VESA works, so the problem is probably triggered when the
>  device-specific drivers run acceleration or 3D-specific functions.
>
>  Once the bugs are fixed in the device-specific drives, I will certainly
>  be trying them out.. but right now I need the other units to be fully
>  functional.
>
>  Al
>
>
>
>     
I tried now with the latest x11 ati driver update and it works again 
with the radeon driver.

Re[4]: Unable to login after latest FC10 updates (i386 on Dell GX270)

[Al Dunsmuir]

Waleed, on Friday, December 26, 2008, 2:36:39 PM, you wrote:

>  Try reinstall the driver for your ATI. Then change the driver
>  name in xorg.conf file from VESA to ATIXXXX < driver name.
>  After that switch to level 5 via init 5 command.
>
>  -----------------------------------------------------------------------
>  Yours,
>  Waleed Harbi 
The whole point is that for both the Intel and ATI device-specific
drivers, the latest X-org is badly broken for many folks.  The
generic VESA works, so the problem is probably triggered when the
device-specific drivers run acceleration or 3D-specific functions.

Once the bugs are fixed in the device-specific drives, I will certainly
be trying them out.. but right now I need the other units to be fully
functional.

Al

Re[2]: Unable to login after latest FC10 updates (i386 on Dell GX270)

[Waleed Harbi]

Try reinstall the driver for your ATI. Then change the driver name in
xorg.conf file from VESA to ATIXXXX < driver name. After that switch to
level 5 via init 5 command.


-----------------------------------------------------------------------
Yours,
Waleed Harbi
If you want your goals to come true, don't sleep.


On Fri, Dec 26, 2008 at 10:12 PM, Al Dunsmuir <al.dunsmuir(a)sympatico.ca&gt;wrote:

>  Hello Toma,
>
>  Friday, December 26, 2008, 6:11:43 AM, you wrote:
>
>  > Hi, everybody!
>  > So, I,m not alone in this problem.
>  > I'm runin' F10 on an old IBM Intellistation,
>  > IDE HDD(originally it was SCSI)
>  > 600MHz CPU & 500 Mb RAM,
>  > after Ubuntu 8.04,that was working  fine.
>  > After installing F10, installed all security updates,
>  > and one(1) debug update(bug icon).
>  > All went O.K. till I restarted it.
>  > After restart, boot proces went fine, but log in screen hangs up.
>  > No active buttons, no text, just white fields on F10 wallpaper. It is
>  impossible to interact.
>  > I tried to reinstall F10 3 times, but, always the same story.
>  > Can anybody help?
>  > Thanks!
>
>  Toma,
>
>  My Dell GX270 is an Intel GPU.  It appears that in the first week of
>  December something broke (or exposed an existing bug that broke)
>  either the X-windows server or lots of drivers.
>
>  If you type "a" during the boot sequence and then append a "3" to
> the
>  grub command line you can log into your system in text (non-X) mode.
>  "yum update" from the command line will install all ready updates...
>  unfortunately there isn't one yet that fixes this problem.
>
>  All I can advise is patience.  The good news is that enough folks are
>  broken 100% of the time that ajax and crew should be able to track
>  down and fix this problem (perhaps after the holidays).
>
>  I'm lucky that my other two Linux installs are on ATI GPUs, but using
>  the VESA driver (which isn't accelerated and does not seem to be
>  affected).
>
>  Good luck,
>  Al
>  All
>
>
>
>
>  --
>  Best regards,
>   Al                            mailto:[e-mail]
>
>
>  --
>  fedora-list mailing list
>  fedora-list(a)redhat.com
>  To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>  Guidelines:
>  http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>

Re[2]: Unable to login after latest FC10 updates (i386 on Dell GX270)

[Al Dunsmuir]

Hello Toma,

Friday, December 26, 2008, 6:11:43 AM, you wrote:

>  Hi, everybody!
>  So, I,m not alone in this problem.
>  I'm runin' F10 on an old IBM Intellistation,
>  IDE HDD(originally it was SCSI)
>  600MHz CPU & 500 Mb RAM,
>  after Ubuntu 8.04,that was working  fine.
>  After installing F10, installed all security updates,
>  and one(1) debug update(bug icon).
>  All went O.K. till I restarted it.
>  After restart, boot proces went fine, but log in screen hangs up.
>  No active buttons, no text, just white fields on F10 wallpaper. It is impossible to
> interact.
>  I tried to reinstall F10 3 times, but, always the same story.
>  Can anybody help?
>  Thanks! 
Toma,

My Dell GX270 is an Intel GPU.  It appears that in the first week of
December something broke (or exposed an existing bug that broke)
either the X-windows server or lots of drivers.

If you type "a" during the boot sequence and then append a "3" to the
grub command line you can log into your system in text (non-X) mode.
"yum update" from the command line will install all ready updates...
unfortunately there isn't one yet that fixes this problem.

All I can advise is patience.  The good news is that enough folks are
broken 100% of the time that ajax and crew should be able to track
down and fix this problem (perhaps after the holidays).

I'm lucky that my other two Linux installs are on ATI GPUs, but using
the VESA driver (which isn't accelerated and does not seem to be
affected).

Good luck,
Al
All




-- 
Best regards,
 Al                            mailto:[e-mail]

[potat0]

Hi, everybody!
So, I,m not alone in this problem.
I'm runin' F10 on an old IBM Intellistation,
IDE HDD(originally it was SCSI)
600MHz CPU & 500 Mb RAM,
after Ubuntu 8.04,that was working  fine.
After installing F10, installed all security updates,
and one(1) debug update(bug icon).
All went O.K. till I restarted it.
After restart, boot proces went fine, but log in screen hangs up. No active buttons, no
text, just white fields on F10 wallpaper. It is impossible to interact.
I tried to reinstall F10 3 times, but, always the same story.
Can anybody help?
Thanks!


-- 
This is an email sent via The Fedora Community Portal https://fcp.surfsite.org
https://fcp.surfsite.org/modules/newbb/viewtopic.php?post_id=314756&t...
If you think, this is spam, please report this to webmaster(a)fcp.surfsite.org and/or blame
jtomast(a)gmail.com.

[Janez Košmrlj]

>  I tried now with the VESA X driver instead of the default RADEON
> driver and it all works now. So it has to be something with the video driver.

Re[2]: Unable to login after latest FC10 updates (i386 on Dell GX270)

[Al Dunsmuir]

Hello Janez,
Sunday, December 21, 2008, 1:00:27 PM, you wrote:
> > I have the same problem on an Dell Latitude D600 with an ati
> chipset.
> > There is no text or icons. i can click on the screen an things happen 
> > but there is no icons buttons or text just grey and white windows.
>  One more thing i forgot to mention. I did an yum uprate yesterday and 
>  with other things i also updated x server 
My Latitude D810 was not affected by the original bug, but your report
means that I'll be applying no further undates until the GX270 is working
again.

I opened the following bug for the GX270 X-related bug(s).
https://bugzilla.redhat.com/show_bug.cgi?id=476578

There are 2 iterations of Xorg.0.log files attached.  The first is
from the original problem.  That had some d-bus problems that were
solved by the latest PolicyKit update, but the underlying X-related
problems remained.

Hopefully Ajax can analyze/fix this one sometime soon.
Al

[Al Dunsmuir]

Hello Al,

Sunday, December 7, 2008, 11:11:42 AM, I wrote:

>  I'm running FC10 on 3 systems - 2x 32-bit (DELL GX270, D810
> laptop)
>  and 1x 64-bit (AMD quad). 
>  After applying all the recent updates, the D810 and AMD box are fine.
>  Unfortunately, on the GX260 I can no longer log on - the Gnome logon
>  panel appears to have all buttons in the bottom row and my user ID
>  button displayed (low intensity) and inactive. 
>  This is my DNS, DHCP and Samba server, and these services continue
> to
>  work in the background. Recommendations as to the appropriate bugzilla
>  component for reporting the problem, and any first-pass problem
>  resolution advice would be appreciated.  I've checked the mailing list,
>  but nothing popped up as relevant. 
Sunday, December 7, 2008, 12:42:43 PM, Stan wrote:

>  Very first pass, but I would log in to runlevel 3 and check
>  the system logs.  I can't remember the parameter that is 
>  passed to grub.  Perhaps someone else here can help or you 
>  can find it in a search.  Sorry I can't be of more help, but 
>    I haven't had problems necessitating that I learn this. 
At Stan's suggestion, I was able to log on as root with runlevel 3
(Enter 'a' when GRUB shows kernel, append " 3" to specify runlevel).
I then ran "yum clean all" followed by "yum update" to correct the
PackageKit/dbus-related problems.

The Gnome logon GUI panel (Plymouth?) still hangs in the same way.
The mouse moves around the screen fine, but there are no active buttons
on the GUI nor any response to the keyboard.  I'm suspecting that
there is a display-related problem with the display driver that does
not crop up in text mode.

The GX270 has the "Integrated Intel Extreme Graphics 2" display
controller.  It would not enter the Anaconda GUI install (dropped to
text install mode) with the FC10 preview, but installed fine with the
FC10 final release (until applying new updates last weekend).

Could someone please suggest the best Bugzilla component to start with?
I suspect this will require explicit direction by someone experienced
in X/Plymouth with me doing the keyboard monkey bit.

Al




-- 
Best regards,
 Al                            mailto:[e-mail]

[potat0]

Hi,
I've got similar problem. Last week I tried to upgrade my FC8 to FC10 using
PreUpgrade, everything went fine, but after reboot I could not login into Gnome. After
clicking on my username and typing my password I was not logged in but returned to the
login screen, instead. The solution was not to click on the username, but write the
username and then the password and then I was able to log in. But after random time the
Gnome session broke, keyboard stopped working, menus stopped working etc. But applications
were still running.

Then I installed the whole new FC10 from the latest DVD image, this time I installed KDE4.
Everything went find until the update. After doing yum update and rebooting I wasn't
able to login. The KDM login screen was broken, instead of password, there is _assword
etc. After another reboot I was suddenly able to log in, but nothing was working, instead
of windows I saw only white rectangles.

So I decided to reinstall the FC10 again, this time using the DVD iso and network
connection, so I wanted to install the latest version. But this time even the screen that
appears after the installation and reboot (the screen, where you type the root password,
username ...) was not working, again only white page with some rubbish letters.

My laptop is Dell D600.


-- 
This is an email sent via The Fedora Community Portal https://fcp.surfsite.org
https://fcp.surfsite.org/modules/newbb/viewtopic.php?post_id=314420&t...
If you think, this is spam, please report this to webmaster(a)fcp.surfsite.org and/or blame
neils(a)seznam.cz.

[Janez Košmrlj]

Al Dunsmuir wrote:
>  Hello Al,
>
>  Sunday, December 7, 2008, 11:11:42 AM, I wrote:
>
>    
> > I'm running FC10 on 3 systems - 2x 32-bit (DELL GX270, D810 laptop)
> > and 1x 64-bit (AMD quad).
> >     
>
>    
> > After applying all the recent updates, the D810 and AMD box are fine.
> >     
>
>    
> > Unfortunately, on the GX260 I can no longer log on - the Gnome logon
> > panel appears to have all buttons in the bottom row and my user ID
> > button displayed (low intensity) and inactive.
> >     
>
>    
> > This is my DNS, DHCP and Samba server, and these services continue to
> > work in the background. Recommendations as to the appropriate bugzilla
> > component for reporting the problem, and any first-pass problem
> > resolution advice would be appreciated.  I've checked the mailing list,
> > but nothing popped up as relevant.
> >     
>
>  Sunday, December 7, 2008, 12:42:43 PM, Stan wrote:
>
>    
> > Very first pass, but I would log in to runlevel 3 and check
> > the system logs.  I can't remember the parameter that is 
> > passed to grub.  Perhaps someone else here can help or you 
> > can find it in a search.  Sorry I can't be of more help, but 
> >   I haven't had problems necessitating that I learn this.
> >     
>
>  At Stan's suggestion, I was able to log on as root with runlevel 3
>  (Enter 'a' when GRUB shows kernel, append " 3" to specify runlevel).
>  I then ran "yum clean all" followed by "yum update" to correct the
>  PackageKit/dbus-related problems.
>
>  The Gnome logon GUI panel (Plymouth?) still hangs in the same way.
>  The mouse moves around the screen fine, but there are no active buttons
>  on the GUI nor any response to the keyboard.  I'm suspecting that
>  there is a display-related problem with the display driver that does
>  not crop up in text mode.
>
>  The GX270 has the "Integrated Intel Extreme Graphics 2" display
>  controller.  It would not enter the Anaconda GUI install (dropped to
>  text install mode) with the FC10 preview, but installed fine with the
>  FC10 final release (until applying new updates last weekend).
>
>  Could someone please suggest the best Bugzilla component to start with?
>  I suspect this will require explicit direction by someone experienced
>  in X/Plymouth with me doing the keyboard monkey bit.
>
>  Al
>
>
>
>
>     
I have the same problem on an Dell Latitude D600 with an ati chipset.
There is no text or icons. i can click on the screen an things happen 
but there is no icons buttons or text just grey and white windows.

[stan]

Al Dunsmuir wrote:
>  
>  Unfortunately, on the GX260 I can no longer log on - the Gnome logon
>  panel appears to have all buttons in the bottom row and my user ID
>  button displayed (low intensity) and inactive.
>  
>  This is my DNS, DHCP and Samba server, and these services continue to
>  work in the background. Recommendations as to the appropriate bugzilla
>  component for reporting the problem, and any first-pass problem
>  resolution advice would be appreciated.  I've checked the mailing list,
>  but nothing popped up as relevant. 
Very first pass, but I would log in to runlevel 3 and check 
the system logs.  I can't remember the parameter that is 
passed to grub.  Perhaps someone else here can help or you 
can find it in a search.  Sorry I can't be of more help, but 
  I haven't had problems necessitating that I learn this.

[Janez Košmrlj]

>  I have the same problem on an Dell Latitude D600 with an ati
> chipset.
>  There is no text or icons. i can click on the screen an things happen 
>  but there is no icons buttons or text just grey and white windows. 
One more thing i
forgot to mention. I did an yum uprate yesterday and 
with other things i also updated x server

SUCCESS! F10 X is significantly improved on multiple machines

[Al Dunsmuir]

Greetings!

Back on Dec 7, I reported that updates to the F10 X server and driver
prevented me from being able to use graphical mode on my Dell GX270.
Other machines I had were set up by the F10 install with vesa only.

I reported the problem as https://bugzilla.redhat.com/show_bug.cgi?id=476578
and many others reported similar (if not identical problems).

There have been some significant changes recently to the F10 X support
recently,  and I can finally report the latest are QUITE functional on
all  my  machines!  All tests are made using my Belkin OmniView PRO2
8-Port KVM.

My Compaq P1210 21" CRT had begun to show signs of imminent failure,
and I picked up a decent sized Samsung LCD to replace it.  As part of
this, I gave this bug one last shot.  I updated the GX270 to the latest
F10 updates, removed the xorg.conf file and rebooted.  Lo and behold, it
worked. I hooked up the Samsung, and it also worked with the intel driver.
My normal DNS/Samba server lives!

Now I decided to get a wee bit brave. 

My AMD X64 box (Radeon HD 3200 video) had been set by the F10 install
to vesa.  I updated to the latest F10, deleted the xorg.conf file, and
rebooted.  It worked with both the CRT and the LCD.

Both  System->Administration->Display  (system-config-display) and the
Gnome System->Preferences->Hardware->Screen Resolution properly show
the 1920x1200 format (using the LCD at 1920x1200).

My Dell D810 laptop (Radeon Mobility X600 video) had also been set by
the F10 install to vesa.  Once again, after updating, removing the old
xorg.conf and rebooting it worked with the radeon driver on both CRT and
LCD.

While Gnome System->Preferences->Hardware->Screen Resolution properly
shows  the 1920x1200 format, and mirrors the Dell 1920x1200 LCD on the
Samsung LCD at 1920x1200, system-config-display  reports the wrong
resolution (1400x1050) and does not list 1920x1200 as an option.

Since the GX270 motherboard Intel video did not support the Samsung's
preferred 1920x1200 format, I picked up a cheap used ATI Radeon 7500
video card.  I slipped that in today, and once again had success (on
the Samsung).

While Gnome System->Preferences->Hardware->Screen Resolution properly
shows the 1920x1200 format, system-config-display  reports the wrong
resolution (1600x1200) and does not list 1920x1200 as an option.

Given that I'm getting 1920x1200 displayed on all machines, I'm good
to go, and absolutely overjoyed at the progress the Xorg teams have
made in Fedora 10!

Anyone on the CC list for this bug should check out their own hardware
again, and see if they also observe progress/success.

Al