Bug 458033
Summary: | No hardware cursor on F10-Alpha | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kazutoshi Morioka <morioka> |
Component: | xorg-x11-drv-openchrome | Assignee: | Xavier Bachelot <xavier> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | friesenfisch |
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: | 2008-08-28 22:42:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Kazutoshi Morioka
2008-08-06 08:36:34 UTC
Was the hardware cursor working properly with either F8 or F9 ? Created attachment 313574 [details]
/var/log/Xorg.0.log from Fedora 9
Created attachment 313575 [details]
/etc/X11/xorg.conf from Fedora 9
Created attachment 313578 [details]
/var/log/Xorg.0.log from Fedora 10 Alpha with SWCursor
Created attachment 313579 [details]
/var/log/Xorg.0.log from Fedora 10
(In reply to comment #1) > Was the hardware cursor working properly with either F8 or F9 ? Yes, I think so. Attached logs and xorg.conf. please try latest rawhide build (0.2.902-10.fc10): http://koji.fedoraproject.org/koji/taskinfo?taskID=763719 (In reply to comment #7) > please try latest rawhide build (0.2.902-10.fc10): > http://koji.fedoraproject.org/koji/taskinfo?taskID=763719 This works fine. Thank you! Created attachment 313660 [details]
/var/log/Xorg.0.log of xorg-x11-drv-openchrome-0.2.902-10.fc10.x86_64
Although it seems working fine, I got this backtrace:
(==) CHROME(0): Depth 24, (==) framebuffer bpp 32
(==) CHROME(0): RGB weight 888
(==) CHROME(0): Default visual is TrueColor
(--) CHROME(0): Chipset: K8M800/K8N800
(--) CHROME(0): Chipset revision: 0
Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x65) [0x479c05]
1: /lib64/libc.so.6 [0x1a31130]
2: /usr/lib64/libpciaccess.so.0 [0x7db863]
3: /usr/lib64/libpciaccess.so.0 [0x7db9c0]
4: /usr/lib64/libpciaccess.so.0(pci_device_cfg_read+0x2d) [0x7da55d]
5: /usr/lib64/libpciaccess.so.0(pci_device_cfg_read_u8+0x13) [0x7da593]
6: /usr/lib64/xorg/modules/drivers//openchrome_drv.so [0x7fea6c5ff5c6]
7: /usr/bin/Xorg(InitOutput+0x969) [0x463079]
8: /usr/bin/Xorg(main+0x286) [0x42c9d6]
9: /lib64/libc.so.6(__libc_start_main+0xe6) [0x1a1c566]
10: /usr/bin/Xorg(FontFileCompleteXLFD+0x279) [0x42bf89]
Fatal server error:
Caught signal 11. Server aborting
And old bugs are return. Vertical green lines after VT switching. Black screen after Ctrl+Alt+Delete to abort X server. (In reply to comment #10) > And old bugs are return. > Vertical green lines after VT switching. > Black screen after Ctrl+Alt+Delete to abort X server. These bugs are introduced since 0.2.902-9.fc10. No green vertical lines are shown with 0.2.902-8.fc10. so, is the hardware cursor issue fixed or not ? Can the backtrace be triggered all the time or not ? The code that probe the video ram amount has not been modified, so this is a bit strange. Also the VT switch issues are known, but this probably belongs to another bug report. (In reply to comment #12) > so, is the hardware cursor issue fixed or not ? Can the backtrace be triggered > all the time or not ? The code that probe the video ram amount has not been > modified, so this is a bit strange. Also the VT switch issues are known, but > this probably belongs to another bug report. 0.2.902-10.fc10 fixed hardware cursor issue. Backtrace was triggered occasionally, not every time. I saw backtraces two times, but I can not reproduce it. Hardware cursor is working again, so I close this bug. Please open new bugs for the other issues if you're still affected. Thanks and regards, Xavier *** Bug 470841 has been marked as a duplicate of this bug. *** |