| Summary: | display messed up (box instead of mouse, no background, poor readrawing) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michal Hlavinka <mhlavink> | ||||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | rawhide | CC: | airlied, ajax, awilliam, bskeggs, twaugh | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-05-04 20:13:31 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Michal Hlavinka
2009-03-26 13:24:29 UTC
Does it behave any differently if you try it with KMS? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #1) > Does it behave any differently if you try it with KMS? yes, system gets frozen 1)without kms messed display (see bug description), unusable but system works 2)kms and 2 LCD (first wide, second normal) during the boot, splash is visible, but - it's not completely smooth (I don't know if it should be) = in about one third of the progress it blinks once - window on the first screen is not wide - empty place on the right side, this is fixed just in the end of the boot - after progress bar reaches the end, splash stops the animation and after few seconds both lcd goes black, system doesn't respond to mouse, keyboard, power button 3)kms and one LCD - situation is the same, but splash covers wide screen completely --------------- after reboot to init 3, Xorg.0.log is empty tested with updated nouveau driver fast user switching works, but display is messed up even more (missing fonts) X server restarting makes no difference Thanks. Can you attach the usual log files (/var/log/Xorg.0.log , possibly ~/.xsession-errors if there's anything interesting in it) and then we can assign this? Thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Created attachment 337488 [details]
Xorg.0.log
tested with xorg-x11-drv-nouveau-0.0.12-20.20090330git9d46930.fc11.x86_64 and xorg-x11-server-Xorg-1.6.0-16.fc11.x86_64
Created attachment 337489 [details]
~/.xsession-errors
xsession-errors is probably useless
thanks a lot. Can I grab an update on how things are with current versions of xorg-11-drv-nouveau and the kernel? If things are still bad, fresh logs would be useful as things have changed a little since the last lot. ^ - it's not completely smooth (I don't know if it should be) = in about one ^ third of the progress it blinks once It should be smooth, and is in the situations I've seen so far. If X decides to choose a different mode for your displays as it starts however, it may flicker there. ^ - window on the first screen is not wide - empty place on the right side, this ^ is fixed just in the end of the boot This is the intended behaviour. fbcon will attempt to program all displays to their preferred modes to avoid a modeset as X starts (for the smooth transition to X). Unfortunately, fbcon expects a single framebuffer, so you get a framebuffer the size of the smallest screen. (In reply to comment #7) > Can I grab an update on how things are with current versions of > xorg-11-drv-nouveau and the kernel? Updated rawhide works (tried: playing video, modeset and dualhead) > ^ - it's not completely smooth (I don't know if it should be) = in about one > ^ third of the progress it blinks once > It should be smooth, and is in the situations I've seen so far. If X decides > to choose a different mode for your displays as it starts however, it may > flicker there. it's smooth now I think you can close this bug now |