Wow, did a rawhide update today catching up two days worth and on reboot got a double blurred screen at what looked like 640x320 resolution. On an alternate terminal looked at xorg.conf and saw that in the device section that radeon had been replaced by fbdev. Fixed and restarted X and all was well.
What changed this? Will file a bz, but against what? There was no mention of an xorg.conf change during the update and a review of the yum.log doesn't show anything except several mesa component updates and compiz update. Would one of those change xorg.conf?
Clyde E. Kunkel (clydekunkel7734@cox.net) said:
Wow, did a rawhide update today catching up two days worth and on reboot got a double blurred screen at what looked like 640x320 resolution. On an alternate terminal looked at xorg.conf and saw that in the device section that radeon had been replaced by fbdev. Fixed and restarted X and all was well.
What changed this? Will file a bz, but against what? There was no mention of an xorg.conf change during the update and a review of the yum.log doesn't show anything except several mesa component updates and compiz update. Would one of those change xorg.conf?
Start with kudzu, we can go from there. What arch, hardware, etc?
Bill
Bill Nottingham (notting@redhat.com) said:
Clyde E. Kunkel (clydekunkel7734@cox.net) said:
Wow, did a rawhide update today catching up two days worth and on reboot got a double blurred screen at what looked like 640x320 resolution. On an alternate terminal looked at xorg.conf and saw that in the device section that radeon had been replaced by fbdev. Fixed and restarted X and all was well.
What changed this? Will file a bz, but against what? There was no mention of an xorg.conf change during the update and a review of the yum.log doesn't show anything except several mesa component updates and compiz update. Would one of those change xorg.conf?
Start with kudzu, we can go from there. What arch, hardware, etc?
In fact, I think I see why this may be happening. Will attempt to get a fix in for tomorrow.
Bill
Bill Nottingham wrote:
Bill Nottingham (notting@redhat.com) said:
Clyde E. Kunkel (clydekunkel7734@cox.net) said:
Wow, did a rawhide update today catching up two days worth and on reboot got a double blurred screen at what looked like 640x320 resolution. On an alternate terminal looked at xorg.conf and saw that in the device section that radeon had been replaced by fbdev. Fixed and restarted X and all was well.
What changed this? Will file a bz, but against what? There was no mention of an xorg.conf change during the update and a review of the yum.log doesn't show anything except several mesa component updates and compiz update. Would one of those change xorg.conf?
Start with kudzu, we can go from there. What arch, hardware, etc?
In fact, I think I see why this may be happening. Will attempt to get a fix in for tomorrow.
Bill
Looks like fix worked. No probs with kudzu-1.2.48-1 except possibly this msg during boot appended to end of Checking for new hardware msg: -Z: unknown option
Bill Nottingham wrote:
Clyde E. Kunkel (clydekunkel7734@cox.net) said:
Wow, did a rawhide update today catching up two days worth and on reboot got a double blurred screen at what looked like 640x320 resolution. On an alternate terminal looked at xorg.conf and saw that in the device section that radeon had been replaced by fbdev. Fixed and restarted X and all was well.
What changed this? Will file a bz, but against what? There was no mention of an xorg.conf change during the update and a review of the yum.log doesn't show anything except several mesa component updates and compiz update. Would one of those change xorg.conf?
Start with kudzu, we can go from there. What arch, hardware, etc?
Bill
Problem confirmed on a second system with radeon graphics card.
Both x86, both ASUS P4C800 Deluxe mobos with Radeon 9200 cards in AGP slot. Second system has two radeon cards, AGP and PCI, 9200s. Both are rawhide updated thru today.
I believe kudzu could be the culprit since I watched the second system upgrade and checked xorg.conf after the upgrade and **before** rebooting and it had **not** been changed. After reboot on second system, X wouldn't start at all but at least got a message saying so which allowed root logon and found fbdev in the Device section of xorg.conf and the original xorg.conf saved as xorg.conf.backup. Fixed and rebooted, came up fine this time.
Clyde E. Kunkel wrote:
Bill Nottingham wrote:
Clyde E. Kunkel (clydekunkel7734@cox.net) said:
<snip>
Start with kudzu, we can go from there. What arch, hardware, etc?
Bill
Problem confirmed on a second system with radeon graphics card.
Both x86, both ASUS P4C800 Deluxe mobos with Radeon 9200 cards in AGP slot. Second system has two radeon cards, AGP and PCI, 9200s. Both are rawhide updated thru today.
I believe kudzu could be the culprit since I watched the second system
<snip>
Ok, on system with two radeon cards replaced kudzu with an older version, rebooted, then yum update kudzu to 1.2.47-1. Checked xorg.conf, fine. Reboot, saw appended to Checking new hardware init msg something like: Freeing option 0x9678cd8.
At logon time, msgs about couldn't start x server, entered root password then msgs about trying cards 0 thru 3, then msg about trying an alternative configuration and X server did start with S-C-D gui asking for a screen resolution. Gave it 1280x1024 (ususal that I use) and got logon screen at strange resolution which turned out to be 2048x1536. Checked xorg.conf and it was a minimalist one, but it did id the graphics card as radeon and not fbdev. Also, there was an xorg.conf.backup created with fbdev as the driver. Deleted this xorg.conf and .backup and copied over xorg.conf I saved and all is well. Reboot with new kudzu was ok.
Shall I enter a bz for kudzu?
-
Bill Nottingham -
Clyde E. Kunkel