[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: update to xorg-x11-drv-ati-6.10.0-1.fc10.x86_64 breaks X



On Sun, Feb 08, 2009 at 15:20:04 -0500,
  "D. Hugh Redelmeier" <hugh mimosa com> wrote:
> X broke on me with recent updates.  Has anyone else experienced
> a problem like this?

Yes. Some of these appear to be related to kernel modesetting as the bug(s)
change with kernel versions. You might try using or not using the
nomodeset kernel parameter. Depending on which kernel I am using, sometimes
I need to use it and sometimes I must not use it.

> 
> When I downgrade from
>   xorg-x11-drv-ati-6.10.0-1.fc10.x86_64
> to 
>   xorg-x11-drv-ati-6.9.0-63.fc10.x86_64
> X started working again.
> 
> Symptom: my login screen is blank.  Ctrl-Alt-F2 works so at least some
> of X is working.
> 
> I intend to Bugzilla this but more info from list subscribers would be
> useful.
> 
> Longer story:
> 
> Last night I updated my desktop.  After reboot, the display is blank.  
> Fedora 10 is running -- I'm typing this on a text console.  But X isn't 
> working.
> 
> It seems that the problem was created by updates that were made available 
> between 2009 Feb 3 @ 1:30AM EST (the date of my previous update) and 2009 
> Feb 7 @ 23:03 EST (this update).  According to /var/log/yum.log, these 
> are the xorg packages that were updated:
>  xorg-x11-drv-ati-6.10.0-1.fc10.x86_64
>  xorg-x11-drv-evdev-2.1.1-1.fc10.x86_64
>  xorg-x11-drv-vmmouse-12.6.3-1.fc10.x86_64
>  xorg-x11-drv-keyboard-1.3.2-1.fc10.x86_64
> Sadly, yum.log does not seem to say what version was replaced.
> 
> My bet is that the ati driver is the problem.
> 
> Perhaps the previous version of drv-ati was:
> Dec 26 01:48:16 Updated: xorg-x11-drv-ati-6.9.0-63.fc10.x86_64
> 
> Where are you supposed to find old update packages?
> xorg-x11-drv-ati-6.9.0-63.fc10.x86_64 is not on the original F10 DVD
> nor is it in up to date update mirrors.  This would seem to be a bit
> problem.  Luckily I found it on a slow-to-mirror mirror.
> 
> I'm looking at /var/log/Xorg.0.log and comparing it with the log from
> the working setup.  I will show the chunks of differences that I think
> are interesting.
> 
> I did "diff -u Xorg.0.log.old Xorg.0.log" so lines prefixed by - are
> old, lines prefixed by + are new, and lines prefixed by a space are
> common.
> 
> | (II) Module ati: vendor="X.Org Foundation"
> |-	compiled for 1.5.3, module version = 6.9.0
> |+	compiled for 1.5.3, module version = 6.10.0
> The ATI driver went from 6.9.0.something to 6.10.0.something
> 
> | (II) Loading /usr/lib64/xorg/modules/drivers//radeon_drv.so
> |-	compiled for 1.5.3, module version = 6.9.0
> |+	compiled for 1.5.3, module version = 6.10.0
> I think that this is just the same thing.
> 
> |-(--) RADEON(0): Chipset: "ATI ATI Radeon HD 3600 XT" (ChipID = 0x9598)
> |+(--) RADEON(0): Chipset: "ATI Radeon HD 3600 XT" (ChipID = 0x9598)
> Looks like a typo got fixed.  I actually quoted this to show what my
> display hardware is.   It is called an "Asus EAH3650 Silent Magic".
> 
> | (II) RADEON(0): Port0:
> |  Monitor   -- AUTO
> |  Connector -- HDMI-B
> |- DAC Type  -- TVDAC/ExtDAC
> |+ DAC Type  -- None
> |  TMDS Type -- UNIPHY
> |  DDC Type  -- 0x7e50
> 
> I don't know what this means.  I'm not sure which connector number I'm
> using.  The card has no HDMI connector.  It has two DVI connectors and
> an S-Video connector.  One of the DVI connectors is Dual-Link, and
> that is what I'm using (my monitor requires dual-link).
> 
> | (II) RADEON(0): Output: HDMI-0, Detected Monitor Type: 0
> |-Dac detection success
> |+invalid output device for dac detection
> This doesn't look good.
> 
> | (II) RADEON(0): Output: HDMI-0, Detected Monitor Type: 0
> |-Dac detection success
> |+invalid output device for dac detection
> Seems like a repeat.  Why?
> 
> | (II) RADEON(0): EDID for output HDMI-0
> | (II) RADEON(0): EDID for output DVI-0
> | (II) RADEON(0): Manufacturer: DEL  Model: 4016  Serial#: 1194472500
> I guess that means that my monitor is connected to DVI-0.
> 
> |-Output DIG2 dpms success
> |+Output DIG0 dpms success
> Does this difference mean anything?
> It appears three times for some reason.
> 
> | Set CRTC 0 Source success
> |-(II) RADEON(0): DIG2: Coherent Mode enabled
> |-Output DIG2 setup success
> |+Output DIG1 encoder setup success
> |+(II) RADEON(0): DIG2 transmitter: Coherent Mode enabled
> | Output DIG2 transmitter setup success
> |-Output DIG2 dpms success
> |+Output DIG0 dpms success
> | Enable CRTC memreq 0 success
> This seems confusing.  Why does the new config ever mention DIG2 when
> it seems to have renumbered DIG2 to DIG0?
> 
> | Set CRTC 0 Source success
> |-(II) RADEON(0): DIG2: Coherent Mode disabled
> |-Output DIG2 setup success
> |+Output DIG1 encoder setup success
> |+(II) RADEON(0): DIG2 transmitter: Coherent Mode enabled
> | Output DIG2 transmitter setup success
> |-Output DIG2 dpms success
> |+Output DIG0 dpms success
> Similarly confusing.
> 
> There are some keyboard-related diffs, but I don't think that they are
> relevant.
> 
> | (II) RADEON(0): Output: HDMI-0, Detected Monitor Type: 0
> |-Dac detection success
> |-(II) RADEON(0): EDID for output HDMI-0
> |-(II) RADEON(0): EDID for output DVI-0
> |-(II) RADEON(0): Manufacturer: DEL  Model: 4016  Serial#: 1194472500
> | ...
> |-(II) RADEON(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
> |-(II) RADEON(0): Output: HDMI-0, Detected Monitor Type: 0
> |+invalid output device for dac detection
> Lots and lots of juicy lines missing after update.
> 
> | (II) RADEON(0): Output: HDMI-0, Detected Monitor Type: 0
> |-Dac detection success
> |+invalid output device for dac detection
> This sequence appears a bunch of times.
> 
> -- 
> 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


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]