| Summary: | Blurred screen with latest drm-next-radeon and KMS | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | DF5JT <ke4unq> | ||||||||
| Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||||||
| Status: | RESOLVED MOVED | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | medium | CC: | aidan, martinstolpe | ||||||||
| Version: | DRI git | ||||||||||
| Hardware: | x86 (IA32) | ||||||||||
| OS: | Linux (All) | ||||||||||
| URL: | http://bloatware.de/bugs/20032010081.mp4 | ||||||||||
| Whiteboard: | |||||||||||
| i915 platform: | i915 features: | ||||||||||
| Attachments: |
|
||||||||||
There are further screenshots at this location: http://bloatware.de/bugs/200320101079.jpg http://bloatware.de/bugs/200320101080.jpg http://bloatware.de/bugs/200320101081.jpg http://bloatware.de/bugs/200320101082.jpg http://bloatware.de/bugs/200320101083.jpg And here is a short video which shows the irregular switching back to regular resolution and no garbling: http://bloatware.de/bugs/20032010081.mp4 Hardware is an IBM Thinkpad with a FireGL V5200, 3GB, Ram, T5600 Core2Duo Processor and 1600x1200 Flexview Display. Created attachment 34260 [details]
Logfile
What kernel are you using? Can you attach your dmesg? Created attachment 34264 [details]
dmesg from garbled screen
Kernel is compiled from up to date git drm-next-radeon on x86 platform with Fedora 12 userland.
(In reply to comment #5) > Created an attachment (id=34264) [details] > dmesg from garbled screen > > Kernel is compiled from up to date git drm-next-radeon on x86 platform with > Fedora 12 userland. Plus all patches from: http://people.freedesktop.org/~agd5f/pm2/ which could all be applied cleanly. is this similar to/same as fdo #25622? (In reply to comment #6) > (In reply to comment #5) > > Created an attachment (id=34264) [details] [details] > > dmesg from garbled screen > > > > Kernel is compiled from up to date git drm-next-radeon on x86 platform with > > Fedora 12 userland. > > Plus all patches from: > > > http://people.freedesktop.org/~agd5f/pm2/ > > which could all be applied cleanly. > Which ones didn't apply? I wouldn't recommend that patch set unless you apply all of them (they apply to drm-radeon-testing). Do you still have problems without those patches applied? (In reply to comment #8) > (In reply to comment #6) > > (In reply to comment #5) > > > Created an attachment (id=34264) [details] [details] [details] > > > dmesg from garbled screen > > > > > > Kernel is compiled from up to date git drm-next-radeon on x86 platform with > > > Fedora 12 userland. > > > > Plus all patches from: > > > > > > http://people.freedesktop.org/~agd5f/pm2/ > > > > which could all be applied cleanly. > > > > Which ones didn't apply? I wouldn't recommend that patch set unless you apply > all of them (they apply to drm-radeon-testing). Do you still have problems > without those patches applied? I pulled a clean, full tree from airlied's drm-next-radeon tree and applied all the 30 patches from your repo and that's what doesn't work. However, there is a slight chance that this is actually hardware related. I have had the LCD inverter changed last week, because of a backlight failure and I have now found out that it was a temperature related problem (notebook staying in a rather cool room overnight), which spontaneously disappears when the laptop gets back to room temperature. It likely is a problem either with the GPU itself or the video RAM and I expect to have it replaced either tomorrow or day after. I will report back as soon as I am sure that my hardware is running flawlessly. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/110. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 34256 [details] Login screen garbled Right after the initrd is loaded and console switches to KMS native resolution, the screen gets garbled. There are vertical blurs approximately every 1 cm of horizontal screen space. These blurs repeat regions of previous screen extate so the visible screen is only 2/3 of its true full size. Difficult to explain, therefore attached screenshots with a camera. Sometimes, in irregular intervals the screen "resettles and shows its true size. This is both with dypm enabled and disabled. Booting without KMS is fine, no garbage on scree, both on console and under X.